From chenjie.xu at intel.com Thu Nov 1 08:27:58 2018 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Thu, 1 Nov 2018 08:27:58 +0000 Subject: [Starlingx-discuss] Analysis of patch 9f926a5 for StartlingX upstreaming Message-ID: Hi Matt/Allain, We analyze the patch 9f926a5 related to l2pop. An RFE "Add l2pop support for floating ip resources" has been written and is attached. The test case is provided by Allain. Could you please help to review and comment? Thanks very much! Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: RFE_ADD_L2POP_SUPPORT_FOR_FLOATINGIP_RESOURCES.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 92905 bytes Desc: RFE_ADD_L2POP_SUPPORT_FOR_FLOATINGIP_RESOURCES.docx URL: From aragorn at intel.com Thu Nov 1 09:37:39 2018 From: aragorn at intel.com (aragorn at intel.com) Date: 01 Nov 2018 02:37:39 -0700 Subject: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report Message-ID: [mirror-downloader][#119] Missing packages. Results report: - Missing: logs/L1_srpms_missing_centos.log lighttpd-1.4.50-1.el7.src.rpm - Missing GPG key: ./output/stx-r1/CentOS/pike/Source/libvirt-python-4.7.0-1.fc28.src.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#596bea5d) From Volker.Hoesslin at swsn.de Thu Nov 1 10:45:45 2018 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Thu, 1 Nov 2018 10:45:45 +0000 Subject: [Starlingx-discuss] Compute boot-loop Message-ID: Hello, there, i have now built a complete stack and believe i did everything right. after unlocking the compute nodes (two pieces), the nodes come into an endless boot loop. Error messages are not really noticeable, except: compute-X 'ceilometer-polling' process has failed. Auto recovery in progress any suggestions? Greez & thx, volker... -------------- next part -------------- An HTML attachment was scrubbed... URL: From liang.a.fang at intel.com Thu Nov 1 10:50:16 2018 From: liang.a.fang at intel.com (Fang, Liang A) Date: Thu, 1 Nov 2018 10:50:16 +0000 Subject: [Starlingx-discuss] About the patch "LVM thin provisioning allocation checks" Message-ID: Hi repo: cinder patch commit id: 2db603a70885823413440c627cace7e3662d0a14 patch title: Pike Rebase: LVM thin provisioning allocation checks I'm working on upstream this patch, but I cannot reproduce the issue. It was originally submitted in year 2016. Is it still needed? If so, could you please provide some info to reproduce this issue? If not, I will abandon this patch. My experiment on this patch: - When I try to create snapshot, the over allocation will be captured by cinder-scheduler. The over allocation will not happen. See: cinder snapshot-create 8e9dba20-2c10-4334-ac51-a1c99421ddbb --name snap3 --description desc3 stack at ceph01liang:~/cinder$ cinder snapshot-list +--------------------------------------+--------------------------------------+-----------+-------+------+----------------------------------+ | ID | Volume ID | Status | Name | Size | User ID | +--------------------------------------+--------------------------------------+-----------+-------+------+----------------------------------+ | 6bf19443-9964-48a7-8094-b3345e7f5434 | 8e9dba20-2c10-4334-ac51-a1c99421ddbb | error | snap3 | 10 | 5255f4922a4340b482b11bbbe7083ee4 | | 887f8584-21e0-41fe-9d08-0c53d642544b | 4bfb4724-b546-4fe9-ba89-6a1f938bd4d1 | available | snap1 | 1 | 5255f4922a4340b482b11bbbe7083ee4 | | 8dc12252-2680-4089-b134-7280f037784f | 8e9dba20-2c10-4334-ac51-a1c99421ddbb | error | snap3 | 10 | 5255f4922a4340b482b11bbbe7083ee4 | | fd61ff3c-4f58-4fc3-a5bd-219eb9b034a6 | 4bfb4724-b546-4fe9-ba89-6a1f938bd4d1 | available | snap2 | 1 | 5255f4922a4340b482b11bbbe7083ee4 | +--------------------------------------+--------------------------------------+-----------+-------+------+----------------------------------+ stack at ceph01liang:~/cinder$ cinder list +--------------------------------------+-----------+------+------+-------------+----------+--------------------------------------+ | ID | Status | Name | Size | Volume Type | Bootable | Attached to | +--------------------------------------+-----------+------+------+-------------+----------+--------------------------------------+ | 25959746-7655-4cf4-a959-6ce8a80eb6fc | in-use | | 1 | lvmdriver-1 | true | 4d963313-4ffc-47fc-a075-6c72082ed121 | | 4bfb4724-b546-4fe9-ba89-6a1f938bd4d1 | available | vol1 | 1 | lvmdriver-1 | true | | | 8e9dba20-2c10-4334-ac51-a1c99421ddbb | available | vol3 | 10 | lvmdriver-1 | true | | | de55aad2-8424-4f2b-a769-0da85daa1889 | available | vol2 | 2 | lvmdriver-1 | true | | +--------------------------------------+-----------+------+------+-------------+----------+--------------------------------------+ (Pdb) pp backends [host 'ceph01liang at lvmdriver-1#lvmdriver-1':free_capacity_gb: 22.76, total_capacity_gb: 22.8,allocated_capacity_gb: 15, max_over_subscription_ratio: 1.0,reserved_percentage: 0, provisioned_capacity_gb: 17.0,thin_provisioning_support: True, thick_provisioning_support: False,pools: None,updated at: 2018-11-01 08:54:58.143006] - When I try to create a volume from a volume (a snapshot will be created during this op), what called is create_lv_snapshot, not create_snapshot. So the check in create_snapshot will not be called. Thanks Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From doantungbk.203 at gmail.com Thu Nov 1 12:43:58 2018 From: doantungbk.203 at gmail.com (Tung Doan) Date: Thu, 1 Nov 2018 13:43:58 +0100 Subject: [Starlingx-discuss] Propose OpenStack/Apmec to StarlingX like an upstream component Message-ID: Hi StarlingX team, I am Tung Doan - An OpenStack contributor and the PTL of OpenStack/Apmec project. Since we acknowledged the potential integration between Apmec and StarlingX, I am writing this email to propose adding OpenStack/Apmec to StarlingX like an upstream project. Project description: OpenStack Apmec [1] stands for the Automated Provisioning Framework for Multi-access Edge Computing which is the first orchestration and management framework dedicated to the MEC services in OpenStack. Below are some of the outstanding features of Apmec project: - Apmec is partly designed following the ETSI MEC standard [2] with the great support from industries. The detailed design of Apmec is elaborated in [3]. - Apmec allows for the automated provisioning of the MEC services under the joint orchestration with NFV MANO frameworks [4]. In our design, the NFV MANO frameworks (such as ONAP or OSM) take care of complex network functions while Apmec is dedicated to the MEC applications (AR/VR, tactile engine support, traffic tracking,...). We planned to support multi-MANO feature [5] which opens up the opportunities to cooperate with the existing MANO frameworks for the delivery of the MEC services. For the implementation, Apmec is currently integrated with Tacker [6] which is NFV MANO framework in OpenStack. - Apmec is the MEC framework which designs a rich modeling language for MEC applications and services following the design of Topology and Orchestration Specification for Cloud Application (TOSCA) [7]. Such a feature was implemented in [8]. - Apmec leveraged the existing OpenStack projects to validate the description of the MEC applications and services (using OpenStack Tosca Parser) and translate them (using OpenStack Heat Translator) to OpenStack resources. - Since computing resources at MEC are limited, we designed a heuristic algorithm that allows for MEC service providers to save their hardware resources. When integrated with Apmec, StarlingX will greatly benefit from: - no need to take care of the NFV functionalities. Since existing NFV MANO frameworks (Tacker, ONAP, OSM, OpenBaton,...) are diverse, integrating them can make StarlingX complicated. Apmec was designed to take over responsibility for integrating them since the delivery of MEC services is our critical mission. - no need to take care of the life-cycle management of the MEC applications. Apmec offers API to help StarlingX perform this function. As mentioned earlier, Apmec is OpenStack project, therefore, to provide low-latency for MEC applications, Apmec is also planned to support acceleration technologies (e.g, integrated with OpenStack Cyborg) such as DPDK and FPGA. [1] https://github.com/openstack/apmec [2] https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/01.01.01_60/gs_MEC003v010101p.pdf [3] https://arxiv.org/pdf/1805.09251.pdf [4] https://www.etsi.org/deliver/etsi_gs/NFV-MAN/001_099/001/01.01.01_60/gs_NFV-MAN001v010101p.pdf [5] https://blueprints.launchpad.net/apmec/+spec/multi-mano [6] https://wiki.openstack.org/wiki/Tacker [7] https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tosca [8] https://review.openstack.org/#/c/570797/ -- Name: Doan Van Tung Email: van_tung.doan at mailbox.tu-dresden.de A member of 5G Lab Germany *Deutsche Telekom Chair of Communication Networks (ComNets)* *Würzburger Str. 35, 01187 Dresden* *TU Dresden, Germany* -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.cordoba.malibran at intel.com Thu Nov 1 13:11:37 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Thu, 1 Nov 2018 13:11:37 +0000 Subject: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report In-Reply-To: References: Message-ID: <4EA80D98-75AF-4DB1-A6B4-9ED5FAC99FC6@intel.com> Lighttpd was upgraded in upstream: Package lighttpd-1.4.50-1.el7.src not found, available lighttpd-1.4.51-1.el7.src We'll send a patch for master today. Should we backport this to r/2018.10 branch? -Erich On 11/1/18, 3:37 AM, "aragorn at intel.com" wrote: [mirror-downloader][#119] Missing packages. Results report: - Missing: logs/L1_srpms_missing_centos.log lighttpd-1.4.50-1.el7.src.rpm - Missing GPG key: ./output/stx-r1/CentOS/pike/Source/libvirt-python-4.7.0-1.fc28.src.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#596bea5d) From cindy.xie at intel.com Thu Nov 1 13:53:00 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Thu, 1 Nov 2018 13:53:00 +0000 Subject: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report In-Reply-To: <4EA80D98-75AF-4DB1-A6B4-9ED5FAC99FC6@intel.com> References: <4EA80D98-75AF-4DB1-A6B4-9ED5FAC99FC6@intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35DB1360@SHSMSX104.ccr.corp.intel.com> + Zhipeng We still have patches on lighttpd and it was rebased to 1.4.50 recently by Zhipeng. If the srpm upgraded to 1.4.51, Zhipeng can you please work w/ Erich and see if those patches need rework? Thx. - cindy -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Thursday, November 1, 2018 6:12 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report Lighttpd was upgraded in upstream: Package lighttpd-1.4.50-1.el7.src not found, available lighttpd-1.4.51-1.el7.src We'll send a patch for master today. Should we backport this to r/2018.10 branch? -Erich On 11/1/18, 3:37 AM, "aragorn at intel.com" wrote: [mirror-downloader][#119] Missing packages. Results report: - Missing: logs/L1_srpms_missing_centos.log lighttpd-1.4.50-1.el7.src.rpm - Missing GPG key: ./output/stx-r1/CentOS/pike/Source/libvirt-python-4.7.0-1.fc28.src.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#596bea5d) _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Brent.Rowsell at windriver.com Thu Nov 1 13:55:36 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Thu, 1 Nov 2018 13:55:36 +0000 Subject: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F35DB1360@SHSMSX104.ccr.corp.intel.com> References: <4EA80D98-75AF-4DB1-A6B4-9ED5FAC99FC6@intel.com> <2FD5DDB5A04D264C80D42CA35194914F35DB1360@SHSMSX104.ccr.corp.intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB2F0821@ALA-MBD.corp.ad.wrs.com> This needs to be functionally tested before it is pushed. Brent -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Thursday, November 1, 2018 9:53 AM To: Cordoba Malibran, Erich ; starlingx-discuss at lists.starlingx.io; Liu, ZhipengS Subject: Re: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report + Zhipeng We still have patches on lighttpd and it was rebased to 1.4.50 recently by Zhipeng. If the srpm upgraded to 1.4.51, Zhipeng can you please work w/ Erich and see if those patches need rework? Thx. - cindy -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Thursday, November 1, 2018 6:12 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report Lighttpd was upgraded in upstream: Package lighttpd-1.4.50-1.el7.src not found, available lighttpd-1.4.51-1.el7.src We'll send a patch for master today. Should we backport this to r/2018.10 branch? -Erich On 11/1/18, 3:37 AM, "aragorn at intel.com" wrote: [mirror-downloader][#119] Missing packages. Results report: - Missing: logs/L1_srpms_missing_centos.log lighttpd-1.4.50-1.el7.src.rpm - Missing GPG key: ./output/stx-r1/CentOS/pike/Source/libvirt-python-4.7.0-1.fc28.src.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#596bea5d) _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Volker.Hoesslin at swsn.de Thu Nov 1 16:12:26 2018 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Thu, 1 Nov 2018 16:12:26 +0000 Subject: [Starlingx-discuss] Compute boot-loop In-Reply-To: References: Message-ID: Maybe it helps: https://ibb.co/n2OgoL ---------------------------------------------------------------- Hello, there, i have now built a complete stack and believe i did everything right. after unlocking the compute nodes (two pieces), the nodes come into an endless boot loop. Error messages are not really noticeable, except: compute-X 'ceilometer-polling' process has failed. Auto recovery in progress any suggestions? Greez & thx, volker... -------------- next part -------------- An HTML attachment was scrubbed... URL: From michel.thebeau at windriver.com Thu Nov 1 16:28:53 2018 From: michel.thebeau at windriver.com (Michel Thebeau) Date: Thu, 1 Nov 2018 12:28:53 -0400 Subject: [Starlingx-discuss] Compute boot-loop In-Reply-To: References: Message-ID: <1e1ebab5-998b-3c27-fc68-4360e148315f@windriver.com> Hi Volker, Could you describe the instructions you were using to setup startlingx (were you following a wiki online)?  Did you recheck the instructions versus what is actually configured on the computes? How many cpus do your computes have? Which build are you using?  Did you build your own? When reboot-loop happens on a node often the error will be presented on the console during boot or could be inferred from console, sometimes referring to puppet logs of the node /var/log/puppet/ M On 2018-11-01 6:45 a.m., von Hoesslin, Volker wrote: > Hello, there, > i have now built a complete stack and believe i did everything right. after unlocking the compute nodes (two pieces), the nodes come into an endless boot loop. > Error messages are not really noticeable, except: > compute-X 'ceilometer-polling' process has failed. Auto recovery in progress > > any suggestions? Greez & thx, volker... > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dtroyer at gmail.com Thu Nov 1 17:16:18 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Thu, 1 Nov 2018 12:16:18 -0500 Subject: [Starlingx-discuss] Propose OpenStack/Apmec to StarlingX like an upstream component In-Reply-To: References: Message-ID: On Thu, Nov 1, 2018 at 7:44 AM Tung Doan wrote: > I am Tung Doan - An OpenStack contributor and the PTL of OpenStack/Apmec project. Since we acknowledged the potential integration between Apmec and StarlingX, I am writing this email to propose adding OpenStack/Apmec to StarlingX like an upstream project. > > Project description: OpenStack Apmec [1] stands for the Automated Provisioning Framework for Multi-access Edge Computing which is the first orchestration and management framework dedicated to the MEC services in OpenStack. Below are some of the outstanding features of Apmec project: I believe Apmec is not an official OpenStack project (as listed in [0]), do you have plans to apply to become an official OpenStack project under TC governance? (Until then you do need to be careful about referring to Apmec as 'an OpenStack project', it is hosted by OpenStack, but is not (yet?) an OpenStack project.) > - no need to take care of the NFV functionalities. Since existing NFV MANO frameworks (Tacker, ONAP, OSM, OpenBaton,...) are diverse, integrating them can make StarlingX complicated. Apmec was designed to take over responsibility for integrating them since the delivery of MEC services is our critical mission. Is this replacing existing StarlingX functionality? > - no need to take care of the life-cycle management of the MEC applications. Apmec offers API to help StarlingX perform this function. As mentioned earlier, Apmec is OpenStack project, therefore, to provide low-latency for MEC applications, Apmec is also planned to support acceleration technologies (e.g, integrated with OpenStack Cyborg) such as DPDK and FPGA. Can you get more specific about what the integration with StarlingX looks like? dt [0] https://governance.openstack.org/tc/reference/projects/index.html -- Dean Troyer dtroyer at gmail.com From juan.carlos.alonso at intel.com Thu Nov 1 22:38:40 2018 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Thu, 1 Nov 2018 22:38:40 +0000 Subject: [Starlingx-discuss] Compute boot-loop In-Reply-To: <1e1ebab5-998b-3c27-fc68-4360e148315f@windriver.com> References: <1e1ebab5-998b-3c27-fc68-4360e148315f@windriver.com> Message-ID: <8557B550001AFB46A43A0CCC314BF85153C592E1@FMSMSX108.amr.corp.intel.com> Hi, I think you set up a Duplex system (two controllers), right? I set up a Duplex system with two ISOs: stx-2018-10-30-171-master.iso and stx-2018-11-01-8-master.iso I faced the same issue you mention with first ISO, but did not with today's ISO: stx-2018-11-01-8-master.iso. Please set up again a Duplex system with today's ISO to see if issue is still presented. Regards. Juan Carlos Alonso -----Original Message----- From: Michel Thebeau [mailto:michel.thebeau at windriver.com] Sent: Thursday, November 1, 2018 10:29 AM To: von Hoesslin, Volker ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] Compute boot-loop Hi Volker, Could you describe the instructions you were using to setup startlingx (were you following a wiki online)?  Did you recheck the instructions versus what is actually configured on the computes? How many cpus do your computes have? Which build are you using?  Did you build your own? When reboot-loop happens on a node often the error will be presented on the console during boot or could be inferred from console, sometimes referring to puppet logs of the node /var/log/puppet/ M On 2018-11-01 6:45 a.m., von Hoesslin, Volker wrote: > Hello, there, > i have now built a complete stack and believe i did everything right. after unlocking the compute nodes (two pieces), the nodes come into an endless boot loop. > Error messages are not really noticeable, except: > compute-X 'ceilometer-polling' process has failed. Auto recovery in progress > > any suggestions? Greez & thx, volker... > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cesar.lara at intel.com Thu Nov 1 22:58:19 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Thu, 1 Nov 2018 22:58:19 +0000 Subject: [Starlingx-discuss] [build][meetings] Meeting minutes 11/1/2018 Message-ID: <0B566C62EC792145B40E29EFEBF1AB4710556C6D@fmsmsx104.amr.corp.intel.com> Build team meeting minutes 11/1/2018 Attendees Ken, Jason, Scott, Memo, Erich, Marcela, Victor, Chuy, Cesar, Luis Cengn Status -Mirror is now completed and operational, the wiki has been updated with the details for Cengn and our partnership, the details and specs are already there. -The scripts that are related with mirror download are now pointing to Cengn repos and are waiting in the queue to be reviewed tested and merged, the desired date for fully operational mirror is November 5th - Now changes to the packages required to build will be caught by Cengn mirror within one day, the scripts will try to download first from Cengn and if is still not available will try to go get the packages from upstream. Koji follow up -presentation on a possible scenario hosting Koji and demo on using Koji based built packages with our current build scripts. -discussion followed up by implementation details led to different points of view about the problem we have to solve if there's any, the amount of effort to integrate tooling as we know Koji doesn't solve every use case by itself and where to host a Koji service(we are striving to host a centralized service for the whole community). -The statement we are using to follow thru with Koji versus our current script is that we will require a lot of effort to support multi OS with the current tools. We had to defer the topic of mirror script refactored using Python. We will start a thread on the goals this team has for next release on the mailing list. Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.cordoba.malibran at intel.com Thu Nov 1 23:01:46 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Thu, 1 Nov 2018 23:01:46 +0000 Subject: [Starlingx-discuss] [Build] Question about meta_patches Message-ID: <05124ef14c610cef028774c818b98681efeab12b.camel@intel.com> Hi all, As I understand, the meta_patches are patches that are applied to the specfiles for projects where a SRPM is downloaded. This process is something like: - Unpack srpm - Apply patches to the .spec file. Most of this patches are just modifications to add source code patches. - Create a new srpm with the source, the modified specfile and additional patches that will be applied on build time. So, having this process, I'm wondering in the need of having the meta_patches instead in just one .spec checked in the repository. Also, I'm trying to understand the rationale behind these meta_patches. Thank you in advance. -Erich From zhipengs.liu at intel.com Fri Nov 2 00:53:27 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Fri, 2 Nov 2018 00:53:27 +0000 Subject: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F35DB1360@SHSMSX104.ccr.corp.intel.com> References: <4EA80D98-75AF-4DB1-A6B4-9ED5FAC99FC6@intel.com> <2FD5DDB5A04D264C80D42CA35194914F35DB1360@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C752FF12D9@SHSMSX104.ccr.corp.intel.com> Hi Erich, There is an error introduced by 1.4.50 that I fixed during 7.5 upgrade. It can block applying manifest step during deployment. Please refer to my patch for 7.5 upgrade and feel free to contact me if you have any question. https://review.openstack.org/#/c/596263/ Thx! -Zhipeng -----Original Message----- From: Xie, Cindy Sent: 2018年11月1日 21:53 To: Cordoba Malibran, Erich ; starlingx-discuss at lists.starlingx.io; Liu, ZhipengS Subject: RE: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report + Zhipeng We still have patches on lighttpd and it was rebased to 1.4.50 recently by Zhipeng. If the srpm upgraded to 1.4.51, Zhipeng can you please work w/ Erich and see if those patches need rework? Thx. - cindy -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Thursday, November 1, 2018 6:12 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report Lighttpd was upgraded in upstream: Package lighttpd-1.4.50-1.el7.src not found, available lighttpd-1.4.51-1.el7.src We'll send a patch for master today. Should we backport this to r/2018.10 branch? -Erich On 11/1/18, 3:37 AM, "aragorn at intel.com" wrote: [mirror-downloader][#119] Missing packages. Results report: - Missing: logs/L1_srpms_missing_centos.log lighttpd-1.4.50-1.el7.src.rpm - Missing GPG key: ./output/stx-r1/CentOS/pike/Source/libvirt-python-4.7.0-1.fc28.src.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#596bea5d) _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From yong.hu at intel.com Fri Nov 2 01:19:13 2018 From: yong.hu at intel.com (Hu, Yong) Date: Fri, 2 Nov 2018 01:19:13 +0000 Subject: [Starlingx-discuss] Compute boot-loop In-Reply-To: <8557B550001AFB46A43A0CCC314BF85153C592E1@FMSMSX108.amr.corp.intel.com> References: <1e1ebab5-998b-3c27-fc68-4360e148315f@windriver.com> <8557B550001AFB46A43A0CCC314BF85153C592E1@FMSMSX108.amr.corp.intel.com> Message-ID: Another head-up is that we need to assure VT is turned on in BIOS for the compute node. On 02/11/2018, 6:39 AM, "Alonso, Juan Carlos" wrote: Hi, I think you set up a Duplex system (two controllers), right? I set up a Duplex system with two ISOs: stx-2018-10-30-171-master.iso and stx-2018-11-01-8-master.iso I faced the same issue you mention with first ISO, but did not with today's ISO: stx-2018-11-01-8-master.iso. Please set up again a Duplex system with today's ISO to see if issue is still presented. Regards. Juan Carlos Alonso -----Original Message----- From: Michel Thebeau [mailto:michel.thebeau at windriver.com] Sent: Thursday, November 1, 2018 10:29 AM To: von Hoesslin, Volker ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] Compute boot-loop Hi Volker, Could you describe the instructions you were using to setup startlingx (were you following a wiki online)? Did you recheck the instructions versus what is actually configured on the computes? How many cpus do your computes have? Which build are you using? Did you build your own? When reboot-loop happens on a node often the error will be presented on the console during boot or could be inferred from console, sometimes referring to puppet logs of the node /var/log/puppet/ M On 2018-11-01 6:45 a.m., von Hoesslin, Volker wrote: > Hello, there, > i have now built a complete stack and believe i did everything right. after unlocking the compute nodes (two pieces), the nodes come into an endless boot loop. > Error messages are not really noticeable, except: > compute-X 'ceilometer-polling' process has failed. Auto recovery in progress > > any suggestions? Greez & thx, volker... > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From shuicheng.lin at intel.com Fri Nov 2 03:12:03 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Fri, 2 Nov 2018 03:12:03 +0000 Subject: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report In-Reply-To: <93814834B4855241994F290E959305C752FF12D9@SHSMSX104.ccr.corp.intel.com> References: <4EA80D98-75AF-4DB1-A6B4-9ED5FAC99FC6@intel.com> <2FD5DDB5A04D264C80D42CA35194914F35DB1360@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752FF12D9@SHSMSX104.ccr.corp.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C765FE3A6AE@SHSMSX101.ccr.corp.intel.com> Hi Erich, I could find the src rpm with below repo (./centos-mirror-tools/yum.repos.d/StarlingX-EPEL-7.repo). Could you help double check it? [slin14 at eb7345575ec1 cgcs-root]$ sudo -E yumdownloader -C --url --source lighttpd-1.4.50-1.el7 https://dl.fedoraproject.org/pub/epel/7/SRPMS/Packages/l/lighttpd-1.4.50-1.el7.src.rpm Best Regards Shuicheng -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Friday, November 2, 2018 8:53 AM To: Xie, Cindy ; Cordoba Malibran, Erich ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report Hi Erich, There is an error introduced by 1.4.50 that I fixed during 7.5 upgrade. It can block applying manifest step during deployment. Please refer to my patch for 7.5 upgrade and feel free to contact me if you have any question. https://review.openstack.org/#/c/596263/ Thx! -Zhipeng -----Original Message----- From: Xie, Cindy Sent: 2018年11月1日 21:53 To: Cordoba Malibran, Erich ; starlingx-discuss at lists.starlingx.io; Liu, ZhipengS Subject: RE: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report + Zhipeng We still have patches on lighttpd and it was rebased to 1.4.50 recently by Zhipeng. If the srpm upgraded to 1.4.51, Zhipeng can you please work w/ Erich and see if those patches need rework? Thx. - cindy -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Thursday, November 1, 2018 6:12 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report Lighttpd was upgraded in upstream: Package lighttpd-1.4.50-1.el7.src not found, available lighttpd-1.4.51-1.el7.src We'll send a patch for master today. Should we backport this to r/2018.10 branch? -Erich On 11/1/18, 3:37 AM, "aragorn at intel.com" wrote: [mirror-downloader][#119] Missing packages. Results report: - Missing: logs/L1_srpms_missing_centos.log lighttpd-1.4.50-1.el7.src.rpm - Missing GPG key: ./output/stx-r1/CentOS/pike/Source/libvirt-python-4.7.0-1.fc28.src.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#596bea5d) _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From chenjie.xu at intel.com Fri Nov 2 06:18:43 2018 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Fri, 2 Nov 2018 06:18:43 +0000 Subject: [Starlingx-discuss] Performance issuses for RFE_Enable_other_subprojects_to_extend_l2pop_fdb_information for StarlingX Upstreaming Message-ID: Hi Matt, For RFE_Enable_other_subprojects_to_extend_l2pop_fdb_information, Miguel asked "How much of a performance issue are the ARPs in your use case? Have you quantified it? Does it justify this proposal?". You can find his question in the link below: https://bugs.launchpad.net/neutron/+bug/1793653 For this question, could you tell me whether you have done the performance test? Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From Rajesh.Jha at rsystems.com Fri Nov 2 09:19:42 2018 From: Rajesh.Jha at rsystems.com (Rajesh Jha) Date: Fri, 2 Nov 2018 14:49:42 +0530 Subject: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 Message-ID: <2F61A2101B4FD447A683EF7E362CF9421C63E2181F@RSI-NOD-EXMDB6.india.rsystems.com> Hi, We were trying to pick up patches for some issues which we had reported like SSH not working and failing to attach data interface from controller to compute nodes. We failed to make the build. at step 2 of section Download Packages¶ from https://docs.starlingx.io/developer_guide/index.html#build-the-centos-mirror-repository document. when we run download_mirror.sh from the container There is one package which fails to download lighttpd-1.4.50-1.el7.src.rpm which is there in rpms_centos.lst. Since this version is not there on any mirror on internet, the version available is lighttpd-1.4.51-1.el7.src.rpm so we updated the file rpms_centos.lst and rpms_centos3rdparties.lst with lighttpd-1.4.51-1.el7.x86_64.rpm instead. Ran the download_mirror.sh again. Now everything is fine except it is failing in build-pkgs step with the following error. b6: ERROR: build_dir (415): Invalid srpm path 'mirror:Source/lighttpd-1.4.50-1.el7.src.rpm', evaluated as '/localdisk/designer/builder/starlingx/cgcs-root/cgcs-centos-repo/Source/lighttpd-1.4.50-1.el7.src.rpm', found in '/localdisk/designer/builder/starlingx/cgcs-root/stx/stx-integ/base/lighttpd/centos/srpm_path' now we are stuck and unable to build. Any suggestions would be welcome. on a general note, had a quick query how much time the incremental build is taking in general. Because we follow the steps for incremental build after step git clone https://git.starlingx.io/stx-tools and then we build the container image and all steps after that which is also taking 3 to 4 hours. Am I doing the incremental build properly?? Best Regards, Rajesh Jha The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, please immediately alert the sender by reply e-mail and then delete this message. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. R Systems has taken every reasonable precaution to minimize the risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. From liang.a.fang at intel.com Fri Nov 2 09:34:08 2018 From: liang.a.fang at intel.com (Fang, Liang A) Date: Fri, 2 Nov 2018 09:34:08 +0000 Subject: [Starlingx-discuss] glance api service is not started in all-in-one deployment Message-ID: Hi I deployed an starlingx all-in-one environment, and it seems glance api service has not been started. I also checked other services such as cinder api / cinder volume, there are started. /bin/sh /usr/lib/ocf/resource.d/openstack/cinder-schedule start /bin/sh /usr/lib/ocf/resource.d/openstack/cinder-volume start /bin/sh /usr/lib/ocf/resource.d/openstack/cinder-backup start But these are not started by service file such as openstack-cinder-api.service / openstack-cinder-scheduler.service. This is really different with the deployment by devstack. Could anybody point out how the services are started? How to restart cinder/glance service in starlingx deployment? Thanks. Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From Stefan.Dinescu at windriver.com Fri Nov 2 10:11:14 2018 From: Stefan.Dinescu at windriver.com (Dinescu, Stefan) Date: Fri, 2 Nov 2018 10:11:14 +0000 Subject: [Starlingx-discuss] glance api service is not started in all-in-one deployment In-Reply-To: References: Message-ID: Hi, On StarlingX, glance-api is managed by SM (short for service management). You can see a list of all the services by using "sm-dump" (from a root prompt or use sudo). If it is working, the sate should be "enabled-active". To restart the service us "sm-restart service glance-api". Also check the logs (/var/log/glance/glance-api.log) for any obvious errors that prevent the service from restarting. ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Friday, November 02, 2018 11:34 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] glance api service is not started in all-in-one deployment Hi I deployed an starlingx all-in-one environment, and it seems glance api service has not been started. I also checked other services such as cinder api / cinder volume, there are started. /bin/sh /usr/lib/ocf/resource.d/openstack/cinder-schedule start /bin/sh /usr/lib/ocf/resource.d/openstack/cinder-volume start /bin/sh /usr/lib/ocf/resource.d/openstack/cinder-backup start But these are not started by service file such as openstack-cinder-api.service / openstack-cinder-scheduler.service. This is really different with the deployment by devstack. Could anybody point out how the services are started? How to restart cinder/glance service in starlingx deployment? Thanks. Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From sajuptpm at gmail.com Fri Nov 2 10:12:18 2018 From: sajuptpm at gmail.com (Saju M) Date: Fri, 2 Nov 2018 15:42:18 +0530 Subject: [Starlingx-discuss] Starlingx stable ISO Message-ID: Hi, How to get stable Starlinx ISO image instead of build from scratch. I have seen the doc which explains how to build ISO image. https://docs.starlingx.io/developer_guide/index.html#developer-guide It would be helpful if we can upload stable ISO file somewhere publicly. Regards Saju Madhavan +91 09535134654 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Fri Nov 2 11:18:13 2018 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Fri, 2 Nov 2018 11:18:13 +0000 Subject: [Starlingx-discuss] Starlingx stable ISO In-Reply-To: <3a32af01c5lgg7cr@shdsegapp1> References: <3a32af01c5lgg7cr@shdsegapp1> Message-ID: +1 volker Von: Saju M [mailto:sajuptpm at gmail.com] Gesendet: Freitag, 2. November 2018 11:12 An: starlingx-discuss at lists.starlingx.io Betreff: [Starlingx-discuss] Starlingx stable ISO Hi, How to get stable Starlinx ISO image instead of build from scratch. I have seen the doc which explains how to build ISO image. https://docs.starlingx.io/developer_guide/index.html#developer-guide It would be helpful if we can upload stable ISO file somewhere publicly. Regards Saju Madhavan +91 09535134654 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cesarlarag at gmail.com Fri Nov 2 12:18:45 2018 From: cesarlarag at gmail.com (Cesar Lara) Date: Fri, 2 Nov 2018 06:18:45 -0600 Subject: [Starlingx-discuss] Starlingx stable ISO In-Reply-To: References: <3a32af01c5lgg7cr@shdsegapp1> Message-ID: We are working on a solution to host Iso files with one of our community partners, we will announce that in a few days, in the meantime, we are posting updates on this as part of the build team on the mailing list, the project wiki and meeting minutes. Cheers Cesar Lara On Fri, Nov 2, 2018, 5:18 AM von Hoesslin, Volker +1 > > > > volker > > > > *Von:* Saju M [mailto:sajuptpm at gmail.com] > *Gesendet:* Freitag, 2. November 2018 11:12 > *An:* starlingx-discuss at lists.starlingx.io > *Betreff:* [Starlingx-discuss] Starlingx stable ISO > > > > Hi, > > > > How to get stable Starlinx ISO image instead of build from scratch. > > I have seen the doc which explains how to build ISO image. > > https://docs.starlingx.io/developer_guide/index.html#developer-guide > > It would be helpful if we can upload stable ISO file somewhere publicly. > > > > Regards > Saju Madhavan > +91 09535134654 > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pongsawat at sysware.asia Fri Nov 2 13:04:23 2018 From: pongsawat at sysware.asia (Pongsawat Payungwong) Date: Fri, 2 Nov 2018 20:04:23 +0700 Subject: [Starlingx-discuss] Missing "Lighttpd-1.4.50-1.el7.src.rpm" Package Re: Starlingx-discuss Digest, Vol 6, Issue 3 In-Reply-To: References: Message-ID: Hi Team, I would like to get some advice for mirror:Source/lighttpd-1.4.50-1.el7.src.rpm , We are from Thailand, Bangkok, trying to build starlingx ISO image on Supermicro Server, [4SSDx1TB, 256Gb Ram, 4x10GE], follow everything on document step but missing "lighttpd-1.4.50-1.el7.src.rpm', , It download from mirror centos repo from ASIA region... I saw similar "lighttpd" issue in this email thread as well but not sure same with my issue or not. We can't "$build pkgs " error as below.. ----Excerpt---- 16:52:40 b0: ===== Build SRPM for 'python-cephclient' ===== 16:52:40 b0: PKG_BASE=/localdisk/designer/swthadmin/starlingx/cgcs-root/stx/stx-integ/ceph/python-cephclient 16:52:40 b0: WORK_BASE=/localdisk/loadbuild/swthadmin/starlingx/std/inputs/stx/stx-integ/ceph/python-cephclient 16:52:40 b0: RPMBUILD_BASE=/localdisk/loadbuild/swthadmin/starlingx/std/inputs/stx/stx-integ/ceph/python-cephclient/rpmbuild 16:52:40 b0: Wrote: /localdisk/loadbuild/swthadmin/starlingx/std/rpmbuild/SOURCES/python-cephclient/srpm_input.md5 16:52:40 b0: SRPM build not required for '/localdisk/designer/swthadmin/starlingx/cgcs-root/stx/stx-integ/ceph/python-cephclient' 16:52:40 b0: ===== Build complete for 'python-cephclient' ===== 16:52:40 b0: *16:52:40 ============ Build failed =============* *16:52:40 b0: ERROR: build_dir (415): Invalid srpm path 'mirror:Source/lighttpd-1.4.50-1.el7.src.rpm', evaluated as '/localdisk/designer/swthadmin/starlingx/cgcs-root/cgcs-centos-repo/Source/lighttpd-1.4.50-1.el7.src.rpm', found in '/localdisk/designer/swthadmin/starlingx/cgcs-root/stx/stx-integ/base/lighttpd/centos/srpm_path'* *16:52:40 ERROR: reaper (1302): Failed to build src.rpm from source at 'b0'* *16:52:40 * ######## Thu Nov 1 16:52:40 UTC 2018: build-srpm-parallel --std failed with rc=1 Thu Nov 1 16:52:40 UTC 2018: build-srpm-parallel --std failed with rc=1 ----------end------------------- Any advice are welcome. -- Warmest Regards, Pongsawat P Sysware Technology (Thailand) On Fri, Nov 2, 2018 at 5:38 AM wrote: > Send Starlingx-discuss mailing list submissions to > starlingx-discuss at lists.starlingx.io > > To subscribe or unsubscribe via the World Wide Web, visit > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > or, via email, send a message with subject or body 'help' to > starlingx-discuss-request at lists.starlingx.io > > You can reach the person managing the list at > starlingx-discuss-owner at lists.starlingx.io > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Starlingx-discuss digest..." > > > Today's Topics: > > 1. Re: Automated Notification for: [mirror-downloader][#119] > Missing packages - Results report (Cordoba Malibran, Erich) > 2. Re: Automated Notification for: [mirror-downloader][#119] > Missing packages - Results report (Xie, Cindy) > 3. Re: Automated Notification for: [mirror-downloader][#119] > Missing packages - Results report (Rowsell, Brent) > 4. Re: Compute boot-loop (von Hoesslin, Volker) > 5. Re: Compute boot-loop (Michel Thebeau) > 6. Re: Propose OpenStack/Apmec to StarlingX like an upstream > component (Dean Troyer) > 7. Re: Compute boot-loop (Alonso, Juan Carlos) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 1 Nov 2018 13:11:37 +0000 > From: "Cordoba Malibran, Erich" > To: "starlingx-discuss at lists.starlingx.io" > > Subject: Re: [Starlingx-discuss] Automated Notification for: > [mirror-downloader][#119] Missing packages - Results report > Message-ID: <4EA80D98-75AF-4DB1-A6B4-9ED5FAC99FC6 at intel.com> > Content-Type: text/plain; charset="utf-8" > > Lighttpd was upgraded in upstream: > > Package lighttpd-1.4.50-1.el7.src not found, available > lighttpd-1.4.51-1.el7.src > > We'll send a patch for master today. Should we backport this to r/2018.10 > branch? > > -Erich > > On 11/1/18, 3:37 AM, "aragorn at intel.com" wrote: > > [mirror-downloader][#119] Missing packages. Results report: > - Missing: logs/L1_srpms_missing_centos.log > lighttpd-1.4.50-1.el7.src.rpm - Missing GPG key: > > ./output/stx-r1/CentOS/pike/Source/libvirt-python-4.7.0-1.fc28.src.rpm: RSA > sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#596bea5d) > > > ------------------------------ > > Message: 2 > Date: Thu, 1 Nov 2018 13:53:00 +0000 > From: "Xie, Cindy" > To: "Cordoba Malibran, Erich" , > "starlingx-discuss at lists.starlingx.io" > , "Liu, ZhipengS" > > Subject: Re: [Starlingx-discuss] Automated Notification for: > [mirror-downloader][#119] Missing packages - Results report > Message-ID: > < > 2FD5DDB5A04D264C80D42CA35194914F35DB1360 at SHSMSX104.ccr.corp.intel.com> > > Content-Type: text/plain; charset="utf-8" > > + Zhipeng > We still have patches on lighttpd and it was rebased to 1.4.50 recently by > Zhipeng. If the srpm upgraded to 1.4.51, Zhipeng can you please work w/ > Erich and see if those patches need rework? > > Thx. - cindy > > -----Original Message----- > From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] > Sent: Thursday, November 1, 2018 6:12 AM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Automated Notification for: > [mirror-downloader][#119] Missing packages - Results report > > Lighttpd was upgraded in upstream: > > Package lighttpd-1.4.50-1.el7.src not found, available > lighttpd-1.4.51-1.el7.src > > We'll send a patch for master today. Should we backport this to r/2018.10 > branch? > > -Erich > > On 11/1/18, 3:37 AM, "aragorn at intel.com" wrote: > > [mirror-downloader][#119] Missing packages. Results report: > - Missing: logs/L1_srpms_missing_centos.log > lighttpd-1.4.50-1.el7.src.rpm - Missing GPG key: > > ./output/stx-r1/CentOS/pike/Source/libvirt-python-4.7.0-1.fc28.src.rpm: RSA > sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#596bea5d) > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > ------------------------------ > > Message: 3 > Date: Thu, 1 Nov 2018 13:55:36 +0000 > From: "Rowsell, Brent" > To: "Xie, Cindy" , "Cordoba Malibran, Erich" > , > "starlingx-discuss at lists.starlingx.io" > , "Liu, ZhipengS" > > Subject: Re: [Starlingx-discuss] Automated Notification for: > [mirror-downloader][#119] Missing packages - Results report > Message-ID: > <2588653EBDFFA34B982FAF00F1B4844EBB2F0821 at ALA-MBD.corp.ad.wrs.com> > Content-Type: text/plain; charset="utf-8" > > This needs to be functionally tested before it is pushed. > > Brent > > -----Original Message----- > From: Xie, Cindy [mailto:cindy.xie at intel.com] > Sent: Thursday, November 1, 2018 9:53 AM > To: Cordoba Malibran, Erich ; > starlingx-discuss at lists.starlingx.io; Liu, ZhipengS < > zhipengs.liu at intel.com> > Subject: Re: [Starlingx-discuss] Automated Notification for: > [mirror-downloader][#119] Missing packages - Results report > > + Zhipeng > We still have patches on lighttpd and it was rebased to 1.4.50 recently by > Zhipeng. If the srpm upgraded to 1.4.51, Zhipeng can you please work w/ > Erich and see if those patches need rework? > > Thx. - cindy > > -----Original Message----- > From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] > Sent: Thursday, November 1, 2018 6:12 AM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Automated Notification for: > [mirror-downloader][#119] Missing packages - Results report > > Lighttpd was upgraded in upstream: > > Package lighttpd-1.4.50-1.el7.src not found, available > lighttpd-1.4.51-1.el7.src > > We'll send a patch for master today. Should we backport this to r/2018.10 > branch? > > -Erich > > On 11/1/18, 3:37 AM, "aragorn at intel.com" wrote: > > [mirror-downloader][#119] Missing packages. Results report: > - Missing: logs/L1_srpms_missing_centos.log > lighttpd-1.4.50-1.el7.src.rpm - Missing GPG key: > > ./output/stx-r1/CentOS/pike/Source/libvirt-python-4.7.0-1.fc28.src.rpm: RSA > sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#596bea5d) > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > ------------------------------ > > Message: 4 > Date: Thu, 1 Nov 2018 16:12:26 +0000 > From: "von Hoesslin, Volker" > To: "'starlingx-discuss at lists.starlingx.io'" > > Subject: Re: [Starlingx-discuss] Compute boot-loop > Message-ID: > Content-Type: text/plain; charset="utf-8" > > Maybe it helps: https://ibb.co/n2OgoL > > ---------------------------------------------------------------- > Hello, there, > i have now built a complete stack and believe i did everything right. > after unlocking the compute nodes (two pieces), the nodes come into an > endless boot loop. > Error messages are not really noticeable, except: > compute-X 'ceilometer-polling' process has failed. Auto recovery in > progress > > any suggestions? Greez & thx, volker... > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20181101/23258d92/attachment-0001.html > > > > ------------------------------ > > Message: 5 > Date: Thu, 1 Nov 2018 12:28:53 -0400 > From: Michel Thebeau > To: "von Hoesslin, Volker" , > "'starlingx-discuss at lists.starlingx.io'" > > Subject: Re: [Starlingx-discuss] Compute boot-loop > Message-ID: <1e1ebab5-998b-3c27-fc68-4360e148315f at windriver.com> > Content-Type: text/plain; charset="windows-1252"; format=flowed > > Hi Volker, > > Could you describe the instructions you were using to setup startlingx > (were you following a wiki online)? Did you recheck the instructions > versus what is actually configured on the computes? > > How many cpus do your computes have? > > Which build are you using? Did you build your own? > > When reboot-loop happens on a node often the error will be presented on > the console during boot or could be inferred from console, sometimes > referring to puppet logs of the node /var/log/puppet/ > > M > > > On 2018-11-01 6:45 a.m., von Hoesslin, Volker wrote: > > Hello, there, > > i have now built a complete stack and believe i did everything right. > after unlocking the compute nodes (two pieces), the nodes come into an > endless boot loop. > > Error messages are not really noticeable, except: > > compute-X 'ceilometer-polling' process has failed. Auto recovery in > progress > > > > any suggestions? Greez & thx, volker... > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > ------------------------------ > > Message: 6 > Date: Thu, 1 Nov 2018 12:16:18 -0500 > From: Dean Troyer > To: doantungbk.203 at gmail.com > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Propose OpenStack/Apmec to StarlingX > like an upstream component > Message-ID: > < > CAOJFoEuSxPNOQto5oVmmFVP+zDtcKq0+oUXDP36W+hG6A1RjNA at mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > On Thu, Nov 1, 2018 at 7:44 AM Tung Doan wrote: > > I am Tung Doan - An OpenStack contributor and the PTL of OpenStack/Apmec > project. Since we acknowledged the potential integration between Apmec and > StarlingX, I am writing this email to propose adding OpenStack/Apmec to > StarlingX like an upstream project. > > > > Project description: OpenStack Apmec [1] stands for the Automated > Provisioning Framework for Multi-access Edge Computing which is the first > orchestration and management framework dedicated to the MEC services in > OpenStack. Below are some of the outstanding features of Apmec project: > > I believe Apmec is not an official OpenStack project (as listed in > [0]), do you have plans to apply to become an official OpenStack > project under TC governance? (Until then you do need to be careful > about referring to Apmec as 'an OpenStack project', it is hosted by > OpenStack, but is not (yet?) an OpenStack project.) > > > - no need to take care of the NFV functionalities. Since existing NFV > MANO frameworks (Tacker, ONAP, OSM, OpenBaton,...) are diverse, integrating > them can make StarlingX complicated. Apmec was designed to take over > responsibility for integrating them since the delivery of MEC services is > our critical mission. > > Is this replacing existing StarlingX functionality? > > > - no need to take care of the life-cycle management of the MEC > applications. Apmec offers API to help StarlingX perform this function. As > mentioned earlier, Apmec is OpenStack project, therefore, to provide > low-latency for MEC applications, Apmec is also planned to support > acceleration technologies (e.g, integrated with OpenStack Cyborg) such as > DPDK and FPGA. > > Can you get more specific about what the integration with StarlingX looks > like? > > dt > > [0] https://governance.openstack.org/tc/reference/projects/index.html > > -- > > Dean Troyer > dtroyer at gmail.com > > > > ------------------------------ > > Message: 7 > Date: Thu, 1 Nov 2018 22:38:40 +0000 > From: "Alonso, Juan Carlos" > To: Michel Thebeau , "von Hoesslin, > Volker" , > "'starlingx-discuss at lists.starlingx.io'" > > Subject: Re: [Starlingx-discuss] Compute boot-loop > Message-ID: > < > 8557B550001AFB46A43A0CCC314BF85153C592E1 at FMSMSX108.amr.corp.intel.com> > > Content-Type: text/plain; charset="utf-8" > > Hi, > > I think you set up a Duplex system (two controllers), right? > > I set up a Duplex system with two ISOs: stx-2018-10-30-171-master.iso and > stx-2018-11-01-8-master.iso > I faced the same issue you mention with first ISO, but did not with > today's ISO: stx-2018-11-01-8-master.iso. > > Please set up again a Duplex system with today's ISO to see if issue is > still presented. > > Regards. > Juan Carlos Alonso > > -----Original Message----- > From: Michel Thebeau [mailto:michel.thebeau at windriver.com] > Sent: Thursday, November 1, 2018 10:29 AM > To: von Hoesslin, Volker ; ' > starlingx-discuss at lists.starlingx.io' < > starlingx-discuss at lists.starlingx.io> > Subject: Re: [Starlingx-discuss] Compute boot-loop > > Hi Volker, > > Could you describe the instructions you were using to setup startlingx > (were you following a wiki online)? Did you recheck the instructions > versus what is actually configured on the computes? > > How many cpus do your computes have? > > Which build are you using? Did you build your own? > > When reboot-loop happens on a node often the error will be presented on > the console during boot or could be inferred from console, sometimes > referring to puppet logs of the node /var/log/puppet/ > > M > > > On 2018-11-01 6:45 a.m., von Hoesslin, Volker wrote: > > Hello, there, > > i have now built a complete stack and believe i did everything right. > after unlocking the compute nodes (two pieces), the nodes come into an > endless boot loop. > > Error messages are not really noticeable, except: > > compute-X 'ceilometer-polling' process has failed. Auto recovery in > progress > > > > any suggestions? Greez & thx, volker... > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > ------------------------------ > > End of Starlingx-discuss Digest, Vol 6, Issue 3 > *********************************************** > -- This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free or virus-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Sysware (Thailand) Co., Ltd., Bangkok, Thailand. www.sysware.asia -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Fri Nov 2 14:15:05 2018 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Fri, 2 Nov 2018 14:15:05 +0000 Subject: [Starlingx-discuss] Instance HA (IHA) Message-ID: Hello, has starlingX IHA support? I didnt find it? In generally I didn't find HA load-balancer features? What about Octavia https://wiki.openstack.org/wiki/Octavia ? Greez & thx, Volker... -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Fri Nov 2 14:29:03 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 2 Nov 2018 14:29:03 +0000 Subject: [Starlingx-discuss] [Process] Code Review Process Updated on wiki Message-ID: <151EE31B9FCCA54397A757BC674650F0BA47FB80@ALA-MBD.corp.ad.wrs.com> More details have been added to the Starling Code Submission Guidelines on the wiki based on input from the current core reviewers: https://wiki.openstack.org/wiki/StarlingX/CodeSubmissionGuidelines The wiki now covers code review etiquette in more detail, testing, early review/feedback. All code contributors should review and follow the guidelines. Happy coding! Regards, Ghada -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Fri Nov 2 17:36:47 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Fri, 2 Nov 2018 18:36:47 +0100 Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED Message-ID: <3868FDB4-49FA-4429-8657-7C4FBD0D93C1@gmail.com> Hi Technical Leads, I started to work on creating the core reviewer groups in Gerrit for each of the sub-projects in StarlingX and I need your input to complete this task. I have an initial list below containing the sub-project repos and the names of the core reviewers belonging to the groups. Please check your sub-project and respond with corrections or with an ‘OK’ in case the core team for your project is listed correctly. Please let me know if you have any questions. Thanks and Best Regards, Ildikó stx-clients - client libraries Jerry Sun (Jerry.Sun at windriver.com) Greg Waines (Greg.Waines at windriver.com) stx-config - Configuration Management Bart Wensley (Barton.Wensley at windriver.com) John Kung (John.Kung at windriver.com) Don Penney (Don.Penney at windriver.com) Bob Church (Robert.Church at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) stx-fault - Fault Management Tao Liu (Tao.Liu at windriver.com) Al Bailey (Al.Bailey at windriver.com) stx-integ - Integration and packaging Scott Little (scott.little at windriver.com) Bob Church (Robert.Church at windriver.com) Don Penney (Don.Penney at windriver.com ) stx-gui - Horizon plugins for new services Tyler Smith (Tyler.Smith at windriver.com) Angie Wang (Angie.Wang at windriver.com) Kristine Bujold (Kristine.Bujold at windriver.com) stx-ha - High Availability/Service Management Bin Qian (Bin.Qian at windriver.com) Eric Macdonald (Eric.MacDonald at windriver.com) John Kung (John.Kung at windriver.com) stx-metal - Bare Metal Management Eric Macdonald (Eric.MacDonald at windriver.com) John Kung (John.Kung at windriver.com) Tao Liu (Tao.Liu at windriver.com) stx-nfv - NFVI Orchestration Bart Wensley (Barton.Wensley at windriver.com) Al Bailey (Al.Bailey at windriver.com) Jack Ding (Jack.Ding at windriver.com) stx-update - Installation/Update/Patching Bart Wensley (Barton.Wensley at windriver.com) Don Penney (Don.Penney at windriver.com) David Sullivan (David.Sullivan at windriver.com) stx-upstream - Upstream packages Bob Church (Robert.Church at windriver.com) Al Bailey (Al.Bailey at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) stx-distcloud – Distributed Cloud Bart Wensley (Barton.Wensley at windriver.com) Brent Rowsell brent.rowsell at windriver.com Chris Friesen (Chris.Friesen at windriver.com) Dean Troyer dtroyer at gmail.com John Kung john.kung at windriver.com Saul Wold sgw at linux.intel.com stx-distcloud-client – Distributed Cloud Bart Wensley (Barton.Wensley at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) John Kung (John.Kung at windriver.com ) stx-manifest - source manifest to manage the repositories Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) stx-root - build source tree root Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) stx-tis-repo - build support Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) stx-tools - build tools Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) From erich.cordoba.malibran at intel.com Fri Nov 2 18:16:00 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Fri, 2 Nov 2018 18:16:00 +0000 Subject: [Starlingx-discuss] Missing "Lighttpd-1.4.50-1.el7.src.rpm" Package Re: Starlingx-discuss Digest, Vol 6, Issue 3 In-Reply-To: References: Message-ID: <550068C2-0613-41D1-955E-4FC12668E612@intel.com> Hi, Since yesterday it seems that the lighttpd version was upgraded in the upstream server. This means that your mirror is incomplete and that is why you are seeing that failure. From other thread in the mailing: I could find the src rpm with below repo (./centos-mirror-tools/yum.repos.d/StarlingX-EPEL-7.repo). Could you help double check it? [slin14 at eb7345575ec1 cgcs-root]$ sudo -E yumdownloader -C --url --source lighttpd-1.4.50-1.el7 https://dl.fedoraproject.org/pub/epel/7/SRPMS/Packages/l/lighttpd-1.4.50-1.el7.src.rpm So, you can try the following: - Download the missing file manually - Update the cgcs-centos-repo symlinks. Just run generate-cgcs-centos-repo.sh - Try to build again. We hope to fix this issue in the next days. -Erich From: Pongsawat Payungwong Date: Friday, November 2, 2018 at 7:05 AM To: "starlingx-discuss at lists.starlingx.io" Cc: "Einarsson, Jim" Subject: [Starlingx-discuss] Missing "Lighttpd-1.4.50-1.el7.src.rpm" Package Re: Starlingx-discuss Digest, Vol 6, Issue 3 Hi Team,  I would like to get some advice for mirror:Source/lighttpd-1.4.50-1.el7.src.rpm   ,  We are from Thailand, Bangkok, trying to build starlingx ISO image on Supermicro Server, [4SSDx1TB, 256Gb Ram, 4x10GE], follow everything on document step but missing  "lighttpd-1.4.50-1.el7.src.rpm', ,  It download from mirror centos repo from ASIA region... I saw similar "lighttpd" issue in this email thread as well but not sure same with my issue or not. We can't   "$build pkgs "   error as below.. ----Excerpt---- 16:52:40 b0: ===== Build SRPM for 'python-cephclient' ===== 16:52:40 b0: PKG_BASE=/localdisk/designer/swthadmin/starlingx/cgcs-root/stx/stx-integ/ceph/python-cephclient 16:52:40 b0: WORK_BASE=/localdisk/loadbuild/swthadmin/starlingx/std/inputs/stx/stx-integ/ceph/python-cephclient 16:52:40 b0: RPMBUILD_BASE=/localdisk/loadbuild/swthadmin/starlingx/std/inputs/stx/stx-integ/ceph/python-cephclient/rpmbuild 16:52:40 b0: Wrote: /localdisk/loadbuild/swthadmin/starlingx/std/rpmbuild/SOURCES/python-cephclient/srpm_input.md5 16:52:40 b0: SRPM build not required for '/localdisk/designer/swthadmin/starlingx/cgcs-root/stx/stx-integ/ceph/python-cephclient' 16:52:40 b0: ===== Build complete for 'python-cephclient' ===== 16:52:40 b0:  16:52:40 ============ Build failed ============= 16:52:40 b0: ERROR: build_dir (415): Invalid srpm path 'mirror:Source/lighttpd-1.4.50-1.el7.src.rpm', evaluated as '/localdisk/designer/swthadmin/starlingx/cgcs-root/cgcs-centos-repo/Source/lighttpd-1.4.50-1.el7.src.rpm', found in '/localdisk/designer/swthadmin/starlingx/cgcs-root/stx/stx-integ/base/lighttpd/centos/srpm_path' 16:52:40 ERROR: reaper (1302): Failed to build src.rpm from source at 'b0' 16:52:40  ######## Thu Nov  1 16:52:40 UTC 2018: build-srpm-parallel --std failed with rc=1 Thu Nov  1 16:52:40 UTC 2018: build-srpm-parallel --std failed with rc=1 ----------end------------------- Any advice are welcome. -- Warmest Regards, Pongsawat P Sysware Technology (Thailand) On Fri, Nov 2, 2018 at 5:38 AM wrote: Send Starlingx-discuss mailing list submissions to         mailto:starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit         http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to         mailto:starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at         mailto:starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics:    1. Re: Automated Notification for: [mirror-downloader][#119]       Missing packages - Results report (Cordoba Malibran, Erich)    2. Re: Automated Notification for: [mirror-downloader][#119]       Missing packages - Results report (Xie, Cindy)    3. Re: Automated Notification for: [mirror-downloader][#119]       Missing packages - Results report (Rowsell, Brent)    4. Re: Compute boot-loop (von Hoesslin, Volker)    5. Re: Compute boot-loop (Michel Thebeau)    6. Re: Propose OpenStack/Apmec to StarlingX like an upstream       component (Dean Troyer)    7. Re: Compute boot-loop (Alonso, Juan Carlos) ---------------------------------------------------------------------- Message: 1 Date: Thu, 1 Nov 2018 13:11:37 +0000 From: "Cordoba Malibran, Erich" To: "mailto:starlingx-discuss at lists.starlingx.io"         Subject: Re: [Starlingx-discuss] Automated Notification for:         [mirror-downloader][#119] Missing packages - Results report Message-ID: Content-Type: text/plain; charset="utf-8" Lighttpd was upgraded in upstream: Package lighttpd-1.4.50-1.el7.src not found, available lighttpd-1.4.51-1.el7.src We'll send a patch for master today. Should we backport this to r/2018.10 branch? -Erich On 11/1/18, 3:37 AM, "mailto:aragorn at intel.com" wrote:     [mirror-downloader][#119] Missing packages. Results report:      - Missing: logs/L1_srpms_missing_centos.log     lighttpd-1.4.50-1.el7.src.rpm - Missing GPG key:     ./output/stx-r1/CentOS/pike/Source/libvirt-python-4.7.0-1.fc28.src.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#596bea5d) ------------------------------ Message: 2 Date: Thu, 1 Nov 2018 13:53:00 +0000 From: "Xie, Cindy" To: "Cordoba Malibran, Erich" ,         "mailto:starlingx-discuss at lists.starlingx.io"         , "Liu, ZhipengS"         Subject: Re: [Starlingx-discuss] Automated Notification for:         [mirror-downloader][#119] Missing packages - Results report Message-ID:         Content-Type: text/plain; charset="utf-8" + Zhipeng We still have patches on lighttpd and it was rebased to 1.4.50 recently by Zhipeng. If the srpm upgraded to 1.4.51, Zhipeng can you please work w/ Erich and see if those patches need rework? Thx. - cindy -----Original Message----- From: Cordoba Malibran, Erich [mailto:mailto:erich.cordoba.malibran at intel.com] Sent: Thursday, November 1, 2018 6:12 AM To: mailto:starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report Lighttpd was upgraded in upstream: Package lighttpd-1.4.50-1.el7.src not found, available lighttpd-1.4.51-1.el7.src We'll send a patch for master today. Should we backport this to r/2018.10 branch? -Erich On 11/1/18, 3:37 AM, "mailto:aragorn at intel.com" wrote:     [mirror-downloader][#119] Missing packages. Results report:      - Missing: logs/L1_srpms_missing_centos.log     lighttpd-1.4.50-1.el7.src.rpm - Missing GPG key:     ./output/stx-r1/CentOS/pike/Source/libvirt-python-4.7.0-1.fc28.src.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#596bea5d) _______________________________________________ Starlingx-discuss mailing list mailto:Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ Message: 3 Date: Thu, 1 Nov 2018 13:55:36 +0000 From: "Rowsell, Brent" To: "Xie, Cindy" , "Cordoba Malibran, Erich"         ,         "mailto:starlingx-discuss at lists.starlingx.io"         , "Liu, ZhipengS"         Subject: Re: [Starlingx-discuss] Automated Notification for:         [mirror-downloader][#119] Missing packages - Results report Message-ID:         Content-Type: text/plain; charset="utf-8" This needs to be functionally tested before it is pushed. Brent -----Original Message----- From: Xie, Cindy [mailto:mailto:cindy.xie at intel.com] Sent: Thursday, November 1, 2018 9:53 AM To: Cordoba Malibran, Erich ; mailto:starlingx-discuss at lists.starlingx.io; Liu, ZhipengS Subject: Re: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report + Zhipeng We still have patches on lighttpd and it was rebased to 1.4.50 recently by Zhipeng. If the srpm upgraded to 1.4.51, Zhipeng can you please work w/ Erich and see if those patches need rework? Thx. - cindy -----Original Message----- From: Cordoba Malibran, Erich [mailto:mailto:erich.cordoba.malibran at intel.com] Sent: Thursday, November 1, 2018 6:12 AM To: mailto:starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report Lighttpd was upgraded in upstream: Package lighttpd-1.4.50-1.el7.src not found, available lighttpd-1.4.51-1.el7.src We'll send a patch for master today. Should we backport this to r/2018.10 branch? -Erich On 11/1/18, 3:37 AM, "mailto:aragorn at intel.com" wrote:     [mirror-downloader][#119] Missing packages. Results report:      - Missing: logs/L1_srpms_missing_centos.log     lighttpd-1.4.50-1.el7.src.rpm - Missing GPG key:     ./output/stx-r1/CentOS/pike/Source/libvirt-python-4.7.0-1.fc28.src.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#596bea5d) _______________________________________________ Starlingx-discuss mailing list mailto:Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list mailto:Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ Message: 4 Date: Thu, 1 Nov 2018 16:12:26 +0000 From: "von Hoesslin, Volker" To: "'mailto:starlingx-discuss at lists.starlingx.io'"         Subject: Re: [Starlingx-discuss] Compute boot-loop Message-ID: Content-Type: text/plain; charset="utf-8" Maybe it helps: https://ibb.co/n2OgoL ---------------------------------------------------------------- Hello, there, i have now built a complete stack and believe i did everything right. after unlocking the compute nodes (two pieces), the nodes come into an endless boot loop. Error messages are not really noticeable, except: compute-X 'ceilometer-polling' process has failed. Auto recovery in progress any suggestions? Greez & thx, volker... -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 5 Date: Thu, 1 Nov 2018 12:28:53 -0400 From: Michel Thebeau To: "von Hoesslin, Volker" ,         "'mailto:starlingx-discuss at lists.starlingx.io'"         Subject: Re: [Starlingx-discuss] Compute boot-loop Message-ID: Content-Type: text/plain; charset="windows-1252"; format=flowed Hi Volker, Could you describe the instructions you were using to setup startlingx (were you following a wiki online)?  Did you recheck the instructions versus what is actually configured on the computes? How many cpus do your computes have? Which build are you using?  Did you build your own? When reboot-loop happens on a node often the error will be presented on the console during boot or could be inferred from console, sometimes referring to puppet logs of the node /var/log/puppet/ M On 2018-11-01 6:45 a.m., von Hoesslin, Volker wrote: > Hello, there, > i have now built a complete stack and believe i did everything right. after unlocking the compute nodes (two pieces), the nodes come into an endless boot loop. > Error messages are not really noticeable, except: > compute-X 'ceilometer-polling' process has failed. Auto recovery in progress > > any suggestions? Greez & thx, volker... > > > _______________________________________________ > Starlingx-discuss mailing list > mailto:Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ Message: 6 Date: Thu, 1 Nov 2018 12:16:18 -0500 From: Dean Troyer To: mailto:doantungbk.203 at gmail.com Cc: mailto:starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Propose OpenStack/Apmec to StarlingX         like an upstream component Message-ID:         Content-Type: text/plain; charset="UTF-8" On Thu, Nov 1, 2018 at 7:44 AM Tung Doan wrote: > I am Tung Doan - An OpenStack contributor and the PTL of OpenStack/Apmec project. Since we acknowledged the potential integration between Apmec and StarlingX, I am writing this email to propose adding OpenStack/Apmec to StarlingX like an upstream project. > > Project description: OpenStack Apmec [1] stands for the Automated Provisioning Framework for Multi-access Edge Computing which is the first orchestration and management framework dedicated to the MEC services in OpenStack. Below are some of the outstanding features of Apmec project: I believe Apmec is not an official OpenStack project (as listed in [0]), do you have plans to apply to become an official OpenStack project under TC governance?  (Until then you do need to be careful about referring to Apmec as 'an OpenStack project', it is hosted by OpenStack, but is not (yet?) an OpenStack project.) > - no need to take care of the NFV functionalities. Since existing NFV MANO frameworks (Tacker, ONAP, OSM, OpenBaton,...) are diverse, integrating them can make StarlingX complicated. Apmec was designed to take over responsibility for integrating them since the delivery of MEC services is our critical mission. Is this replacing existing StarlingX functionality? >  - no need to take care of the life-cycle management of the MEC applications. Apmec offers API to help StarlingX perform this function.  As mentioned earlier, Apmec is OpenStack project, therefore, to provide low-latency for MEC applications,  Apmec is also planned to support acceleration technologies (e.g, integrated with OpenStack Cyborg) such as DPDK and FPGA. Can you get more specific about what the integration with StarlingX looks like? dt [0] https://governance.openstack.org/tc/reference/projects/index.html -- Dean Troyer mailto:dtroyer at gmail.com ------------------------------ Message: 7 Date: Thu, 1 Nov 2018 22:38:40 +0000 From: "Alonso, Juan Carlos" To: Michel Thebeau , "von Hoesslin,         Volker" ,         "'mailto:starlingx-discuss at lists.starlingx.io'"         Subject: Re: [Starlingx-discuss] Compute boot-loop Message-ID:         Content-Type: text/plain; charset="utf-8" Hi, I think you set up a Duplex system (two controllers), right? I set up a Duplex system with two ISOs: stx-2018-10-30-171-master.iso and stx-2018-11-01-8-master.iso I faced the same issue you mention with first ISO, but did not with today's ISO: stx-2018-11-01-8-master.iso. Please set up again a Duplex system with today's ISO to see if issue is still presented. Regards. Juan Carlos Alonso -----Original Message----- From: Michel Thebeau [mailto:mailto:michel.thebeau at windriver.com] Sent: Thursday, November 1, 2018 10:29 AM To: von Hoesslin, Volker ; 'mailto:starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] Compute boot-loop Hi Volker, Could you describe the instructions you were using to setup startlingx (were you following a wiki online)?  Did you recheck the instructions versus what is actually configured on the computes? How many cpus do your computes have? Which build are you using?  Did you build your own? When reboot-loop happens on a node often the error will be presented on the console during boot or could be inferred from console, sometimes referring to puppet logs of the node /var/log/puppet/ M On 2018-11-01 6:45 a.m., von Hoesslin, Volker wrote: > Hello, there, > i have now built a complete stack and believe i did everything right. after unlocking the compute nodes (two pieces), the nodes come into an endless boot loop. > Error messages are not really noticeable, except: > compute-X 'ceilometer-polling' process has failed. Auto recovery in progress > > any suggestions? Greez & thx, volker... > > > _______________________________________________ > Starlingx-discuss mailing list > mailto:Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list mailto:Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list mailto:Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 6, Issue 3 *********************************************** This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free or virus-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Sysware (Thailand) Co., Ltd., Bangkok, Thailand. http://www.sysware.asia From tyler.smith at windriver.com Fri Nov 2 18:19:37 2018 From: tyler.smith at windriver.com (Smith, Tyler) Date: Fri, 2 Nov 2018 18:19:37 +0000 Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED In-Reply-To: <3868FDB4-49FA-4429-8657-7C4FBD0D93C1@gmail.com> References: <3868FDB4-49FA-4429-8657-7C4FBD0D93C1@gmail.com> Message-ID: OK for stx-gui Thanks, Tyler -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: Friday, November 2, 2018 1:37 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED Hi Technical Leads, I started to work on creating the core reviewer groups in Gerrit for each of the sub-projects in StarlingX and I need your input to complete this task. I have an initial list below containing the sub-project repos and the names of the core reviewers belonging to the groups. Please check your sub-project and respond with corrections or with an ‘OK’ in case the core team for your project is listed correctly. Please let me know if you have any questions. Thanks and Best Regards, Ildikó stx-clients - client libraries Jerry Sun (Jerry.Sun at windriver.com) Greg Waines (Greg.Waines at windriver.com) stx-config - Configuration Management Bart Wensley (Barton.Wensley at windriver.com) John Kung (John.Kung at windriver.com) Don Penney (Don.Penney at windriver.com) Bob Church (Robert.Church at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) stx-fault - Fault Management Tao Liu (Tao.Liu at windriver.com) Al Bailey (Al.Bailey at windriver.com) stx-integ - Integration and packaging Scott Little (scott.little at windriver.com) Bob Church (Robert.Church at windriver.com) Don Penney (Don.Penney at windriver.com ) stx-gui - Horizon plugins for new services Tyler Smith (Tyler.Smith at windriver.com) Angie Wang (Angie.Wang at windriver.com) Kristine Bujold (Kristine.Bujold at windriver.com) stx-ha - High Availability/Service Management Bin Qian (Bin.Qian at windriver.com) Eric Macdonald (Eric.MacDonald at windriver.com) John Kung (John.Kung at windriver.com) stx-metal - Bare Metal Management Eric Macdonald (Eric.MacDonald at windriver.com) John Kung (John.Kung at windriver.com) Tao Liu (Tao.Liu at windriver.com) stx-nfv - NFVI Orchestration Bart Wensley (Barton.Wensley at windriver.com) Al Bailey (Al.Bailey at windriver.com) Jack Ding (Jack.Ding at windriver.com) stx-update - Installation/Update/Patching Bart Wensley (Barton.Wensley at windriver.com) Don Penney (Don.Penney at windriver.com) David Sullivan (David.Sullivan at windriver.com) stx-upstream - Upstream packages Bob Church (Robert.Church at windriver.com) Al Bailey (Al.Bailey at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) stx-distcloud – Distributed Cloud Bart Wensley (Barton.Wensley at windriver.com) Brent Rowsell brent.rowsell at windriver.com Chris Friesen (Chris.Friesen at windriver.com) Dean Troyer dtroyer at gmail.com John Kung john.kung at windriver.com Saul Wold sgw at linux.intel.com stx-distcloud-client – Distributed Cloud Bart Wensley (Barton.Wensley at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) John Kung (John.Kung at windriver.com ) stx-manifest - source manifest to manage the repositories Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) stx-root - build source tree root Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) stx-tis-repo - build support Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) stx-tools - build tools Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From yong.hu at intel.com Fri Nov 2 02:10:26 2018 From: yong.hu at intel.com (Hu, Yong) Date: Fri, 2 Nov 2018 02:10:26 +0000 Subject: [Starlingx-discuss] Community meeting minutes Oct 31 2018 Message-ID: Regarding 2019 March release planning, one of customers asked: Will *container for user* be a target feature to deliver? Though, we have “Containerized OpenStack services” listed with 1st priority. Another question is about when we will publish such a release plan officially. I guess it will be in Berlin Summit, isn’t? From: "Jones, Bruce E" Date: Thursday, 1 November 2018 at 4:07 AM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Community meeting minutes Oct 31 2018 Agenda and Notes for the Oct 31st call · How to handle DST changes? Use UTC timeslots or keep Pacific time? · Remote client SDK module - remove it? Keep it? Do we keep the TiC SDK? If so, should we support it and document it? * Brent: We can remove the SDK. WR to handle. · Updated Code Submission Guidelines: https://wiki.openstack.org/wiki/StarlingX/CodeSubmissionGuidelines * Still seeing reviews that haven't been tested or compiled. Please review the updated guidelines and post with WF -1 and WIP if you're looking for early review comments · March release planning * Project priority call for submissions * Each sub-team should be thinking about what they want to do for the release § Can/should we schedule the teams to come into this meeting and present their plans? § Each team to update the Ethercalc with their high priority work items * https://ethercalc.openstack.org/fafyo2729fnr § Each team to come to the community call next week to briefly review § TSC to review globally at or before Berlin. * Release team to consider how/when/if to establish some additional milestones · Can we please have some reviewers look into this Ceph upgrade PR: * https://github.com/starlingx-staging/stx-ceph/pull/5 * There are no notifications for new PRs so please send email out to the mailing list when you post one · TSC members - now that we've grown the TSC we need more +1/+2 on specs to approve specs * "Clear the decks over the next few days to approve specs in flight" · Meeting time switch options * Keep meeting times as per UTC - 6AM meetings would move to 5AM * Move meeting times around to keep 5AM meetings off US calendars * Poll: https://doodle.com/poll/pw7mds8qms9d989y * Meetings: https://wiki.openstack.org/wiki/Starlingx/Meetings * Decision - move meeting times with US DST and keep the 6AM meetings at 6am -------------- next part -------------- An HTML attachment was scrubbed... URL: From pongsawat at sysware.asia Fri Nov 2 19:01:01 2018 From: pongsawat at sysware.asia (Pongsawat Payungwong) Date: Sat, 3 Nov 2018 02:01:01 +0700 Subject: [Starlingx-discuss] Missing "Lighttpd-1.4.50-1.el7.src.rpm" Package Re: Starlingx-discuss Digest, Vol 6, Issue 3 In-Reply-To: <550068C2-0613-41D1-955E-4FC12668E612@intel.com> References: <550068C2-0613-41D1-955E-4FC12668E612@intel.com> Message-ID: Hi Erich, Thanks for suggestion, please see my inline comments. I will try again in next few days. Have a nice day -- Warmest Regards, Pongsawat Payungwong Sysware Technology On Sat, Nov 3, 2018 at 1:16 AM Cordoba Malibran, Erich < erich.cordoba.malibran at intel.com> wrote: > Hi, > > Since yesterday it seems that the lighttpd version was upgraded in the > upstream server. This means that your > mirror is incomplete and that is why you are seeing that failure. > > From other thread in the mailing: > I could find the src rpm with below repo > (./centos-mirror-tools/yum.repos.d/StarlingX-EPEL-7.repo). > Could you help double check it? > [pspw] [image: image.png] [image: image.png] > [slin14 at eb7345575ec1 cgcs-root]$ sudo -E yumdownloader -C --url --source > lighttpd-1.4.50-1.el7 > > https://dl.fedoraproject.org/pub/epel/7/SRPMS/Packages/l/lighttpd-1.4.50-1.el7.src.rpm > > So, you can try the following: > > - Download the missing file manually > - Update the cgcs-centos-repo symlinks. Just run > generate-cgcs-centos-repo.sh > - Try to build again. > > We hope to fix this issue in the next days. > > -Erich > > From: Pongsawat Payungwong > Date: Friday, November 2, 2018 at 7:05 AM > To: "starlingx-discuss at lists.starlingx.io" < > starlingx-discuss at lists.starlingx.io> > Cc: "Einarsson, Jim" > Subject: [Starlingx-discuss] Missing "Lighttpd-1.4.50-1.el7.src.rpm" > Package Re: Starlingx-discuss Digest, Vol 6, Issue 3 > > Hi Team, > I would like to get some advice > for mirror:Source/lighttpd-1.4.50-1.el7.src.rpm , We are from Thailand, > Bangkok, trying to build starlingx ISO image on Supermicro Server, > [4SSDx1TB, 256Gb Ram, 4x10GE], follow everything on document step but > missing "lighttpd-1.4.50-1.el7.src.rpm', , It download from mirror centos > repo from ASIA region... > I saw similar "lighttpd" issue in this email thread as well but not sure > same with my issue or not. > > We can't "$build pkgs " error as below.. > ----Excerpt---- > 16:52:40 b0: ===== Build SRPM for 'python-cephclient' ===== > 16:52:40 b0: > PKG_BASE=/localdisk/designer/swthadmin/starlingx/cgcs-root/stx/stx-integ/ceph/python-cephclient > 16:52:40 b0: > WORK_BASE=/localdisk/loadbuild/swthadmin/starlingx/std/inputs/stx/stx-integ/ceph/python-cephclient > 16:52:40 b0: > RPMBUILD_BASE=/localdisk/loadbuild/swthadmin/starlingx/std/inputs/stx/stx-integ/ceph/python-cephclient/rpmbuild > 16:52:40 b0: Wrote: > /localdisk/loadbuild/swthadmin/starlingx/std/rpmbuild/SOURCES/python-cephclient/srpm_input.md5 > 16:52:40 b0: SRPM build not required for > '/localdisk/designer/swthadmin/starlingx/cgcs-root/stx/stx-integ/ceph/python-cephclient' > 16:52:40 b0: ===== Build complete for 'python-cephclient' ===== > 16:52:40 b0: > 16:52:40 ============ Build failed ============= > 16:52:40 b0: ERROR: build_dir (415): Invalid srpm path > 'mirror:Source/lighttpd-1.4.50-1.el7.src.rpm', evaluated as > '/localdisk/designer/swthadmin/starlingx/cgcs-root/cgcs-centos-repo/Source/lighttpd-1.4.50-1.el7.src.rpm', > found in > '/localdisk/designer/swthadmin/starlingx/cgcs-root/stx/stx-integ/base/lighttpd/centos/srpm_path' > 16:52:40 ERROR: reaper (1302): Failed to build src.rpm from source at 'b0' > 16:52:40 > > ######## Thu Nov 1 16:52:40 UTC 2018: build-srpm-parallel --std failed > with rc=1 > > Thu Nov 1 16:52:40 UTC 2018: build-srpm-parallel --std failed with rc=1 > > ----------end------------------- > > > Any advice are welcome. > > -- > Warmest Regards, > Pongsawat P > Sysware Technology (Thailand) > > On Fri, Nov 2, 2018 at 5:38 AM starlingx-discuss-request at lists.starlingx.io> wrote: > Send Starlingx-discuss mailing list submissions to > mailto:starlingx-discuss at lists.starlingx.io > > To subscribe or unsubscribe via the World Wide Web, visit > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > or, via email, send a message with subject or body 'help' to > mailto:starlingx-discuss-request at lists.starlingx.io > > You can reach the person managing the list at > mailto:starlingx-discuss-owner at lists.starlingx.io > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Starlingx-discuss digest..." > > > Today's Topics: > > 1. Re: Automated Notification for: [mirror-downloader][#119] > Missing packages - Results report (Cordoba Malibran, Erich) > 2. Re: Automated Notification for: [mirror-downloader][#119] > Missing packages - Results report (Xie, Cindy) > 3. Re: Automated Notification for: [mirror-downloader][#119] > Missing packages - Results report (Rowsell, Brent) > 4. Re: Compute boot-loop (von Hoesslin, Volker) > 5. Re: Compute boot-loop (Michel Thebeau) > 6. Re: Propose OpenStack/Apmec to StarlingX like an upstream > component (Dean Troyer) > 7. Re: Compute boot-loop (Alonso, Juan Carlos) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 1 Nov 2018 13:11:37 +0000 > From: "Cordoba Malibran, Erich" > To: "mailto:starlingx-discuss at lists.starlingx.io" > > Subject: Re: [Starlingx-discuss] Automated Notification for: > [mirror-downloader][#119] Missing packages - Results report > Message-ID: > Content-Type: text/plain; charset="utf-8" > > Lighttpd was upgraded in upstream: > > Package lighttpd-1.4.50-1.el7.src not found, available > lighttpd-1.4.51-1.el7.src > > We'll send a patch for master today. Should we backport this to r/2018.10 > branch? > > -Erich > > On 11/1/18, 3:37 AM, "mailto:aragorn at intel.com" > wrote: > > [mirror-downloader][#119] Missing packages. Results report: > - Missing: logs/L1_srpms_missing_centos.log > lighttpd-1.4.50-1.el7.src.rpm - Missing GPG key: > > ./output/stx-r1/CentOS/pike/Source/libvirt-python-4.7.0-1.fc28.src.rpm: RSA > sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#596bea5d) > > > ------------------------------ > > Message: 2 > Date: Thu, 1 Nov 2018 13:53:00 +0000 > From: "Xie, Cindy" > To: "Cordoba Malibran, Erich" , > "mailto:starlingx-discuss at lists.starlingx.io" > , "Liu, ZhipengS" > > Subject: Re: [Starlingx-discuss] Automated Notification for: > [mirror-downloader][#119] Missing packages - Results report > Message-ID: > 2FD5DDB5A04D264C80D42CA35194914F35DB1360 at SHSMSX104.ccr.corp.intel.com> > > Content-Type: text/plain; charset="utf-8" > > + Zhipeng > We still have patches on lighttpd and it was rebased to 1.4.50 recently by > Zhipeng. If the srpm upgraded to 1.4.51, Zhipeng can you please work w/ > Erich and see if those patches need rework? > > Thx. - cindy > > -----Original Message----- > From: Cordoba Malibran, Erich [mailto:mailto: > erich.cordoba.malibran at intel.com] > Sent: Thursday, November 1, 2018 6:12 AM > To: mailto:starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Automated Notification for: > [mirror-downloader][#119] Missing packages - Results report > > Lighttpd was upgraded in upstream: > > Package lighttpd-1.4.50-1.el7.src not found, available > lighttpd-1.4.51-1.el7.src > > We'll send a patch for master today. Should we backport this to r/2018.10 > branch? > > -Erich > > On 11/1/18, 3:37 AM, "mailto:aragorn at intel.com" > wrote: > > [mirror-downloader][#119] Missing packages. Results report: > - Missing: logs/L1_srpms_missing_centos.log > lighttpd-1.4.50-1.el7.src.rpm - Missing GPG key: > > ./output/stx-r1/CentOS/pike/Source/libvirt-python-4.7.0-1.fc28.src.rpm: RSA > sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#596bea5d) > > _______________________________________________ > Starlingx-discuss mailing list > mailto:Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > ------------------------------ > > Message: 3 > Date: Thu, 1 Nov 2018 13:55:36 +0000 > From: "Rowsell, Brent" > To: "Xie, Cindy" , "Cordoba Malibran, Erich" > , > "mailto:starlingx-discuss at lists.starlingx.io" > , "Liu, ZhipengS" > > Subject: Re: [Starlingx-discuss] Automated Notification for: > [mirror-downloader][#119] Missing packages - Results report > Message-ID: > 2588653EBDFFA34B982FAF00F1B4844EBB2F0821 at ALA-MBD.corp.ad.wrs.com> > Content-Type: text/plain; charset="utf-8" > > This needs to be functionally tested before it is pushed. > > Brent > > -----Original Message----- > From: Xie, Cindy [mailto:mailto:cindy.xie at intel.com] > Sent: Thursday, November 1, 2018 9:53 AM > To: Cordoba Malibran, Erich ; > mailto:starlingx-discuss at lists.starlingx.io; Liu, ZhipengS zhipengs.liu at intel.com> > Subject: Re: [Starlingx-discuss] Automated Notification for: > [mirror-downloader][#119] Missing packages - Results report > > + Zhipeng > We still have patches on lighttpd and it was rebased to 1.4.50 recently by > Zhipeng. If the srpm upgraded to 1.4.51, Zhipeng can you please work w/ > Erich and see if those patches need rework? > > Thx. - cindy > > -----Original Message----- > From: Cordoba Malibran, Erich [mailto:mailto: > erich.cordoba.malibran at intel.com] > Sent: Thursday, November 1, 2018 6:12 AM > To: mailto:starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Automated Notification for: > [mirror-downloader][#119] Missing packages - Results report > > Lighttpd was upgraded in upstream: > > Package lighttpd-1.4.50-1.el7.src not found, available > lighttpd-1.4.51-1.el7.src > > We'll send a patch for master today. Should we backport this to r/2018.10 > branch? > > -Erich > > On 11/1/18, 3:37 AM, "mailto:aragorn at intel.com" > wrote: > > [mirror-downloader][#119] Missing packages. Results report: > - Missing: logs/L1_srpms_missing_centos.log > lighttpd-1.4.50-1.el7.src.rpm - Missing GPG key: > > ./output/stx-r1/CentOS/pike/Source/libvirt-python-4.7.0-1.fc28.src.rpm: RSA > sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#596bea5d) > > _______________________________________________ > Starlingx-discuss mailing list > mailto:Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > mailto:Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > ------------------------------ > > Message: 4 > Date: Thu, 1 Nov 2018 16:12:26 +0000 > From: "von Hoesslin, Volker" > To: "'mailto:starlingx-discuss at lists.starlingx.io'" > > Subject: Re: [Starlingx-discuss] Compute boot-loop > Message-ID: DB39DAB5F762704A93D316F9CE7D021E4280986F at emilio.sis.net> > Content-Type: text/plain; charset="utf-8" > > Maybe it helps: https://ibb.co/n2OgoL > > ---------------------------------------------------------------- > Hello, there, > i have now built a complete stack and believe i did everything right. > after unlocking the compute nodes (two pieces), the nodes come into an > endless boot loop. > Error messages are not really noticeable, except: > compute-X 'ceilometer-polling' process has failed. Auto recovery in > progress > > any suggestions? Greez & thx, volker... > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20181101/23258d92/attachment-0001.html > > > > ------------------------------ > > Message: 5 > Date: Thu, 1 Nov 2018 12:28:53 -0400 > From: Michel Thebeau > To: "von Hoesslin, Volker" , > "'mailto:starlingx-discuss at lists.starlingx.io'" > > Subject: Re: [Starlingx-discuss] Compute boot-loop > Message-ID: > Content-Type: text/plain; charset="windows-1252"; format=flowed > > Hi Volker, > > Could you describe the instructions you were using to setup startlingx > (were you following a wiki online)? Did you recheck the instructions > versus what is actually configured on the computes? > > How many cpus do your computes have? > > Which build are you using? Did you build your own? > > When reboot-loop happens on a node often the error will be presented on > the console during boot or could be inferred from console, sometimes > referring to puppet logs of the node /var/log/puppet/ > > M > > > On 2018-11-01 6:45 a.m., von Hoesslin, Volker wrote: > > Hello, there, > > i have now built a complete stack and believe i did everything right. > after unlocking the compute nodes (two pieces), the nodes come into an > endless boot loop. > > Error messages are not really noticeable, except: > > compute-X 'ceilometer-polling' process has failed. Auto recovery in > progress > > > > any suggestions? Greez & thx, volker... > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > mailto:Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > ------------------------------ > > Message: 6 > Date: Thu, 1 Nov 2018 12:16:18 -0500 > From: Dean Troyer > To: mailto:doantungbk.203 at gmail.com > Cc: mailto:starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Propose OpenStack/Apmec to StarlingX > like an upstream component > Message-ID: > CAOJFoEuSxPNOQto5oVmmFVP+zDtcKq0+oUXDP36W+hG6A1RjNA at mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > On Thu, Nov 1, 2018 at 7:44 AM Tung Doan > wrote: > > I am Tung Doan - An OpenStack contributor and the PTL of OpenStack/Apmec > project. Since we acknowledged the potential integration between Apmec and > StarlingX, I am writing this email to propose adding OpenStack/Apmec to > StarlingX like an upstream project. > > > > Project description: OpenStack Apmec [1] stands for the Automated > Provisioning Framework for Multi-access Edge Computing which is the first > orchestration and management framework dedicated to the MEC services in > OpenStack. Below are some of the outstanding features of Apmec project: > > I believe Apmec is not an official OpenStack project (as listed in > [0]), do you have plans to apply to become an official OpenStack > project under TC governance? (Until then you do need to be careful > about referring to Apmec as 'an OpenStack project', it is hosted by > OpenStack, but is not (yet?) an OpenStack project.) > > > - no need to take care of the NFV functionalities. Since existing NFV > MANO frameworks (Tacker, ONAP, OSM, OpenBaton,...) are diverse, integrating > them can make StarlingX complicated. Apmec was designed to take over > responsibility for integrating them since the delivery of MEC services is > our critical mission. > > Is this replacing existing StarlingX functionality? > > > - no need to take care of the life-cycle management of the MEC > applications. Apmec offers API to help StarlingX perform this function. As > mentioned earlier, Apmec is OpenStack project, therefore, to provide > low-latency for MEC applications, Apmec is also planned to support > acceleration technologies (e.g, integrated with OpenStack Cyborg) such as > DPDK and FPGA. > > Can you get more specific about what the integration with StarlingX looks > like? > > dt > > [0] https://governance.openstack.org/tc/reference/projects/index.html > > -- > > Dean Troyer > mailto:dtroyer at gmail.com > > > > ------------------------------ > > Message: 7 > Date: Thu, 1 Nov 2018 22:38:40 +0000 > From: "Alonso, Juan Carlos" > To: Michel Thebeau , "von Hoesslin, > Volker" , > "'mailto:starlingx-discuss at lists.starlingx.io'" > > Subject: Re: [Starlingx-discuss] Compute boot-loop > Message-ID: > 8557B550001AFB46A43A0CCC314BF85153C592E1 at FMSMSX108.amr.corp.intel.com> > > Content-Type: text/plain; charset="utf-8" > > Hi, > > I think you set up a Duplex system (two controllers), right? > > I set up a Duplex system with two ISOs: stx-2018-10-30-171-master.iso and > stx-2018-11-01-8-master.iso > I faced the same issue you mention with first ISO, but did not with > today's ISO: stx-2018-11-01-8-master.iso. > > Please set up again a Duplex system with today's ISO to see if issue is > still presented. > > Regards. > Juan Carlos Alonso > > -----Original Message----- > From: Michel Thebeau [mailto:mailto:michel.thebeau at windriver.com] > Sent: Thursday, November 1, 2018 10:29 AM > To: von Hoesslin, Volker ; 'mailto: > starlingx-discuss at lists.starlingx.io' starlingx-discuss at lists.starlingx.io> > Subject: Re: [Starlingx-discuss] Compute boot-loop > > Hi Volker, > > Could you describe the instructions you were using to setup startlingx > (were you following a wiki online)? Did you recheck the instructions > versus what is actually configured on the computes? > > How many cpus do your computes have? > > Which build are you using? Did you build your own? > > When reboot-loop happens on a node often the error will be presented on > the console during boot or could be inferred from console, sometimes > referring to puppet logs of the node /var/log/puppet/ > > M > > > On 2018-11-01 6:45 a.m., von Hoesslin, Volker wrote: > > Hello, there, > > i have now built a complete stack and believe i did everything right. > after unlocking the compute nodes (two pieces), the nodes come into an > endless boot loop. > > Error messages are not really noticeable, except: > > compute-X 'ceilometer-polling' process has failed. Auto recovery in > progress > > > > any suggestions? Greez & thx, volker... > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > mailto:Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > _______________________________________________ > Starlingx-discuss mailing list > mailto:Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Starlingx-discuss mailing list > mailto:Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > ------------------------------ > > End of Starlingx-discuss Digest, Vol 6, Issue 3 > *********************************************** > > > > -- This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free or virus-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Sysware (Thailand) Co., Ltd., Bangkok, Thailand. www.sysware.asia -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 35269 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 108233 bytes Desc: not available URL: From scott.little at windriver.com Fri Nov 2 20:19:33 2018 From: scott.little at windriver.com (Scott Little) Date: Fri, 2 Nov 2018 16:19:33 -0400 Subject: [Starlingx-discuss] Missing "Lighttpd-1.4.50-1.el7.src.rpm" Package Re: Starlingx-discuss Digest, Vol 6, Issue 3 In-Reply-To: <550068C2-0613-41D1-955E-4FC12668E612@intel.com> References: <550068C2-0613-41D1-955E-4FC12668E612@intel.com> Message-ID: You can find it here ... http://mirror.starlingx.cengn.ca/mirror/centos/epel/dl.fedoraproject.org/pub/epel/7/SRPMS/Packages/l/lighttpd-1.4.50-1.el7.src.rpm On 18-11-02 02:16 PM, Cordoba Malibran, Erich wrote: > Hi, > > Since yesterday it seems that the lighttpd version was upgraded in the upstream server. This means that your > mirror is incomplete and that is why you are seeing that failure. > > From other thread in the mailing: > I could find the src rpm with below repo (./centos-mirror-tools/yum.repos.d/StarlingX-EPEL-7.repo). > Could you help double check it? > > [slin14 at eb7345575ec1 cgcs-root]$ sudo -E yumdownloader -C --url --source lighttpd-1.4.50-1.el7 > https://dl.fedoraproject.org/pub/epel/7/SRPMS/Packages/l/lighttpd-1.4.50-1.el7.src.rpm > > So, you can try the following: > > - Download the missing file manually > - Update the cgcs-centos-repo symlinks. Just run generate-cgcs-centos-repo.sh > - Try to build again. > > We hope to fix this issue in the next days. > > -Erich > > From: Pongsawat Payungwong > Date: Friday, November 2, 2018 at 7:05 AM > To: "starlingx-discuss at lists.starlingx.io" > Cc: "Einarsson, Jim" > Subject: [Starlingx-discuss] Missing "Lighttpd-1.4.50-1.el7.src.rpm" Package Re: Starlingx-discuss Digest, Vol 6, Issue 3 > > Hi Team, >  I would like to get some advice for mirror:Source/lighttpd-1.4.50-1.el7.src.rpm   ,  We are from Thailand, Bangkok, trying to build starlingx ISO image on Supermicro Server, [4SSDx1TB, 256Gb Ram, 4x10GE], follow everything on document step but missing  "lighttpd-1.4.50-1.el7.src.rpm', ,  It download from mirror centos repo from ASIA region... > I saw similar "lighttpd" issue in this email thread as well but not sure same with my issue or not. > > We can't   "$build pkgs "   error as below.. > ----Excerpt---- > 16:52:40 b0: ===== Build SRPM for 'python-cephclient' ===== > 16:52:40 b0: PKG_BASE=/localdisk/designer/swthadmin/starlingx/cgcs-root/stx/stx-integ/ceph/python-cephclient > 16:52:40 b0: WORK_BASE=/localdisk/loadbuild/swthadmin/starlingx/std/inputs/stx/stx-integ/ceph/python-cephclient > 16:52:40 b0: RPMBUILD_BASE=/localdisk/loadbuild/swthadmin/starlingx/std/inputs/stx/stx-integ/ceph/python-cephclient/rpmbuild > 16:52:40 b0: Wrote: /localdisk/loadbuild/swthadmin/starlingx/std/rpmbuild/SOURCES/python-cephclient/srpm_input.md5 > 16:52:40 b0: SRPM build not required for '/localdisk/designer/swthadmin/starlingx/cgcs-root/stx/stx-integ/ceph/python-cephclient' > 16:52:40 b0: ===== Build complete for 'python-cephclient' ===== > 16:52:40 b0: > 16:52:40 ============ Build failed ============= > 16:52:40 b0: ERROR: build_dir (415): Invalid srpm path 'mirror:Source/lighttpd-1.4.50-1.el7.src.rpm', evaluated as '/localdisk/designer/swthadmin/starlingx/cgcs-root/cgcs-centos-repo/Source/lighttpd-1.4.50-1.el7.src.rpm', found in '/localdisk/designer/swthadmin/starlingx/cgcs-root/stx/stx-integ/base/lighttpd/centos/srpm_path' > 16:52:40 ERROR: reaper (1302): Failed to build src.rpm from source at 'b0' > 16:52:40 > > ######## Thu Nov  1 16:52:40 UTC 2018: build-srpm-parallel --std failed with rc=1 > > Thu Nov  1 16:52:40 UTC 2018: build-srpm-parallel --std failed with rc=1 > > ----------end------------------- > > > Any advice are welcome. > > -- > Warmest Regards, > Pongsawat P > Sysware Technology (Thailand) > > On Fri, Nov 2, 2018 at 5:38 AM wrote: > Send Starlingx-discuss mailing list submissions to >         mailto:starlingx-discuss at lists.starlingx.io > > To subscribe or unsubscribe via the World Wide Web, visit >         http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > or, via email, send a message with subject or body 'help' to >         mailto:starlingx-discuss-request at lists.starlingx.io > > You can reach the person managing the list at >         mailto:starlingx-discuss-owner at lists.starlingx.io > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Starlingx-discuss digest..." > > > Today's Topics: > >    1. Re: Automated Notification for: [mirror-downloader][#119] >       Missing packages - Results report (Cordoba Malibran, Erich) >    2. Re: Automated Notification for: [mirror-downloader][#119] >       Missing packages - Results report (Xie, Cindy) >    3. Re: Automated Notification for: [mirror-downloader][#119] >       Missing packages - Results report (Rowsell, Brent) >    4. Re: Compute boot-loop (von Hoesslin, Volker) >    5. Re: Compute boot-loop (Michel Thebeau) >    6. Re: Propose OpenStack/Apmec to StarlingX like an upstream >       component (Dean Troyer) >    7. Re: Compute boot-loop (Alonso, Juan Carlos) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 1 Nov 2018 13:11:37 +0000 > From: "Cordoba Malibran, Erich" > To: "mailto:starlingx-discuss at lists.starlingx.io" >         > Subject: Re: [Starlingx-discuss] Automated Notification for: >         [mirror-downloader][#119] Missing packages - Results report > Message-ID: > Content-Type: text/plain; charset="utf-8" > > Lighttpd was upgraded in upstream: > > Package lighttpd-1.4.50-1.el7.src not found, available lighttpd-1.4.51-1.el7.src > > We'll send a patch for master today. Should we backport this to r/2018.10 branch? > > -Erich > > On 11/1/18, 3:37 AM, "mailto:aragorn at intel.com" wrote: > >     [mirror-downloader][#119] Missing packages. Results report: >      - Missing: logs/L1_srpms_missing_centos.log >     lighttpd-1.4.50-1.el7.src.rpm - Missing GPG key: >     ./output/stx-r1/CentOS/pike/Source/libvirt-python-4.7.0-1.fc28.src.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#596bea5d) > > > ------------------------------ > > Message: 2 > Date: Thu, 1 Nov 2018 13:53:00 +0000 > From: "Xie, Cindy" > To: "Cordoba Malibran, Erich" , >         "mailto:starlingx-discuss at lists.starlingx.io" >         , "Liu, ZhipengS" >         > Subject: Re: [Starlingx-discuss] Automated Notification for: >         [mirror-downloader][#119] Missing packages - Results report > Message-ID: >         > > Content-Type: text/plain; charset="utf-8" > > + Zhipeng > We still have patches on lighttpd and it was rebased to 1.4.50 recently by Zhipeng. If the srpm upgraded to 1.4.51, Zhipeng can you please work w/ Erich and see if those patches need rework? > > Thx. - cindy > > -----Original Message----- > From: Cordoba Malibran, Erich [mailto:mailto:erich.cordoba.malibran at intel.com] > Sent: Thursday, November 1, 2018 6:12 AM > To: mailto:starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report > > Lighttpd was upgraded in upstream: > > Package lighttpd-1.4.50-1.el7.src not found, available lighttpd-1.4.51-1.el7.src > > We'll send a patch for master today. Should we backport this to r/2018.10 branch? > > -Erich > > On 11/1/18, 3:37 AM, "mailto:aragorn at intel.com" wrote: > >     [mirror-downloader][#119] Missing packages. Results report: >      - Missing: logs/L1_srpms_missing_centos.log >     lighttpd-1.4.50-1.el7.src.rpm - Missing GPG key: >     ./output/stx-r1/CentOS/pike/Source/libvirt-python-4.7.0-1.fc28.src.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#596bea5d) > > _______________________________________________ > Starlingx-discuss mailing list > mailto:Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > ------------------------------ > > Message: 3 > Date: Thu, 1 Nov 2018 13:55:36 +0000 > From: "Rowsell, Brent" > To: "Xie, Cindy" , "Cordoba Malibran, Erich" >         , >         "mailto:starlingx-discuss at lists.starlingx.io" >         , "Liu, ZhipengS" >         > Subject: Re: [Starlingx-discuss] Automated Notification for: >         [mirror-downloader][#119] Missing packages - Results report > Message-ID: >         > Content-Type: text/plain; charset="utf-8" > > This needs to be functionally tested before it is pushed. > > Brent > > -----Original Message----- > From: Xie, Cindy [mailto:mailto:cindy.xie at intel.com] > Sent: Thursday, November 1, 2018 9:53 AM > To: Cordoba Malibran, Erich ; mailto:starlingx-discuss at lists.starlingx.io; Liu, ZhipengS > Subject: Re: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report > > + Zhipeng > We still have patches on lighttpd and it was rebased to 1.4.50 recently by Zhipeng. If the srpm upgraded to 1.4.51, Zhipeng can you please work w/ Erich and see if those patches need rework? > > Thx. - cindy > > -----Original Message----- > From: Cordoba Malibran, Erich [mailto:mailto:erich.cordoba.malibran at intel.com] > Sent: Thursday, November 1, 2018 6:12 AM > To: mailto:starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#119] Missing packages - Results report > > Lighttpd was upgraded in upstream: > > Package lighttpd-1.4.50-1.el7.src not found, available lighttpd-1.4.51-1.el7.src > > We'll send a patch for master today. Should we backport this to r/2018.10 branch? > > -Erich > > On 11/1/18, 3:37 AM, "mailto:aragorn at intel.com" wrote: > >     [mirror-downloader][#119] Missing packages. Results report: >      - Missing: logs/L1_srpms_missing_centos.log >     lighttpd-1.4.50-1.el7.src.rpm - Missing GPG key: >     ./output/stx-r1/CentOS/pike/Source/libvirt-python-4.7.0-1.fc28.src.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#596bea5d) > > _______________________________________________ > Starlingx-discuss mailing list > mailto:Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > mailto:Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > ------------------------------ > > Message: 4 > Date: Thu, 1 Nov 2018 16:12:26 +0000 > From: "von Hoesslin, Volker" > To: "'mailto:starlingx-discuss at lists.starlingx.io'" >         > Subject: Re: [Starlingx-discuss] Compute boot-loop > Message-ID: > Content-Type: text/plain; charset="utf-8" > > Maybe it helps: https://ibb.co/n2OgoL > > ---------------------------------------------------------------- > Hello, there, > i have now built a complete stack and believe i did everything right. after unlocking the compute nodes (two pieces), the nodes come into an endless boot loop. > Error messages are not really noticeable, except: > compute-X 'ceilometer-polling' process has failed. Auto recovery in progress > > any suggestions? Greez & thx, volker... > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > ------------------------------ > > Message: 5 > Date: Thu, 1 Nov 2018 12:28:53 -0400 > From: Michel Thebeau > To: "von Hoesslin, Volker" , >         "'mailto:starlingx-discuss at lists.starlingx.io'" >         > Subject: Re: [Starlingx-discuss] Compute boot-loop > Message-ID: > Content-Type: text/plain; charset="windows-1252"; format=flowed > > Hi Volker, > > Could you describe the instructions you were using to setup startlingx > (were you following a wiki online)?  Did you recheck the instructions > versus what is actually configured on the computes? > > How many cpus do your computes have? > > Which build are you using?  Did you build your own? > > When reboot-loop happens on a node often the error will be presented on > the console during boot or could be inferred from console, sometimes > referring to puppet logs of the node /var/log/puppet/ > > M > > > On 2018-11-01 6:45 a.m., von Hoesslin, Volker wrote: >> Hello, there, >> i have now built a complete stack and believe i did everything right. after unlocking the compute nodes (two pieces), the nodes come into an endless boot loop. >> Error messages are not really noticeable, except: >> compute-X 'ceilometer-polling' process has failed. Auto recovery in progress >> >> any suggestions? Greez & thx, volker... >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> mailto:Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > ------------------------------ > > Message: 6 > Date: Thu, 1 Nov 2018 12:16:18 -0500 > From: Dean Troyer > To: mailto:doantungbk.203 at gmail.com > Cc: mailto:starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Propose OpenStack/Apmec to StarlingX >         like an upstream component > Message-ID: >         > Content-Type: text/plain; charset="UTF-8" > > On Thu, Nov 1, 2018 at 7:44 AM Tung Doan wrote: >> I am Tung Doan - An OpenStack contributor and the PTL of OpenStack/Apmec project. Since we acknowledged the potential integration between Apmec and StarlingX, I am writing this email to propose adding OpenStack/Apmec to StarlingX like an upstream project. >> >> Project description: OpenStack Apmec [1] stands for the Automated Provisioning Framework for Multi-access Edge Computing which is the first orchestration and management framework dedicated to the MEC services in OpenStack. Below are some of the outstanding features of Apmec project: > I believe Apmec is not an official OpenStack project (as listed in > [0]), do you have plans to apply to become an official OpenStack > project under TC governance?  (Until then you do need to be careful > about referring to Apmec as 'an OpenStack project', it is hosted by > OpenStack, but is not (yet?) an OpenStack project.) > >> - no need to take care of the NFV functionalities. Since existing NFV MANO frameworks (Tacker, ONAP, OSM, OpenBaton,...) are diverse, integrating them can make StarlingX complicated. Apmec was designed to take over responsibility for integrating them since the delivery of MEC services is our critical mission. > Is this replacing existing StarlingX functionality? > >>   - no need to take care of the life-cycle management of the MEC applications. Apmec offers API to help StarlingX perform this function.  As mentioned earlier, Apmec is OpenStack project, therefore, to provide low-latency for MEC applications,  Apmec is also planned to support acceleration technologies (e.g, integrated with OpenStack Cyborg) such as DPDK and FPGA. > Can you get more specific about what the integration with StarlingX looks like? > > dt > > [0] https://governance.openstack.org/tc/reference/projects/index.html > From scott.little at windriver.com Fri Nov 2 20:22:55 2018 From: scott.little at windriver.com (Scott Little) Date: Fri, 2 Nov 2018 16:22:55 -0400 Subject: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 In-Reply-To: <2F61A2101B4FD447A683EF7E362CF9421C63E2181F@RSI-NOD-EXMDB6.india.rsystems.com> References: <2F61A2101B4FD447A683EF7E362CF9421C63E2181F@RSI-NOD-EXMDB6.india.rsystems.com> Message-ID: <3a8a02b2-624d-6f91-5dbd-b20d3fab0e16@windriver.com> Try updating your stx-tools and running download_mirror.sh again. Alternatively, you can find it here ... http://mirror.starlingx.cengn.ca/mirror/centos/epel/dl.fedoraproject.org/pub/epel/7/SRPMS/Packages/l/lighttpd-1.4.50-1.el7.src.rpm Scott On 18-11-02 05:19 AM, Rajesh Jha wrote: > Hi, > > > We were trying to pick up patches for some issues which we had reported like SSH not working and failing to attach data interface from controller to compute nodes. We failed to make the build. at step 2 of section Download Packages¶ from > https://docs.starlingx.io/developer_guide/index.html#build-the-centos-mirror-repository document. > when we run download_mirror.sh from the container There is one package which fails to download lighttpd-1.4.50-1.el7.src.rpm which is there in rpms_centos.lst. Since this version is not there on any mirror on internet, the version available is lighttpd-1.4.51-1.el7.src.rpm so we updated the file rpms_centos.lst and rpms_centos3rdparties.lst with lighttpd-1.4.51-1.el7.x86_64.rpm instead. Ran the download_mirror.sh again. Now everything is fine except it is failing in build-pkgs step with the following error. > > b6: ERROR: build_dir (415): Invalid srpm path 'mirror:Source/lighttpd-1.4.50-1.el7.src.rpm', evaluated as '/localdisk/designer/builder/starlingx/cgcs-root/cgcs-centos-repo/Source/lighttpd-1.4.50-1.el7.src.rpm', found in '/localdisk/designer/builder/starlingx/cgcs-root/stx/stx-integ/base/lighttpd/centos/srpm_path' > > now we are stuck and unable to build. Any suggestions would be welcome. > > on a general note, had a quick query how much time the incremental build is taking in general. Because we follow the steps for incremental build after step git clone https://git.starlingx.io/stx-tools > > and then we build the container image and all steps after that which is also taking 3 to 4 hours. Am I doing the incremental build properly?? > > Best Regards, > Rajesh Jha > > > The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, please immediately alert the sender by reply e-mail and then delete this message. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. R Systems has taken every reasonable precaution to minimize the risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From liang.a.fang at intel.com Sat Nov 3 07:43:36 2018 From: liang.a.fang at intel.com (Fang, Liang A) Date: Sat, 3 Nov 2018 07:43:36 +0000 Subject: [Starlingx-discuss] glance api service is not started in all-in-one deployment In-Reply-To: References: Message-ID: Thanks Stefan. Is there any help doc about SM? Where does SM read the service list and the service exec from? Regards Liang From: Dinescu, Stefan [mailto:Stefan.Dinescu at windriver.com] Sent: Friday, November 2, 2018 6:11 PM To: Fang, Liang A ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] glance api service is not started in all-in-one deployment Hi, On StarlingX, glance-api is managed by SM (short for service management). You can see a list of all the services by using "sm-dump" (from a root prompt or use sudo). If it is working, the sate should be "enabled-active". To restart the service us "sm-restart service glance-api". Also check the logs (/var/log/glance/glance-api.log) for any obvious errors that prevent the service from restarting. ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Friday, November 02, 2018 11:34 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] glance api service is not started in all-in-one deployment Hi I deployed an starlingx all-in-one environment, and it seems glance api service has not been started. I also checked other services such as cinder api / cinder volume, there are started. /bin/sh /usr/lib/ocf/resource.d/openstack/cinder-schedule start /bin/sh /usr/lib/ocf/resource.d/openstack/cinder-volume start /bin/sh /usr/lib/ocf/resource.d/openstack/cinder-backup start But these are not started by service file such as openstack-cinder-api.service / openstack-cinder-scheduler.service. This is really different with the deployment by devstack. Could anybody point out how the services are started? How to restart cinder/glance service in starlingx deployment? Thanks. Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From vm.rod25 at gmail.com Sat Nov 3 13:45:22 2018 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Sat, 3 Nov 2018 07:45:22 -0600 Subject: [Starlingx-discuss] Starlingx stable ISO In-Reply-To: References: Message-ID: +1 On Fri, Nov 2, 2018 at 4:12 AM Saju M wrote: > > Hi, > > How to get stable Starlinx ISO image instead of build from scratch. > I have seen the doc which explains how to build ISO image. > https://docs.starlingx.io/developer_guide/index.html#developer-guide > It would be helpful if we can upload stable ISO file somewhere publicly. > > Regards > Saju Madhavan > +91 09535134654 > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From erich.cordoba.malibran at intel.com Sat Nov 3 16:21:26 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Sat, 3 Nov 2018 16:21:26 +0000 Subject: [Starlingx-discuss] [build] size of official mirror Message-ID: <640F0E2D-5289-48A0-80A8-6E2F1A089ADC@intel.com> Hi, I was taking a look into the mirror recently created and I noticed that is bigger than the needed for StarlingX. It seems to have complete centos mirrors like this[0] or this[1]. For starlingx we only need around 2GB of packages. Does anybody knows the rationale behind this amount of files? -Erich [0] http://mirror.starlingx.cengn.ca/mirror/centos/centos/vault.centos.org/7.4.1708/os/Source/SPackages/  [1] http://mirror.starlingx.cengn.ca/mirror/centos/centos/mirror.centos.org/7.5.1804/os/x86_64/ From cindy.xie at intel.com Mon Nov 5 06:24:18 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Mon, 5 Nov 2018 06:24:18 +0000 Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED In-Reply-To: References: <3868FDB4-49FA-4429-8657-7C4FBD0D93C1@gmail.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35DB6397@SHSMSX104.ccr.corp.intel.com> For stx-integ, this repo was used for non-openstack distro sub-project a lot. I am hoping that both Saul and Brent can be the core reviewers for it. stx-integ - Integration and packaging Scott Little (scott.little at windriver.com) Bob Church (Robert.Church at windriver.com) Don Penney (Don.Penney at windriver.com ) Wold, Saul Rowsell, Brent Thx. - cindy -----Original Message----- From: Smith, Tyler [mailto:tyler.smith at windriver.com] Sent: Friday, November 2, 2018 11:20 AM To: Ildiko Vancsa ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED OK for stx-gui Thanks, Tyler -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: Friday, November 2, 2018 1:37 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED Hi Technical Leads, I started to work on creating the core reviewer groups in Gerrit for each of the sub-projects in StarlingX and I need your input to complete this task. I have an initial list below containing the sub-project repos and the names of the core reviewers belonging to the groups. Please check your sub-project and respond with corrections or with an ‘OK’ in case the core team for your project is listed correctly. Please let me know if you have any questions. Thanks and Best Regards, Ildikó stx-clients - client libraries Jerry Sun (Jerry.Sun at windriver.com) Greg Waines (Greg.Waines at windriver.com) stx-config - Configuration Management Bart Wensley (Barton.Wensley at windriver.com) John Kung (John.Kung at windriver.com) Don Penney (Don.Penney at windriver.com) Bob Church (Robert.Church at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) stx-fault - Fault Management Tao Liu (Tao.Liu at windriver.com) Al Bailey (Al.Bailey at windriver.com) stx-integ - Integration and packaging Scott Little (scott.little at windriver.com) Bob Church (Robert.Church at windriver.com) Don Penney (Don.Penney at windriver.com ) stx-gui - Horizon plugins for new services Tyler Smith (Tyler.Smith at windriver.com) Angie Wang (Angie.Wang at windriver.com) Kristine Bujold (Kristine.Bujold at windriver.com) stx-ha - High Availability/Service Management Bin Qian (Bin.Qian at windriver.com) Eric Macdonald (Eric.MacDonald at windriver.com) John Kung (John.Kung at windriver.com) stx-metal - Bare Metal Management Eric Macdonald (Eric.MacDonald at windriver.com) John Kung (John.Kung at windriver.com) Tao Liu (Tao.Liu at windriver.com) stx-nfv - NFVI Orchestration Bart Wensley (Barton.Wensley at windriver.com) Al Bailey (Al.Bailey at windriver.com) Jack Ding (Jack.Ding at windriver.com) stx-update - Installation/Update/Patching Bart Wensley (Barton.Wensley at windriver.com) Don Penney (Don.Penney at windriver.com) David Sullivan (David.Sullivan at windriver.com) stx-upstream - Upstream packages Bob Church (Robert.Church at windriver.com) Al Bailey (Al.Bailey at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) stx-distcloud – Distributed Cloud Bart Wensley (Barton.Wensley at windriver.com) Brent Rowsell brent.rowsell at windriver.com Chris Friesen (Chris.Friesen at windriver.com) Dean Troyer dtroyer at gmail.com John Kung john.kung at windriver.com Saul Wold sgw at linux.intel.com stx-distcloud-client – Distributed Cloud Bart Wensley (Barton.Wensley at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) John Kung (John.Kung at windriver.com ) stx-manifest - source manifest to manage the repositories Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) stx-root - build source tree root Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) stx-tis-repo - build support Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) stx-tools - build tools Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cindy.xie at intel.com Mon Nov 5 06:27:08 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Mon, 5 Nov 2018 06:27:08 +0000 Subject: [Starlingx-discuss] Weekly StarlingX non-OpenStack Distro meeting Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35DB63C4@SHSMSX104.ccr.corp.intel.com> * Cadence and time slot: o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) * Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ * Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3648 bytes Desc: not available URL: From cindy.xie at intel.com Mon Nov 5 06:27:43 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Mon, 5 Nov 2018 06:27:43 +0000 Subject: [Starlingx-discuss] Canceled: Weekly StarlingX non-OpenStack Distro meeting Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35DB644D@SHSMSX104.ccr.corp.intel.com> * Cadence and time slot: o Wednesday 9AM EDT (9PM China time) * Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ * Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 5225 bytes Desc: not available URL: From cindy.xie at intel.com Mon Nov 5 06:27:42 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Mon, 5 Nov 2018 06:27:42 +0000 Subject: [Starlingx-discuss] Canceled: Weekly StarlingX non-OpenStack Distro meeting Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35DB6414@SHSMSX104.ccr.corp.intel.com> * Cadence and time slot: o Wednesday 9AM EDT (9PM China time) * Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ * Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 13028 bytes Desc: not available URL: From cindy.xie at intel.com Mon Nov 5 06:36:09 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Mon, 5 Nov 2018 06:36:09 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack Distro meeting, 11/7 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35DB65E0@SHSMSX104.ccr.corp.intel.com> Agenda for 11/7 meeting: 1. 2019.03 release content discussion (Cindy) 2. non-openStack patch refactor status (Zhipeng/Shuicheng) 3. non-openStack patch upstream status (Saul) 4. Ceph upgrade status (Vivian/Dehao) 5. Opens (all) For anybody who would like to add topics into agenda, please let me know. Thx. - cindy -----Original Appointment----- From: Xie, Cindy Sent: Sunday, November 4, 2018 10:27 PM To: Xie, Cindy; Wold, Saul; Rowsell, Brent; Jones, Bruce E; Troyer, Dean; Khalil, Ghada; Waheed, Numan; Lin, Shuicheng; Zhu, Vivian; Shang, Dehao; Liu, ZhipengS; Hu, Yong; Sun, Austin; Somerville, Jim; starlingx-discuss at lists.starlingx.io Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, November 7, 2018 6:00 AM-7:00 AM (UTC-08:00) Pacific Time (US & Canada). Where: https://zoom.us/j/342730236 . Cadence and time slot: o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) . Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ . Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other From Volker.Hoesslin at swsn.de Mon Nov 5 13:56:31 2018 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Mon, 5 Nov 2018 13:56:31 +0000 Subject: [Starlingx-discuss] Compute boot-loop In-Reply-To: <1e1ebab5-998b-3c27-fc68-4360e148315f@windriver.com> References: <1e1ebab5-998b-3c27-fc68-4360e148315f@windriver.com> Message-ID: build instructions: https://docs.starlingx.io/developer_guide/ (2018-11-02) install instruction: https://docs.starlingx.io/installation_guide/dedicated_storage.html#dedicated-storage the installation runs without problems, only at the very end the unlocking of the compute-nodes ends in said endless loop. here are the last ~500kb of puppet.log from the compute-node: https://pastebin.com/wsSUY741 it seems that there are problems with the network interface eno1. the output of "ip a" only shows eno2, eno1 is not started. did i understand correctly that the "data" interface at the compute-nodes is the interface via which the "provider-networks" can be reached (via VLAN) ? i refer to this line from the doku: system host-if-modify -p providernet-a -c data compute-0 eno1 here is an overview of my network, basically very primitive and i think also in the sense of starlingX/openstack quite classic. https://docdro.id/0CRp2OA i am grateful for any help! Volker... -----Ursprüngliche Nachricht----- Von: Michel Thebeau [mailto:michel.thebeau at windriver.com] Gesendet: Donnerstag, 1. November 2018 17:29 An: von Hoesslin, Volker; 'starlingx-discuss at lists.starlingx.io' Betreff: Re: [Starlingx-discuss] Compute boot-loop Hi Volker, Could you describe the instructions you were using to setup startlingx (were you following a wiki online)?  Did you recheck the instructions versus what is actually configured on the computes? How many cpus do your computes have? Which build are you using?  Did you build your own? When reboot-loop happens on a node often the error will be presented on the console during boot or could be inferred from console, sometimes referring to puppet logs of the node /var/log/puppet/ M On 2018-11-01 6:45 a.m., von Hoesslin, Volker wrote: > Hello, there, > i have now built a complete stack and believe i did everything right. after unlocking the compute nodes (two pieces), the nodes come into an endless boot loop. > Error messages are not really noticeable, except: > compute-X 'ceilometer-polling' process has failed. Auto recovery in progress > > any suggestions? Greez & thx, volker... > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From michel.thebeau at windriver.com Mon Nov 5 14:55:22 2018 From: michel.thebeau at windriver.com (Michel Thebeau) Date: Mon, 5 Nov 2018 09:55:22 -0500 Subject: [Starlingx-discuss] Compute boot-loop In-Reply-To: References: <1e1ebab5-998b-3c27-fc68-4360e148315f@windriver.com> Message-ID: <13a017af-35c1-a889-e884-c81b950715c7@windriver.com> Hi Volker, The puppet log is pointing at vswitch.  I'll ask one of the networking guys to look at this thread. 2018-11-05T11:16:26.170 Notice: 2018-11-05 11:16:26 +0000 /Stage[main]/Platform::Vswitch::Ovs/Platform::Vswitch::Ovs::Device[0000:01:00.0]/Exec[ovs-bind-device: 0000:01:00.0]/returns: Error: bind failed for 0000:01:00.0 - Cannot bind to driver vfio-pci 2018-11-05T11:16:26.173 Notice: 2018-11-05 11:16:26 +0000 /Stage[main]/Platform::Vswitch::Ovs/Platform::Vswitch::Ovs::Device[0000:01:00.0]/Exec[ovs-bind-device: 0000:01:00.0]/returns: Error: unbind failed for 0000:01:00.0 - Cannot open /sys/bus/pci/drivers//unbind 2018-11-05T11:16:26.175 Error: 2018-11-05 11:16:26 +0000 dpdk-devbind.py --bind=vfio-pci 0000:01:00.0 returned 1 instead of one of [0] === PS.  It is normal for ifconfig and ip commands to not show the interfaces configured for platform data. M On 2018-11-05 8:56 a.m., von Hoesslin, Volker wrote: > build instructions: https://docs.starlingx.io/developer_guide/ (2018-11-02) > install instruction: https://docs.starlingx.io/installation_guide/dedicated_storage.html#dedicated-storage > > the installation runs without problems, only at the very end the unlocking of the compute-nodes ends in said endless loop. here are the last ~500kb of puppet.log from the compute-node: > > https://pastebin.com/wsSUY741 > > it seems that there are problems with the network interface eno1. the output of "ip a" only shows eno2, eno1 is not started. > did i understand correctly that the "data" interface at the compute-nodes is the interface via which the "provider-networks" can be reached (via VLAN) ? i refer to this line from the doku: > > system host-if-modify -p providernet-a -c data compute-0 eno1 > > here is an overview of my network, basically very primitive and i think also in the sense of starlingX/openstack quite classic. > > https://docdro.id/0CRp2OA > > i am grateful for any help! > > Volker... > > -----Ursprüngliche Nachricht----- > Von: Michel Thebeau [mailto:michel.thebeau at windriver.com] > Gesendet: Donnerstag, 1. November 2018 17:29 > An: von Hoesslin, Volker; 'starlingx-discuss at lists.starlingx.io' > Betreff: Re: [Starlingx-discuss] Compute boot-loop > > Hi Volker, > > Could you describe the instructions you were using to setup startlingx > (were you following a wiki online)?  Did you recheck the instructions > versus what is actually configured on the computes? > > How many cpus do your computes have? > > Which build are you using?  Did you build your own? > > When reboot-loop happens on a node often the error will be presented on > the console during boot or could be inferred from console, sometimes > referring to puppet logs of the node /var/log/puppet/ > > M > > > On 2018-11-01 6:45 a.m., von Hoesslin, Volker wrote: >> Hello, there, >> i have now built a complete stack and believe i did everything right. after unlocking the compute nodes (two pieces), the nodes come into an endless boot loop. >> Error messages are not really noticeable, except: >> compute-X 'ceilometer-polling' process has failed. Auto recovery in progress >> >> any suggestions? Greez & thx, volker... >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From michel.thebeau at windriver.com Mon Nov 5 15:34:18 2018 From: michel.thebeau at windriver.com (Michel Thebeau) Date: Mon, 5 Nov 2018 10:34:18 -0500 Subject: [Starlingx-discuss] Compute boot-loop In-Reply-To: References: <1e1ebab5-998b-3c27-fc68-4360e148315f@windriver.com> <8557B550001AFB46A43A0CCC314BF85153C592E1@FMSMSX108.amr.corp.intel.com> Message-ID: <7e411c5d-ae49-c4f8-35b8-4dd59ef91f34@windriver.com> Ack Yong. I received this initial internal response:  "The usual cause of this error is when they don't enable VT-d (Intel Virtualization Technology for Directed I/O) in the BIOS for the compute hosts." Volker, please let us know when you've confirmed that. M On 2018-11-01 9:19 p.m., Hu, Yong wrote: > Another head-up is that we need to assure VT is turned on in BIOS for the compute node. > > > On 02/11/2018, 6:39 AM, "Alonso, Juan Carlos" wrote: > > Hi, > > I think you set up a Duplex system (two controllers), right? > > I set up a Duplex system with two ISOs: stx-2018-10-30-171-master.iso and stx-2018-11-01-8-master.iso > I faced the same issue you mention with first ISO, but did not with today's ISO: stx-2018-11-01-8-master.iso. > > Please set up again a Duplex system with today's ISO to see if issue is still presented. > > Regards. > Juan Carlos Alonso > > -----Original Message----- > From: Michel Thebeau [mailto:michel.thebeau at windriver.com] > Sent: Thursday, November 1, 2018 10:29 AM > To: von Hoesslin, Volker ; 'starlingx-discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] Compute boot-loop > > Hi Volker, > > Could you describe the instructions you were using to setup startlingx (were you following a wiki online)? Did you recheck the instructions versus what is actually configured on the computes? > > How many cpus do your computes have? > > Which build are you using? Did you build your own? > > When reboot-loop happens on a node often the error will be presented on the console during boot or could be inferred from console, sometimes referring to puppet logs of the node /var/log/puppet/ > > M > > > On 2018-11-01 6:45 a.m., von Hoesslin, Volker wrote: > > Hello, there, > > i have now built a complete stack and believe i did everything right. after unlocking the compute nodes (two pieces), the nodes come into an endless boot loop. > > Error messages are not really noticeable, except: > > compute-X 'ceilometer-polling' process has failed. Auto recovery in progress > > > > any suggestions? Greez & thx, volker... > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > From scott.little at windriver.com Mon Nov 5 15:37:26 2018 From: scott.little at windriver.com (Scott Little) Date: Mon, 5 Nov 2018 10:37:26 -0500 Subject: [Starlingx-discuss] [build] size of official mirror In-Reply-To: <640F0E2D-5289-48A0-80A8-6E2F1A089ADC@intel.com> References: <640F0E2D-5289-48A0-80A8-6E2F1A089ADC@intel.com> Message-ID: <22f7d850-6184-65f8-6cc0-336e2a5bce65@windriver.com> That was the intent, as presented to me. 1) What you see currently It's not a StarlingX mirror, it's a CentOS/EPEL mirror for use by StarlingX.  The StarlingX specific parts will be added when CENGN can host it's own builds. 2) Allows use of standard reposync tool 3) A new package can be added to StarlingX at any time.  It was likely in test weeks before being accepted using version X.  If version Y is released roughly concurrent with the review of the update that introduces the requirement for X, we might see breakage.  This way X is already available. 4) (speculative) If we ever wanted to consider feature backports (non-security) to release branches, and the feature adds new packages, we may want to use versions that are compatible with that release.   i.e. if the target release for the backport was based on Centos 7.5, but master is on 7.8.  If the backport requires package Y, but Y has a lot of 'Requires'. Do we want the 7.8 version of Y, or the 7.5 version of Y which is sufficient? The 7.8 version would force us to update a lot of other packages, some of which might be patched.  The scope of work, and the risk, for the backport could increase significantly.  Having 7.5 already cached in our mirror means it's ready for use.  It might no longer be available from upstream.  (e.g. EPEL). On 18-11-03 12:21 PM, Cordoba Malibran, Erich wrote: > Hi, > > I was taking a look into the mirror recently created and I noticed that is > bigger than the needed for StarlingX. It seems to have complete centos mirrors > like this[0] or this[1]. > > For starlingx we only need around 2GB of packages. Does anybody knows the rationale behind > this amount of files? > > -Erich > > [0] http://mirror.starlingx.cengn.ca/mirror/centos/centos/vault.centos.org/7.4.1708/os/Source/SPackages/  > [1] http://mirror.starlingx.cengn.ca/mirror/centos/centos/mirror.centos.org/7.5.1804/os/x86_64/ > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Mon Nov 5 15:47:40 2018 From: scott.little at windriver.com (Scott Little) Date: Mon, 5 Nov 2018 10:47:40 -0500 Subject: [Starlingx-discuss] [Build] Question about meta_patches In-Reply-To: <05124ef14c610cef028774c818b98681efeab12b.camel@intel.com> References: <05124ef14c610cef028774c818b98681efeab12b.camel@intel.com> Message-ID: <9eb73332-1f4a-292e-b8f8-04ffc4aa4f5f@windriver.com> Not just the spec file, but any other files not in the upstream tarball.  E.g. centos specific config files. 1) It works for srpms from all sources.  Including those that don't publish a git of their spec files and other meta-data. 2) It yields a very clean boundary between what was 'ours' and what was 'others'.  Made the lawyers happy. 3) Before we switched to the 'repo' tools, we had to keep all repos using a common branch name.  This created a strong incentive to keep the number of gits to a minimum. On 18-11-01 07:01 PM, Cordoba Malibran, Erich wrote: > Hi all, > > As I understand, the meta_patches are patches that are applied to the > specfiles for projects where a SRPM is downloaded. This process is > something like: > > - Unpack srpm > - Apply patches to the .spec file. Most of this patches are > just modifications to add source code patches. > - Create a new srpm with the source, the modified specfile and > additional patches that will be applied on build time. > > So, having this process, I'm wondering in the need of having the > meta_patches instead in just one .spec checked in the > repository. > > Also, I'm trying to understand the rationale behind these meta_patches. > > Thank you in advance. > > -Erich > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From chris.friesen at windriver.com Mon Nov 5 16:00:59 2018 From: chris.friesen at windriver.com (Chris Friesen) Date: Mon, 5 Nov 2018 10:00:59 -0600 Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED In-Reply-To: <3868FDB4-49FA-4429-8657-7C4FBD0D93C1@gmail.com> References: <3868FDB4-49FA-4429-8657-7C4FBD0D93C1@gmail.com> Message-ID: <75d5f98b-1f30-68e7-0502-18179e2b0695@windriver.com> On 11/2/2018 11:36 AM, Ildiko Vancsa wrote: > Hi Technical Leads, > > I started to work on creating the core reviewer groups in Gerrit for each of the sub-projects in StarlingX and I need your input to complete this task. > > I have an initial list below containing the sub-project repos and the names of the core reviewers belonging to the groups. Please check your sub-project and respond with corrections or with an ‘OK’ in case the core team for your project is listed correctly. I think stx-config, stx-upstream, and stx-distcloud-client look okay. Chris From Volker.Hoesslin at swsn.de Mon Nov 5 16:05:38 2018 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Mon, 5 Nov 2018 16:05:38 +0000 Subject: [Starlingx-discuss] Compute boot-loop In-Reply-To: <7e411c5d-ae49-c4f8-35b8-4dd59ef91f34@windriver.com> References: <1e1ebab5-998b-3c27-fc68-4360e148315f@windriver.com> <8557B550001AFB46A43A0CCC314BF85153C592E1@FMSMSX108.amr.corp.intel.com> <7e411c5d-ae49-c4f8-35b8-4dd59ef91f34@windriver.com> Message-ID: Ok, shame on me! I have to read all the hints from you and realy check all the details... I have an AMD EPYC 7601 (32 cores), and I didn’t realized that the point "IOMMU" in my BIOS the generic term for VT-d is, so it is all the time leave disabled -.- After enabled this option, my VM seems to run, currently booted but still in "In-Test" mode... we will see... Thx for help! Volker... -----Ursprüngliche Nachricht----- Von: Michel Thebeau [mailto:michel.thebeau at windriver.com] Gesendet: Montag, 5. November 2018 16:34 An: Hu, Yong; Alonso, Juan Carlos; von Hoesslin, Volker; 'starlingx-discuss at lists.starlingx.io' Betreff: Re: [Starlingx-discuss] Compute boot-loop Ack Yong. I received this initial internal response:  "The usual cause of this error is when they don't enable VT-d (Intel Virtualization Technology for Directed I/O) in the BIOS for the compute hosts." Volker, please let us know when you've confirmed that. M On 2018-11-01 9:19 p.m., Hu, Yong wrote: > Another head-up is that we need to assure VT is turned on in BIOS for the compute node. > > > On 02/11/2018, 6:39 AM, "Alonso, Juan Carlos" wrote: > > Hi, > > I think you set up a Duplex system (two controllers), right? > > I set up a Duplex system with two ISOs: stx-2018-10-30-171-master.iso and stx-2018-11-01-8-master.iso > I faced the same issue you mention with first ISO, but did not with today's ISO: stx-2018-11-01-8-master.iso. > > Please set up again a Duplex system with today's ISO to see if issue is still presented. > > Regards. > Juan Carlos Alonso > > -----Original Message----- > From: Michel Thebeau [mailto:michel.thebeau at windriver.com] > Sent: Thursday, November 1, 2018 10:29 AM > To: von Hoesslin, Volker ; 'starlingx-discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] Compute boot-loop > > Hi Volker, > > Could you describe the instructions you were using to setup startlingx (were you following a wiki online)? Did you recheck the instructions versus what is actually configured on the computes? > > How many cpus do your computes have? > > Which build are you using? Did you build your own? > > When reboot-loop happens on a node often the error will be presented on the console during boot or could be inferred from console, sometimes referring to puppet logs of the node /var/log/puppet/ > > M > > > On 2018-11-01 6:45 a.m., von Hoesslin, Volker wrote: > > Hello, there, > > i have now built a complete stack and believe i did everything right. after unlocking the compute nodes (two pieces), the nodes come into an endless boot loop. > > Error messages are not really noticeable, except: > > compute-X 'ceilometer-polling' process has failed. Auto recovery in progress > > > > any suggestions? Greez & thx, volker... > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > From Barton.Wensley at windriver.com Mon Nov 5 16:10:23 2018 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Mon, 5 Nov 2018 16:10:23 +0000 Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED In-Reply-To: <3868FDB4-49FA-4429-8657-7C4FBD0D93C1@gmail.com> References: <3868FDB4-49FA-4429-8657-7C4FBD0D93C1@gmail.com> Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA2C0CC@ALA-MBD.corp.ad.wrs.com> Ildikó, Both stx-nfv and stx-update look good. I think stx-distcloud should probably just be: stx-distcloud – Distributed Cloud Bart Wensley (Barton.Wensley at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) John Kung john.kung at windriver.com I'm not sure why the TSC members (Brent, Dean and Saul) were listed as cores for this one project - there isn't anything special about it that would require them as core reviewers. Bart -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: November 2, 2018 1:37 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED Hi Technical Leads, I started to work on creating the core reviewer groups in Gerrit for each of the sub-projects in StarlingX and I need your input to complete this task. I have an initial list below containing the sub-project repos and the names of the core reviewers belonging to the groups. Please check your sub-project and respond with corrections or with an ‘OK’ in case the core team for your project is listed correctly. Please let me know if you have any questions. Thanks and Best Regards, Ildikó stx-clients - client libraries Jerry Sun (Jerry.Sun at windriver.com) Greg Waines (Greg.Waines at windriver.com) stx-config - Configuration Management Bart Wensley (Barton.Wensley at windriver.com) John Kung (John.Kung at windriver.com) Don Penney (Don.Penney at windriver.com) Bob Church (Robert.Church at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) stx-fault - Fault Management Tao Liu (Tao.Liu at windriver.com) Al Bailey (Al.Bailey at windriver.com) stx-integ - Integration and packaging Scott Little (scott.little at windriver.com) Bob Church (Robert.Church at windriver.com) Don Penney (Don.Penney at windriver.com ) stx-gui - Horizon plugins for new services Tyler Smith (Tyler.Smith at windriver.com) Angie Wang (Angie.Wang at windriver.com) Kristine Bujold (Kristine.Bujold at windriver.com) stx-ha - High Availability/Service Management Bin Qian (Bin.Qian at windriver.com) Eric Macdonald (Eric.MacDonald at windriver.com) John Kung (John.Kung at windriver.com) stx-metal - Bare Metal Management Eric Macdonald (Eric.MacDonald at windriver.com) John Kung (John.Kung at windriver.com) Tao Liu (Tao.Liu at windriver.com) stx-nfv - NFVI Orchestration Bart Wensley (Barton.Wensley at windriver.com) Al Bailey (Al.Bailey at windriver.com) Jack Ding (Jack.Ding at windriver.com) stx-update - Installation/Update/Patching Bart Wensley (Barton.Wensley at windriver.com) Don Penney (Don.Penney at windriver.com) David Sullivan (David.Sullivan at windriver.com) stx-upstream - Upstream packages Bob Church (Robert.Church at windriver.com) Al Bailey (Al.Bailey at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) stx-distcloud – Distributed Cloud Bart Wensley (Barton.Wensley at windriver.com) Brent Rowsell brent.rowsell at windriver.com Chris Friesen (Chris.Friesen at windriver.com) Dean Troyer dtroyer at gmail.com John Kung john.kung at windriver.com Saul Wold sgw at linux.intel.com stx-distcloud-client – Distributed Cloud Bart Wensley (Barton.Wensley at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) John Kung (John.Kung at windriver.com ) stx-manifest - source manifest to manage the repositories Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) stx-root - build source tree root Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) stx-tis-repo - build support Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) stx-tools - build tools Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From michel.thebeau at windriver.com Mon Nov 5 16:45:13 2018 From: michel.thebeau at windriver.com (Michel Thebeau) Date: Mon, 5 Nov 2018 11:45:13 -0500 Subject: [Starlingx-discuss] Instance HA (IHA) In-Reply-To: References: Message-ID: Hi Volker, For context, documents describe Instance HA as "respawn the VM on another compute when the compute the VM was running on fails". But you wrote "load-balancer", from what I can tell these are different subjects.  Do you have a document I can refer to? === In so far as I am aware, if you kick a compute node over, the VMs that were running there will restart on another compute node in the cluster (assuming another compute can run them).  I actually haven't tested this on startlingx though.  I'll intend to do that today, now that you've asked about it. I know nothing about load-balancing. M On 2018-11-02 10:15 a.m., von Hoesslin, Volker wrote: > Hello, > has starlingX IHA support? I didnt find it? In generally I didn't find HA load-balancer features? What about Octavia https://wiki.openstack.org/wiki/Octavia ? > > Greez & thx, Volker... > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From michel.thebeau at windriver.com Mon Nov 5 18:22:29 2018 From: michel.thebeau at windriver.com (Michel Thebeau) Date: Mon, 5 Nov 2018 13:22:29 -0500 Subject: [Starlingx-discuss] Instance HA (IHA) In-Reply-To: References: Message-ID: Hi Volker, Yes, what is described online as instance HA is working in StarlingX.  I tested on a cluster with dedicated storage. I added storage extra spec to a flavor, like this: $ nova flavor-key ${flavour_name} set aggregate_instance_extra_specs:storage=remote And I added all the computes to the existing host aggregate named remote_storage_hosts (it already has extra spec storage=remote). Then I launched an instance.  And I abruptly stopped the host it was running on.  After a few seconds the controller recognized the compute was not responding and the instance was rebuilt on the other compute. === If you still have a question for load-balancing, I recommend a new message to starlingx discuss list with instance load-balancing in the subject line. M On 2018-11-05 11:45 a.m., Michel Thebeau wrote: > Hi Volker, > > For context, documents describe Instance HA as "respawn the VM on > another compute when the compute the VM was running on fails". But you > wrote "load-balancer", from what I can tell these are different > subjects.  Do you have a document I can refer to? > > === > > In so far as I am aware, if you kick a compute node over, the VMs that > were running there will restart on another compute node in the cluster > (assuming another compute can run them).  I actually haven't tested > this on startlingx though.  I'll intend to do that today, now that > you've asked about it. > > I know nothing about load-balancing. > > M > > > > > On 2018-11-02 10:15 a.m., von Hoesslin, Volker wrote: >> Hello, >> has starlingX IHA support? I didnt find it? In generally I didn't >> find HA load-balancer features? What about Octavia >> https://wiki.openstack.org/wiki/Octavia ? >> >> Greez & thx, Volker... >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Bin.Qian at windriver.com Mon Nov 5 18:25:16 2018 From: Bin.Qian at windriver.com (Qian, Bin) Date: Mon, 5 Nov 2018 18:25:16 +0000 Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED In-Reply-To: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA2C0CC@ALA-MBD.corp.ad.wrs.com> References: <3868FDB4-49FA-4429-8657-7C4FBD0D93C1@gmail.com>, <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA2C0CC@ALA-MBD.corp.ad.wrs.com> Message-ID: Looks OK for stx-ha Bin ________________________________________ From: Wensley, Barton [Barton.Wensley at windriver.com] Sent: Monday, November 05, 2018 8:10 AM To: Ildiko Vancsa; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED Ildikó, Both stx-nfv and stx-update look good. I think stx-distcloud should probably just be: stx-distcloud – Distributed Cloud Bart Wensley (Barton.Wensley at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) John Kung john.kung at windriver.com I'm not sure why the TSC members (Brent, Dean and Saul) were listed as cores for this one project - there isn't anything special about it that would require them as core reviewers. Bart -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: November 2, 2018 1:37 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED Hi Technical Leads, I started to work on creating the core reviewer groups in Gerrit for each of the sub-projects in StarlingX and I need your input to complete this task. I have an initial list below containing the sub-project repos and the names of the core reviewers belonging to the groups. Please check your sub-project and respond with corrections or with an ‘OK’ in case the core team for your project is listed correctly. Please let me know if you have any questions. Thanks and Best Regards, Ildikó stx-clients - client libraries Jerry Sun (Jerry.Sun at windriver.com) Greg Waines (Greg.Waines at windriver.com) stx-config - Configuration Management Bart Wensley (Barton.Wensley at windriver.com) John Kung (John.Kung at windriver.com) Don Penney (Don.Penney at windriver.com) Bob Church (Robert.Church at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) stx-fault - Fault Management Tao Liu (Tao.Liu at windriver.com) Al Bailey (Al.Bailey at windriver.com) stx-integ - Integration and packaging Scott Little (scott.little at windriver.com) Bob Church (Robert.Church at windriver.com) Don Penney (Don.Penney at windriver.com ) stx-gui - Horizon plugins for new services Tyler Smith (Tyler.Smith at windriver.com) Angie Wang (Angie.Wang at windriver.com) Kristine Bujold (Kristine.Bujold at windriver.com) stx-ha - High Availability/Service Management Bin Qian (Bin.Qian at windriver.com) Eric Macdonald (Eric.MacDonald at windriver.com) John Kung (John.Kung at windriver.com) stx-metal - Bare Metal Management Eric Macdonald (Eric.MacDonald at windriver.com) John Kung (John.Kung at windriver.com) Tao Liu (Tao.Liu at windriver.com) stx-nfv - NFVI Orchestration Bart Wensley (Barton.Wensley at windriver.com) Al Bailey (Al.Bailey at windriver.com) Jack Ding (Jack.Ding at windriver.com) stx-update - Installation/Update/Patching Bart Wensley (Barton.Wensley at windriver.com) Don Penney (Don.Penney at windriver.com) David Sullivan (David.Sullivan at windriver.com) stx-upstream - Upstream packages Bob Church (Robert.Church at windriver.com) Al Bailey (Al.Bailey at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) stx-distcloud – Distributed Cloud Bart Wensley (Barton.Wensley at windriver.com) Brent Rowsell brent.rowsell at windriver.com Chris Friesen (Chris.Friesen at windriver.com) Dean Troyer dtroyer at gmail.com John Kung john.kung at windriver.com Saul Wold sgw at linux.intel.com stx-distcloud-client – Distributed Cloud Bart Wensley (Barton.Wensley at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) John Kung (John.Kung at windriver.com ) stx-manifest - source manifest to manage the repositories Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) stx-root - build source tree root Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) stx-tis-repo - build support Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) stx-tools - build tools Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cboylan at sapwetik.org Mon Nov 5 18:36:27 2018 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 05 Nov 2018 10:36:27 -0800 Subject: [Starlingx-discuss] Community Infrastructure Berlin Summit Onboarding Session Message-ID: <1541442987.3761150.1566423440.2A7B1A3E@webmail.messagingengine.com> Hello everyone, My apologies for cross posting but wanted to make sure the various developer groups saw this. Rather than use the Infrastructure Onboarding session in Berlin [0] for infrastructure sysadmin/developer onboarding, I thought we could use the time for user onboarding. We've got quite a few new groups interacting with us recently, and it would probably be useful to have a session on what we do, how people can take advantage of this, and so on. I've been brainstorming ideas on this etherpad [1]. If you think you'll attend the session and find any of these subjects to be useful please +1 them. Also feel free to add additional topics. I expect this will be an informal session that directly targets the interests of those attending. Please do drop by if you have any interest in using this infrastructure at all. This is your chance to better understand Zuul job configuration, the test environments themselves, the metrics and data we collect, and basically anything else related to the community developer infrastructure. [0] https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22950/infrastructure-project-onboarding [1] https://etherpad.openstack.org/p/openstack-infra-berlin-onboarding Hope to see you there, Clark From vm.rod25 at gmail.com Mon Nov 5 14:44:47 2018 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Mon, 5 Nov 2018 08:44:47 -0600 Subject: [Starlingx-discuss] [Build] Question about meta_patches In-Reply-To: <9eb73332-1f4a-292e-b8f8-04ffc4aa4f5f@windriver.com> References: <05124ef14c610cef028774c818b98681efeab12b.camel@intel.com> <9eb73332-1f4a-292e-b8f8-04ffc4aa4f5f@windriver.com> Message-ID: On Mon, Nov 5, 2018 at 9:48 AM Scott Little wrote: > > Not just the spec file, but any other files not in the upstream > tarball. E.g. centos specific config files. > > 1) It works for srpms from all sources. Including those that don't > publish a git of their spec files and other meta-data. > > 2) It yields a very clean boundary between what was 'ours' and what was > 'others'. Made the lawyers happy. > > 3) Before we switched to the 'repo' tools, we had to keep all repos > using a common branch name. This created a strong incentive to keep the > number of gits to a minimum. > > > > On 18-11-01 07:01 PM, Cordoba Malibran, Erich wrote: > > Hi all, > > > > As I understand, the meta_patches are patches that are applied to the > > specfiles for projects where a SRPM is downloaded. This process is > > something like: > > > > - Unpack srpm > > - Apply patches to the .spec file. Most of this patches are > > just modifications to add source code patches. > > - Create a new srpm with the source, the modified specfile and > > additional patches that will be applied on build time. > > > > So, having this process, I'm wondering in the need of having the > > meta_patches instead in just one .spec checked in the > > repository. > > > > Also, I'm trying to understand the rationale behind these meta_patches. > > > > Thank you in advance. > > > > -Erich > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss HI I am new to the project and i would like to ask some basic questions related to this topic from what i have seen in other projects: a) I love the idea of having one git repository per project where the spec files , sources , patches and more could live (something that we discuss last week with Erich) . In the long/short future if we support other OS based on deb files we could have a directory : rpms_base and deb_baase. However i would like to ear some feedback ( pros and cons ) from the STX community What to do after this is open to the community many tools to build from a single git repository are living today out in the opensource ( koji / obs/ you name it ) But before that ( and in a separate mail ) i would like to hear the feedback about this idea Regards Victor Rodriguez From Bin.Qian at windriver.com Mon Nov 5 19:46:07 2018 From: Bin.Qian at windriver.com (Qian, Bin) Date: Mon, 5 Nov 2018 19:46:07 +0000 Subject: [Starlingx-discuss] glance api service is not started in all-in-one deployment In-Reply-To: References: , Message-ID: Hi, Liang Sm has its sqlite database to have all service and related information stored, the db can be found at /var/run/sm/sm.db on a controller. A quick way to list all services is to use smc command. source /etc/nova/openrc smc service-list This command is similar to sm-dump but sm-dump is only for designers to debug/troubleshooting. smc also provides other sub commands to for querying service, servicegroup, and servicenode. Regards, Bin From: Fang, Liang A [liang.a.fang at intel.com] Sent: Saturday, November 03, 2018 12:43 AM To: Dinescu, Stefan; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] glance api service is not started in all-in-one deployment Thanks Stefan. Is there any help doc about SM? Where does SM read the service list and the service exec from? Regards Liang From: Dinescu, Stefan [mailto:Stefan.Dinescu at windriver.com] Sent: Friday, November 2, 2018 6:11 PM To: Fang, Liang A ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] glance api service is not started in all-in-one deployment Hi, On StarlingX, glance-api is managed by SM (short for service management). You can see a list of all the services by using "sm-dump" (from a root prompt or use sudo). If it is working, the sate should be "enabled-active". To restart the service us "sm-restart service glance-api". Also check the logs (/var/log/glance/glance-api.log) for any obvious errors that prevent the service from restarting. ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Friday, November 02, 2018 11:34 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] glance api service is not started in all-in-one deployment Hi I deployed an starlingx all-in-one environment, and it seems glance api service has not been started. I also checked other services such as cinder api / cinder volume, there are started. /bin/sh /usr/lib/ocf/resource.d/openstack/cinder-schedule start /bin/sh /usr/lib/ocf/resource.d/openstack/cinder-volume start /bin/sh /usr/lib/ocf/resource.d/openstack/cinder-backup start But these are not started by service file such as openstack-cinder-api.service / openstack-cinder-scheduler.service. This is really different with the deployment by devstack. Could anybody point out how the services are started? How to restart cinder/glance service in starlingx deployment? Thanks. Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From John.Kung at windriver.com Mon Nov 5 19:52:36 2018 From: John.Kung at windriver.com (Kung, John) Date: Mon, 5 Nov 2018 19:52:36 +0000 Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED Message-ID: Ildikó, Looks OK for stx-config, Thanks, John -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: November 2, 2018 1:37 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED Hi Technical Leads, I started to work on creating the core reviewer groups in Gerrit for each of the sub-projects in StarlingX and I need your input to complete this task. I have an initial list below containing the sub-project repos and the names of the core reviewers belonging to the groups. Please check your sub-project and respond with corrections or with an 'OK' in case the core team for your project is listed correctly. Please let me know if you have any questions. Thanks and Best Regards, Ildikó stx-clients - client libraries Jerry Sun (Jerry.Sun at windriver.com) Greg Waines (Greg.Waines at windriver.com) stx-config - Configuration Management Bart Wensley (Barton.Wensley at windriver.com) John Kung (John.Kung at windriver.com) Don Penney (Don.Penney at windriver.com) Bob Church (Robert.Church at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) stx-fault - Fault Management Tao Liu (Tao.Liu at windriver.com) Al Bailey (Al.Bailey at windriver.com) stx-integ - Integration and packaging Scott Little (scott.little at windriver.com) Bob Church (Robert.Church at windriver.com) Don Penney (Don.Penney at windriver.com ) stx-gui - Horizon plugins for new services Tyler Smith (Tyler.Smith at windriver.com) Angie Wang (Angie.Wang at windriver.com) Kristine Bujold (Kristine.Bujold at windriver.com) stx-ha - High Availability/Service Management Bin Qian (Bin.Qian at windriver.com) Eric Macdonald (Eric.MacDonald at windriver.com) John Kung (John.Kung at windriver.com) stx-metal - Bare Metal Management Eric Macdonald (Eric.MacDonald at windriver.com) John Kung (John.Kung at windriver.com) Tao Liu (Tao.Liu at windriver.com) stx-nfv - NFVI Orchestration Bart Wensley (Barton.Wensley at windriver.com) Al Bailey (Al.Bailey at windriver.com) Jack Ding (Jack.Ding at windriver.com) stx-update - Installation/Update/Patching Bart Wensley (Barton.Wensley at windriver.com) Don Penney (Don.Penney at windriver.com) David Sullivan (David.Sullivan at windriver.com) stx-upstream - Upstream packages Bob Church (Robert.Church at windriver.com) Al Bailey (Al.Bailey at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) stx-distcloud - Distributed Cloud Bart Wensley (Barton.Wensley at windriver.com) Brent Rowsell brent.rowsell at windriver.com Chris Friesen (Chris.Friesen at windriver.com) Dean Troyer dtroyer at gmail.com John Kung john.kung at windriver.com Saul Wold sgw at linux.intel.com stx-distcloud-client - Distributed Cloud Bart Wensley (Barton.Wensley at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) John Kung (John.Kung at windriver.com ) stx-manifest - source manifest to manage the repositories Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) stx-root - build source tree root Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) stx-tis-repo - build support Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) stx-tools - build tools Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Mon Nov 5 20:07:26 2018 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 5 Nov 2018 12:07:26 -0800 Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F35DB6397@SHSMSX104.ccr.corp.intel.com> References: <3868FDB4-49FA-4429-8657-7C4FBD0D93C1@gmail.com> <2FD5DDB5A04D264C80D42CA35194914F35DB6397@SHSMSX104.ccr.corp.intel.com> Message-ID: I agree with this, I also think I should be added to stx-root, stx-tools, stx-manifest and stx-tis-repo as part of the build. Thanks Sau! On 11/4/18 10:24 PM, Xie, Cindy wrote: > For stx-integ, this repo was used for non-openstack distro sub-project a lot. I am hoping that both Saul and Brent can be the core reviewers for it. > > stx-integ - Integration and packaging > Scott Little (scott.little at windriver.com) > Bob Church (Robert.Church at windriver.com) > Don Penney (Don.Penney at windriver.com ) > Wold, Saul > Rowsell, Brent > > Thx. - cindy > > -----Original Message----- > From: Smith, Tyler [mailto:tyler.smith at windriver.com] > Sent: Friday, November 2, 2018 11:20 AM > To: Ildiko Vancsa ; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED > > OK for stx-gui > > Thanks, > Tyler > > -----Original Message----- > From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] > Sent: Friday, November 2, 2018 1:37 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED > > Hi Technical Leads, > > I started to work on creating the core reviewer groups in Gerrit for each of the sub-projects in StarlingX and I need your input to complete this task. > > I have an initial list below containing the sub-project repos and the names of the core reviewers belonging to the groups. Please check your sub-project and respond with corrections or with an ‘OK’ in case the core team for your project is listed correctly. > > Please let me know if you have any questions. > > Thanks and Best Regards, > Ildikó > > > stx-clients - client libraries > Jerry Sun (Jerry.Sun at windriver.com) > Greg Waines (Greg.Waines at windriver.com) > > stx-config - Configuration Management > Bart Wensley (Barton.Wensley at windriver.com) > John Kung (John.Kung at windriver.com) > Don Penney (Don.Penney at windriver.com) > Bob Church (Robert.Church at windriver.com) > Chris Friesen (Chris.Friesen at windriver.com) > > stx-fault - Fault Management > Tao Liu (Tao.Liu at windriver.com) > Al Bailey (Al.Bailey at windriver.com) > > stx-integ - Integration and packaging > Scott Little (scott.little at windriver.com) > Bob Church (Robert.Church at windriver.com) > Don Penney (Don.Penney at windriver.com ) > > stx-gui - Horizon plugins for new services > Tyler Smith (Tyler.Smith at windriver.com) > Angie Wang (Angie.Wang at windriver.com) > Kristine Bujold (Kristine.Bujold at windriver.com) > > stx-ha - High Availability/Service Management > Bin Qian (Bin.Qian at windriver.com) > Eric Macdonald (Eric.MacDonald at windriver.com) > John Kung (John.Kung at windriver.com) > > stx-metal - Bare Metal Management > Eric Macdonald (Eric.MacDonald at windriver.com) > John Kung (John.Kung at windriver.com) > Tao Liu (Tao.Liu at windriver.com) > > stx-nfv - NFVI Orchestration > Bart Wensley (Barton.Wensley at windriver.com) > Al Bailey (Al.Bailey at windriver.com) > Jack Ding (Jack.Ding at windriver.com) > > stx-update - Installation/Update/Patching > Bart Wensley (Barton.Wensley at windriver.com) > Don Penney (Don.Penney at windriver.com) > David Sullivan (David.Sullivan at windriver.com) > > stx-upstream - Upstream packages > Bob Church (Robert.Church at windriver.com) > Al Bailey (Al.Bailey at windriver.com) > Chris Friesen (Chris.Friesen at windriver.com) > > stx-distcloud – Distributed Cloud > Bart Wensley (Barton.Wensley at windriver.com) > Brent Rowsell brent.rowsell at windriver.com > Chris Friesen (Chris.Friesen at windriver.com) > Dean Troyer dtroyer at gmail.com > John Kung john.kung at windriver.com > Saul Wold sgw at linux.intel.com > > stx-distcloud-client – Distributed Cloud > Bart Wensley (Barton.Wensley at windriver.com) > Chris Friesen (Chris.Friesen at windriver.com) > John Kung (John.Kung at windriver.com ) > > stx-manifest - source manifest to manage the repositories > Scott Little (scott.little at windriver.com) > Jason McKenna (Jason.McKenna at windriver.com) > > stx-root - build source tree root > Scott Little (scott.little at windriver.com) > Jason McKenna (Jason.McKenna at windriver.com) > > stx-tis-repo - build support > Scott Little (scott.little at windriver.com) > Jason McKenna (Jason.McKenna at windriver.com) > > stx-tools - build tools > Scott Little (scott.little at windriver.com) > Jason McKenna (Jason.McKenna at windriver.com) > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From doantungbk.203 at gmail.com Mon Nov 5 20:21:06 2018 From: doantungbk.203 at gmail.com (Tung Doan) Date: Mon, 5 Nov 2018 21:21:06 +0100 Subject: [Starlingx-discuss] Propose OpenStack/Apmec to StarlingX like an upstream component In-Reply-To: References: Message-ID: Hi Dean, Thank you for your attention to this integration. I just gave you the feedbacks. Please see inline. Vào Th 5, 1 thg 11, 2018 vào lúc 18:16 Dean Troyer đã viết: > On Thu, Nov 1, 2018 at 7:44 AM Tung Doan wrote: > > I am Tung Doan - An OpenStack contributor and the PTL of OpenStack/Apmec > project. Since we acknowledged the potential integration between Apmec and > StarlingX, I am writing this email to propose adding OpenStack/Apmec to > StarlingX like an upstream project. > > > > Project description: OpenStack Apmec [1] stands for the Automated > Provisioning Framework for Multi-access Edge Computing which is the first > orchestration and management framework dedicated to the MEC services in > OpenStack. Below are some of the outstanding features of Apmec project: > > I believe Apmec is not an official OpenStack project (as listed in > [0]), do you have plans to apply to become an official OpenStack > project under TC governance? (Until then you do need to be careful > about referring to Apmec as 'an OpenStack project', it is hosted by > OpenStack, but is not (yet?) an OpenStack project.) > Apmec is not official OpenStack but we planned to aplly to make it become the official project as stated in [1]. > - no need to take care of the NFV functionalities. Since existing NFV > MANO frameworks (Tacker, ONAP, OSM, OpenBaton,...) are diverse, integrating > them can make StarlingX complicated. Apmec was designed to take over > responsibility for integrating them since the delivery of MEC services is > our critical mission. > > Is this replacing existing StarlingX functionality? > Our desire is to make Apmec become a "bridge" that helps StarlingX to cooperate with different NFV MANO frameworks. Instead of managing various APIs from the diffirent NFV MANO frameworks, StarlingX can offload them to Apmec. > > > - no need to take care of the life-cycle management of the MEC > applications. Apmec offers API to help StarlingX perform this function. As > mentioned earlier, Apmec is OpenStack project, therefore, to provide > low-latency for MEC applications, Apmec is also planned to support > acceleration technologies (e.g, integrated with OpenStack Cyborg) such as > DPDK and FPGA. > > Can you get more specific about what the integration with StarlingX looks > like? > Since Apmec is OpenStack repo, it has good chances to leverage different OpenStack projects. When integrated with Starling, Apmec provides APIs that help Starling manage the MEC applications which could be supported many acceleration technologies. StarlingX does not need to take care of low-layer design for such features. StarlingX only needs to describe the requirements for the applications (Apmec provides tool to describe them [2]), the rest will be taken care by Apmec. > dt > > [0] https://governance.openstack.org/tc/reference/projects/index.html > > -- > > Dean Troyer > dtroyer at gmail.com > [1] https://review.openstack.org/#/c/612962/ [2] https://review.openstack.org/#/c/570797/ -- Name: Doan Van Tung Email: van_tung.doan at mailbox.tu-dresden.de A member of 5G Lab Germany *Deutsche Telekom Chair of Communication Networks (ComNets)* *Würzburger Str. 35, 01187 Dresden* *TU Dresden, Germany* -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jason.McKenna at windriver.com Mon Nov 5 20:31:41 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Mon, 5 Nov 2018 20:31:41 +0000 Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED In-Reply-To: References: <3868FDB4-49FA-4429-8657-7C4FBD0D93C1@gmail.com> <2FD5DDB5A04D264C80D42CA35194914F35DB6397@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi Cindy, I think I should be added to stx-integ as well. Thanks in advance, -Jason > -----Original Message----- > From: Saul Wold > Sent: November 5, 2018 3:07 PM > To: Xie, Cindy ; Ildiko Vancsa > ; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - > ACTION NEEDED > > > I agree with this, I also think I should be added to stx-root, stx-tools, stx- > manifest and stx-tis-repo as part of the build. > > Thanks > > Sau! > > > On 11/4/18 10:24 PM, Xie, Cindy wrote: > > For stx-integ, this repo was used for non-openstack distro sub-project a lot. > I am hoping that both Saul and Brent can be the core reviewers for it. > > > > stx-integ - Integration and packaging > > Scott Little (scott.little at windriver.com) > > Bob Church (Robert.Church at windriver.com) > > Don Penney (Don.Penney at windriver.com ) > > Wold, Saul > > Rowsell, Brent > > > > Thx. - cindy > > > > -----Original Message----- > > From: Smith, Tyler [mailto:tyler.smith at windriver.com] > > Sent: Friday, November 2, 2018 11:20 AM > > To: Ildiko Vancsa ; > > starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] TLs to sign off on initial core > > reviewer groups - ACTION NEEDED > > > > OK for stx-gui > > > > Thanks, > > Tyler > > > > -----Original Message----- > > From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] > > Sent: Friday, November 2, 2018 1:37 PM > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer > > groups - ACTION NEEDED > > > > Hi Technical Leads, > > > > I started to work on creating the core reviewer groups in Gerrit for each of > the sub-projects in StarlingX and I need your input to complete this task. > > > > I have an initial list below containing the sub-project repos and the names > of the core reviewers belonging to the groups. Please check your sub-project > and respond with corrections or with an ‘OK’ in case the core team for your > project is listed correctly. > > > > Please let me know if you have any questions. > > > > Thanks and Best Regards, > > Ildikó > > > > > > stx-clients - client libraries > > Jerry Sun (Jerry.Sun at windriver.com) > > Greg Waines (Greg.Waines at windriver.com) > > > > stx-config - Configuration Management > > Bart Wensley (Barton.Wensley at windriver.com) > > John Kung (John.Kung at windriver.com) > > Don Penney (Don.Penney at windriver.com) > > Bob Church (Robert.Church at windriver.com) > > Chris Friesen (Chris.Friesen at windriver.com) > > > > stx-fault - Fault Management > > Tao Liu (Tao.Liu at windriver.com) > > Al Bailey (Al.Bailey at windriver.com) > > > > stx-integ - Integration and packaging > > Scott Little (scott.little at windriver.com) > > Bob Church (Robert.Church at windriver.com) > > Don Penney (Don.Penney at windriver.com ) > > > > stx-gui - Horizon plugins for new services > > Tyler Smith (Tyler.Smith at windriver.com) > > Angie Wang (Angie.Wang at windriver.com) > > Kristine Bujold (Kristine.Bujold at windriver.com) > > > > stx-ha - High Availability/Service Management > > Bin Qian (Bin.Qian at windriver.com) > > Eric Macdonald (Eric.MacDonald at windriver.com) > > John Kung (John.Kung at windriver.com) > > > > stx-metal - Bare Metal Management > > Eric Macdonald (Eric.MacDonald at windriver.com) > > John Kung (John.Kung at windriver.com) > > Tao Liu (Tao.Liu at windriver.com) > > > > stx-nfv - NFVI Orchestration > > Bart Wensley (Barton.Wensley at windriver.com) > > Al Bailey (Al.Bailey at windriver.com) > > Jack Ding (Jack.Ding at windriver.com) > > > > stx-update - Installation/Update/Patching > > Bart Wensley (Barton.Wensley at windriver.com) > > Don Penney (Don.Penney at windriver.com) > > David Sullivan (David.Sullivan at windriver.com) > > > > stx-upstream - Upstream packages > > Bob Church (Robert.Church at windriver.com) > > Al Bailey (Al.Bailey at windriver.com) > > Chris Friesen (Chris.Friesen at windriver.com) > > > > stx-distcloud – Distributed Cloud > > Bart Wensley (Barton.Wensley at windriver.com) > > Brent Rowsell brent.rowsell at windriver.com > > Chris Friesen (Chris.Friesen at windriver.com) > > Dean Troyer dtroyer at gmail.com > > John Kung john.kung at windriver.com > > Saul Wold sgw at linux.intel.com > > > > stx-distcloud-client – Distributed Cloud > > Bart Wensley (Barton.Wensley at windriver.com) > > Chris Friesen (Chris.Friesen at windriver.com) > > John Kung (John.Kung at windriver.com ) > > > > stx-manifest - source manifest to manage the repositories > > Scott Little (scott.little at windriver.com) > > Jason McKenna (Jason.McKenna at windriver.com) > > > > stx-root - build source tree root > > Scott Little (scott.little at windriver.com) > > Jason McKenna (Jason.McKenna at windriver.com) > > > > stx-tis-repo - build support > > Scott Little (scott.little at windriver.com) > > Jason McKenna (Jason.McKenna at windriver.com) > > > > stx-tools - build tools > > Scott Little (scott.little at windriver.com) > > Jason McKenna (Jason.McKenna at windriver.com) > > > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ken.Young at windriver.com Mon Nov 5 20:42:50 2018 From: Ken.Young at windriver.com (Young, Ken) Date: Mon, 5 Nov 2018 20:42:50 +0000 Subject: [Starlingx-discuss] [build][meetings] Meeting minutes 11/1/2018 Message-ID: Cesar, A quick update on the mirror. The tooling to enable the mirror was merged on Friday. The Wind River used the mirror over the week-end for its builds with no issues. How have your builds gone since Friday? /KenY From: "Lara, Cesar" Date: Thursday, November 1, 2018 at 6:58 PM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] [build][meetings] Meeting minutes 11/1/2018 Build team meeting minutes 11/1/2018 Attendees Ken, Jason, Scott, Memo, Erich, Marcela, Victor, Chuy, Cesar, Luis Cengn Status -Mirror is now completed and operational, the wiki has been updated with the details for Cengn and our partnership, the details and specs are already there. -The scripts that are related with mirror download are now pointing to Cengn repos and are waiting in the queue to be reviewed tested and merged, the desired date for fully operational mirror is November 5th - Now changes to the packages required to build will be caught by Cengn mirror within one day, the scripts will try to download first from Cengn and if is still not available will try to go get the packages from upstream. Koji follow up -presentation on a possible scenario hosting Koji and demo on using Koji based built packages with our current build scripts. -discussion followed up by implementation details led to different points of view about the problem we have to solve if there’s any, the amount of effort to integrate tooling as we know Koji doesn’t solve every use case by itself and where to host a Koji service(we are striving to host a centralized service for the whole community). -The statement we are using to follow thru with Koji versus our current script is that we will require a lot of effort to support multi OS with the current tools. We had to defer the topic of mirror script refactored using Python. We will start a thread on the goals this team has for next release on the mailing list. Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tao.Liu at windriver.com Mon Nov 5 20:45:19 2018 From: Tao.Liu at windriver.com (Liu, Tao) Date: Mon, 5 Nov 2018 20:45:19 +0000 Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED Message-ID: <7242A3DC72E453498E3D783BBB134C3E9DD92C2A@ALA-MBD.corp.ad.wrs.com> OK for stx-fault and stx-metal. Regards, Tao -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: November 2, 2018 1:37 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED Hi Technical Leads, I started to work on creating the core reviewer groups in Gerrit for each of the sub-projects in StarlingX and I need your input to complete this task. I have an initial list below containing the sub-project repos and the names of the core reviewers belonging to the groups. Please check your sub-project and respond with corrections or with an 'OK' in case the core team for your project is listed correctly. Please let me know if you have any questions. Thanks and Best Regards, Ildikó stx-clients - client libraries Jerry Sun (Jerry.Sun at windriver.com) Greg Waines (Greg.Waines at windriver.com) stx-config - Configuration Management Bart Wensley (Barton.Wensley at windriver.com) John Kung (John.Kung at windriver.com) Don Penney (Don.Penney at windriver.com) Bob Church (Robert.Church at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) stx-fault - Fault Management Tao Liu (Tao.Liu at windriver.com) Al Bailey (Al.Bailey at windriver.com) stx-integ - Integration and packaging Scott Little (scott.little at windriver.com) Bob Church (Robert.Church at windriver.com) Don Penney (Don.Penney at windriver.com ) stx-gui - Horizon plugins for new services Tyler Smith (Tyler.Smith at windriver.com) Angie Wang (Angie.Wang at windriver.com) Kristine Bujold (Kristine.Bujold at windriver.com) stx-ha - High Availability/Service Management Bin Qian (Bin.Qian at windriver.com) Eric Macdonald (Eric.MacDonald at windriver.com) John Kung (John.Kung at windriver.com) stx-metal - Bare Metal Management Eric Macdonald (Eric.MacDonald at windriver.com) John Kung (John.Kung at windriver.com) Tao Liu (Tao.Liu at windriver.com) stx-nfv - NFVI Orchestration Bart Wensley (Barton.Wensley at windriver.com) Al Bailey (Al.Bailey at windriver.com) Jack Ding (Jack.Ding at windriver.com) stx-update - Installation/Update/Patching Bart Wensley (Barton.Wensley at windriver.com) Don Penney (Don.Penney at windriver.com) David Sullivan (David.Sullivan at windriver.com) stx-upstream - Upstream packages Bob Church (Robert.Church at windriver.com) Al Bailey (Al.Bailey at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) stx-distcloud - Distributed Cloud Bart Wensley (Barton.Wensley at windriver.com) Brent Rowsell brent.rowsell at windriver.com Chris Friesen (Chris.Friesen at windriver.com) Dean Troyer dtroyer at gmail.com John Kung john.kung at windriver.com Saul Wold sgw at linux.intel.com stx-distcloud-client - Distributed Cloud Bart Wensley (Barton.Wensley at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) John Kung (John.Kung at windriver.com ) stx-manifest - source manifest to manage the repositories Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) stx-root - build source tree root Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) stx-tis-repo - build support Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) stx-tools - build tools Scott Little (scott.little at windriver.com) Jason McKenna (Jason.McKenna at windriver.com) -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 2 Date: Mon, 5 Nov 2018 12:07:26 -0800 From: Saul Wold To: "Xie, Cindy" , Ildiko Vancsa , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED Message-ID: Content-Type: text/plain; charset=utf-8; format=flowed I agree with this, I also think I should be added to stx-root, stx-tools, stx-manifest and stx-tis-repo as part of the build. Thanks Sau! On 11/4/18 10:24 PM, Xie, Cindy wrote: > For stx-integ, this repo was used for non-openstack distro sub-project a lot. I am hoping that both Saul and Brent can be the core reviewers for it. > > stx-integ - Integration and packaging > Scott Little (scott.little at windriver.com) > Bob Church (Robert.Church at windriver.com) > Don Penney (Don.Penney at windriver.com ) > Wold, Saul > Rowsell, Brent > > Thx. - cindy > > -----Original Message----- > From: Smith, Tyler [mailto:tyler.smith at windriver.com] > Sent: Friday, November 2, 2018 11:20 AM > To: Ildiko Vancsa ; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED > > OK for stx-gui > > Thanks, > Tyler > > -----Original Message----- > From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] > Sent: Friday, November 2, 2018 1:37 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED > > Hi Technical Leads, > > I started to work on creating the core reviewer groups in Gerrit for each of the sub-projects in StarlingX and I need your input to complete this task. > > I have an initial list below containing the sub-project repos and the names of the core reviewers belonging to the groups. Please check your sub-project and respond with corrections or with an ‘OK’ in case the core team for your project is listed correctly. > > Please let me know if you have any questions. > > Thanks and Best Regards, > Ildikó > > > stx-clients - client libraries > Jerry Sun (Jerry.Sun at windriver.com) > Greg Waines (Greg.Waines at windriver.com) > > stx-config - Configuration Management > Bart Wensley (Barton.Wensley at windriver.com) > John Kung (John.Kung at windriver.com) > Don Penney (Don.Penney at windriver.com) > Bob Church (Robert.Church at windriver.com) > Chris Friesen (Chris.Friesen at windriver.com) > > stx-fault - Fault Management > Tao Liu (Tao.Liu at windriver.com) > Al Bailey (Al.Bailey at windriver.com) > > stx-integ - Integration and packaging > Scott Little (scott.little at windriver.com) > Bob Church (Robert.Church at windriver.com) > Don Penney (Don.Penney at windriver.com ) > > stx-gui - Horizon plugins for new services > Tyler Smith (Tyler.Smith at windriver.com) > Angie Wang (Angie.Wang at windriver.com) > Kristine Bujold (Kristine.Bujold at windriver.com) > > stx-ha - High Availability/Service Management > Bin Qian (Bin.Qian at windriver.com) > Eric Macdonald (Eric.MacDonald at windriver.com) > John Kung (John.Kung at windriver.com) > > stx-metal - Bare Metal Management > Eric Macdonald (Eric.MacDonald at windriver.com) > John Kung (John.Kung at windriver.com) > Tao Liu (Tao.Liu at windriver.com) > > stx-nfv - NFVI Orchestration > Bart Wensley (Barton.Wensley at windriver.com) > Al Bailey (Al.Bailey at windriver.com) > Jack Ding (Jack.Ding at windriver.com) > > stx-update - Installation/Update/Patching > Bart Wensley (Barton.Wensley at windriver.com) > Don Penney (Don.Penney at windriver.com) > David Sullivan (David.Sullivan at windriver.com) > > stx-upstream - Upstream packages > Bob Church (Robert.Church at windriver.com) > Al Bailey (Al.Bailey at windriver.com) > Chris Friesen (Chris.Friesen at windriver.com) > > stx-distcloud – Distributed Cloud > Bart Wensley (Barton.Wensley at windriver.com) > Brent Rowsell brent.rowsell at windriver.com > Chris Friesen (Chris.Friesen at windriver.com) > Dean Troyer dtroyer at gmail.com > John Kung john.kung at windriver.com > Saul Wold sgw at linux.intel.com > > stx-distcloud-client – Distributed Cloud > Bart Wensley (Barton.Wensley at windriver.com) > Chris Friesen (Chris.Friesen at windriver.com) > John Kung (John.Kung at windriver.com ) > > stx-manifest - source manifest to manage the repositories > Scott Little (scott.little at windriver.com) > Jason McKenna (Jason.McKenna at windriver.com) > > stx-root - build source tree root > Scott Little (scott.little at windriver.com) > Jason McKenna (Jason.McKenna at windriver.com) > > stx-tis-repo - build support > Scott Little (scott.little at windriver.com) > Jason McKenna (Jason.McKenna at windriver.com) > > stx-tools - build tools > Scott Little (scott.little at windriver.com) > Jason McKenna (Jason.McKenna at windriver.com) > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > ------------------------------ Message: 3 Date: Mon, 5 Nov 2018 21:21:06 +0100 From: Tung Doan To: dtroyer at gmail.com Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Propose OpenStack/Apmec to StarlingX like an upstream component Message-ID: Content-Type: text/plain; charset="utf-8" Hi Dean, Thank you for your attention to this integration. I just gave you the feedbacks. Please see inline. Vào Th 5, 1 thg 11, 2018 vào lúc 18:16 Dean Troyer đã viết: > On Thu, Nov 1, 2018 at 7:44 AM Tung Doan wrote: > > I am Tung Doan - An OpenStack contributor and the PTL of OpenStack/Apmec > project. Since we acknowledged the potential integration between Apmec and > StarlingX, I am writing this email to propose adding OpenStack/Apmec to > StarlingX like an upstream project. > > > > Project description: OpenStack Apmec [1] stands for the Automated > Provisioning Framework for Multi-access Edge Computing which is the first > orchestration and management framework dedicated to the MEC services in > OpenStack. Below are some of the outstanding features of Apmec project: > > I believe Apmec is not an official OpenStack project (as listed in > [0]), do you have plans to apply to become an official OpenStack > project under TC governance? (Until then you do need to be careful > about referring to Apmec as 'an OpenStack project', it is hosted by > OpenStack, but is not (yet?) an OpenStack project.) > Apmec is not official OpenStack but we planned to aplly to make it become the official project as stated in [1]. > - no need to take care of the NFV functionalities. Since existing NFV > MANO frameworks (Tacker, ONAP, OSM, OpenBaton,...) are diverse, integrating > them can make StarlingX complicated. Apmec was designed to take over > responsibility for integrating them since the delivery of MEC services is > our critical mission. > > Is this replacing existing StarlingX functionality? > Our desire is to make Apmec become a "bridge" that helps StarlingX to cooperate with different NFV MANO frameworks. Instead of managing various APIs from the diffirent NFV MANO frameworks, StarlingX can offload them to Apmec. > > > - no need to take care of the life-cycle management of the MEC > applications. Apmec offers API to help StarlingX perform this function. As > mentioned earlier, Apmec is OpenStack project, therefore, to provide > low-latency for MEC applications, Apmec is also planned to support > acceleration technologies (e.g, integrated with OpenStack Cyborg) such as > DPDK and FPGA. > > Can you get more specific about what the integration with StarlingX looks > like? > Since Apmec is OpenStack repo, it has good chances to leverage different OpenStack projects. When integrated with Starling, Apmec provides APIs that help Starling manage the MEC applications which could be supported many acceleration technologies. StarlingX does not need to take care of low-layer design for such features. StarlingX only needs to describe the requirements for the applications (Apmec provides tool to describe them [2]), the rest will be taken care by Apmec. > dt > > [0] https://governance.openstack.org/tc/reference/projects/index.html > > -- > > Dean Troyer > dtroyer at gmail.com > [1] https://review.openstack.org/#/c/612962/ [2] https://review.openstack.org/#/c/570797/ -- Name: Doan Van Tung Email: van_tung.doan at mailbox.tu-dresden.de A member of 5G Lab Germany *Deutsche Telekom Chair of Communication Networks (ComNets)* *Würzburger Str. 35, 01187 Dresden* *TU Dresden, Germany* -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 6, Issue 15 ************************************************ From dtroyer at gmail.com Mon Nov 5 20:52:35 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Mon, 5 Nov 2018 14:52:35 -0600 Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED In-Reply-To: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA2C0CC@ALA-MBD.corp.ad.wrs.com> References: <3868FDB4-49FA-4429-8657-7C4FBD0D93C1@gmail.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA2C0CC@ALA-MBD.corp.ad.wrs.com> Message-ID: On Mon, Nov 5, 2018 at 10:11 AM Wensley, Barton wrote: > Both stx-nfv and stx-update look good. I think stx-distcloud should probably just be: > > stx-distcloud – Distributed Cloud > Bart Wensley (Barton.Wensley at windriver.com) > Chris Friesen (Chris.Friesen at windriver.com) > John Kung john.kung at windriver.com Done. > I'm not sure why the TSC members (Brent, Dean and Saul) were listed as cores for this one project - there isn't anything special about it that would require them as core reviewers. This is left over from when those repos were created a few months ago. That also means Ildiko wasn't in the group and could not make the change so I did. dt -- Dean Troyer dtroyer at gmail.com From scott.little at windriver.com Mon Nov 5 22:01:02 2018 From: scott.little at windriver.com (Scott Little) Date: Mon, 5 Nov 2018 17:01:02 -0500 Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED In-Reply-To: References: <3868FDB4-49FA-4429-8657-7C4FBD0D93C1@gmail.com> <2FD5DDB5A04D264C80D42CA35194914F35DB6397@SHSMSX104.ccr.corp.intel.com> Message-ID: Strange,  I used to have +2 powers over stx-upstream a few days ago.  Now it seems to be gone. Please restore. Thanks Scott On 18-11-05 03:31 PM, McKenna, Jason wrote: > Hi Cindy, > > I think I should be added to stx-integ as well. > > Thanks in advance, > -Jason > >> -----Original Message----- >> From: Saul Wold >> Sent: November 5, 2018 3:07 PM >> To: Xie, Cindy ; Ildiko Vancsa >> ; starlingx-discuss at lists.starlingx.io >> Subject: Re: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - >> ACTION NEEDED >> >> >> I agree with this, I also think I should be added to stx-root, stx-tools, stx- >> manifest and stx-tis-repo as part of the build. >> >> Thanks >> >> Sau! >> >> >> On 11/4/18 10:24 PM, Xie, Cindy wrote: >>> For stx-integ, this repo was used for non-openstack distro sub-project a lot. >> I am hoping that both Saul and Brent can be the core reviewers for it. >>> stx-integ - Integration and packaging >>> Scott Little (scott.little at windriver.com) >>> Bob Church (Robert.Church at windriver.com) >>> Don Penney (Don.Penney at windriver.com ) >>> Wold, Saul >>> Rowsell, Brent >>> >>> Thx. - cindy >>> >>> -----Original Message----- >>> From: Smith, Tyler [mailto:tyler.smith at windriver.com] >>> Sent: Friday, November 2, 2018 11:20 AM >>> To: Ildiko Vancsa ; >>> starlingx-discuss at lists.starlingx.io >>> Subject: Re: [Starlingx-discuss] TLs to sign off on initial core >>> reviewer groups - ACTION NEEDED >>> >>> OK for stx-gui >>> >>> Thanks, >>> Tyler >>> >>> -----Original Message----- >>> From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] >>> Sent: Friday, November 2, 2018 1:37 PM >>> To: starlingx-discuss at lists.starlingx.io >>> Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer >>> groups - ACTION NEEDED >>> >>> Hi Technical Leads, >>> >>> I started to work on creating the core reviewer groups in Gerrit for each of >> the sub-projects in StarlingX and I need your input to complete this task. >>> I have an initial list below containing the sub-project repos and the names >> of the core reviewers belonging to the groups. Please check your sub-project >> and respond with corrections or with an ‘OK’ in case the core team for your >> project is listed correctly. >>> Please let me know if you have any questions. >>> >>> Thanks and Best Regards, >>> Ildikó >>> >>> >>> stx-clients - client libraries >>> Jerry Sun (Jerry.Sun at windriver.com) >>> Greg Waines (Greg.Waines at windriver.com) >>> >>> stx-config - Configuration Management >>> Bart Wensley (Barton.Wensley at windriver.com) >>> John Kung (John.Kung at windriver.com) >>> Don Penney (Don.Penney at windriver.com) >>> Bob Church (Robert.Church at windriver.com) >>> Chris Friesen (Chris.Friesen at windriver.com) >>> >>> stx-fault - Fault Management >>> Tao Liu (Tao.Liu at windriver.com) >>> Al Bailey (Al.Bailey at windriver.com) >>> >>> stx-integ - Integration and packaging >>> Scott Little (scott.little at windriver.com) >>> Bob Church (Robert.Church at windriver.com) >>> Don Penney (Don.Penney at windriver.com ) >>> >>> stx-gui - Horizon plugins for new services >>> Tyler Smith (Tyler.Smith at windriver.com) >>> Angie Wang (Angie.Wang at windriver.com) >>> Kristine Bujold (Kristine.Bujold at windriver.com) >>> >>> stx-ha - High Availability/Service Management >>> Bin Qian (Bin.Qian at windriver.com) >>> Eric Macdonald (Eric.MacDonald at windriver.com) >>> John Kung (John.Kung at windriver.com)TLs to sign off on initial core reviewer groups >>> >>> stx-metal - Bare Metal Management >>> Eric Macdonald (Eric.MacDonald at windriver.com) >>> John Kung (John.Kung at windriver.com) >>> Tao Liu (Tao.Liu at windriver.com) >>> >>> stx-nfv - NFVI Orchestration >>> Bart Wensley (Barton.Wensley at windriver.com) >>> Al Bailey (Al.Bailey at windriver.com) >>> Jack Ding (Jack.Ding at windriver.com) >>> >>> stx-update - Installation/Update/Patching >>> Bart Wensley (Barton.Wensley at windriver.com) >>> Don Penney (Don.Penney at windriver.com) >>> David Sullivan (David.Sullivan at windriver.com) >>> >>> stx-upstream - Upstream packages >>> Bob Church (Robert.Church at windriver.com) >>> Al Bailey (Al.Bailey at windriver.com) >>> Chris Friesen (Chris.Friesen at windriver.com) >>> >>> stx-distcloud – Distributed Cloud >>> Bart Wensley (Barton.Wensley at windriver.com) >>> Brent Rowsell brent.rowsell at windriver.com >>> Chris Friesen (Chris.Friesen at windriver.com) >>> Dean Troyer dtroyer at gmail.com >>> John Kung john.kung at windriver.com >>> Saul Wold sgw at linux.intel.com >>> >>> stx-distcloud-client – Distributed Cloud >>> Bart Wensley (Barton.Wensley at windriver.com) >>> Chris Friesen (Chris.Friesen at windriver.com) >>> John Kung (John.Kung at windriver.com ) >>> >>> stx-manifest - source manifest to manage the repositories >>> Scott Little (scott.little at windriver.com) >>> Jason McKenna (Jason.McKenna at windriver.com) >>> >>> stx-root - build source tree root >>> Scott Little (scott.little at windriver.com) >>> Jason McKenna (Jason.McKenna at windriver.com) >>> >>> stx-tis-repo - build support >>> Scott Little (scott.little at windriver.com) >>> Jason McKenna (Jason.McKenna at windriver.com) >>> >>> stx-tools - build tools >>> Scott Little (scott.little at windriver.com) >>> Jason McKenna (Jason.McKenna at windriver.com) >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From chris.friesen at windriver.com Mon Nov 5 22:18:03 2018 From: chris.friesen at windriver.com (Chris Friesen) Date: Mon, 5 Nov 2018 16:18:03 -0600 Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED In-Reply-To: <3868FDB4-49FA-4429-8657-7C4FBD0D93C1@gmail.com> References: <3868FDB4-49FA-4429-8657-7C4FBD0D93C1@gmail.com> Message-ID: <64fae22c-af1d-f002-f908-8774b2bb1cce@windriver.com> On 11/2/2018 11:36 AM, Ildiko Vancsa wrote: > Hi Technical Leads, > > I started to work on creating the core reviewer groups in Gerrit for each of the sub-projects in StarlingX and I need your input to complete this task. > > I have an initial list below containing the sub-project repos and the names of the core reviewers belonging to the groups. Please check your sub-project and respond with corrections or with an ‘OK’ in case the core team for your project is listed correctly. > > Please let me know if you have any questions. > stx-config - Configuration Management > Bart Wensley (Barton.Wensley at windriver.com) > John Kung (John.Kung at windriver.com) > Don Penney (Don.Penney at windriver.com) > Bob Church (Robert.Church at windriver.com) > Chris Friesen (Chris.Friesen at windriver.com) I seem to have lost my core reviewer status in stx-config. Could you please fix this? Thanks, Chris From dtroyer at gmail.com Mon Nov 5 22:31:40 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Mon, 5 Nov 2018 16:31:40 -0600 Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED In-Reply-To: References: <3868FDB4-49FA-4429-8657-7C4FBD0D93C1@gmail.com> <2FD5DDB5A04D264C80D42CA35194914F35DB6397@SHSMSX104.ccr.corp.intel.com> Message-ID: On Mon, Nov 5, 2018 at 4:01 PM Scott Little wrote: > Strange, I used to have +2 powers over stx-upstream a few days ago. > Now it seems to be gone. Ildiko implemented the individual project core reviewer groups as provided by Brent and amended and approved by the project TLs. > Please restore. All project TLs have control over their list memberships. While it is traditional in OpenStack to discuss core group changes on the mailing list, project TLs have the final decision. dt -- Dean Troyer dtroyer at gmail.com From ildiko.vancsa at gmail.com Mon Nov 5 22:46:20 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Mon, 5 Nov 2018 23:46:20 +0100 Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED In-Reply-To: References: <3868FDB4-49FA-4429-8657-7C4FBD0D93C1@gmail.com> <2FD5DDB5A04D264C80D42CA35194914F35DB6397@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi Scott, I got the following initial list for stx-upstream: stx-upstream - Upstream packages Bob Church (Robert.Church at windriver.com) Al Bailey (Al.Bailey at windriver.com) Chris Friesen (Chris.Friesen at windriver.com) And so far it got confirmed here: http://lists.starlingx.io/pipermail/starlingx-discuss/2018-November/001742.html I’m working with the TLs to double check the lists, however I don’t seem to be able to figure out all the TLs for all the repos at this point, will start a separate thread about that. Thanks, Ildikó > On 2018. Nov 5., at 23:01, Scott Little wrote: > > Strange, I used to have +2 powers over stx-upstream a few days ago. Now it seems to be gone. > > Please restore. > > Thanks > > Scott > > > > On 18-11-05 03:31 PM, McKenna, Jason wrote: >> Hi Cindy, >> >> I think I should be added to stx-integ as well. >> >> Thanks in advance, >> -Jason >> >>> -----Original Message----- >>> From: Saul Wold >>> Sent: November 5, 2018 3:07 PM >>> To: Xie, Cindy ; Ildiko Vancsa >>> ; starlingx-discuss at lists.starlingx.io >>> Subject: Re: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - >>> ACTION NEEDED >>> >>> >>> I agree with this, I also think I should be added to stx-root, stx-tools, stx- >>> manifest and stx-tis-repo as part of the build. >>> >>> Thanks >>> >>> Sau! >>> >>> >>> On 11/4/18 10:24 PM, Xie, Cindy wrote: >>>> For stx-integ, this repo was used for non-openstack distro sub-project a lot. >>> I am hoping that both Saul and Brent can be the core reviewers for it. >>>> stx-integ - Integration and packaging >>>> Scott Little (scott.little at windriver.com) >>>> Bob Church (Robert.Church at windriver.com) >>>> Don Penney (Don.Penney at windriver.com ) >>>> Wold, Saul >>>> Rowsell, Brent >>>> >>>> Thx. - cindy >>>> >>>> -----Original Message----- >>>> From: Smith, Tyler [mailto:tyler.smith at windriver.com] >>>> Sent: Friday, November 2, 2018 11:20 AM >>>> To: Ildiko Vancsa ; >>>> starlingx-discuss at lists.starlingx.io >>>> Subject: Re: [Starlingx-discuss] TLs to sign off on initial core >>>> reviewer groups - ACTION NEEDED >>>> >>>> OK for stx-gui >>>> >>>> Thanks, >>>> Tyler >>>> >>>> -----Original Message----- >>>> From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] >>>> Sent: Friday, November 2, 2018 1:37 PM >>>> To: starlingx-discuss at lists.starlingx.io >>>> Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer >>>> groups - ACTION NEEDED >>>> >>>> Hi Technical Leads, >>>> >>>> I started to work on creating the core reviewer groups in Gerrit for each of >>> the sub-projects in StarlingX and I need your input to complete this task. >>>> I have an initial list below containing the sub-project repos and the names >>> of the core reviewers belonging to the groups. Please check your sub-project >>> and respond with corrections or with an ‘OK’ in case the core team for your >>> project is listed correctly. >>>> Please let me know if you have any questions. >>>> >>>> Thanks and Best Regards, >>>> Ildikó >>>> >>>> >>>> stx-clients - client libraries >>>> Jerry Sun (Jerry.Sun at windriver.com) >>>> Greg Waines (Greg.Waines at windriver.com) >>>> >>>> stx-config - Configuration Management >>>> Bart Wensley (Barton.Wensley at windriver.com) >>>> John Kung (John.Kung at windriver.com) >>>> Don Penney (Don.Penney at windriver.com) >>>> Bob Church (Robert.Church at windriver.com) >>>> Chris Friesen (Chris.Friesen at windriver.com) >>>> >>>> stx-fault - Fault Management >>>> Tao Liu (Tao.Liu at windriver.com) >>>> Al Bailey (Al.Bailey at windriver.com) >>>> >>>> stx-integ - Integration and packaging >>>> Scott Little (scott.little at windriver.com) >>>> Bob Church (Robert.Church at windriver.com) >>>> Don Penney (Don.Penney at windriver.com ) >>>> >>>> stx-gui - Horizon plugins for new services >>>> Tyler Smith (Tyler.Smith at windriver.com) >>>> Angie Wang (Angie.Wang at windriver.com) >>>> Kristine Bujold (Kristine.Bujold at windriver.com) >>>> >>>> stx-ha - High Availability/Service Management >>>> Bin Qian (Bin.Qian at windriver.com) >>>> Eric Macdonald (Eric.MacDonald at windriver.com) >>>> John Kung (John.Kung at windriver.com)TLs to sign off on initial core reviewer groups >>>> >>>> stx-metal - Bare Metal Management >>>> Eric Macdonald (Eric.MacDonald at windriver.com) >>>> John Kung (John.Kung at windriver.com) >>>> Tao Liu (Tao.Liu at windriver.com) >>>> >>>> stx-nfv - NFVI Orchestration >>>> Bart Wensley (Barton.Wensley at windriver.com) >>>> Al Bailey (Al.Bailey at windriver.com) >>>> Jack Ding (Jack.Ding at windriver.com) >>>> >>>> stx-update - Installation/Update/Patching >>>> Bart Wensley (Barton.Wensley at windriver.com) >>>> Don Penney (Don.Penney at windriver.com) >>>> David Sullivan (David.Sullivan at windriver.com) >>>> >>>> stx-upstream - Upstream packages >>>> Bob Church (Robert.Church at windriver.com) >>>> Al Bailey (Al.Bailey at windriver.com) >>>> Chris Friesen (Chris.Friesen at windriver.com) >>>> >>>> stx-distcloud – Distributed Cloud >>>> Bart Wensley (Barton.Wensley at windriver.com) >>>> Brent Rowsell brent.rowsell at windriver.com >>>> Chris Friesen (Chris.Friesen at windriver.com) >>>> Dean Troyer dtroyer at gmail.com >>>> John Kung john.kung at windriver.com >>>> Saul Wold sgw at linux.intel.com >>>> >>>> stx-distcloud-client – Distributed Cloud >>>> Bart Wensley (Barton.Wensley at windriver.com) >>>> Chris Friesen (Chris.Friesen at windriver.com) >>>> John Kung (John.Kung at windriver.com ) >>>> >>>> stx-manifest - source manifest to manage the repositories >>>> Scott Little (scott.little at windriver.com) >>>> Jason McKenna (Jason.McKenna at windriver.com) >>>> >>>> stx-root - build source tree root >>>> Scott Little (scott.little at windriver.com) >>>> Jason McKenna (Jason.McKenna at windriver.com) >>>> >>>> stx-tis-repo - build support >>>> Scott Little (scott.little at windriver.com) >>>> Jason McKenna (Jason.McKenna at windriver.com) >>>> >>>> stx-tools - build tools >>>> Scott Little (scott.little at windriver.com) >>>> Jason McKenna (Jason.McKenna at windriver.com) >>>> >>>> >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ildiko.vancsa at gmail.com Mon Nov 5 22:55:37 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Mon, 5 Nov 2018 23:55:37 +0100 Subject: [Starlingx-discuss] [TLs][PLs][TSC] Sub-project and git repo mapping seems to be incomplete Message-ID: Hi, While I was working on getting the initial core reviewer teams setup in Gerrit I realized that not all repositories seem to be covered by sub-project teams or even if they are it is not documented clearly. Currently we have information about the main project on the docs website under governance: https://docs.starlingx.io/governance/reference/tsc/projects/index.html And we have further information on the wiki about sub-projects: https://wiki.openstack.org/wiki/StarlingX Some repositories such as stx-upstream does not seem to be listed on either of the above links which makes it hard to identify which sub-project team maintains it. I would like to ask the Project and Technical Leads as well as the TSC to please help to look into this and make the mapping a full coverage that is also easily accessible. As we have started to fill up the documentation website with information I would suggest to extend the project list under the governance section that I linked in above. Thanks and Best Regards, Ildikó From liang.a.fang at intel.com Tue Nov 6 01:03:16 2018 From: liang.a.fang at intel.com (Fang, Liang A) Date: Tue, 6 Nov 2018 01:03:16 +0000 Subject: [Starlingx-discuss] glance api service is not started in all-in-one deployment In-Reply-To: References: , Message-ID: Thank you Bin. Regards Liang From: Qian, Bin [mailto:Bin.Qian at windriver.com] Sent: Tuesday, November 6, 2018 3:46 AM To: Fang, Liang A ; Dinescu, Stefan ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] glance api service is not started in all-in-one deployment Hi, Liang Sm has its sqlite database to have all service and related information stored, the db can be found at /var/run/sm/sm.db on a controller. A quick way to list all services is to use smc command. source /etc/nova/openrc smc service-list This command is similar to sm-dump but sm-dump is only for designers to debug/troubleshooting. smc also provides other sub commands to for querying service, servicegroup, and servicenode. Regards, Bin From: Fang, Liang A [liang.a.fang at intel.com] Sent: Saturday, November 03, 2018 12:43 AM To: Dinescu, Stefan; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] glance api service is not started in all-in-one deployment Thanks Stefan. Is there any help doc about SM? Where does SM read the service list and the service exec from? Regards Liang From: Dinescu, Stefan [mailto:Stefan.Dinescu at windriver.com] Sent: Friday, November 2, 2018 6:11 PM To: Fang, Liang A >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] glance api service is not started in all-in-one deployment Hi, On StarlingX, glance-api is managed by SM (short for service management). You can see a list of all the services by using "sm-dump" (from a root prompt or use sudo). If it is working, the sate should be "enabled-active". To restart the service us "sm-restart service glance-api". Also check the logs (/var/log/glance/glance-api.log) for any obvious errors that prevent the service from restarting. ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Friday, November 02, 2018 11:34 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] glance api service is not started in all-in-one deployment Hi I deployed an starlingx all-in-one environment, and it seems glance api service has not been started. I also checked other services such as cinder api / cinder volume, there are started. /bin/sh /usr/lib/ocf/resource.d/openstack/cinder-schedule start /bin/sh /usr/lib/ocf/resource.d/openstack/cinder-volume start /bin/sh /usr/lib/ocf/resource.d/openstack/cinder-backup start But these are not started by service file such as openstack-cinder-api.service / openstack-cinder-scheduler.service. This is really different with the deployment by devstack. Could anybody point out how the services are started? How to restart cinder/glance service in starlingx deployment? Thanks. Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From Rajesh.Jha at rsystems.com Tue Nov 6 07:05:43 2018 From: Rajesh.Jha at rsystems.com (Rajesh Jha) Date: Tue, 6 Nov 2018 12:35:43 +0530 Subject: [Starlingx-discuss] Build failure Message-ID: <2F61A2101B4FD447A683EF7E362CF9421C63E21826@RSI-NOD-EXMDB6.india.rsystems.com> Hi, Please find the build issue, this was after the Ceph updates in starlingX. 06:09:39 Failed to build packages: vm-topology-1.0-1.tis.src.rpm qemu-kvm-ev-2.10.0-0.tis.0.src.rpm python-networking-sfc-5.0.0-1.tis.2.src.rpm python-networking-bgpvpn-7.0.0-0.tis.3.src.rpm openstack-neutron-11.0.0-1.tis.8.src.rpm libvirt-python-4.7.0-1.tis.3.src.rpm libvirt-4.7.0-1.tis.23.src.rpm openvswitch-2.9.0-3.el7.tis.1.src.rpm ######## Tue Nov 6 06:09:39 UTC 2018: build-rpm-parallel --std failed with rc=1 Tue Nov 6 06:09:39 UTC 2018: build-rpm-parallel --std failed with rc=1 Best Regards, Rajesh Jha The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, please immediately alert the sender by reply e-mail and then delete this message. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. R Systems has taken every reasonable precaution to minimize the risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. From kailun.qin at intel.com Tue Nov 6 07:09:48 2018 From: kailun.qin at intel.com (Qin, Kailun) Date: Tue, 6 Nov 2018 07:09:48 +0000 Subject: [Starlingx-discuss] Analysis of patch 039705e for StarlingX upstreaming Message-ID: Hi Matt, We're looking into the patch 039705e for upstreaming, which contains several base changes. 1. For the oslo.db related change, upstream has already dropped this override in neutron-server to make it use default values from oslo.db (see https://review.openstack.org/456419/ for detailed information). 2. For the keystone opts registration, I guess it is used for connecting to external services. From upstream's perspective, this should be maintained along with the specific service to extend rather than make it globally. 3. For the others, I think they're StarlingX specific. Thus, I suggest that we should not upstream these changes. What do you think? Let me know if any question, thanks! BR, Kailun -------------- next part -------------- An HTML attachment was scrubbed... URL: From chenjie.xu at intel.com Tue Nov 6 07:34:52 2018 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Tue, 6 Nov 2018 07:34:52 +0000 Subject: [Starlingx-discuss] Analysis of patch 2e4ca00 for StarlingX Upstreaming Message-ID: Hi Matt, The patch 2e4ca00 changes function get_max_timeout() by changing the multiplication factor of 10 to 1 to avoid wait for 60*10 seconds(The default value for rpc_response_timeout is 60). This can be done by changing the default value from 60 to 6. Then will wait 6*10 seconds. This patch may be just a configuration problem to neutron upstream. Do you think we should upstream this patch or not? Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From liang.a.fang at intel.com Tue Nov 6 08:55:26 2018 From: liang.a.fang at intel.com (Fang, Liang A) Date: Tue, 6 Nov 2018 08:55:26 +0000 Subject: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming Message-ID: Hi Daniel and Ovidiu Repo: cinder Commit: 294a63c821233e3307f142965f366e8eb3d0c1de Title: Pike Rebase: Fix Cinder memory leak This patch is to call novaclient's API "set_timings_max_len", to limit the max timing logs, so that the log list will not be to huge. But novaclient(both the upstream version and stx- version) don't contain the API set_timings_max_len, I also cannot find in repo history. It seems this patch may co-worked with some private version of novaclient previously, but not the public version. In fact current novaclient contains an API "reset_timings" which can be called to purge the timing logs. I want to mark this patch as abandoned, do you have any comments? Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From Allain.Legacy at windriver.com Tue Nov 6 12:15:56 2018 From: Allain.Legacy at windriver.com (Legacy, Allain) Date: Tue, 6 Nov 2018 12:15:56 +0000 Subject: [Starlingx-discuss] Analysis of patch 039705e for StarlingX upstreaming In-Reply-To: References: Message-ID: <70A7408C6E1BFB41B192A929744D8523BAC2F43A@ALA-MBD.corp.ad.wrs.com> I agree. These changes can all be dropped. The keystone config opts change was needed for the host driver to communicate back to our sysinv subsystem, but, as far as I know, that is being redesigned to avoid this requirement. Regards, Allain Allain Legacy, Software Developer, Wind River direct 613.270.2279 fax 613.492.7870 skype allain.legacy 350 Terry Fox Drive, Suite 200, Ottawa, Ontario, K2K 2W5 [WIND] From: Qin, Kailun [mailto:kailun.qin at intel.com] Sent: Tuesday, November 06, 2018 2:10 AM To: Peters, Matt; starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Analysis of patch 039705e for StarlingX upstreaming Hi Matt, We're looking into the patch 039705e for upstreaming, which contains several base changes. 1. For the oslo.db related change, upstream has already dropped this override in neutron-server to make it use default values from oslo.db (see https://review.openstack.org/456419/ for detailed information). 2. For the keystone opts registration, I guess it is used for connecting to external services. From upstream's perspective, this should be maintained along with the specific service to extend rather than make it globally. 3. For the others, I think they're StarlingX specific. Thus, I suggest that we should not upstream these changes. What do you think? Let me know if any question, thanks! BR, Kailun -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1807 bytes Desc: image001.png URL: From Allain.Legacy at windriver.com Tue Nov 6 12:29:36 2018 From: Allain.Legacy at windriver.com (Legacy, Allain) Date: Tue, 6 Nov 2018 12:29:36 +0000 Subject: [Starlingx-discuss] Analysis of patch 2e4ca00 for StarlingX Upstreaming In-Reply-To: References: Message-ID: <70A7408C6E1BFB41B192A929744D8523BAC2F483@ALA-MBD.corp.ad.wrs.com> The issue with changing the configuration value from 60 to 6 is that provides the default value for _METHOD_TIMEOUTS which means now each RPC request will timeout after 6 seconds rather than 60 seconds. In a heavily loaded system that timeout will get hit frequently thus leading to repeated RPC requests and an increased load on the server. We need a way to control the maximum timeout without reducing the timeout of each individual RPC timeout so much as to increase the load on the server. I think it is unlikely that upstream will accept the current change in its current form. Perhaps we need to propose a configuration option that can be controlled via config file but still leaves the default as it is today. Regards, Allain Allain Legacy, Software Developer, Wind River direct 613.270.2279 fax 613.492.7870 skype allain.legacy 350 Terry Fox Drive, Suite 200, Ottawa, Ontario, K2K 2W5 [WIND] From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, November 06, 2018 2:35 AM To: Peters, Matt Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Analysis of patch 2e4ca00 for StarlingX Upstreaming Hi Matt, The patch 2e4ca00 changes function get_max_timeout() by changing the multiplication factor of 10 to 1 to avoid wait for 60*10 seconds(The default value for rpc_response_timeout is 60). This can be done by changing the default value from 60 to 6. Then will wait 6*10 seconds. This patch may be just a configuration problem to neutron upstream. Do you think we should upstream this patch or not? Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1807 bytes Desc: image001.png URL: From Daniel.Badea at windriver.com Tue Nov 6 14:02:47 2018 From: Daniel.Badea at windriver.com (Badea, Daniel) Date: Tue, 6 Nov 2018 14:02:47 +0000 Subject: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming In-Reply-To: References: Message-ID: <9174DAE490321844AE273F6AD001E3EA9D804C36@ALA-MBD.corp.ad.wrs.com> Hi Liang, No objections here, mark this patch as abandoned. Regards, Daniel ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Tuesday, November 06, 2018 10:55 To: Badea, Daniel; Poncea, Ovidiu Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming Hi Daniel and Ovidiu Repo: cinder Commit: 294a63c821233e3307f142965f366e8eb3d0c1de Title: Pike Rebase: Fix Cinder memory leak This patch is to call novaclient’s API “set_timings_max_len”, to limit the max timing logs, so that the log list will not be to huge. But novaclient(both the upstream version and stx- version) don’t contain the API set_timings_max_len, I also cannot find in repo history. It seems this patch may co-worked with some private version of novaclient previously, but not the public version. In fact current novaclient contains an API “reset_timings” which can be called to purge the timing logs. I want to mark this patch as abandoned, do you have any comments? Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From liang.a.fang at intel.com Tue Nov 6 14:17:29 2018 From: liang.a.fang at intel.com (Fang, Liang A) Date: Tue, 6 Nov 2018 14:17:29 +0000 Subject: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming In-Reply-To: <9174DAE490321844AE273F6AD001E3EA9D804C36@ALA-MBD.corp.ad.wrs.com> References: <9174DAE490321844AE273F6AD001E3EA9D804C36@ALA-MBD.corp.ad.wrs.com> Message-ID: Thanks Daniel. Regards Liang From: Badea, Daniel [mailto:Daniel.Badea at windriver.com] Sent: Tuesday, November 6, 2018 10:03 PM To: Fang, Liang A ; Poncea, Ovidiu Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming Hi Liang, No objections here, mark this patch as abandoned. Regards, Daniel ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Tuesday, November 06, 2018 10:55 To: Badea, Daniel; Poncea, Ovidiu Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming Hi Daniel and Ovidiu Repo: cinder Commit: 294a63c821233e3307f142965f366e8eb3d0c1de Title: Pike Rebase: Fix Cinder memory leak This patch is to call novaclient's API "set_timings_max_len", to limit the max timing logs, so that the log list will not be to huge. But novaclient(both the upstream version and stx- version) don't contain the API set_timings_max_len, I also cannot find in repo history. It seems this patch may co-worked with some private version of novaclient previously, but not the public version. In fact current novaclient contains an API "reset_timings" which can be called to purge the timing logs. I want to mark this patch as abandoned, do you have any comments? Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From kailun.qin at intel.com Tue Nov 6 14:38:25 2018 From: kailun.qin at intel.com (Qin, Kailun) Date: Tue, 6 Nov 2018 14:38:25 +0000 Subject: [Starlingx-discuss] Analysis of patch 039705e for StarlingX upstreaming In-Reply-To: <70A7408C6E1BFB41B192A929744D8523BAC2F43A@ALA-MBD.corp.ad.wrs.com> References: <70A7408C6E1BFB41B192A929744D8523BAC2F43A@ALA-MBD.corp.ad.wrs.com> Message-ID: Allain, Thanks a lot for the confirmation and clarification. Yes, the host driver is being redesigned. I'll drop the patch accordingly. BR, Kailun From: Legacy, Allain [mailto:Allain.Legacy at windriver.com] Sent: Tuesday, November 6, 2018 8:16 PM To: Qin, Kailun ; Peters, Matt ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Analysis of patch 039705e for StarlingX upstreaming I agree. These changes can all be dropped. The keystone config opts change was needed for the host driver to communicate back to our sysinv subsystem, but, as far as I know, that is being redesigned to avoid this requirement. Regards, Allain Allain Legacy, Software Developer, Wind River direct 613.270.2279 fax 613.492.7870 skype allain.legacy 350 Terry Fox Drive, Suite 200, Ottawa, Ontario, K2K 2W5 [WIND] From: Qin, Kailun [mailto:kailun.qin at intel.com] Sent: Tuesday, November 06, 2018 2:10 AM To: Peters, Matt; starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Analysis of patch 039705e for StarlingX upstreaming Hi Matt, We're looking into the patch 039705e for upstreaming, which contains several base changes. 1. For the oslo.db related change, upstream has already dropped this override in neutron-server to make it use default values from oslo.db (see https://review.openstack.org/456419/ for detailed information). 2. For the keystone opts registration, I guess it is used for connecting to external services. From upstream's perspective, this should be maintained along with the specific service to extend rather than make it globally. 3. For the others, I think they're StarlingX specific. Thus, I suggest that we should not upstream these changes. What do you think? Let me know if any question, thanks! BR, Kailun -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1807 bytes Desc: image001.png URL: From Jim.Einarsson at windriver.com Tue Nov 6 14:43:47 2018 From: Jim.Einarsson at windriver.com (Einarsson, Jim) Date: Tue, 6 Nov 2018 14:43:47 +0000 Subject: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming Message-ID: <38713B7817E1A049AB469EA7F6EEF69EBBFCA226@ALA-MBD.corp.ad.wrs.com> I don't understand why we would mark this patch "Abandoned". If the code is not required, then it should be deleted and marked as "deleted", no? Regards JimE -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io [mailto:starlingx-discuss-request at lists.starlingx.io] Sent: Tuesday, November 06, 2018 9:39 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 6, Issue 20 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. Re: Analysis of patch 294a63c for StarlingX Upstreaming (Badea, Daniel) 2. Re: Analysis of patch 294a63c for StarlingX Upstreaming (Fang, Liang A) 3. Re: Analysis of patch 039705e for StarlingX upstreaming (Qin, Kailun) ---------------------------------------------------------------------- Message: 1 Date: Tue, 6 Nov 2018 14:02:47 +0000 From: "Badea, Daniel" To: "Fang, Liang A" , "Poncea, Ovidiu" Cc: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming Message-ID: <9174DAE490321844AE273F6AD001E3EA9D804C36 at ALA-MBD.corp.ad.wrs.com> Content-Type: text/plain; charset="windows-1252" Hi Liang, No objections here, mark this patch as abandoned. Regards, Daniel ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Tuesday, November 06, 2018 10:55 To: Badea, Daniel; Poncea, Ovidiu Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming Hi Daniel and Ovidiu Repo: cinder Commit: 294a63c821233e3307f142965f366e8eb3d0c1de Title: Pike Rebase: Fix Cinder memory leak This patch is to call novaclient’s API “set_timings_max_len”, to limit the max timing logs, so that the log list will not be to huge. But novaclient(both the upstream version and stx- version) don’t contain the API set_timings_max_len, I also cannot find in repo history. It seems this patch may co-worked with some private version of novaclient previously, but not the public version. In fact current novaclient contains an API “reset_timings” which can be called to purge the timing logs. I want to mark this patch as abandoned, do you have any comments? Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 2 Date: Tue, 6 Nov 2018 14:17:29 +0000 From: "Fang, Liang A" To: "Badea, Daniel" , "Poncea, Ovidiu" Cc: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming Message-ID: Content-Type: text/plain; charset="utf-8" Thanks Daniel. Regards Liang From: Badea, Daniel [mailto:Daniel.Badea at windriver.com] Sent: Tuesday, November 6, 2018 10:03 PM To: Fang, Liang A ; Poncea, Ovidiu Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming Hi Liang, No objections here, mark this patch as abandoned. Regards, Daniel ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Tuesday, November 06, 2018 10:55 To: Badea, Daniel; Poncea, Ovidiu Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming Hi Daniel and Ovidiu Repo: cinder Commit: 294a63c821233e3307f142965f366e8eb3d0c1de Title: Pike Rebase: Fix Cinder memory leak This patch is to call novaclient's API "set_timings_max_len", to limit the max timing logs, so that the log list will not be to huge. But novaclient(both the upstream version and stx- version) don't contain the API set_timings_max_len, I also cannot find in repo history. It seems this patch may co-worked with some private version of novaclient previously, but not the public version. In fact current novaclient contains an API "reset_timings" which can be called to purge the timing logs. I want to mark this patch as abandoned, do you have any comments? Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Tue, 6 Nov 2018 14:38:25 +0000 From: "Qin, Kailun" To: "Legacy, Allain" , "Peters, Matt" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Analysis of patch 039705e for StarlingX upstreaming Message-ID: Content-Type: text/plain; charset="utf-8" Allain, Thanks a lot for the confirmation and clarification. Yes, the host driver is being redesigned. I'll drop the patch accordingly. BR, Kailun From: Legacy, Allain [mailto:Allain.Legacy at windriver.com] Sent: Tuesday, November 6, 2018 8:16 PM To: Qin, Kailun ; Peters, Matt ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Analysis of patch 039705e for StarlingX upstreaming I agree. These changes can all be dropped. The keystone config opts change was needed for the host driver to communicate back to our sysinv subsystem, but, as far as I know, that is being redesigned to avoid this requirement. Regards, Allain Allain Legacy, Software Developer, Wind River direct 613.270.2279 fax 613.492.7870 skype allain.legacy 350 Terry Fox Drive, Suite 200, Ottawa, Ontario, K2K 2W5 [WIND] From: Qin, Kailun [mailto:kailun.qin at intel.com] Sent: Tuesday, November 06, 2018 2:10 AM To: Peters, Matt; starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Analysis of patch 039705e for StarlingX upstreaming Hi Matt, We're looking into the patch 039705e for upstreaming, which contains several base changes. 1. For the oslo.db related change, upstream has already dropped this override in neutron-server to make it use default values from oslo.db (see https://review.openstack.org/456419/ for detailed information). 2. For the keystone opts registration, I guess it is used for connecting to external services. From upstream's perspective, this should be maintained along with the specific service to extend rather than make it globally. 3. For the others, I think they're StarlingX specific. Thus, I suggest that we should not upstream these changes. What do you think? Let me know if any question, thanks! BR, Kailun -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1807 bytes Desc: image001.png URL: ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 6, Issue 20 ************************************************ From hayde.martinez.landa at intel.com Tue Nov 6 16:51:48 2018 From: hayde.martinez.landa at intel.com (Martinez Landa, Hayde) Date: Tue, 6 Nov 2018 16:51:48 +0000 Subject: [Starlingx-discuss] [build][meetings] Meeting minutes 11/1/2018 In-Reply-To: References: Message-ID: <26C1EE58-528C-4F24-89DB-9D3DB6C7E4F2@intel.com> Hi Ken! We tried mirror_downloader.sh on our Jenkins automated environment and also on my local environment and when it finished running we noticed that the following files were moved: this ones were sent to: “/localdisk/output/stx-r1/CentOS/pike/Binary/x86_64” -rpms_3rdparties.lst -rpms_centos.lst -rpms_centos3rdparties.lst -tarball-dl.lst Same with “yum.repos.d” were sent to: “CentOS/pike/Binary/noarch/” CentOS/pike/Binary/noarch/yum.repos.d/ CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.2.repo CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_buildlogs_centos_org.repo CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_download_docker_com.repo CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_CentOS-OpenStack-queens.repo CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_epel_blizoo_mk.repo CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_linuxsoft_cern_ch.repo CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.3.repo CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_buildlogs-seed_centos_org.repo CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_www_rpmfind_net.repo CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.4.repo CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-EPEL-7.repo CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_ftp_iij_ad_jp.repo CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.5.repo And finally rpm-gpg-keys sent to: “CentOS/pike/Binary/x86_64” CentOS/pike/Binary/x86_64/rpm-gpg-keys/ CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC27-primary CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-SCLo CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Debug-6 CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-6 CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-EPEL-6 CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Security-6 CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-OpsTools CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC29 CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC27 CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-EPEL-7 CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-5 CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-DOCKER CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-cern CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-Virtualization CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC27-second CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC28 CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Testing-6 CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-Cloud-SIG Is this the expected behavior? I’m currently finishing the build with this mirror, will update once it’s done. Best -Hayde From: "Young, Ken" Date: Monday, November 5, 2018 at 2:43 PM To: "Lara, Cesar" Cc: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [build][meetings] Meeting minutes 11/1/2018 Cesar, A quick update on the mirror. The tooling to enable the mirror was merged on Friday. The Wind River used the mirror over the week-end for its builds with no issues. How have your builds gone since Friday? /KenY From: "Lara, Cesar" Date: Thursday, November 1, 2018 at 6:58 PM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] [build][meetings] Meeting minutes 11/1/2018 Build team meeting minutes 11/1/2018 Attendees Ken, Jason, Scott, Memo, Erich, Marcela, Victor, Chuy, Cesar, Luis Cengn Status -Mirror is now completed and operational, the wiki has been updated with the details for Cengn and our partnership, the details and specs are already there. -The scripts that are related with mirror download are now pointing to Cengn repos and are waiting in the queue to be reviewed tested and merged, the desired date for fully operational mirror is November 5th - Now changes to the packages required to build will be caught by Cengn mirror within one day, the scripts will try to download first from Cengn and if is still not available will try to go get the packages from upstream. Koji follow up -presentation on a possible scenario hosting Koji and demo on using Koji based built packages with our current build scripts. -discussion followed up by implementation details led to different points of view about the problem we have to solve if there’s any, the amount of effort to integrate tooling as we know Koji doesn’t solve every use case by itself and where to host a Koji service(we are striving to host a centralized service for the whole community). -The statement we are using to follow thru with Koji versus our current script is that we will require a lot of effort to support multi OS with the current tools. We had to defer the topic of mirror script refactored using Python. We will start a thread on the goals this team has for next release on the mailing list. Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.a.cobbley at intel.com Tue Nov 6 19:05:48 2018 From: david.a.cobbley at intel.com (Cobbley, David A) Date: Tue, 6 Nov 2018 19:05:48 +0000 Subject: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming In-Reply-To: <38713B7817E1A049AB469EA7F6EEF69EBBFCA226@ALA-MBD.corp.ad.wrs.com> References: <38713B7817E1A049AB469EA7F6EEF69EBBFCA226@ALA-MBD.corp.ad.wrs.com> Message-ID: Jim, The technical team decided months ago on nomenclature to use for each action taken on the original patches for TCR5. "Abandoned" was determined by the team (now the TSC) for patches that were in the original set but determined to no longer be needed. No need to change the nomenclature midpoint as long as all team members understand what is meant by each state we are using; further details on reason for the state change are also included in the patch resolution. --David C -----Original Message----- From: Einarsson, Jim [mailto:Jim.Einarsson at windriver.com] Sent: Tuesday, November 6, 2018 6:44 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming I don't understand why we would mark this patch "Abandoned". If the code is not required, then it should be deleted and marked as "deleted", no? Regards JimE -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io [mailto:starlingx-discuss-request at lists.starlingx.io] Sent: Tuesday, November 06, 2018 9:39 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 6, Issue 20 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. Re: Analysis of patch 294a63c for StarlingX Upstreaming (Badea, Daniel) 2. Re: Analysis of patch 294a63c for StarlingX Upstreaming (Fang, Liang A) 3. Re: Analysis of patch 039705e for StarlingX upstreaming (Qin, Kailun) ---------------------------------------------------------------------- Message: 1 Date: Tue, 6 Nov 2018 14:02:47 +0000 From: "Badea, Daniel" To: "Fang, Liang A" , "Poncea, Ovidiu" Cc: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming Message-ID: <9174DAE490321844AE273F6AD001E3EA9D804C36 at ALA-MBD.corp.ad.wrs.com> Content-Type: text/plain; charset="windows-1252" Hi Liang, No objections here, mark this patch as abandoned. Regards, Daniel ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Tuesday, November 06, 2018 10:55 To: Badea, Daniel; Poncea, Ovidiu Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming Hi Daniel and Ovidiu Repo: cinder Commit: 294a63c821233e3307f142965f366e8eb3d0c1de Title: Pike Rebase: Fix Cinder memory leak This patch is to call novaclient’s API “set_timings_max_len”, to limit the max timing logs, so that the log list will not be to huge. But novaclient(both the upstream version and stx- version) don’t contain the API set_timings_max_len, I also cannot find in repo history. It seems this patch may co-worked with some private version of novaclient previously, but not the public version. In fact current novaclient contains an API “reset_timings” which can be called to purge the timing logs. I want to mark this patch as abandoned, do you have any comments? Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 2 Date: Tue, 6 Nov 2018 14:17:29 +0000 From: "Fang, Liang A" To: "Badea, Daniel" , "Poncea, Ovidiu" Cc: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming Message-ID: Content-Type: text/plain; charset="utf-8" Thanks Daniel. Regards Liang From: Badea, Daniel [mailto:Daniel.Badea at windriver.com] Sent: Tuesday, November 6, 2018 10:03 PM To: Fang, Liang A ; Poncea, Ovidiu Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming Hi Liang, No objections here, mark this patch as abandoned. Regards, Daniel ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Tuesday, November 06, 2018 10:55 To: Badea, Daniel; Poncea, Ovidiu Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming Hi Daniel and Ovidiu Repo: cinder Commit: 294a63c821233e3307f142965f366e8eb3d0c1de Title: Pike Rebase: Fix Cinder memory leak This patch is to call novaclient's API "set_timings_max_len", to limit the max timing logs, so that the log list will not be to huge. But novaclient(both the upstream version and stx- version) don't contain the API set_timings_max_len, I also cannot find in repo history. It seems this patch may co-worked with some private version of novaclient previously, but not the public version. In fact current novaclient contains an API "reset_timings" which can be called to purge the timing logs. I want to mark this patch as abandoned, do you have any comments? Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Tue, 6 Nov 2018 14:38:25 +0000 From: "Qin, Kailun" To: "Legacy, Allain" , "Peters, Matt" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Analysis of patch 039705e for StarlingX upstreaming Message-ID: Content-Type: text/plain; charset="utf-8" Allain, Thanks a lot for the confirmation and clarification. Yes, the host driver is being redesigned. I'll drop the patch accordingly. BR, Kailun From: Legacy, Allain [mailto:Allain.Legacy at windriver.com] Sent: Tuesday, November 6, 2018 8:16 PM To: Qin, Kailun ; Peters, Matt ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Analysis of patch 039705e for StarlingX upstreaming I agree. These changes can all be dropped. The keystone config opts change was needed for the host driver to communicate back to our sysinv subsystem, but, as far as I know, that is being redesigned to avoid this requirement. Regards, Allain Allain Legacy, Software Developer, Wind River direct 613.270.2279 fax 613.492.7870 skype allain.legacy 350 Terry Fox Drive, Suite 200, Ottawa, Ontario, K2K 2W5 [WIND] From: Qin, Kailun [mailto:kailun.qin at intel.com] Sent: Tuesday, November 06, 2018 2:10 AM To: Peters, Matt; starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Analysis of patch 039705e for StarlingX upstreaming Hi Matt, We're looking into the patch 039705e for upstreaming, which contains several base changes. 1. For the oslo.db related change, upstream has already dropped this override in neutron-server to make it use default values from oslo.db (see https://review.openstack.org/456419/ for detailed information). 2. For the keystone opts registration, I guess it is used for connecting to external services. From upstream's perspective, this should be maintained along with the specific service to extend rather than make it globally. 3. For the others, I think they're StarlingX specific. Thus, I suggest that we should not upstream these changes. What do you think? Let me know if any question, thanks! BR, Kailun -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1807 bytes Desc: image001.png URL: ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 6, Issue 20 ************************************************ _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Jim.Einarsson at windriver.com Tue Nov 6 19:10:35 2018 From: Jim.Einarsson at windriver.com (Einarsson, Jim) Date: Tue, 6 Nov 2018 19:10:35 +0000 Subject: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming In-Reply-To: References: <38713B7817E1A049AB469EA7F6EEF69EBBFCA226@ALA-MBD.corp.ad.wrs.com> Message-ID: <38713B7817E1A049AB469EA7F6EEF69EBBFCA890@ALA-MBD.corp.ad.wrs.com> I like "removed from code base". This is clear about what was done to eliminate the technical debt. What value "abandoned" adds escapes me, since the code isn’t abandoned, it is removed from the code base. Jim -----Original Message----- From: Cobbley, David A [mailto:david.a.cobbley at intel.com] Sent: Tuesday, November 06, 2018 2:06 PM To: Einarsson, Jim; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming Jim, The technical team decided months ago on nomenclature to use for each action taken on the original patches for TCR5. "Abandoned" was determined by the team (now the TSC) for patches that were in the original set but determined to no longer be needed. No need to change the nomenclature midpoint as long as all team members understand what is meant by each state we are using; further details on reason for the state change are also included in the patch resolution. --David C -----Original Message----- From: Einarsson, Jim [mailto:Jim.Einarsson at windriver.com] Sent: Tuesday, November 6, 2018 6:44 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming I don't understand why we would mark this patch "Abandoned". If the code is not required, then it should be deleted and marked as "deleted", no? Regards JimE -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io [mailto:starlingx-discuss-request at lists.starlingx.io] Sent: Tuesday, November 06, 2018 9:39 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 6, Issue 20 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. Re: Analysis of patch 294a63c for StarlingX Upstreaming (Badea, Daniel) 2. Re: Analysis of patch 294a63c for StarlingX Upstreaming (Fang, Liang A) 3. Re: Analysis of patch 039705e for StarlingX upstreaming (Qin, Kailun) ---------------------------------------------------------------------- Message: 1 Date: Tue, 6 Nov 2018 14:02:47 +0000 From: "Badea, Daniel" To: "Fang, Liang A" , "Poncea, Ovidiu" Cc: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming Message-ID: <9174DAE490321844AE273F6AD001E3EA9D804C36 at ALA-MBD.corp.ad.wrs.com> Content-Type: text/plain; charset="windows-1252" Hi Liang, No objections here, mark this patch as abandoned. Regards, Daniel ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Tuesday, November 06, 2018 10:55 To: Badea, Daniel; Poncea, Ovidiu Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming Hi Daniel and Ovidiu Repo: cinder Commit: 294a63c821233e3307f142965f366e8eb3d0c1de Title: Pike Rebase: Fix Cinder memory leak This patch is to call novaclient’s API “set_timings_max_len”, to limit the max timing logs, so that the log list will not be to huge. But novaclient(both the upstream version and stx- version) don’t contain the API set_timings_max_len, I also cannot find in repo history. It seems this patch may co-worked with some private version of novaclient previously, but not the public version. In fact current novaclient contains an API “reset_timings” which can be called to purge the timing logs. I want to mark this patch as abandoned, do you have any comments? Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 2 Date: Tue, 6 Nov 2018 14:17:29 +0000 From: "Fang, Liang A" To: "Badea, Daniel" , "Poncea, Ovidiu" Cc: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming Message-ID: Content-Type: text/plain; charset="utf-8" Thanks Daniel. Regards Liang From: Badea, Daniel [mailto:Daniel.Badea at windriver.com] Sent: Tuesday, November 6, 2018 10:03 PM To: Fang, Liang A ; Poncea, Ovidiu Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming Hi Liang, No objections here, mark this patch as abandoned. Regards, Daniel ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Tuesday, November 06, 2018 10:55 To: Badea, Daniel; Poncea, Ovidiu Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Analysis of patch 294a63c for StarlingX Upstreaming Hi Daniel and Ovidiu Repo: cinder Commit: 294a63c821233e3307f142965f366e8eb3d0c1de Title: Pike Rebase: Fix Cinder memory leak This patch is to call novaclient's API "set_timings_max_len", to limit the max timing logs, so that the log list will not be to huge. But novaclient(both the upstream version and stx- version) don't contain the API set_timings_max_len, I also cannot find in repo history. It seems this patch may co-worked with some private version of novaclient previously, but not the public version. In fact current novaclient contains an API "reset_timings" which can be called to purge the timing logs. I want to mark this patch as abandoned, do you have any comments? Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Tue, 6 Nov 2018 14:38:25 +0000 From: "Qin, Kailun" To: "Legacy, Allain" , "Peters, Matt" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Analysis of patch 039705e for StarlingX upstreaming Message-ID: Content-Type: text/plain; charset="utf-8" Allain, Thanks a lot for the confirmation and clarification. Yes, the host driver is being redesigned. I'll drop the patch accordingly. BR, Kailun From: Legacy, Allain [mailto:Allain.Legacy at windriver.com] Sent: Tuesday, November 6, 2018 8:16 PM To: Qin, Kailun ; Peters, Matt ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Analysis of patch 039705e for StarlingX upstreaming I agree. These changes can all be dropped. The keystone config opts change was needed for the host driver to communicate back to our sysinv subsystem, but, as far as I know, that is being redesigned to avoid this requirement. Regards, Allain Allain Legacy, Software Developer, Wind River direct 613.270.2279 fax 613.492.7870 skype allain.legacy 350 Terry Fox Drive, Suite 200, Ottawa, Ontario, K2K 2W5 [WIND] From: Qin, Kailun [mailto:kailun.qin at intel.com] Sent: Tuesday, November 06, 2018 2:10 AM To: Peters, Matt; starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Analysis of patch 039705e for StarlingX upstreaming Hi Matt, We're looking into the patch 039705e for upstreaming, which contains several base changes. 1. For the oslo.db related change, upstream has already dropped this override in neutron-server to make it use default values from oslo.db (see https://review.openstack.org/456419/ for detailed information). 2. For the keystone opts registration, I guess it is used for connecting to external services. From upstream's perspective, this should be maintained along with the specific service to extend rather than make it globally. 3. For the others, I think they're StarlingX specific. Thus, I suggest that we should not upstream these changes. What do you think? Let me know if any question, thanks! BR, Kailun -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1807 bytes Desc: image001.png URL: ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 6, Issue 20 ************************************************ _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Tue Nov 6 21:33:27 2018 From: scott.little at windriver.com (Scott Little) Date: Tue, 6 Nov 2018 16:33:27 -0500 Subject: [Starlingx-discuss] [build][meetings] Meeting minutes 11/1/2018 In-Reply-To: <26C1EE58-528C-4F24-89DB-9D3DB6C7E4F2@intel.com> References: <26C1EE58-528C-4F24-89DB-9D3DB6C7E4F2@intel.com> Message-ID: <5720fea7-9b69-8723-d940-a66d23dd5fb2@windriver.com> I can't reproduce this, with or without https://review.openstack.org/#/c/615316 Where you in the container when you ran mirror_downloader.sh?  In directory /localdisk? Scott On 18-11-06 11:51 AM, Martinez Landa, Hayde wrote: > > Hi Ken! > > We tried mirror_downloader.sh on our Jenkins automated environment and > also on > > my local environment and when it finished running we noticed that the > following files were moved: > > this ones were sent to: > “/localdisk/output/stx-r1/CentOS/pike/Binary/x86_64” > > -rpms_3rdparties.lst > > -rpms_centos.lst > > -rpms_centos3rdparties.lst > > -tarball-dl.lst > > Same with “yum.repos.d” were sent to: “CentOS/pike/Binary/noarch/” > > CentOS/pike/Binary/noarch/yum.repos.d/ > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.2.repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_buildlogs_centos_org.repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_download_docker_com.repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_CentOS-OpenStack-queens.repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_epel_blizoo_mk.repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_linuxsoft_cern_ch.repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.3.repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_buildlogs-seed_centos_org.repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_www_rpmfind_net.repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.4.repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-EPEL-7.repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_ftp_iij_ad_jp.repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.5.repo > > And finally rpm-gpg-keys sent to: “CentOS/pike/Binary/x86_64” > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/ > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC27-primary > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-SCLo > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Debug-6 > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-6 > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-EPEL-6 > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Security-6 > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-OpsTools > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC29 > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC27 > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-EPEL-7 > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-5 > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-DOCKER > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-cern > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-Virtualization > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC27-second > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC28 > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Testing-6 > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-Cloud-SIG > > Is this the expected behavior? > > I’m currently finishing the build with this mirror, will update once > it’s done. > > Best > > -Hayde > > *From: *"Young, Ken" > *Date: *Monday, November 5, 2018 at 2:43 PM > *To: *"Lara, Cesar" > *Cc: *"starlingx-discuss at lists.starlingx.io" > > *Subject: *Re: [Starlingx-discuss] [build][meetings] Meeting minutes > 11/1/2018 > > Cesar, > > A quick update on the mirror.  The tooling to enable the mirror was > merged on Friday.  The Wind River used the mirror over the week-end > for its builds with no issues. > > How have your builds gone since Friday? > > /KenY > > *From: *"Lara, Cesar" > *Date: *Thursday, November 1, 2018 at 6:58 PM > *To: *"starlingx-discuss at lists.starlingx.io" > > *Subject: *[Starlingx-discuss] [build][meetings] Meeting minutes 11/1/2018 > > Build team meeting minutes 11/1/2018 > > Attendees > > Ken, Jason, Scott, Memo, Erich, Marcela, Victor, Chuy, Cesar, Luis > > Cengn Status > > -Mirror is now completed and operational, the wiki has been updated > with the details for Cengn and our partnership, the details and specs > are already there. > > -The scripts that are related with mirror download are now pointing to > Cengn repos and are waiting in the queue to be reviewed tested and > merged, the desired date for fully operational mirror is November 5^th > > - Now changes to the packages required to build will be caught by > Cengn mirror within one day, the scripts will try to download first > from Cengn and if is still not available will try to go get the > packages from upstream. > > Koji follow up > > -presentation on a possible scenario hosting Koji and demo on using > Koji based built packages with our current build scripts. > > -discussion followed up by implementation details led to different > points of view about the problem we have to solve if there’s any, the > amount of effort to integrate tooling as we know Koji doesn’t solve > every use case by itself and where to host a Koji service(we are > striving to host a centralized service for the whole community). > > -The statement we are using to follow thru with Koji versus our > current script is that we will require a lot of effort to support > multi OS with the current tools. > > We had to defer the topic of mirror script refactored using Python. > > We will start a thread on the goals this team has for next release on > the mailing list. > > Regards > > *//* > > */Cesar Lara/* > > Software Engineering Manager > > OpenSource Technology Center > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.cordoba.malibran at intel.com Wed Nov 7 00:29:18 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Wed, 7 Nov 2018 00:29:18 +0000 Subject: [Starlingx-discuss] Does openstack-helm-infra needs network access to build? Message-ID: Hi all, We are seeing a failure today in our build environment. The openstack- helm-infra package is failing. Checking the logs it seems that the network access is required during building: Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com Error: Looks like "https://kubernetes-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: Get https://kubernetes-charts.storage.googleapis.com/index.yaml: proxyconnect tcp: dial tcp: lookup on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address error: Bad exit status from /var/tmp/rpm-tmp.KecSPl (%build) We run the build in an isolated environment without internet access. Is someone seeing something similar? If this is true, then what would be the best practice here, do we want network access while building? or it should work in an isolated environment? Thanks in advance -Erich From sgw at linux.intel.com Wed Nov 7 01:30:38 2018 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 6 Nov 2018 17:30:38 -0800 Subject: [Starlingx-discuss] [TLs][PLs][TSC] Sub-project and git repo mapping seems to be incomplete In-Reply-To: References: Message-ID: As TL for the Build and Distro non-Openstack sub-projects, I think that the following Repos should belong as follows: Build: - stx-tools - stx-root - stx-manifest (I think) The Non-Openstack Distro should contain: - stx-integ There are some other communities members that should be added as Core reviewers once the correct ownership at the TL level is set. Any concerns from the TSC on this list. I would have replied last week, but had no VPN until midday Monday. Thanks Sau! On 11/5/18 2:55 PM, Ildiko Vancsa wrote: > Hi, > > While I was working on getting the initial core reviewer teams setup in Gerrit I realized that not all repositories seem to be covered by sub-project teams or even if they are it is not documented clearly. > > Currently we have information about the main project on the docs website under governance: https://docs.starlingx.io/governance/reference/tsc/projects/index.html > And we have further information on the wiki about sub-projects: https://wiki.openstack.org/wiki/StarlingX > > Some repositories such as stx-upstream does not seem to be listed on either of the above links which makes it hard to identify which sub-project team maintains it. > > I would like to ask the Project and Technical Leads as well as the TSC to please help to look into this and make the mapping a full coverage that is also easily accessible. As we have started to fill up the documentation website with information I would suggest to extend the project list under the governance section that I linked in above. > > Thanks and Best Regards, > Ildikó > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From shuicheng.lin at intel.com Wed Nov 7 01:33:39 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Wed, 7 Nov 2018 01:33:39 +0000 Subject: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 In-Reply-To: <3a8a02b2-624d-6f91-5dbd-b20d3fab0e16@windriver.com> References: <2F61A2101B4FD447A683EF7E362CF9421C63E2181F@RSI-NOD-EXMDB6.india.rsystems.com> <3a8a02b2-624d-6f91-5dbd-b20d3fab0e16@windriver.com> Message-ID: <9700A18779F35F49AF027300A49E7C765FE3B1FF@SHSMSX101.ccr.corp.intel.com> Hi all, Do we have bug/story to track the issue? I prefer to upgrade the lighttpd src rpm to 1.4.51 to solve it. Best Regards Shuicheng -----Original Message----- From: Scott Little [mailto:scott.little at windriver.com] Sent: Saturday, November 3, 2018 4:23 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 Try updating your stx-tools and running download_mirror.sh again. Alternatively, you can find it here ... http://mirror.starlingx.cengn.ca/mirror/centos/epel/dl.fedoraproject.org/pub/epel/7/SRPMS/Packages/l/lighttpd-1.4.50-1.el7.src.rpm Scott On 18-11-02 05:19 AM, Rajesh Jha wrote: > Hi, > > > We were trying to pick up patches for some issues which we had > reported like SSH not working and failing to attach data interface from controller to compute nodes. We failed to make the build. at step 2 of section Download Packages¶ from https://docs.starlingx.io/developer_guide/index.html#build-the-centos-mirror-repository document. > when we run download_mirror.sh from the container There is one package which fails to download lighttpd-1.4.50-1.el7.src.rpm which is there in rpms_centos.lst. Since this version is not there on any mirror on internet, the version available is lighttpd-1.4.51-1.el7.src.rpm so we updated the file rpms_centos.lst and rpms_centos3rdparties.lst with lighttpd-1.4.51-1.el7.x86_64.rpm instead. Ran the download_mirror.sh again. Now everything is fine except it is failing in build-pkgs step with the following error. > > b6: ERROR: build_dir (415): Invalid srpm path 'mirror:Source/lighttpd-1.4.50-1.el7.src.rpm', evaluated as '/localdisk/designer/builder/starlingx/cgcs-root/cgcs-centos-repo/Source/lighttpd-1.4.50-1.el7.src.rpm', found in '/localdisk/designer/builder/starlingx/cgcs-root/stx/stx-integ/base/lighttpd/centos/srpm_path' > > now we are stuck and unable to build. Any suggestions would be welcome. > > on a general note, had a quick query how much time the incremental > build is taking in general. Because we follow the steps for > incremental build after step git clone > https://git.starlingx.io/stx-tools > > and then we build the container image and all steps after that which is also taking 3 to 4 hours. Am I doing the incremental build properly?? > > Best Regards, > Rajesh Jha > > > The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, please immediately alert the sender by reply e-mail and then delete this message. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. R Systems has taken every reasonable precaution to minimize the risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From yong.hu at intel.com Wed Nov 7 03:50:11 2018 From: yong.hu at intel.com (Hu, Yong) Date: Wed, 7 Nov 2018 03:50:11 +0000 Subject: [Starlingx-discuss] Does openstack-helm-infra needs network access to build? In-Reply-To: References: Message-ID: I also met the same problem, and resolved it by adding proxy settings into “~/cgcs-root/cgcs-centos-repo/mock.cfg.proto”: config_opts[‘rpmbuild_networking’] = False + config_opts[‘no_proxy’] = ‘127.0.0.1’ + config_opts[‘http_proxy’]= ‘http://:’ + config_opts[‘https_proxy’]= ‘http:// :’ Here is my screenshot of my build: 03:35:07 ===== wait for last jobs in iteration 1 to complete ===== 03:35:07 building openstack-helm-infra-1.0-3.tis.src.rpm 03:36:02 End build on ‘b0’: /localdisk/loadbuild/yhu6/starlingx/std/rpmbuild/SRPMS/openstack-helm-infra-1.0-3.tis.src.rpm 03:36:02 Success building openstack-helm-infra-1.0-3.tis.src.rpm on ‘b0’ (edited) I might file a patch to "~/build-tools/repo_files/mock.cfg.proto b/build-tools/repo_files/mock.cfg.proto", which is the original copy of “~/cgcs-root/cgcs-centos-repo/mock.cfg.proto". Though, I also like to see if there is a better solution. -yong On 07/11/2018, 8:29 AM, "Cordoba Malibran, Erich" wrote: Hi all, We are seeing a failure today in our build environment. The openstack- helm-infra package is failing. Checking the logs it seems that the network access is required during building: Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com Error: Looks like "https://kubernetes-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: Get https://kubernetes-charts.storage.googleapis.com/index.yaml: proxyconnect tcp: dial tcp: lookup on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address error: Bad exit status from /var/tmp/rpm-tmp.KecSPl (%build) We run the build in an isolated environment without internet access. Is someone seeing something similar? If this is true, then what would be the best practice here, do we want network access while building? or it should work in an isolated environment? Thanks in advance -Erich _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From shuicheng.lin at intel.com Wed Nov 7 04:28:50 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Wed, 7 Nov 2018 04:28:50 +0000 Subject: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 References: <2F61A2101B4FD447A683EF7E362CF9421C63E2181F@RSI-NOD-EXMDB6.india.rsystems.com> <3a8a02b2-624d-6f91-5dbd-b20d3fab0e16@windriver.com> Message-ID: <9700A18779F35F49AF027300A49E7C765FE3B2B9@SHSMSX101.ccr.corp.intel.com> Hi all, I created a story for it: https://storyboard.openstack.org/#!/story/2004282 And here is the code. Please help review it: https://review.openstack.org/616061 https://review.openstack.org/616062 I have done build and deploy test. Please share me if there is any more test need be done. Thanks. Best Regards Shuicheng -----Original Message----- From: Lin, Shuicheng Sent: Wednesday, November 7, 2018 9:34 AM To: 'Scott Little' ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 Hi all, Do we have bug/story to track the issue? I prefer to upgrade the lighttpd src rpm to 1.4.51 to solve it. Best Regards Shuicheng -----Original Message----- From: Scott Little [mailto:scott.little at windriver.com] Sent: Saturday, November 3, 2018 4:23 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 Try updating your stx-tools and running download_mirror.sh again. Alternatively, you can find it here ... http://mirror.starlingx.cengn.ca/mirror/centos/epel/dl.fedoraproject.org/pub/epel/7/SRPMS/Packages/l/lighttpd-1.4.50-1.el7.src.rpm Scott On 18-11-02 05:19 AM, Rajesh Jha wrote: > Hi, > > > We were trying to pick up patches for some issues which we had > reported like SSH not working and failing to attach data interface from controller to compute nodes. We failed to make the build. at step 2 of section Download Packages¶ from https://docs.starlingx.io/developer_guide/index.html#build-the-centos-mirror-repository document. > when we run download_mirror.sh from the container There is one package which fails to download lighttpd-1.4.50-1.el7.src.rpm which is there in rpms_centos.lst. Since this version is not there on any mirror on internet, the version available is lighttpd-1.4.51-1.el7.src.rpm so we updated the file rpms_centos.lst and rpms_centos3rdparties.lst with lighttpd-1.4.51-1.el7.x86_64.rpm instead. Ran the download_mirror.sh again. Now everything is fine except it is failing in build-pkgs step with the following error. > > b6: ERROR: build_dir (415): Invalid srpm path 'mirror:Source/lighttpd-1.4.50-1.el7.src.rpm', evaluated as '/localdisk/designer/builder/starlingx/cgcs-root/cgcs-centos-repo/Source/lighttpd-1.4.50-1.el7.src.rpm', found in '/localdisk/designer/builder/starlingx/cgcs-root/stx/stx-integ/base/lighttpd/centos/srpm_path' > > now we are stuck and unable to build. Any suggestions would be welcome. > > on a general note, had a quick query how much time the incremental > build is taking in general. Because we follow the steps for > incremental build after step git clone > https://git.starlingx.io/stx-tools > > and then we build the container image and all steps after that which is also taking 3 to 4 hours. Am I doing the incremental build properly?? > > Best Regards, > Rajesh Jha > > > The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, please immediately alert the sender by reply e-mail and then delete this message. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. R Systems has taken every reasonable precaution to minimize the risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From chenjie.xu at intel.com Wed Nov 7 05:24:51 2018 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Wed, 7 Nov 2018 05:24:51 +0000 Subject: [Starlingx-discuss] Analysis of patch 2e4ca00 for StarlingX Upstreaming In-Reply-To: <70A7408C6E1BFB41B192A929744D8523BAC2F483@ALA-MBD.corp.ad.wrs.com> References: <70A7408C6E1BFB41B192A929744D8523BAC2F483@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Allain, Thanks for your reply! I agree with your opinions. About configuration option, I think we can propose to add max_rpc_response_timeout or multipler into the config file. The function get_max_timeout() should return max_rpc_response_timeout or multipler*rpc_response_timeout. The default value for max_rpc_response_timeout can be 300s and for multipler can be 5. Coud you please help review and comment? Best Regards, Xu, Chenjie From: Legacy, Allain [mailto:Allain.Legacy at windriver.com] Sent: Tuesday, November 6, 2018 8:30 PM To: Xu, Chenjie ; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Analysis of patch 2e4ca00 for StarlingX Upstreaming The issue with changing the configuration value from 60 to 6 is that provides the default value for _METHOD_TIMEOUTS which means now each RPC request will timeout after 6 seconds rather than 60 seconds. In a heavily loaded system that timeout will get hit frequently thus leading to repeated RPC requests and an increased load on the server. We need a way to control the maximum timeout without reducing the timeout of each individual RPC timeout so much as to increase the load on the server. I think it is unlikely that upstream will accept the current change in its current form. Perhaps we need to propose a configuration option that can be controlled via config file but still leaves the default as it is today. Regards, Allain Allain Legacy, Software Developer, Wind River direct 613.270.2279 fax 613.492.7870 skype allain.legacy 350 Terry Fox Drive, Suite 200, Ottawa, Ontario, K2K 2W5 [WIND] From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, November 06, 2018 2:35 AM To: Peters, Matt Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Analysis of patch 2e4ca00 for StarlingX Upstreaming Hi Matt, The patch 2e4ca00 changes function get_max_timeout() by changing the multiplication factor of 10 to 1 to avoid wait for 60*10 seconds(The default value for rpc_response_timeout is 60). This can be done by changing the default value from 60 to 6. Then will wait 6*10 seconds. This patch may be just a configuration problem to neutron upstream. Do you think we should upstream this patch or not? Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1807 bytes Desc: image001.png URL: From Allain.Legacy at windriver.com Wed Nov 7 12:14:22 2018 From: Allain.Legacy at windriver.com (Legacy, Allain) Date: Wed, 7 Nov 2018 12:14:22 +0000 Subject: [Starlingx-discuss] Analysis of patch 2e4ca00 for StarlingX Upstreaming In-Reply-To: References: <70A7408C6E1BFB41B192A929744D8523BAC2F483@ALA-MBD.corp.ad.wrs.com> Message-ID: <70A7408C6E1BFB41B192A929744D8523BAC2FF4E@ALA-MBD.corp.ad.wrs.com> Adding a config option for "max_rpc_response_timeout" is acceptable, but I would continue to use the existing values for multiplier (10) and rpc_response_timeout (60). Anyone needing to use a different maximum can override the configuration option but everyone else will continue to use the existing maximum timeout. Regards, Allain Allain Legacy, Software Developer, Wind River direct 613.270.2279 fax 613.492.7870 skype allain.legacy 350 Terry Fox Drive, Suite 200, Ottawa, Ontario, K2K 2W5 [WIND] From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Wednesday, November 07, 2018 12:25 AM To: Legacy, Allain Cc: starlingx-discuss at lists.starlingx.io; Peters, Matt Subject: RE: [Starlingx-discuss] Analysis of patch 2e4ca00 for StarlingX Upstreaming Hi Allain, Thanks for your reply! I agree with your opinions. About configuration option, I think we can propose to add max_rpc_response_timeout or multipler into the config file. The function get_max_timeout() should return max_rpc_response_timeout or multipler*rpc_response_timeout. The default value for max_rpc_response_timeout can be 300s and for multipler can be 5. Coud you please help review and comment? Best Regards, Xu, Chenjie From: Legacy, Allain [mailto:Allain.Legacy at windriver.com] Sent: Tuesday, November 6, 2018 8:30 PM To: Xu, Chenjie >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Analysis of patch 2e4ca00 for StarlingX Upstreaming The issue with changing the configuration value from 60 to 6 is that provides the default value for _METHOD_TIMEOUTS which means now each RPC request will timeout after 6 seconds rather than 60 seconds. In a heavily loaded system that timeout will get hit frequently thus leading to repeated RPC requests and an increased load on the server. We need a way to control the maximum timeout without reducing the timeout of each individual RPC timeout so much as to increase the load on the server. I think it is unlikely that upstream will accept the current change in its current form. Perhaps we need to propose a configuration option that can be controlled via config file but still leaves the default as it is today. Regards, Allain Allain Legacy, Software Developer, Wind River direct 613.270.2279 fax 613.492.7870 skype allain.legacy 350 Terry Fox Drive, Suite 200, Ottawa, Ontario, K2K 2W5 [WIND] From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, November 06, 2018 2:35 AM To: Peters, Matt Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Analysis of patch 2e4ca00 for StarlingX Upstreaming Hi Matt, The patch 2e4ca00 changes function get_max_timeout() by changing the multiplication factor of 10 to 1 to avoid wait for 60*10 seconds(The default value for rpc_response_timeout is 60). This can be done by changing the default value from 60 to 6. Then will wait 6*10 seconds. This patch may be just a configuration problem to neutron upstream. Do you think we should upstream this patch or not? Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1807 bytes Desc: image001.png URL: From Ian.Jolliffe at windriver.com Wed Nov 7 14:07:19 2018 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Wed, 7 Nov 2018 14:07:19 +0000 Subject: [Starlingx-discuss] [tsc] Nov 1 - notes from TSC meeting Message-ID: <9B335247-BB0A-4368-AE15-93B73243BB92@windriver.com> 11/1/18 TSC meeting facilitation - we discussed the TSC needing to be self-managed now that we have 8 members - topic for further discussion at Berlin. A big thank you to Bruce for helping facilitate the TSC during the early days. Review items in governance review - all TSC members - reminder from Ildiko Review project priorities and start prioritization - Priorities list is here [0] this is an early view and has not been fully prioritized - we added two columns (inflight and spec) to help set some context for the items - we did an overview of the ones the TSC was familiar with. - as requested previously, if people from the sub teams have ideas or items for the list please add it and provide contact information so we can reach out to you. Defects from 2018.10 release - 49 open defects - from prior release - need to be addressed in 2019.03 Upcoming specs - 3 open specs need final reviews Retirement of more staging trees, general discussion about strategy and plans - we didn't get to this item [0] https://ethercalc.openstack.org/fafyo2729fnr From Al.Bailey at windriver.com Wed Nov 7 14:13:46 2018 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Wed, 7 Nov 2018 14:13:46 +0000 Subject: [Starlingx-discuss] Does openstack-helm-infra needs network access to build? In-Reply-To: References: Message-ID: Do you guys have this commit? https://github.com/openstack/stx-root/commit/1615f281093af91da3b998209ff90bbfd0c74350 It flips the networking flag to True Al -----Original Message----- From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Tuesday, November 06, 2018 10:50 PM To: Cordoba Malibran, Erich; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Does openstack-helm-infra needs network access to build? I also met the same problem, and resolved it by adding proxy settings into “~/cgcs-root/cgcs-centos-repo/mock.cfg.proto”: config_opts[‘rpmbuild_networking’] = False + config_opts[‘no_proxy’] = ‘127.0.0.1’ + config_opts[‘http_proxy’]= ‘http://:’ + config_opts[‘https_proxy’]= ‘http:// :’ Here is my screenshot of my build: 03:35:07 ===== wait for last jobs in iteration 1 to complete ===== 03:35:07 building openstack-helm-infra-1.0-3.tis.src.rpm 03:36:02 End build on ‘b0’: /localdisk/loadbuild/yhu6/starlingx/std/rpmbuild/SRPMS/openstack-helm-infra-1.0-3.tis.src.rpm 03:36:02 Success building openstack-helm-infra-1.0-3.tis.src.rpm on ‘b0’ (edited) I might file a patch to "~/build-tools/repo_files/mock.cfg.proto b/build-tools/repo_files/mock.cfg.proto", which is the original copy of “~/cgcs-root/cgcs-centos-repo/mock.cfg.proto". Though, I also like to see if there is a better solution. -yong On 07/11/2018, 8:29 AM, "Cordoba Malibran, Erich" wrote: Hi all, We are seeing a failure today in our build environment. The openstack- helm-infra package is failing. Checking the logs it seems that the network access is required during building: Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com Error: Looks like "https://kubernetes-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: Get https://kubernetes-charts.storage.googleapis.com/index.yaml: proxyconnect tcp: dial tcp: lookup on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address error: Bad exit status from /var/tmp/rpm-tmp.KecSPl (%build) We run the build in an isolated environment without internet access. Is someone seeing something similar? If this is true, then what would be the best practice here, do we want network access while building? or it should work in an isolated environment? Thanks in advance -Erich _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From yong.hu at intel.com Wed Nov 7 14:22:31 2018 From: yong.hu at intel.com (Hu, Yong) Date: Wed, 7 Nov 2018 14:22:31 +0000 Subject: [Starlingx-discuss] Does openstack-helm-infra needs network access to build? In-Reply-To: References: Message-ID: Hi AI, We do have this update in build-tools. The problem was that our build environment is not able to directly access Google site without a special http/https proxy. Regards, Yong On 07/11/2018, 10:14 PM, "Bailey, Henry Albert (Al)" wrote: Do you guys have this commit? https://github.com/openstack/stx-root/commit/1615f281093af91da3b998209ff90bbfd0c74350 It flips the networking flag to True Al -----Original Message----- From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Tuesday, November 06, 2018 10:50 PM To: Cordoba Malibran, Erich; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Does openstack-helm-infra needs network access to build? I also met the same problem, and resolved it by adding proxy settings into “~/cgcs-root/cgcs-centos-repo/mock.cfg.proto”: config_opts[‘rpmbuild_networking’] = False + config_opts[‘no_proxy’] = ‘127.0.0.1’ + config_opts[‘http_proxy’]= ‘http://:’ + config_opts[‘https_proxy’]= ‘http:// :’ Here is my screenshot of my build: 03:35:07 ===== wait for last jobs in iteration 1 to complete ===== 03:35:07 building openstack-helm-infra-1.0-3.tis.src.rpm 03:36:02 End build on ‘b0’: /localdisk/loadbuild/yhu6/starlingx/std/rpmbuild/SRPMS/openstack-helm-infra-1.0-3.tis.src.rpm 03:36:02 Success building openstack-helm-infra-1.0-3.tis.src.rpm on ‘b0’ (edited) I might file a patch to "~/build-tools/repo_files/mock.cfg.proto b/build-tools/repo_files/mock.cfg.proto", which is the original copy of “~/cgcs-root/cgcs-centos-repo/mock.cfg.proto". Though, I also like to see if there is a better solution. -yong On 07/11/2018, 8:29 AM, "Cordoba Malibran, Erich" wrote: Hi all, We are seeing a failure today in our build environment. The openstack- helm-infra package is failing. Checking the logs it seems that the network access is required during building: Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com Error: Looks like "https://kubernetes-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: Get https://kubernetes-charts.storage.googleapis.com/index.yaml: proxyconnect tcp: dial tcp: lookup on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address error: Bad exit status from /var/tmp/rpm-tmp.KecSPl (%build) We run the build in an isolated environment without internet access. Is someone seeing something similar? If this is true, then what would be the best practice here, do we want network access while building? or it should work in an isolated environment? Thanks in advance -Erich _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cindy.xie at intel.com Wed Nov 7 14:49:51 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 7 Nov 2018 14:49:51 +0000 Subject: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack Distro meeting, 11/7 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35DB8FE4@SHSMSX104.ccr.corp.intel.com> Agenda and notes for 11/7 meeting: 1. 2019.03 release content discussion (Cindy) - CentOS 7.6 upgrade (including kernel upgrade) when appropriate): Redhat release dropped 7.6 on Oct 30th. CentOS 7.6 should be released by the end of this year. - non-openStack patch reduction by 40%: ~400 patches in the beginning of effort. ~160 patches needs to be abandomed or upstreamed - Python2to3 non-openStack 100% done: flocks and OS dependent packages need to be Python3 ready. - DevStack flocks plug-in 100% done: stories have been created. - Qemu updated to 3.0, libvirt TBD - Ceph upgrade 2. non-openStack patch refactor status (Zhipeng/Shuicheng) 23 tasks created for 23 packages under story 2003768: https://storyboard.openstack.org/#!/story/2003768 9/23 now have patches generated, with 3 merged and 6 under review. 39 Meta patches removed with 9 packages refactored. 6 SRPM can be replaced with RPM if we finish up 23 packages, 3 of them finished by 9 package refactor other effort also going on, Shuicheng will have detail data after the effort. 3. non-openStack patch upstream status (Saul) generating storyboard for newly reviewed patch, no # yet. 2 reviewed which can be moved to the next step. Others are waiting for WR's feedback. Cindy will take the AR to see my storyboard dashboard. 4. Ceph upgrade status (Vivian/Dehao) - deferred to TSC discussion 5. review the core reviewer name list for non-openstack distro sub-project repo belongs to non-Openstack distro: stx-integ; stx-tis repo is legacy repo and can be dropped. stx-tool will be covered by build/package sub-project. Current proposed core reviewers: Scott Little (scott.little at windriver.com) Bob Church (Robert.Church at windriver.com) Don Penney (Don.Penney at windriver.com ) Jason McKenna (Jason.McKenna at windriver.com) Wold, Saul Rowsell, Brent Process of adding core reviewers: community to nominate, be reviewed by TL (Saul & Brent) and approve. We approved all 6 core reviewers for non-openstack distro project. 6. Opens (all) - None -----Original Appointment----- From: Xie, Cindy Sent: Monday, November 5, 2018 2:27 PM To: Xie, Cindy; Wold, Saul; Rowsell, Brent; Jones, Bruce E; Troyer, Dean; Khalil, Ghada; Waheed, Numan; Lin, Shuicheng; Zhu, Vivian; Shang, Dehao; Liu, ZhipengS; Hu, Yong; Sun, Austin; Somerville, Jim; starlingx-discuss at lists.starlingx.io Cc: Perez Carranza, Jose; 'Hellmann, Gil'; 'Waines, Greg'; 'Chen, Jacky'; Armstrong, Robert H; Perez Rodriguez, Humberto I; Martinez Landa, Hayde; Martinez Monroy, Elio; Hu, Wei W; Seiler, Glenn; Eslimi, Dariush; Gomez, Juan P; Lara, Cesar Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, November 7, 2018 6:00 AM-7:00 AM (UTC-08:00) Pacific Time (US & Canada). Where: https://zoom.us/j/342730236 . Cadence and time slot: o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) . Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ . Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other From erich.cordoba.malibran at intel.com Wed Nov 7 15:16:40 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Wed, 7 Nov 2018 15:16:40 +0000 Subject: [Starlingx-discuss] [build][meetings] Meeting minutes 11/1/2018 In-Reply-To: <5720fea7-9b69-8723-d940-a66d23dd5fb2@windriver.com> References: <26C1EE58-528C-4F24-89DB-9D3DB6C7E4F2@intel.com> <5720fea7-9b69-8723-d940-a66d23dd5fb2@windriver.com> Message-ID: <19d4cd748c8d04563ae59889bbaa185af6043637.camel@intel.com> We have seen this behavior in two different systems. The script is run in this way: cd stx-tools/centos-mirror-tools docker build -t stx-mirror -f Dockerfile . docker run -ti -v $(pwd):/localdisk stx-mirror ./download_mirror.sh After run the script, this is what git reports: On branch master Your branch is up to date with 'origin/master'. Changes not staged for commit: (use "git add/rm ..." to update what will be committed) (use "git checkout -- ..." to discard changes in working directory) deleted: centos-mirror-tools/make_stx_mirror_yum_conf.sh deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-5 deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-6 deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Debug-6 deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-OpsTools deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-SCLo deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-Virtualization deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Security-6 deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Testing-6 deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-Cloud-SIG deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-DOCKER deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-EPEL-6 deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-EPEL-7 deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-FC27 deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-FC27-primary deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-FC27-second deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-FC28 deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-FC29 deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-cern deleted: centos-mirror-tools/rpms_3rdparties.lst deleted: centos-mirror-tools/rpms_centos.lst deleted: centos-mirror-tools/rpms_centos3rdparties.lst deleted: centos-mirror-tools/tarball-dl.lst deleted: centos-mirror-tools/yum.conf.sample deleted: centos-mirror-tools/yum.repos.d/StarlingX-Centos-7.2.repo deleted: centos-mirror-tools/yum.repos.d/StarlingX-Centos-7.3.repo deleted: centos-mirror-tools/yum.repos.d/StarlingX-Centos-7.4.repo deleted: centos-mirror-tools/yum.repos.d/StarlingX-Centos-7.5.repo deleted: centos-mirror-tools/yum.repos.d/StarlingX-EPEL-7.repo deleted: centos-mirror-tools/yum.repos.d/StarlingX_3rd_buildlogs-seed_centos_org.repo deleted: centos-mirror-tools/yum.repos.d/StarlingX_3rd_buildlogs_centos_org.repo deleted: centos-mirror-tools/yum.repos.d/StarlingX_3rd_download_docker_com.repo deleted: centos-mirror-tools/yum.repos.d/StarlingX_3rd_epel_blizoo_mk.repo deleted: centos-mirror-tools/yum.repos.d/StarlingX_3rd_ftp_iij_ad_jp.repo deleted: centos-mirror-tools/yum.repos.d/StarlingX_3rd_linuxsoft_cern_ch.repo deleted: centos-mirror-tools/yum.repos.d/StarlingX_3rd_www_rpmfind_net.repo deleted: centos-mirror-tools/yum.repos.d/StarlingX_CentOS-OpenStack-queens.repo On Tue, 2018-11-06 at 16:33 -0500, Scott Little wrote: > I can't reproduce this, with or without https://review.openstack.org/ > #/c/615316 > > Where you in the container when you ran mirror_downloader.sh? In > directory /localdisk? > > Scott > > > On 18-11-06 11:51 AM, Martinez Landa, Hayde wrote: > > Hi Ken! > > > > We tried mirror_downloader.sh on our Jenkins automated environment > > and also on > > my local environment and when it finished running we noticed that > > the following files were moved: > > > > this ones were sent to: “/localdisk/output/stx- > > r1/CentOS/pike/Binary/x86_64” > > -rpms_3rdparties.lst > > -rpms_centos.lst > > -rpms_centos3rdparties.lst > > -tarball-dl.lst > > Same with “yum.repos.d” were sent to: “CentOS/pike/Binary/noarch/” > > CentOS/pike/Binary/noarch/yum.repos.d/ > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.2.repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_buildlogs_cento > > s_org.repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_download_docker > > _com.repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_CentOS-OpenStack- > > queens.repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_epel_blizoo_mk. > > repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_linuxsoft_cern_ > > ch.repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.3.repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_buildlogs- > > seed_centos_org.repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_www_rpmfind_net > > .repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.4.repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-EPEL-7.repo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_ftp_iij_ad_jp.r > > epo > > CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.5.repo > > > > And finally rpm-gpg-keys sent to: “CentOS/pike/Binary/x86_64” > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/ > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC27-primary > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-SCLo > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Debug-6 > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-6 > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-EPEL-6 > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Security- > > 6 > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG- > > OpsTools > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC29 > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC27 > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-EPEL-7 > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-5 > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-DOCKER > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-cern > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG- > > Virtualization > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC27-second > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC28 > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Testing-6 > > CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-Cloud-SIG > > > > Is this the expected behavior? > > > > I’m currently finishing the build with this mirror, will update > > once it’s done. > > > > Best > > -Hayde > > > > From: "Young, Ken" > > Date: Monday, November 5, 2018 at 2:43 PM > > To: "Lara, Cesar" > > Cc: "starlingx-discuss at lists.starlingx.io" > .starlingx.io> > > Subject: Re: [Starlingx-discuss] [build][meetings] Meeting minutes > > 11/1/2018 > > > > Cesar, > > > > A quick update on the mirror. The tooling to enable the mirror was > > merged on Friday. The Wind River used the mirror over the week-end > > for its builds with no issues. > > > > How have your builds gone since Friday? > > > > /KenY > > > > From: "Lara, Cesar" > > Date: Thursday, November 1, 2018 at 6:58 PM > > To: "starlingx-discuss at lists.starlingx.io" > .starlingx.io> > > Subject: [Starlingx-discuss] [build][meetings] Meeting minutes > > 11/1/2018 > > > > Build team meeting minutes 11/1/2018 > > > > Attendees > > Ken, Jason, Scott, Memo, Erich, Marcela, Victor, Chuy, Cesar, Luis > > > > > > Cengn Status > > > > -Mirror is now completed and operational, the wiki has been updated > > with the details for Cengn and our partnership, the details and > > specs are already there. > > -The scripts that are related with mirror download are now pointing > > to Cengn repos and are waiting in the queue to be reviewed tested > > and merged, the desired date for fully operational mirror is > > November 5th > > - Now changes to the packages required to build will be caught by > > Cengn mirror within one day, the scripts will try to download first > > from Cengn and if is still not available will try to go get the > > packages from upstream. > > > > Koji follow up > > > > -presentation on a possible scenario hosting Koji and demo on using > > Koji based built packages with our current build scripts. > > -discussion followed up by implementation details led to different > > points of view about the problem we have to solve if there’s any, > > the amount of effort to integrate tooling as we know Koji doesn’t > > solve every use case by itself and where to host a Koji service(we > > are striving to host a centralized service for the whole > > community). > > -The statement we are using to follow thru with Koji versus our > > current script is that we will require a lot of effort to support > > multi OS with the current tools. > > > > We had to defer the topic of mirror script refactored using Python. > > > > We will start a thread on the goals this team has for next release > > on the mailing list. > > > > Regards > > > > Cesar Lara > > Software Engineering Manager > > OpenSource Technology Center > > > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From erich.cordoba.malibran at intel.com Wed Nov 7 15:25:33 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Wed, 7 Nov 2018 15:25:33 +0000 Subject: [Starlingx-discuss] Does openstack-helm-infra needs network access to build? In-Reply-To: References: Message-ID: <0991687c82ff0b3cf79bc70db3830b6ea5ef1f5b.camel@intel.com> On Wed, 2018-11-07 at 22:22 +0800, Hu, Yong wrote: > Hi AI, > We do have this update in build-tools. > The problem was that our build environment is not able to directly > access Google site without a special http/https proxy. This means that for anyone (like us) that lives behind a proxy, the build is broken, unless changes are applied in the mock configuration. I'm not sure if it's good to require network access to build a package. This is similar to python code needing to run pip when a rpm is created, or Golang software using "go get". If the package needs something extra to be build, then there is hidden dependency and we need to provide it in a different way. -Erich > > Regards, > Yong > > On 07/11/2018, 10:14 PM, "Bailey, Henry Albert (Al)" river.com> wrote: > > Do you guys have this commit? > https://github.com/openstack/stx-root/commit/1615f281093af91da3b9 > 98209ff90bbfd0c74350 > > It flips the networking flag to True > > Al > > -----Original Message----- > From: Hu, Yong [mailto:yong.hu at intel.com] > Sent: Tuesday, November 06, 2018 10:50 PM > To: Cordoba Malibran, Erich; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Does openstack-helm-infra needs > network access to build? > > I also met the same problem, and resolved it by adding proxy > settings into “~/cgcs-root/cgcs-centos-repo/mock.cfg.proto”: > config_opts[‘rpmbuild_networking’] = False > + config_opts[‘no_proxy’] = ‘127.0.0.1’ > + config_opts[‘http_proxy’]= ‘http://: _proxy_port>’ > + config_opts[‘https_proxy’]= ‘http:// > :’ > > Here is my screenshot of my build: > 03:35:07 ===== wait for last jobs in iteration 1 to complete > ===== > 03:35:07 building openstack-helm-infra-1.0-3.tis.src.rpm > 03:36:02 End build on ‘b0’: > /localdisk/loadbuild/yhu6/starlingx/std/rpmbuild/SRPMS/openstack- > helm-infra-1.0-3.tis.src.rpm > 03:36:02 Success building openstack-helm-infra-1.0-3.tis.src.rpm > on ‘b0’ (edited) > > I might file a patch to "~/build-tools/repo_files/mock.cfg.proto > b/build-tools/repo_files/mock.cfg.proto", which is the original copy > of “~/cgcs-root/cgcs-centos-repo/mock.cfg.proto". > Though, I also like to see if there is a better solution. > > -yong > > On 07/11/2018, 8:29 AM, "Cordoba Malibran, Erich" malibran at intel.com> wrote: > > Hi all, > > We are seeing a failure today in our build environment. The > openstack- > helm-infra package is failing. Checking the logs it seems > that the > network access is required during building: > > Adding stable repo with URL: https://kubernetes-charts.storag > e.googleapis.com > Error: Looks like "https://kubernetes-charts.storage.googleap > is.com" is not a valid chart repository or cannot be reached: Get htt > ps://kubernetes-charts.storage.googleapis.com/index.yaml: > proxyconnect tcp: dial tcp: lookup on [::1]:53: dial udp > [::1]:53: connect: cannot assign requested address > error: Bad exit status from /var/tmp/rpm-tmp.KecSPl (%build) > > We run the build in an isolated environment without internet > access. > > Is someone seeing something similar? If this is true, then > what would > be the best practice here, do we want network access while > building? or > it should work in an isolated environment? > > Thanks in advance > > -Erich > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx- > discuss > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-disc > uss > > From scott.little at windriver.com Wed Nov 7 15:33:04 2018 From: scott.little at windriver.com (Scott Little) Date: Wed, 7 Nov 2018 10:33:04 -0500 Subject: [Starlingx-discuss] Does openstack-helm-infra needs network access to build? In-Reply-To: References: Message-ID: <2dab59a1-2abc-b305-dfb4-02f7e4092b06@windriver.com> Al, Would it be possible to create build-pkgs --helm-charts .... or build-pkgs --network_required build phase.  A peer to 'std' and 'rt'.  Only enable networking for that subset of builds.  Probably better than enabling networking for the build of all packages. Proxy setup is still required for folks that want to do the container portions of the build. Scott On 18-11-07 09:13 AM, Bailey, Henry Albert (Al) wrote: > Do you guys have this commit? > https://github.com/openstack/stx-root/commit/1615f281093af91da3b998209ff90bbfd0c74350 > > It flips the networking flag to True > > Al > > -----Original Message----- > From: Hu, Yong [mailto:yong.hu at intel.com] > Sent: Tuesday, November 06, 2018 10:50 PM > To: Cordoba Malibran, Erich; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Does openstack-helm-infra needs network access to build? > > I also met the same problem, and resolved it by adding proxy settings into “~/cgcs-root/cgcs-centos-repo/mock.cfg.proto”: > config_opts[‘rpmbuild_networking’] = False > + config_opts[‘no_proxy’] = ‘127.0.0.1’ > + config_opts[‘http_proxy’]= ‘http://:’ > + config_opts[‘https_proxy’]= ‘http:// :’ > > Here is my screenshot of my build: > 03:35:07 ===== wait for last jobs in iteration 1 to complete ===== > 03:35:07 building openstack-helm-infra-1.0-3.tis.src.rpm > 03:36:02 End build on ‘b0’: /localdisk/loadbuild/yhu6/starlingx/std/rpmbuild/SRPMS/openstack-helm-infra-1.0-3.tis.src.rpm > 03:36:02 Success building openstack-helm-infra-1.0-3.tis.src.rpm on ‘b0’ (edited) > > I might file a patch to "~/build-tools/repo_files/mock.cfg.proto b/build-tools/repo_files/mock.cfg.proto", which is the original copy of “~/cgcs-root/cgcs-centos-repo/mock.cfg.proto". > Though, I also like to see if there is a better solution. > > -yong > > On 07/11/2018, 8:29 AM, "Cordoba Malibran, Erich" wrote: > > Hi all, > > We are seeing a failure today in our build environment. The openstack- > helm-infra package is failing. Checking the logs it seems that the > network access is required during building: > > Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com > Error: Looks like "https://kubernetes-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: Get https://kubernetes-charts.storage.googleapis.com/index.yaml: proxyconnect tcp: dial tcp: lookup on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address > error: Bad exit status from /var/tmp/rpm-tmp.KecSPl (%build) > > We run the build in an isolated environment without internet access. > > Is someone seeing something similar? If this is true, then what would > be the best practice here, do we want network access while building? or > it should work in an isolated environment? > > Thanks in advance > > -Erich > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Al.Bailey at windriver.com Wed Nov 7 15:36:58 2018 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Wed, 7 Nov 2018 15:36:58 +0000 Subject: [Starlingx-discuss] Does openstack-helm-infra needs network access to build? In-Reply-To: <2dab59a1-2abc-b305-dfb4-02f7e4092b06@windriver.com> References: <2dab59a1-2abc-b305-dfb4-02f7e4092b06@windriver.com> Message-ID: That sounds like a good approach. Al -----Original Message----- From: Scott Little [mailto:scott.little at windriver.com] Sent: Wednesday, November 07, 2018 10:33 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Does openstack-helm-infra needs network access to build? Al, Would it be possible to create build-pkgs --helm-charts .... or build-pkgs --network_required build phase.  A peer to 'std' and 'rt'.  Only enable networking for that subset of builds.  Probably better than enabling networking for the build of all packages. Proxy setup is still required for folks that want to do the container portions of the build. Scott On 18-11-07 09:13 AM, Bailey, Henry Albert (Al) wrote: > Do you guys have this commit? > https://github.com/openstack/stx-root/commit/1615f281093af91da3b998209ff90bbfd0c74350 > > It flips the networking flag to True > > Al > > -----Original Message----- > From: Hu, Yong [mailto:yong.hu at intel.com] > Sent: Tuesday, November 06, 2018 10:50 PM > To: Cordoba Malibran, Erich; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Does openstack-helm-infra needs network access to build? > > I also met the same problem, and resolved it by adding proxy settings into “~/cgcs-root/cgcs-centos-repo/mock.cfg.proto”: > config_opts[‘rpmbuild_networking’] = False > + config_opts[‘no_proxy’] = ‘127.0.0.1’ > + config_opts[‘http_proxy’]= ‘http://:’ > + config_opts[‘https_proxy’]= ‘http:// :’ > > Here is my screenshot of my build: > 03:35:07 ===== wait for last jobs in iteration 1 to complete ===== > 03:35:07 building openstack-helm-infra-1.0-3.tis.src.rpm > 03:36:02 End build on ‘b0’: /localdisk/loadbuild/yhu6/starlingx/std/rpmbuild/SRPMS/openstack-helm-infra-1.0-3.tis.src.rpm > 03:36:02 Success building openstack-helm-infra-1.0-3.tis.src.rpm on ‘b0’ (edited) > > I might file a patch to "~/build-tools/repo_files/mock.cfg.proto b/build-tools/repo_files/mock.cfg.proto", which is the original copy of “~/cgcs-root/cgcs-centos-repo/mock.cfg.proto". > Though, I also like to see if there is a better solution. > > -yong > > On 07/11/2018, 8:29 AM, "Cordoba Malibran, Erich" wrote: > > Hi all, > > We are seeing a failure today in our build environment. The openstack- > helm-infra package is failing. Checking the logs it seems that the > network access is required during building: > > Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com > Error: Looks like "https://kubernetes-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: Get https://kubernetes-charts.storage.googleapis.com/index.yaml: proxyconnect tcp: dial tcp: lookup on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address > error: Bad exit status from /var/tmp/rpm-tmp.KecSPl (%build) > > We run the build in an isolated environment without internet access. > > Is someone seeing something similar? If this is true, then what would > be the best practice here, do we want network access while building? or > it should work in an isolated environment? > > Thanks in advance > > -Erich > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Wed Nov 7 15:43:19 2018 From: scott.little at windriver.com (Scott Little) Date: Wed, 7 Nov 2018 10:43:19 -0500 Subject: [Starlingx-discuss] [build][meetings] Meeting minutes 11/1/2018 In-Reply-To: <19d4cd748c8d04563ae59889bbaa185af6043637.camel@intel.com> References: <26C1EE58-528C-4F24-89DB-9D3DB6C7E4F2@intel.com> <5720fea7-9b69-8723-d940-a66d23dd5fb2@windriver.com> <19d4cd748c8d04563ae59889bbaa185af6043637.camel@intel.com> Message-ID: Ok, I'll repo sync and try a new Docker. I'll run these exact commands.  My previous docker was over a month old.  Perhaps the difference lies there. For the first pass I'll run using the bug fix in https://review.openstack.org/#/c/615316/  .   I would like your eyes on that review. Scott On 18-11-07 10:16 AM, Cordoba Malibran, Erich wrote: > We have seen this behavior in two different systems. > > The script is run in this way: > > cd stx-tools/centos-mirror-tools > docker build -t stx-mirror -f Dockerfile . > docker run -ti -v $(pwd):/localdisk stx-mirror ./download_mirror.sh > > After run the script, this is what git reports: > > On branch master > Your branch is up to date with 'origin/master'. > > Changes not staged for commit: > (use "git add/rm ..." to update what will be committed) > (use "git checkout -- ..." to discard changes in working directory) > > deleted: centos-mirror-tools/make_stx_mirror_yum_conf.sh > deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-5 > deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-6 > deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Debug-6 > deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-OpsTools > deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-SCLo > deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-Virtualization > deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Security-6 > deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Testing-6 > deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-Cloud-SIG > deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-DOCKER > deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-EPEL-6 > deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-EPEL-7 > deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-FC27 > deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-FC27-primary > deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-FC27-second > deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-FC28 > deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-FC29 > deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-cern > deleted: centos-mirror-tools/rpms_3rdparties.lst > deleted: centos-mirror-tools/rpms_centos.lst > deleted: centos-mirror-tools/rpms_centos3rdparties.lst > deleted: centos-mirror-tools/tarball-dl.lst > deleted: centos-mirror-tools/yum.conf.sample > deleted: centos-mirror-tools/yum.repos.d/StarlingX-Centos-7.2.repo > deleted: centos-mirror-tools/yum.repos.d/StarlingX-Centos-7.3.repo > deleted: centos-mirror-tools/yum.repos.d/StarlingX-Centos-7.4.repo > deleted: centos-mirror-tools/yum.repos.d/StarlingX-Centos-7.5.repo > deleted: centos-mirror-tools/yum.repos.d/StarlingX-EPEL-7.repo > deleted: centos-mirror-tools/yum.repos.d/StarlingX_3rd_buildlogs-seed_centos_org.repo > deleted: centos-mirror-tools/yum.repos.d/StarlingX_3rd_buildlogs_centos_org.repo > deleted: centos-mirror-tools/yum.repos.d/StarlingX_3rd_download_docker_com.repo > deleted: centos-mirror-tools/yum.repos.d/StarlingX_3rd_epel_blizoo_mk.repo > deleted: centos-mirror-tools/yum.repos.d/StarlingX_3rd_ftp_iij_ad_jp.repo > deleted: centos-mirror-tools/yum.repos.d/StarlingX_3rd_linuxsoft_cern_ch.repo > deleted: centos-mirror-tools/yum.repos.d/StarlingX_3rd_www_rpmfind_net.repo > deleted: centos-mirror-tools/yum.repos.d/StarlingX_CentOS-OpenStack-queens.repo > > > On Tue, 2018-11-06 at 16:33 -0500, Scott Little wrote: >> I can't reproduce this, with or without https://review.openstack.org/ >> #/c/615316 >> >> Where you in the container when you ran mirror_downloader.sh? In >> directory /localdisk? >> >> Scott >> >> >> On 18-11-06 11:51 AM, Martinez Landa, Hayde wrote: >>> Hi Ken! >>> >>> We tried mirror_downloader.sh on our Jenkins automated environment >>> and also on >>> my local environment and when it finished running we noticed that >>> the following files were moved: >>> >>> this ones were sent to: “/localdisk/output/stx- >>> r1/CentOS/pike/Binary/x86_64” >>> -rpms_3rdparties.lst >>> -rpms_centos.lst >>> -rpms_centos3rdparties.lst >>> -tarball-dl.lst >>> Same with “yum.repos.d” were sent to: “CentOS/pike/Binary/noarch/” >>> CentOS/pike/Binary/noarch/yum.repos.d/ >>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.2.repo >>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_buildlogs_cento >>> s_org.repo >>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_download_docker >>> _com.repo >>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_CentOS-OpenStack- >>> queens.repo >>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_epel_blizoo_mk. >>> repo >>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_linuxsoft_cern_ >>> ch.repo >>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.3.repo >>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_buildlogs- >>> seed_centos_org.repo >>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_www_rpmfind_net >>> .repo >>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.4.repo >>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-EPEL-7.repo >>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_ftp_iij_ad_jp.r >>> epo >>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.5.repo >>> >>> And finally rpm-gpg-keys sent to: “CentOS/pike/Binary/x86_64” >>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/ >>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC27-primary >>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-SCLo >>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Debug-6 >>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-6 >>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-EPEL-6 >>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Security- >>> 6 >>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG- >>> OpsTools >>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC29 >>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC27 >>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-EPEL-7 >>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-5 >>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-DOCKER >>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-cern >>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG- >>> Virtualization >>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC27-second >>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC28 >>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Testing-6 >>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-Cloud-SIG >>> >>> Is this the expected behavior? >>> >>> I’m currently finishing the build with this mirror, will update >>> once it’s done. >>> >>> Best >>> -Hayde >>> >>> From: "Young, Ken" >>> Date: Monday, November 5, 2018 at 2:43 PM >>> To: "Lara, Cesar" >>> Cc: "starlingx-discuss at lists.starlingx.io" >> .starlingx.io> >>> Subject: Re: [Starlingx-discuss] [build][meetings] Meeting minutes >>> 11/1/2018 >>> >>> Cesar, >>> >>> A quick update on the mirror. The tooling to enable the mirror was >>> merged on Friday. The Wind River used the mirror over the week-end >>> for its builds with no issues. >>> >>> How have your builds gone since Friday? >>> >>> /KenY >>> >>> From: "Lara, Cesar" >>> Date: Thursday, November 1, 2018 at 6:58 PM >>> To: "starlingx-discuss at lists.starlingx.io" >> .starlingx.io> >>> Subject: [Starlingx-discuss] [build][meetings] Meeting minutes >>> 11/1/2018 >>> >>> Build team meeting minutes 11/1/2018 >>> >>> Attendees >>> Ken, Jason, Scott, Memo, Erich, Marcela, Victor, Chuy, Cesar, Luis >>> >>> >>> Cengn Status >>> >>> -Mirror is now completed and operational, the wiki has been updated >>> with the details for Cengn and our partnership, the details and >>> specs are already there. >>> -The scripts that are related with mirror download are now pointing >>> to Cengn repos and are waiting in the queue to be reviewed tested >>> and merged, the desired date for fully operational mirror is >>> November 5th >>> - Now changes to the packages required to build will be caught by >>> Cengn mirror within one day, the scripts will try to download first >>> from Cengn and if is still not available will try to go get the >>> packages from upstream. >>> >>> Koji follow up >>> >>> -presentation on a possible scenario hosting Koji and demo on using >>> Koji based built packages with our current build scripts. >>> -discussion followed up by implementation details led to different >>> points of view about the problem we have to solve if there’s any, >>> the amount of effort to integrate tooling as we know Koji doesn’t >>> solve every use case by itself and where to host a Koji service(we >>> are striving to host a centralized service for the whole >>> community). >>> -The statement we are using to follow thru with Koji versus our >>> current script is that we will require a lot of effort to support >>> multi OS with the current tools. >>> >>> We had to defer the topic of mirror script refactored using Python. >>> >>> We will start a thread on the goals this team has for next release >>> on the mailing list. >>> >>> Regards >>> >>> Cesar Lara >>> Software Engineering Manager >>> OpenSource Technology Center >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus >>> s >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Wed Nov 7 15:58:17 2018 From: scott.little at windriver.com (Scott Little) Date: Wed, 7 Nov 2018 10:58:17 -0500 Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED In-Reply-To: References: <3868FDB4-49FA-4429-8657-7C4FBD0D93C1@gmail.com> <2FD5DDB5A04D264C80D42CA35194914F35DB6397@SHSMSX104.ccr.corp.intel.com> Message-ID: <7f534867-cd40-afa0-89f4-8b8987eea250@windriver.com> Actually I had pretty broad +2/+1 power to most repos, at least initially, to facilitate repo creation and restructuring.  Roughly on par with Dean.  I wasn't that I was a core reviewer in the normal sense.  Just a backup to Dean that can do some of the structural work. If I'm being demoted, fine, as long as that was the intent. Scott On 18-11-05 05:46 PM, Ildiko Vancsa wrote: > Hi Scott, > > I got the following initial list for stx-upstream: > > stx-upstream - Upstream packages > Bob Church (Robert.Church at windriver.com) > Al Bailey (Al.Bailey at windriver.com) > Chris Friesen (Chris.Friesen at windriver.com) > > And so far it got confirmed here: http://lists.starlingx.io/pipermail/starlingx-discuss/2018-November/001742.html > > I’m working with the TLs to double check the lists, however I don’t seem to be able to figure out all the TLs for all the repos at this point, will start a separate thread about that. > > Thanks, > Ildikó > > >> On 2018. Nov 5., at 23:01, Scott Little wrote: >> >> Strange, I used to have +2 powers over stx-upstream a few days ago. Now it seems to be gone. >> >> Please restore. >> >> Thanks >> >> Scott >> >> >> >> On 18-11-05 03:31 PM, McKenna, Jason wrote: >>> Hi Cindy, >>> >>> I think I should be added to stx-integ as well. >>> >>> Thanks in advance, >>> -Jason >>> >>>> -----Original Message----- >>>> From: Saul Wold >>>> Sent: November 5, 2018 3:07 PM >>>> To: Xie, Cindy ; Ildiko Vancsa >>>> ; starlingx-discuss at lists.starlingx.io >>>> Subject: Re: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - >>>> ACTION NEEDED >>>> >>>> >>>> I agree with this, I also think I should be added to stx-root, stx-tools, stx- >>>> manifest and stx-tis-repo as part of the build. >>>> >>>> Thanks >>>> >>>> Sau! >>>> >>>> >>>> On 11/4/18 10:24 PM, Xie, Cindy wrote: >>>>> For stx-integ, this repo was used for non-openstack distro sub-project a lot. >>>> I am hoping that both Saul and Brent can be the core reviewers for it. >>>>> stx-integ - Integration and packaging >>>>> Scott Little (scott.little at windriver.com) >>>>> Bob Church (Robert.Church at windriver.com) >>>>> Don Penney (Don.Penney at windriver.com ) >>>>> Wold, Saul >>>>> Rowsell, Brent >>>>> >>>>> Thx. - cindy >>>>> >>>>> -----Original Message----- >>>>> From: Smith, Tyler [mailto:tyler.smith at windriver.com] >>>>> Sent: Friday, November 2, 2018 11:20 AM >>>>> To: Ildiko Vancsa ; >>>>> starlingx-discuss at lists.starlingx.io >>>>> Subject: Re: [Starlingx-discuss] TLs to sign off on initial core >>>>> reviewer groups - ACTION NEEDED >>>>> >>>>> OK for stx-gui >>>>> >>>>> Thanks, >>>>> Tyler >>>>> >>>>> -----Original Message----- >>>>> From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] >>>>> Sent: Friday, November 2, 2018 1:37 PM >>>>> To: starlingx-discuss at lists.starlingx.io >>>>> Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer >>>>> groups - ACTION NEEDED >>>>> >>>>> Hi Technical Leads, >>>>> >>>>> I started to work on creating the core reviewer groups in Gerrit for each of >>>> the sub-projects in StarlingX and I need your input to complete this task. >>>>> I have an initial list below containing the sub-project repos and the names >>>> of the core reviewers belonging to the groups. Please check your sub-project >>>> and respond with corrections or with an ‘OK’ in case the core team for your >>>> project is listed correctly. >>>>> Please let me know if you have any questions. >>>>> >>>>> Thanks and Best Regards, >>>>> Ildikó >>>>> >>>>> >>>>> stx-clients - client libraries >>>>> Jerry Sun (Jerry.Sun at windriver.com) >>>>> Greg Waines (Greg.Waines at windriver.com) >>>>> >>>>> stx-config - Configuration Management >>>>> Bart Wensley (Barton.Wensley at windriver.com) >>>>> John Kung (John.Kung at windriver.com) >>>>> Don Penney (Don.Penney at windriver.com) >>>>> Bob Church (Robert.Church at windriver.com) >>>>> Chris Friesen (Chris.Friesen at windriver.com) >>>>> >>>>> stx-fault - Fault Management >>>>> Tao Liu (Tao.Liu at windriver.com) >>>>> Al Bailey (Al.Bailey at windriver.com) >>>>> >>>>> stx-integ - Integration and packaging >>>>> Scott Little (scott.little at windriver.com) >>>>> Bob Church (Robert.Church at windriver.com) >>>>> Don Penney (Don.Penney at windriver.com ) >>>>> >>>>> stx-gui - Horizon plugins for new services >>>>> Tyler Smith (Tyler.Smith at windriver.com) >>>>> Angie Wang (Angie.Wang at windriver.com) >>>>> Kristine Bujold (Kristine.Bujold at windriver.com) >>>>> >>>>> stx-ha - High Availability/Service Management >>>>> Bin Qian (Bin.Qian at windriver.com) >>>>> Eric Macdonald (Eric.MacDonald at windriver.com) >>>>> John Kung (John.Kung at windriver.com)TLs to sign off on initial core reviewer groups >>>>> >>>>> stx-metal - Bare Metal Management >>>>> Eric Macdonald (Eric.MacDonald at windriver.com) >>>>> John Kung (John.Kung at windriver.com) >>>>> Tao Liu (Tao.Liu at windriver.com) >>>>> >>>>> stx-nfv - NFVI Orchestration >>>>> Bart Wensley (Barton.Wensley at windriver.com) >>>>> Al Bailey (Al.Bailey at windriver.com) >>>>> Jack Ding (Jack.Ding at windriver.com) >>>>> >>>>> stx-update - Installation/Update/Patching >>>>> Bart Wensley (Barton.Wensley at windriver.com) >>>>> Don Penney (Don.Penney at windriver.com) >>>>> David Sullivan (David.Sullivan at windriver.com) >>>>> >>>>> stx-upstream - Upstream packages >>>>> Bob Church (Robert.Church at windriver.com) >>>>> Al Bailey (Al.Bailey at windriver.com) >>>>> Chris Friesen (Chris.Friesen at windriver.com) >>>>> >>>>> stx-distcloud – Distributed Cloud >>>>> Bart Wensley (Barton.Wensley at windriver.com) >>>>> Brent Rowsell brent.rowsell at windriver.com >>>>> Chris Friesen (Chris.Friesen at windriver.com) >>>>> Dean Troyer dtroyer at gmail.com >>>>> John Kung john.kung at windriver.com >>>>> Saul Wold sgw at linux.intel.com >>>>> >>>>> stx-distcloud-client – Distributed Cloud >>>>> Bart Wensley (Barton.Wensley at windriver.com) >>>>> Chris Friesen (Chris.Friesen at windriver.com) >>>>> John Kung (John.Kung at windriver.com ) >>>>> >>>>> stx-manifest - source manifest to manage the repositories >>>>> Scott Little (scott.little at windriver.com) >>>>> Jason McKenna (Jason.McKenna at windriver.com) >>>>> >>>>> stx-root - build source tree root >>>>> Scott Little (scott.little at windriver.com) >>>>> Jason McKenna (Jason.McKenna at windriver.com) >>>>> >>>>> stx-tis-repo - build support >>>>> Scott Little (scott.little at windriver.com) >>>>> Jason McKenna (Jason.McKenna at windriver.com) >>>>> >>>>> stx-tools - build tools >>>>> Scott Little (scott.little at windriver.com) >>>>> Jason McKenna (Jason.McKenna at windriver.com) >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From erich.cordoba.malibran at intel.com Wed Nov 7 16:02:21 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Wed, 7 Nov 2018 16:02:21 +0000 Subject: [Starlingx-discuss] Does openstack-helm-infra needs network access to build? In-Reply-To: References: <2dab59a1-2abc-b305-dfb4-02f7e4092b06@windriver.com> Message-ID: <94afd921b349cdca968b654f459173c8890a9e93.camel@intel.com> Then this reaises a question, should helm chart creation be a build task (manage by build-pkgs) or a configuration task (managed by config_controller) ? -Erich On Wed, 2018-11-07 at 15:36 +0000, Bailey, Henry Albert (Al) wrote: > That sounds like a good approach. > Al > > -----Original Message----- > From: Scott Little [mailto:scott.little at windriver.com] > Sent: Wednesday, November 07, 2018 10:33 AM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Does openstack-helm-infra needs > network access to build? > > Al, > > Would it be possible to create build-pkgs --helm-charts .... or > build-pkgs --network_required build phase. A peer to 'std' and > 'rt'. > Only enable networking for that subset of builds. Probably better > than > enabling networking for the build of all packages. > > Proxy setup is still required for folks that want to do the > container > portions of the build. > > Scott > > > On 18-11-07 09:13 AM, Bailey, Henry Albert (Al) wrote: > > Do you guys have this commit? > > https://github.com/openstack/stx-root/commit/1615f281093af91da3b998 > > 209ff90bbfd0c74350 > > > > It flips the networking flag to True > > > > Al > > > > -----Original Message----- > > From: Hu, Yong [mailto:yong.hu at intel.com] > > Sent: Tuesday, November 06, 2018 10:50 PM > > To: Cordoba Malibran, Erich; starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] Does openstack-helm-infra needs > > network access to build? > > > > I also met the same problem, and resolved it by adding proxy > > settings into “~/cgcs-root/cgcs-centos-repo/mock.cfg.proto”: > > config_opts[‘rpmbuild_networking’] = False > > + config_opts[‘no_proxy’] = ‘127.0.0.1’ > > + config_opts[‘http_proxy’]= ‘http://: > roxy_port>’ > > + config_opts[‘https_proxy’]= ‘http:// > > :’ > > > > Here is my screenshot of my build: > > 03:35:07 ===== wait for last jobs in iteration 1 to complete ===== > > 03:35:07 building openstack-helm-infra-1.0-3.tis.src.rpm > > 03:36:02 End build on ‘b0’: > > /localdisk/loadbuild/yhu6/starlingx/std/rpmbuild/SRPMS/openstack- > > helm-infra-1.0-3.tis.src.rpm > > 03:36:02 Success building openstack-helm-infra-1.0-3.tis.src.rpm on > > ‘b0’ (edited) > > > > I might file a patch to "~/build-tools/repo_files/mock.cfg.proto > > b/build-tools/repo_files/mock.cfg.proto", which is the original > > copy of “~/cgcs-root/cgcs-centos-repo/mock.cfg.proto". > > Though, I also like to see if there is a better solution. > > > > -yong > > > > On 07/11/2018, 8:29 AM, "Cordoba Malibran, Erich" > alibran at intel.com> wrote: > > > > Hi all, > > > > We are seeing a failure today in our build environment. The > > openstack- > > helm-infra package is failing. Checking the logs it seems that > > the > > network access is required during building: > > > > Adding stable repo with URL: https://kubernetes-charts.storage > > .googleapis.com > > Error: Looks like "https://kubernetes-charts.storage.googleapi > > s.com" is not a valid chart repository or cannot be reached: Get ht > > tps://kubernetes-charts.storage.googleapis.com/index.yaml: > > proxyconnect tcp: dial tcp: lookup on [::1]:53: dial > > udp [::1]:53: connect: cannot assign requested address > > error: Bad exit status from /var/tmp/rpm-tmp.KecSPl (%build) > > > > We run the build in an isolated environment without internet > > access. > > > > Is someone seeing something similar? If this is true, then > > what would > > be the best practice here, do we want network access while > > building? or > > it should work in an isolated environment? > > > > Thanks in advance > > > > -Erich > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-d > > iscuss > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ildiko.vancsa at gmail.com Wed Nov 7 16:16:58 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 7 Nov 2018 17:16:58 +0100 Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED In-Reply-To: <7f534867-cd40-afa0-89f4-8b8987eea250@windriver.com> References: <3868FDB4-49FA-4429-8657-7C4FBD0D93C1@gmail.com> <2FD5DDB5A04D264C80D42CA35194914F35DB6397@SHSMSX104.ccr.corp.intel.com> <7f534867-cd40-afa0-89f4-8b8987eea250@windriver.com> Message-ID: <39A510CA-B13E-4DA7-BE77-331D06173B6D@gmail.com> Hi Scott, On the technical side we had one starlingx-core group setup for the community in Gerrit. This group was assigned to every initial stx-* repo which gave everyone on that group +2 rights in all those repositories. As we are moving forward and formalizing the sub-project teams and overall project governance we got to the steps of defining the core reviewer groups for each sub-project and the repositories they manage which is the change you are experiencing now. It is not about demoting anybody but rather identifying those individuals for each sub-project and relevant repositories who have the duties of looking after the mission and scope of the sub-project as well as architecture and code quality by performing code reviews and being able to approve patches in Gerrit. I believe StarlingX is already big and complex enough that we don’t expect anyone to be on top of what is happening in every single sub-project and repo on code-level but rather focus on one or a few sub-projects. In case you feel that you are actively participating in some projects and should retain your core reviewer rights please reach out the the Technical Lead of the sub-project to discuss and fix this. Please let me know if you have further questions. Thanks and Best Regards, Ildikó > On 2018. Nov 7., at 16:58, Scott Little wrote: > > Actually I had pretty broad +2/+1 power to most repos, at least initially, to facilitate repo creation and restructuring. Roughly on par with Dean. I wasn't that I was a core reviewer in the normal sense. Just a backup to Dean that can do some of the structural work. > > If I'm being demoted, fine, as long as that was the intent. > > Scott > > > On 18-11-05 05:46 PM, Ildiko Vancsa wrote: >> Hi Scott, >> >> I got the following initial list for stx-upstream: >> >> stx-upstream - Upstream packages >> Bob Church (Robert.Church at windriver.com) >> Al Bailey (Al.Bailey at windriver.com) >> Chris Friesen (Chris.Friesen at windriver.com) >> >> And so far it got confirmed here: http://lists.starlingx.io/pipermail/starlingx-discuss/2018-November/001742.html >> >> I’m working with the TLs to double check the lists, however I don’t seem to be able to figure out all the TLs for all the repos at this point, will start a separate thread about that. >> >> Thanks, >> Ildikó >> >> >>> On 2018. Nov 5., at 23:01, Scott Little wrote: >>> >>> Strange, I used to have +2 powers over stx-upstream a few days ago. Now it seems to be gone. >>> >>> Please restore. >>> >>> Thanks >>> >>> Scott >>> >>> >>> >>> On 18-11-05 03:31 PM, McKenna, Jason wrote: >>>> Hi Cindy, >>>> >>>> I think I should be added to stx-integ as well. >>>> >>>> Thanks in advance, >>>> -Jason >>>> >>>>> -----Original Message----- >>>>> From: Saul Wold >>>>> Sent: November 5, 2018 3:07 PM >>>>> To: Xie, Cindy ; Ildiko Vancsa >>>>> ; starlingx-discuss at lists.starlingx.io >>>>> Subject: Re: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - >>>>> ACTION NEEDED >>>>> >>>>> >>>>> I agree with this, I also think I should be added to stx-root, stx-tools, stx- >>>>> manifest and stx-tis-repo as part of the build. >>>>> >>>>> Thanks >>>>> >>>>> Sau! >>>>> >>>>> >>>>> On 11/4/18 10:24 PM, Xie, Cindy wrote: >>>>>> For stx-integ, this repo was used for non-openstack distro sub-project a lot. >>>>> I am hoping that both Saul and Brent can be the core reviewers for it. >>>>>> stx-integ - Integration and packaging >>>>>> Scott Little (scott.little at windriver.com) >>>>>> Bob Church (Robert.Church at windriver.com) >>>>>> Don Penney (Don.Penney at windriver.com ) >>>>>> Wold, Saul >>>>>> Rowsell, Brent >>>>>> >>>>>> Thx. - cindy >>>>>> >>>>>> -----Original Message----- >>>>>> From: Smith, Tyler [mailto:tyler.smith at windriver.com] >>>>>> Sent: Friday, November 2, 2018 11:20 AM >>>>>> To: Ildiko Vancsa ; >>>>>> starlingx-discuss at lists.starlingx.io >>>>>> Subject: Re: [Starlingx-discuss] TLs to sign off on initial core >>>>>> reviewer groups - ACTION NEEDED >>>>>> >>>>>> OK for stx-gui >>>>>> >>>>>> Thanks, >>>>>> Tyler >>>>>> >>>>>> -----Original Message----- >>>>>> From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] >>>>>> Sent: Friday, November 2, 2018 1:37 PM >>>>>> To: starlingx-discuss at lists.starlingx.io >>>>>> Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer >>>>>> groups - ACTION NEEDED >>>>>> >>>>>> Hi Technical Leads, >>>>>> >>>>>> I started to work on creating the core reviewer groups in Gerrit for each of >>>>> the sub-projects in StarlingX and I need your input to complete this task. >>>>>> I have an initial list below containing the sub-project repos and the names >>>>> of the core reviewers belonging to the groups. Please check your sub-project >>>>> and respond with corrections or with an ‘OK’ in case the core team for your >>>>> project is listed correctly. >>>>>> Please let me know if you have any questions. >>>>>> >>>>>> Thanks and Best Regards, >>>>>> Ildikó >>>>>> >>>>>> >>>>>> stx-clients - client libraries >>>>>> Jerry Sun (Jerry.Sun at windriver.com) >>>>>> Greg Waines (Greg.Waines at windriver.com) >>>>>> >>>>>> stx-config - Configuration Management >>>>>> Bart Wensley (Barton.Wensley at windriver.com) >>>>>> John Kung (John.Kung at windriver.com) >>>>>> Don Penney (Don.Penney at windriver.com) >>>>>> Bob Church (Robert.Church at windriver.com) >>>>>> Chris Friesen (Chris.Friesen at windriver.com) >>>>>> >>>>>> stx-fault - Fault Management >>>>>> Tao Liu (Tao.Liu at windriver.com) >>>>>> Al Bailey (Al.Bailey at windriver.com) >>>>>> >>>>>> stx-integ - Integration and packaging >>>>>> Scott Little (scott.little at windriver.com) >>>>>> Bob Church (Robert.Church at windriver.com) >>>>>> Don Penney (Don.Penney at windriver.com ) >>>>>> >>>>>> stx-gui - Horizon plugins for new services >>>>>> Tyler Smith (Tyler.Smith at windriver.com) >>>>>> Angie Wang (Angie.Wang at windriver.com) >>>>>> Kristine Bujold (Kristine.Bujold at windriver.com) >>>>>> >>>>>> stx-ha - High Availability/Service Management >>>>>> Bin Qian (Bin.Qian at windriver.com) >>>>>> Eric Macdonald (Eric.MacDonald at windriver.com) >>>>>> John Kung (John.Kung at windriver.com)TLs to sign off on initial core reviewer groups >>>>>> >>>>>> stx-metal - Bare Metal Management >>>>>> Eric Macdonald (Eric.MacDonald at windriver.com) >>>>>> John Kung (John.Kung at windriver.com) >>>>>> Tao Liu (Tao.Liu at windriver.com) >>>>>> >>>>>> stx-nfv - NFVI Orchestration >>>>>> Bart Wensley (Barton.Wensley at windriver.com) >>>>>> Al Bailey (Al.Bailey at windriver.com) >>>>>> Jack Ding (Jack.Ding at windriver.com) >>>>>> >>>>>> stx-update - Installation/Update/Patching >>>>>> Bart Wensley (Barton.Wensley at windriver.com) >>>>>> Don Penney (Don.Penney at windriver.com) >>>>>> David Sullivan (David.Sullivan at windriver.com) >>>>>> >>>>>> stx-upstream - Upstream packages >>>>>> Bob Church (Robert.Church at windriver.com) >>>>>> Al Bailey (Al.Bailey at windriver.com) >>>>>> Chris Friesen (Chris.Friesen at windriver.com) >>>>>> >>>>>> stx-distcloud – Distributed Cloud >>>>>> Bart Wensley (Barton.Wensley at windriver.com) >>>>>> Brent Rowsell brent.rowsell at windriver.com >>>>>> Chris Friesen (Chris.Friesen at windriver.com) >>>>>> Dean Troyer dtroyer at gmail.com >>>>>> John Kung john.kung at windriver.com >>>>>> Saul Wold sgw at linux.intel.com >>>>>> >>>>>> stx-distcloud-client – Distributed Cloud >>>>>> Bart Wensley (Barton.Wensley at windriver.com) >>>>>> Chris Friesen (Chris.Friesen at windriver.com) >>>>>> John Kung (John.Kung at windriver.com ) >>>>>> >>>>>> stx-manifest - source manifest to manage the repositories >>>>>> Scott Little (scott.little at windriver.com) >>>>>> Jason McKenna (Jason.McKenna at windriver.com) >>>>>> >>>>>> stx-root - build source tree root >>>>>> Scott Little (scott.little at windriver.com) >>>>>> Jason McKenna (Jason.McKenna at windriver.com) >>>>>> >>>>>> stx-tis-repo - build support >>>>>> Scott Little (scott.little at windriver.com) >>>>>> Jason McKenna (Jason.McKenna at windriver.com) >>>>>> >>>>>> stx-tools - build tools >>>>>> Scott Little (scott.little at windriver.com) >>>>>> Jason McKenna (Jason.McKenna at windriver.com) >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Starlingx-discuss mailing list >>>>>> Starlingx-discuss at lists.starlingx.io >>>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>>> _______________________________________________ >>>>>> Starlingx-discuss mailing list >>>>>> Starlingx-discuss at lists.starlingx.io >>>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>>> _______________________________________________ >>>>>> Starlingx-discuss mailing list >>>>>> Starlingx-discuss at lists.starlingx.io >>>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>>> >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > From Al.Bailey at windriver.com Wed Nov 7 16:22:59 2018 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Wed, 7 Nov 2018 16:22:59 +0000 Subject: [Starlingx-discuss] Does openstack-helm-infra needs network access to build? In-Reply-To: <94afd921b349cdca968b654f459173c8890a9e93.camel@intel.com> References: <2dab59a1-2abc-b305-dfb4-02f7e4092b06@windriver.com> <94afd921b349cdca968b654f459173c8890a9e93.camel@intel.com> Message-ID: This review should get people with limited network access building again https://review.openstack.org/#/c/616237 Al -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Wednesday, November 07, 2018 11:02 AM To: Little, Scott; Bailey, Henry Albert (Al); starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Does openstack-helm-infra needs network access to build? Then this reaises a question, should helm chart creation be a build task (manage by build-pkgs) or a configuration task (managed by config_controller) ? -Erich On Wed, 2018-11-07 at 15:36 +0000, Bailey, Henry Albert (Al) wrote: > That sounds like a good approach. > Al > > -----Original Message----- > From: Scott Little [mailto:scott.little at windriver.com] > Sent: Wednesday, November 07, 2018 10:33 AM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Does openstack-helm-infra needs > network access to build? > > Al, > > Would it be possible to create build-pkgs --helm-charts .... or > build-pkgs --network_required build phase. A peer to 'std' and > 'rt'. > Only enable networking for that subset of builds. Probably better > than > enabling networking for the build of all packages. > > Proxy setup is still required for folks that want to do the > container > portions of the build. > > Scott > > > On 18-11-07 09:13 AM, Bailey, Henry Albert (Al) wrote: > > Do you guys have this commit? > > https://github.com/openstack/stx-root/commit/1615f281093af91da3b998 > > 209ff90bbfd0c74350 > > > > It flips the networking flag to True > > > > Al > > > > -----Original Message----- > > From: Hu, Yong [mailto:yong.hu at intel.com] > > Sent: Tuesday, November 06, 2018 10:50 PM > > To: Cordoba Malibran, Erich; starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] Does openstack-helm-infra needs > > network access to build? > > > > I also met the same problem, and resolved it by adding proxy > > settings into “~/cgcs-root/cgcs-centos-repo/mock.cfg.proto”: > > config_opts[‘rpmbuild_networking’] = False > > + config_opts[‘no_proxy’] = ‘127.0.0.1’ > > + config_opts[‘http_proxy’]= ‘http://: > roxy_port>’ > > + config_opts[‘https_proxy’]= ‘http:// > > :’ > > > > Here is my screenshot of my build: > > 03:35:07 ===== wait for last jobs in iteration 1 to complete ===== > > 03:35:07 building openstack-helm-infra-1.0-3.tis.src.rpm > > 03:36:02 End build on ‘b0’: > > /localdisk/loadbuild/yhu6/starlingx/std/rpmbuild/SRPMS/openstack- > > helm-infra-1.0-3.tis.src.rpm > > 03:36:02 Success building openstack-helm-infra-1.0-3.tis.src.rpm on > > ‘b0’ (edited) > > > > I might file a patch to "~/build-tools/repo_files/mock.cfg.proto > > b/build-tools/repo_files/mock.cfg.proto", which is the original > > copy of “~/cgcs-root/cgcs-centos-repo/mock.cfg.proto". > > Though, I also like to see if there is a better solution. > > > > -yong > > > > On 07/11/2018, 8:29 AM, "Cordoba Malibran, Erich" > alibran at intel.com> wrote: > > > > Hi all, > > > > We are seeing a failure today in our build environment. The > > openstack- > > helm-infra package is failing. Checking the logs it seems that > > the > > network access is required during building: > > > > Adding stable repo with URL: https://kubernetes-charts.storage > > .googleapis.com > > Error: Looks like "https://kubernetes-charts.storage.googleapi > > s.com" is not a valid chart repository or cannot be reached: Get ht > > tps://kubernetes-charts.storage.googleapis.com/index.yaml: > > proxyconnect tcp: dial tcp: lookup on [::1]:53: dial > > udp [::1]:53: connect: cannot assign requested address > > error: Bad exit status from /var/tmp/rpm-tmp.KecSPl (%build) > > > > We run the build in an isolated environment without internet > > access. > > > > Is someone seeing something similar? If this is true, then > > what would > > be the best practice here, do we want network access while > > building? or > > it should work in an isolated environment? > > > > Thanks in advance > > > > -Erich > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-d > > iscuss > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dtroyer at gmail.com Wed Nov 7 17:25:28 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Wed, 7 Nov 2018 11:25:28 -0600 Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED In-Reply-To: <7f534867-cd40-afa0-89f4-8b8987eea250@windriver.com> References: <3868FDB4-49FA-4429-8657-7C4FBD0D93C1@gmail.com> <2FD5DDB5A04D264C80D42CA35194914F35DB6397@SHSMSX104.ccr.corp.intel.com> <7f534867-cd40-afa0-89f4-8b8987eea250@windriver.com> Message-ID: On Wed, Nov 7, 2018 at 9:58 AM Scott Little wrote: > Actually I had pretty broad +2/+1 power to most repos, at least > initially, to facilitate repo creation and restructuring. Roughly on > par with Dean. I wasn't that I was a core reviewer in the normal > sense. Just a backup to Dean that can do some of the structural work. > > If I'm being demoted, fine, as long as that was the intent. The intent was to get the right people with the responsibility into the right groups. FWIW I no longer have +2 in any of the code repos in Gerrit [0] now that we're basically up and running. The TL's have management of their groups and enough people know their way around to fix the things I needed to handle in the beginning that I can let go there. In emergency cases where core team members may be unavailable we have the OpenStack Infrastructure team to turn to for help in IRC #openstack-infra. dt [0] Just docs, specs and release now. This is a Good Thing(TM). -- Dean Troyer dtroyer at gmail.com From scott.little at windriver.com Wed Nov 7 18:21:45 2018 From: scott.little at windriver.com (Scott Little) Date: Wed, 7 Nov 2018 13:21:45 -0500 Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED In-Reply-To: References: <3868FDB4-49FA-4429-8657-7C4FBD0D93C1@gmail.com> <2FD5DDB5A04D264C80D42CA35194914F35DB6397@SHSMSX104.ccr.corp.intel.com> <7f534867-cd40-afa0-89f4-8b8987eea250@windriver.com> Message-ID: Ok. I wasn't complaining. Just wanted to make sure it was all intentional.  It was strange to have +2 power for one iteration of a review, but not the next. Scott PS.   If the Koji train starts building momentum, there will be a lot more restructuring work to do.  A lot more gits to manage. It'll be interesting. On 18-11-07 12:25 PM, Dean Troyer wrote: > On Wed, Nov 7, 2018 at 9:58 AM Scott Little wrote: >> Actually I had pretty broad +2/+1 power to most repos, at least >> initially, to facilitate repo creation and restructuring. Roughly on >> par with Dean. I wasn't that I was a core reviewer in the normal >> sense. Just a backup to Dean that can do some of the structural work. >> >> If I'm being demoted, fine, as long as that was the intent. > The intent was to get the right people with the responsibility into > the right groups. FWIW I no longer have +2 in any of the code repos > in Gerrit [0] now that we're basically up and running. The TL's have > management of their groups and enough people know their way around to > fix the things I needed to handle in the beginning that I can let go > there. > > In emergency cases where core team members may be unavailable we have > the OpenStack Infrastructure team to turn to for help in IRC > #openstack-infra. > > dt > > [0] Just docs, specs and release now. This is a Good Thing(TM). > From ildiko.vancsa at gmail.com Wed Nov 7 18:32:37 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 7 Nov 2018 19:32:37 +0100 Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED In-Reply-To: References: <3868FDB4-49FA-4429-8657-7C4FBD0D93C1@gmail.com> <2FD5DDB5A04D264C80D42CA35194914F35DB6397@SHSMSX104.ccr.corp.intel.com> <7f534867-cd40-afa0-89f4-8b8987eea250@windriver.com> Message-ID: Hi Scott, It came up on the TSC call two or three weeks ago and I started to execute as I got responses from TL’s. Sorry if it felt sudden we probably should’ve given a bit longer heads up on the mailing list. As for the Koji changes, I believe that will be an excellent opportunity to see how the cross-sub-project synchronization and collaboration works within the community and improve on the parts that are less efficient. Thanks and Best Regards, Ildikó > On 2018. Nov 7., at 19:21, Scott Little wrote: > > Ok. > > I wasn't complaining. Just wanted to make sure it was all intentional. It was strange to have +2 power for one iteration of a review, but not the next. > > Scott > > PS. If the Koji train starts building momentum, there will be a lot more restructuring work to do. A lot more gits to manage. It'll be interesting. > > > On 18-11-07 12:25 PM, Dean Troyer wrote: >> On Wed, Nov 7, 2018 at 9:58 AM Scott Little wrote: >>> Actually I had pretty broad +2/+1 power to most repos, at least >>> initially, to facilitate repo creation and restructuring. Roughly on >>> par with Dean. I wasn't that I was a core reviewer in the normal >>> sense. Just a backup to Dean that can do some of the structural work. >>> >>> If I'm being demoted, fine, as long as that was the intent. >> The intent was to get the right people with the responsibility into >> the right groups. FWIW I no longer have +2 in any of the code repos >> in Gerrit [0] now that we're basically up and running. The TL's have >> management of their groups and enough people know their way around to >> fix the things I needed to handle in the beginning that I can let go >> there. >> >> In emergency cases where core team members may be unavailable we have >> the OpenStack Infrastructure team to turn to for help in IRC >> #openstack-infra. >> >> dt >> >> [0] Just docs, specs and release now. This is a Good Thing(TM). >> > From scott.little at windriver.com Wed Nov 7 18:39:23 2018 From: scott.little at windriver.com (Scott Little) Date: Wed, 7 Nov 2018 13:39:23 -0500 Subject: [Starlingx-discuss] [build][meetings] Meeting minutes 11/1/2018 In-Reply-To: References: <26C1EE58-528C-4F24-89DB-9D3DB6C7E4F2@intel.com> <5720fea7-9b69-8723-d940-a66d23dd5fb2@windriver.com> <19d4cd748c8d04563ae59889bbaa185af6043637.camel@intel.com> Message-ID: Can't reproduce with a fresh container and https://review.openstack.org/#/c/615316/.  I'll try without the update. Scott On 18-11-07 10:43 AM, Scott Little wrote: > Ok, I'll repo sync and try a new Docker. I'll run these exact > commands.  My previous docker was over a month old.  Perhaps the > difference lies there. > > For the first pass I'll run using the bug fix in > https://review.openstack.org/#/c/615316/  .   I would like your eyes > on that review. > > Scott > > > On 18-11-07 10:16 AM, Cordoba Malibran, Erich wrote: >> We have seen this behavior in two different systems. >> >> The script is run in this way: >> >> cd stx-tools/centos-mirror-tools >> docker build -t stx-mirror -f Dockerfile . >> docker run -ti -v $(pwd):/localdisk stx-mirror ./download_mirror.sh >> >> After run the script, this is what git reports: >> >> On branch master >> Your branch is up to date with 'origin/master'. >> >> Changes not staged for commit: >>    (use "git add/rm ..." to update what will be committed) >>    (use "git checkout -- ..." to discard changes in working >> directory) >> >>     deleted:    centos-mirror-tools/make_stx_mirror_yum_conf.sh >>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-5 >>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-6 >>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Debug-6 >>     deleted: >> centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-OpsTools >>     deleted: >> centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-SCLo >>     deleted: >> centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-Virtualization >>     deleted: >> centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Security-6 >>     deleted: >> centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Testing-6 >>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-Cloud-SIG >>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-DOCKER >>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-EPEL-6 >>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-EPEL-7 >>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-FC27 >>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-FC27-primary >>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-FC27-second >>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-FC28 >>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-FC29 >>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-cern >>     deleted:    centos-mirror-tools/rpms_3rdparties.lst >>     deleted:    centos-mirror-tools/rpms_centos.lst >>     deleted:    centos-mirror-tools/rpms_centos3rdparties.lst >>     deleted:    centos-mirror-tools/tarball-dl.lst >>     deleted:    centos-mirror-tools/yum.conf.sample >>     deleted: centos-mirror-tools/yum.repos.d/StarlingX-Centos-7.2.repo >>     deleted: centos-mirror-tools/yum.repos.d/StarlingX-Centos-7.3.repo >>     deleted: centos-mirror-tools/yum.repos.d/StarlingX-Centos-7.4.repo >>     deleted: centos-mirror-tools/yum.repos.d/StarlingX-Centos-7.5.repo >>     deleted: centos-mirror-tools/yum.repos.d/StarlingX-EPEL-7.repo >>     deleted: >> centos-mirror-tools/yum.repos.d/StarlingX_3rd_buildlogs-seed_centos_org.repo >>     deleted: >> centos-mirror-tools/yum.repos.d/StarlingX_3rd_buildlogs_centos_org.repo >>     deleted: >> centos-mirror-tools/yum.repos.d/StarlingX_3rd_download_docker_com.repo >>     deleted: >> centos-mirror-tools/yum.repos.d/StarlingX_3rd_epel_blizoo_mk.repo >>     deleted: >> centos-mirror-tools/yum.repos.d/StarlingX_3rd_ftp_iij_ad_jp.repo >>     deleted: >> centos-mirror-tools/yum.repos.d/StarlingX_3rd_linuxsoft_cern_ch.repo >>     deleted: >> centos-mirror-tools/yum.repos.d/StarlingX_3rd_www_rpmfind_net.repo >>     deleted: >> centos-mirror-tools/yum.repos.d/StarlingX_CentOS-OpenStack-queens.repo >> >> >> On Tue, 2018-11-06 at 16:33 -0500, Scott Little wrote: >>> I can't reproduce this, with or without https://review.openstack.org/ >>> #/c/615316 >>> >>> Where you in the container when you ran mirror_downloader.sh? In >>> directory /localdisk? >>> >>> Scott >>> >>> >>> On 18-11-06 11:51 AM, Martinez Landa, Hayde wrote: >>>> Hi Ken! >>>>   We tried mirror_downloader.sh on our Jenkins automated environment >>>> and also on >>>> my local environment and when it finished running we noticed that >>>> the following files were moved: >>>>   this ones were sent to: “/localdisk/output/stx- >>>> r1/CentOS/pike/Binary/x86_64” >>>> -rpms_3rdparties.lst >>>> -rpms_centos.lst >>>> -rpms_centos3rdparties.lst >>>> -tarball-dl.lst >>>> Same with “yum.repos.d” were sent to: “CentOS/pike/Binary/noarch/” >>>> CentOS/pike/Binary/noarch/yum.repos.d/ >>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.2.repo >>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_buildlogs_cento >>>> s_org.repo >>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_download_docker >>>> _com.repo >>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_CentOS-OpenStack- >>>> queens.repo >>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_epel_blizoo_mk. >>>> repo >>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_linuxsoft_cern_ >>>> ch.repo >>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.3.repo >>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_buildlogs- >>>> seed_centos_org.repo >>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_www_rpmfind_net >>>> .repo >>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.4.repo >>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-EPEL-7.repo >>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_ftp_iij_ad_jp.r >>>> epo >>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.5.repo >>>>   And finally rpm-gpg-keys sent to: “CentOS/pike/Binary/x86_64” >>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/ >>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC27-primary >>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-SCLo >>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Debug-6 >>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-6 >>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-EPEL-6 >>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Security- >>>> 6 >>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG- >>>> OpsTools >>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC29 >>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC27 >>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-EPEL-7 >>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-5 >>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-DOCKER >>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-cern >>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG- >>>> Virtualization >>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC27-second >>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC28 >>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Testing-6 >>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-Cloud-SIG >>>>   Is this the expected behavior? >>>>   I’m currently finishing the build with this mirror, will update >>>> once it’s done. >>>>   Best >>>> -Hayde >>>>   From: "Young, Ken" >>>> Date: Monday, November 5, 2018 at 2:43 PM >>>> To: "Lara, Cesar" >>>> Cc: "starlingx-discuss at lists.starlingx.io" >>> .starlingx.io> >>>> Subject: Re: [Starlingx-discuss] [build][meetings] Meeting minutes >>>> 11/1/2018 >>>>   Cesar, >>>>   A quick update on the mirror.  The tooling to enable the mirror was >>>> merged on Friday.  The Wind River used the mirror over the week-end >>>> for its builds with no issues. >>>>   How have your builds gone since Friday? >>>>   /KenY >>>>   From: "Lara, Cesar" >>>> Date: Thursday, November 1, 2018 at 6:58 PM >>>> To: "starlingx-discuss at lists.starlingx.io" >>> .starlingx.io> >>>> Subject: [Starlingx-discuss] [build][meetings] Meeting minutes >>>> 11/1/2018 >>>>   Build team meeting minutes 11/1/2018 >>>>   Attendees >>>> Ken, Jason, Scott, Memo, Erich, Marcela, Victor, Chuy, Cesar, Luis >>>>     Cengn Status >>>>   -Mirror is now completed and operational, the wiki has been updated >>>> with the details for Cengn and our partnership, the details and >>>> specs are already there. >>>> -The scripts that are related with mirror download are now pointing >>>> to Cengn repos and are waiting in the queue to be reviewed tested >>>> and merged, the desired date for fully operational mirror is >>>> November 5th >>>> - Now changes to the packages required to build will be caught by >>>> Cengn mirror within one day, the scripts will try to download first >>>> from Cengn and if is still not available will try to go get the >>>> packages from upstream. >>>>   Koji follow up >>>>   -presentation on a possible scenario hosting Koji and demo on using >>>> Koji based built packages with our current build scripts. >>>> -discussion followed up by implementation details led to different >>>> points of view about the problem we have to solve if there’s any, >>>> the amount of effort to integrate tooling as we know Koji doesn’t >>>> solve every use case by itself and where to host a Koji service(we >>>> are striving to host a centralized service for the whole >>>> community). >>>> -The statement we are using to follow thru with Koji versus our >>>> current script is that we will require a lot of effort to support >>>> multi OS with the current tools. >>>>   We had to defer the topic of mirror script refactored using Python. >>>>   We will start a thread on the goals this team has for next release >>>> on the mailing list. >>>>   Regards >>>>   Cesar Lara >>>> Software Engineering Manager >>>> OpenSource Technology Center >>>> >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus >>>> s >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Wed Nov 7 18:41:24 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 7 Nov 2018 18:41:24 +0000 Subject: [Starlingx-discuss] Community call Nov 7th 2018 Message-ID: <9A85D2917C58154C960D95352B22818BB1EA1A49@fmsmsx117.amr.corp.intel.com> Agenda and notes - November 7th call: * Ghada to run this call next week due to the Summit. * Do we have any requests from the OpenStack User Committee? Prep for meeting at the summit. - Ian o The UC is an elected committee parallel to the TC in the OpenStack project, who drive user POV and the Operators meetup. o Follow up to Ian's meeting with the UC in Denver o Team does not have much input for Ian today. Looking to establish a good working relationship with the UC. * March release planning - TSC is reviewing the Ethercalc - any other input incoming? * Bug status We have 74 open bugs, most assigned, some need to be triaged o https://bugs.launchpad.net/starlingx * Sub-project status / help needed / issues? o Build - build mirror set up at Cengn. Debug of some issues is in progress. The build is broken for people who live behind proxies since it now requires network access. To be discussed at the next build meeting. o Test - four configurations automated in the virtual env in addition to multi-node. 90 test cases automated. Test planning for 2019.03 beginning. o Config, HA, Metal, Update, Fault, GUI, NFV - most activity in the Flock is in Containers right now. o Dist Cloud - Yesterday at the Edge Computing meeting regarding the reference arch discussed at the PTG. Some uses cases will need the synchronized Keystone solution for small edge clouds that don't need identity providers on each edge node. WG accepting the need for an option for this. Spec for distcloud coming soon. o Docs - Team working on how to version the docs between the release branch and master. Contributor guide for the Docs is on line. Feel free to update the docs. o Distro - working on planning for 2019.03. Agreed on quite a few items to target to the release. Making some progress on non-openstack patches. 23 tasks identified for refactoring in one SB entry. 3 patches merged, 6 under review. Ceph upgrade to be discussed with the TSC this week. Core reviewers defined. o Security - on-going discussions on Security issues - team has worked the bug backlog down from 15 to 5. Focused on two policy items - draft document for how we do vulnerability management on the wiki - please review. New Banned C function policy coming together o Containers - Code is starting to flow. Only takes effect when the system is configued with --kubernetes, will remove option once the code is more stable. Changes likely needed to test automation and some documents (e.g. installation, build). Most of the activity in the Flock right now is tied to container support. We have support for BM and VM containers today with Magnum and Ironic. In the new architecture work will be needed to ensure that all still works after the changes. o Releases - taking a well-deserved break o Networking - focused on neutron patch upstreaming - 3 patches merged upstream. Analysis complete for identifying good candidates for upstream. Removing 2 custom features for QoSand port security in Neutron to align more closely with upstream. Helping with Container team for networking changes needed. There are a couple specs on the Neutron side that are being reviewed. o MultiOS - Pursuing 3 tracks - CI/CD for Clear which for now is internal. DevStack enablement for Clear Linux is being done within the StarlingX staging tree. Plug ins for the Flock services are being done within each Flock service. Our goal is to have DevStack running on Clear with the Flock services starting. No intention now to have the services do anything other than stand up and not fall down. Don't expect API functions to work. o DevStack - See above o Zuul - we have 6 stories in SB but no activity seen. o Python2->3 - non-openstack covered in the distro.openstack team. Goal is to be 100% P3 compliant - analysis in progress. -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Wed Nov 7 20:00:41 2018 From: scott.little at windriver.com (Scott Little) Date: Wed, 7 Nov 2018 15:00:41 -0500 Subject: [Starlingx-discuss] [build][meetings] Meeting minutes 11/1/2018 In-Reply-To: References: <26C1EE58-528C-4F24-89DB-9D3DB6C7E4F2@intel.com> <5720fea7-9b69-8723-d940-a66d23dd5fb2@windriver.com> <19d4cd748c8d04563ae59889bbaa185af6043637.camel@intel.com> Message-ID: I can reproduce  without https://review.openstack.org/#/c/615316/. and no pre-existing output. So the fix is in covered by https://review.openstack.org/#/c/615316/ Scott On 18-11-07 01:39 PM, Scott Little wrote: > Can't reproduce with a fresh container and > https://review.openstack.org/#/c/615316/.  I'll try without the update. > > > Scott > > > On 18-11-07 10:43 AM, Scott Little wrote: >> Ok, I'll repo sync and try a new Docker. I'll run these exact >> commands.  My previous docker was over a month old.  Perhaps the >> difference lies there. >> >> For the first pass I'll run using the bug fix in >> https://review.openstack.org/#/c/615316/  .   I would like your eyes >> on that review. >> >> Scott >> >> >> On 18-11-07 10:16 AM, Cordoba Malibran, Erich wrote: >>> We have seen this behavior in two different systems. >>> >>> The script is run in this way: >>> >>> cd stx-tools/centos-mirror-tools >>> docker build -t stx-mirror -f Dockerfile . >>> docker run -ti -v $(pwd):/localdisk stx-mirror ./download_mirror.sh >>> >>> After run the script, this is what git reports: >>> >>> On branch master >>> Your branch is up to date with 'origin/master'. >>> >>> Changes not staged for commit: >>>    (use "git add/rm ..." to update what will be committed) >>>    (use "git checkout -- ..." to discard changes in working >>> directory) >>> >>>     deleted: centos-mirror-tools/make_stx_mirror_yum_conf.sh >>>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-5 >>>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-6 >>>     deleted: >>> centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Debug-6 >>>     deleted: >>> centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-OpsTools >>>     deleted: >>> centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-SCLo >>>     deleted: >>> centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-Virtualization >>>     deleted: >>> centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Security-6 >>>     deleted: >>> centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Testing-6 >>>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-Cloud-SIG >>>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-DOCKER >>>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-EPEL-6 >>>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-EPEL-7 >>>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-FC27 >>>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-FC27-primary >>>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-FC27-second >>>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-FC28 >>>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-FC29 >>>     deleted: centos-mirror-tools/rpm-gpg-keys/RPM-GPG-KEY-cern >>>     deleted:    centos-mirror-tools/rpms_3rdparties.lst >>>     deleted:    centos-mirror-tools/rpms_centos.lst >>>     deleted:    centos-mirror-tools/rpms_centos3rdparties.lst >>>     deleted:    centos-mirror-tools/tarball-dl.lst >>>     deleted:    centos-mirror-tools/yum.conf.sample >>>     deleted: centos-mirror-tools/yum.repos.d/StarlingX-Centos-7.2.repo >>>     deleted: centos-mirror-tools/yum.repos.d/StarlingX-Centos-7.3.repo >>>     deleted: centos-mirror-tools/yum.repos.d/StarlingX-Centos-7.4.repo >>>     deleted: centos-mirror-tools/yum.repos.d/StarlingX-Centos-7.5.repo >>>     deleted: centos-mirror-tools/yum.repos.d/StarlingX-EPEL-7.repo >>>     deleted: >>> centos-mirror-tools/yum.repos.d/StarlingX_3rd_buildlogs-seed_centos_org.repo >>>     deleted: >>> centos-mirror-tools/yum.repos.d/StarlingX_3rd_buildlogs_centos_org.repo >>>     deleted: >>> centos-mirror-tools/yum.repos.d/StarlingX_3rd_download_docker_com.repo >>>     deleted: >>> centos-mirror-tools/yum.repos.d/StarlingX_3rd_epel_blizoo_mk.repo >>>     deleted: >>> centos-mirror-tools/yum.repos.d/StarlingX_3rd_ftp_iij_ad_jp.repo >>>     deleted: >>> centos-mirror-tools/yum.repos.d/StarlingX_3rd_linuxsoft_cern_ch.repo >>>     deleted: >>> centos-mirror-tools/yum.repos.d/StarlingX_3rd_www_rpmfind_net.repo >>>     deleted: >>> centos-mirror-tools/yum.repos.d/StarlingX_CentOS-OpenStack-queens.repo >>> >>> >>> On Tue, 2018-11-06 at 16:33 -0500, Scott Little wrote: >>>> I can't reproduce this, with or without https://review.openstack.org/ >>>> #/c/615316 >>>> >>>> Where you in the container when you ran mirror_downloader.sh? In >>>> directory /localdisk? >>>> >>>> Scott >>>> >>>> >>>> On 18-11-06 11:51 AM, Martinez Landa, Hayde wrote: >>>>> Hi Ken! >>>>>   We tried mirror_downloader.sh on our Jenkins automated environment >>>>> and also on >>>>> my local environment and when it finished running we noticed that >>>>> the following files were moved: >>>>>   this ones were sent to: “/localdisk/output/stx- >>>>> r1/CentOS/pike/Binary/x86_64” >>>>> -rpms_3rdparties.lst >>>>> -rpms_centos.lst >>>>> -rpms_centos3rdparties.lst >>>>> -tarball-dl.lst >>>>> Same with “yum.repos.d” were sent to: “CentOS/pike/Binary/noarch/” >>>>> CentOS/pike/Binary/noarch/yum.repos.d/ >>>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.2.repo >>>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_buildlogs_cento >>>>> s_org.repo >>>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_download_docker >>>>> _com.repo >>>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_CentOS-OpenStack- >>>>> queens.repo >>>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_epel_blizoo_mk. >>>>> repo >>>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_linuxsoft_cern_ >>>>> ch.repo >>>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.3.repo >>>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_buildlogs- >>>>> seed_centos_org.repo >>>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_www_rpmfind_net >>>>> .repo >>>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.4.repo >>>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-EPEL-7.repo >>>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_ftp_iij_ad_jp.r >>>>> epo >>>>> CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.5.repo >>>>>   And finally rpm-gpg-keys sent to: “CentOS/pike/Binary/x86_64” >>>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/ >>>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC27-primary >>>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-SCLo >>>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Debug-6 >>>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-6 >>>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-EPEL-6 >>>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Security- >>>>> 6 >>>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG- >>>>> OpsTools >>>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC29 >>>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC27 >>>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-EPEL-7 >>>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-5 >>>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-DOCKER >>>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-cern >>>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG- >>>>> Virtualization >>>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC27-second >>>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC28 >>>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Testing-6 >>>>> CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-Cloud-SIG >>>>>   Is this the expected behavior? >>>>>   I’m currently finishing the build with this mirror, will update >>>>> once it’s done. >>>>>   Best >>>>> -Hayde >>>>>   From: "Young, Ken" >>>>> Date: Monday, November 5, 2018 at 2:43 PM >>>>> To: "Lara, Cesar" >>>>> Cc: "starlingx-discuss at lists.starlingx.io" >>>> .starlingx.io> >>>>> Subject: Re: [Starlingx-discuss] [build][meetings] Meeting minutes >>>>> 11/1/2018 >>>>>   Cesar, >>>>>   A quick update on the mirror.  The tooling to enable the mirror was >>>>> merged on Friday.  The Wind River used the mirror over the week-end >>>>> for its builds with no issues. >>>>>   How have your builds gone since Friday? >>>>>   /KenY >>>>>   From: "Lara, Cesar" >>>>> Date: Thursday, November 1, 2018 at 6:58 PM >>>>> To: "starlingx-discuss at lists.starlingx.io" >>>> .starlingx.io> >>>>> Subject: [Starlingx-discuss] [build][meetings] Meeting minutes >>>>> 11/1/2018 >>>>>   Build team meeting minutes 11/1/2018 >>>>>   Attendees >>>>> Ken, Jason, Scott, Memo, Erich, Marcela, Victor, Chuy, Cesar, Luis >>>>>     Cengn Status >>>>>   -Mirror is now completed and operational, the wiki has been updated >>>>> with the details for Cengn and our partnership, the details and >>>>> specs are already there. >>>>> -The scripts that are related with mirror download are now pointing >>>>> to Cengn repos and are waiting in the queue to be reviewed tested >>>>> and merged, the desired date for fully operational mirror is >>>>> November 5th >>>>> - Now changes to the packages required to build will be caught by >>>>> Cengn mirror within one day, the scripts will try to download first >>>>> from Cengn and if is still not available will try to go get the >>>>> packages from upstream. >>>>>   Koji follow up >>>>>   -presentation on a possible scenario hosting Koji and demo on using >>>>> Koji based built packages with our current build scripts. >>>>> -discussion followed up by implementation details led to different >>>>> points of view about the problem we have to solve if there’s any, >>>>> the amount of effort to integrate tooling as we know Koji doesn’t >>>>> solve every use case by itself and where to host a Koji service(we >>>>> are striving to host a centralized service for the whole >>>>> community). >>>>> -The statement we are using to follow thru with Koji versus our >>>>> current script is that we will require a lot of effort to support >>>>> multi OS with the current tools. >>>>>   We had to defer the topic of mirror script refactored using Python. >>>>>   We will start a thread on the goals this team has for next release >>>>> on the mailing list. >>>>>   Regards >>>>>   Cesar Lara >>>>> Software Engineering Manager >>>>> OpenSource Technology Center >>>>> >>>>> >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus >>>>> s >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ildiko.vancsa at gmail.com Wed Nov 7 20:39:27 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 7 Nov 2018 21:39:27 +0100 Subject: [Starlingx-discuss] StarlingX slide template Message-ID: <0B8F4BA6-7278-49C5-B2B8-E687F36CAD1E@gmail.com> Hi StarlingX Community, I would like to draw your attention to the new slide template that our design team has just uploaded to the website. You can find links on the FAQ page to download it in Keynote or PowerPoint format: https://www.starlingx.io/faq/ Hope you like it! :) Best Regards, Ildikó From cesar.lara at intel.com Wed Nov 7 22:51:36 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Wed, 7 Nov 2018 22:51:36 +0000 Subject: [Starlingx-discuss] [TLs][PLs][TSC] Sub-project and git repo mapping seems to be incomplete In-Reply-To: References: Message-ID: <0B566C62EC792145B40E29EFEBF1AB471055C3F6@fmsmsx104.amr.corp.intel.com> I do agree on the repos that should be owned by the build team I would like to propose Erich Cordoba as core reviewer for those repos Regards Cesar Lara -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Tuesday, November 6, 2018 7:31 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [TLs][PLs][TSC] Sub-project and git repo mapping seems to be incomplete As TL for the Build and Distro non-Openstack sub-projects, I think that the following Repos should belong as follows: Build: - stx-tools - stx-root - stx-manifest (I think) The Non-Openstack Distro should contain: - stx-integ There are some other communities members that should be added as Core reviewers once the correct ownership at the TL level is set. Any concerns from the TSC on this list. I would have replied last week, but had no VPN until midday Monday. Thanks Sau! On 11/5/18 2:55 PM, Ildiko Vancsa wrote: > Hi, > > While I was working on getting the initial core reviewer teams setup in Gerrit I realized that not all repositories seem to be covered by sub-project teams or even if they are it is not documented clearly. > > Currently we have information about the main project on the docs > website under governance: > https://docs.starlingx.io/governance/reference/tsc/projects/index.html > And we have further information on the wiki about sub-projects: > https://wiki.openstack.org/wiki/StarlingX > > Some repositories such as stx-upstream does not seem to be listed on either of the above links which makes it hard to identify which sub-project team maintains it. > > I would like to ask the Project and Technical Leads as well as the TSC to please help to look into this and make the mapping a full coverage that is also easily accessible. As we have started to fill up the documentation website with information I would suggest to extend the project list under the governance section that I linked in above. > > Thanks and Best Regards, > Ildikó > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cesar.lara at intel.com Wed Nov 7 22:51:57 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Wed, 7 Nov 2018 22:51:57 +0000 Subject: [Starlingx-discuss] [build][meetings] Agenda for 11/8/2018 Message-ID: <0B566C62EC792145B40E29EFEBF1AB471055C415@fmsmsx104.amr.corp.intel.com> Build team meeting Agenda for 11/8/2018 - Cengn mirror follow up - Build system proposal and tools - TL and repos owned by Build team - Planning for next release Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Thu Nov 8 02:32:50 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 8 Nov 2018 02:32:50 +0000 Subject: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 In-Reply-To: <9700A18779F35F49AF027300A49E7C765FE3B2B9@SHSMSX101.ccr.corp.intel.com> References: <2F61A2101B4FD447A683EF7E362CF9421C63E2181F@RSI-NOD-EXMDB6.india.rsystems.com> <3a8a02b2-624d-6f91-5dbd-b20d3fab0e16@windriver.com> <9700A18779F35F49AF027300A49E7C765FE3B2B9@SHSMSX101.ccr.corp.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C765FE3B6AF@SHSMSX101.ccr.corp.intel.com> Hi all, Anybody has +2 for stx-tools, please help review patch and W+1 for https://review.openstack.org/616062 . Otherwise it will break build, since https://review.openstack.org/616061 is already merged. Thanks. Best Regards Shuicheng -----Original Message----- From: Lin, Shuicheng Sent: Wednesday, November 7, 2018 12:29 PM To: Scott Little ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 Hi all, I created a story for it: https://storyboard.openstack.org/#!/story/2004282 And here is the code. Please help review it: https://review.openstack.org/616061 https://review.openstack.org/616062 I have done build and deploy test. Please share me if there is any more test need be done. Thanks. Best Regards Shuicheng -----Original Message----- From: Lin, Shuicheng Sent: Wednesday, November 7, 2018 9:34 AM To: 'Scott Little' ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 Hi all, Do we have bug/story to track the issue? I prefer to upgrade the lighttpd src rpm to 1.4.51 to solve it. Best Regards Shuicheng -----Original Message----- From: Scott Little [mailto:scott.little at windriver.com] Sent: Saturday, November 3, 2018 4:23 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 Try updating your stx-tools and running download_mirror.sh again. Alternatively, you can find it here ... http://mirror.starlingx.cengn.ca/mirror/centos/epel/dl.fedoraproject.org/pub/epel/7/SRPMS/Packages/l/lighttpd-1.4.50-1.el7.src.rpm Scott On 18-11-02 05:19 AM, Rajesh Jha wrote: > Hi, > > > We were trying to pick up patches for some issues which we had > reported like SSH not working and failing to attach data interface from controller to compute nodes. We failed to make the build. at step 2 of section Download Packages¶ from https://docs.starlingx.io/developer_guide/index.html#build-the-centos-mirror-repository document. > when we run download_mirror.sh from the container There is one package which fails to download lighttpd-1.4.50-1.el7.src.rpm which is there in rpms_centos.lst. Since this version is not there on any mirror on internet, the version available is lighttpd-1.4.51-1.el7.src.rpm so we updated the file rpms_centos.lst and rpms_centos3rdparties.lst with lighttpd-1.4.51-1.el7.x86_64.rpm instead. Ran the download_mirror.sh again. Now everything is fine except it is failing in build-pkgs step with the following error. > > b6: ERROR: build_dir (415): Invalid srpm path 'mirror:Source/lighttpd-1.4.50-1.el7.src.rpm', evaluated as '/localdisk/designer/builder/starlingx/cgcs-root/cgcs-centos-repo/Source/lighttpd-1.4.50-1.el7.src.rpm', found in '/localdisk/designer/builder/starlingx/cgcs-root/stx/stx-integ/base/lighttpd/centos/srpm_path' > > now we are stuck and unable to build. Any suggestions would be welcome. > > on a general note, had a quick query how much time the incremental > build is taking in general. Because we follow the steps for > incremental build after step git clone > https://git.starlingx.io/stx-tools > > and then we build the container image and all steps after that which is also taking 3 to 4 hours. Am I doing the incremental build properly?? > > Best Regards, > Rajesh Jha > > > The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, please immediately alert the sender by reply e-mail and then delete this message. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. R Systems has taken every reasonable precaution to minimize the risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cindy.xie at intel.com Thu Nov 8 03:54:20 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Thu, 8 Nov 2018 03:54:20 +0000 Subject: [Starlingx-discuss] [TLs][PLs][TSC] Sub-project and git repo mapping seems to be incomplete In-Reply-To: <0B566C62EC792145B40E29EFEBF1AB471055C3F6@fmsmsx104.amr.corp.intel.com> References: <0B566C62EC792145B40E29EFEBF1AB471055C3F6@fmsmsx104.amr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35DBA2F7@SHSMSX104.ccr.corp.intel.com> Cesar, I'd like to propose Yong Hu being the core reviewers for those repos as well. Thanks. - cindy -----Original Message----- From: Lara, Cesar [mailto:cesar.lara at intel.com] Sent: Thursday, November 8, 2018 6:52 AM To: Saul Wold ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [TLs][PLs][TSC] Sub-project and git repo mapping seems to be incomplete I do agree on the repos that should be owned by the build team I would like to propose Erich Cordoba as core reviewer for those repos Regards Cesar Lara -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Tuesday, November 6, 2018 7:31 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [TLs][PLs][TSC] Sub-project and git repo mapping seems to be incomplete As TL for the Build and Distro non-Openstack sub-projects, I think that the following Repos should belong as follows: Build: - stx-tools - stx-root - stx-manifest (I think) The Non-Openstack Distro should contain: - stx-integ There are some other communities members that should be added as Core reviewers once the correct ownership at the TL level is set. Any concerns from the TSC on this list. I would have replied last week, but had no VPN until midday Monday. Thanks Sau! On 11/5/18 2:55 PM, Ildiko Vancsa wrote: > Hi, > > While I was working on getting the initial core reviewer teams setup in Gerrit I realized that not all repositories seem to be covered by sub-project teams or even if they are it is not documented clearly. > > Currently we have information about the main project on the docs > website under governance: > https://docs.starlingx.io/governance/reference/tsc/projects/index.html > And we have further information on the wiki about sub-projects: > https://wiki.openstack.org/wiki/StarlingX > > Some repositories such as stx-upstream does not seem to be listed on either of the above links which makes it hard to identify which sub-project team maintains it. > > I would like to ask the Project and Technical Leads as well as the TSC to please help to look into this and make the mapping a full coverage that is also easily accessible. As we have started to fill up the documentation website with information I would suggest to extend the project list under the governance section that I linked in above. > > Thanks and Best Regards, > Ildikó > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From sgw at linux.intel.com Thu Nov 8 05:06:11 2018 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 7 Nov 2018 21:06:11 -0800 Subject: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 In-Reply-To: <9700A18779F35F49AF027300A49E7C765FE3B6AF@SHSMSX101.ccr.corp.intel.com> References: <2F61A2101B4FD447A683EF7E362CF9421C63E2181F@RSI-NOD-EXMDB6.india.rsystems.com> <3a8a02b2-624d-6f91-5dbd-b20d3fab0e16@windriver.com> <9700A18779F35F49AF027300A49E7C765FE3B2B9@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765FE3B6AF@SHSMSX101.ccr.corp.intel.com> Message-ID: <1513234c-d202-7d62-d291-c3f2ebf37441@linux.intel.com> On 11/7/18 6:32 PM, Lin, Shuicheng wrote: > Hi all, > Anybody has +2 for stx-tools, please help review patch and W+1 for https://review.openstack.org/616062 . > Otherwise it will break build, since https://review.openstack.org/616061 is already merged. > Thanks. > Did you not set the Depends-On Correctly? We need to make sure that they are ordered correctly and blocked until the right one merges first in the future. Sau! > > Best Regards > Shuicheng > > > -----Original Message----- > From: Lin, Shuicheng > Sent: Wednesday, November 7, 2018 12:29 PM > To: Scott Little ; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 > > Hi all, > I created a story for it: > https://storyboard.openstack.org/#!/story/2004282 > > And here is the code. Please help review it: > https://review.openstack.org/616061 > https://review.openstack.org/616062 > I have done build and deploy test. Please share me if there is any more test need be done. > Thanks. > > Best Regards > Shuicheng > > > -----Original Message----- > From: Lin, Shuicheng > Sent: Wednesday, November 7, 2018 9:34 AM > To: 'Scott Little' ; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 > > Hi all, > Do we have bug/story to track the issue? > I prefer to upgrade the lighttpd src rpm to 1.4.51 to solve it. > > > Best Regards > Shuicheng > > > -----Original Message----- > From: Scott Little [mailto:scott.little at windriver.com] > Sent: Saturday, November 3, 2018 4:23 AM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 > > Try updating your stx-tools and running download_mirror.sh again. > > Alternatively, you can find it here ... > > http://mirror.starlingx.cengn.ca/mirror/centos/epel/dl.fedoraproject.org/pub/epel/7/SRPMS/Packages/l/lighttpd-1.4.50-1.el7.src.rpm > > Scott > > > On 18-11-02 05:19 AM, Rajesh Jha wrote: >> Hi, >> >> >> We were trying to pick up patches for some issues which we had >> reported like SSH not working and failing to attach data interface from controller to compute nodes. We failed to make the build. at step 2 of section Download Packages¶ from https://docs.starlingx.io/developer_guide/index.html#build-the-centos-mirror-repository document. >> when we run download_mirror.sh from the container There is one package which fails to download lighttpd-1.4.50-1.el7.src.rpm which is there in rpms_centos.lst. Since this version is not there on any mirror on internet, the version available is lighttpd-1.4.51-1.el7.src.rpm so we updated the file rpms_centos.lst and rpms_centos3rdparties.lst with lighttpd-1.4.51-1.el7.x86_64.rpm instead. Ran the download_mirror.sh again. Now everything is fine except it is failing in build-pkgs step with the following error. >> >> b6: ERROR: build_dir (415): Invalid srpm path 'mirror:Source/lighttpd-1.4.50-1.el7.src.rpm', evaluated as '/localdisk/designer/builder/starlingx/cgcs-root/cgcs-centos-repo/Source/lighttpd-1.4.50-1.el7.src.rpm', found in '/localdisk/designer/builder/starlingx/cgcs-root/stx/stx-integ/base/lighttpd/centos/srpm_path' >> >> now we are stuck and unable to build. Any suggestions would be welcome. >> >> on a general note, had a quick query how much time the incremental >> build is taking in general. Because we follow the steps for >> incremental build after step git clone >> https://git.starlingx.io/stx-tools >> >> and then we build the container image and all steps after that which is also taking 3 to 4 hours. Am I doing the incremental build properly?? >> >> Best Regards, >> Rajesh Jha >> >> >> The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, please immediately alert the sender by reply e-mail and then delete this message. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. R Systems has taken every reasonable precaution to minimize the risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From shuicheng.lin at intel.com Thu Nov 8 05:12:01 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 8 Nov 2018 05:12:01 +0000 Subject: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 In-Reply-To: <1513234c-d202-7d62-d291-c3f2ebf37441@linux.intel.com> References: <2F61A2101B4FD447A683EF7E362CF9421C63E2181F@RSI-NOD-EXMDB6.india.rsystems.com> <3a8a02b2-624d-6f91-5dbd-b20d3fab0e16@windriver.com> <9700A18779F35F49AF027300A49E7C765FE3B2B9@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765FE3B6AF@SHSMSX101.ccr.corp.intel.com> <1513234c-d202-7d62-d291-c3f2ebf37441@linux.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C765FE3B753@SHSMSX101.ccr.corp.intel.com> Hi Saul, The two patches need be merged together, so it is like A and B depends on each other. But currently in gerrit/zuul, we cannot make patch depends on each other. It is a limitation I think. So I just set A depends on B. Best Regards Shuicheng -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Thursday, November 8, 2018 1:06 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 On 11/7/18 6:32 PM, Lin, Shuicheng wrote: > Hi all, > Anybody has +2 for stx-tools, please help review patch and W+1 for https://review.openstack.org/616062 . > Otherwise it will break build, since https://review.openstack.org/616061 is already merged. > Thanks. > Did you not set the Depends-On Correctly? We need to make sure that they are ordered correctly and blocked until the right one merges first in the future. Sau! > > Best Regards > Shuicheng > > > -----Original Message----- > From: Lin, Shuicheng > Sent: Wednesday, November 7, 2018 12:29 PM > To: Scott Little ; > starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] Build failure on lastest build > Sterling 31/10/2018 > > Hi all, > I created a story for it: > https://storyboard.openstack.org/#!/story/2004282 > > And here is the code. Please help review it: > https://review.openstack.org/616061 > https://review.openstack.org/616062 > I have done build and deploy test. Please share me if there is any more test need be done. > Thanks. > > Best Regards > Shuicheng > > > -----Original Message----- > From: Lin, Shuicheng > Sent: Wednesday, November 7, 2018 9:34 AM > To: 'Scott Little' ; > starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] Build failure on lastest build > Sterling 31/10/2018 > > Hi all, > Do we have bug/story to track the issue? > I prefer to upgrade the lighttpd src rpm to 1.4.51 to solve it. > > > Best Regards > Shuicheng > > > -----Original Message----- > From: Scott Little [mailto:scott.little at windriver.com] > Sent: Saturday, November 3, 2018 4:23 AM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Build failure on lastest build > Sterling 31/10/2018 > > Try updating your stx-tools and running download_mirror.sh again. > > Alternatively, you can find it here ... > > http://mirror.starlingx.cengn.ca/mirror/centos/epel/dl.fedoraproject.o > rg/pub/epel/7/SRPMS/Packages/l/lighttpd-1.4.50-1.el7.src.rpm > > Scott > > > On 18-11-02 05:19 AM, Rajesh Jha wrote: >> Hi, >> >> >> We were trying to pick up patches for some issues which we had >> reported like SSH not working and failing to attach data interface from controller to compute nodes. We failed to make the build. at step 2 of section Download Packages¶ from https://docs.starlingx.io/developer_guide/index.html#build-the-centos-mirror-repository document. >> when we run download_mirror.sh from the container There is one package which fails to download lighttpd-1.4.50-1.el7.src.rpm which is there in rpms_centos.lst. Since this version is not there on any mirror on internet, the version available is lighttpd-1.4.51-1.el7.src.rpm so we updated the file rpms_centos.lst and rpms_centos3rdparties.lst with lighttpd-1.4.51-1.el7.x86_64.rpm instead. Ran the download_mirror.sh again. Now everything is fine except it is failing in build-pkgs step with the following error. >> >> b6: ERROR: build_dir (415): Invalid srpm path 'mirror:Source/lighttpd-1.4.50-1.el7.src.rpm', evaluated as '/localdisk/designer/builder/starlingx/cgcs-root/cgcs-centos-repo/Source/lighttpd-1.4.50-1.el7.src.rpm', found in '/localdisk/designer/builder/starlingx/cgcs-root/stx/stx-integ/base/lighttpd/centos/srpm_path' >> >> now we are stuck and unable to build. Any suggestions would be welcome. >> >> on a general note, had a quick query how much time the incremental >> build is taking in general. Because we follow the steps for >> incremental build after step git clone >> https://git.starlingx.io/stx-tools >> >> and then we build the container image and all steps after that which is also taking 3 to 4 hours. Am I doing the incremental build properly?? >> >> Best Regards, >> Rajesh Jha >> >> >> The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, please immediately alert the sender by reply e-mail and then delete this message. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. R Systems has taken every reasonable precaution to minimize the risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From jose.perez.carranza at intel.com Thu Nov 8 14:56:00 2018 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Thu, 8 Nov 2018 14:56:00 +0000 Subject: [Starlingx-discuss] Second controller on degraded for long time - Duplex Virtual Message-ID: <0A5D9A624DF90343892F8F3FE7DE525A2A8FC437@fmsmsx101.amr.corp.intel.com> Hi I setup a Duplex virtual environment and I noticed that after installation and provisioning of second controller (controller-1) this one stays in Degraded for long time (~ 1 hour), and alarm 400.001 is being displayed [1], Is this normal behavior? Is here a way to take out the controller-1 from 'degraded' to 'available' faster? 1- http://paste.openstack.org/show/734425/ Regards, José From Stefan.Dinescu at windriver.com Thu Nov 8 15:00:33 2018 From: Stefan.Dinescu at windriver.com (Dinescu, Stefan) Date: Thu, 8 Nov 2018 15:00:33 +0000 Subject: [Starlingx-discuss] Second controller on degraded for long time - Duplex Virtual In-Reply-To: <0A5D9A624DF90343892F8F3FE7DE525A2A8FC437@fmsmsx101.amr.corp.intel.com> References: <0A5D9A624DF90343892F8F3FE7DE525A2A8FC437@fmsmsx101.amr.corp.intel.com> Message-ID: Hello, Depending on the size of your cinder partition and network speed between the two controller nodes, cinder make take some time to sync as it is usually the biggest partition. you can use "drbd-overview" to see the progress of the sync. Thanks, Stefan ________________________________________ From: Perez Carranza, Jose [jose.perez.carranza at intel.com] Sent: Thursday, November 08, 2018 4:56 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] Second controller on degraded for long time - Duplex Virtual Hi I setup a Duplex virtual environment and I noticed that after installation and provisioning of second controller (controller-1) this one stays in Degraded for long time (~ 1 hour), and alarm 400.001 is being displayed [1], Is this normal behavior? Is here a way to take out the controller-1 from 'degraded' to 'available' faster? 1- http://paste.openstack.org/show/734425/ Regards, José _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dtroyer at gmail.com Thu Nov 8 15:56:14 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Thu, 8 Nov 2018 09:56:14 -0600 Subject: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 In-Reply-To: <9700A18779F35F49AF027300A49E7C765FE3B753@SHSMSX101.ccr.corp.intel.com> References: <2F61A2101B4FD447A683EF7E362CF9421C63E2181F@RSI-NOD-EXMDB6.india.rsystems.com> <3a8a02b2-624d-6f91-5dbd-b20d3fab0e16@windriver.com> <9700A18779F35F49AF027300A49E7C765FE3B2B9@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765FE3B6AF@SHSMSX101.ccr.corp.intel.com> <1513234c-d202-7d62-d291-c3f2ebf37441@linux.intel.com> <9700A18779F35F49AF027300A49E7C765FE3B753@SHSMSX101.ccr.corp.intel.com> Message-ID: On Wed, Nov 7, 2018 at 11:12 PM Lin, Shuicheng wrote: > The two patches need be merged together, so it is like A and B depends on each other. > But currently in gerrit/zuul, we cannot make patch depends on each other. It is a limitation I think. > So I just set A depends on B. In this situation the best approach is to get A approved first. It will go through the gate pipeline but will not merge until B is approved. When B gets through the gate pipeline they will both merge close together. It is still not at exactly the same time but is gets close. You do not have to wait until A is done before approving B, you just want it to get started enough earlier so B does not finish ahead of it. This minimizes the gap between the merges. dt -- Dean Troyer dtroyer at gmail.com From erich.cordoba.malibran at intel.com Thu Nov 8 16:39:18 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Thu, 8 Nov 2018 16:39:18 +0000 Subject: [Starlingx-discuss] [build] Project atomic Message-ID: Hi all, I was just in research mode for building options and I found the Project Atomic[0] It seems interesting the way they build that project and the focus on containerization. There are different flavors of Atomic, CentOS Atomic, Fedora Silverblue[1] (Fedora CoreOS in the near future). I hope you can find it interesting. -Erich [0] https://www.projectatomic.io [1] https://silverblue.fedoraproject.org From Jason.McKenna at windriver.com Thu Nov 8 17:15:08 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Thu, 8 Nov 2018 17:15:08 +0000 Subject: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 In-Reply-To: References: <2F61A2101B4FD447A683EF7E362CF9421C63E2181F@RSI-NOD-EXMDB6.india.rsystems.com> <3a8a02b2-624d-6f91-5dbd-b20d3fab0e16@windriver.com> <9700A18779F35F49AF027300A49E7C765FE3B2B9@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765FE3B6AF@SHSMSX101.ccr.corp.intel.com> <1513234c-d202-7d62-d291-c3f2ebf37441@linux.intel.com> <9700A18779F35F49AF027300A49E7C765FE3B753@SHSMSX101.ccr.corp.intel.com> Message-ID: Hi StarlingX, One possible workaround particular for the case of modifying the lst files are to use 3 commits: A - Adds the new source rpm to the .lst file in stx-tools B - Changes the code in [your git] to use the new source RPM C - Removes the old source rpm from the .lst file in stx-tools C Depends-On B B Depends-On A The only downside is that for some window, you might have two versions of the source rpm in your workspace, eating an extra few MB of disk space. -Jason > -----Original Message----- > From: Dean Troyer > Sent: November 8, 2018 10:56 AM > To: Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Build failure on lastest build Sterling > 31/10/2018 > > On Wed, Nov 7, 2018 at 11:12 PM Lin, Shuicheng > wrote: > > The two patches need be merged together, so it is like A and B depends on > each other. > > But currently in gerrit/zuul, we cannot make patch depends on each other. > It is a limitation I think. > > So I just set A depends on B. > > In this situation the best approach is to get A approved first. It will go > through the gate pipeline but will not merge until B is approved. When B > gets through the gate pipeline they will both merge close together. It is still > not at exactly the same time but is gets close. > > You do not have to wait until A is done before approving B, you just want it to > get started enough earlier so B does not finish ahead of it. This minimizes the > gap between the merges. > > dt > > -- > > Dean Troyer > dtroyer at gmail.com > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Thu Nov 8 17:44:33 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 8 Nov 2018 17:44:33 +0000 Subject: [Starlingx-discuss] Requesting WF +1 in stx-config Message-ID: <9A85D2917C58154C960D95352B22818BB1EA24E1@fmsmsx117.amr.corp.intel.com> Review https://review.openstack.org/#/c/595865/ is waiting for WF+1. It has +2's from Bart Wensley and John Kung. Can this be merged please? brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Thu Nov 8 17:49:39 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 8 Nov 2018 17:49:39 +0000 Subject: [Starlingx-discuss] Requesting WF +1 in stx-config In-Reply-To: <9A85D2917C58154C960D95352B22818BB1EA24E1@fmsmsx117.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BB1EA24E1@fmsmsx117.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BB1EA2507@fmsmsx117.amr.corp.intel.com> A couple more related to DevStack... Review https://review.openstack.org/#/c/614804/ in stx-integ needs one more +2 and a WF+1. Can this be reviewed and merged please too? Review https://review.openstack.org/#/c/614244/ in stx-update needs one more +2 and a WF +1 too. brucej From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, November 8, 2018 9:45 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Requesting WF +1 in stx-config Review https://review.openstack.org/#/c/595865/ is waiting for WF+1. It has +2's from Bart Wensley and John Kung. Can this be merged please? brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Barton.Wensley at windriver.com Thu Nov 8 17:56:15 2018 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Thu, 8 Nov 2018 17:56:15 +0000 Subject: [Starlingx-discuss] Requesting WF +1 in stx-config In-Reply-To: <9A85D2917C58154C960D95352B22818BB1EA2507@fmsmsx117.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BB1EA24E1@fmsmsx117.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BB1EA2507@fmsmsx117.amr.corp.intel.com> Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA2D4D3@ALA-MBD.corp.ad.wrs.com> I have approved 614244 and 595865. You will need a core from stx-integ to approve 614804. Bart From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: November 8, 2018 12:50 PM To: Jones, Bruce E; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Requesting WF +1 in stx-config A couple more related to DevStack... Review https://review.openstack.org/#/c/614804/ in stx-integ needs one more +2 and a WF+1. Can this be reviewed and merged please too? Review https://review.openstack.org/#/c/614244/ in stx-update needs one more +2 and a WF +1 too. brucej From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, November 8, 2018 9:45 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Requesting WF +1 in stx-config Review https://review.openstack.org/#/c/595865/ is waiting for WF+1. It has +2's from Bart Wensley and John Kung. Can this be merged please? brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Robert.Church at windriver.com Thu Nov 8 18:11:17 2018 From: Robert.Church at windriver.com (Church, Robert) Date: Thu, 8 Nov 2018 18:11:17 +0000 Subject: [Starlingx-discuss] Requesting WF +1 in stx-config Message-ID: <24B4BD7A-007D-4FF3-8C68-A7BB9E7B9A1B@windriver.com> >> You will need a core from stx-integ to approve 614804 Done.. Bob. From: "Wensley, Barton" Date: Thursday, November 8, 2018 at 11:56 AM To: "Jones, Bruce E" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Requesting WF +1 in stx-config I have approved 614244 and 595865. You will need a core from stx-integ to approve 614804. Bart From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: November 8, 2018 12:50 PM To: Jones, Bruce E; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Requesting WF +1 in stx-config A couple more related to DevStack… Review https://review.openstack.org/#/c/614804/ in stx-integ needs one more +2 and a WF+1. Can this be reviewed and merged please too? Review https://review.openstack.org/#/c/614244/ in stx-update needs one more +2 and a WF +1 too. brucej From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, November 8, 2018 9:45 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Requesting WF +1 in stx-config Review https://review.openstack.org/#/c/595865/ is waiting for WF+1. It has +2’s from Bart Wensley and John Kung. Can this be merged please? brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Thu Nov 8 18:21:59 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 8 Nov 2018 18:21:59 +0000 Subject: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 In-Reply-To: References: <2F61A2101B4FD447A683EF7E362CF9421C63E2181F@RSI-NOD-EXMDB6.india.rsystems.com> <3a8a02b2-624d-6f91-5dbd-b20d3fab0e16@windriver.com> <9700A18779F35F49AF027300A49E7C765FE3B2B9@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765FE3B6AF@SHSMSX101.ccr.corp.intel.com> <1513234c-d202-7d62-d291-c3f2ebf37441@linux.intel.com> <9700A18779F35F49AF027300A49E7C765FE3B753@SHSMSX101.ccr.corp.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA3E4D87@ALA-MBD.corp.ad.wrs.com> Set the workflow of A to -1, set B to depend on A. Once B is fully approved and W+1, then A can be W+1, and (hopefully) they get merged in the same window. -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Thursday, November 08, 2018 12:15 PM To: Dean Troyer; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 Hi StarlingX, One possible workaround particular for the case of modifying the lst files are to use 3 commits: A - Adds the new source rpm to the .lst file in stx-tools B - Changes the code in [your git] to use the new source RPM C - Removes the old source rpm from the .lst file in stx-tools C Depends-On B B Depends-On A The only downside is that for some window, you might have two versions of the source rpm in your workspace, eating an extra few MB of disk space. -Jason > -----Original Message----- > From: Dean Troyer > Sent: November 8, 2018 10:56 AM > To: Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Build failure on lastest build Sterling > 31/10/2018 > > On Wed, Nov 7, 2018 at 11:12 PM Lin, Shuicheng > wrote: > > The two patches need be merged together, so it is like A and B depends on > each other. > > But currently in gerrit/zuul, we cannot make patch depends on each other. > It is a limitation I think. > > So I just set A depends on B. > > In this situation the best approach is to get A approved first. It will go > through the gate pipeline but will not merge until B is approved. When B > gets through the gate pipeline they will both merge close together. It is still > not at exactly the same time but is gets close. > > You do not have to wait until A is done before approving B, you just want it to > get started enough earlier so B does not finish ahead of it. This minimizes the > gap between the merges. > > dt > > -- > > Dean Troyer > dtroyer at gmail.com > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cboylan at sapwetik.org Thu Nov 8 19:42:19 2018 From: cboylan at sapwetik.org (Clark Boylan) Date: Thu, 08 Nov 2018 11:42:19 -0800 Subject: [Starlingx-discuss] OpenDev, the future of OpenStack Infra Message-ID: <1541706139.393458.1570439656.675141A3@webmail.messagingengine.com> Hello everyone, Sorry for another cross post so soon. In the land before time we had Stackforge. Stackforge gave non-OpenStack projects a place to live with their own clearly defined "not OpenStack" namespacing. As the wheel of time spun we realized that many Stackforge projects were becoming OpenStack projects and we would have to migrate them. This involved Gerrit downtimes to rename things safely. To ease the pain of this, the TC decided that all projects developed in the OpenStack Infrastructure could live under the OpenStack git namespace to simplify migrations. Unfortunately this had the effect of creating confusion over which projects were officially a part of OpenStack, and whether or not projects that were not OpenStack could use our project hosting. Stackforge lived on under a different name, "unofficial project hosting", but many potential infrastructure users either didn't understand this or didn't want that strong association to OpenStack for their project hosting [0]. Turns out that we want to be able to host OpenStack and non-OpenStack projects together without confusion in a way that makes all of the projects involved happy. In an effort to make this a reality the OpenStack Infra team has been working through a process to rename itself to make it clear that our awesome project infrastructure and open collaboration tooling is community run, not just for OpenStack, but for others that want to be involved. To this end we've acquired the opendev.org domain which will allow us to host services under a neutral name as the OpenDev Infrastructure team. The OpenStack community will continue to be the largest and a primary user for the OpenDev Infrastructure team, but our hope in making our infrastructure services more inclusive is that we'll also attract new contributors, which will ultimately benefit OpenStack and other open infrastructure projects. Our goals for OpenDev are to: * Encourage additional active infrastructure contributors to help us scale. Make it clear that this is community-run tooling & infrastructure and everyone can get involved. * Make open source collaboration tools and project infrastructure more accessible to those that want it. * Have exposure to and dogfooding of OpenStack clouds as viable open source cloud providers. * Enable more projects to take advantage of the OpenStack-pioneered model of development and collaboration, including recommended practices like code review and gating. * Help build relationships with new and adjacent open source projects and create an inclusive space for collaboration and open source development. Much of this is still in the early planning stages. This is the infrastructure team's current thinking on the subject, but understand we have an existing community from which we'd like to see buy-in and involvement. To that end we have tried to compile a list of expected FAQ/Q&A information below, but feel free to followup either on this thread or with myself for anything we haven't considered already. Any transition will be slow and considered so don't expect everything to change overnight. But don't be surprised if you run into some new HTTP redirects as we reorganize the names under which services run. We'll also be sure to keep you informed on any major (and probably minor) transition steps so that they won't surprise you. Thank you, Clark [0] It should be noted that some projects did not mind this and hosted with OpenStack Infra anyway. ARA is an excellent example of this. FAQ * What is OpenDev? OpenDev is community-run tools and infrastructure services for collaboratively developing open source software. The OpenDev infrastruture team is the community of people who operate the infrastructure under the umbrella of the OpenStack Foundation. * What services are you offering? What is the expected timeline? In the near-term we expect to transition simple services like etherpad hosting to the OpenDev domain. It wil take us months and potentially up to a year to transition key infrastructure pieces like Git and Gerrit. Example services managed by the team today include etherpad, wiki, the zuul and nodepool CI system, git and gerrit, and other minor systems like pbx conferencing and survey tools. * Where will these services live? We've acquired opendev.org and are planning to set up DNS hosting very soon. We will post a simple information page and FAQ on the website and build it out as necessary over time. * Why are you changing from the OpenStack infrastructure team to the OpenDev infrastructure team? In the same way we want to signal that our services are not strictly for OpenStack projects, and that not every project using our services is an official part of OpenStack, we want to make it clear that our team also serves this larger community. * Who should use OpenDev services? Does it have to be projects related to OpenStack, or any open source projects? In short, open source contributors who share our community values, especially those who might want to help contribute to improving and maintaining OpenDev infrastructure over time. Projects using OpenDev hosted git and gerrit services should have an OSI-approved license. * Will the OpenStack projects live at git.opendev.org? All projects hosted with OpenDev will live at git.opendev.org. For backwards compatibility reasons, at the very least git.openstack.org will be an alias for git.opendev.org for the forseeable future. The same is true of the other existing whitelabel git domains such as git.starlingx.io and git.zuul-ci.org. Whether or not other 'whitelabel' domains are created is an open question. Given a neutral domain name, the desire for such sites may not seem as necessary. * Does this mean the infrastruture team will be spending less time on OpenStack? OpenStack will continue to be the largest and a primary user for the OpenDev Infrastructure team, and we expect that our work will benefit all users. There will be additional effort required as we transition to the new namespace and reorganize, but over the long term we hope this inclusive approach will help us attract new contributors and ultimately benefit OpenStack. * Are OpenStack cloud test resources the only resources that will be used? At the present time all of the donated resources come to us from a combination of OpenStack Public and Private clouds. Nobody from any of the proprietary clouds has asked to donate resources to us. It is conceivable that the shift to OpenDev could open the door to those cloud providers wanting to donate some cloud resources. Assuming nodepool supports talking to those clouds, it is certainly a possibility, but at the moment it's all speculation. * Is this name associated with the OpenDev Conferences (opendevconf.com) that OpenStack Foundation has previously organized? Yes! They are related, albeit indirectly. To quote from the conference's promotional site, "the focus is on bringing together composable open infrastructure technologies across communities and industries." The possibility of cross-promotional tie-ins could prove synergistic, since the conference and the collaboratory we're building share a lot of similar values and goals, and are ultimately supported by the same donors, community and foundation. * How will OpenDev be governed? Will the OpenStack TC retain oversight over it? The OpenDev governance discussion is just getting started, but like all OSF-supported initiatives, OpenDev follows the Four Opens, so it will ultimately be directly governed by OpenDev contributors. While it won't be under the sole oversight of the OpenStack Technical Committee anymore, OpenDev users (in particular OpenStack) should be represented in the governance model so that they can feed back their requirements to the OpenDev team. From bruce.e.jones at intel.com Thu Nov 8 21:46:56 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 8 Nov 2018 21:46:56 +0000 Subject: [Starlingx-discuss] Requesting WF +1 in stx-config In-Reply-To: <24B4BD7A-007D-4FF3-8C68-A7BB9E7B9A1B@windriver.com> References: <24B4BD7A-007D-4FF3-8C68-A7BB9E7B9A1B@windriver.com> Message-ID: <9A85D2917C58154C960D95352B22818BB1EA26F6@fmsmsx117.amr.corp.intel.com> Thank you! brucej From: Church, Robert [mailto:Robert.Church at windriver.com] Sent: Thursday, November 8, 2018 10:11 AM To: Wensley, Barton ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Requesting WF +1 in stx-config >> You will need a core from stx-integ to approve 614804 Done.. Bob. From: "Wensley, Barton" > Date: Thursday, November 8, 2018 at 11:56 AM To: "Jones, Bruce E" >, "starlingx-discuss at lists.starlingx.io" > Subject: Re: [Starlingx-discuss] Requesting WF +1 in stx-config I have approved 614244 and 595865. You will need a core from stx-integ to approve 614804. Bart From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: November 8, 2018 12:50 PM To: Jones, Bruce E; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Requesting WF +1 in stx-config A couple more related to DevStack… Review https://review.openstack.org/#/c/614804/ in stx-integ needs one more +2 and a WF+1. Can this be reviewed and merged please too? Review https://review.openstack.org/#/c/614244/ in stx-update needs one more +2 and a WF +1 too. brucej From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, November 8, 2018 9:45 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Requesting WF +1 in stx-config Review https://review.openstack.org/#/c/595865/ is waiting for WF+1. It has +2’s from Bart Wensley and John Kung. Can this be merged please? brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From cesar.lara at intel.com Thu Nov 8 21:41:34 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Thu, 8 Nov 2018 21:41:34 +0000 Subject: [Starlingx-discuss] [build][meetings] Build team meeting minutes 11/08/2018 Message-ID: <0B566C62EC792145B40E29EFEBF1AB471055D411@fmsmsx104.amr.corp.intel.com> Build team meeting minutes Agenda 11/08/2018 - Cengn mirror follow up - Build system proposal and tools - TL and repos owned by Build team - Planning for next release Attendees Saul, Jason, Scott, Ken, Memo, Erich, Mario, Victor, Cesar Cengn Mirror - Rpms are completed and available in the Cengn mirror posted as yum repository, we now have a way to create them and update them to make those available to the community. We are now focusing on next steps for our hosting infrastructure, builds generated at Cengn and ISO files posted as well as a mechanism to archive older versions, once we are over with that, we might want to start looking into optimizations for the current tools used for managing these processes. Things to be considered for the next phase of the builds: Separation of the OS layer versus the flock services and the containerization of these services, hardening of the current implementation to make it more robust, reliable and secure. Hosting details for the Cengn mirror: we have a bare metal server with enough space for the mirror RPMs and possibly hosting of ISO files, we need to decide the cadence for those. The evolution of this service is coming to us and we are going to be hosted on a K8 cluster with a Ceph storage backend so we don't have a hard dependency on direct attached storage. While we decide the cadence and the how's of the CI/CD system for StarlingX builds, we will generate an ISO file manually based on the 2018.10 release branch so we can make it available to the community for the OpenStack summit. We will sync up with the CI/CD spec already being created by WindRiver and will share a high level architecture and tools that Intel is using for our CI/CD so we can compare notes and come up with a solid plan for implementation on our Cengn server deployment. For the generation of the 2018.10 ISO we will conduct an audit to make sure to include only the packages that were part of the release branch. - Build system proposals and tools - see attached presentation, we had a great discussions on the details of this proposal, and had a level set of what we have today and some of the requirements and the how engineers are using the different pieces inside WindRiver so we can that those to account when building the proposed tools. We will be discussing details on the mailing list. - TL and repos owned by Build team, Erich and Yong will be added to the repositories owned by build team stx-root, stx-manifests, stx-integ. - Opens: we need a "best known method" for handling conflicts with dependent PRs and their packages so we avoid broken builds, Jason to post some options to mailing list. Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: build system proposal.pdf Type: application/pdf Size: 331193 bytes Desc: build system proposal.pdf URL: From cindy.xie at intel.com Thu Nov 8 23:16:21 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Thu, 8 Nov 2018 23:16:21 +0000 Subject: [Starlingx-discuss] Second controller on degraded for long time - Duplex Virtual In-Reply-To: References: <0A5D9A624DF90343892F8F3FE7DE525A2A8FC437@fmsmsx101.amr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35DBEAD3@SHSMSX104.ccr.corp.intel.com> Jose, Can you check if you reported issue is similar as the existing one reported here: https://bugs.launchpad.net/starlingx/+bug/1798836 thx. - cindy -----Original Message----- From: Dinescu, Stefan [mailto:Stefan.Dinescu at windriver.com] Sent: Thursday, November 8, 2018 11:01 PM To: Perez Carranza, Jose ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] Second controller on degraded for long time - Duplex Virtual Hello, Depending on the size of your cinder partition and network speed between the two controller nodes, cinder make take some time to sync as it is usually the biggest partition. you can use "drbd-overview" to see the progress of the sync. Thanks, Stefan ________________________________________ From: Perez Carranza, Jose [jose.perez.carranza at intel.com] Sent: Thursday, November 08, 2018 4:56 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] Second controller on degraded for long time - Duplex Virtual Hi I setup a Duplex virtual environment and I noticed that after installation and provisioning of second controller (controller-1) this one stays in Degraded for long time (~ 1 hour), and alarm 400.001 is being displayed [1], Is this normal behavior? Is here a way to take out the controller-1 from 'degraded' to 'available' faster? 1- http://paste.openstack.org/show/734425/ Regards, José _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Matt.Peters at windriver.com Fri Nov 9 02:16:47 2018 From: Matt.Peters at windriver.com (Peters, Matt) Date: Fri, 9 Nov 2018 02:16:47 +0000 Subject: [Starlingx-discuss] openstack-neutron-openvswitch In-Reply-To: <9700A18779F35F49AF027300A49E7C765FE3BA92@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C765FE3B7F2@SHSMSX101.ccr.corp.intel.com> <6DBDF5DC-EC5A-4CF0-BBE3-76CD3AEF6680@windriver.com> <9700A18779F35F49AF027300A49E7C765FE3BA92@SHSMSX101.ccr.corp.intel.com> Message-ID: <1E55C7AC-FD9E-4AAF-8B96-C1604F6A69E2@windriver.com> Hello Shuicheng, I think it should be fine to remove it from the controller host, but it should be verified in all system configurations. Regards, Matt From: "Lin, Shuicheng" Date: Thursday, November 8, 2018 at 7:18 PM To: "Peters, Matt" Subject: RE: openstack-neutron-openvswitch Hi Matt, Yes, I am referring to the filter file in stx-metal. I am doing code refactor now for openvswitch package. Here is the story: https://storyboard.openstack.org/#!/story/2003768 I prefer to remove openstack-neutron-openvswitch from controller node. Is it ok? Thanks. Best Regards Shuicheng From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Thursday, November 8, 2018 9:27 PM To: Lin, Shuicheng Subject: Re: openstack-neutron-openvswitch Hello Shuicheng, I’m assuming you are referring to the filter_out_xxx files in stx-metal. Packages listed in these files are *excluded* from the installation for that personality. Therefore this package will not be included on the storage hosts, but will be included on all other hosts (controller, compute, etc). Regards, Matt From: "Lin, Shuicheng" > Date: Thursday, November 8, 2018 at 3:16 AM To: "Peters, Matt" > Subject: openstack-neutron-openvswitch Hi Matt, I find package openstack-neutron-openvswitch is filtered for storage node only. Does controller node need it? I ask this question, because I thought openvswitch is installed in compute node only. But due to openstack-neutron-openvswitch requires openvswitch, so openvswitch is installed in controller node currently. Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From vm.rod25 at gmail.com Fri Nov 9 12:55:30 2018 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Fri, 9 Nov 2018 06:55:30 -0600 Subject: [Starlingx-discuss] [build] Project atomic In-Reply-To: References: Message-ID: On Thu, Nov 8, 2018 at 10:39 AM Cordoba Malibran, Erich wrote: > > Hi all, > > I was just in research mode for building options and I found the Project Atomic[0] > It seems interesting the way they build that project and the focus on containerization. > > There are different flavors of Atomic, CentOS Atomic, Fedora Silverblue[1] (Fedora CoreOS in the near future). > > I hope you can find it interesting. > I did find interesting Actually is pretty interesting how they are part of Fedora as a package : https://src.fedoraproject.org/rpms/atomic/blob/master/f/atomic.spec And also supported and build using Fedora infrastructure: https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2018-October/msg00006.html Is also interesting how they create a module that defines the package set required for running a fully featured, module-based Atomic Host https://src.fedoraproject.org/modules/atomic/tree/master So they are actaully a sub porject a of Fedora : https://getfedora.org/en/atomic/ NICE !! ( internally they will use all the existing infrastructure (koji and distributed git repository ) and tools to build the base of Fedora Atomic ) Same for CentOS : https://blog.centos.org/2018/03/centos-atomic-host-7-1802-available-for-download/ Thanks for sharing Erich > -Erich > > [0] https://www.projectatomic.io > [1] https://silverblue.fedoraproject.org > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Volker.Hoesslin at swsn.de Fri Nov 9 15:00:11 2018 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Fri, 9 Nov 2018 15:00:11 +0000 Subject: [Starlingx-discuss] Compute boot-loop In-Reply-To: <3a32af01c5lgg80i@shdsegapp1> References: <1e1ebab5-998b-3c27-fc68-4360e148315f@windriver.com> <8557B550001AFB46A43A0CCC314BF85153C592E1@FMSMSX108.amr.corp.intel.com> <7e411c5d-ae49-c4f8-35b8-4dd59ef91f34@windriver.com> <3a32af01c5lgg80i@shdsegapp1> Message-ID: ...make long story short: - activate IOMMU for an already installed compute-node will end in some other crashes - try to reinstall a compute-node ends in a realy desaster -> server briks completely -> have to flash BIOS - now my 9341-4i MegaRaid controller is not regonized by anyway :( nevermind, for testing just use the on-board sata controller - install compute-node run like a charm - unlock the compute-node -> auto-restart -> testing -> CRASH! Now I got this nova error log: https://pastebin.com/fvA7yKmT (loops for some times -> reboot with auto-revover try ...) So I'm so short befor getting a running starlingX cluster, but someone/something don’t want this :( PLZ HELP :) greez, volker... -----Ursprüngliche Nachricht----- Von: von Hoesslin, Volker [mailto:Volker.Hoesslin at swsn.de] Gesendet: Montag, 5. November 2018 17:06 An: 'Michel Thebeau'; Hu, Yong; Alonso, Juan Carlos; 'starlingx-discuss at lists.starlingx.io' Betreff: Re: [Starlingx-discuss] Compute boot-loop Ok, shame on me! I have to read all the hints from you and realy check all the details... I have an AMD EPYC 7601 (32 cores), and I didn’t realized that the point "IOMMU" in my BIOS the generic term for VT-d is, so it is all the time leave disabled -.- After enabled this option, my VM seems to run, currently booted but still in "In-Test" mode... we will see... Thx for help! Volker... -----Ursprüngliche Nachricht----- Von: Michel Thebeau [mailto:michel.thebeau at windriver.com] Gesendet: Montag, 5. November 2018 16:34 An: Hu, Yong; Alonso, Juan Carlos; von Hoesslin, Volker; 'starlingx-discuss at lists.starlingx.io' Betreff: Re: [Starlingx-discuss] Compute boot-loop Ack Yong. I received this initial internal response:  "The usual cause of this error is when they don't enable VT-d (Intel Virtualization Technology for Directed I/O) in the BIOS for the compute hosts." Volker, please let us know when you've confirmed that. M On 2018-11-01 9:19 p.m., Hu, Yong wrote: > Another head-up is that we need to assure VT is turned on in BIOS for the compute node. > > > On 02/11/2018, 6:39 AM, "Alonso, Juan Carlos" wrote: > > Hi, > > I think you set up a Duplex system (two controllers), right? > > I set up a Duplex system with two ISOs: stx-2018-10-30-171-master.iso and stx-2018-11-01-8-master.iso > I faced the same issue you mention with first ISO, but did not with today's ISO: stx-2018-11-01-8-master.iso. > > Please set up again a Duplex system with today's ISO to see if issue is still presented. > > Regards. > Juan Carlos Alonso > > -----Original Message----- > From: Michel Thebeau [mailto:michel.thebeau at windriver.com] > Sent: Thursday, November 1, 2018 10:29 AM > To: von Hoesslin, Volker ; 'starlingx-discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] Compute boot-loop > > Hi Volker, > > Could you describe the instructions you were using to setup startlingx (were you following a wiki online)? Did you recheck the instructions versus what is actually configured on the computes? > > How many cpus do your computes have? > > Which build are you using? Did you build your own? > > When reboot-loop happens on a node often the error will be presented on the console during boot or could be inferred from console, sometimes referring to puppet logs of the node /var/log/puppet/ > > M > > > On 2018-11-01 6:45 a.m., von Hoesslin, Volker wrote: > > Hello, there, > > i have now built a complete stack and believe i did everything right. after unlocking the compute nodes (two pieces), the nodes come into an endless boot loop. > > Error messages are not really noticeable, except: > > compute-X 'ceilometer-polling' process has failed. Auto recovery in progress > > > > any suggestions? Greez & thx, volker... > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Jason.McKenna at windriver.com Fri Nov 9 15:26:15 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Fri, 9 Nov 2018 15:26:15 +0000 Subject: [Starlingx-discuss] Build broken - utils-linux package fails to build with commit Message-ID: Hi StarlingX, Build is currently broken due in the utils-linux package. The following commit removes the shadow-utils build, and refactors it as a config-only package (which is a desirable thing) https://review.openstack.org/#/c/612897/ The issue is that another package, utils-linux, relies on a file (pam.d/su) which was living in the shadow-utils source directory. Removing the shadow-utils directory therefore breaks the build of utils-linux package. As a side note, I agree that the utils-linux package should not be relying on stuff in other packages, but that's another topic... My bigger question is in regards to testing the commit. I would expect the build tools to detect the change in the inputs to utils-linux and attempt to recompile the source rpm (which would fail). Is it possible that the addition and build of the new shadow-utils-config package was tested in an environment which did not incorporate the removal of shadow-utils? -Jason -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jason.McKenna at windriver.com Fri Nov 9 15:46:37 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Fri, 9 Nov 2018 15:46:37 +0000 Subject: [Starlingx-discuss] Build broken - utils-linux package fails to build with commit In-Reply-To: References: Message-ID: Sorry for the noise, I now see that a Launchpad has already been created, and a fix proposed. https://bugs.launchpad.net/starlingx/+bug/1802434 From: McKenna, Jason Sent: November 9, 2018 10:26 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Build broken - utils-linux package fails to build with commit Hi StarlingX, Build is currently broken due in the utils-linux package. The following commit removes the shadow-utils build, and refactors it as a config-only package (which is a desirable thing) https://review.openstack.org/#/c/612897/ The issue is that another package, utils-linux, relies on a file (pam.d/su) which was living in the shadow-utils source directory. Removing the shadow-utils directory therefore breaks the build of utils-linux package. As a side note, I agree that the utils-linux package should not be relying on stuff in other packages, but that's another topic... My bigger question is in regards to testing the commit. I would expect the build tools to detect the change in the inputs to utils-linux and attempt to recompile the source rpm (which would fail). Is it possible that the addition and build of the new shadow-utils-config package was tested in an environment which did not incorporate the removal of shadow-utils? -Jason -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Peters at windriver.com Fri Nov 9 13:21:30 2018 From: Matt.Peters at windriver.com (Peters, Matt) Date: Fri, 9 Nov 2018 13:21:30 +0000 Subject: [Starlingx-discuss] Analysis of patch 9f926a5 for StartlingX upstreaming In-Reply-To: References: Message-ID: <51F8F06E-D06E-4DDA-AABF-D69B622EFD56@windriver.com> Hi Chenjie, The RFE looks good. The use cases are clear and detailed. I only have a few minor review comments (see attached). Regards, Matt From: "Xu, Chenjie" Date: Thursday, November 1, 2018 at 4:28 AM To: "Peters, Matt" , Allain Legacy Cc: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Analysis of patch 9f926a5 for StartlingX upstreaming Hi Matt/Allain, We analyze the patch 9f926a5 related to l2pop. An RFE “Add l2pop support for floating ip resources” has been written and is attached. The test case is provided by Allain. Could you please help to review and comment? Thanks very much! Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: RFE_ADD_L2POP_SUPPORT_FOR_FLOATINGIP_RESOURCES-MPv1.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 98655 bytes Desc: RFE_ADD_L2POP_SUPPORT_FOR_FLOATINGIP_RESOURCES-MPv1.docx URL: From Michel.Thebeau at windriver.com Fri Nov 9 16:26:28 2018 From: Michel.Thebeau at windriver.com (Thebeau, Michel) Date: Fri, 9 Nov 2018 16:26:28 +0000 Subject: [Starlingx-discuss] Compute boot-loop In-Reply-To: References: <1e1ebab5-998b-3c27-fc68-4360e148315f@windriver.com> <8557B550001AFB46A43A0CCC314BF85153C592E1@FMSMSX108.amr.corp.intel.com> <7e411c5d-ae49-c4f8-35b8-4dd59ef91f34@windriver.com> <3a32af01c5lgg80i@shdsegapp1>, Message-ID: <36F925451B17AF4A99BEA78C7E086057F43B4388@ALA-MBD.corp.ad.wrs.com> That's a lot to take in Volker ;) *If* this if the first time you've worked with StarlingX I recommend trying it out under the virtualization usecase. That would be a good way to become familiar with the install process. The actual error listed in pastebin is interesting, referring to "vm_4K = vm_4K_nodes[cell.id]" in nova/virt/libvirt/host.py. I'll ask internally if that error looks familiar. M ________________________________________ From: von Hoesslin, Volker [Volker.Hoesslin at swsn.de] Sent: Friday, November 09, 2018 10:00 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] Compute boot-loop ...make long story short: - activate IOMMU for an already installed compute-node will end in some other crashes - try to reinstall a compute-node ends in a realy desaster -> server briks completely -> have to flash BIOS - now my 9341-4i MegaRaid controller is not regonized by anyway :( nevermind, for testing just use the on-board sata controller - install compute-node run like a charm - unlock the compute-node -> auto-restart -> testing -> CRASH! Now I got this nova error log: https://pastebin.com/fvA7yKmT (loops for some times -> reboot with auto-revover try ...) So I'm so short befor getting a running starlingX cluster, but someone/something don’t want this :( PLZ HELP :) greez, volker... -----Ursprüngliche Nachricht----- Von: von Hoesslin, Volker [mailto:Volker.Hoesslin at swsn.de] Gesendet: Montag, 5. November 2018 17:06 An: 'Michel Thebeau'; Hu, Yong; Alonso, Juan Carlos; 'starlingx-discuss at lists.starlingx.io' Betreff: Re: [Starlingx-discuss] Compute boot-loop Ok, shame on me! I have to read all the hints from you and realy check all the details... I have an AMD EPYC 7601 (32 cores), and I didn’t realized that the point "IOMMU" in my BIOS the generic term for VT-d is, so it is all the time leave disabled -.- After enabled this option, my VM seems to run, currently booted but still in "In-Test" mode... we will see... Thx for help! Volker... -----Ursprüngliche Nachricht----- Von: Michel Thebeau [mailto:michel.thebeau at windriver.com] Gesendet: Montag, 5. November 2018 16:34 An: Hu, Yong; Alonso, Juan Carlos; von Hoesslin, Volker; 'starlingx-discuss at lists.starlingx.io' Betreff: Re: [Starlingx-discuss] Compute boot-loop Ack Yong. I received this initial internal response: "The usual cause of this error is when they don't enable VT-d (Intel Virtualization Technology for Directed I/O) in the BIOS for the compute hosts." Volker, please let us know when you've confirmed that. M On 2018-11-01 9:19 p.m., Hu, Yong wrote: > Another head-up is that we need to assure VT is turned on in BIOS for the compute node. > > > On 02/11/2018, 6:39 AM, "Alonso, Juan Carlos" wrote: > > Hi, > > I think you set up a Duplex system (two controllers), right? > > I set up a Duplex system with two ISOs: stx-2018-10-30-171-master.iso and stx-2018-11-01-8-master.iso > I faced the same issue you mention with first ISO, but did not with today's ISO: stx-2018-11-01-8-master.iso. > > Please set up again a Duplex system with today's ISO to see if issue is still presented. > > Regards. > Juan Carlos Alonso > > -----Original Message----- > From: Michel Thebeau [mailto:michel.thebeau at windriver.com] > Sent: Thursday, November 1, 2018 10:29 AM > To: von Hoesslin, Volker ; 'starlingx-discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] Compute boot-loop > > Hi Volker, > > Could you describe the instructions you were using to setup startlingx (were you following a wiki online)? Did you recheck the instructions versus what is actually configured on the computes? > > How many cpus do your computes have? > > Which build are you using? Did you build your own? > > When reboot-loop happens on a node often the error will be presented on the console during boot or could be inferred from console, sometimes referring to puppet logs of the node /var/log/puppet/ > > M > > > On 2018-11-01 6:45 a.m., von Hoesslin, Volker wrote: > > Hello, there, > > i have now built a complete stack and believe i did everything right. after unlocking the compute nodes (two pieces), the nodes come into an endless boot loop. > > Error messages are not really noticeable, except: > > compute-X 'ceilometer-polling' process has failed. Auto recovery in progress > > > > any suggestions? Greez & thx, volker... > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From jose.perez.carranza at intel.com Fri Nov 9 17:36:36 2018 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Fri, 9 Nov 2018 17:36:36 +0000 Subject: [Starlingx-discuss] Second controller on degraded for long time - Duplex Virtual In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F35DBEAD3@SHSMSX104.ccr.corp.intel.com> References: <0A5D9A624DF90343892F8F3FE7DE525A2A8FC437@fmsmsx101.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35DBEAD3@SHSMSX104.ccr.corp.intel.com> Message-ID: <0A5D9A624DF90343892F8F3FE7DE525A2A8FC8D1@fmsmsx101.amr.corp.intel.com> Hi Cindy Actually I did not fill a Launchpad, I just sent the question to the mailing list, in my case controller-1 gets available after sync (~1 hour) but I did not noticed that after that a controller goes back to degraded mode again. Regards, José > -----Original Message----- > From: Xie, Cindy > Sent: Thursday, November 8, 2018 5:16 PM > To: Dinescu, Stefan ; Perez Carranza, Jose > ; 'starlingx-discuss at lists.starlingx.io' > > Subject: RE: [Starlingx-discuss] Second controller on degraded for long time - > Duplex Virtual > > Jose, > Can you check if you reported issue is similar as the existing one reported > here: > > https://bugs.launchpad.net/starlingx/+bug/1798836 > > thx. - cindy > > -----Original Message----- > From: Dinescu, Stefan [mailto:Stefan.Dinescu at windriver.com] > Sent: Thursday, November 8, 2018 11:01 PM > To: Perez Carranza, Jose ; 'starlingx- > discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] Second controller on degraded for long time - > Duplex Virtual > > Hello, > > Depending on the size of your cinder partition and network speed between > the two controller nodes, cinder make take some time to sync as it is usually > the biggest partition. > > you can use "drbd-overview" to see the progress of the sync. > > Thanks, > Stefan > ________________________________________ > From: Perez Carranza, Jose [jose.perez.carranza at intel.com] > Sent: Thursday, November 08, 2018 4:56 PM > To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] Second controller on degraded for long time - > Duplex Virtual > > Hi > > I setup a Duplex virtual environment and I noticed that after installation and > provisioning of second controller (controller-1) this one stays in Degraded for > long time (~ 1 hour), and alarm 400.001 is being displayed [1], Is this normal > behavior? Is here a way to take out the controller-1 from 'degraded' to > 'available' faster? > > 1- http://paste.openstack.org/show/734425/ > > > Regards, > José > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From James.Gauld at windriver.com Fri Nov 9 19:09:32 2018 From: James.Gauld at windriver.com (Gauld, James) Date: Fri, 9 Nov 2018 19:09:32 +0000 Subject: [Starlingx-discuss] Compute boot-loop In-Reply-To: <36F925451B17AF4A99BEA78C7E086057F43B4388@ALA-MBD.corp.ad.wrs.com> References: <1e1ebab5-998b-3c27-fc68-4360e148315f@windriver.com> <8557B550001AFB46A43A0CCC314BF85153C592E1@FMSMSX108.amr.corp.intel.com> <7e411c5d-ae49-c4f8-35b8-4dd59ef91f34@windriver.com> <3a32af01c5lgg80i@shdsegapp1>, <36F925451B17AF4A99BEA78C7E086057F43B4388@ALA-MBD.corp.ad.wrs.com> Message-ID: <8E5740EC88EF3E4BA3196F2545DC8625BA19FD5D@ALA-MBD.corp.ad.wrs.com> I took a brief look at the pastebin nova-compute.log and noticed you have 8 numa nodes and 2 sockets. See section : 2018-11-09 14:42:10.928 69097 INFO nova.virt.libvirt.host [-] Libvirt host capabilities i.e., see Libvirt host -- there are 8 NUMA Cells, but only 2 socket_ids. Our sysinv and platform code does not support numa nodes per socket, we require a 1-to-1 mapping of socket to NUMA node. The specific error in nova/virt/libvirt/host.py", line 743, in get_capabilities() occurs since platform did not provision all 8 numa nodes (Cells). i.e., caps = self._host.get_capabilities() 2018-11-09 14:42:10.936 69097 ERROR oslo_service.service vm_4K = vm_4K_nodes[cell.id] 2018-11-09 14:42:10.936 69097 ERROR oslo_service.service IndexError: list index out of range The underlying routine _get_configured_pages() replies on platform configuration knowledge of sockets/numa cells. The platform likely provided 2 sockets of configuration data, but this code required 8 numa Cell indices. We have seen cases like this where a BIOS for setting like 'enable Sub NUMA Cluster configuration' is enabled. If that is the case, disable that setting, then reinstall the compute. -jim -----Original Message----- From: Thebeau, Michel Sent: November-09-18 11:26 AM To: von Hoesslin, Volker; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] Compute boot-loop That's a lot to take in Volker ;) *If* this if the first time you've worked with StarlingX I recommend trying it out under the virtualization usecase. That would be a good way to become familiar with the install process. The actual error listed in pastebin is interesting, referring to "vm_4K = vm_4K_nodes[cell.id]" in nova/virt/libvirt/host.py. I'll ask internally if that error looks familiar. M ________________________________________ From: von Hoesslin, Volker [Volker.Hoesslin at swsn.de] Sent: Friday, November 09, 2018 10:00 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] Compute boot-loop ...make long story short: - activate IOMMU for an already installed compute-node will end in some other crashes - try to reinstall a compute-node ends in a realy desaster -> server briks completely -> have to flash BIOS - now my 9341-4i MegaRaid controller is not regonized by anyway :( nevermind, for testing just use the on-board sata controller - install compute-node run like a charm - unlock the compute-node -> auto-restart -> testing -> CRASH! Now I got this nova error log: https://pastebin.com/fvA7yKmT (loops for some times -> reboot with auto-revover try ...) So I'm so short befor getting a running starlingX cluster, but someone/something don’t want this :( PLZ HELP :) greez, volker... -----Ursprüngliche Nachricht----- Von: von Hoesslin, Volker [mailto:Volker.Hoesslin at swsn.de] Gesendet: Montag, 5. November 2018 17:06 An: 'Michel Thebeau'; Hu, Yong; Alonso, Juan Carlos; 'starlingx-discuss at lists.starlingx.io' Betreff: Re: [Starlingx-discuss] Compute boot-loop Ok, shame on me! I have to read all the hints from you and realy check all the details... I have an AMD EPYC 7601 (32 cores), and I didn’t realized that the point "IOMMU" in my BIOS the generic term for VT-d is, so it is all the time leave disabled -.- After enabled this option, my VM seems to run, currently booted but still in "In-Test" mode... we will see... Thx for help! Volker... -----Ursprüngliche Nachricht----- Von: Michel Thebeau [mailto:michel.thebeau at windriver.com] Gesendet: Montag, 5. November 2018 16:34 An: Hu, Yong; Alonso, Juan Carlos; von Hoesslin, Volker; 'starlingx-discuss at lists.starlingx.io' Betreff: Re: [Starlingx-discuss] Compute boot-loop Ack Yong. I received this initial internal response: "The usual cause of this error is when they don't enable VT-d (Intel Virtualization Technology for Directed I/O) in the BIOS for the compute hosts." Volker, please let us know when you've confirmed that. M On 2018-11-01 9:19 p.m., Hu, Yong wrote: > Another head-up is that we need to assure VT is turned on in BIOS for the compute node. > > > On 02/11/2018, 6:39 AM, "Alonso, Juan Carlos" wrote: > > Hi, > > I think you set up a Duplex system (two controllers), right? > > I set up a Duplex system with two ISOs: stx-2018-10-30-171-master.iso and stx-2018-11-01-8-master.iso > I faced the same issue you mention with first ISO, but did not with today's ISO: stx-2018-11-01-8-master.iso. > > Please set up again a Duplex system with today's ISO to see if issue is still presented. > > Regards. > Juan Carlos Alonso > > -----Original Message----- > From: Michel Thebeau [mailto:michel.thebeau at windriver.com] > Sent: Thursday, November 1, 2018 10:29 AM > To: von Hoesslin, Volker ; 'starlingx-discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] Compute boot-loop > > Hi Volker, > > Could you describe the instructions you were using to setup startlingx (were you following a wiki online)? Did you recheck the instructions versus what is actually configured on the computes? > > How many cpus do your computes have? > > Which build are you using? Did you build your own? > > When reboot-loop happens on a node often the error will be > presented on the console during boot or could be inferred from > console, sometimes referring to puppet logs of the node > /var/log/puppet/ > > M > > > On 2018-11-01 6:45 a.m., von Hoesslin, Volker wrote: > > Hello, there, > > i have now built a complete stack and believe i did everything right. after unlocking the compute nodes (two pieces), the nodes come into an endless boot loop. > > Error messages are not really noticeable, except: > > compute-X 'ceilometer-polling' process has failed. Auto recovery in progress > > > > any suggestions? Greez & thx, volker... > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cindy.xie at intel.com Sat Nov 10 00:12:10 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Sat, 10 Nov 2018 00:12:10 +0000 Subject: [Starlingx-discuss] Second controller on degraded for long time - Duplex Virtual In-Reply-To: <0A5D9A624DF90343892F8F3FE7DE525A2A8FC8D1@fmsmsx101.amr.corp.intel.com> References: <0A5D9A624DF90343892F8F3FE7DE525A2A8FC437@fmsmsx101.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35DBEAD3@SHSMSX104.ccr.corp.intel.com> <0A5D9A624DF90343892F8F3FE7DE525A2A8FC8D1@fmsmsx101.amr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35DBFFF8@SHSMSX104.ccr.corp.intel.com> So Jose, you think the issue you encountered is the same issue as bug#1798836, my understanding correct? @Austin who is working on this bug may contact you for more details including log files. Thx. - cindy -----Original Message----- From: Perez Carranza, Jose Sent: Saturday, November 10, 2018 1:37 AM To: Xie, Cindy ; Dinescu, Stefan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] Second controller on degraded for long time - Duplex Virtual Hi Cindy Actually I did not fill a Launchpad, I just sent the question to the mailing list, in my case controller-1 gets available after sync (~1 hour) but I did not noticed that after that a controller goes back to degraded mode again. Regards, José > -----Original Message----- > From: Xie, Cindy > Sent: Thursday, November 8, 2018 5:16 PM > To: Dinescu, Stefan ; Perez Carranza, > Jose ; 'starlingx-discuss at lists.starlingx.io' > > Subject: RE: [Starlingx-discuss] Second controller on degraded for > long time - Duplex Virtual > > Jose, > Can you check if you reported issue is similar as the existing one > reported > here: > > https://bugs.launchpad.net/starlingx/+bug/1798836 > > thx. - cindy > > -----Original Message----- > From: Dinescu, Stefan [mailto:Stefan.Dinescu at windriver.com] > Sent: Thursday, November 8, 2018 11:01 PM > To: Perez Carranza, Jose ; 'starlingx- > discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] Second controller on degraded for > long time - Duplex Virtual > > Hello, > > Depending on the size of your cinder partition and network speed > between the two controller nodes, cinder make take some time to sync > as it is usually the biggest partition. > > you can use "drbd-overview" to see the progress of the sync. > > Thanks, > Stefan > ________________________________________ > From: Perez Carranza, Jose [jose.perez.carranza at intel.com] > Sent: Thursday, November 08, 2018 4:56 PM > To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] Second controller on degraded for long > time - Duplex Virtual > > Hi > > I setup a Duplex virtual environment and I noticed that after > installation and provisioning of second controller (controller-1) this > one stays in Degraded for long time (~ 1 hour), and alarm 400.001 is > being displayed [1], Is this normal behavior? Is here a way to take > out the controller-1 from 'degraded' to 'available' faster? > > 1- http://paste.openstack.org/show/734425/ > > > Regards, > José > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From austin.sun at intel.com Sat Nov 10 01:10:10 2018 From: austin.sun at intel.com (Sun, Austin) Date: Sat, 10 Nov 2018 01:10:10 +0000 Subject: [Starlingx-discuss] Second controller on degraded for long time - Duplex Virtual In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F35DBFFF8@SHSMSX104.ccr.corp.intel.com> References: <0A5D9A624DF90343892F8F3FE7DE525A2A8FC437@fmsmsx101.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35DBEAD3@SHSMSX104.ccr.corp.intel.com> <0A5D9A624DF90343892F8F3FE7DE525A2A8FC8D1@fmsmsx101.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35DBFFF8@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi Cindy: Mhg raised bug#1798836 and I worked with him. I cannot reproduce this issue. bug#1798836 is using static IPv4 , not dynamic . Mhg's setup has been changed to do other test. @Jose: could you raise bug and attach logs ( /var/log/*) in controller-0/controller-1 ? Thanks. BR Austin Sun. -----Original Message----- From: Xie, Cindy Sent: Saturday, November 10, 2018 8:12 AM To: Perez Carranza, Jose ; Sun, Austin ; Dinescu, Stefan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] Second controller on degraded for long time - Duplex Virtual So Jose, you think the issue you encountered is the same issue as bug#1798836, my understanding correct? @Austin who is working on this bug may contact you for more details including log files. Thx. - cindy -----Original Message----- From: Perez Carranza, Jose Sent: Saturday, November 10, 2018 1:37 AM To: Xie, Cindy ; Dinescu, Stefan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] Second controller on degraded for long time - Duplex Virtual Hi Cindy Actually I did not fill a Launchpad, I just sent the question to the mailing list, in my case controller-1 gets available after sync (~1 hour) but I did not noticed that after that a controller goes back to degraded mode again. Regards, José > -----Original Message----- > From: Xie, Cindy > Sent: Thursday, November 8, 2018 5:16 PM > To: Dinescu, Stefan ; Perez Carranza, > Jose ; 'starlingx-discuss at lists.starlingx.io' > > Subject: RE: [Starlingx-discuss] Second controller on degraded for > long time - Duplex Virtual > > Jose, > Can you check if you reported issue is similar as the existing one > reported > here: > > https://bugs.launchpad.net/starlingx/+bug/1798836 > > thx. - cindy > > -----Original Message----- > From: Dinescu, Stefan [mailto:Stefan.Dinescu at windriver.com] > Sent: Thursday, November 8, 2018 11:01 PM > To: Perez Carranza, Jose ; 'starlingx- > discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] Second controller on degraded for > long time - Duplex Virtual > > Hello, > > Depending on the size of your cinder partition and network speed > between the two controller nodes, cinder make take some time to sync > as it is usually the biggest partition. > > you can use "drbd-overview" to see the progress of the sync. > > Thanks, > Stefan > ________________________________________ > From: Perez Carranza, Jose [jose.perez.carranza at intel.com] > Sent: Thursday, November 08, 2018 4:56 PM > To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] Second controller on degraded for long > time - Duplex Virtual > > Hi > > I setup a Duplex virtual environment and I noticed that after > installation and provisioning of second controller (controller-1) this > one stays in Degraded for long time (~ 1 hour), and alarm 400.001 is > being displayed [1], Is this normal behavior? Is here a way to take > out the controller-1 from 'degraded' to 'available' faster? > > 1- http://paste.openstack.org/show/734425/ > > > Regards, > José > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From liang.a.fang at intel.com Sat Nov 10 09:23:54 2018 From: liang.a.fang at intel.com (Fang, Liang A) Date: Sat, 10 Nov 2018 09:23:54 +0000 Subject: [Starlingx-discuss] [glance] Analysis of patch c73ab48 (Enhanced-error-messages) for StartlingX upstreaming Message-ID: Hi Daniel and Stefan Please refer to https://review.openstack.org/#/c/616880/ This patch is to provide detailed exception info when no space in rbd. But in my environment, if rbd has no space, the function call to rbd will not return, there's no exception raised. Details: In /usr/local/lib/python2.7/dist-packages/glance_store/_drivers/rbd.py - Function call will hang at line 484 (_create_image) if no space to create image at the beginning [cid:image001.png at 01D47916.203BFA30] - Function call will hang at line 506 (image.resize) if no space at the middle of uploading. [cid:image002.png at 01D47917.1BBFA460] Could you please give some clue to reproduce this patch (raise rbd.NoSpace)? Couple of other thought: 1. This patch is to catch exception at v1 api, but v1 is about to be removed by community. 2. rbd is just one type of the multiple types of backend, so I think catch specific backend's exception at a common code is not so good. glance_store/rbd.py may be the better place to catch this exception. In fact rbd.py already did similar thing, see: [cid:image003.png at 01D47919.B20AE9F0] Thanks Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 2947 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 1524 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8559 bytes Desc: image003.png URL: From chenjie.xu at intel.com Mon Nov 12 06:22:56 2018 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Mon, 12 Nov 2018 06:22:56 +0000 Subject: [Starlingx-discuss] Analysis of patch 9f926a5 for StartlingX upstreaming In-Reply-To: <51F8F06E-D06E-4DDA-AABF-D69B622EFD56@windriver.com> References: <51F8F06E-D06E-4DDA-AABF-D69B622EFD56@windriver.com> Message-ID: Hi Matt, The RFE has been updated and is attached. Could you please help review and comment? Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Friday, November 9, 2018 9:22 PM To: Xu, Chenjie ; Legacy, Allain Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Analysis of patch 9f926a5 for StartlingX upstreaming Hi Chenjie, The RFE looks good. The use cases are clear and detailed. I only have a few minor review comments (see attached). Regards, Matt From: "Xu, Chenjie" > Date: Thursday, November 1, 2018 at 4:28 AM To: "Peters, Matt" >, Allain Legacy > Cc: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] Analysis of patch 9f926a5 for StartlingX upstreaming Hi Matt/Allain, We analyze the patch 9f926a5 related to l2pop. An RFE “Add l2pop support for floating ip resources” has been written and is attached. The test case is provided by Allain. Could you please help to review and comment? Thanks very much! Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: RFE_ADD_L2POP_SUPPORT_FOR_FLOATINGIP_RESOURCES.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 93953 bytes Desc: RFE_ADD_L2POP_SUPPORT_FOR_FLOATINGIP_RESOURCES.docx URL: From liang.a.fang at intel.com Mon Nov 12 08:02:27 2018 From: liang.a.fang at intel.com (Fang, Liang A) Date: Mon, 12 Nov 2018 08:02:27 +0000 Subject: [Starlingx-discuss] [glance] Analysis of patch daacf12 (Validate image properties) for StartlingX upstreaming Message-ID: Hi Kristine Please refer to https://review.openstack.org/#/c/616873/ This patch is to add checks for extra_properties when creating image. I want to abandon this patch, because: 1. The properties to be checked are Starlingx specific, so it's not suitable to hard code these check in common code. 2. Glance provided a mechanism (property_protections & policy) to check extra_properties, by adding rules in policy.json 3. If the check is too complex and policy.json cannot do this job, then it should be the property owner's responsibility to do the check before sending to glance. Glance is just like a DB to store these properties. The user is the owner (such as nova, cinder, etc). Do you have any comments? Please correct me if I have misunderstand something. Thanks. Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Mon Nov 12 09:19:08 2018 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 12 Nov 2018 01:19:08 -0800 Subject: [Starlingx-discuss] Using %{_bindir} for executables in specfiles Message-ID: <8634a411-bc25-4d45-c577-2c7ed51ae025@linux.intel.com> Folks, I noticed something today when I was reviewing one of the refactor patches and it got me thinking (which is never a good thing when jet-lagged). Why don't we use the RPM macro %{_bindir} which is /usr/bin by default? I did a quick grep in the spec files and patches for spec files and found that we current use systemctl, /bin/systemctl and /usr/bin/systemctl. Not all OSes have a /bin/systemctl, so this might fail later. I am going to recommend that we have a standard of using the RPM macros when calling executables inside of RPM Spec files so that we have some consistency. I am not saying we should to a mass find/replace right now, but as we touch/update move to a consistent format, this will help later with multi-os. If needed we can get a specification written around this concept. Thoughts, flames? Sau! From Volker.Hoesslin at swsn.de Mon Nov 12 10:55:40 2018 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Mon, 12 Nov 2018 10:55:40 +0000 Subject: [Starlingx-discuss] Compute boot-loop In-Reply-To: <8E5740EC88EF3E4BA3196F2545DC8625BA19FD5D@ALA-MBD.corp.ad.wrs.com> References: <1e1ebab5-998b-3c27-fc68-4360e148315f@windriver.com> <8557B550001AFB46A43A0CCC314BF85153C592E1@FMSMSX108.amr.corp.intel.com> <7e411c5d-ae49-c4f8-35b8-4dd59ef91f34@windriver.com> <3a32af01c5lgg80i@shdsegapp1>, <36F925451B17AF4A99BEA78C7E086057F43B4388@ALA-MBD.corp.ad.wrs.com> <8E5740EC88EF3E4BA3196F2545DC8625BA19FD5D@ALA-MBD.corp.ad.wrs.com> Message-ID: unbelievable! after I tortured the server with several restarts it seems to run: Used hardware: - Mainboard: H11DSi-NT - CPU: 2x AMD Epyc 7601 - RAM: 256GB (ECC 2666MHz) Important BIOS settings: - IOMMU: Enabeld // for Neutron - SR-IOV: Enabled - Memory interleaving: Die // This equals NUMA-Count and sockets (in my case to 2/2) Many thanks for the really good and very target-oriented support! I've spent a lot of time setting up an OpenStack, but this project trumps everything so far! Go on! I will certainly get back to you one or two times but so far it's a lot of fun! greetings, volker -----Ursprüngliche Nachricht----- Von: Gauld, James [mailto:James.Gauld at windriver.com] Gesendet: Freitag, 9. November 2018 20:10 An: Thebeau, Michel; von Hoesslin, Volker; 'starlingx-discuss at lists.starlingx.io' Betreff: RE: [Starlingx-discuss] Compute boot-loop I took a brief look at the pastebin nova-compute.log and noticed you have 8 numa nodes and 2 sockets. See section : 2018-11-09 14:42:10.928 69097 INFO nova.virt.libvirt.host [-] Libvirt host capabilities i.e., see Libvirt host -- there are 8 NUMA Cells, but only 2 socket_ids. Our sysinv and platform code does not support numa nodes per socket, we require a 1-to-1 mapping of socket to NUMA node. The specific error in nova/virt/libvirt/host.py", line 743, in get_capabilities() occurs since platform did not provision all 8 numa nodes (Cells). i.e., caps = self._host.get_capabilities() 2018-11-09 14:42:10.936 69097 ERROR oslo_service.service vm_4K = vm_4K_nodes[cell.id] 2018-11-09 14:42:10.936 69097 ERROR oslo_service.service IndexError: list index out of range The underlying routine _get_configured_pages() replies on platform configuration knowledge of sockets/numa cells. The platform likely provided 2 sockets of configuration data, but this code required 8 numa Cell indices. We have seen cases like this where a BIOS for setting like 'enable Sub NUMA Cluster configuration' is enabled. If that is the case, disable that setting, then reinstall the compute. -jim -----Original Message----- From: Thebeau, Michel Sent: November-09-18 11:26 AM To: von Hoesslin, Volker; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] Compute boot-loop That's a lot to take in Volker ;) *If* this if the first time you've worked with StarlingX I recommend trying it out under the virtualization usecase. That would be a good way to become familiar with the install process. The actual error listed in pastebin is interesting, referring to "vm_4K = vm_4K_nodes[cell.id]" in nova/virt/libvirt/host.py. I'll ask internally if that error looks familiar. M ________________________________________ From: von Hoesslin, Volker [Volker.Hoesslin at swsn.de] Sent: Friday, November 09, 2018 10:00 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] Compute boot-loop ...make long story short: - activate IOMMU for an already installed compute-node will end in some other crashes - try to reinstall a compute-node ends in a realy desaster -> server briks completely -> have to flash BIOS - now my 9341-4i MegaRaid controller is not regonized by anyway :( nevermind, for testing just use the on-board sata controller - install compute-node run like a charm - unlock the compute-node -> auto-restart -> testing -> CRASH! Now I got this nova error log: https://pastebin.com/fvA7yKmT (loops for some times -> reboot with auto-revover try ...) So I'm so short befor getting a running starlingX cluster, but someone/something don’t want this :( PLZ HELP :) greez, volker... -----Ursprüngliche Nachricht----- Von: von Hoesslin, Volker [mailto:Volker.Hoesslin at swsn.de] Gesendet: Montag, 5. November 2018 17:06 An: 'Michel Thebeau'; Hu, Yong; Alonso, Juan Carlos; 'starlingx-discuss at lists.starlingx.io' Betreff: Re: [Starlingx-discuss] Compute boot-loop Ok, shame on me! I have to read all the hints from you and realy check all the details... I have an AMD EPYC 7601 (32 cores), and I didn’t realized that the point "IOMMU" in my BIOS the generic term for VT-d is, so it is all the time leave disabled -.- After enabled this option, my VM seems to run, currently booted but still in "In-Test" mode... we will see... Thx for help! Volker... -----Ursprüngliche Nachricht----- Von: Michel Thebeau [mailto:michel.thebeau at windriver.com] Gesendet: Montag, 5. November 2018 16:34 An: Hu, Yong; Alonso, Juan Carlos; von Hoesslin, Volker; 'starlingx-discuss at lists.starlingx.io' Betreff: Re: [Starlingx-discuss] Compute boot-loop Ack Yong. I received this initial internal response: "The usual cause of this error is when they don't enable VT-d (Intel Virtualization Technology for Directed I/O) in the BIOS for the compute hosts." Volker, please let us know when you've confirmed that. M On 2018-11-01 9:19 p.m., Hu, Yong wrote: > Another head-up is that we need to assure VT is turned on in BIOS for the compute node. > > > On 02/11/2018, 6:39 AM, "Alonso, Juan Carlos" wrote: > > Hi, > > I think you set up a Duplex system (two controllers), right? > > I set up a Duplex system with two ISOs: stx-2018-10-30-171-master.iso and stx-2018-11-01-8-master.iso > I faced the same issue you mention with first ISO, but did not with today's ISO: stx-2018-11-01-8-master.iso. > > Please set up again a Duplex system with today's ISO to see if issue is still presented. > > Regards. > Juan Carlos Alonso > > -----Original Message----- > From: Michel Thebeau [mailto:michel.thebeau at windriver.com] > Sent: Thursday, November 1, 2018 10:29 AM > To: von Hoesslin, Volker ; 'starlingx-discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] Compute boot-loop > > Hi Volker, > > Could you describe the instructions you were using to setup startlingx (were you following a wiki online)? Did you recheck the instructions versus what is actually configured on the computes? > > How many cpus do your computes have? > > Which build are you using? Did you build your own? > > When reboot-loop happens on a node often the error will be > presented on the console during boot or could be inferred from > console, sometimes referring to puppet logs of the node > /var/log/puppet/ > > M > > > On 2018-11-01 6:45 a.m., von Hoesslin, Volker wrote: > > Hello, there, > > i have now built a complete stack and believe i did everything right. after unlocking the compute nodes (two pieces), the nodes come into an endless boot loop. > > Error messages are not really noticeable, except: > > compute-X 'ceilometer-polling' process has failed. Auto recovery in progress > > > > any suggestions? Greez & thx, volker... > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From jose.perez.carranza at intel.com Mon Nov 12 13:29:32 2018 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Mon, 12 Nov 2018 13:29:32 +0000 Subject: [Starlingx-discuss] Second controller on degraded for long time - Duplex Virtual In-Reply-To: References: <0A5D9A624DF90343892F8F3FE7DE525A2A8FC437@fmsmsx101.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35DBEAD3@SHSMSX104.ccr.corp.intel.com> <0A5D9A624DF90343892F8F3FE7DE525A2A8FC8D1@fmsmsx101.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35DBFFF8@SHSMSX104.ccr.corp.intel.com> Message-ID: <0A5D9A624DF90343892F8F3FE7DE525A2A8FDFB6@fmsmsx101.amr.corp.intel.com> Hi Cindy / Austin As I mentioned on my previous mail, I did not see the behavior mentioned on the bug, in my case the controller-1 becomes "Available" after the synchronization is finished and did not goes back again to "Degraded" mode. All my tests were done on an virtual environment. Regards, José > -----Original Message----- > From: Sun, Austin > Sent: Friday, November 9, 2018 7:10 PM > To: Xie, Cindy ; Perez Carranza, Jose > ; Dinescu, Stefan > ; 'starlingx-discuss at lists.starlingx.io' > > Subject: RE: [Starlingx-discuss] Second controller on degraded for long time - > Duplex Virtual > > Hi Cindy: > Mhg raised bug#1798836 and I worked with him. I cannot reproduce this > issue. bug#1798836 is using static IPv4 , not dynamic . > Mhg's setup has been changed to do other test. > @Jose: could you raise bug and attach logs ( /var/log/*) in controller- > 0/controller-1 ? > > Thanks. > BR > Austin Sun. > > > > -----Original Message----- > From: Xie, Cindy > Sent: Saturday, November 10, 2018 8:12 AM > To: Perez Carranza, Jose ; Sun, Austin > ; Dinescu, Stefan ; > 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] Second controller on degraded for long time - > Duplex Virtual > > So Jose, you think the issue you encountered is the same issue as > bug#1798836, my understanding correct? > > @Austin who is working on this bug may contact you for more details > including log files. > > Thx. - cindy > > -----Original Message----- > From: Perez Carranza, Jose > Sent: Saturday, November 10, 2018 1:37 AM > To: Xie, Cindy ; Dinescu, Stefan > ; 'starlingx-discuss at lists.starlingx.io' > > Subject: RE: [Starlingx-discuss] Second controller on degraded for long time - > Duplex Virtual > > Hi Cindy > > Actually I did not fill a Launchpad, I just sent the question to the mailing list, > in my case controller-1 gets available after sync (~1 hour) but I did not > noticed that after that a controller goes back to degraded mode again. > > Regards, > José > > > > -----Original Message----- > > From: Xie, Cindy > > Sent: Thursday, November 8, 2018 5:16 PM > > To: Dinescu, Stefan ; Perez Carranza, > > Jose ; 'starlingx-discuss at lists.starlingx.io' > > > > Subject: RE: [Starlingx-discuss] Second controller on degraded for > > long time - Duplex Virtual > > > > Jose, > > Can you check if you reported issue is similar as the existing one > > reported > > here: > > > > https://bugs.launchpad.net/starlingx/+bug/1798836 > > > > thx. - cindy > > > > -----Original Message----- > > From: Dinescu, Stefan [mailto:Stefan.Dinescu at windriver.com] > > Sent: Thursday, November 8, 2018 11:01 PM > > To: Perez Carranza, Jose ; 'starlingx- > > discuss at lists.starlingx.io' > > Subject: Re: [Starlingx-discuss] Second controller on degraded for > > long time - Duplex Virtual > > > > Hello, > > > > Depending on the size of your cinder partition and network speed > > between the two controller nodes, cinder make take some time to sync > > as it is usually the biggest partition. > > > > you can use "drbd-overview" to see the progress of the sync. > > > > Thanks, > > Stefan > > ________________________________________ > > From: Perez Carranza, Jose [jose.perez.carranza at intel.com] > > Sent: Thursday, November 08, 2018 4:56 PM > > To: 'starlingx-discuss at lists.starlingx.io' > > Subject: [Starlingx-discuss] Second controller on degraded for long > > time - Duplex Virtual > > > > Hi > > > > I setup a Duplex virtual environment and I noticed that after > > installation and provisioning of second controller (controller-1) this > > one stays in Degraded for long time (~ 1 hour), and alarm 400.001 is > > being displayed [1], Is this normal behavior? Is here a way to take > > out the controller-1 from 'degraded' to 'available' faster? > > > > 1- http://paste.openstack.org/show/734425/ > > > > > > Regards, > > José > > > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Stefan.Dinescu at windriver.com Mon Nov 12 14:12:36 2018 From: Stefan.Dinescu at windriver.com (Dinescu, Stefan) Date: Mon, 12 Nov 2018 14:12:36 +0000 Subject: [Starlingx-discuss] [glance] Analysis of patch c73ab48 (Enhanced-error-messages) for StartlingX upstreaming In-Reply-To: References: Message-ID: Hello, I havent' tested that part of the code in some time now, but from what I remember it was part of a larger set of changes to prevent ceph from hanging if not enough space was available. How it should work (but as I said, I haven't tested this in some time): - decrease the glance image pool quota (this is just so it's easier to test) - upload images to glance until space if almost full - the image that would have filled the pool should fail to upload entirely. It seems you are doing the correct procedure from what you described, so this probably requires a more in-depth investigation to see why it fails. ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Saturday, November 10, 2018 11:23 AM To: Badea, Daniel; Dinescu, Stefan Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [glance] Analysis of patch c73ab48 (Enhanced-error-messages) for StartlingX upstreaming Hi Daniel and Stefan Please refer to https://review.openstack.org/#/c/616880/ This patch is to provide detailed exception info when no space in rbd. But in my environment, if rbd has no space, the function call to rbd will not return, there’s no exception raised. Details: In /usr/local/lib/python2.7/dist-packages/glance_store/_drivers/rbd.py - Function call will hang at line 484 (_create_image) if no space to create image at the beginning [cid:image001.png at 01D47916.203BFA30] - Function call will hang at line 506 (image.resize) if no space at the middle of uploading. [cid:image002.png at 01D47917.1BBFA460] Could you please give some clue to reproduce this patch (raise rbd.NoSpace)? Couple of other thought: 1. This patch is to catch exception at v1 api, but v1 is about to be removed by community. 2. rbd is just one type of the multiple types of backend, so I think catch specific backend’s exception at a common code is not so good. glance_store/rbd.py may be the better place to catch this exception. In fact rbd.py already did similar thing, see: [cid:image003.png at 01D47919.B20AE9F0] Thanks Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 2947 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 1524 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8559 bytes Desc: image003.png URL: From Matt.Peters at windriver.com Mon Nov 12 15:19:17 2018 From: Matt.Peters at windriver.com (Peters, Matt) Date: Mon, 12 Nov 2018 15:19:17 +0000 Subject: [Starlingx-discuss] Analysis of patch 9f926a5 for StartlingX upstreaming In-Reply-To: References: <51F8F06E-D06E-4DDA-AABF-D69B622EFD56@windriver.com> Message-ID: <331FE402-1858-451D-8506-92E3E1033612@windriver.com> Hi Chenjie, The latest RFE looks good to me. Regards, Matt From: "Xu, Chenjie" Date: Monday, November 12, 2018 at 1:23 AM To: "Peters, Matt" Cc: "starlingx-discuss at lists.starlingx.io" , Allain Legacy Subject: RE: [Starlingx-discuss] Analysis of patch 9f926a5 for StartlingX upstreaming Hi Matt, The RFE has been updated and is attached. Could you please help review and comment? Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Friday, November 9, 2018 9:22 PM To: Xu, Chenjie ; Legacy, Allain Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Analysis of patch 9f926a5 for StartlingX upstreaming Hi Chenjie, The RFE looks good. The use cases are clear and detailed. I only have a few minor review comments (see attached). Regards, Matt From: "Xu, Chenjie" > Date: Thursday, November 1, 2018 at 4:28 AM To: "Peters, Matt" >, Allain Legacy > Cc: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] Analysis of patch 9f926a5 for StartlingX upstreaming Hi Matt/Allain, We analyze the patch 9f926a5 related to l2pop. An RFE “Add l2pop support for floating ip resources” has been written and is attached. The test case is provided by Allain. Could you please help to review and comment? Thanks very much! Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Mon Nov 12 16:56:14 2018 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Mon, 12 Nov 2018 16:56:14 +0000 Subject: [Starlingx-discuss] set([remote]) do not match local_image Message-ID: hmmmm, this doesn't stop :( now I can set up the complete stack in one go. but as soon as I try to set up a VM (cirrOS 0.4.0 as RAW or QCOW2) I get the following error: compute-0: (AggregateInstanceExtraSpecsFilter) extra_specs 'set([u'remote'])' do not match 'local_image', compute-1: (AggregateInstanceExtraSpecsFilter) extra_specs 'set([u'remote'])' do not match 'local_image'. as usual i followed the original instructions from the doku: https://docs.starlingx.io/installation_guide/dedicated_storage.html#dedicated-storage what am I doing wrong? Volker... -------------- next part -------------- An HTML attachment was scrubbed... URL: From Robert.Church at windriver.com Mon Nov 12 17:24:27 2018 From: Robert.Church at windriver.com (Church, Robert) Date: Mon, 12 Nov 2018 17:24:27 +0000 Subject: [Starlingx-discuss] set([remote]) do not match local_image Message-ID: <68B75BAC-B58F-4062-8D06-7CC668610B09@windriver.com> Hi Volker, Sounds like your flavor’s storage extra spec doesn’t match the storage configuration for the computes. ‘local_image’ is the default value for a flavor. You can specify the extra spec from the CLI by setting the following parameter for a flavor: aggregate_instance_extra_specs:storage=storage_type where storage_type is one of the following: * local_lvm - Specifies hosts with LVM-backed local storage for use by the VM. * local_image - Specifies hosts with image-backed local storage for use by the VM. * remote - Specifies hosts with Ceph-backed remote storage for use by the VM. For example: Looks like you need to set: nova flavor-key flavor_name set aggregate_instance_extra_specs:storage=remote Regards, Bob From: "von Hoesslin, Volker" Date: Monday, November 12, 2018 at 10:56 AM To: "'starlingx-discuss at lists.starlingx.io'" Subject: [Starlingx-discuss] set([remote]) do not match local_image hmmmm, this doesn't stop :( now I can set up the complete stack in one go. but as soon as I try to set up a VM (cirrOS 0.4.0 as RAW or QCOW2) I get the following error: compute-0: (AggregateInstanceExtraSpecsFilter) extra_specs 'set([u'remote'])' do not match 'local_image', compute-1: (AggregateInstanceExtraSpecsFilter) extra_specs 'set([u'remote'])' do not match 'local_image'. as usual i followed the original instructions from the doku: https://docs.starlingx.io/installation_guide/dedicated_storage.html#dedicated-storage what am I doing wrong? Volker… -------------- next part -------------- An HTML attachment was scrubbed... URL: From vm.rod25 at gmail.com Mon Nov 12 19:24:42 2018 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Mon, 12 Nov 2018 13:24:42 -0600 Subject: [Starlingx-discuss] Using %{_bindir} for executables in specfiles In-Reply-To: <8634a411-bc25-4d45-c577-2c7ed51ae025@linux.intel.com> References: <8634a411-bc25-4d45-c577-2c7ed51ae025@linux.intel.com> Message-ID: On Mon, Nov 12, 2018 at 3:19 AM Saul Wold wrote: > > > Folks, > > I noticed something today when I was reviewing one of the refactor > patches and it got me thinking (which is never a good thing when > jet-lagged). > > Why don't we use the RPM macro %{_bindir} which is /usr/bin by default? > I am not very fan of RPM macros , whoever for the multi OS target that we have it might work :) +1 from my side > I did a quick grep in the spec files and patches for spec files and > found that we current use systemctl, /bin/systemctl and > /usr/bin/systemctl. Not all OSes have a /bin/systemctl, so this might > fail later. > > I am going to recommend that we have a standard of using the RPM macros > when calling executables inside of RPM Spec files so that we have some > consistency. > > I am not saying we should to a mass find/replace right now, but as we > touch/update move to a consistent format, this will help later with > multi-os. > > If needed we can get a specification written around this concept. > > Thoughts, flames? > > Sau! > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cindy.xie at intel.com Tue Nov 13 01:06:54 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 13 Nov 2018 01:06:54 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack Distro meeting, 11/15 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35DC301A@SHSMSX104.ccr.corp.intel.com> Agenda for 11/15 meeting: 1. non-OpenStack patch refactoring status (Zhipeng/Shuicheng) 2. kernel driver upgrade testing update (Ada/Shuicheng) 3. Python2to3 non-openStack status brief (Austin) 4. Ceph upgrade status (Vivian/Dehao) 5. Opens (all) -----Original Appointment----- From: Xie, Cindy Sent: Monday, November 5, 2018 2:27 PM To: Xie, Cindy; Wold, Saul; 'Rowsell, Brent'; Jones, Bruce E; Troyer, Dean; 'Khalil, Ghada'; Waheed, Numan; Lin, Shuicheng; Zhu, Vivian; Shang, Dehao; Liu, ZhipengS; Hu, Yong; Sun, Austin; Somerville, Jim; starlingx-discuss at lists.starlingx.io Cc: Perez Carranza, Jose; 'Hellmann, Gil'; 'Waines, Greg'; 'Chen, Jacky'; Armstrong, Robert H; Perez Rodriguez, Humberto I; Martinez Landa, Hayde; Martinez Monroy, Elio; Hu, Wei W; Seiler, Glenn; Eslimi, Dariush; Gomez, Juan P; Lara, Cesar; Young, Ken Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, November 14, 2018 6:00 AM-7:00 AM (UTC-08:00) Pacific Time (US & Canada). Where: https://zoom.us/j/342730236 . Cadence and time slot: o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) . Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ . Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other From yong.hu at intel.com Tue Nov 13 04:55:05 2018 From: yong.hu at intel.com (Hu, Yong) Date: Tue, 13 Nov 2018 04:55:05 +0000 Subject: [Starlingx-discuss] Second controller on degraded for long time - Duplex Virtual In-Reply-To: <0A5D9A624DF90343892F8F3FE7DE525A2A8FDFB6@fmsmsx101.amr.corp.intel.com> References: <0A5D9A624DF90343892F8F3FE7DE525A2A8FC437@fmsmsx101.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35DBEAD3@SHSMSX104.ccr.corp.intel.com> <0A5D9A624DF90343892F8F3FE7DE525A2A8FC8D1@fmsmsx101.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35DBFFF8@SHSMSX104.ccr.corp.intel.com> <0A5D9A624DF90343892F8F3FE7DE525A2A8FDFB6@fmsmsx101.amr.corp.intel.com> Message-ID: Hi José, I ever saw this kind of issue when I added a very big disk partition (like 900 GB) on controller node by "host-lvg-modify". And you might see some info meaningful by "fm alarm-list". In my case the message was about inconsistent in drbd-cinder. Regards, Yong On 12/11/2018, 9:29 PM, "Perez Carranza, Jose" wrote: Hi Cindy / Austin As I mentioned on my previous mail, I did not see the behavior mentioned on the bug, in my case the controller-1 becomes "Available" after the synchronization is finished and did not goes back again to "Degraded" mode. All my tests were done on an virtual environment. Regards, José > -----Original Message----- > From: Sun, Austin > Sent: Friday, November 9, 2018 7:10 PM > To: Xie, Cindy ; Perez Carranza, Jose > ; Dinescu, Stefan > ; 'starlingx-discuss at lists.starlingx.io' > > Subject: RE: [Starlingx-discuss] Second controller on degraded for long time - > Duplex Virtual > > Hi Cindy: > Mhg raised bug#1798836 and I worked with him. I cannot reproduce this > issue. bug#1798836 is using static IPv4 , not dynamic . > Mhg's setup has been changed to do other test. > @Jose: could you raise bug and attach logs ( /var/log/*) in controller- > 0/controller-1 ? > > Thanks. > BR > Austin Sun. > > > > -----Original Message----- > From: Xie, Cindy > Sent: Saturday, November 10, 2018 8:12 AM > To: Perez Carranza, Jose ; Sun, Austin > ; Dinescu, Stefan ; > 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] Second controller on degraded for long time - > Duplex Virtual > > So Jose, you think the issue you encountered is the same issue as > bug#1798836, my understanding correct? > > @Austin who is working on this bug may contact you for more details > including log files. > > Thx. - cindy > > -----Original Message----- > From: Perez Carranza, Jose > Sent: Saturday, November 10, 2018 1:37 AM > To: Xie, Cindy ; Dinescu, Stefan > ; 'starlingx-discuss at lists.starlingx.io' > > Subject: RE: [Starlingx-discuss] Second controller on degraded for long time - > Duplex Virtual > > Hi Cindy > > Actually I did not fill a Launchpad, I just sent the question to the mailing list, > in my case controller-1 gets available after sync (~1 hour) but I did not > noticed that after that a controller goes back to degraded mode again. > > Regards, > José > > > > -----Original Message----- > > From: Xie, Cindy > > Sent: Thursday, November 8, 2018 5:16 PM > > To: Dinescu, Stefan ; Perez Carranza, > > Jose ; 'starlingx-discuss at lists.starlingx.io' > > > > Subject: RE: [Starlingx-discuss] Second controller on degraded for > > long time - Duplex Virtual > > > > Jose, > > Can you check if you reported issue is similar as the existing one > > reported > > here: > > > > https://bugs.launchpad.net/starlingx/+bug/1798836 > > > > thx. - cindy > > > > -----Original Message----- > > From: Dinescu, Stefan [mailto:Stefan.Dinescu at windriver.com] > > Sent: Thursday, November 8, 2018 11:01 PM > > To: Perez Carranza, Jose ; 'starlingx- > > discuss at lists.starlingx.io' > > Subject: Re: [Starlingx-discuss] Second controller on degraded for > > long time - Duplex Virtual > > > > Hello, > > > > Depending on the size of your cinder partition and network speed > > between the two controller nodes, cinder make take some time to sync > > as it is usually the biggest partition. > > > > you can use "drbd-overview" to see the progress of the sync. > > > > Thanks, > > Stefan > > ________________________________________ > > From: Perez Carranza, Jose [jose.perez.carranza at intel.com] > > Sent: Thursday, November 08, 2018 4:56 PM > > To: 'starlingx-discuss at lists.starlingx.io' > > Subject: [Starlingx-discuss] Second controller on degraded for long > > time - Duplex Virtual > > > > Hi > > > > I setup a Duplex virtual environment and I noticed that after > > installation and provisioning of second controller (controller-1) this > > one stays in Degraded for long time (~ 1 hour), and alarm 400.001 is > > being displayed [1], Is this normal behavior? Is here a way to take > > out the controller-1 from 'degraded' to 'available' faster? > > > > 1- http://paste.openstack.org/show/734425/ > > > > > > Regards, > > José > > > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From xiaoyan.li at intel.com Tue Nov 13 07:19:49 2018 From: xiaoyan.li at intel.com (Li, Xiaoyan) Date: Tue, 13 Nov 2018 07:19:49 +0000 Subject: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching In-Reply-To: References: <2588653EBDFFA34B982FAF00F1B4844EBB25D46B@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi, About the raw cache function in StarlingX Cinder and Glance, I would like to remove it as Cinder has similar function. Please see following detail. And if I would like to remove the function in StarlingX, there are two methods: 1. Submit a patch to revert the changes in Glance and Cinder. 2. Ignore these patches during upgrading StarlingX/Cinder to new Cinder release. Which way do we prefer to? Best wishes Lisa From: Li, Xiaoyan Sent: Thursday, September 20, 2018 10:17 AM To: Rowsell, Brent ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi, Brent The following are mechanism of Cinder volume cache. Creation of cached volume: It creates a cached volume in the backend storage when creating from an image. 1. Create_from_image: https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L890 2. Return image cache entry: If not existed, it creates a new entry. https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L746 3. Create a new image-volume and cache entry for it: https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L872 Use a cached volume when creating a volume: https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L723-L735 Delete the cache volume: When capacity and number of cache entries exceed specified limit, it deletes cache entries (cached volumes). https://github.com/openstack/cinder/blob/stable/pike/cinder/image/cache.py#L164 Best wishes Lisa From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Thursday, September 6, 2018 10:02 AM To: Li, Xiaoyan >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching We would need to review this feature to ensure it provides equivalent functionality first. If it does, great, we can look at reverting and enabling this cinder functionality. Brent From: Li, Xiaoyan [mailto:xiaoyan.li at intel.com] Sent: Wednesday, September 5, 2018 9:59 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi all, This email is about Raw caching function in StarlingX. This feature is to cache an image in backend storage like Ceph when we first create a volume in this backend storage. In fact, Cinder upstream has already had a similar function in Pike release. https://specs.openstack.org/openstack/cinder-specs/specs/liberty/image-volume-cache.html So I want to revert Raw caching function in StarlingX, and use Cinder generic image cache instead. The problem is that we need to update Cinder config in StarlingX. Any comments? Best wishes Lisa -------------- next part -------------- An HTML attachment was scrubbed... URL: From chenjie.xu at intel.com Tue Nov 13 10:46:53 2018 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Tue, 13 Nov 2018 10:46:53 +0000 Subject: [Starlingx-discuss] Example of RFE "Enable other subprojects to extend l2pop fdb information" for StarlingX Upstreaming Message-ID: Hi Allain, During the OpenStack driver meeting on last Friday, the community asked me to provide some examples of l2pop RPC payloads with this extension to this RFE. Could you please help review the example? The link for RFE: https://bugs.launchpad.net/neutron/+bug/1793653 The patch ID: 4ae5a58 Example: L2pop driver on server side: =============================== 1) when port binding or status or ip_address(or mac) is updated, notify this port's FDB(i.e port's ip address, mac, hosting agent's tunnel ip) to all agents 2) also checks if it is the first or last port on the hosting agent's network, if so a) notifies all agents to create/delete tunnels and flood flows to hosting agent b) notifies hosting agent about all the existing network ports on other agents(so that hosting agent can create tunnels, flood and unicast flows to these ports). For subproject networking-bgpvpn to extend l2pop fdbs: =============================== 1) when port binding or status or ip_address(or mac) is updated, notify this port's FDB(i.e port's ip address, mac, hosting agent's tunnel ip) to all agents No action 2) also checks if it is the first or last port on the hosting agent's network, if so a) notifies all agents to create/delete tunnels and flood flows to hosting agent No action b) notifies hosting agent about all the existing network ports on other agents(so that hosting agent can create tunnels, flood and unicast flows to these ports). Insert the ports information from BGPVPN to the FDB The network_id, segment_id and network_type are all from neutron. Becaue the network_id, segment_id and network_type relate to the port which triggers l2pop. network_id: comes from the port's network segment_id: comes from the segment which the port bounds to. network_type: comes from the port's network Thus networking-bgpvpn only needs to insert information into 'ports' as following: {75b21e39-15b9-4f12-8a60-1375a4dbdbef: {'segment_id': '12', 'network_type': 'vxlan', 'ports': {'12.66.1.1': [('fa:16:3e:d2:70:92', '168.177.1.23'),('fa:16:3e:f3:a4:21', '168.177.1.5')], '13.96.1.1': [('fa:16:3e:f9:cc:77', '169.177.1.16'),( 'fa:16:3e:a5:ee:f1', '169.177.1.12')]}}} 3) Update the BGPVPN gateway a) add a new gateway Use the L2populationAgentNotifyAPI in neutron\plugins\ml2\drivers\l2pop\rpc.py. For simplicity, we call L2populationAgentNotifyAPI as l2pop_notifier. l2pop_notifier. add_fdb_entries() network: the network associated with the BGPVPN network_id: network's id segment_id: network's "provider:segmentation_id". network_type: network's "provider:network_type" Thus networking-bgpvpn needs to call add_fdb_entries() to add the following fdb: {75b21e39-15b9-4f12-8a60-1375a4dbdbef: {'segment_id': '100', 'network_type': 'vxlan', 'ports': {'12.66.1.1': [('00:00:00:00:00:00', '0.0.0.0')]}}} b) withdraw an existing gateway l2pop_notifier. remove_fdb_entries() network: the network associated with the BGPVPN network_id: network's id segment_id: network's "provider:segmentation_id". network_type: network's "provider:network_type" Thus networking-bgpvpn needs to call add remove_fdb_entries() to remove the following fdb: {75b21e39-15b9-4f12-8a60-1375a4dbdbef: {'segment_id': '100', 'network_type': 'vxlan', 'ports': {'12.66.1.1': [('00:00:00:00:00:00', '0.0.0.0')]}}} 4) Delete BGPVPN l2pop_notifier. remove_fdb_entries() Similar to 3b but will remove all the fdbs belonging to the BGPVPN(including the gateway and all the devices in the BGPVPN) 5) Update BGPVPN device a) add new devices l2pop_notifier. add_fdb_entries() Similar to 3a but add new device's fdb information. b) withdraw existing devices l2pop_notifier. add_fdb_entries() Similar to 3b but remove the fdb information belonging to the devices which are withdrawn 6) BGP agent updates a) agent up l2pop_notifier. add_fdb_entries() Similar to 3a but add new device's fdb information l2pop_notifier. remove_fdb_entries() Similar to 3a but remove the fdb information belonging to the stale device b) agent down Similar to 3b but remove all the fdbs belonging to the agent(including the gateway and all the devices) 7) disassociated a VPN from a BGP speaker l2pop_notifier. remove_fdb_entries() Similar to 3b but remove the fdb information belonging to the BGPVPN whose association with a BGP speaker has been dropped. What's more, I have several questions: 1. it seems that the bgpvpn in stx-networking-bgpvpn can only be l2vpn according to the docstring in function _get_network_id. To support this RFE, whether it can be l3vpn or a bgpvpn can associate more than one network? 2. Could you please provide the network flow between a vm in neutron network and a device in bgpvpn? Suppose the fdb of the device in bgpvpn has been prepopulated. Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From volker.von.hoesslin at gmx.de Tue Nov 13 13:18:45 2018 From: volker.von.hoesslin at gmx.de (volker.von.hoesslin at gmx.de) Date: Tue, 13 Nov 2018 14:18:45 +0100 Subject: [Starlingx-discuss] Can not launch instance Message-ID: An HTML attachment was scrubbed... URL: From SkyDiablo at gmx.net Tue Nov 13 12:58:28 2018 From: SkyDiablo at gmx.net (SkyDiablo) Date: Tue, 13 Nov 2018 13:58:28 +0100 Subject: [Starlingx-discuss] =?utf-8?q?=28no_subject=29?= Message-ID: An HTML attachment was scrubbed... URL: From liang.a.fang at intel.com Tue Nov 13 15:23:38 2018 From: liang.a.fang at intel.com (Fang, Liang A) Date: Tue, 13 Nov 2018 15:23:38 +0000 Subject: [Starlingx-discuss] [glance] Analysis of patch c73ab48 (Enhanced-error-messages) for StartlingX upstreaming In-Reply-To: References: Message-ID: Hi Stefan I take a look at this issue today, the hang happened inside ceph. So I modified ceph code (function resize) to just raise exception rbd.NoSpace at the entry of the function. This issue can be simulated now. Regarding this patch, as I said previously, rbd (ceph) is just one type of the multiple types of backend, so I prefer to catch the rbd.NoSpace in glance_store (rbd.py), handle the exception there, and then re-raise a more common exception (StorageFull) to glance. Do you think this makes sense? If so, I will close the review in glance, and create a new review in glance_store. Regards Liang From: Dinescu, Stefan [mailto:Stefan.Dinescu at windriver.com] Sent: Monday, November 12, 2018 10:13 PM To: Fang, Liang A ; Badea, Daniel Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [glance] Analysis of patch c73ab48 (Enhanced-error-messages) for StartlingX upstreaming Hello, I havent' tested that part of the code in some time now, but from what I remember it was part of a larger set of changes to prevent ceph from hanging if not enough space was available. How it should work (but as I said, I haven't tested this in some time): - decrease the glance image pool quota (this is just so it's easier to test) - upload images to glance until space if almost full - the image that would have filled the pool should fail to upload entirely. It seems you are doing the correct procedure from what you described, so this probably requires a more in-depth investigation to see why it fails. ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Saturday, November 10, 2018 11:23 AM To: Badea, Daniel; Dinescu, Stefan Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [glance] Analysis of patch c73ab48 (Enhanced-error-messages) for StartlingX upstreaming Hi Daniel and Stefan Please refer to https://review.openstack.org/#/c/616880/ This patch is to provide detailed exception info when no space in rbd. But in my environment, if rbd has no space, the function call to rbd will not return, there's no exception raised. Details: In /usr/local/lib/python2.7/dist-packages/glance_store/_drivers/rbd.py - Function call will hang at line 484 (_create_image) if no space to create image at the beginning [cid:image001.png at 01D47B9B.E0DB9020] - Function call will hang at line 506 (image.resize) if no space at the middle of uploading. [cid:image002.png at 01D47B9B.E0DB9020] Could you please give some clue to reproduce this patch (raise rbd.NoSpace)? Couple of other thought: 1. This patch is to catch exception at v1 api, but v1 is about to be removed by community. 2. rbd is just one type of the multiple types of backend, so I think catch specific backend's exception at a common code is not so good. glance_store/rbd.py may be the better place to catch this exception. In fact rbd.py already did similar thing, see: [cid:image003.png at 01D47B9B.E0DB9020] Thanks Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 2947 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 1524 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8559 bytes Desc: image003.png URL: From Stefan.Dinescu at windriver.com Tue Nov 13 15:41:02 2018 From: Stefan.Dinescu at windriver.com (Dinescu, Stefan) Date: Tue, 13 Nov 2018 15:41:02 +0000 Subject: [Starlingx-discuss] [glance] Analysis of patch c73ab48 (Enhanced-error-messages) for StartlingX upstreaming In-Reply-To: References: , Message-ID: I think you are missing a glance_store patch for starlingx: https://github.com/openstack/stx-upstream/blob/master/openstack/python-glance-store/centos/patches/0001-Check-ceph-cluster-free-space-before-creating-image.patch This patch added aditional checks for ceph space requirments. I am saying this due to how you described the "self._create_image function" where it is missing a parameter added by the above patch. In our use-case, the image-size was always passed to the rbd driver code, so the resize function (which is only called when the size is zero) was never called. How the algorithm should work: - grab the size of the image that is about to be uploaded (we tested this through cli and horizon) - before uploading any data, check that ceph actually has space for that data - only after the check passes, we actually begin writing data to ceph We did this, because ceph actually blocked almost completely when a pool was full, requiring manual intervention to recover. The LVM backend behaved properly in such cases, so no fix was written for that. ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Tuesday, November 13, 2018 5:23 PM To: Dinescu, Stefan; Badea, Daniel Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [glance] Analysis of patch c73ab48 (Enhanced-error-messages) for StartlingX upstreaming Hi Stefan I take a look at this issue today, the hang happened inside ceph. So I modified ceph code (function resize) to just raise exception rbd.NoSpace at the entry of the function. This issue can be simulated now. Regarding this patch, as I said previously, rbd (ceph) is just one type of the multiple types of backend, so I prefer to catch the rbd.NoSpace in glance_store (rbd.py), handle the exception there, and then re-raise a more common exception (StorageFull) to glance. Do you think this makes sense? If so, I will close the review in glance, and create a new review in glance_store. Regards Liang From: Dinescu, Stefan [mailto:Stefan.Dinescu at windriver.com] Sent: Monday, November 12, 2018 10:13 PM To: Fang, Liang A ; Badea, Daniel Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [glance] Analysis of patch c73ab48 (Enhanced-error-messages) for StartlingX upstreaming Hello, I havent' tested that part of the code in some time now, but from what I remember it was part of a larger set of changes to prevent ceph from hanging if not enough space was available. How it should work (but as I said, I haven't tested this in some time): - decrease the glance image pool quota (this is just so it's easier to test) - upload images to glance until space if almost full - the image that would have filled the pool should fail to upload entirely. It seems you are doing the correct procedure from what you described, so this probably requires a more in-depth investigation to see why it fails. ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Saturday, November 10, 2018 11:23 AM To: Badea, Daniel; Dinescu, Stefan Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [glance] Analysis of patch c73ab48 (Enhanced-error-messages) for StartlingX upstreaming Hi Daniel and Stefan Please refer to https://review.openstack.org/#/c/616880/ This patch is to provide detailed exception info when no space in rbd. But in my environment, if rbd has no space, the function call to rbd will not return, there’s no exception raised. Details: In /usr/local/lib/python2.7/dist-packages/glance_store/_drivers/rbd.py - Function call will hang at line 484 (_create_image) if no space to create image at the beginning [cid:image001.png at 01D47B9B.E0DB9020] - Function call will hang at line 506 (image.resize) if no space at the middle of uploading. [cid:image002.png at 01D47B9B.E0DB9020] Could you please give some clue to reproduce this patch (raise rbd.NoSpace)? Couple of other thought: 1. This patch is to catch exception at v1 api, but v1 is about to be removed by community. 2. rbd is just one type of the multiple types of backend, so I think catch specific backend’s exception at a common code is not so good. glance_store/rbd.py may be the better place to catch this exception. In fact rbd.py already did similar thing, see: [cid:image003.png at 01D47B9B.E0DB9020] Thanks Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 2947 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 1524 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8559 bytes Desc: image003.png URL: From Don.Penney at windriver.com Tue Nov 13 15:57:12 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 13 Nov 2018 15:57:12 +0000 Subject: [Starlingx-discuss] Using %{_bindir} for executables in specfiles In-Reply-To: References: <8634a411-bc25-4d45-c577-2c7ed51ae025@linux.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA3E5B24@ALA-MBD.corp.ad.wrs.com> Seems reasonable to me. -----Original Message----- From: Victor Rodriguez [mailto:vm.rod25 at gmail.com] Sent: Monday, November 12, 2018 2:25 PM To: sgw at linux.intel.com Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Using %{_bindir} for executables in specfiles On Mon, Nov 12, 2018 at 3:19 AM Saul Wold wrote: > > > Folks, > > I noticed something today when I was reviewing one of the refactor > patches and it got me thinking (which is never a good thing when > jet-lagged). > > Why don't we use the RPM macro %{_bindir} which is /usr/bin by default? > I am not very fan of RPM macros , whoever for the multi OS target that we have it might work :) +1 from my side > I did a quick grep in the spec files and patches for spec files and > found that we current use systemctl, /bin/systemctl and > /usr/bin/systemctl. Not all OSes have a /bin/systemctl, so this might > fail later. > > I am going to recommend that we have a standard of using the RPM macros > when calling executables inside of RPM Spec files so that we have some > consistency. > > I am not saying we should to a mass find/replace right now, but as we > touch/update move to a consistent format, this will help later with > multi-os. > > If needed we can get a specification written around this concept. > > Thoughts, flames? > > Sau! > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cesar.lara at intel.com Tue Nov 13 21:13:04 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Tue, 13 Nov 2018 21:13:04 +0000 Subject: [Starlingx-discuss] [build] StarlingX ISO file now available at our Cengn mirror Message-ID: <0B566C62EC792145B40E29EFEBF1AB47105628DE@fmsmsx104.amr.corp.intel.com> Hello community We have an ISO file available at our Cengn mirror so people who wants to start playing with the StarlingX project can do so. I want to give out special thanks to Scott Little and Jason McKenna for making this happen in such timely manner. The image is hosted at http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/outputs/iso/ For more information about the mirror and other build and news from the build team please check our wiki. https://wiki.openstack.org/wiki/StarlingX/Build Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Tue Nov 13 21:33:37 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 13 Nov 2018 21:33:37 +0000 Subject: [Starlingx-discuss] Call for Agenda items - StarlingX Community Meeting - 11/14 Message-ID: <151EE31B9FCCA54397A757BC674650F0BA48304A@ALA-MBD.corp.ad.wrs.com> Hello, I will be chairing the StarlingX Wednesday community meeting tomorrow at 7am PT / 10am ET as Bruce is attending the Openstack summit in Berlin. Zoom link: https://zoom.us/j/342730236 Agenda/Minutes: https://etherpad.openstack.org/p/stx-status So far, there are no agenda items. If you have any items for discussion, please add them to the Etherpad above. Regards, Ghada -------------- next part -------------- An HTML attachment was scrubbed... URL: From jose.perez.carranza at intel.com Tue Nov 13 21:57:50 2018 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Tue, 13 Nov 2018 21:57:50 +0000 Subject: [Starlingx-discuss] Question about interface profile Message-ID: <0A5D9A624DF90343892F8F3FE7DE525A2A8FE71A@fmsmsx101.amr.corp.intel.com> Hi I have below scenario that is giving me an error when trying to unlock a controller, do I'm missing something in the process of creating a profile for an interface ? STEPS: 1. Create an interface profile via CLI using "system ifprofile-add " 2. Lock the node used to host the profile via CLI with "system host-lock" 3. On Horizon, edit the host by applying the interface profile created in step 1 4. Attempt to unlock host via CLI using "system host-unlock" RESULTS: Error seen in step four says "Cannot unlock host controller-1 without configuring a management interface". When checking the node's interface list using "system host-if-list" there appear two ethernet platforms--mgmt0 and enp2s1. Checking the locked host also provides a correctly filled-in mgmt_ip and mgmt_mac section. Output -> http://paste.openstack.org/show/734793/ Regards, José From juan.carlos.alonso at intel.com Wed Nov 14 00:00:22 2018 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Wed, 14 Nov 2018 00:00:22 +0000 Subject: [Starlingx-discuss] system pm-modify retention_secs=n Message-ID: <8557B550001AFB46A43A0CCC314BF85153C5C10B@FMSMSX108.amr.corp.intel.com> Hi, "Verify CLI system pm-modify does not require option action=apply" The step of such test cases is: "system pm-modify retention_secs=n" The output of this command is an error message: "system: error: argument : invalid choice: pm-modify". Seems that this command is not supported anymore. Do you know what is the correct command to apply or if there is something missing? I am don't understand what is the purpose of this command. I am using a Multimode Controller Storage. Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Wed Nov 14 00:44:15 2018 From: yong.hu at intel.com (Hu, Yong) Date: Wed, 14 Nov 2018 00:44:15 +0000 Subject: [Starlingx-discuss] [build] StarlingX ISO file now available at our Cengn mirror In-Reply-To: <0B566C62EC792145B40E29EFEBF1AB47105628DE@fmsmsx104.amr.corp.intel.com> References: <0B566C62EC792145B40E29EFEBF1AB47105628DE@fmsmsx104.amr.corp.intel.com> Message-ID: <1D109C16-047F-46C4-BC58-A541352679D9@intel.com> Hi Cesar, Thank you for sharing this great progress. With this, it’s more convenient for us to share ISO with customers who want to have a quick try. In addition, I would like to know whether or not Cengn has plan to share the *build mirrors* (RPMs, SRPMs, and other downloading packages) with community. If so, how soon will it be ready? Regards, Yong From: "Lara, Cesar" Date: Wednesday, 14 November 2018 at 5:15 AM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] [build] StarlingX ISO file now available at our Cengn mirror Hello community We have an ISO file available at our Cengn mirror so people who wants to start playing with the StarlingX project can do so. I want to give out special thanks to Scott Little and Jason McKenna for making this happen in such timely manner. The image is hosted at http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/outputs/iso/ For more information about the mirror and other build and news from the build team please check our wiki. https://wiki.openstack.org/wiki/StarlingX/Build Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Wed Nov 14 01:47:51 2018 From: yong.hu at intel.com (Hu, Yong) Date: Wed, 14 Nov 2018 01:47:51 +0000 Subject: [Starlingx-discuss] [Ironic] deploy bare metal by Ironic Message-ID: <4279697A-14A1-4819-8390-FB95C80E0CEB@intel.com> One customer asked how StarlingX supports bare metal support by Ironic. And they mentioned Titanium Cloud used to support it well. Anyone has the experience to deploy bare metal system by Ironic on StarlingX? Suggests and feedbacks are much appreciated! -------------- next part -------------- An HTML attachment was scrubbed... URL: From abraham.arce.moreno at intel.com Wed Nov 14 02:06:06 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Wed, 14 Nov 2018 02:06:06 +0000 Subject: [Starlingx-discuss] API requests: stx-ha Message-ID: stx-ha team, Based in some time spent within stx-ha, I found some mismatches between documentation and source code so I am kindly requesting your comments for questions "?" under each section [ Section ]. Let's assume the require X-Auth-Token is in place to authenticate, only URLs are shown. [ v1/ ] API documentation [0] includes the following services: - services - servicenodes - servicegroup And API queries shows those services plus additional ones: - servicenode - services - sm_sda - nodes - service_groups ? Should we target an update to the documentation in terms of number of services? ? Should we include the matching of names? e.g. servicegroup > service_group ? Anything we are not considering to have these differences as valid? Additionally, when we look at the name and description reported out by curl -i http://10.10.10.2:7777/ there is a mismatch between documentation [0] and source code [1] ? Documentation "description":"STX-HA Services API allows for the management of HA Services running on the Controller Cluster. This includes inventory collection and configuration of hosts, ports, interfaces, CPUs, disk, memory, and system configuration. The API also supports the configuration of the cloud's SNMP interface. ", "name":"STX-HA Services API" Source Code root.name = "System Management API" root.description = "System Management API from Wind River" ? I am assuming the correct information is from documentation since it was modified and the source code needs to be updated, is this a correct assumption? [ v1/servicenode] This specific service is the only one not available sending API requests but available in code [2]: $ curl -i http://10.10.10.2:7777/v1/servicenode ? Any special treatment / call for this service? ? Is this not available in Simplex configuration? This is the actual configuration I am requesting information to. Thanks for your initial support. [0] https://docs.starlingx.io/api-ref/stx-ha/ [1] https://git.openstack.org/cgit/openstack/stx-ha/tree/service-mgmt-api/sm-api/sm_api/api/controllers/root.py [2] https://git.openstack.org/cgit/openstack/stx-ha/tree/service-mgmt-api/sm-api/sm_api/api/controllers/v1 From liang.a.fang at intel.com Wed Nov 14 04:18:57 2018 From: liang.a.fang at intel.com (Fang, Liang A) Date: Wed, 14 Nov 2018 04:18:57 +0000 Subject: [Starlingx-discuss] [glance] Analysis of patch c73ab48 (Enhanced-error-messages) for StartlingX upstreaming In-Reply-To: References: , Message-ID: Hi Stefan Thanks for the info. The patch you mentioned is not in the upstreaming patch list. I take a look at this patch, it looks more like a workaround for the bug of ceph. It checks the available space in ceph, and goes ahead to create image only if there's enough space in ceph. - This patch assumed image size always be given, but this is not the case in current upstream glance. I know there're patches in cinder and glanceclient to specify image size, I'm working on upstreaming these patches. These patches can improve the uploading performance(about 30%) because no resize will happen when creating an image with exact and large enough size. But cinder is not the only client of glance, at least we cannot assume this, so we still cannot assume image size always be given. Maybe the assumption is correct before starlingx be open sourced. - Even if image size always be given, this patch may also cannot handle all the cases. E.g. o Some images be created simultaneously by glance o The quote of ceph pool happened to be changed o The ceph pool be consumed by other app though this may rarely happen I'm not sure if these are the reasons of not triaged this patch to the upstreaming patch list. Go back to the patch c73ab48 (Enhanced-error-messages), this assumes rbd.NoSpace exception will happen, right? So do you agree to catch this exception in rbd.py? Regards Liang From: Dinescu, Stefan [mailto:Stefan.Dinescu at windriver.com] Sent: Tuesday, November 13, 2018 11:41 PM To: Fang, Liang A ; Badea, Daniel Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [glance] Analysis of patch c73ab48 (Enhanced-error-messages) for StartlingX upstreaming I think you are missing a glance_store patch for starlingx: https://github.com/openstack/stx-upstream/blob/master/openstack/python-glance-store/centos/patches/0001-Check-ceph-cluster-free-space-before-creating-image.patch This patch added aditional checks for ceph space requirments. I am saying this due to how you described the "self._create_image function" where it is missing a parameter added by the above patch. In our use-case, the image-size was always passed to the rbd driver code, so the resize function (which is only called when the size is zero) was never called. How the algorithm should work: - grab the size of the image that is about to be uploaded (we tested this through cli and horizon) - before uploading any data, check that ceph actually has space for that data - only after the check passes, we actually begin writing data to ceph We did this, because ceph actually blocked almost completely when a pool was full, requiring manual intervention to recover. The LVM backend behaved properly in such cases, so no fix was written for that. ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Tuesday, November 13, 2018 5:23 PM To: Dinescu, Stefan; Badea, Daniel Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [glance] Analysis of patch c73ab48 (Enhanced-error-messages) for StartlingX upstreaming Hi Stefan I take a look at this issue today, the hang happened inside ceph. So I modified ceph code (function resize) to just raise exception rbd.NoSpace at the entry of the function. This issue can be simulated now. Regarding this patch, as I said previously, rbd (ceph) is just one type of the multiple types of backend, so I prefer to catch the rbd.NoSpace in glance_store (rbd.py), handle the exception there, and then re-raise a more common exception (StorageFull) to glance. Do you think this makes sense? If so, I will close the review in glance, and create a new review in glance_store. Regards Liang From: Dinescu, Stefan [mailto:Stefan.Dinescu at windriver.com] Sent: Monday, November 12, 2018 10:13 PM To: Fang, Liang A >; Badea, Daniel > Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [glance] Analysis of patch c73ab48 (Enhanced-error-messages) for StartlingX upstreaming Hello, I havent' tested that part of the code in some time now, but from what I remember it was part of a larger set of changes to prevent ceph from hanging if not enough space was available. How it should work (but as I said, I haven't tested this in some time): - decrease the glance image pool quota (this is just so it's easier to test) - upload images to glance until space if almost full - the image that would have filled the pool should fail to upload entirely. It seems you are doing the correct procedure from what you described, so this probably requires a more in-depth investigation to see why it fails. ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Saturday, November 10, 2018 11:23 AM To: Badea, Daniel; Dinescu, Stefan Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [glance] Analysis of patch c73ab48 (Enhanced-error-messages) for StartlingX upstreaming Hi Daniel and Stefan Please refer to https://review.openstack.org/#/c/616880/ This patch is to provide detailed exception info when no space in rbd. But in my environment, if rbd has no space, the function call to rbd will not return, there's no exception raised. Details: In /usr/local/lib/python2.7/dist-packages/glance_store/_drivers/rbd.py - Function call will hang at line 484 (_create_image) if no space to create image at the beginning [cid:image001.png at 01D47C0A.94F63E70] - Function call will hang at line 506 (image.resize) if no space at the middle of uploading. [cid:image002.png at 01D47C0A.94F63E70] Could you please give some clue to reproduce this patch (raise rbd.NoSpace)? Couple of other thought: 1. This patch is to catch exception at v1 api, but v1 is about to be removed by community. 2. rbd is just one type of the multiple types of backend, so I think catch specific backend's exception at a common code is not so good. glance_store/rbd.py may be the better place to catch this exception. In fact rbd.py already did similar thing, see: [cid:image003.png at 01D47C0A.94F63E70] Thanks Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 2947 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 1524 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8559 bytes Desc: image003.png URL: From austin.sun at intel.com Wed Nov 14 05:54:21 2018 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 14 Nov 2018 05:54:21 +0000 Subject: [Starlingx-discuss] Support IBRS cpu model. Message-ID: Hi All: if install StarlingX in compute-node with cpu type 'Skylake-Server-IBRS' , it cannot use 'passthrough' type with keyword hw:cpu_model in favor to create instance It will prompt "No valid host was found. There are not enough hosts available. computer-0: (VCpuModelFilter) Host VCPU model Skylake-Server-IBRS required Passthrough Code 501" After investigation , Libvirt 4.7.0 supports *IBRS (for example IvyBridge-IBRS, Skylake-Server-IBRS) CPU model , but nova and meta favor does not support *IBRS CPU model yet. I have made patch for nova[0] and glance[1]. Nova[0] will support *-IBRS type vcpu when select passthrough Glance[1] will add metadata to support *-IBRS in hw:cpu_model Please review these PRs. Thanks. BR Austin Sun. [0] https://github.com/starlingx-staging/stx-nova/pull/15 [1] https://github.com/starlingx-staging/stx-glance/pull/4 From cindy.xie at intel.com Wed Nov 14 06:02:57 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 14 Nov 2018 06:02:57 +0000 Subject: [Starlingx-discuss] Support IBRS cpu model. In-Reply-To: References: Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35DC4B9D@SHSMSX104.ccr.corp.intel.com> Austin, Is this bug related to your finding? https://bugs.launchpad.net/starlingx/+bug/1801773 thx. - cindy -----Original Message----- From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Wednesday, November 14, 2018 1:54 PM To: 'starlingx-discuss at lists.starlingx.io' Cc: He, Zhiwei Subject: [Starlingx-discuss] Support IBRS cpu model. Hi All: if install StarlingX in compute-node with cpu type 'Skylake-Server-IBRS' , it cannot use 'passthrough' type with keyword hw:cpu_model in favor to create instance It will prompt "No valid host was found. There are not enough hosts available. computer-0: (VCpuModelFilter) Host VCPU model Skylake-Server-IBRS required Passthrough Code 501" After investigation , Libvirt 4.7.0 supports *IBRS (for example IvyBridge-IBRS, Skylake-Server-IBRS) CPU model , but nova and meta favor does not support *IBRS CPU model yet. I have made patch for nova[0] and glance[1]. Nova[0] will support *-IBRS type vcpu when select passthrough Glance[1] will add metadata to support *-IBRS in hw:cpu_model Please review these PRs. Thanks. BR Austin Sun. [0] https://github.com/starlingx-staging/stx-nova/pull/15 [1] https://github.com/starlingx-staging/stx-glance/pull/4 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From austin.sun at intel.com Wed Nov 14 06:21:17 2018 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 14 Nov 2018 06:21:17 +0000 Subject: [Starlingx-discuss] Support IBRS cpu model. In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F35DC4B9D@SHSMSX104.ccr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F35DC4B9D@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi Cindy: It should be same issue. I was not aware bug#1801773, so I created another bug#1803280. I have just duplicated bug#1803280 to bug#1801773. Thanks. BR Austin Sun. -----Original Message----- From: Xie, Cindy Sent: Wednesday, November 14, 2018 2:03 PM To: Sun, Austin ; 'starlingx-discuss at lists.starlingx.io' Cc: He, Zhiwei Subject: RE: [Starlingx-discuss] Support IBRS cpu model. Austin, Is this bug related to your finding? https://bugs.launchpad.net/starlingx/+bug/1801773 thx. - cindy -----Original Message----- From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Wednesday, November 14, 2018 1:54 PM To: 'starlingx-discuss at lists.starlingx.io' Cc: He, Zhiwei Subject: [Starlingx-discuss] Support IBRS cpu model. Hi All: if install StarlingX in compute-node with cpu type 'Skylake-Server-IBRS' , it cannot use 'passthrough' type with keyword hw:cpu_model in favor to create instance It will prompt "No valid host was found. There are not enough hosts available. computer-0: (VCpuModelFilter) Host VCPU model Skylake-Server-IBRS required Passthrough Code 501" After investigation , Libvirt 4.7.0 supports *IBRS (for example IvyBridge-IBRS, Skylake-Server-IBRS) CPU model , but nova and meta favor does not support *IBRS CPU model yet. I have made patch for nova[0] and glance[1]. Nova[0] will support *-IBRS type vcpu when select passthrough Glance[1] will add metadata to support *-IBRS in hw:cpu_model Please review these PRs. Thanks. BR Austin Sun. [0] https://github.com/starlingx-staging/stx-nova/pull/15 [1] https://github.com/starlingx-staging/stx-glance/pull/4 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Rajesh.Jha at rsystems.com Wed Nov 14 12:59:08 2018 From: Rajesh.Jha at rsystems.com (Rajesh Jha) Date: Wed, 14 Nov 2018 18:29:08 +0530 Subject: [Starlingx-discuss] Latest build failure Message-ID: <2F61A2101B4FD447A683EF7E362CF9421C63E21841@RSI-NOD-EXMDB6.india.rsystems.com> Hi, I am trying to build starlingx iso. After step repo sync -j`nproc` it is failing because of some checkouts. Kindly see the attached screenshot. Error is as follows. error: cgcs-root/stx/stx-integ/: stx-integ.git checkout afb2aabe13642f2100039e7f86a482986d001fc3 error: stx-tools/: stx-tools.git checkout 779e2ff4c61986fc47d28c00d18096cf74c5cdcc Best Regards, Rajesh Jha The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, please immediately alert the sender by reply e-mail and then delete this message. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. R Systems has taken every reasonable precaution to minimize the risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. -------------- next part -------------- A non-text attachment was scrubbed... Name: reposync_fail.png Type: image/png Size: 363646 bytes Desc: reposync_fail.png URL: From Bin.Qian at windriver.com Wed Nov 14 14:31:48 2018 From: Bin.Qian at windriver.com (Qian, Bin) Date: Wed, 14 Nov 2018 14:31:48 +0000 Subject: [Starlingx-discuss] API requests: stx-ha In-Reply-To: References: Message-ID: There are 2 parts of the api. The ones in the API document (services, nodes, and service_groups) are open for customers to develop their own 3 party applications. Note that servicegroup in the document should be "service_groups", and servicenodes should be nodes, the document is incorrect. Then there are 2 extra internal APIs: nodes, and sm_sda, these two are used internally by other StarlingX services, to provide important function, such as swact, lock controller, etc. We didn't want the customer to use such APIs, that's why they are not in the API document as they don't represent a full function. If they want swact or lock node, they should use sysinv-api functions instead. Above is a little background. For the questions, ? Should we target an update to the documentation in terms of number of services? A: I think we should keep the current internal APIs out from the document for the customers. ? Should we include the matching of names? e.g. servicegroup > service_group A: yes, we should update the document to change servicegroup ->service_groups. We should also update the document to change servicenode to nodes. servicenode is a valid but internal use only REST api. ? Anything we are not considering to have these differences as valid? A: See the background info. ? I am assuming the correct information is from documentation since it was modified and the source code needs to be updated, is this a correct assumption? A: The document is not correct. The source code version is accurate. ? Any special treatment / call for this service? A: servicenode is a post request, it require multiple parameters for different functions, such as swact-precheck and lock-precheck ? Is this not available in Simplex configuration? This is the actual con"figuration I am requesting information to. A: it is available in all configurations, include simplex Regards, Bin ________________________________________ From: Arce Moreno, Abraham [abraham.arce.moreno at intel.com] Sent: Tuesday, November 13, 2018 6:06 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] API requests: stx-ha stx-ha team, Based in some time spent within stx-ha, I found some mismatches between documentation and source code so I am kindly requesting your comments for questions "?" under each section [ Section ]. Let's assume the require X-Auth-Token is in place to authenticate, only URLs are shown. [ v1/ ] API documentation [0] includes the following services: - services - servicenodes - servicegroup And API queries shows those services plus additional ones: - servicenode - services - sm_sda - nodes - service_groups ? Should we target an update to the documentation in terms of number of services? ? Should we include the matching of names? e.g. servicegroup > service_group ? Anything we are not considering to have these differences as valid? Additionally, when we look at the name and description reported out by curl -i http://10.10.10.2:7777/ there is a mismatch between documentation [0] and source code [1] ? Documentation "description":"STX-HA Services API allows for the management of HA Services running on the Controller Cluster. This includes inventory collection and configuration of hosts, ports, interfaces, CPUs, disk, memory, and system configuration. The API also supports the configuration of the cloud's SNMP interface. ", "name":"STX-HA Services API" Source Code root.name = "System Management API" root.description = "System Management API from Wind River" ? I am assuming the correct information is from documentation since it was modified and the source code needs to be updated, is this a correct assumption? [ v1/servicenode] This specific service is the only one not available sending API requests but available in code [2]: $ curl -i http://10.10.10.2:7777/v1/servicenode ? Any special treatment / call for this service? ? Is this not available in Simplex configuration? This is the actual configuration I am requesting information to. Thanks for your initial support. [0] https://docs.starlingx.io/api-ref/stx-ha/ [1] https://git.openstack.org/cgit/openstack/stx-ha/tree/service-mgmt-api/sm-api/sm_api/api/controllers/root.py [2] https://git.openstack.org/cgit/openstack/stx-ha/tree/service-mgmt-api/sm-api/sm_api/api/controllers/v1 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cindy.xie at intel.com Wed Nov 14 14:53:03 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 14 Nov 2018 14:53:03 +0000 Subject: [Starlingx-discuss] Minutes: Weekly StarlingX non-OpenStack Distro meeting, 11/15 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35DC56EB@SHSMSX104.ccr.corp.intel.com> Agenda & Notes for 11/15 meeting: 1. non-OpenStack patch refactoring status (Zhipeng/Shuicheng) 79 meta patches have been removed by the refactoring work; and more to come after we start working on 4 remaining tasks. 2. kernel driver upgrade testing update (Ada/Shuicheng) lacking of server w/ QAT feature. asking GDC local teams. some problem of HW PCI card detection. May have HW issue due to they are not production version. will find right HW. DRBD patch also require NIC driver. no problems with installation so far: load the driver. Pending the testing until we get the 2nd server. more test plan on top of the test cases from Numan. installing Duplex, reboot and launching VM, live migrations, etc. hopefully we expect the test results by end of next week. use the ISO Ada have to get the test plan, test environment ready; Shuicheng can provide 2nd ISO with drivers rebased to the latest code base. 3. Python2to3 non-openStack status brief (Austin) for Flocks project, we have 4 projects not fully implemented: nfv, config, ha & integ still not fully p3 compatible. we may need to add more stories for the 3rd party sRPM P3 readiness and the solution how to address them. Review the complete picture in next meeting. 4. Ceph upgrade status (Vivian/Dehao) Scott provide new option: Option2.4 with detail suggestions for the build_srpm scripts. did some quick investigation and proved the option works from Dehao's side. - use base code from stx-ceph 13.x staging branch - write ceph custmization scripts: srpm_build - in this scripts, call ceph tools for preparation work. - change the last commit ID question: if we follow this option2.4, no impact to the build process current have, which was the original concern from Brent; Scott also do not prefer to use srpm directly, and that's why we need to build srpm by ourselves. still meet some technical issue for example failed to download submodules, still need Scott's technical support to ensure the path can work smoothly for Ceph team. Dehao to continue working w/ community to address the patch concern and upload new patch sets. status from Changcheng regarding patch rebase: 42 patches in total with 32 patches ported to v13. Other 10 patches have been abandamed. Can create PR against staging branch and mark it as "WIP" so that WR engineers can provide early feedback regarding the patch porting work; Changcheng can also send emails to ML to seek feedbacks. 5. 2019.03 release content, any additon? bare-metal support through Ironic: is this feature part of StarlingX? We'd like to have the feature in 2019.03 if this is not yet. 6. Opens (all) None -----Original Appointment----- From: Xie, Cindy Sent: Monday, November 5, 2018 2:27 PM To: Xie, Cindy; Wold, Saul; 'Rowsell, Brent'; Jones, Bruce E; Troyer, Dean; 'Khalil, Ghada'; Waheed, Numan; Lin, Shuicheng; Zhu, Vivian; Shang, Dehao; Liu, ZhipengS; Hu, Yong; Sun, Austin; Somerville, Jim; starlingx-discuss at lists.starlingx.io Cc: Perez Carranza, Jose; 'Hellmann, Gil'; 'Waines, Greg'; 'Chen, Jacky'; Armstrong, Robert H; Perez Rodriguez, Humberto I; Martinez Landa, Hayde; Martinez Monroy, Elio; Hu, Wei W; 'Seiler, Glenn'; 'Eslimi, Dariush'; Gomez, Juan P; Lara, Cesar; Young, Ken; Arce Moreno, Abraham Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, November 14, 2018 6:00 AM-7:00 AM (UTC-08:00) Pacific Time (US & Canada). Where: https://zoom.us/j/342730236 . Cadence and time slot: o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) . Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ . Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other From scott.little at windriver.com Wed Nov 14 14:57:20 2018 From: scott.little at windriver.com (Scott Little) Date: Wed, 14 Nov 2018 09:57:20 -0500 Subject: [Starlingx-discuss] [build] StarlingX ISO file now available at our Cengn mirror In-Reply-To: <1D109C16-047F-46C4-BC58-A541352679D9@intel.com> References: <0B566C62EC792145B40E29EFEBF1AB47105628DE@fmsmsx104.amr.corp.intel.com> <1D109C16-047F-46C4-BC58-A541352679D9@intel.com> Message-ID: <1a3ebbad-e2bd-bcc3-25be-5f3bf56ec7f9@windriver.com> Yes, that will be coming soon. Scott On 18-11-13 07:44 PM, Hu, Yong wrote: > > Hi Cesar, > > Thank you for sharing this great progress. With this, it’s more > convenient for us to share ISO with customers who want to have a quick > try. > > In addition, I would like to know whether or not Cengn has plan to > share the **build mirrors** (RPMs, SRPMs, and other downloading > packages) with community. > > If so, how soon will it be ready? > > Regards, > > Yong > > *From: *"Lara, Cesar" > *Date: *Wednesday, 14 November 2018 at 5:15 AM > *To: *"starlingx-discuss at lists.starlingx.io" > > *Subject: *[Starlingx-discuss] [build] StarlingX ISO file now > available at our Cengn mirror > > Hello community > > We have an ISO file available at our Cengn mirror so people who wants > to start playing with the StarlingX project can do so. I want to give > out special thanks to Scott Little and Jason McKenna for making this > happen in such timely manner. > > The image is hosted at > > http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/outputs/iso/ > > For more information about the mirror and other build and news from > the build team please check our wiki. > > https://wiki.openstack.org/wiki/StarlingX/Build > > Regards > > *//* > > */Cesar Lara/* > > Software Engineering Manager > > OpenSource Technology Center > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Wed Nov 14 16:02:59 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 14 Nov 2018 16:02:59 +0000 Subject: [Starlingx-discuss] Community meeting minutes - Nov 14 2018 Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4832EA@ALA-MBD.corp.ad.wrs.com> Minutes are available on etherpad at: https://etherpad.openstack.org/p/stx-status Agenda and Notes - November 14th call: - Several StarlingX team members are attending the Openstack Summit in Berlin. - Expect updates in the next community meeting - Build Update: - stx.2018.10 ISO now available for download on CENGN - Email sent to the community - Validation cycle was run on the ISO before the announcement was sent - The build team is discussing whether they will generate ISOs from master on a regular cadence - The discussion will need to cover what validation is done before releasing each ISO - Distro.other Update - Made good progress on patch reduction of meta patches - Working on scoping and resourcing the March release team deliverables - Ceph upgrade: team made progress by following Scott's suggestion related to using git source repo (stx-ceph repo on stx-staging). Once the repo is ready, the storage team will upload the WIP patch. Frank will have a storage expert do an early review once avialable. - Test Update - Deployment of 4 configurations is now fully automated: simplex, duplex, multi-node (local storage), multi-node (external storage) - Automated sanity is now running in the 4 above configurations. - Team continues to focus on automating test-cases - In the next two weeks, working on a proposal for the test plan for the March release. Expect first draft by early December. From Numan.Waheed at windriver.com Wed Nov 14 16:33:16 2018 From: Numan.Waheed at windriver.com (Waheed, Numan) Date: Wed, 14 Nov 2018 16:33:16 +0000 Subject: [Starlingx-discuss] system pm-modify retention_secs=n In-Reply-To: <8557B550001AFB46A43A0CCC314BF85153C5C10B@FMSMSX108.amr.corp.intel.com> References: <8557B550001AFB46A43A0CCC314BF85153C5C10B@FMSMSX108.amr.corp.intel.com> Message-ID: <3CAA827B7A79BA46B15B280EC82088FE4822FC0D@ALA-MBD.corp.ad.wrs.com> Hi Juan, This command is not supported anymore. Following are the commands that should be used. system service-parameter-add system service-parameter-apply system service-parameter-delete system service-parameter-list system service-parameter-modify system service-parameter-show Thanks, Numan. From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: November-13-18 7:00 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] system pm-modify retention_secs=n Hi, "Verify CLI system pm-modify does not require option action=apply" The step of such test cases is: "system pm-modify retention_secs=n" The output of this command is an error message: "system: error: argument : invalid choice: pm-modify". Seems that this command is not supported anymore. Do you know what is the correct command to apply or if there is something missing? I am don't understand what is the purpose of this command. I am using a Multimode Controller Storage. Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From cesar.lara at intel.com Wed Nov 14 21:26:36 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Wed, 14 Nov 2018 21:26:36 +0000 Subject: [Starlingx-discuss] [build][meetings] Canceled for 11/15/2018 Message-ID: <0B566C62EC792145B40E29EFEBF1AB4710563D49@fmsmsx104.amr.corp.intel.com> Team Since there are a couple folks attending events during this week, I've decided to skip our meeting for this week We are currently just waiting to finish the complete availability of the Cengn mirror and working on the second part of the Koji based build infrastructure proposal which are the tools for developers/contributors we also have pending the mirror creator script refactor by Marcela that we can go over next week. Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From volker.von.hoesslin at gmx.de Thu Nov 15 09:03:20 2018 From: volker.von.hoesslin at gmx.de (volker.von.hoesslin at gmx.de) Date: Thu, 15 Nov 2018 10:03:20 +0100 Subject: [Starlingx-discuss] Can not launch instance In-Reply-To: References: Message-ID: An HTML attachment was scrubbed... URL: From Stefan.Dinescu at windriver.com Thu Nov 15 10:15:22 2018 From: Stefan.Dinescu at windriver.com (Dinescu, Stefan) Date: Thu, 15 Nov 2018 10:15:22 +0000 Subject: [Starlingx-discuss] Can not launch instance In-Reply-To: References: , Message-ID: hello, Just a few quick questions to eliminate some potential issues (or maybe even figure out the issue): 1. Are the storage nodes in an available state? 2. On the compute nodes, is nova-local configures for remote backing as well? To check use "system host-lvg-show compute-0 nova-local" and check the "instance_backing" parameter. ________________________________ From: volker.von.hoesslin at gmx.de [volker.von.hoesslin at gmx.de] Sent: Thursday, November 15, 2018 11:03 AM To: starlingx Subject: Re: [Starlingx-discuss] Can not launch instance ok, after download the first official ISO (Cengn-mirror) and reinstall the complete starlingX i got the same error. for now, i can see some lines in "/var/log/nova/nova-scheduler.log". i have pasted here: https://pastebin.com/TbvYwTqu i really need a running openstack and i am willing to spend money for service, please help me guys... volker... i don't understand that, either i am the only one who builds a starlingX-stack at all or i have to fight very hard for all the additional knowledge i need in addition to the install-doku... now i have created all necessary components: - external network - internal network - router (add external and internal network) - add flavoir (aggregate_instance_extra_specs:storage=remote) - add image (cirrOS 0.4.0 RAW/QCOW2) - add key pairs now i created a new instance (via horizon/CLI), without success. the instance is created but it ends in an error-stat :( error messages in the horizon GUI are meaningless for me: Fault Message: No valid host was found. There are not enough hosts available. compute-0: (RetryFilter) Previously tried: [[u'compute-1', u'compute-1'], [u'compute-0', u'compute-0']], compute-1: (RetryFilter) Previously tried: [[u'compute-1', u'compute-1'], [u'compute-0 Code: 501 Details: compute-0: (RetryFilter) Previously tried: [[u'compute-1', u'compute-1'], [u'compute-0', u'compute-0']], compute-1: (RetryFilter) Previously tried: [[u'compute-1', u'compute-1'], [u'compute-0', u'compute-0']] Created: Nov. 13, 2018, 11:49 a.m. ================================================ Alarm UUID: 15f5bc85-de93-4109-a278-425bafc7c997 Alarm ID: 700.001 Severity: critical Alarm State: set Alarm Type: processing-error Timestamp: Nov. 13, 2018, 11:49 a.m. Suppression: Entity Instance ID: tenant=571bfa02-4736-4359-a15d-871224b3b202.instance=3ef09380-47e6-479a-91cc-6813474a183d Entity Type ID: tenant.instance Probable Cause: underlying-resource-unavailable Proposed Repair Action: Manual intervention required Service Affecting: True Management Affecting: True Reason: Instance foobar123 owned by admin has failed to schedule Interesting is, half of the instance is missing: @see: https://imgur.com/a/UVmEZhF - missing NIC - missing IP Addresses - missing Security Groups - missing Volumes Attached does anyone still have a tip for me? Volker -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Thu Nov 15 10:25:10 2018 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Thu, 15 Nov 2018 10:25:10 +0000 Subject: [Starlingx-discuss] Can not launch instance In-Reply-To: References: , Message-ID: cool, thanks for your feedback! i've already read and understood the topic with the backing. i'm now so far that it seems to work if I create an instance without the security-groups (default-group) specification, i don't know why exactly. as far as i've understood it now, it's supposed to have something to do with "port-security-enabled=false"? sorry that i got in touch with the group so quickly before i exhausted all my possibilities... I promise improvement ;) Von: Dinescu, Stefan [mailto:Stefan.Dinescu at windriver.com] Gesendet: Donnerstag, 15. November 2018 11:15 An: volker.von.hoesslin at gmx.de; starlingx Betreff: Re: [Starlingx-discuss] Can not launch instance hello, Just a few quick questions to eliminate some potential issues (or maybe even figure out the issue): 1. Are the storage nodes in an available state? 2. On the compute nodes, is nova-local configures for remote backing as well? To check use "system host-lvg-show compute-0 nova-local" and check the "instance_backing" parameter. ________________________________ From: volker.von.hoesslin at gmx.de [volker.von.hoesslin at gmx.de] Sent: Thursday, November 15, 2018 11:03 AM To: starlingx Subject: Re: [Starlingx-discuss] Can not launch instance ok, after download the first official ISO (Cengn-mirror) and reinstall the complete starlingX i got the same error. for now, i can see some lines in "/var/log/nova/nova-scheduler.log". i have pasted here: https://pastebin.com/TbvYwTqu i really need a running openstack and i am willing to spend money for service, please help me guys... volker... i don't understand that, either i am the only one who builds a starlingX-stack at all or i have to fight very hard for all the additional knowledge i need in addition to the install-doku... now i have created all necessary components: - external network - internal network - router (add external and internal network) - add flavoir (aggregate_instance_extra_specs:storage=remote) - add image (cirrOS 0.4.0 RAW/QCOW2) - add key pairs now i created a new instance (via horizon/CLI), without success. the instance is created but it ends in an error-stat :( error messages in the horizon GUI are meaningless for me: Fault Message: No valid host was found. There are not enough hosts available. compute-0: (RetryFilter) Previously tried: [[u'compute-1', u'compute-1'], [u'compute-0', u'compute-0']], compute-1: (RetryFilter) Previously tried: [[u'compute-1', u'compute-1'], [u'compute-0 Code: 501 Details: compute-0: (RetryFilter) Previously tried: [[u'compute-1', u'compute-1'], [u'compute-0', u'compute-0']], compute-1: (RetryFilter) Previously tried: [[u'compute-1', u'compute-1'], [u'compute-0', u'compute-0']] Created: Nov. 13, 2018, 11:49 a.m. ================================================ Alarm UUID: 15f5bc85-de93-4109-a278-425bafc7c997 Alarm ID: 700.001 Severity: critical Alarm State: set Alarm Type: processing-error Timestamp: Nov. 13, 2018, 11:49 a.m. Suppression: Entity Instance ID: tenant=571bfa02-4736-4359-a15d-871224b3b202.instance=3ef09380-47e6-479a-91cc-6813474a183d Entity Type ID: tenant.instance Probable Cause: underlying-resource-unavailable Proposed Repair Action: Manual intervention required Service Affecting: True Management Affecting: True Reason: Instance foobar123 owned by admin has failed to schedule Interesting is, half of the instance is missing: @see: https://imgur.com/a/UVmEZhF - missing NIC - missing IP Addresses - missing Security Groups - missing Volumes Attached does anyone still have a tip for me? Volker -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Thu Nov 15 13:39:08 2018 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Thu, 15 Nov 2018 13:39:08 +0000 Subject: [Starlingx-discuss] instance load-balancing Message-ID: Hi there! How or does starlingX support load-balancing out of the box? and next question, what about auto-scaling? Greez & thx, Volker... -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Thu Nov 15 14:15:56 2018 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Thu, 15 Nov 2018 14:15:56 +0000 Subject: [Starlingx-discuss] DBaaS / Trove ? Message-ID: Hi, are there already plans to integrate DBaaS (Trove) or is that already available only I haven't found it yet? Volker... -------------- next part -------------- An HTML attachment was scrubbed... URL: From James.Gauld at windriver.com Thu Nov 15 14:24:00 2018 From: James.Gauld at windriver.com (Gauld, James) Date: Thu, 15 Nov 2018 14:24:00 +0000 Subject: [Starlingx-discuss] Can not launch instance In-Reply-To: References: , Message-ID: <8E5740EC88EF3E4BA3196F2545DC8625BA1A07DA@ALA-MBD.corp.ad.wrs.com> Volker, The nova-scheduler.log indicates rejection reasons per host as they get filtered out for various reasons. They look like this: ' (compute-x) REJECT: '. From your pastebin result, I only saw the RetryFilter. You got "SCHED: PASS. Selected compute-x", that means it actually attempted to launch on that compute. There is something failing during the launch on the compute, so you get scheduling retries on other computes. That is why you see messages like "RetryFilter: (compute-1) REJECT: Previously tried: [[u'compute-0', .." Log into each compute and look for error/exceptions in /var/log/nova/nova-compute.log at the specific timestamp of launch. A similar error message will likely present in the nova-conductor.log (on the controller). Depending on the specific error, you may need to dig into other logs on the compute (eg, /var/log/kern.log, /var/log/libvirt/qemu/instance-.log, /var/log/libvirt/libvirtd.log, /var/log/openstack.log, etc). This should give hints. Some of the logs are extraneous noise, so focus near the exact timestamp. -jim From: von Hoesslin, Volker [mailto:Volker.Hoesslin at swsn.de] Sent: November-15-18 5:25 AM To: starlingx Subject: Re: [Starlingx-discuss] Can not launch instance cool, thanks for your feedback! i've already read and understood the topic with the backing. i'm now so far that it seems to work if I create an instance without the security-groups (default-group) specification, i don't know why exactly. as far as i've understood it now, it's supposed to have something to do with "port-security-enabled=false"? sorry that i got in touch with the group so quickly before i exhausted all my possibilities... I promise improvement ;) Von: Dinescu, Stefan [mailto:Stefan.Dinescu at windriver.com] Gesendet: Donnerstag, 15. November 2018 11:15 An: volker.von.hoesslin at gmx.de; starlingx Betreff: Re: [Starlingx-discuss] Can not launch instance hello, Just a few quick questions to eliminate some potential issues (or maybe even figure out the issue): 1. Are the storage nodes in an available state? 2. On the compute nodes, is nova-local configures for remote backing as well? To check use "system host-lvg-show compute-0 nova-local" and check the "instance_backing" parameter. ________________________________ From: volker.von.hoesslin at gmx.de [volker.von.hoesslin at gmx.de] Sent: Thursday, November 15, 2018 11:03 AM To: starlingx Subject: Re: [Starlingx-discuss] Can not launch instance ok, after download the first official ISO (Cengn-mirror) and reinstall the complete starlingX i got the same error. for now, i can see some lines in "/var/log/nova/nova-scheduler.log". i have pasted here: https://pastebin.com/TbvYwTqu i really need a running openstack and i am willing to spend money for service, please help me guys... volker... i don't understand that, either i am the only one who builds a starlingX-stack at all or i have to fight very hard for all the additional knowledge i need in addition to the install-doku... now i have created all necessary components: - external network - internal network - router (add external and internal network) - add flavoir (aggregate_instance_extra_specs:storage=remote) - add image (cirrOS 0.4.0 RAW/QCOW2) - add key pairs now i created a new instance (via horizon/CLI), without success. the instance is created but it ends in an error-stat :( error messages in the horizon GUI are meaningless for me: Fault Message: No valid host was found. There are not enough hosts available. compute-0: (RetryFilter) Previously tried: [[u'compute-1', u'compute-1'], [u'compute-0', u'compute-0']], compute-1: (RetryFilter) Previously tried: [[u'compute-1', u'compute-1'], [u'compute-0 Code: 501 Details: compute-0: (RetryFilter) Previously tried: [[u'compute-1', u'compute-1'], [u'compute-0', u'compute-0']], compute-1: (RetryFilter) Previously tried: [[u'compute-1', u'compute-1'], [u'compute-0', u'compute-0']] Created: Nov. 13, 2018, 11:49 a.m. ================================================ Alarm UUID: 15f5bc85-de93-4109-a278-425bafc7c997 Alarm ID: 700.001 Severity: critical Alarm State: set Alarm Type: processing-error Timestamp: Nov. 13, 2018, 11:49 a.m. Suppression: Entity Instance ID: tenant=571bfa02-4736-4359-a15d-871224b3b202.instance=3ef09380-47e6-479a-91cc-6813474a183d Entity Type ID: tenant.instance Probable Cause: underlying-resource-unavailable Proposed Repair Action: Manual intervention required Service Affecting: True Management Affecting: True Reason: Instance foobar123 owned by admin has failed to schedule Interesting is, half of the instance is missing: @see: https://imgur.com/a/UVmEZhF - missing NIC - missing IP Addresses - missing Security Groups - missing Volumes Attached does anyone still have a tip for me? Volker -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Thu Nov 15 15:19:11 2018 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Thu, 15 Nov 2018 15:19:11 +0000 Subject: [Starlingx-discuss] instance load-balancing In-Reply-To: <3a32af01c5lggc8u@shdsegapp1> References: <3a32af01c5lggc8u@shdsegapp1> Message-ID: Ok, i think based on public doku, this will work: https://docs.openstack.org/mitaka/networking-guide/config-lbaas.html I just missing an GUI in horizon. If Octavia available, maybe we can add the given interface in horizon ;) Greez & thx, Volker... Von: von Hoesslin, Volker [mailto:Volker.Hoesslin at swsn.de] Gesendet: Donnerstag, 15. November 2018 14:39 An: 'starlingx-discuss at lists.starlingx.io' Betreff: [Starlingx-discuss] instance load-balancing Hi there! How or does starlingX support load-balancing out of the box? and next question, what about auto-scaling? Greez & thx, Volker... -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Fri Nov 16 01:35:54 2018 From: yong.hu at intel.com (Hu, Yong) Date: Fri, 16 Nov 2018 01:35:54 +0000 Subject: [Starlingx-discuss] Second controller on degraded for long time - Duplex Virtual In-Reply-To: References: <0A5D9A624DF90343892F8F3FE7DE525A2A8FC437@fmsmsx101.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35DBEAD3@SHSMSX104.ccr.corp.intel.com> <0A5D9A624DF90343892F8F3FE7DE525A2A8FC8D1@fmsmsx101.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35DBFFF8@SHSMSX104.ccr.corp.intel.com> <0A5D9A624DF90343892F8F3FE7DE525A2A8FDFB6@fmsmsx101.amr.corp.intel.com> Message-ID: Hi José, I checked the alarm you pasted and found it seemed normal that the data sync b/w 2 controllers was in progress - "data-syncing": Service group controller-services degraded; drbd-extension(enabled-standby, degraded, data-syncing), | | drbd-cinder(enabled-standby, degraded, data-syncing) *If you still have such an environment, you can check host status once again after such a long time (hours/days).* Moreover, 2 other comments: 1). you can use "drbd-overview" to check the sync percentage, whenever you see "degraded" state caused triggered by "data-syncing" alarm. As Stefan pointed out the sync might take very long time if the partition size is big and network speed is relatively slow. 2). The sync might fail eventually in the case that PV sizes on controller-0 and controller-1 is not the same (or roughly identically sized). In such a failure case, you can also see the details by "drbd-overview". Regards, Yong On 13/11/2018, 12:56 PM, "Hu, Yong" wrote: Hi José, I ever saw this kind of issue when I added a very big disk partition (like 900 GB) on controller node by "host-lvg-modify". And you might see some info meaningful by "fm alarm-list". In my case the message was about inconsistent in drbd-cinder. Regards, Yong On 12/11/2018, 9:29 PM, "Perez Carranza, Jose" wrote: Hi Cindy / Austin As I mentioned on my previous mail, I did not see the behavior mentioned on the bug, in my case the controller-1 becomes "Available" after the synchronization is finished and did not goes back again to "Degraded" mode. All my tests were done on an virtual environment. Regards, José > -----Original Message----- > From: Sun, Austin > Sent: Friday, November 9, 2018 7:10 PM > To: Xie, Cindy ; Perez Carranza, Jose > ; Dinescu, Stefan > ; 'starlingx-discuss at lists.starlingx.io' > > Subject: RE: [Starlingx-discuss] Second controller on degraded for long time - > Duplex Virtual > > Hi Cindy: > Mhg raised bug#1798836 and I worked with him. I cannot reproduce this > issue. bug#1798836 is using static IPv4 , not dynamic . > Mhg's setup has been changed to do other test. > @Jose: could you raise bug and attach logs ( /var/log/*) in controller- > 0/controller-1 ? > > Thanks. > BR > Austin Sun. > > > > -----Original Message----- > From: Xie, Cindy > Sent: Saturday, November 10, 2018 8:12 AM > To: Perez Carranza, Jose ; Sun, Austin > ; Dinescu, Stefan ; > 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] Second controller on degraded for long time - > Duplex Virtual > > So Jose, you think the issue you encountered is the same issue as > bug#1798836, my understanding correct? > > @Austin who is working on this bug may contact you for more details > including log files. > > Thx. - cindy > > -----Original Message----- > From: Perez Carranza, Jose > Sent: Saturday, November 10, 2018 1:37 AM > To: Xie, Cindy ; Dinescu, Stefan > ; 'starlingx-discuss at lists.starlingx.io' > > Subject: RE: [Starlingx-discuss] Second controller on degraded for long time - > Duplex Virtual > > Hi Cindy > > Actually I did not fill a Launchpad, I just sent the question to the mailing list, > in my case controller-1 gets available after sync (~1 hour) but I did not > noticed that after that a controller goes back to degraded mode again. > > Regards, > José > > > > -----Original Message----- > > From: Xie, Cindy > > Sent: Thursday, November 8, 2018 5:16 PM > > To: Dinescu, Stefan ; Perez Carranza, > > Jose ; 'starlingx-discuss at lists.starlingx.io' > > > > Subject: RE: [Starlingx-discuss] Second controller on degraded for > > long time - Duplex Virtual > > > > Jose, > > Can you check if you reported issue is similar as the existing one > > reported > > here: > > > > https://bugs.launchpad.net/starlingx/+bug/1798836 > > > > thx. - cindy > > > > -----Original Message----- > > From: Dinescu, Stefan [mailto:Stefan.Dinescu at windriver.com] > > Sent: Thursday, November 8, 2018 11:01 PM > > To: Perez Carranza, Jose ; 'starlingx- > > discuss at lists.starlingx.io' > > Subject: Re: [Starlingx-discuss] Second controller on degraded for > > long time - Duplex Virtual > > > > Hello, > > > > Depending on the size of your cinder partition and network speed > > between the two controller nodes, cinder make take some time to sync > > as it is usually the biggest partition. > > > > you can use "drbd-overview" to see the progress of the sync. > > > > Thanks, > > Stefan > > ________________________________________ > > From: Perez Carranza, Jose [jose.perez.carranza at intel.com] > > Sent: Thursday, November 08, 2018 4:56 PM > > To: 'starlingx-discuss at lists.starlingx.io' > > Subject: [Starlingx-discuss] Second controller on degraded for long > > time - Duplex Virtual > > > > Hi > > > > I setup a Duplex virtual environment and I noticed that after > > installation and provisioning of second controller (controller-1) this > > one stays in Degraded for long time (~ 1 hour), and alarm 400.001 is > > being displayed [1], Is this normal behavior? Is here a way to take > > out the controller-1 from 'degraded' to 'available' faster? > > > > 1- http://paste.openstack.org/show/734425/ > > > > > > Regards, > > José > > > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ovidiu.Poncea at windriver.com Fri Nov 16 08:57:00 2018 From: Ovidiu.Poncea at windriver.com (Poncea, Ovidiu) Date: Fri, 16 Nov 2018 08:57:00 +0000 Subject: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching In-Reply-To: References: <2588653EBDFFA34B982FAF00F1B4844EBB25D46B@ALA-MBD.corp.ad.wrs.com> , Message-ID: <4C60D9C5C8176C47874FFF36647AA19E9D5F8E8F@ALA-MBD.corp.ad.wrs.com> Hi Li, Quick question: Is cache going to be freed when an image is deleted from glance? It would be a waste to cache images that are no longer needed. Thanks, Ovidiu ________________________________ From: Li, Xiaoyan [xiaoyan.li at intel.com] Sent: Tuesday, November 13, 2018 9:19 AM To: Rowsell, Brent; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi, About the raw cache function in StarlingX Cinder and Glance, I would like to remove it as Cinder has similar function. Please see following detail. And if I would like to remove the function in StarlingX, there are two methods: 1. Submit a patch to revert the changes in Glance and Cinder. 2. Ignore these patches during upgrading StarlingX/Cinder to new Cinder release. Which way do we prefer to? Best wishes Lisa From: Li, Xiaoyan Sent: Thursday, September 20, 2018 10:17 AM To: Rowsell, Brent ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi, Brent The following are mechanism of Cinder volume cache. Creation of cached volume: It creates a cached volume in the backend storage when creating from an image. 1. Create_from_image: https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L890 2. Return image cache entry: If not existed, it creates a new entry. https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L746 3. Create a new image-volume and cache entry for it: https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L872 Use a cached volume when creating a volume: https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L723-L735 Delete the cache volume: When capacity and number of cache entries exceed specified limit, it deletes cache entries (cached volumes). https://github.com/openstack/cinder/blob/stable/pike/cinder/image/cache.py#L164 Best wishes Lisa From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Thursday, September 6, 2018 10:02 AM To: Li, Xiaoyan >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching We would need to review this feature to ensure it provides equivalent functionality first. If it does, great, we can look at reverting and enabling this cinder functionality. Brent From: Li, Xiaoyan [mailto:xiaoyan.li at intel.com] Sent: Wednesday, September 5, 2018 9:59 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi all, This email is about Raw caching function in StarlingX. This feature is to cache an image in backend storage like Ceph when we first create a volume in this backend storage. In fact, Cinder upstream has already had a similar function in Pike release. https://specs.openstack.org/openstack/cinder-specs/specs/liberty/image-volume-cache.html So I want to revert Raw caching function in StarlingX, and use Cinder generic image cache instead. The problem is that we need to update Cinder config in StarlingX. Any comments? Best wishes Lisa -------------- next part -------------- An HTML attachment was scrubbed... URL: From luis.ramirez at opencloud.es Fri Nov 16 09:23:48 2018 From: luis.ramirez at opencloud.es (Luis Ramirez) Date: Fri, 16 Nov 2018 10:23:48 +0100 Subject: [Starlingx-discuss] Deployment from ISO Message-ID: Hi all, Which should be the min hw conf. to deploy one single controller? Could i do into a VM? Br, Luis Rmz Blockchain, DevOps & Open Source Cloud Solutions Architect ---------------------------------------- Founder & CEO OpenCloud.es luis.ramirez at opencloud.es Skype ID: d.overload Freenode IRC: lramrez/overbit Hangouts: luis.ramirez at opencloud.es [image: ] +34 682 740 973 / [image: ]+39 392 1289553 / [image: ]+49 152 26917722 / Česká republika: +420 774 274 882 ----------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Fri Nov 16 09:31:08 2018 From: austin.sun at intel.com (Sun, Austin) Date: Fri, 16 Nov 2018 09:31:08 +0000 Subject: [Starlingx-discuss] Deployment from ISO In-Reply-To: References: Message-ID: Hi Luis: You can check https://docs.starlingx.io/installation_guide/index.html , which describe the HW request needed . Yes, you can deploy into VM ? There is guide In the link shared. And you can find iso http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/outputs/iso/ Thanks. BR Austin Sun. From: Luis Ramirez [mailto:luis.ramirez at opencloud.es] Sent: Friday, November 16, 2018 5:24 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Deployment from ISO Hi all, Which should be the min hw conf. to deploy one single controller? Could i do into a VM? Br, Luis Rmz Blockchain, DevOps & Open Source Cloud Solutions Architect ---------------------------------------- Founder & CEO OpenCloud.es luis.ramirez at opencloud.es Skype ID: d.overload Freenode IRC: lramrez/overbit Hangouts: luis.ramirez at opencloud.es [] +34 682 740 973 / [] +39 392 1289553 / [] +49 152 26917722 / Česká republika: +420 774 274 882 ----------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From luis.ramirez at opencloud.es Fri Nov 16 09:35:55 2018 From: luis.ramirez at opencloud.es (Luis Ramirez) Date: Fri, 16 Nov 2018 10:35:55 +0100 Subject: [Starlingx-discuss] Deployment from ISO In-Reply-To: References: Message-ID: Thanks, I'll check it out. El El vie, 16 nov 2018 a las 10:31, Sun, Austin escribió: > Hi Luis: > > You can check https://docs.starlingx.io/installation_guide/index.html , > which describe the HW request needed . Yes, you can deploy into VM ? > > There is guide In the link shared. And you can find iso > http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/outputs/iso/ > > > > Thanks. > BR > Austin Sun. > > > > *From:* Luis Ramirez [mailto:luis.ramirez at opencloud.es] > *Sent:* Friday, November 16, 2018 5:24 PM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] Deployment from ISO > > > > Hi all, > > > > Which should be the min hw conf. to deploy one single controller? Could i > do into a VM? > > > > Br, > > Luis Rmz > > Blockchain, DevOps & Open Source Cloud Solutions Architect > > ---------------------------------------- > > Founder & CEO > > OpenCloud.es > > luis.ramirez at opencloud.es > > Skype ID: d.overload > > Freenode IRC: lramrez/overbit > > Hangouts: luis.ramirez at opencloud.es > > [image: ] +34 682 740 973 / [image: ]+39 392 1289553 / [image: ]+49 > 152 26917722 / Česká republika: +420 774 274 882 > > ----------------------------------------------------- > -- Br, Luis Rmz Blockchain, DevOps & Open Source Cloud Solutions Architect ---------------------------------------- Founder & CEO OpenCloud.es luis.ramirez at opencloud.es Skype ID: d.overload Hangouts: luis.ramirez at opencloud.es [image: ] +34 682 740 973 / [image: ]+39 392 1289553 / [image: ]+49 152 26917722 / Česká republika: +420 774 274 882 ----------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From sajuptpm at gmail.com Fri Nov 16 09:51:41 2018 From: sajuptpm at gmail.com (Saju M) Date: Fri, 16 Nov 2018 15:21:41 +0530 Subject: [Starlingx-discuss] ISO build Failing : Command "build-pkgs", How to rebuild failed packages Message-ID: Hi, I am following the link https://docs.starlingx.io/developer_guide/index.html#build-packages When I run "build-pkgs" and it returns list of "*Failed to build packages: ", *I have attached the name of failed packages *.* I could not find http://127.0.0.1:8088/localdisk/loadbuild/starlingx/starlingx/installer/rpmbuild/RPMS/repodata/repomd.xml in my setup. *I am getting 2 types of build errors. * *============ Build Error Type - 1 ===========* 20:49:00 Finish: Outputting list of installed packages 20:49:00 ERROR: Exception(/localdisk/loadbuild/starlingx/starlingx/std/rpmbuild/SRPMS/lldpd-0.9.0-0.tis.4.src.rpm) Config(starlingx-starlingx-tis-r5-pike-std/mock) 0 minutes 5 seconds 20:49:00 INFO: Results and/or logs in: /localdisk/loadbuild/starlingx/starlingx/std/results/starlingx-starlingx-tis-r5-pike-std/lldpd-0.9.0-0.tis.4 *20:49:00 ERROR: Command failed: 20:49:00 # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/lldpd.spec* 20:49:00 20:49:00 End build: /localdisk/loadbuild/starlingx/starlingx/std/rpmbuild/SRPMS/lldpd-0.9.0-0.tis.4.src.rpm 20:49:00 Error building lldpd-0.9.0-0.tis.4.src.rpm. *============ Build Error Type - 2 ===========* 20:41:07 Start: build setup for libvirt-python-4.7.0-1.tis.3.src.rpm 20:41:07 ERROR: Exception(/localdisk/loadbuild/starlingx/starlingx/std/rpmbuild/SRPMS/libvirt-python-4.7.0-1.tis.3.src.rpm) Config(starlingx-starlingx-tis-r5-pike-std/mock) 0 minutes 4 seconds 20:41:07 INFO: Results and/or logs in: /localdisk/loadbuild/starlingx/starlingx/std/results/starlingx-starlingx-tis-r5-pike-std/libvirt-python-4.7.0-1.tis.3 *20:41:07 ERROR: Command failed: 20:41:07 # /usr/bin/yum-builddep --installroot /localdisk/loadbuild/starlingx/starlingx/std/mock/root/ --releasever 7 /localdisk/loadbuild/starlingx/starlingx/std/mock/root//builddir/build/SRPMS/libvirt-python-4.7.0-1.tis.3.src.rpm* 20:41:07 Failed to set locale, defaulting to C *20:41:07 http://127.0.0.1:8088/localdisk/loadbuild/starlingx/starlingx/installer/rpmbuild/RPMS/repodata/repomd.xml : [Errno 14] HTTP Error 404 - Not Found* 20:41:07 Trying other mirror. *============= Failed Packages ======================* *20:33:10 Failed to build packages: vm-topology-1.0-1.tis.src.rpm swtpm-0.1.0-2.tis.0.src.rpm qemu-kvm-ev-2.10.0-0.tis.0.src.rpm python-networking-sfc-5.0.0-1.tis.2.src.rpm python-networking-bgpvpn-7.0.0-0.tis.3.src.rpm pxe-network-installer-1.0-27.tis.src.rpm platform-kickstarts-1.0.0-2.tis.src.rpm openvswitch-2.9.0-3.el7.tis.1.src.rpm openstack-neutron-11.0.0-1.tis.9.src.rpm lldpd-0.9.0-0.tis.4.src.rpm libvirt-python-4.7.0-1.tis.3.src.rpm libvirt-4.7.0-1.tis.23.src.rpm libtpms-0.6.0-2.tis.0.src.rpm libfdt-1.4.4-0.tis.1.src.rpm ldapscripts-2.0.8-0.tis.2.src.rpm ixgbevf-kmod-4.3.5-0.tis.2.src.rpm ixgbe-kmod-5.3.7-0.tis.1.src.rpm i40evf-kmod-3.5.13-0.tis.1.src.rpm i40e-kmod-2.4.10-0.tis.1.src.rpm e1000e-kmod-3.4.1.1-0.tis.1.src.rpm drbd-kernel-8.4.7-1.tis.4.src.rpm drbd-8.4.3-0.tis.6.src.rpm dpkg-1.18.24-0.tis.1.src.rpm cgcs-users-1.0-0.tis.2.src.rpm * -------------- next part -------------- An HTML attachment was scrubbed... URL: From changcheng.liu at intel.com Fri Nov 16 12:30:56 2018 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Fri, 16 Nov 2018 12:30:56 +0000 Subject: [Starlingx-discuss] setup stx build environment Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50EF7133@SHSMSX104.ccr.corp.intel.com> Hi all, I have one question about setting up stx build environment. Why not move lots of many basic program installation process from mirror-check.sh to Dockerfile directly? Then stx community could supply one basic docker image as the base image to let developer customize it. Currently, I still need install lots of program after building Dockerfile into image. B.R. Changcheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Fri Nov 16 15:45:07 2018 From: scott.little at windriver.com (Scott Little) Date: Fri, 16 Nov 2018 10:45:07 -0500 Subject: [Starlingx-discuss] [build] StarlingX ISO file now available at our Cengn mirror In-Reply-To: <1a3ebbad-e2bd-bcc3-25be-5f3bf56ec7f9@windriver.com> References: <0B566C62EC792145B40E29EFEBF1AB47105628DE@fmsmsx104.amr.corp.intel.com> <1D109C16-047F-46C4-BC58-A541352679D9@intel.com> <1a3ebbad-e2bd-bcc3-25be-5f3bf56ec7f9@windriver.com> Message-ID: The spec should be posted soon.  Until then... Proposed directory structure: http://mirror.starlingx.cengn.ca/mirror/starlingx/ = ///outputs/          ///inputs/ = 'centos'            'ubuntu'            'clear_linux' = 'master'             = 2018.10 # dropping the 'r/' prefix                    ... = $(date +%Y%m%dT%H%M%SZ)   # time stamp of start of 'repo sync'                   # a symlink to the last successful build date = RPMS/                         SRPMS/                         downloads/ = RPMS//                          SRPMS//                          iso/                          installer/                          CONTEXT                                                                            logs/ = std                 rt                 installer                 container                 ... = TBD = 'success' | 'fail' RPMS and SRPMS subdirectories will include repodata. Scott On 18-11-14 09:57 AM, Scott Little wrote: > Yes, that will be coming soon. > > Scott > > > On 18-11-13 07:44 PM, Hu, Yong wrote: >> >> Hi Cesar, >> >> Thank you for sharing this great progress. With this, it’s more >> convenient for us to share ISO with customers who want to have a >> quick try. >> >> In addition, I would like to know whether or not Cengn has plan to >> share the **build mirrors** (RPMs, SRPMs, and other downloading >> packages) with community. >> >> If so, how soon will it be ready? >> >> Regards, >> >> Yong >> >> *From: *"Lara, Cesar" >> *Date: *Wednesday, 14 November 2018 at 5:15 AM >> *To: *"starlingx-discuss at lists.starlingx.io" >> >> *Subject: *[Starlingx-discuss] [build] StarlingX ISO file now >> available at our Cengn mirror >> >> Hello community >> >> We have an ISO file available at our Cengn mirror so people who wants >> to start playing with the StarlingX project can do so. I want to give >> out special thanks to Scott Little and Jason McKenna for making this >> happen in such timely manner. >> >> The image is hosted at >> >> http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/outputs/iso/ >> >> For more information about the mirror and other build and news from >> the build team please check our wiki. >> >> https://wiki.openstack.org/wiki/StarlingX/Build >> >> Regards >> >> *//* >> >> */Cesar Lara/* >> >> Software Engineering Manager >> >> OpenSource Technology Center >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.friesen at windriver.com Fri Nov 16 15:49:58 2018 From: chris.friesen at windriver.com (Chris Friesen) Date: Fri, 16 Nov 2018 09:49:58 -0600 Subject: [Starlingx-discuss] Support IBRS cpu model. In-Reply-To: References: Message-ID: There's a problem with this patch. The way the VCpuModelFilter is designed, the basic idea is that a host with a CPU model "later" in the list can support guests with all CPU models "earlier" in the list. According to [1] the "spec-ctrl" and "ssbd" CPU features require host CPU microcode (i.e. that the host is detected as the "-IBRS" model) before it can be used for guest CPUs. This means that a "Skylake-Server" host cannot support a "Broadwell-IBRS" guest, which violates the design of the VCpuModelFilter. I think as part of adding the -IBRS models we'll have to also modify the filter itself. Chris [1] https://www.berrange.com/posts/2018/06/29/cpu-model-configuration-for-qemu-kvm-on-x86-hosts/ On 11/13/2018 11:54 PM, Sun, Austin wrote: > Hi All: > if install StarlingX in compute-node with cpu type 'Skylake-Server-IBRS' , it cannot use 'passthrough' type with keyword hw:cpu_model in favor to create instance > It will prompt "No valid host was found. There are not enough hosts available. computer-0: (VCpuModelFilter) Host VCPU model Skylake-Server-IBRS required Passthrough Code 501" > After investigation , Libvirt 4.7.0 supports *IBRS (for example IvyBridge-IBRS, Skylake-Server-IBRS) CPU model , but nova and meta favor does not support *IBRS CPU model yet. > > I have made patch for nova[0] and glance[1]. > Nova[0] will support *-IBRS type vcpu when select passthrough > Glance[1] will add metadata to support *-IBRS in hw:cpu_model > > Please review these PRs. > > Thanks. > BR > Austin Sun. > > [0] https://github.com/starlingx-staging/stx-nova/pull/15 > [1] https://github.com/starlingx-staging/stx-glance/pull/4 > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From dtroyer at gmail.com Fri Nov 16 17:06:02 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Fri, 16 Nov 2018 11:06:02 -0600 Subject: [Starlingx-discuss] [build] StarlingX ISO file now available at our Cengn mirror In-Reply-To: References: <0B566C62EC792145B40E29EFEBF1AB47105628DE@fmsmsx104.amr.corp.intel.com> <1D109C16-047F-46C4-BC58-A541352679D9@intel.com> <1a3ebbad-e2bd-bcc3-25be-5f3bf56ec7f9@windriver.com> Message-ID: On Fri, Nov 16, 2018 at 9:47 AM Scott Little wrote: > The spec should be posted soon. Until then... > Proposed directory structure:> > http://mirror.starlingx.cengn.ca/mirror/starlingx/ > > = ///outputs/ > ///inputs/ My instinct is to do / because I tend to think in sorting by time more than type...but /me shrugs... > = 'centos' > 'ubuntu' > 'clear_linux' The value for Clear Linux should match however the clear community self-identifies... Victor? /me does research In DevStack we are using 'clearlinux' while Clear's os-release file uses 'clear-linux-os'. I don't recall why those are different. > = 'master' > > > = 2018.10 # dropping the 'r/' prefix This maybe should be instead, the tags do not have prefixes, but do have a 'z' component: the actual release is 2018.10.0 and 2018.10.1 would be the next bug-fix release of r/2018.10 if we were to do one, that might be a useful distinction in the future. dt -- Dean Troyer dtroyer at gmail.com From scott.little at windriver.com Fri Nov 16 21:24:27 2018 From: scott.little at windriver.com (Scott Little) Date: Fri, 16 Nov 2018 16:24:27 -0500 Subject: [Starlingx-discuss] [build] StarlingX ISO file now available at our Cengn mirror In-Reply-To: References: <0B566C62EC792145B40E29EFEBF1AB47105628DE@fmsmsx104.amr.corp.intel.com> <1D109C16-047F-46C4-BC58-A541352679D9@intel.com> <1a3ebbad-e2bd-bcc3-25be-5f3bf56ec7f9@windriver.com> Message-ID: <2bd619ce-79f3-abac-e61e-fa6e16d11524@windriver.com> Thanks for the input. The spec has been posted.... https://review.openstack.org/#/c/618587/1/specs/2019.03/approved/mirror_2003906_published_builds.rst Scott On 18-11-16 12:06 PM, Dean Troyer wrote: > On Fri, Nov 16, 2018 at 9:47 AM Scott Little wrote: >> The spec should be posted soon. Until then... >> Proposed directory structure:> >> http://mirror.starlingx.cengn.ca/mirror/starlingx/ >> >> = ///outputs/ >> ///inputs/ > My instinct is to do / because I tend to think in > sorting by time more than type...but /me shrugs... > >> = 'centos' >> 'ubuntu' >> 'clear_linux' > The value for Clear Linux should match however the clear community > self-identifies... Victor? > > /me does research > > In DevStack we are using 'clearlinux' while Clear's os-release file > uses 'clear-linux-os'. I don't recall why those are different. > >> = 'master' >> >> >> = 2018.10 # dropping the 'r/' prefix > This maybe should be instead, the tags do not have > prefixes, but do have a 'z' component: the actual release is 2018.10.0 > and 2018.10.1 would be the next bug-fix release of r/2018.10 if we > were to do one, that might be a useful distinction in the future. > > dt > From austin.sun at intel.com Sat Nov 17 02:59:21 2018 From: austin.sun at intel.com (Sun, Austin) Date: Sat, 17 Nov 2018 02:59:21 +0000 Subject: [Starlingx-discuss] Support IBRS cpu model. In-Reply-To: References: Message-ID: Hi Chris: Thanks your review. I have made new patch [1] based on your suggestion. Could you help review it again ? https://github.com/austinsun/stx-nova/commit/3255facb16b70b138ff12243822b43d1824f6890#diff-6955c78b8a0da8ec1cbf33c3834de1e0 Thanks. BR Austin Sun. -----Original Message----- From: Chris Friesen [mailto:chris.friesen at windriver.com] Sent: Friday, November 16, 2018 11:50 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Support IBRS cpu model. There's a problem with this patch. The way the VCpuModelFilter is designed, the basic idea is that a host with a CPU model "later" in the list can support guests with all CPU models "earlier" in the list. According to [1] the "spec-ctrl" and "ssbd" CPU features require host CPU microcode (i.e. that the host is detected as the "-IBRS" model) before it can be used for guest CPUs. This means that a "Skylake-Server" host cannot support a "Broadwell-IBRS" guest, which violates the design of the VCpuModelFilter. I think as part of adding the -IBRS models we'll have to also modify the filter itself. Chris [1] https://www.berrange.com/posts/2018/06/29/cpu-model-configuration-for-qemu-kvm-on-x86-hosts/ On 11/13/2018 11:54 PM, Sun, Austin wrote: > Hi All: > if install StarlingX in compute-node with cpu type 'Skylake-Server-IBRS' , it cannot use 'passthrough' type with keyword hw:cpu_model in favor to create instance > It will prompt "No valid host was found. There are not enough hosts available. computer-0: (VCpuModelFilter) Host VCPU model Skylake-Server-IBRS required Passthrough Code 501" > After investigation , Libvirt 4.7.0 supports *IBRS (for example IvyBridge-IBRS, Skylake-Server-IBRS) CPU model , but nova and meta favor does not support *IBRS CPU model yet. > > I have made patch for nova[0] and glance[1]. > Nova[0] will support *-IBRS type vcpu when select passthrough > Glance[1] will add metadata to support *-IBRS in hw:cpu_model > > Please review these PRs. > > Thanks. > BR > Austin Sun. > > [0] https://github.com/starlingx-staging/stx-nova/pull/15 > [1] https://github.com/starlingx-staging/stx-glance/pull/4 > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From vm.rod25 at gmail.com Sun Nov 18 19:46:04 2018 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Sun, 18 Nov 2018 13:46:04 -0600 Subject: [Starlingx-discuss] [build] StarlingX ISO file now available at our Cengn mirror In-Reply-To: References: <0B566C62EC792145B40E29EFEBF1AB47105628DE@fmsmsx104.amr.corp.intel.com> <1D109C16-047F-46C4-BC58-A541352679D9@intel.com> <1a3ebbad-e2bd-bcc3-25be-5f3bf56ec7f9@windriver.com> Message-ID: On Fri, Nov 16, 2018 at 11:06 AM Dean Troyer wrote: > > On Fri, Nov 16, 2018 at 9:47 AM Scott Little wrote: > > The spec should be posted soon. Until then... > > Proposed directory structure:> > > http://mirror.starlingx.cengn.ca/mirror/starlingx/ > > > > = ///outputs/ > > ///inputs/ > > My instinct is to do / because I tend to think in > sorting by time more than type...but /me shrugs... > +1 on this , is better in my opinion / for sorting and debuging in the future > > = 'centos' > > 'ubuntu' > > 'clear_linux' > > The value for Clear Linux should match however the clear community > self-identifies... Victor? as clear linux developer and user I love the idea of having clear linxu losted here , we are working on the enblment of STX with clearlinux > > /me does research > > In DevStack we are using 'clearlinux' while Clear's os-release file > uses 'clear-linux-os'. I don't recall why those are different. > We use the os-release file from systemd , for example : $ cat /lib/os-release NAME="Clear Linux OS" VERSION=1 ID=clear-linux-os ID_LIKE=clear-linux-os VERSION_ID=26260 PRETTY_NAME="Clear Linux OS" ANSI_COLOR="1;35" HOME_URL="https://clearlinux.org" SUPPORT_URL="https://clearlinux.org" BUG_REPORT_URL="mailto:dev at lists.clearlinux.org" PRIVACY_POLICY_URL="http://www.intel.com/privacy" Whatever standard you prefer is fine > > = 'master' > > > > > > = 2018.10 # dropping the 'r/' prefix > > This maybe should be instead, the tags do not have > prefixes, but do have a 'z' component: the actual release is 2018.10.0 > and 2018.10.1 would be the next bug-fix release of r/2018.10 if we > were to do one, that might be a useful distinction in the future. > > dt > Regards > -- > > Dean Troyer > dtroyer at gmail.com > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From yong.hu at intel.com Mon Nov 19 01:03:47 2018 From: yong.hu at intel.com (Hu, Yong) Date: Mon, 19 Nov 2018 01:03:47 +0000 Subject: [Starlingx-discuss] ISO build Failing : Command "build-pkgs", How to rebuild failed packages In-Reply-To: References: Message-ID: <083189A1-EFF1-4ACC-8114-F96F96C566E6@intel.com> Hi Saju, In order to drill down the cause of build-pkgs failure, clarifying a few things would let us help you further: 1. First of all, have you *successfully* gone through the mirror setup procedures, and assured no packages were missing of downloading? Indeed, the mirror setup is nontrivial and likely something might go wrong caused by network connectivity, timeout or even upstream repo unavailability. One way to check mirror completeness is to confirm all packages listed in “~/stx-tools/centos-mirror-tools/*.lst” are there after running downloading scripts. Another way is to check if any packages are listed in *missing*.txt files (which means something wrong when downloading related packages). 2. Regarding the build log, it would be helpful if you can attach the build log (such as: /localdisk/loadbuild/yourname/starlingx/build-std.log). With this, we can see the wholistic log and capture some clues. BTW: you can search your log file, to see whether there are any pieces of “Success building” info with any rpm pkgs. If so, it is a good sign that at least your local repo “cgcs-centos-repo” was correctly made and parts of RPMs were built out already. 3. Back to your build failure, you can actually enter into “/localdisk/loadbuild/starlingx/starlingx/std/results/starlingx-starlingx-tis-r5-pike-std/libvirt-python-4.7.0-1.tis.3/” and there are many build logs in next level details. And “build.log” and “root.log” should the most important 2 files you like to look into what’s happening inside. 4. Last but not least, about the question “how to rebuild failed packages”. The answer is you couldn’t or don’t have to. If the build-pkgs ended up with failures, rebuilding won’t work, until you fix the issues caused the build failures. In another word, *IF* build setup was done correctly in advance, the build would *iterate* for more than rounds automatically, and eventually ALL the packages should be built out. Hope this kind of info give you a structural way to narrow down the build issues you are facing. Regards, Yong From: Saju M Date: Friday, 16 November 2018 at 5:52 PM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] ISO build Failing : Command "build-pkgs", How to rebuild failed packages Hi, I am following the link https://docs.starlingx.io/developer_guide/index.html#build-packages When I run "build-pkgs" and it returns list of "Failed to build packages: ", I have attached the name of failed packages. I could not find http://127.0.0.1:8088/localdisk/loadbuild/starlingx/starlingx/installer/rpmbuild/RPMS/repodata/repomd.xml in my setup. I am getting 2 types of build errors. ============ Build Error Type - 1 =========== 20:49:00 Finish: Outputting list of installed packages 20:49:00 ERROR: Exception(/localdisk/loadbuild/starlingx/starlingx/std/rpmbuild/SRPMS/lldpd-0.9.0-0.tis.4.src.rpm) Config(starlingx-starlingx-tis-r5-pike-std/mock) 0 minutes 5 seconds 20:49:00 INFO: Results and/or logs in: /localdisk/loadbuild/starlingx/starlingx/std/results/starlingx-starlingx-tis-r5-pike-std/lldpd-0.9.0-0.tis.4 20:49:00 ERROR: Command failed: 20:49:00 # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/lldpd.spec 20:49:00 20:49:00 End build: /localdisk/loadbuild/starlingx/starlingx/std/rpmbuild/SRPMS/lldpd-0.9.0-0.tis.4.src.rpm 20:49:00 Error building lldpd-0.9.0-0.tis.4.src.rpm. ============ Build Error Type - 2 =========== 20:41:07 Start: build setup for libvirt-python-4.7.0-1.tis.3.src.rpm 20:41:07 ERROR: Exception(/localdisk/loadbuild/starlingx/starlingx/std/rpmbuild/SRPMS/libvirt-python-4.7.0-1.tis.3.src.rpm) Config(starlingx-starlingx-tis-r5-pike-std/mock) 0 minutes 4 seconds 20:41:07 INFO: Results and/or logs in: /localdisk/loadbuild/starlingx/starlingx/std/results/starlingx-starlingx-tis-r5-pike-std/libvirt-python-4.7.0-1.tis.3 20:41:07 ERROR: Command failed: 20:41:07 # /usr/bin/yum-builddep --installroot /localdisk/loadbuild/starlingx/starlingx/std/mock/root/ --releasever 7 /localdisk/loadbuild/starlingx/starlingx/std/mock/root//builddir/build/SRPMS/libvirt-python-4.7.0-1.tis.3.src.rpm 20:41:07 Failed to set locale, defaulting to C 20:41:07 http://127.0.0.1:8088/localdisk/loadbuild/starlingx/starlingx/installer/rpmbuild/RPMS/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found 20:41:07 Trying other mirror. ============= Failed Packages ====================== 20:33:10 Failed to build packages: vm-topology-1.0-1.tis.src.rpm swtpm-0.1.0-2.tis.0.src.rpm qemu-kvm-ev-2.10.0-0.tis.0.src.rpm python-networking-sfc-5.0.0-1.tis.2.src.rpm python-networking-bgpvpn-7.0.0-0.tis.3.src.rpm pxe-network-installer-1.0-27.tis.src.rpm platform-kickstarts-1.0.0-2.tis.src.rpm openvswitch-2.9.0-3.el7.tis.1.src.rpm openstack-neutron-11.0.0-1.tis.9.src.rpm lldpd-0.9.0-0.tis.4.src.rpm libvirt-python-4.7.0-1.tis.3.src.rpm libvirt-4.7.0-1.tis.23.src.rpm libtpms-0.6.0-2.tis.0.src.rpm libfdt-1.4.4-0.tis.1.src.rpm ldapscripts-2.0.8-0.tis.2.src.rpm ixgbevf-kmod-4.3.5-0.tis.2.src.rpm ixgbe-kmod-5.3.7-0.tis.1.src.rpm i40evf-kmod-3.5.13-0.tis.1.src.rpm i40e-kmod-2.4.10-0.tis.1.src.rpm e1000e-kmod-3.4.1.1-0.tis.1.src.rpm drbd-kernel-8.4.7-1.tis.4.src.rpm drbd-8.4.3-0.tis.6.src.rpm dpkg-1.18.24-0.tis.1.src.rpm cgcs-users-1.0-0.tis.2.src.rpm -------------- next part -------------- An HTML attachment was scrubbed... URL: From xiaoyan.li at intel.com Mon Nov 19 01:44:04 2018 From: xiaoyan.li at intel.com (Li, Xiaoyan) Date: Mon, 19 Nov 2018 01:44:04 +0000 Subject: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching In-Reply-To: <4C60D9C5C8176C47874FFF36647AA19E9D5F8E8F@ALA-MBD.corp.ad.wrs.com> References: <2588653EBDFFA34B982FAF00F1B4844EBB25D46B@ALA-MBD.corp.ad.wrs.com> , <4C60D9C5C8176C47874FFF36647AA19E9D5F8E8F@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Ovidiu, A cached image ( new volume from this image) is created on a storage backend when Cinder firstly creates a volume in the same backend storage from the image. All the information are stored in Cinder, including volume id, image id etc. https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/manager.py#L1368 https://github.com/openstack/cinder/blob/stable/pike/cinder/image/cache.py#L82 A cached image is deleted when the configure space for cache is used up. So currently Cinder doesn't delete the cached image volumes even if the image is deleted. But this can be an enhancement of current cinder image cache. https://github.com/openstack/cinder/blob/stable/pike/cinder/image/cache.py#L117 https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/manager.py#L1351 Best wishes Lisa From: Poncea, Ovidiu [mailto:Ovidiu.Poncea at windriver.com] Sent: Friday, November 16, 2018 4:57 PM To: Li, Xiaoyan ; Rowsell, Brent ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi Li, Quick question: Is cache going to be freed when an image is deleted from glance? It would be a waste to cache images that are no longer needed. Thanks, Ovidiu ________________________________ From: Li, Xiaoyan [xiaoyan.li at intel.com] Sent: Tuesday, November 13, 2018 9:19 AM To: Rowsell, Brent; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi, About the raw cache function in StarlingX Cinder and Glance, I would like to remove it as Cinder has similar function. Please see following detail. And if I would like to remove the function in StarlingX, there are two methods: 1. Submit a patch to revert the changes in Glance and Cinder. 2. Ignore these patches during upgrading StarlingX/Cinder to new Cinder release. Which way do we prefer to? Best wishes Lisa From: Li, Xiaoyan Sent: Thursday, September 20, 2018 10:17 AM To: Rowsell, Brent >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi, Brent The following are mechanism of Cinder volume cache. Creation of cached volume: It creates a cached volume in the backend storage when creating from an image. 1. Create_from_image: https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L890 2. Return image cache entry: If not existed, it creates a new entry. https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L746 3. Create a new image-volume and cache entry for it: https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L872 Use a cached volume when creating a volume: https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L723-L735 Delete the cache volume: When capacity and number of cache entries exceed specified limit, it deletes cache entries (cached volumes). https://github.com/openstack/cinder/blob/stable/pike/cinder/image/cache.py#L164 Best wishes Lisa From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Thursday, September 6, 2018 10:02 AM To: Li, Xiaoyan >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching We would need to review this feature to ensure it provides equivalent functionality first. If it does, great, we can look at reverting and enabling this cinder functionality. Brent From: Li, Xiaoyan [mailto:xiaoyan.li at intel.com] Sent: Wednesday, September 5, 2018 9:59 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi all, This email is about Raw caching function in StarlingX. This feature is to cache an image in backend storage like Ceph when we first create a volume in this backend storage. In fact, Cinder upstream has already had a similar function in Pike release. https://specs.openstack.org/openstack/cinder-specs/specs/liberty/image-volume-cache.html So I want to revert Raw caching function in StarlingX, and use Cinder generic image cache instead. The problem is that we need to update Cinder config in StarlingX. Any comments? Best wishes Lisa -------------- next part -------------- An HTML attachment was scrubbed... URL: From changcheng.liu at intel.com Mon Nov 19 01:45:24 2018 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Mon, 19 Nov 2018 01:45:24 +0000 Subject: [Starlingx-discuss] stx-tools: document isn't aligned with code Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50EF7D01@SHSMSX104.ccr.corp.intel.com> Hi all, I'm following below document to create-starlingx-packages. It's not aligned with latest code. https://docs.starlingx.io/developer_guide/index.html#create-starlingx-packages Could the man, who's responsible for continuous-integration, clean the document and make it more clear? 1. The stx-tools code isn't aligned with the above document since base-build/build target has been removed. commit 402961394e6cb0678629eadba25822dc82448528 Author: Mario Alfredo Carrillo Arevalo Date: Tue Oct 30 16:46:04 2018 -0600 Update Makefile Now the Makefile will be dedicated to build just one docker image, this commit updates the Makefile rules. 2. Besides this, README.rst is not updated in time when the build rule has been changed. B.R. Changcheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Rajesh.Jha at rsystems.com Mon Nov 19 06:50:50 2018 From: Rajesh.Jha at rsystems.com (Rajesh Jha) Date: Mon, 19 Nov 2018 06:50:50 +0000 Subject: [Starlingx-discuss] Duplex Mode standby controller not coming up Message-ID: Hi, On the latest iso from mirror http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/outputs/iso/ When I run the Duplex mode, the standby controller is not coming up. Its state is coming as inTest. Screen shot attached. Best Regards, Rajesh Jha The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, please immediately alert the sender by reply e-mail and then delete this message. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. R Systems has taken every reasonable precaution to minimize the risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: failed_standby_controller_duplex.png Type: image/png Size: 63345 bytes Desc: failed_standby_controller_duplex.png URL: From Don.Penney at windriver.com Mon Nov 19 14:37:54 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Mon, 19 Nov 2018 14:37:54 +0000 Subject: [Starlingx-discuss] Duplex Mode standby controller not coming up In-Reply-To: References: Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA3EBFF2@ALA-MBD.corp.ad.wrs.com> At a high level... Once the standby controller is installed and boots, it will run a set of tests, with a disabled/InTest state. Once the tests have completed successfully, the host will transition to Enabled/Degraded, while the DRBD filesystems sync (sudo drbd-overview). After the filesystems sync and everything is happy, the host will be Enabled/Available. Cheers, Don. From: Rajesh Jha [mailto:Rajesh.Jha at rsystems.com] Sent: Monday, November 19, 2018 1:51 AM To: starlingx-discuss at lists.starlingx.io Cc: Sumit Agarwal; Ajay Tomar Subject: [Starlingx-discuss] Duplex Mode standby controller not coming up Hi, On the latest iso from mirror http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/outputs/iso/ When I run the Duplex mode, the standby controller is not coming up. Its state is coming as inTest. Screen shot attached. Best Regards, Rajesh Jha The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, please immediately alert the sender by reply e-mail and then delete this message. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. R Systems has taken every reasonable precaution to minimize the risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Mon Nov 19 17:57:34 2018 From: Greg.Waines at windriver.com (Waines, Greg) Date: Mon, 19 Nov 2018 17:57:34 +0000 Subject: [Starlingx-discuss] [Ironic] deploy bare metal by Ironic Message-ID: Yes StarlingX does support Ironic. Some quick notes on its usage: * It is currently only supported on StarlingX Standard Configurations * i.e. NOT on All-In-One Simplex or Duplex * An additional interface, of network-type ‘control’, must be added to the two Controllers * These interfaces are connected to the ‘ironic provisioning tenant network’, * ... used for network-booting the ironic nodes * These interfaces are configured with an IP Address from the subnet of the ‘ironic provisioning network’, * Typically the ironic provisioning network is on a flat provider network ... but does not have to be * At least one compute node must also be attached to the ‘ironic provisioning network’ * The ironic service is optional in StarlingX Deployments * Before enabling it you must first set a number of ironic ‘service parameters’ i.e. * system service-parameter-add ironic neutron provisioning_network= * system service-parameter-add ironic pxe tftp_server= * NOTE: this is the floating IP of the Ironic Conductor / TFTP Server on the ironic provisioning network * system service-parameter-add ironic pxe netmask=24 * system service-parameter-add ironic pxe controller_0_if= * system service-parameter-add ironic pxe controller_1_if= * and then * system service-enable ironic ... after that, create ironic nodes and boot Baremetal Instances on those nodes as described in the Ironic Documentation. Greg. From: "Hu, Yong" Date: Tuesday, November 13, 2018 at 8:48 PM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] [Ironic] deploy bare metal by Ironic One customer asked how StarlingX supports bare metal support by Ironic. And they mentioned Titanium Cloud used to support it well. Anyone has the experience to deploy bare metal system by Ironic on StarlingX? Suggests and feedbacks are much appreciated! -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Mon Nov 19 23:34:38 2018 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 19 Nov 2018 15:34:38 -0800 Subject: [Starlingx-discuss] UID / GID adds and removes in setup package Message-ID: <260adee4-cc85-25ef-8732-12eaa8d80736@linux.intel.com> Hi Dariush, As I was reviewing the recent setup package refactor, I thought we need more background on why we add / remove uids and gids in the setup package vs for in an associated stx packages. I can understand some of the uids (add associated gids) are being removed such as mail, operator, games, ftp, lp. But the bin, daemon and adm users are also removed, and I think later we modify other packages because some of these users are missing. Is there any reason we can't keep these standard UIDs/GIDs? Sau! From yong.hu at intel.com Tue Nov 20 01:33:34 2018 From: yong.hu at intel.com (Hu, Yong) Date: Tue, 20 Nov 2018 01:33:34 +0000 Subject: [Starlingx-discuss] [Ironic] deploy bare metal by Ironic In-Reply-To: References: Message-ID: Thanks Greg for sharing the setup procedures! Well, I noticed “system host-if-modify” was changed, and we need a bit help here. In the past, it seemed to directly support a “-nt” (network type) input, with which “control” type can be specified. But currently “-nt” doesn’t exist anymore, and instead, another option “--networks ” is provided. It implies before running “system host-if-modify”, we need to use “system network-add” to create a network with a particular type: Type of network [REQUIRED] After looking through the code, I saw the network types are defined in “sysinv/sysinv/sysinv/sysinv/common/constants.py”: # Interface definitions NETWORK_TYPE_NONE = 'none' NETWORK_TYPE_INFRA = 'infra' NETWORK_TYPE_MGMT = 'mgmt' NETWORK_TYPE_OAM = 'oam' NETWORK_TYPE_BM = 'bm' NETWORK_TYPE_MULTICAST = 'multicast' NETWORK_TYPE_DATA = 'data' NETWORK_TYPE_SYSTEM_CONTROLLER = 'system-controller' NETWORK_TYPE_PCI_PASSTHROUGH = 'pci-passthrough' NETWORK_TYPE_PCI_SRIOV = 'pci-sriov' NETWORK_TYPE_PXEBOOT = 'pxeboot' PLATFORM_NETWORK_TYPES = [NETWORK_TYPE_PXEBOOT, NETWORK_TYPE_MGMT, NETWORK_TYPE_INFRA, NETWORK_TYPE_OAM] PCI_NETWORK_TYPES = [NETWORK_TYPE_PCI_PASSTHROUGH, NETWORK_TYPE_PCI_SRIOV] The at this point, my question is: for ironic network, *which network type should we set as the replacement of the previous “control” type??* ======================================================================= Hi @Teresa, according to git log, I noticed you handled following changes mostly. So, highly appreciate if you could provide some supports here. Thanks in advance! Regards, Yong From: "Waines, Greg" Date: Tuesday, 20 November 2018 at 1:58 AM To: "Hu, Yong" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [Ironic] deploy bare metal by Ironic Yes StarlingX does support Ironic. Some quick notes on its usage: * It is currently only supported on StarlingX Standard Configurations * i.e. NOT on All-In-One Simplex or Duplex * An additional interface, of network-type ‘control’, must be added to the two Controllers * These interfaces are connected to the ‘ironic provisioning tenant network’, * ... used for network-booting the ironic nodes * These interfaces are configured with an IP Address from the subnet of the ‘ironic provisioning network’, * Typically the ironic provisioning network is on a flat provider network ... but does not have to be * At least one compute node must also be attached to the ‘ironic provisioning network’ * The ironic service is optional in StarlingX Deployments * Before enabling it you must first set a number of ironic ‘service parameters’ i.e. * system service-parameter-add ironic neutron provisioning_network= * system service-parameter-add ironic pxe tftp_server= * NOTE: this is the floating IP of the Ironic Conductor / TFTP Server on the ironic provisioning network * system service-parameter-add ironic pxe netmask=24 * system service-parameter-add ironic pxe controller_0_if= * system service-parameter-add ironic pxe controller_1_if= * and then * system service-enable ironic ... after that, create ironic nodes and boot Baremetal Instances on those nodes as described in the Ironic Documentation. Greg. From: "Hu, Yong" Date: Tuesday, November 13, 2018 at 8:48 PM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] [Ironic] deploy bare metal by Ironic One customer asked how StarlingX supports bare metal support by Ironic. And they mentioned Titanium Cloud used to support it well. Anyone has the experience to deploy bare metal system by Ironic on StarlingX? Suggests and feedbacks are much appreciated! -------------- next part -------------- An HTML attachment was scrubbed... URL: From kailun.qin at intel.com Tue Nov 20 07:02:11 2018 From: kailun.qin at intel.com (Qin, Kailun) Date: Tue, 20 Nov 2018 07:02:11 +0000 Subject: [Starlingx-discuss] Questions about patch fd6cfc upstreaming Message-ID: Hi Matt, I'm working on the patch fd6cfc upstreaming, which tries to address the stale RPC message issue when DHCP agent restarting up. The patch was in good shape https://review.openstack.org/609463/ whereas the neutron community was questioning about the exact failure modes of this issue. The DHCP agent will have a full sync after the agent restarting up (https://github.com/openstack/neutron/blob/master/neutron/agent/dhcp/agent.py#L195), what kind of corner cases and negative behaviors could happen even w/ this full sync? Based on the commit message, I tried to reproduce this issue w/ the following steps: 1. schedule network1 to agent1. 2. turn down agent1 at almost the same time. 3. network1 is rescheduled to agent2 after finding that agent1 is dead. 4. turn up agent1, expecting stale RPC messages to be received by agent1 so that both agent1 and agent2 are servicing network1. However, I can only meet the described failure mode by sending another scheduling operation (network1->agent1) after step 2) is done. For the others, they seem to work as expected. Would you please kindly help provide more details about the failure pattern of this issue and/or the reproduction steps? Thanks a lot. BR, Kailun -------------- next part -------------- An HTML attachment was scrubbed... URL: From huifeng.le at intel.com Tue Nov 20 08:54:04 2018 From: huifeng.le at intel.com (Le, Huifeng) Date: Tue, 20 Nov 2018 08:54:04 +0000 Subject: [Starlingx-discuss] Questions about patch ab1baac upstreaming Message-ID: <76647BD697F40748B1FA4F56DA02AA0B4D53B851@SHSMSX104.ccr.corp.intel.com> Matt, I am looking at patch#ab1baac (US106501: Change to Titanium's handling Neutron Extensions) which targets to remove wrs-fields from the response to non-wrs client (e.g. no 'wrs-header' in the client request), suppose this is STX special feature and not need for upstream, could you please help to confirm? Thanks much! Best Regards, Le, Huifeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Peters at windriver.com Tue Nov 20 13:34:08 2018 From: Matt.Peters at windriver.com (Peters, Matt) Date: Tue, 20 Nov 2018 13:34:08 +0000 Subject: [Starlingx-discuss] [Ironic] deploy bare metal by Ironic In-Reply-To: References: Message-ID: <04212C96-1A30-43B5-85F9-219857D36A37@windriver.com> Hello Yong, You no longer require a network type in order to configure an IP address against an interface. Therefore you can setup the ironic provisioning network interface without assigning a specific network to the interface. Simply set the interface class to ‘platform’ and configure the required IP address. Hope that helps. Regards, Matt From: "Hu, Yong" Date: Monday, November 19, 2018 at 8:34 PM To: "Waines, Greg" , "Ho, Teresa" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [Ironic] deploy bare metal by Ironic Thanks Greg for sharing the setup procedures! Well, I noticed “system host-if-modify” was changed, and we need a bit help here. In the past, it seemed to directly support a “-nt” (network type) input, with which “control” type can be specified. But currently “-nt” doesn’t exist anymore, and instead, another option “--networks ” is provided. It implies before running “system host-if-modify”, we need to use “system network-add” to create a network with a particular type: Type of network [REQUIRED] After looking through the code, I saw the network types are defined in “sysinv/sysinv/sysinv/sysinv/common/constants.py”: # Interface definitions NETWORK_TYPE_NONE = 'none' NETWORK_TYPE_INFRA = 'infra' NETWORK_TYPE_MGMT = 'mgmt' NETWORK_TYPE_OAM = 'oam' NETWORK_TYPE_BM = 'bm' NETWORK_TYPE_MULTICAST = 'multicast' NETWORK_TYPE_DATA = 'data' NETWORK_TYPE_SYSTEM_CONTROLLER = 'system-controller' NETWORK_TYPE_PCI_PASSTHROUGH = 'pci-passthrough' NETWORK_TYPE_PCI_SRIOV = 'pci-sriov' NETWORK_TYPE_PXEBOOT = 'pxeboot' PLATFORM_NETWORK_TYPES = [NETWORK_TYPE_PXEBOOT, NETWORK_TYPE_MGMT, NETWORK_TYPE_INFRA, NETWORK_TYPE_OAM] PCI_NETWORK_TYPES = [NETWORK_TYPE_PCI_PASSTHROUGH, NETWORK_TYPE_PCI_SRIOV] The at this point, my question is: for ironic network, *which network type should we set as the replacement of the previous “control” type??* ======================================================================= Hi @Teresa, according to git log, I noticed you handled following changes mostly. So, highly appreciate if you could provide some supports here. Thanks in advance! Regards, Yong From: "Waines, Greg" Date: Tuesday, 20 November 2018 at 1:58 AM To: "Hu, Yong" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [Ironic] deploy bare metal by Ironic Yes StarlingX does support Ironic. Some quick notes on its usage: * It is currently only supported on StarlingX Standard Configurations * i.e. NOT on All-In-One Simplex or Duplex * An additional interface, of network-type ‘control’, must be added to the two Controllers * These interfaces are connected to the ‘ironic provisioning tenant network’, * ... used for network-booting the ironic nodes * These interfaces are configured with an IP Address from the subnet of the ‘ironic provisioning network’, * Typically the ironic provisioning network is on a flat provider network ... but does not have to be * At least one compute node must also be attached to the ‘ironic provisioning network’ * The ironic service is optional in StarlingX Deployments * Before enabling it you must first set a number of ironic ‘service parameters’ i.e. * system service-parameter-add ironic neutron provisioning_network= * system service-parameter-add ironic pxe tftp_server= * NOTE: this is the floating IP of the Ironic Conductor / TFTP Server on the ironic provisioning network * system service-parameter-add ironic pxe netmask=24 * system service-parameter-add ironic pxe controller_0_if= * system service-parameter-add ironic pxe controller_1_if= * and then * system service-enable ironic ... after that, create ironic nodes and boot Baremetal Instances on those nodes as described in the Ironic Documentation. Greg. From: "Hu, Yong" Date: Tuesday, November 13, 2018 at 8:48 PM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] [Ironic] deploy bare metal by Ironic One customer asked how StarlingX supports bare metal support by Ironic. And they mentioned Titanium Cloud used to support it well. Anyone has the experience to deploy bare metal system by Ironic on StarlingX? Suggests and feedbacks are much appreciated! -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dariush.Eslimi at windriver.com Tue Nov 20 14:02:21 2018 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Tue, 20 Nov 2018 14:02:21 +0000 Subject: [Starlingx-discuss] UID / GID adds and removes in setup package In-Reply-To: <260adee4-cc85-25ef-8732-12eaa8d80736@linux.intel.com> References: <260adee4-cc85-25ef-8732-12eaa8d80736@linux.intel.com> Message-ID: I will try to go get your answer, but would you mind creating a task for this as we agreed so I can answer there as a comment. Thanks, Dariush -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: November-19-18 6:35 PM To: starlingx-discuss at lists.starlingx.io; Eslimi, Dariush Subject: UID / GID adds and removes in setup package Hi Dariush, As I was reviewing the recent setup package refactor, I thought we need more background on why we add / remove uids and gids in the setup package vs for in an associated stx packages. I can understand some of the uids (add associated gids) are being removed such as mail, operator, games, ftp, lp. But the bin, daemon and adm users are also removed, and I think later we modify other packages because some of these users are missing. Is there any reason we can't keep these standard UIDs/GIDs? Sau! From sajuptpm at gmail.com Tue Nov 20 14:06:19 2018 From: sajuptpm at gmail.com (Saju M) Date: Tue, 20 Nov 2018 19:36:19 +0530 Subject: [Starlingx-discuss] Simplex mode : config_controller Failed to execute bootstrap manifest Message-ID: HI, I am using below starlingx iso (build 2018-Nov-11) http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/outputs/iso/bootimage.iso *1)* “sudo config_controller” failed with following error message (Selected Simplex mode) 02/08 Applying bootstrap manifest … Failed to execute bootstrap manifest *2)* *I run it again, but this time it failed with different error*. Configuration Failed: Configuration has already been done and cannot be repeated I think, I have to delete “/tmp/config/cgcs_config” to re-run “sudo config_controller”. Please let me know the procedure to re-run “sudo config_controller”. *3)Let me go back to bootstrap error.* I have checked “puppet.log” and seen now error there, my be that is the reason of bootstrap failure. localhost:~$ localhost:~$ sudo vim /var/log/puppet/latest/puppet.log localhost:~$ 2018-11-20T12:27:05.851 ^[[0;36mDebug: 2018-11-20 12:27:04 +0000 hiera(): Found platform::params::security_feature in global^[[0m 2018-11-20T12:27:05.856 ^[[1;31mError: 2018-11-20 12:27:04 +0000 Evaluation Error: *Unknown variable: '::platform_res_mem'.* at /usr/share/puppet/modules/platform/manifests/params.pp:37:23 on node localhost 2018-11-20T12:27:05.862 /usr/share/ruby/vendor_ruby/puppet/pops/evaluator/runtime3_support.rb:39:in `optionally_fail' 2018-11-20T12:27:05.867 /usr/share/ruby/vendor_ruby/puppet/pops/evaluator/runtime3_support.rb:99:in `get_variable_value' localhost:~$ localhost:~$ Regards Saju Madhavan +91 09535134654 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sajuptpm at gmail.com Tue Nov 20 14:32:12 2018 From: sajuptpm at gmail.com (Saju M) Date: Tue, 20 Nov 2018 20:02:12 +0530 Subject: [Starlingx-discuss] Simplex mode : config_controller Failed to execute bootstrap manifest In-Reply-To: References: Message-ID: Hi, Is this is the reason of bootstrap failure ? localhost:~$ localhost:~$ localhost:~$ cat /usr/share/puppet/modules/platform/lib/facter/platform_res_mem.rb Facter.add(:platform_res_mem) do setcode "memtop | awk 'FNR == 3 {a=$13+$14} END {print a}'" end localhost:~$ localhost:~$ localhost:~$ sudo memtop | awk 'FNR == 3 {a=$13+$14} END {print a}' Cannot open file: /sys/devices/system/node/node1/meminfo (No such file or directory) at /usr/bin/memtop line 257. localhost:~$ localhost:~$ Regards Saju Madhavan +91 09535134654 On Tue, Nov 20, 2018 at 7:36 PM Saju M wrote: > HI, > > I am using below starlingx iso (build 2018-Nov-11) > > http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/outputs/iso/bootimage.iso > > *1)* > “sudo config_controller” failed with following error message (Selected > Simplex mode) > > 02/08 Applying bootstrap manifest … Failed to execute bootstrap manifest > > *2)* > *I run it again, but this time it failed with different error*. > Configuration Failed: Configuration has already been done and cannot be > repeated > > I think, I have to delete “/tmp/config/cgcs_config” to re-run “sudo > config_controller”. > Please let me know the procedure to re-run “sudo config_controller”. > > > *3)Let me go back to bootstrap error.* > > I have checked “puppet.log” and seen now error there, my be that is the > reason of bootstrap failure. > > localhost:~$ > localhost:~$ sudo vim /var/log/puppet/latest/puppet.log > localhost:~$ > 2018-11-20T12:27:05.851 ^[[0;36mDebug: 2018-11-20 12:27:04 +0000 hiera(): > Found platform::params::security_feature in global^[[0m > 2018-11-20T12:27:05.856 ^[[1;31mError: 2018-11-20 12:27:04 +0000 > Evaluation Error: *Unknown variable: '::platform_res_mem'.* at > /usr/share/puppet/modules/platform/manifests/params.pp:37:23 on node > localhost > 2018-11-20T12:27:05.862 > /usr/share/ruby/vendor_ruby/puppet/pops/evaluator/runtime3_support.rb:39:in > `optionally_fail' > 2018-11-20T12:27:05.867 > /usr/share/ruby/vendor_ruby/puppet/pops/evaluator/runtime3_support.rb:99:in > `get_variable_value' > localhost:~$ > localhost:~$ > > > > Regards > Saju Madhavan > +91 09535134654 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Tue Nov 20 03:00:30 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 20 Nov 2018 03:00:30 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack Distro meeting, 11/21 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35DCB4AE@SHSMSX104.ccr.corp.intel.com> Agenda for 11/21 meeting: 1. Discuss the feasibility of abandom source patch for non-OpenStack (Saul/Brent) 2. non-Openstack patch refactoring status (Zhipeng/Shuicheng) 3. kernel driver upgrade testing status update (Ada/Ricardo/Shuicheng) 4. Pyhon2to3 non-OpenStack status (Austin) 5. Ceph upgrade status (Vivian/Dehao) 6. Devstack flocks plug-in update (Erick) 7. Opens (all) -----Original Appointment----- From: Xie, Cindy Sent: Monday, November 5, 2018 2:27 PM To: Xie, Cindy; Wold, Saul; 'Rowsell, Brent'; Jones, Bruce E; Troyer, Dean; 'Khalil, Ghada'; Waheed, Numan; Lin, Shuicheng; Zhu, Vivian; Shang, Dehao; Liu, ZhipengS; Hu, Yong; Sun, Austin; Somerville, Jim; starlingx-discuss at lists.starlingx.io Cc: Perez Carranza, Jose; 'Hellmann, Gil'; 'Waines, Greg'; 'Chen, Jacky'; Armstrong, Robert H; Perez Rodriguez, Humberto I; Martinez Landa, Hayde; Martinez Monroy, Elio; Hu, Wei W; 'Seiler, Glenn'; 'Eslimi, Dariush'; Gomez, Juan P; Lara, Cesar; Young, Ken; Arce Moreno, Abraham Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, November 21, 2018 6:00 AM-7:00 AM (UTC-08:00) Pacific Time (US & Canada). Where: https://zoom.us/j/342730236 . Cadence and time slot: o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) . Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ . Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other From claire at openstack.org Tue Nov 20 14:50:22 2018 From: claire at openstack.org (claire at openstack.org) Date: Tue, 20 Nov 2018 14:50:22 +0000 Subject: [Starlingx-discuss] Updated invitation: Weekly StarlingX mtg 7:00am Pacific Timezone @ Weekly from 9am to 10am on Wednesday (CST) (starlingx-discuss@lists.starlingx.io) Message-ID: <000000000000c747fb057b19c063@google.com> This event has been changed. Title: Weekly StarlingX mtg 7:00am Pacific Timezone (changed) Agenda & Notes: https://wiki.openstack.org/wiki/StarlingX#Meetings When: Weekly from 9am to 10am on Wednesday Central Time - Chicago (changed) Where: https://zoom.us/j/342730236 Calendar: starlingx-discuss at lists.starlingx.io Who: * claire at openstack.org - organizer * Ildiko Vancsa * starlingx-discuss at lists.starlingx.io Event details: https://www.google.com/calendar/event?action=VIEW&eid=XzZvb2syYzloNjkxMzBiOWg4Z3A0Y2I5azg4bzM0YjlwNmgxNDJiYTI2b3MzMmc5ZzZoMWs2ZHBuNmsgc3Rhcmxpbmd4LWRpc2N1c3NAbGlzdHMuc3Rhcmxpbmd4Lmlv&tok=MjAjY2xhaXJlQG9wZW5zdGFjay5vcmcyNzEzYTdmZDQ3NjI0OWViZWEyNjA2ZTUzMjA3ZjZhODliOGZkMzAy&ctz=America%2FChicago&hl=en&es=0 Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account starlingx-discuss at lists.starlingx.io because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2336 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 2400 bytes Desc: not available URL: From lionel.fiat at atos.net Tue Nov 20 15:53:08 2018 From: lionel.fiat at atos.net (FIAT, LIONEL) Date: Tue, 20 Nov 2018 15:53:08 +0000 Subject: [Starlingx-discuss] Simplex mode : config_controller Failed to execute bootstrap manifest In-Reply-To: References: Message-ID: Hi Saju, All, If it can help: I have the same error for same context: starlingx iso (build 2018-Nov-11) in simplex mode. Regards, Lionel Lionel Fiat IoT Architect SL Big Data & Security – MCS ISS Mob: +33 6 12 45 89 11 lionel.fiat at atos.net 1 Rue de Provence BP 208 38130 ECHIROLLES atos.net From: Saju M Sent: Tuesday, November 20, 2018 3:32 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Simplex mode : config_controller Failed to execute bootstrap manifest Hi, Is this is the reason of bootstrap failure ? localhost:~$ localhost:~$ localhost:~$ cat /usr/share/puppet/modules/platform/lib/facter/platform_res_mem.rb Facter.add(:platform_res_mem) do setcode "memtop | awk 'FNR == 3 {a=$13+$14} END {print a}'" end localhost:~$ localhost:~$ localhost:~$ sudo memtop | awk 'FNR == 3 {a=$13+$14} END {print a}' Cannot open file: /sys/devices/system/node/node1/meminfo (No such file or directory) at /usr/bin/memtop line 257. localhost:~$ localhost:~$ Regards Saju Madhavan +91 09535134654 On Tue, Nov 20, 2018 at 7:36 PM Saju M > wrote: HI, I am using below starlingx iso (build 2018-Nov-11) http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/outputs/iso/bootimage.iso 1) “sudo config_controller” failed with following error message (Selected Simplex mode) 02/08 Applying bootstrap manifest … Failed to execute bootstrap manifest 2) I run it again, but this time it failed with different error. Configuration Failed: Configuration has already been done and cannot be repeated I think, I have to delete “/tmp/config/cgcs_config” to re-run “sudo config_controller”. Please let me know the procedure to re-run “sudo config_controller”. 3) Let me go back to bootstrap error. I have checked “puppet.log” and seen now error there, my be that is the reason of bootstrap failure. localhost:~$ localhost:~$ sudo vim /var/log/puppet/latest/puppet.log localhost:~$ 2018-11-20T12:27:05.851 ^[[0;36mDebug: 2018-11-20 12:27:04 +0000 hiera(): Found platform::params::security_feature in global^[[0m 2018-11-20T12:27:05.856 ^[[1;31mError: 2018-11-20 12:27:04 +0000 Evaluation Error: Unknown variable: '::platform_res_mem'. at /usr/share/puppet/modules/platform/manifests/params.pp:37:23 on node localhost 2018-11-20T12:27:05.862 /usr/share/ruby/vendor_ruby/puppet/pops/evaluator/runtime3_support.rb:39:in `optionally_fail' 2018-11-20T12:27:05.867 /usr/share/ruby/vendor_ruby/puppet/pops/evaluator/runtime3_support.rb:99:in `get_variable_value' localhost:~$ localhost:~$ Regards Saju Madhavan +91 09535134654 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 405 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 65 bytes Desc: image002.gif URL: From juan.carlos.alonso at intel.com Tue Nov 20 16:32:31 2018 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Tue, 20 Nov 2018 16:32:31 +0000 Subject: [Starlingx-discuss] Can not launch instance In-Reply-To: References: , Message-ID: <8557B550001AFB46A43A0CCC314BF85153C5CF68@FMSMSX108.amr.corp.intel.com> Hello Volker, Can you share me the steps to create an instance successfully? I am facing the same issue. Regards. Juan Carlos Alonso From: von Hoesslin, Volker [mailto:Volker.Hoesslin at swsn.de] Sent: Thursday, November 15, 2018 4:25 AM To: starlingx Subject: Re: [Starlingx-discuss] Can not launch instance cool, thanks for your feedback! i've already read and understood the topic with the backing. i'm now so far that it seems to work if I create an instance without the security-groups (default-group) specification, i don't know why exactly. as far as i've understood it now, it's supposed to have something to do with "port-security-enabled=false"? sorry that i got in touch with the group so quickly before i exhausted all my possibilities... I promise improvement ;) Von: Dinescu, Stefan [mailto:Stefan.Dinescu at windriver.com] Gesendet: Donnerstag, 15. November 2018 11:15 An: volker.von.hoesslin at gmx.de; starlingx Betreff: Re: [Starlingx-discuss] Can not launch instance hello, Just a few quick questions to eliminate some potential issues (or maybe even figure out the issue): 1. Are the storage nodes in an available state? 2. On the compute nodes, is nova-local configures for remote backing as well? To check use "system host-lvg-show compute-0 nova-local" and check the "instance_backing" parameter. ________________________________ From: volker.von.hoesslin at gmx.de [volker.von.hoesslin at gmx.de] Sent: Thursday, November 15, 2018 11:03 AM To: starlingx Subject: Re: [Starlingx-discuss] Can not launch instance ok, after download the first official ISO (Cengn-mirror) and reinstall the complete starlingX i got the same error. for now, i can see some lines in "/var/log/nova/nova-scheduler.log". i have pasted here: https://pastebin.com/TbvYwTqu i really need a running openstack and i am willing to spend money for service, please help me guys... volker... i don't understand that, either i am the only one who builds a starlingX-stack at all or i have to fight very hard for all the additional knowledge i need in addition to the install-doku... now i have created all necessary components: - external network - internal network - router (add external and internal network) - add flavoir (aggregate_instance_extra_specs:storage=remote) - add image (cirrOS 0.4.0 RAW/QCOW2) - add key pairs now i created a new instance (via horizon/CLI), without success. the instance is created but it ends in an error-stat :( error messages in the horizon GUI are meaningless for me: Fault Message: No valid host was found. There are not enough hosts available. compute-0: (RetryFilter) Previously tried: [[u'compute-1', u'compute-1'], [u'compute-0', u'compute-0']], compute-1: (RetryFilter) Previously tried: [[u'compute-1', u'compute-1'], [u'compute-0 Code: 501 Details: compute-0: (RetryFilter) Previously tried: [[u'compute-1', u'compute-1'], [u'compute-0', u'compute-0']], compute-1: (RetryFilter) Previously tried: [[u'compute-1', u'compute-1'], [u'compute-0', u'compute-0']] Created: Nov. 13, 2018, 11:49 a.m. ================================================ Alarm UUID: 15f5bc85-de93-4109-a278-425bafc7c997 Alarm ID: 700.001 Severity: critical Alarm State: set Alarm Type: processing-error Timestamp: Nov. 13, 2018, 11:49 a.m. Suppression: Entity Instance ID: tenant=571bfa02-4736-4359-a15d-871224b3b202.instance=3ef09380-47e6-479a-91cc-6813474a183d Entity Type ID: tenant.instance Probable Cause: underlying-resource-unavailable Proposed Repair Action: Manual intervention required Service Affecting: True Management Affecting: True Reason: Instance foobar123 owned by admin has failed to schedule Interesting is, half of the instance is missing: @see: https://imgur.com/a/UVmEZhF - missing NIC - missing IP Addresses - missing Security Groups - missing Volumes Attached does anyone still have a tip for me? Volker -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Peters at windriver.com Tue Nov 20 17:42:12 2018 From: Matt.Peters at windriver.com (Peters, Matt) Date: Tue, 20 Nov 2018 17:42:12 +0000 Subject: [Starlingx-discuss] Questions about patch ab1baac upstreaming In-Reply-To: <76647BD697F40748B1FA4F56DA02AA0B4D53B851@SHSMSX104.ccr.corp.intel.com> References: <76647BD697F40748B1FA4F56DA02AA0B4D53B851@SHSMSX104.ccr.corp.intel.com> Message-ID: <485BAAC5-DFA0-40EB-BF11-8222F92C6937@windriver.com> Hello Huifeng, You are correct. This commit should not be upstreamed since the underlying features are being upstreamed, refactored or abandoned. Regards, Matt From: "Le, Huifeng" Date: Tuesday, November 20, 2018 at 3:54 AM To: "Peters, Matt" Cc: "starlingx-discuss at lists.starlingx.io" Subject: Questions about patch ab1baac upstreaming Matt, I am looking at patch#ab1baac (US106501: Change to Titanium’s handling Neutron Extensions) which targets to remove wrs-fields from the response to non-wrs client (e.g. no ‘wrs-header’ in the client request), suppose this is STX special feature and not need for upstream, could you please help to confirm? Thanks much! Best Regards, Le, Huifeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Tue Nov 20 17:49:54 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 20 Nov 2018 17:49:54 +0000 Subject: [Starlingx-discuss] Questions about patch ab1baac upstreaming In-Reply-To: <485BAAC5-DFA0-40EB-BF11-8222F92C6937@windriver.com> References: <76647BD697F40748B1FA4F56DA02AA0B4D53B851@SHSMSX104.ccr.corp.intel.com> <485BAAC5-DFA0-40EB-BF11-8222F92C6937@windriver.com> Message-ID: <9A85D2917C58154C960D95352B22818BB1EAF71F@fmsmsx115.amr.corp.intel.com> Cool. One more resolved. There has been some confusion on what happens next once we get to this state. Do we: 1) Mark this patch as abandoned in the spreadsheet and wait to remove it until we rebase? 2) Mark the patch as abandoned and remove it from the code base? 3) Mark the patch as deleted and remove it from the code base now? 4) Something else? brucej From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, November 20, 2018 9:42 AM To: Le, Huifeng Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Questions about patch ab1baac upstreaming Hello Huifeng, You are correct. This commit should not be upstreamed since the underlying features are being upstreamed, refactored or abandoned. Regards, Matt From: "Le, Huifeng" > Date: Tuesday, November 20, 2018 at 3:54 AM To: "Peters, Matt" > Cc: "starlingx-discuss at lists.starlingx.io" > Subject: Questions about patch ab1baac upstreaming Matt, I am looking at patch#ab1baac (US106501: Change to Titanium’s handling Neutron Extensions) which targets to remove wrs-fields from the response to non-wrs client (e.g. no ‘wrs-header’ in the client request), suppose this is STX special feature and not need for upstream, could you please help to confirm? Thanks much! Best Regards, Le, Huifeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Peters at windriver.com Tue Nov 20 17:55:43 2018 From: Matt.Peters at windriver.com (Peters, Matt) Date: Tue, 20 Nov 2018 17:55:43 +0000 Subject: [Starlingx-discuss] Questions about patch ab1baac upstreaming In-Reply-To: <9A85D2917C58154C960D95352B22818BB1EAF71F@fmsmsx115.amr.corp.intel.com> References: <76647BD697F40748B1FA4F56DA02AA0B4D53B851@SHSMSX104.ccr.corp.intel.com> <485BAAC5-DFA0-40EB-BF11-8222F92C6937@windriver.com> <9A85D2917C58154C960D95352B22818BB1EAF71F@fmsmsx115.amr.corp.intel.com> Message-ID: Hi Bruce, This particular one is tricky since it covers several other underlying patches/features. I would say that it falls within the category of #1. We need the other work to complete so this would need to be held until the underlying patches are either upstreamed or refactored. Regards, Matt From: "Jones, Bruce E" Date: Tuesday, November 20, 2018 at 12:50 PM To: "Peters, Matt" , "Le, Huifeng" , "Chilcote Bacco, Derek A" Cc: "starlingx-discuss at lists.starlingx.io" Subject: RE: Questions about patch ab1baac upstreaming Cool. One more resolved. There has been some confusion on what happens next once we get to this state. Do we: 1. Mark this patch as abandoned in the spreadsheet and wait to remove it until we rebase? 2. Mark the patch as abandoned and remove it from the code base? 3. Mark the patch as deleted and remove it from the code base now? 4. Something else? brucej From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, November 20, 2018 9:42 AM To: Le, Huifeng Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Questions about patch ab1baac upstreaming Hello Huifeng, You are correct. This commit should not be upstreamed since the underlying features are being upstreamed, refactored or abandoned. Regards, Matt From: "Le, Huifeng" > Date: Tuesday, November 20, 2018 at 3:54 AM To: "Peters, Matt" > Cc: "starlingx-discuss at lists.starlingx.io" > Subject: Questions about patch ab1baac upstreaming Matt, I am looking at patch#ab1baac (US106501: Change to Titanium’s handling Neutron Extensions) which targets to remove wrs-fields from the response to non-wrs client (e.g. no ‘wrs-header’ in the client request), suppose this is STX special feature and not need for upstream, could you please help to confirm? Thanks much! Best Regards, Le, Huifeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Allain.Legacy at windriver.com Tue Nov 20 18:12:58 2018 From: Allain.Legacy at windriver.com (Legacy, Allain) Date: Tue, 20 Nov 2018 18:12:58 +0000 Subject: [Starlingx-discuss] Questions about patch fd6cfc upstreaming In-Reply-To: References: Message-ID: <70A7408C6E1BFB41B192A929744D8523BAC380CE@ALA-MBD.corp.ad.wrs.com> We only observed this type of issue in a large office configuration where the neutron-server is overloaded during a DOR test (dead office recovery) where all nodes are powered off and back on. In such a scenario the system is overloaded for an extended period and there is a long delay between when events occur and when notifications are received by subscribers. It is difficult to reproduce this on small systems where the time between event and notification is short. I don't remember the exact details of the entire scenario, but the high level issue was that we wanted to avoid agents receiving and processing RPC messages that were sent to them before they started up. That happens more frequently in a DOR test because the server has a stale view of the system state and can send RPC messages to nodes that are not enabled yet. That is, its agent DB table may show that all agents are healthy depending on how long it took for the DOR to recover the controller node. What we found was that it was possible for the server to think that the agent was up when it was actually down. During the window where the server sees the agent as up it can send it RPC messages. Those messages get queued up and delivered to the agent once it is finally up. The problem is since the agent was not actually up in the first place those messages were never really valid. Therefore we wanted the agent to discard any RPC requests until after it was able to resync to the server. This allowed the system to avoid unnecessary transitions based on old data. One of the specific problems that this was addressing was something like this: 1. A subnet had no remaining IP addresses to allocated 2. A DCHP agent (agent-X) received a stale message to "create network" so it reserved a DHCP port with an IP address (this used the last available IP address) 3. Meanwhile, the DHCP agent (agent-Y) that actually was assigned the network came up and was not able to reserve a DHCP port because there were no IP addresses available 4. The first agent (agent-X) was taken down because its node was rebooted by system maintenance 5. The second agent (agent-Y) never retries the DHCP port creation because the DHCP agent has no periodic audit so there was no DHCP server servicing the network Regards, Allain Allain Legacy, Software Developer, Wind River direct 613.270.2279 fax 613.492.7870 skype allain.legacy 350 Terry Fox Drive, Suite 200, Ottawa, Ontario, K2K 2W5 [WIND] From: Qin, Kailun [mailto:kailun.qin at intel.com] Sent: Tuesday, November 20, 2018 2:02 AM To: Peters, Matt Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Questions about patch fd6cfc upstreaming Hi Matt, I'm working on the patch fd6cfc upstreaming, which tries to address the stale RPC message issue when DHCP agent restarting up. The patch was in good shape https://review.openstack.org/609463/ whereas the neutron community was questioning about the exact failure modes of this issue. The DHCP agent will have a full sync after the agent restarting up (https://github.com/openstack/neutron/blob/master/neutron/agent/dhcp/agent.py#L195), what kind of corner cases and negative behaviors could happen even w/ this full sync? Based on the commit message, I tried to reproduce this issue w/ the following steps: 1. schedule network1 to agent1. 2. turn down agent1 at almost the same time. 3. network1 is rescheduled to agent2 after finding that agent1 is dead. 4. turn up agent1, expecting stale RPC messages to be received by agent1 so that both agent1 and agent2 are servicing network1. However, I can only meet the described failure mode by sending another scheduling operation (network1->agent1) after step 2) is done. For the others, they seem to work as expected. Would you please kindly help provide more details about the failure pattern of this issue and/or the reproduction steps? Thanks a lot. BR, Kailun -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1807 bytes Desc: image001.png URL: From vm.rod25 at gmail.com Wed Nov 21 02:20:18 2018 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Tue, 20 Nov 2018 20:20:18 -0600 Subject: [Starlingx-discuss] Migrate Starling X kernel patches to LTS kernel Message-ID: Hi team I am a new user/developer of starling X and after searching into the kernel metapatches at: https://git.starlingx.io/cgit/stx-integ/tree/kernel Some questions came to me : As far as I can see we are under kernel 3.10 from RHEL RT fork right? There are some ( actually many ) security and functional changes that exist in the LTS kernel ( like 4.19 as an example), because of that I would like to use a more stable kernel into my starling x system Is there any specific reason why use that specific for from RHEL? What does starling X think about the migration of these patches ( some of them are already applied into the latest versions of Linux Kernel)? What kind of test should I perform to check that my vanilla kernel + STX patches work as expected? All feedback is more than welcome BTW thanks to Mario and Saul for the help on understand more these patches Regards Victor Rodriguez From Brent.Rowsell at windriver.com Wed Nov 21 02:25:48 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Wed, 21 Nov 2018 02:25:48 +0000 Subject: [Starlingx-discuss] Migrate Starling X kernel patches to LTS kernel In-Reply-To: References: Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB318642@ALA-MBD.corp.ad.wrs.com> There are two kernels, standard and rt. Both are centos 7.5 based with a small set of patches applied on top along with modified kernel config options. Not quite understanding what you are asking. Are you proposing to replace the kernel in the starlingX project or just in your local environment ? What is the objective here ? Brent -----Original Message----- From: Victor Rodriguez [mailto:vm.rod25 at gmail.com] Sent: Tuesday, November 20, 2018 9:20 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Migrate Starling X kernel patches to LTS kernel Hi team I am a new user/developer of starling X and after searching into the kernel metapatches at: https://git.starlingx.io/cgit/stx-integ/tree/kernel Some questions came to me : As far as I can see we are under kernel 3.10 from RHEL RT fork right? There are some ( actually many ) security and functional changes that exist in the LTS kernel ( like 4.19 as an example), because of that I would like to use a more stable kernel into my starling x system Is there any specific reason why use that specific for from RHEL? What does starling X think about the migration of these patches ( some of them are already applied into the latest versions of Linux Kernel)? What kind of test should I perform to check that my vanilla kernel + STX patches work as expected? All feedback is more than welcome BTW thanks to Mario and Saul for the help on understand more these patches Regards Victor Rodriguez _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From vm.rod25 at gmail.com Wed Nov 21 02:42:35 2018 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Tue, 20 Nov 2018 20:42:35 -0600 Subject: [Starlingx-discuss] Migrate Starling X kernel patches to LTS kernel In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB318642@ALA-MBD.corp.ad.wrs.com> References: <2588653EBDFFA34B982FAF00F1B4844EBB318642@ALA-MBD.corp.ad.wrs.com> Message-ID: On Tue, Nov 20, 2018 at 8:25 PM Rowsell, Brent wrote: > > There are two kernels, standard and rt. > Both are centos 7.5 based with a small set of patches applied on top along with modified kernel config options. > Thanks for the clarification > Not quite understanding what you are asking. Are you proposing to replace the kernel in the starlingX project or just in your local environment ? For my local environment. I would not like to use CentOS kernel 3.10 but instead LTS 4.19 > What is the objective here ? To have a more stable and secure kernel on my production system, there are security fixes that would like to have on my kernel that LTS provides I know RHEL/CentOS is based on kernel 3.10 but other OSs are ot like ubuntu/debian/fedora Regards > > Brent > > -----Original Message----- > From: Victor Rodriguez [mailto:vm.rod25 at gmail.com] > Sent: Tuesday, November 20, 2018 9:20 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Migrate Starling X kernel patches to LTS kernel > > Hi team > > I am a new user/developer of starling X and after searching into the kernel metapatches at: > > https://git.starlingx.io/cgit/stx-integ/tree/kernel > > Some questions came to me : > > As far as I can see we are under kernel 3.10 from RHEL RT fork right? > There are some ( actually many ) security and functional changes that exist in the LTS kernel ( like 4.19 as an example), because of that I would like to use a more stable kernel into my starling x system > > Is there any specific reason why use that specific for from RHEL? > > What does starling X think about the migration of these patches ( some of them are already applied into the latest versions of Linux Kernel)? > > What kind of test should I perform to check that my vanilla kernel + STX patches work as expected? > > All feedback is more than welcome > > BTW thanks to Mario and Saul for the help on understand more these patches > > Regards > > Victor Rodriguez > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From kailun.qin at intel.com Wed Nov 21 03:01:06 2018 From: kailun.qin at intel.com (Qin, Kailun) Date: Wed, 21 Nov 2018 03:01:06 +0000 Subject: [Starlingx-discuss] Questions about patch fd6cfc upstreaming In-Reply-To: <70A7408C6E1BFB41B192A929744D8523BAC380CE@ALA-MBD.corp.ad.wrs.com> References: <70A7408C6E1BFB41B192A929744D8523BAC380CE@ALA-MBD.corp.ad.wrs.com> Message-ID: Allain, Great thanks for the information! The scenario is reasonable and detailed enough for me. Let's feedback this along with some other follow-up answers to the Neutron team and see how it goes. BR, Kailun From: Legacy, Allain [mailto:Allain.Legacy at windriver.com] Sent: Wednesday, November 21, 2018 2:13 AM To: Qin, Kailun ; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io Subject: RE: Questions about patch fd6cfc upstreaming We only observed this type of issue in a large office configuration where the neutron-server is overloaded during a DOR test (dead office recovery) where all nodes are powered off and back on. In such a scenario the system is overloaded for an extended period and there is a long delay between when events occur and when notifications are received by subscribers. It is difficult to reproduce this on small systems where the time between event and notification is short. I don't remember the exact details of the entire scenario, but the high level issue was that we wanted to avoid agents receiving and processing RPC messages that were sent to them before they started up. That happens more frequently in a DOR test because the server has a stale view of the system state and can send RPC messages to nodes that are not enabled yet. That is, its agent DB table may show that all agents are healthy depending on how long it took for the DOR to recover the controller node. What we found was that it was possible for the server to think that the agent was up when it was actually down. During the window where the server sees the agent as up it can send it RPC messages. Those messages get queued up and delivered to the agent once it is finally up. The problem is since the agent was not actually up in the first place those messages were never really valid. Therefore we wanted the agent to discard any RPC requests until after it was able to resync to the server. This allowed the system to avoid unnecessary transitions based on old data. One of the specific problems that this was addressing was something like this: 1. A subnet had no remaining IP addresses to allocated 2. A DCHP agent (agent-X) received a stale message to "create network" so it reserved a DHCP port with an IP address (this used the last available IP address) 3. Meanwhile, the DHCP agent (agent-Y) that actually was assigned the network came up and was not able to reserve a DHCP port because there were no IP addresses available 4. The first agent (agent-X) was taken down because its node was rebooted by system maintenance 5. The second agent (agent-Y) never retries the DHCP port creation because the DHCP agent has no periodic audit so there was no DHCP server servicing the network Regards, Allain Allain Legacy, Software Developer, Wind River direct 613.270.2279 fax 613.492.7870 skype allain.legacy 350 Terry Fox Drive, Suite 200, Ottawa, Ontario, K2K 2W5 [WIND] From: Qin, Kailun [mailto:kailun.qin at intel.com] Sent: Tuesday, November 20, 2018 2:02 AM To: Peters, Matt Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Questions about patch fd6cfc upstreaming Hi Matt, I'm working on the patch fd6cfc upstreaming, which tries to address the stale RPC message issue when DHCP agent restarting up. The patch was in good shape https://review.openstack.org/609463/ whereas the neutron community was questioning about the exact failure modes of this issue. The DHCP agent will have a full sync after the agent restarting up (https://github.com/openstack/neutron/blob/master/neutron/agent/dhcp/agent.py#L195), what kind of corner cases and negative behaviors could happen even w/ this full sync? Based on the commit message, I tried to reproduce this issue w/ the following steps: 1. schedule network1 to agent1. 2. turn down agent1 at almost the same time. 3. network1 is rescheduled to agent2 after finding that agent1 is dead. 4. turn up agent1, expecting stale RPC messages to be received by agent1 so that both agent1 and agent2 are servicing network1. However, I can only meet the described failure mode by sending another scheduling operation (network1->agent1) after step 2) is done. For the others, they seem to work as expected. Would you please kindly help provide more details about the failure pattern of this issue and/or the reproduction steps? Thanks a lot. BR, Kailun -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1807 bytes Desc: image001.png URL: From shuicheng.lin at intel.com Wed Nov 21 04:50:56 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Wed, 21 Nov 2018 04:50:56 +0000 Subject: [Starlingx-discuss] question about create-var-run-resource-agents.patch in cluster-resource-agent Message-ID: <9700A18779F35F49AF027300A49E7C765FE3D93F@SHSMSX101.ccr.corp.intel.com> Hi Scott/Penney, I am looking at story [0], which want to remove patches [1] for create directory /var/run/resource-agents. And I find another patch [2] disabled explicit requires the directory in spec file. (#%dir %attr (1755, root, root) %{_var}/run/resource-agents) Could you share me the history of patch [1] and [2]? I prefer to add back this line in patch [2], and patch [1] could be removed without puppet replacement. What's your suggestion? Thanks. [0]: https://storyboard.openstack.org/#!/story/2004019 [1]: https://git.openstack.org/cgit/openstack/stx-integ/tree/base/cluster-resource-agents/centos/patches/create-var-run-resource-agents.patch [2]: https://git.openstack.org/cgit/openstack/stx-integ/tree/base/cluster-resource-agents/centos/meta_patches/spec-avoid-dir-collisions.patch Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Wed Nov 21 10:24:37 2018 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Wed, 21 Nov 2018 10:24:37 +0000 Subject: [Starlingx-discuss] Can not launch instance In-Reply-To: <8557B550001AFB46A43A0CCC314BF85153C5CF68@FMSMSX108.amr.corp.intel.com> References: , <8557B550001AFB46A43A0CCC314BF85153C5CF68@FMSMSX108.amr.corp.intel.com> Message-ID: Hi, nothing easier than that, basically use the normal instance wizard in the horizon and don't make any entries in the step "security groups". regardless of that, i would be interested in a solution with security groups in the future! Volker... Von: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Gesendet: Dienstag, 20. November 2018 17:33 An: von Hoesslin, Volker; starlingx Betreff: RE: [Starlingx-discuss] Can not launch instance Hello Volker, Can you share me the steps to create an instance successfully? I am facing the same issue. Regards. Juan Carlos Alonso From: von Hoesslin, Volker [mailto:Volker.Hoesslin at swsn.de] Sent: Thursday, November 15, 2018 4:25 AM To: starlingx Subject: Re: [Starlingx-discuss] Can not launch instance cool, thanks for your feedback! i've already read and understood the topic with the backing. i'm now so far that it seems to work if I create an instance without the security-groups (default-group) specification, i don't know why exactly. as far as i've understood it now, it's supposed to have something to do with "port-security-enabled=false"? sorry that i got in touch with the group so quickly before i exhausted all my possibilities... I promise improvement ;) Von: Dinescu, Stefan [mailto:Stefan.Dinescu at windriver.com] Gesendet: Donnerstag, 15. November 2018 11:15 An: volker.von.hoesslin at gmx.de; starlingx Betreff: Re: [Starlingx-discuss] Can not launch instance hello, Just a few quick questions to eliminate some potential issues (or maybe even figure out the issue): 1. Are the storage nodes in an available state? 2. On the compute nodes, is nova-local configures for remote backing as well? To check use "system host-lvg-show compute-0 nova-local" and check the "instance_backing" parameter. ________________________________ From: volker.von.hoesslin at gmx.de [volker.von.hoesslin at gmx.de] Sent: Thursday, November 15, 2018 11:03 AM To: starlingx Subject: Re: [Starlingx-discuss] Can not launch instance ok, after download the first official ISO (Cengn-mirror) and reinstall the complete starlingX i got the same error. for now, i can see some lines in "/var/log/nova/nova-scheduler.log". i have pasted here: https://pastebin.com/TbvYwTqu i really need a running openstack and i am willing to spend money for service, please help me guys... volker... i don't understand that, either i am the only one who builds a starlingX-stack at all or i have to fight very hard for all the additional knowledge i need in addition to the install-doku... now i have created all necessary components: - external network - internal network - router (add external and internal network) - add flavoir (aggregate_instance_extra_specs:storage=remote) - add image (cirrOS 0.4.0 RAW/QCOW2) - add key pairs now i created a new instance (via horizon/CLI), without success. the instance is created but it ends in an error-stat :( error messages in the horizon GUI are meaningless for me: Fault Message: No valid host was found. There are not enough hosts available. compute-0: (RetryFilter) Previously tried: [[u'compute-1', u'compute-1'], [u'compute-0', u'compute-0']], compute-1: (RetryFilter) Previously tried: [[u'compute-1', u'compute-1'], [u'compute-0 Code: 501 Details: compute-0: (RetryFilter) Previously tried: [[u'compute-1', u'compute-1'], [u'compute-0', u'compute-0']], compute-1: (RetryFilter) Previously tried: [[u'compute-1', u'compute-1'], [u'compute-0', u'compute-0']] Created: Nov. 13, 2018, 11:49 a.m. ================================================ Alarm UUID: 15f5bc85-de93-4109-a278-425bafc7c997 Alarm ID: 700.001 Severity: critical Alarm State: set Alarm Type: processing-error Timestamp: Nov. 13, 2018, 11:49 a.m. Suppression: Entity Instance ID: tenant=571bfa02-4736-4359-a15d-871224b3b202.instance=3ef09380-47e6-479a-91cc-6813474a183d Entity Type ID: tenant.instance Probable Cause: underlying-resource-unavailable Proposed Repair Action: Manual intervention required Service Affecting: True Management Affecting: True Reason: Instance foobar123 owned by admin has failed to schedule Interesting is, half of the instance is missing: @see: https://imgur.com/a/UVmEZhF - missing NIC - missing IP Addresses - missing Security Groups - missing Volumes Attached does anyone still have a tip for me? Volker -------------- next part -------------- An HTML attachment was scrubbed... URL: From changcheng.liu at intel.com Wed Nov 21 10:35:17 2018 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Wed, 21 Nov 2018 10:35:17 +0000 Subject: [Starlingx-discuss] stx-tools: setup stx build environment Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50EF91DD@SHSMSX104.ccr.corp.intel.com> Could someone help check below bug? Title: stx-tools: failed to download required packaged Link: https://bugs.launchpad.net/starlingx/+bug/1804412 B.R. Changcheng From: Liu, Changcheng Sent: Friday, November 16, 2018 8:31 PM To: starlingx-discuss at lists.starlingx.io Subject: setup stx build environment Hi all, I have one question about setting up stx build environment. Why not move lots of many basic program installation process from mirror-check.sh to Dockerfile directly? Then stx community could supply one basic docker image as the base image to let developer customize it. Currently, I still need install lots of program after building Dockerfile into image. B.R. Changcheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Wed Nov 21 14:36:39 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 21 Nov 2018 14:36:39 +0000 Subject: [Starlingx-discuss] question about create-var-run-resource-agents.patch in cluster-resource-agent In-Reply-To: <9700A18779F35F49AF027300A49E7C765FE3D93F@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C765FE3D93F@SHSMSX101.ccr.corp.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA3F0F92@ALA-MBD.corp.ad.wrs.com> We can't do this in a spec file, as /var/run is on tmpfs, so the dir would be lost on the subsequent reboot. But we do have the following: controller-0:~$ rpm -qf /usr/lib/tmpfiles.d/resource-agents.conf resource-agents-3.9.5-124.el7.tis.12.x86_64 controller-0:~$ cat /usr/lib/tmpfiles.d/resource-agents.conf d /var/run/resource-agents/ 1755 root root So we could probably drop patch [1] and safely rely on the tmpfiles.d to create it. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Tuesday, November 20, 2018 11:51 PM To: Little, Scott; Penney, Don; Rowsell, Brent Cc: starlingx-discuss at lists.starlingx.io Subject: question about create-var-run-resource-agents.patch in cluster-resource-agent Hi Scott/Penney, I am looking at story [0], which want to remove patches [1] for create directory /var/run/resource-agents. And I find another patch [2] disabled explicit requires the directory in spec file. (#%dir %attr (1755, root, root) %{_var}/run/resource-agents) Could you share me the history of patch [1] and [2]? I prefer to add back this line in patch [2], and patch [1] could be removed without puppet replacement. What's your suggestion? Thanks. [0]: https://storyboard.openstack.org/#!/story/2004019 [1]: https://git.openstack.org/cgit/openstack/stx-integ/tree/base/cluster-resource-agents/centos/patches/create-var-run-resource-agents.patch [2]: https://git.openstack.org/cgit/openstack/stx-integ/tree/base/cluster-resource-agents/centos/meta_patches/spec-avoid-dir-collisions.patch Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Wed Nov 21 14:54:42 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 21 Nov 2018 14:54:42 +0000 Subject: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack Distro meeting, 11/21 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35DCCC25@SHSMSX104.ccr.corp.intel.com> Agenda and notes for 11/21 meeting: 1. Discuss the feasibility of abandon source patch for non-OpenStack (Saul/Brent) push this topic to later time when it's more mature. 2. non-Openstack patch refactoring status (Zhipeng/Shuicheng) for story: https://storyboard.openstack.org/#!/story/2003768 , total 23 tasks, we have 17 merged, and 6 still under review. 94 patches got abandoned, and 10 srpms can be replaced by rpms. in total, we have 137 patches removed. 3. kernel driver upgrade testing status update (Ada/Ricardo/Shuicheng) face installation issues yesterday, will install new ISO again. Shuicheng provided a new ISO today. the stability of GDC system may related to using validation HW instead of commercial systems. The ISO shared with Shuicheng didn't show any in-stability issue. did Shanghai ever install StarlingX SW on QAT system through FlexRAN? no, it works well on that NPG QAT system. 4. Pyhon2to3 non-OpenStack status (Austin) we have total 364 packages which has Python code. We did investigation and 303 rpms includes Python code. Need more work to understand if they are already p3 compatible. 107 packages have tis patches we need to scan if they are already p3 compatible for those patches. (most of them are in stx-integ, but some Openstack related patches are under stx-upstream). all Flock services are working in progress, stx-config, stx-nfv, stx-integ are still WIP. others are all done. Stein will support Python3. more work needs to be done to understand the overall picture of 303 rpms - some uncertainties if those upstream project already have Python3 transition plan or not. 5. Ceph upgrade status (Vivian/Dehao) Dehao followed up w/ Scott regarding to Ceph v13.2 upgrade. Upgrade method is updated and 1st path has been done with updated scripts. scripts refer the default build-rpms scripts by adding some special steps. Scott requirement: split download and action from Ceph scripts. repo-sync can download all ceph submodules. download tarball will download all libraries. No puppet download is required at this stage. StarlingX can be built with updated Ceph v13.2.0. Brent prefer to move to v13.2.2. Need to wait for Dean to create a branch to hold v13.2.2; AR: Saul will try to do it and see if he has the privilige of doing it on staging. in total we have 42 patches, 10 of them are abandon, 32 needs to be rebased to new version. WIP based on v13.2.0, with the decision of moving to v13.2.2, it may impact the schedule. Saul just created v13.2.2 branch under stx-ceph. Dehao is checking for the branch. Changcheng faced rpm download issue from China and filed a launchpad bug -> assigned to Erich. Ask WR to double confirm if those 10 patches can be removed or not. Frank has people from WR to look at them. document created: https://etherpad.openstack.org/p/stx-ceph_upgrade. 6. Devstack flocks plug-in update (Erick) skip this topic as Erick is not on. 7. Glance/Cinder raw cache (Lisa) to abandon patches about raw cache feature by WR, the new Glance/Cinder provide such features already. What's the difference btw the two implementation. Ovidiu from WR is reviewing the email sent from Lisa and will reply it, this is already in the todo list. 8. Opens (all) Saul question: how about Qemu update, need to have update from Ghada or Jim regarding the qemu 3.0 upgrade status. -----Original Appointment----- From: Xie, Cindy Sent: Monday, November 5, 2018 2:27 PM To: Xie, Cindy; Wold, Saul; 'Rowsell, Brent'; Jones, Bruce E; Troyer, Dean; 'Khalil, Ghada'; Waheed, Numan; Lin, Shuicheng; Zhu, Vivian; Shang, Dehao; Liu, ZhipengS; Hu, Yong; Sun, Austin; Somerville, Jim; starlingx-discuss at lists.starlingx.io Cc: Perez Carranza, Jose; 'Hellmann, Gil'; 'Waines, Greg'; 'Chen, Jacky'; Armstrong, Robert H; Perez Rodriguez, Humberto I; Martinez Landa, Hayde; Martinez Monroy, Elio; Hu, Wei W; 'Seiler, Glenn'; 'Eslimi, Dariush'; Gomez, Juan P; Lara, Cesar; Young, Ken; Arce Moreno, Abraham Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, November 21, 2018 6:00 AM-7:00 AM (UTC-08:00) Pacific Time (US & Canada). Where: https://zoom.us/j/342730236 . Cadence and time slot: o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) . Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ . Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other From abraham.arce.moreno at intel.com Wed Nov 21 15:14:17 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Wed, 21 Nov 2018 15:14:17 +0000 Subject: [Starlingx-discuss] [Build] Create mechanism to publish tarballs in StarlingX Message-ID: Hi all, As a result of our review for story 2003736 [0], here you have our first level of findings but most important a request for comments: [ Objective ] "Create a new zuul check job to create tarballs from stx projects" Taking the existing OpenStack tarball infrastructure, we have the url tarballs @ openstack org [1] so initial idea would be to host StarlingX tarballs in tarballs @ starlingx io [2] - Any question on the objective? Anything to highlight? - Any other preference where to host the tarballs? [ Zuul ] There are some examples of jobs related to tarballs: - publish-openstack-artifacts - publish-openstack-python-branch-tarball - build-openstack-puppet-tarball - publish-openstack-puppet-branch-tarball Should we target a reuse of existing jobs, probably not listed above or create a new set of jobs? - build-starlingx-tarball - publish-starlingx-tarball Getting your feedback in these first 2 questions will allow us to get a solid direction for the rest of the week. [0] https://storyboard.openstack.org/#!/story/2003736 [1] http://tarballs.openstack.org/ [2] http://tarballs.starlingx.io/ From abraham.arce.moreno at intel.com Wed Nov 21 15:22:11 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Wed, 21 Nov 2018 15:22:11 +0000 Subject: [Starlingx-discuss] setup stx build environment In-Reply-To: <0D7994A90DD70040A9F5E77C4D23C57D50EF7133@SHSMSX104.ccr.corp.intel.com> References: <0D7994A90DD70040A9F5E77C4D23C57D50EF7133@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi Changcheng, > I have one question about setting up stx build environment. > Why not move lots of many basic program installation process from > mirror-check.sh to Dockerfile directly? There is a story to simplify the building process [0] > Then stx community could supply one basic docker image as the base > image to let developer customize it. Currently, I still need install lots of > program after building Dockerfile into image. Here you have some patches already merged and waiting for feedback: - [1] Add unified dockerfile - [2] Update Makefile - [3] Remove deprecated Dockerfiles - [4] Update documentation This last commit will be fully reviewed by our Technical Writing team. [0] https://storyboard.openstack.org/#!/story/2003712 [1] https://review.openstack.org/#/c/601306/ [2] https://review.openstack.org/#/c/601307/ [3] https://review.openstack.org/#/c/601309/ [4] https://review.openstack.org/#/c/601308/ From changcheng.liu at intel.com Wed Nov 21 15:24:14 2018 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Wed, 21 Nov 2018 15:24:14 +0000 Subject: [Starlingx-discuss] stx-tools: setup stx build environment Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50EF931C@SHSMSX104.ccr.corp.intel.com> Hi Erich, Please help check the problem. Tell me if you need more information. I'm trying to run "download_mirror.sh" again. B.R. Changcheng From: Liu, Changcheng Sent: Wednesday, November 21, 2018 6:35 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: stx-tools: setup stx build environment Could someone help check below bug? Title: stx-tools: failed to download required packaged Link: https://bugs.launchpad.net/starlingx/+bug/1804412 B.R. Changcheng From: Liu, Changcheng Sent: Friday, November 16, 2018 8:31 PM To: starlingx-discuss at lists.starlingx.io Subject: setup stx build environment Hi all, I have one question about setting up stx build environment. Why not move lots of many basic program installation process from mirror-check.sh to Dockerfile directly? Then stx community could supply one basic docker image as the base image to let developer customize it. Currently, I still need install lots of program after building Dockerfile into image. B.R. Changcheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From abraham.arce.moreno at intel.com Wed Nov 21 15:35:55 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Wed, 21 Nov 2018 15:35:55 +0000 Subject: [Starlingx-discuss] stx-tools: document isn't aligned with code In-Reply-To: <0D7994A90DD70040A9F5E77C4D23C57D50EF7D01@SHSMSX104.ccr.corp.intel.com> References: <0D7994A90DD70040A9F5E77C4D23C57D50EF7D01@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi again Changcheng, > I'm following below document to create-starlingx-packages. It's not > aligned with latest code. You are right... > https://docs.starlingx.io/developer_guide/index.html#create- > starlingx-packages > packages> > Could the man, who's responsible for continuous-integration, clean the > document and make it more clear? Under this review we will include the changes to align with Mario's cleanup: [Developer Guide] Setup Building Docker Container [0] The logic behind to accommodate the new "Developer Guide" flow proposal would look like: FYI "..." means content is not intended to be changed. - Requirements - ... - Development Environment Setup - ... - Prepare the Base Docker Image - Configuration - Sample localrc - Build Base Docker Image - Build the CentOS Mirror Repository - Run Mirror Docker Container - Download Packages - Verify Packages - Packages Structure - Create CentOS Mirror Repository - Create StarlingX Packages - Run Building Docker Container - Download Source Code Repositories - Build Packages - Build StarlingX ISO - Build Installer - ... - Build Avoidance - ... In summary, "flow proposal" could look like: - Prepare Base Docker Image - Build "base image" - Build the CentOS Mirror Repository - Run container from "base image" - Get mirror files - Create StarlingX Packages - Run container from "base image" - Get StarlingX source code - Build StarlingX packages - Build StarlingX ISO > 1. The stx-tools code isn't aligned with the above document since base- > build/build target has been removed. > 2. Besides this, README.rst is not updated in time when the build rule > has been changed. README.rst from stx-tools project is going under a review process [1] so please feel free to leave your comments. [0] https://review.openstack.org/#/c/619043/ [1] https://review.openstack.org/#/c/601308/ From chris.friesen at windriver.com Wed Nov 21 15:41:28 2018 From: chris.friesen at windriver.com (Chris Friesen) Date: Wed, 21 Nov 2018 09:41:28 -0600 Subject: [Starlingx-discuss] Support IBRS cpu model. In-Reply-To: References: Message-ID: On 11/16/2018 8:59 PM, Sun, Austin wrote: > Hi Chris: > Thanks your review. I have made new patch [1] based on your suggestion. Could you help review it again ? > > https://github.com/austinsun/stx-nova/commit/3255facb16b70b138ff12243822b43d1824f6890#diff-6955c78b8a0da8ec1cbf33c3834de1e0 The code looks okay, the git commit message looks like it was partially duplicated. Chris From abraham.arce.moreno at intel.com Wed Nov 21 15:48:27 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Wed, 21 Nov 2018 15:48:27 +0000 Subject: [Starlingx-discuss] Deployment from ISO In-Reply-To: References: Message-ID: Thanks Luis, Austin, To sync up our StarlingX community with respect upcoming installation changes: > El El vie, 16 nov 2018 a las 10:31, Sun, Austin > escribió: > > Hi Luis: > > You can check https://docs.starlingx.io/installation_guide/index.html > , which describe the HW request needed . Yes, you can deploy into VM ? In case deployment is being done via libvirt/qemu changes are coming, the set of patches under review are: - [0] stx-tools topic:xml-server-definition - [1] stx-docs [Doc] XML Server Definition > There is guide In the link shared. And you can find iso > http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/ > outputs/iso/ > /outputs/iso/> A patch is under review to have the CENGN Starlingx Mirror under our Installation Guide: [2] [Installation] CENGN StarlingX Mirror [0] https://review.openstack.org/#/q/topic:xml-server-definition+(status:open+OR+status:merged) [1] https://review.openstack.org/#/c/612826/ [2] https://review.openstack.org/#/c/617965/ From bruce.e.jones at intel.com Wed Nov 21 16:16:44 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 21 Nov 2018 16:16:44 +0000 Subject: [Starlingx-discuss] Notes from 11/21/18 community meeting Message-ID: <9A85D2917C58154C960D95352B22818BB1EB0034@fmsmsx115.amr.corp.intel.com> Agenda and Notes - Nov 21st Call * Happy Thanksgiving! The US based folks will be out Thursday - Friday this week. * Berlin Summit Summary - Bruce, etc... o Really good summit for StarlingX. Good showcase for the project, and great progress since May where we started with seed code. Big accomplishment by the team! o Brent presented to the BoD, Ian and Dean keynoted, there were numerous StarlingX sessions and we had good participation across the overall Open Infrastructure community. o Conference sessions were recorded and are in the process of being posted o The next Summit / PTG will be in Denver. The one after that will be in China! o The next OpenStack release will be called Train. * Patch resolution strategy change - Brent o Reduction of OpenStack technical debt has not been going as fast as we would like, which means maintaining the forks for longer and impacting rebasing. o The TSC discussed a new approach. Rather than work through patch by patch, the TSC proposes to turn the problem on its head and move to OpenStack master o As soon as possible. o We would then look to address gaps through upstream submissions/specs, refactoring of STX or (worst case) carrying a small number of patches in packaging RPMs. o Brent to post the chart deck describing the changes to keep onto the wiki. o List has been shared with the STX Neutron team and the Nova PTL. o Will likely change the release cadence to accommodate this change - Stein releases in April making it hard to support in an STX release in March. * We are looking into holding an in person community meeting in January to discuss planning for these changes. Hosted by Intel in Phoenix (Chandler). Target date is January 15-16 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Wed Nov 21 16:26:43 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 21 Nov 2018 16:26:43 +0000 Subject: [Starlingx-discuss] StarlingX mini-PTG Jan 15-16 in Phoenix Message-ID: <9A85D2917C58154C960D95352B22818BB1EB0050@fmsmsx115.amr.corp.intel.com> We are thinking about holding a StarlingX mini-PTG meeting in January in Phoenix, to be hosted on the Intel campus. I'd like to get an early headcount and make sure there are no conflicts for the dates. Please reply to this email and let me know if you can/want to attend, or if you would like to attend but have a conflict for these dates. Thank you! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From mario.alfredo.c.arevalo at intel.com Wed Nov 21 16:55:39 2018 From: mario.alfredo.c.arevalo at intel.com (Arevalo, Mario Alfredo C) Date: Wed, 21 Nov 2018 16:55:39 +0000 Subject: [Starlingx-discuss] stx-tools: document isn't aligned with code In-Reply-To: References: <0D7994A90DD70040A9F5E77C4D23C57D50EF7D01@SHSMSX104.ccr.corp.intel.com>, Message-ID: <6594B51DBE477C48AAE23675314E6C466451F8E3@fmsmsx107.amr.corp.intel.com> Hi Changcheng and Abraham, I have sent a new version in order to update the documentation according to the new changes in Dockerfile[s]. You can take a look in this link: https://review.openstack.org/#/c/601308/ sorry for any inconvenience. Best regards. Mario. ________________________________________ From: Arce Moreno, Abraham Sent: Wednesday, November 21, 2018 7:35 AM To: Liu, Changcheng; starlingx-discuss at lists.starlingx.io; Arevalo, Mario Alfredo C Subject: RE: stx-tools: document isn't aligned with code Hi again Changcheng, > I’m following below document to create-starlingx-packages. It’s not > aligned with latest code. You are right... > https://docs.starlingx.io/developer_guide/index.html#create- > starlingx-packages > packages> > Could the man, who’s responsible for continuous-integration, clean the > document and make it more clear? Under this review we will include the changes to align with Mario's cleanup: [Developer Guide] Setup Building Docker Container [0] The logic behind to accommodate the new "Developer Guide" flow proposal would look like: FYI "..." means content is not intended to be changed. - Requirements - ... - Development Environment Setup - ... - Prepare the Base Docker Image - Configuration - Sample localrc - Build Base Docker Image - Build the CentOS Mirror Repository - Run Mirror Docker Container - Download Packages - Verify Packages - Packages Structure - Create CentOS Mirror Repository - Create StarlingX Packages - Run Building Docker Container - Download Source Code Repositories - Build Packages - Build StarlingX ISO - Build Installer - ... - Build Avoidance - ... In summary, "flow proposal" could look like: - Prepare Base Docker Image - Build "base image" - Build the CentOS Mirror Repository - Run container from "base image" - Get mirror files - Create StarlingX Packages - Run container from "base image" - Get StarlingX source code - Build StarlingX packages - Build StarlingX ISO > 1. The stx-tools code isn’t aligned with the above document since base- > build/build target has been removed. > 2. Besides this, README.rst is not updated in time when the build rule > has been changed. README.rst from stx-tools project is going under a review process [1] so please feel free to leave your comments. [0] https://review.openstack.org/#/c/619043/ [1] https://review.openstack.org/#/c/601308/ From sgw at linux.intel.com Wed Nov 21 17:10:47 2018 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 21 Nov 2018 09:10:47 -0800 Subject: [Starlingx-discuss] Migrate Starling X kernel patches to LTS kernel In-Reply-To: References: <2588653EBDFFA34B982FAF00F1B4844EBB318642@ALA-MBD.corp.ad.wrs.com> Message-ID: Victor, Brent: There are a couple of things not mentioned that I have heard talked about on both sides of this discussion. My understanding is that the kernel version is based on the RHEL/CentOS version as it's a known tested combination at the Distro level, even though there are patches to the kernel and user-space. On the other side, the 3.10 RHEL kernel (with all the RHEL patches) may not address all the known CVEs, so there is a concern about overall security. Intel is looking at the newer kernel and porting the StarlingX patches (as needed) for the Clear and Multi-OS parts of the project. The overall question becomes can StarlingX take the 4.19LTS kernel as a newer base kernel for the project, it reduces the overall patch load and address some security issues. I believe you understand these objectives. Sau! On 11/20/18 6:42 PM, Victor Rodriguez wrote: > On Tue, Nov 20, 2018 at 8:25 PM Rowsell, Brent > wrote: >> >> There are two kernels, standard and rt. >> Both are centos 7.5 based with a small set of patches applied on top along with modified kernel config options. >> > > Thanks for the clarification > >> Not quite understanding what you are asking. Are you proposing to replace the kernel in the starlingX project or just in your local environment ? > > For my local environment. I would not like to use CentOS kernel 3.10 > but instead LTS 4.19 > >> What is the objective here ? > > To have a more stable and secure kernel on my production system, there > are security fixes that would like to have on my kernel that LTS > provides > > I know RHEL/CentOS is based on kernel 3.10 but other OSs are ot like > ubuntu/debian/fedora > > Regards > >> >> Brent >> >> -----Original Message----- >> From: Victor Rodriguez [mailto:vm.rod25 at gmail.com] >> Sent: Tuesday, November 20, 2018 9:20 PM >> To: starlingx-discuss at lists.starlingx.io >> Subject: [Starlingx-discuss] Migrate Starling X kernel patches to LTS kernel >> >> Hi team >> >> I am a new user/developer of starling X and after searching into the kernel metapatches at: >> >> https://git.starlingx.io/cgit/stx-integ/tree/kernel >> >> Some questions came to me : >> >> As far as I can see we are under kernel 3.10 from RHEL RT fork right? >> There are some ( actually many ) security and functional changes that exist in the LTS kernel ( like 4.19 as an example), because of that I would like to use a more stable kernel into my starling x system >> >> Is there any specific reason why use that specific for from RHEL? >> >> What does starling X think about the migration of these patches ( some of them are already applied into the latest versions of Linux Kernel)? >> >> What kind of test should I perform to check that my vanilla kernel + STX patches work as expected? >> >> All feedback is more than welcome >> >> BTW thanks to Mario and Saul for the help on understand more these patches >> >> Regards >> >> Victor Rodriguez >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From Brent.Rowsell at windriver.com Wed Nov 21 17:21:49 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Wed, 21 Nov 2018 17:21:49 +0000 Subject: [Starlingx-discuss] Migrate Starling X kernel patches to LTS kernel In-Reply-To: References: <2588653EBDFFA34B982FAF00F1B4844EBB318642@ALA-MBD.corp.ad.wrs.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB31A592@ALA-MBD.corp.ad.wrs.com> Saul, This is a big change. I suggest adding it to the next TSC call. Brent -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Wednesday, November 21, 2018 12:11 PM To: Victor Rodriguez ; Rowsell, Brent Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Migrate Starling X kernel patches to LTS kernel Victor, Brent: There are a couple of things not mentioned that I have heard talked about on both sides of this discussion. My understanding is that the kernel version is based on the RHEL/CentOS version as it's a known tested combination at the Distro level, even though there are patches to the kernel and user-space. On the other side, the 3.10 RHEL kernel (with all the RHEL patches) may not address all the known CVEs, so there is a concern about overall security. Intel is looking at the newer kernel and porting the StarlingX patches (as needed) for the Clear and Multi-OS parts of the project. The overall question becomes can StarlingX take the 4.19LTS kernel as a newer base kernel for the project, it reduces the overall patch load and address some security issues. I believe you understand these objectives. Sau! On 11/20/18 6:42 PM, Victor Rodriguez wrote: > On Tue, Nov 20, 2018 at 8:25 PM Rowsell, Brent > wrote: >> >> There are two kernels, standard and rt. >> Both are centos 7.5 based with a small set of patches applied on top along with modified kernel config options. >> > > Thanks for the clarification > >> Not quite understanding what you are asking. Are you proposing to replace the kernel in the starlingX project or just in your local environment ? > > For my local environment. I would not like to use CentOS kernel 3.10 > but instead LTS 4.19 > >> What is the objective here ? > > To have a more stable and secure kernel on my production system, there > are security fixes that would like to have on my kernel that LTS > provides > > I know RHEL/CentOS is based on kernel 3.10 but other OSs are ot like > ubuntu/debian/fedora > > Regards > >> >> Brent >> >> -----Original Message----- >> From: Victor Rodriguez [mailto:vm.rod25 at gmail.com] >> Sent: Tuesday, November 20, 2018 9:20 PM >> To: starlingx-discuss at lists.starlingx.io >> Subject: [Starlingx-discuss] Migrate Starling X kernel patches to LTS >> kernel >> >> Hi team >> >> I am a new user/developer of starling X and after searching into the kernel metapatches at: >> >> https://git.starlingx.io/cgit/stx-integ/tree/kernel >> >> Some questions came to me : >> >> As far as I can see we are under kernel 3.10 from RHEL RT fork right? >> There are some ( actually many ) security and functional changes that >> exist in the LTS kernel ( like 4.19 as an example), because of that I >> would like to use a more stable kernel into my starling x system >> >> Is there any specific reason why use that specific for from RHEL? >> >> What does starling X think about the migration of these patches ( some of them are already applied into the latest versions of Linux Kernel)? >> >> What kind of test should I perform to check that my vanilla kernel + STX patches work as expected? >> >> All feedback is more than welcome >> >> BTW thanks to Mario and Saul for the help on understand more these >> patches >> >> Regards >> >> Victor Rodriguez >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From cesar.lara at intel.com Wed Nov 21 21:36:29 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Wed, 21 Nov 2018 21:36:29 +0000 Subject: [Starlingx-discuss] [build][meetings]Agenda for Build team meeting 11/22/2018 Message-ID: <0B566C62EC792145B40E29EFEBF1AB471056AB69@fmsmsx104.amr.corp.intel.com> Build team meeting 11/22/2018 Agenda - Cengn follow up - Ken - Mirror script refactor - Marcela - Build team Imperatives for next release Most of us are in non-holiday areas, please let me know if there is a showstopper to host this meeting without people from USA Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From changcheng.liu at intel.com Wed Nov 21 23:04:31 2018 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Wed, 21 Nov 2018 23:04:31 +0000 Subject: [Starlingx-discuss] stx-tools: document isn't aligned with code In-Reply-To: <6594B51DBE477C48AAE23675314E6C466451F8E3@fmsmsx107.amr.corp.intel.com> References: <0D7994A90DD70040A9F5E77C4D23C57D50EF7D01@SHSMSX104.ccr.corp.intel.com>, <6594B51DBE477C48AAE23675314E6C466451F8E3@fmsmsx107.amr.corp.intel.com> Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50EF9644@SHSMSX104.ccr.corp.intel.com> I'll follow the README.rst to set up the environment again. -----Original Message----- From: Arevalo, Mario Alfredo C Sent: Thursday, November 22, 2018 12:56 AM To: Arce Moreno, Abraham ; Liu, Changcheng ; starlingx-discuss at lists.starlingx.io Subject: RE: stx-tools: document isn't aligned with code Hi Changcheng and Abraham, I have sent a new version in order to update the documentation according to the new changes in Dockerfile[s]. You can take a look in this link: https://review.openstack.org/#/c/601308/ sorry for any inconvenience. Best regards. Mario. ________________________________________ From: Arce Moreno, Abraham Sent: Wednesday, November 21, 2018 7:35 AM To: Liu, Changcheng; starlingx-discuss at lists.starlingx.io; Arevalo, Mario Alfredo C Subject: RE: stx-tools: document isn't aligned with code Hi again Changcheng, > I'm following below document to create-starlingx-packages. It's not > aligned with latest code. You are right... > https://docs.starlingx.io/developer_guide/index.html#create- > starlingx-packages > - > packages> > Could the man, who's responsible for continuous-integration, clean the > document and make it more clear? Under this review we will include the changes to align with Mario's cleanup: [Developer Guide] Setup Building Docker Container [0] The logic behind to accommodate the new "Developer Guide" flow proposal would look like: FYI "..." means content is not intended to be changed. - Requirements - ... - Development Environment Setup - ... - Prepare the Base Docker Image - Configuration - Sample localrc - Build Base Docker Image - Build the CentOS Mirror Repository - Run Mirror Docker Container - Download Packages - Verify Packages - Packages Structure - Create CentOS Mirror Repository - Create StarlingX Packages - Run Building Docker Container - Download Source Code Repositories - Build Packages - Build StarlingX ISO - Build Installer - ... - Build Avoidance - ... In summary, "flow proposal" could look like: - Prepare Base Docker Image - Build "base image" - Build the CentOS Mirror Repository - Run container from "base image" - Get mirror files - Create StarlingX Packages - Run container from "base image" - Get StarlingX source code - Build StarlingX packages - Build StarlingX ISO > 1. The stx-tools code isn't aligned with the above document since > base- build/build target has been removed. > 2. Besides this, README.rst is not updated in time when the > build rule has been changed. README.rst from stx-tools project is going under a review process [1] so please feel free to leave your comments. [0] https://review.openstack.org/#/c/619043/ [1] https://review.openstack.org/#/c/601308/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From changcheng.liu at intel.com Wed Nov 21 23:27:03 2018 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Wed, 21 Nov 2018 23:27:03 +0000 Subject: [Starlingx-discuss] stx-ceph patch commit detail: StarlingX open source release updates Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50EF968C@SHSMSX104.ccr.corp.intel.com> Hi Dean, I'm porting stx-ceph/v10.2.6 upgrade patches to be v13.2.2 There's one giant below patch submitted by you. StarlingX open source release updates https://github.com/starlingx-staging/stx-ceph/commit/3f07f7ff1a5c7bfa8d0de12c966594d5fb7cf4ec Please confirm whether the above patch is generated by below method. 1) git clone https://github.intel.com/Madawaska/download.ceph.com.rpm.jewel.el7; cd download.ceph.com.rpm.jewel.el7 2) git reset --soft db5aab71333112e1afc170b685c7599cf1f848ce 3) squash all below patches into one giant patch and applied on the code repository in 2) https://github.intel.com/Madawaska/download.ceph.com.rpm.jewel.el7/compare/db5aab713...868280aa8 4) git commit -s -m "StarlingX open source release updates" Besides that above changes, please let us know whether there're separate changes in the commit "StarlingX open source release updates". This is quiet important. B.R. Changcheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From xiaoyan.li at intel.com Thu Nov 22 00:41:26 2018 From: xiaoyan.li at intel.com (Li, Xiaoyan) Date: Thu, 22 Nov 2018 00:41:26 +0000 Subject: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching In-Reply-To: References: <2588653EBDFFA34B982FAF00F1B4844EBB25D46B@ALA-MBD.corp.ad.wrs.com> , <4C60D9C5C8176C47874FFF36647AA19E9D5F8E8F@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Brent and Ovidiu, As this email has a long history, I re-summarize the raw cache in StarlingX and Cinder upstream image cache. Please vote whether we can abandon raw cache in StarlingX. StarlingX Create an image cache in ceph when Glance creates an image. And delete the cached image in ceph when deleting the original image in Glance. Cinder: When creating a volume from an image in a backend storage at the first time, Cinder creates a volume from this image, and uses it as the image cache. So next time if users create another volume from this image in the same backend storage, Cinder at first finds out the cached image volume and clones a new volume from it. Cinder allows capacity configuration for cached images. If the space is used up, Cinder will evict the cached image volumes. >From my viewpoint, Cinder image cache can achieve same functionality as Raw cache in StarlingX with more enhancement. It is for all Cinder supported backend storage, not just for Ceph. Best wishes Lisa From: Li, Xiaoyan Sent: Monday, November 19, 2018 9:44 AM To: Poncea, Ovidiu ; Rowsell, Brent ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi Ovidiu, A cached image ( new volume from this image) is created on a storage backend when Cinder firstly creates a volume in the same backend storage from the image. All the information are stored in Cinder, including volume id, image id etc. https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/manager.py#L1368 https://github.com/openstack/cinder/blob/stable/pike/cinder/image/cache.py#L82 A cached image is deleted when the configure space for cache is used up. So currently Cinder doesn't delete the cached image volumes even if the image is deleted. But this can be an enhancement of current cinder image cache. https://github.com/openstack/cinder/blob/stable/pike/cinder/image/cache.py#L117 https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/manager.py#L1351 Best wishes Lisa From: Poncea, Ovidiu [mailto:Ovidiu.Poncea at windriver.com] Sent: Friday, November 16, 2018 4:57 PM To: Li, Xiaoyan >; Rowsell, Brent >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi Li, Quick question: Is cache going to be freed when an image is deleted from glance? It would be a waste to cache images that are no longer needed. Thanks, Ovidiu ________________________________ From: Li, Xiaoyan [xiaoyan.li at intel.com] Sent: Tuesday, November 13, 2018 9:19 AM To: Rowsell, Brent; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi, About the raw cache function in StarlingX Cinder and Glance, I would like to remove it as Cinder has similar function. Please see following detail. And if I would like to remove the function in StarlingX, there are two methods: 1. Submit a patch to revert the changes in Glance and Cinder. 2. Ignore these patches during upgrading StarlingX/Cinder to new Cinder release. Which way do we prefer to? Best wishes Lisa From: Li, Xiaoyan Sent: Thursday, September 20, 2018 10:17 AM To: Rowsell, Brent >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi, Brent The following are mechanism of Cinder volume cache. Creation of cached volume: It creates a cached volume in the backend storage when creating from an image. 1. Create_from_image: https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L890 2. Return image cache entry: If not existed, it creates a new entry. https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L746 3. Create a new image-volume and cache entry for it: https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L872 Use a cached volume when creating a volume: https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L723-L735 Delete the cache volume: When capacity and number of cache entries exceed specified limit, it deletes cache entries (cached volumes). https://github.com/openstack/cinder/blob/stable/pike/cinder/image/cache.py#L164 Best wishes Lisa From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Thursday, September 6, 2018 10:02 AM To: Li, Xiaoyan >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching We would need to review this feature to ensure it provides equivalent functionality first. If it does, great, we can look at reverting and enabling this cinder functionality. Brent From: Li, Xiaoyan [mailto:xiaoyan.li at intel.com] Sent: Wednesday, September 5, 2018 9:59 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi all, This email is about Raw caching function in StarlingX. This feature is to cache an image in backend storage like Ceph when we first create a volume in this backend storage. In fact, Cinder upstream has already had a similar function in Pike release. https://specs.openstack.org/openstack/cinder-specs/specs/liberty/image-volume-cache.html So I want to revert Raw caching function in StarlingX, and use Cinder generic image cache instead. The problem is that we need to update Cinder config in StarlingX. Any comments? Best wishes Lisa -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Thu Nov 22 00:45:26 2018 From: yong.hu at intel.com (Hu, Yong) Date: Thu, 22 Nov 2018 00:45:26 +0000 Subject: [Starlingx-discuss] stx-tools: document isn't aligned with code Message-ID: <5573DFE7-5CB4-4F6B-AA26-356AC03AB8D9@intel.com> Changcheng, I’ve recently refreshed my build environment. If you still see some problems, you can come to me. -Yong From: "Liu, Changcheng" Date: Thursday, 22 November 2018 at 7:05 AM To: "Arevalo, Mario Alfredo C" , "Arce Moreno, Abraham" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] stx-tools: document isn't aligned with code I'll follow the README.rst to set up the environment again. -----Original Message----- From: Arevalo, Mario Alfredo C Sent: Thursday, November 22, 2018 12:56 AM To: Arce Moreno, Abraham ; Liu, Changcheng ; starlingx-discuss at lists.starlingx.io Subject: RE: stx-tools: document isn't aligned with code Hi Changcheng and Abraham, I have sent a new version in order to update the documentation according to the new changes in Dockerfile[s]. You can take a look in this link: https://review.openstack.org/#/c/601308/ sorry for any inconvenience. Best regards. Mario. ________________________________________ From: Arce Moreno, Abraham Sent: Wednesday, November 21, 2018 7:35 AM To: Liu, Changcheng; starlingx-discuss at lists.starlingx.io; Arevalo, Mario Alfredo C Subject: RE: stx-tools: document isn't aligned with code Hi again Changcheng, > I’m following below document to create-starlingx-packages. It’s not > aligned with latest code. You are right... > https://docs.starlingx.io/developer_guide/index.html#create- > starlingx-packages > - > packages> > Could the man, who’s responsible for continuous-integration, clean the > document and make it more clear? Under this review we will include the changes to align with Mario's cleanup: [Developer Guide] Setup Building Docker Container [0] The logic behind to accommodate the new "Developer Guide" flow proposal would look like: FYI "..." means content is not intended to be changed. - Requirements - ... - Development Environment Setup - ... - Prepare the Base Docker Image - Configuration - Sample localrc - Build Base Docker Image - Build the CentOS Mirror Repository - Run Mirror Docker Container - Download Packages - Verify Packages - Packages Structure - Create CentOS Mirror Repository - Create StarlingX Packages - Run Building Docker Container - Download Source Code Repositories - Build Packages - Build StarlingX ISO - Build Installer - ... - Build Avoidance - ... In summary, "flow proposal" could look like: - Prepare Base Docker Image - Build "base image" - Build the CentOS Mirror Repository - Run container from "base image" - Get mirror files - Create StarlingX Packages - Run container from "base image" - Get StarlingX source code - Build StarlingX packages - Build StarlingX ISO > 1. The stx-tools code isn’t aligned with the above document since > base- build/build target has been removed. > 2. Besides this, README.rst is not updated in time when the > build rule has been changed. README.rst from stx-tools project is going under a review process [1] so please feel free to leave your comments. [0] https://review.openstack.org/#/c/619043/ [1] https://review.openstack.org/#/c/601308/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From xiaoyan.li at intel.com Thu Nov 22 00:48:46 2018 From: xiaoyan.li at intel.com (Li, Xiaoyan) Date: Thu, 22 Nov 2018 00:48:46 +0000 Subject: [Starlingx-discuss] Force deletion in Cinder Message-ID: Hi, This email is to discuss whether we can abandon 0009-Pike-Rebase-Enhanced-force-deletion.patch in StarlingX/Cinder. This patch resolves the problem that a volume is attached to a non-existed VM and can't be deleted. I talked with Openstack/Cinder community. As Cinder uses new attach/detach workflow, now this problem doesn't exist. Users can use "cinder attachment-list" to list all the attachments, and then delete them. After that, the volume can be deleted. Fang Liang also did such test, it works. So I think we can abandon this patch. Any objections? Best wishes Lisa -------------- next part -------------- An HTML attachment was scrubbed... URL: From xiaoyan.li at intel.com Thu Nov 22 00:49:54 2018 From: xiaoyan.li at intel.com (Li, Xiaoyan) Date: Thu, 22 Nov 2018 00:49:54 +0000 Subject: [Starlingx-discuss] [StarlingX] Force deletion in Cinder Message-ID: Sorry, updated the subject. _____________________________________________ From: Li, Xiaoyan Sent: Thursday, November 22, 2018 8:49 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: Force deletion in Cinder Hi, This email is to discuss whether we can abandon 0009-Pike-Rebase-Enhanced-force-deletion.patch in StarlingX/Cinder. This patch resolves the problem that a volume is attached to a non-existed VM and can't be deleted. I talked with Openstack/Cinder community. As Cinder uses new attach/detach workflow, now this problem doesn't exist. Users can use "cinder attachment-list" to list all the attachments, and then delete them. After that, the volume can be deleted. Fang Liang also did such test, it works. So I think we can abandon this patch. Any objections? Best wishes Lisa -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Thu Nov 22 01:09:52 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 22 Nov 2018 01:09:52 +0000 Subject: [Starlingx-discuss] question about create-var-run-resource-agents.patch in cluster-resource-agent In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA3F0F92@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C765FE3D93F@SHSMSX101.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA3F0F92@ALA-MBD.corp.ad.wrs.com> Message-ID: <9700A18779F35F49AF027300A49E7C765FE3DCD5@SHSMSX101.ccr.corp.intel.com> Hi Penny, Thanks for the explanation. This issue is tracked in link [0]. And is already fixed in "resource-agents-3.9.5-116". Our current version already contains the fix. So we could drop the patch safely. [0]: https://bugzilla.redhat.com/show_bug.cgi?id=1462802 Best Regards Shuicheng From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Wednesday, November 21, 2018 10:37 PM To: Lin, Shuicheng ; Little, Scott ; Rowsell, Brent Cc: starlingx-discuss at lists.starlingx.io Subject: RE: question about create-var-run-resource-agents.patch in cluster-resource-agent We can't do this in a spec file, as /var/run is on tmpfs, so the dir would be lost on the subsequent reboot. But we do have the following: controller-0:~$ rpm -qf /usr/lib/tmpfiles.d/resource-agents.conf resource-agents-3.9.5-124.el7.tis.12.x86_64 controller-0:~$ cat /usr/lib/tmpfiles.d/resource-agents.conf d /var/run/resource-agents/ 1755 root root So we could probably drop patch [1] and safely rely on the tmpfiles.d to create it. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Tuesday, November 20, 2018 11:51 PM To: Little, Scott; Penney, Don; Rowsell, Brent Cc: starlingx-discuss at lists.starlingx.io Subject: question about create-var-run-resource-agents.patch in cluster-resource-agent Hi Scott/Penney, I am looking at story [0], which want to remove patches [1] for create directory /var/run/resource-agents. And I find another patch [2] disabled explicit requires the directory in spec file. (#%dir %attr (1755, root, root) %{_var}/run/resource-agents) Could you share me the history of patch [1] and [2]? I prefer to add back this line in patch [2], and patch [1] could be removed without puppet replacement. What's your suggestion? Thanks. [0]: https://storyboard.openstack.org/#!/story/2004019 [1]: https://git.openstack.org/cgit/openstack/stx-integ/tree/base/cluster-resource-agents/centos/patches/create-var-run-resource-agents.patch [2]: https://git.openstack.org/cgit/openstack/stx-integ/tree/base/cluster-resource-agents/centos/meta_patches/spec-avoid-dir-collisions.patch Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From liang.a.fang at intel.com Thu Nov 22 01:26:14 2018 From: liang.a.fang at intel.com (Fang, Liang A) Date: Thu, 22 Nov 2018 01:26:14 +0000 Subject: [Starlingx-discuss] [StarlingX] Force deletion in Cinder In-Reply-To: References: Message-ID: Hi Lisa The core Eric Harney from redhat has already abandoned the review of this patch. In the meanwhile, a bug for horizon was created: https://bugs.launchpad.net/horizon/+bug/1794661 Regards Liang From: Li, Xiaoyan [mailto:xiaoyan.li at intel.com] Sent: Thursday, November 22, 2018 8:50 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] [StarlingX] Force deletion in Cinder Sorry, updated the subject. _____________________________________________ From: Li, Xiaoyan Sent: Thursday, November 22, 2018 8:49 AM To: 'starlingx-discuss at lists.starlingx.io' > Subject: Force deletion in Cinder Hi, This email is to discuss whether we can abandon 0009-Pike-Rebase-Enhanced-force-deletion.patch in StarlingX/Cinder. This patch resolves the problem that a volume is attached to a non-existed VM and can't be deleted. I talked with Openstack/Cinder community. As Cinder uses new attach/detach workflow, now this problem doesn't exist. Users can use "cinder attachment-list" to list all the attachments, and then delete them. After that, the volume can be deleted. Fang Liang also did such test, it works. So I think we can abandon this patch. Any objections? Best wishes Lisa -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Thu Nov 22 02:57:33 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Thu, 22 Nov 2018 02:57:33 +0000 Subject: [Starlingx-discuss] [StarlingX] Force deletion in Cinder In-Reply-To: References: Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB31B5DF@ALA-MBD.corp.ad.wrs.com> Hi Liang, Can you explain the relationship to horizon. The patches address an issue where cinder still believes the volume is attached to a VM but the VM no longer exists. II am not seeing the horizon connection here. Brent From: Fang, Liang A [mailto:liang.a.fang at intel.com] Sent: Wednesday, November 21, 2018 8:26 PM To: Li, Xiaoyan ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] [StarlingX] Force deletion in Cinder Hi Lisa The core Eric Harney from redhat has already abandoned the review of this patch. In the meanwhile, a bug for horizon was created: https://bugs.launchpad.net/horizon/+bug/1794661 Regards Liang From: Li, Xiaoyan [mailto:xiaoyan.li at intel.com] Sent: Thursday, November 22, 2018 8:50 AM To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] [StarlingX] Force deletion in Cinder Sorry, updated the subject. _____________________________________________ From: Li, Xiaoyan Sent: Thursday, November 22, 2018 8:49 AM To: 'starlingx-discuss at lists.starlingx.io' > Subject: Force deletion in Cinder Hi, This email is to discuss whether we can abandon 0009-Pike-Rebase-Enhanced-force-deletion.patch in StarlingX/Cinder. This patch resolves the problem that a volume is attached to a non-existed VM and can't be deleted. I talked with Openstack/Cinder community. As Cinder uses new attach/detach workflow, now this problem doesn't exist. Users can use "cinder attachment-list" to list all the attachments, and then delete them. After that, the volume can be deleted. Fang Liang also did such test, it works. So I think we can abandon this patch. Any objections? Best wishes Lisa -------------- next part -------------- An HTML attachment was scrubbed... URL: From liang.a.fang at intel.com Thu Nov 22 03:45:53 2018 From: liang.a.fang at intel.com (Fang, Liang A) Date: Thu, 22 Nov 2018 03:45:53 +0000 Subject: [Starlingx-discuss] [StarlingX] Force deletion in Cinder In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB31B5DF@ALA-MBD.corp.ad.wrs.com> References: <2588653EBDFFA34B982FAF00F1B4844EBB31B5DF@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Brent The bug reported to horizon is: When user try to remove the attachment by click the button "Manage Attachments" for the orphan volume, GUI just shows: "Error: Unable to retrieve volume information. ", and cannot open the "Manage Attachments" dialog. Regards Liang From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Thursday, November 22, 2018 10:58 AM To: Fang, Liang A ; Li, Xiaoyan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] [StarlingX] Force deletion in Cinder Hi Liang, Can you explain the relationship to horizon. The patches address an issue where cinder still believes the volume is attached to a VM but the VM no longer exists. II am not seeing the horizon connection here. Brent From: Fang, Liang A [mailto:liang.a.fang at intel.com] Sent: Wednesday, November 21, 2018 8:26 PM To: Li, Xiaoyan >; 'starlingx-discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] [StarlingX] Force deletion in Cinder Hi Lisa The core Eric Harney from redhat has already abandoned the review of this patch. In the meanwhile, a bug for horizon was created: https://bugs.launchpad.net/horizon/+bug/1794661 Regards Liang From: Li, Xiaoyan [mailto:xiaoyan.li at intel.com] Sent: Thursday, November 22, 2018 8:50 AM To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] [StarlingX] Force deletion in Cinder Sorry, updated the subject. _____________________________________________ From: Li, Xiaoyan Sent: Thursday, November 22, 2018 8:49 AM To: 'starlingx-discuss at lists.starlingx.io' > Subject: Force deletion in Cinder Hi, This email is to discuss whether we can abandon 0009-Pike-Rebase-Enhanced-force-deletion.patch in StarlingX/Cinder. This patch resolves the problem that a volume is attached to a non-existed VM and can't be deleted. I talked with Openstack/Cinder community. As Cinder uses new attach/detach workflow, now this problem doesn't exist. Users can use "cinder attachment-list" to list all the attachments, and then delete them. After that, the volume can be deleted. Fang Liang also did such test, it works. So I think we can abandon this patch. Any objections? Best wishes Lisa -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Thu Nov 22 05:46:27 2018 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 22 Nov 2018 05:46:27 +0000 Subject: [Starlingx-discuss] Support IBRS cpu model. In-Reply-To: References: Message-ID: Hi Chris: Very appreciate your review The new PRs are https://github.com/starlingx-staging/stx-nova/pull/17 https://github.com/starlingx-staging/stx-glance/pull/5 Thanks. BR Austin Sun. -----Original Message----- From: Chris Friesen [mailto:chris.friesen at windriver.com] Sent: Wednesday, November 21, 2018 11:41 PM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Support IBRS cpu model. On 11/16/2018 8:59 PM, Sun, Austin wrote: > Hi Chris: > Thanks your review. I have made new patch [1] based on your suggestion. Could you help review it again ? > > https://github.com/austinsun/stx-nova/commit/3255facb16b70b138ff122438 > 22b43d1824f6890#diff-6955c78b8a0da8ec1cbf33c3834de1e0 The code looks okay, the git commit message looks like it was partially duplicated. Chris From shuicheng.lin at intel.com Thu Nov 22 07:35:29 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 22 Nov 2018 07:35:29 +0000 Subject: [Starlingx-discuss] build broken with mtce-guest failure in stx-nfv Message-ID: <9700A18779F35F49AF027300A49E7C765FE3DD89@SHSMSX101.ccr.corp.intel.com> Hi, I synced latest code today, and meet build failure with mtce-guest in stx-nfv. Here is the error message in the build log: BUILDSTDERR: guestServer.cpp: In function 'int _config_handler(void*, const char*, const char*, const char*)': BUILDSTDERR: guestServer.cpp:140:21: error: 'struct daemon_config_type' has no member named 'hbs_pulse_period' BUILDSTDERR: config_ptr->hbs_pulse_period = atoi(value); BUILDSTDERR: ^ It seems it is relate with patch [0], which removed "hbs_pulse_period". I have created LP issue [1]. Could anybody familiar with it help fix it? Thanks. [0]: https://review.openstack.org/617835 [1]: https://bugs.launchpad.net/starlingx/+bug/1804579 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From changcheng.liu at intel.com Thu Nov 22 08:50:02 2018 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Thu, 22 Nov 2018 08:50:02 +0000 Subject: [Starlingx-discuss] stx-tools: document isn't aligned with code In-Reply-To: <5573DFE7-5CB4-4F6B-AA26-356AC03AB8D9@intel.com> References: <5573DFE7-5CB4-4F6B-AA26-356AC03AB8D9@intel.com> Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50EFA8EB@SHSMSX104.ccr.corp.intel.com> Hi Yong, Thanks for your hands up. (Sorry for late reply) I’m using Erich’s method to setup the environment again. I’ll look you for help if I still fail to set up the environment this time. --Thanks Changcheng From: Hu, Yong Sent: Thursday, November 22, 2018 8:45 AM To: Liu, Changcheng ; Arevalo, Mario Alfredo C ; Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] stx-tools: document isn't aligned with code Changcheng, I’ve recently refreshed my build environment. If you still see some problems, you can come to me. -Yong From: "Liu, Changcheng" > Date: Thursday, 22 November 2018 at 7:05 AM To: "Arevalo, Mario Alfredo C" >, "Arce Moreno, Abraham" >, "starlingx-discuss at lists.starlingx.io" > Subject: Re: [Starlingx-discuss] stx-tools: document isn't aligned with code I'll follow the README.rst to set up the environment again. -----Original Message----- From: Arevalo, Mario Alfredo C Sent: Thursday, November 22, 2018 12:56 AM To: Arce Moreno, Abraham >; Liu, Changcheng >; starlingx-discuss at lists.starlingx.io Subject: RE: stx-tools: document isn't aligned with code Hi Changcheng and Abraham, I have sent a new version in order to update the documentation according to the new changes in Dockerfile[s]. You can take a look in this link: https://review.openstack.org/#/c/601308/ sorry for any inconvenience. Best regards. Mario. ________________________________________ From: Arce Moreno, Abraham Sent: Wednesday, November 21, 2018 7:35 AM To: Liu, Changcheng; starlingx-discuss at lists.starlingx.io; Arevalo, Mario Alfredo C Subject: RE: stx-tools: document isn't aligned with code Hi again Changcheng, > I’m following below document to create-starlingx-packages. It’s not > aligned with latest code. You are right... > https://docs.starlingx.io/developer_guide/index.html#create- > starlingx-packages > - > packages> > Could the man, who’s responsible for continuous-integration, clean the > document and make it more clear? Under this review we will include the changes to align with Mario's cleanup: [Developer Guide] Setup Building Docker Container [0] The logic behind to accommodate the new "Developer Guide" flow proposal would look like: FYI "..." means content is not intended to be changed. - Requirements - ... - Development Environment Setup - ... - Prepare the Base Docker Image - Configuration - Sample localrc - Build Base Docker Image - Build the CentOS Mirror Repository - Run Mirror Docker Container - Download Packages - Verify Packages - Packages Structure - Create CentOS Mirror Repository - Create StarlingX Packages - Run Building Docker Container - Download Source Code Repositories - Build Packages - Build StarlingX ISO - Build Installer - ... - Build Avoidance - ... In summary, "flow proposal" could look like: - Prepare Base Docker Image - Build "base image" - Build the CentOS Mirror Repository - Run container from "base image" - Get mirror files - Create StarlingX Packages - Run container from "base image" - Get StarlingX source code - Build StarlingX packages - Build StarlingX ISO > 1. The stx-tools code isn’t aligned with the above document since > base- build/build target has been removed. > 2. Besides this, README.rst is not updated in time when the > build rule has been changed. README.rst from stx-tools project is going under a review process [1] so please feel free to leave your comments. [0] https://review.openstack.org/#/c/619043/ [1] https://review.openstack.org/#/c/601308/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jim.Einarsson at windriver.com Thu Nov 22 15:06:39 2018 From: Jim.Einarsson at windriver.com (Einarsson, Jim) Date: Thu, 22 Nov 2018 15:06:39 +0000 Subject: [Starlingx-discuss] 3. Re: Migrate Starling X kernel patches to LTS kernel (Saul Wold) Message-ID: <38713B7817E1A049AB469EA7F6EEF69EBBFD7007@ALA-MBD.corp.ad.wrs.com> Saul, We have no objections to your investigation of a kernel up version, but the forklift may be heavier than you realize. Certainly considerable work needs to be done to validate both functionality and performance aspects. I assume the investigation will happen in a sandbox side stream, to avoid disruption to the main branch. I highly recommend a spec be created and reviewed, to make sure all the necessary angles of the investigation are covered. JimE. Message: 3 Date: Wed, 21 Nov 2018 09:10:47 -0800 From: Saul Wold To: Victor Rodriguez , Brent.Rowsell at windriver.com Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Migrate Starling X kernel patches to LTS kernel Message-ID: Content-Type: text/plain; charset=utf-8; format=flowed Victor, Brent: There are a couple of things not mentioned that I have heard talked about on both sides of this discussion. My understanding is that the kernel version is based on the RHEL/CentOS version as it's a known tested combination at the Distro level, even though there are patches to the kernel and user-space. On the other side, the 3.10 RHEL kernel (with all the RHEL patches) may not address all the known CVEs, so there is a concern about overall security. Intel is looking at the newer kernel and porting the StarlingX patches (as needed) for the Clear and Multi-OS parts of the project. The overall question becomes can StarlingX take the 4.19LTS kernel as a newer base kernel for the project, it reduces the overall patch load and address some security issues. I believe you understand these objectives. Sau! -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io [mailto:starlingx-discuss-request at lists.starlingx.io] Sent: Wednesday, November 21, 2018 4:37 PM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 6, Issue 70 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. StarlingX mini-PTG Jan 15-16 in Phoenix (Jones, Bruce E) 2. Re: stx-tools: document isn't aligned with code (Arevalo, Mario Alfredo C) 3. Re: Migrate Starling X kernel patches to LTS kernel (Saul Wold) 4. Re: Migrate Starling X kernel patches to LTS kernel (Rowsell, Brent) 5. [build][meetings]Agenda for Build team meeting 11/22/2018 (Lara, Cesar) ---------------------------------------------------------------------- Message: 1 Date: Wed, 21 Nov 2018 16:26:43 +0000 From: "Jones, Bruce E" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] StarlingX mini-PTG Jan 15-16 in Phoenix Message-ID: <9A85D2917C58154C960D95352B22818BB1EB0050 at fmsmsx115.amr.corp.intel.com> Content-Type: text/plain; charset="utf-8" We are thinking about holding a StarlingX mini-PTG meeting in January in Phoenix, to be hosted on the Intel campus. I'd like to get an early headcount and make sure there are no conflicts for the dates. Please reply to this email and let me know if you can/want to attend, or if you would like to attend but have a conflict for these dates. Thank you! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 2 Date: Wed, 21 Nov 2018 16:55:39 +0000 From: "Arevalo, Mario Alfredo C" To: "Arce Moreno, Abraham" , "Liu, Changcheng" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] stx-tools: document isn't aligned with code Message-ID: <6594B51DBE477C48AAE23675314E6C466451F8E3 at fmsmsx107.amr.corp.intel.com> Content-Type: text/plain; charset="Windows-1252" Hi Changcheng and Abraham, I have sent a new version in order to update the documentation according to the new changes in Dockerfile[s]. You can take a look in this link: https://review.openstack.org/#/c/601308/ sorry for any inconvenience. Best regards. Mario. ________________________________________ From: Arce Moreno, Abraham Sent: Wednesday, November 21, 2018 7:35 AM To: Liu, Changcheng; starlingx-discuss at lists.starlingx.io; Arevalo, Mario Alfredo C Subject: RE: stx-tools: document isn't aligned with code Hi again Changcheng, > I’m following below document to create-starlingx-packages. It’s not > aligned with latest code. You are right... > https://docs.starlingx.io/developer_guide/index.html#create- > starlingx-packages > packages> > Could the man, who’s responsible for continuous-integration, clean the > document and make it more clear? Under this review we will include the changes to align with Mario's cleanup: [Developer Guide] Setup Building Docker Container [0] The logic behind to accommodate the new "Developer Guide" flow proposal would look like: FYI "..." means content is not intended to be changed. - Requirements - ... - Development Environment Setup - ... - Prepare the Base Docker Image - Configuration - Sample localrc - Build Base Docker Image - Build the CentOS Mirror Repository - Run Mirror Docker Container - Download Packages - Verify Packages - Packages Structure - Create CentOS Mirror Repository - Create StarlingX Packages - Run Building Docker Container - Download Source Code Repositories - Build Packages - Build StarlingX ISO - Build Installer - ... - Build Avoidance - ... In summary, "flow proposal" could look like: - Prepare Base Docker Image - Build "base image" - Build the CentOS Mirror Repository - Run container from "base image" - Get mirror files - Create StarlingX Packages - Run container from "base image" - Get StarlingX source code - Build StarlingX packages - Build StarlingX ISO > 1. The stx-tools code isn’t aligned with the above document since base- > build/build target has been removed. > 2. Besides this, README.rst is not updated in time when the build rule > has been changed. README.rst from stx-tools project is going under a review process [1] so please feel free to leave your comments. [0] https://review.openstack.org/#/c/619043/ [1] https://review.openstack.org/#/c/601308/ ------------------------------ Message: 3 Date: Wed, 21 Nov 2018 09:10:47 -0800 From: Saul Wold To: Victor Rodriguez , Brent.Rowsell at windriver.com Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Migrate Starling X kernel patches to LTS kernel Message-ID: Content-Type: text/plain; charset=utf-8; format=flowed Victor, Brent: There are a couple of things not mentioned that I have heard talked about on both sides of this discussion. My understanding is that the kernel version is based on the RHEL/CentOS version as it's a known tested combination at the Distro level, even though there are patches to the kernel and user-space. On the other side, the 3.10 RHEL kernel (with all the RHEL patches) may not address all the known CVEs, so there is a concern about overall security. Intel is looking at the newer kernel and porting the StarlingX patches (as needed) for the Clear and Multi-OS parts of the project. The overall question becomes can StarlingX take the 4.19LTS kernel as a newer base kernel for the project, it reduces the overall patch load and address some security issues. I believe you understand these objectives. Sau! On 11/20/18 6:42 PM, Victor Rodriguez wrote: > On Tue, Nov 20, 2018 at 8:25 PM Rowsell, Brent > wrote: >> >> There are two kernels, standard and rt. >> Both are centos 7.5 based with a small set of patches applied on top along with modified kernel config options. >> > > Thanks for the clarification > >> Not quite understanding what you are asking. Are you proposing to replace the kernel in the starlingX project or just in your local environment ? > > For my local environment. I would not like to use CentOS kernel 3.10 > but instead LTS 4.19 > >> What is the objective here ? > > To have a more stable and secure kernel on my production system, there > are security fixes that would like to have on my kernel that LTS > provides > > I know RHEL/CentOS is based on kernel 3.10 but other OSs are ot like > ubuntu/debian/fedora > > Regards > >> >> Brent >> >> -----Original Message----- >> From: Victor Rodriguez [mailto:vm.rod25 at gmail.com] >> Sent: Tuesday, November 20, 2018 9:20 PM >> To: starlingx-discuss at lists.starlingx.io >> Subject: [Starlingx-discuss] Migrate Starling X kernel patches to LTS kernel >> >> Hi team >> >> I am a new user/developer of starling X and after searching into the kernel metapatches at: >> >> https://git.starlingx.io/cgit/stx-integ/tree/kernel >> >> Some questions came to me : >> >> As far as I can see we are under kernel 3.10 from RHEL RT fork right? >> There are some ( actually many ) security and functional changes that exist in the LTS kernel ( like 4.19 as an example), because of that I would like to use a more stable kernel into my starling x system >> >> Is there any specific reason why use that specific for from RHEL? >> >> What does starling X think about the migration of these patches ( some of them are already applied into the latest versions of Linux Kernel)? >> >> What kind of test should I perform to check that my vanilla kernel + STX patches work as expected? >> >> All feedback is more than welcome >> >> BTW thanks to Mario and Saul for the help on understand more these patches >> >> Regards >> >> Victor Rodriguez >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > ------------------------------ Message: 4 Date: Wed, 21 Nov 2018 17:21:49 +0000 From: "Rowsell, Brent" To: Saul Wold , Victor Rodriguez Cc: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Migrate Starling X kernel patches to LTS kernel Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB31A592 at ALA-MBD.corp.ad.wrs.com> Content-Type: text/plain; charset="utf-8" Saul, This is a big change. I suggest adding it to the next TSC call. Brent -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Wednesday, November 21, 2018 12:11 PM To: Victor Rodriguez ; Rowsell, Brent Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Migrate Starling X kernel patches to LTS kernel Victor, Brent: There are a couple of things not mentioned that I have heard talked about on both sides of this discussion. My understanding is that the kernel version is based on the RHEL/CentOS version as it's a known tested combination at the Distro level, even though there are patches to the kernel and user-space. On the other side, the 3.10 RHEL kernel (with all the RHEL patches) may not address all the known CVEs, so there is a concern about overall security. Intel is looking at the newer kernel and porting the StarlingX patches (as needed) for the Clear and Multi-OS parts of the project. The overall question becomes can StarlingX take the 4.19LTS kernel as a newer base kernel for the project, it reduces the overall patch load and address some security issues. I believe you understand these objectives. Sau! On 11/20/18 6:42 PM, Victor Rodriguez wrote: > On Tue, Nov 20, 2018 at 8:25 PM Rowsell, Brent > wrote: >> >> There are two kernels, standard and rt. >> Both are centos 7.5 based with a small set of patches applied on top along with modified kernel config options. >> > > Thanks for the clarification > >> Not quite understanding what you are asking. Are you proposing to replace the kernel in the starlingX project or just in your local environment ? > > For my local environment. I would not like to use CentOS kernel 3.10 > but instead LTS 4.19 > >> What is the objective here ? > > To have a more stable and secure kernel on my production system, there > are security fixes that would like to have on my kernel that LTS > provides > > I know RHEL/CentOS is based on kernel 3.10 but other OSs are ot like > ubuntu/debian/fedora > > Regards > >> >> Brent >> >> -----Original Message----- >> From: Victor Rodriguez [mailto:vm.rod25 at gmail.com] >> Sent: Tuesday, November 20, 2018 9:20 PM >> To: starlingx-discuss at lists.starlingx.io >> Subject: [Starlingx-discuss] Migrate Starling X kernel patches to LTS >> kernel >> >> Hi team >> >> I am a new user/developer of starling X and after searching into the kernel metapatches at: >> >> https://git.starlingx.io/cgit/stx-integ/tree/kernel >> >> Some questions came to me : >> >> As far as I can see we are under kernel 3.10 from RHEL RT fork right? >> There are some ( actually many ) security and functional changes that >> exist in the LTS kernel ( like 4.19 as an example), because of that I >> would like to use a more stable kernel into my starling x system >> >> Is there any specific reason why use that specific for from RHEL? >> >> What does starling X think about the migration of these patches ( some of them are already applied into the latest versions of Linux Kernel)? >> >> What kind of test should I perform to check that my vanilla kernel + STX patches work as expected? >> >> All feedback is more than welcome >> >> BTW thanks to Mario and Saul for the help on understand more these >> patches >> >> Regards >> >> Victor Rodriguez >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > ------------------------------ Message: 5 Date: Wed, 21 Nov 2018 21:36:29 +0000 From: "Lara, Cesar" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] [build][meetings]Agenda for Build team meeting 11/22/2018 Message-ID: <0B566C62EC792145B40E29EFEBF1AB471056AB69 at fmsmsx104.amr.corp.intel.com> Content-Type: text/plain; charset="utf-8" Build team meeting 11/22/2018 Agenda - Cengn follow up - Ken - Mirror script refactor - Marcela - Build team Imperatives for next release Most of us are in non-holiday areas, please let me know if there is a showstopper to host this meeting without people from USA Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 6, Issue 70 ************************************************ From Ghada.Khalil at windriver.com Thu Nov 22 15:41:10 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 22 Nov 2018 15:41:10 +0000 Subject: [Starlingx-discuss] build broken with mtce-guest failure in stx-nfv In-Reply-To: <9700A18779F35F49AF027300A49E7C765FE3DD89@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C765FE3DD89@SHSMSX101.ccr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA486370@ALA-MBD.corp.ad.wrs.com> Eric MacDonald is working on a fix. The Launchpad has been assigned to him. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, November 22, 2018 2:35 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] build broken with mtce-guest failure in stx-nfv Hi, I synced latest code today, and meet build failure with mtce-guest in stx-nfv. Here is the error message in the build log: BUILDSTDERR: guestServer.cpp: In function 'int _config_handler(void*, const char*, const char*, const char*)': BUILDSTDERR: guestServer.cpp:140:21: error: 'struct daemon_config_type' has no member named 'hbs_pulse_period' BUILDSTDERR: config_ptr->hbs_pulse_period = atoi(value); BUILDSTDERR: ^ It seems it is relate with patch [0], which removed "hbs_pulse_period". I have created LP issue [1]. Could anybody familiar with it help fix it? Thanks. [0]: https://review.openstack.org/617835 [1]: https://bugs.launchpad.net/starlingx/+bug/1804579 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Thu Nov 22 16:02:11 2018 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 22 Nov 2018 08:02:11 -0800 Subject: [Starlingx-discuss] 3. Re: Migrate Starling X kernel patches to LTS kernel (Saul Wold) In-Reply-To: <38713B7817E1A049AB469EA7F6EEF69EBBFD7007@ALA-MBD.corp.ad.wrs.com> References: <38713B7817E1A049AB469EA7F6EEF69EBBFD7007@ALA-MBD.corp.ad.wrs.com> Message-ID: On 11/22/18 7:06 AM, Einarsson, Jim wrote: > Saul, > We have no objections to your investigation of a kernel up version, but the forklift may be heavier than you realize. Certainly considerable work needs to be done to validate both functionality and performance aspects. I assume the investigation will happen in a sandbox side stream, to avoid disruption to the main branch. I highly recommend a spec be created and reviewed, to make sure all the necessary angles of the investigation are covered. > Exactly, we need to start this work for the Clear port we are currently doing and it will also need to be done as part of the Multi-OS effort since Ubuntu has a newer kernel. I am not proposing this happen on CentOS / master at this time, we know there is a large amount of work the forklift the patches, that work is already started against the 4.19 LTS kernel internally at Intel. We will work on a spec and address testing of the kernel. Sau! > JimE. > > Message: 3 > Date: Wed, 21 Nov 2018 09:10:47 -0800 > From: Saul Wold > To: Victor Rodriguez , Brent.Rowsell at windriver.com > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Migrate Starling X kernel patches to > LTS kernel > Message-ID: > Content-Type: text/plain; charset=utf-8; format=flowed > > Victor, Brent: > > There are a couple of things not mentioned that I have heard talked > about on both sides of this discussion. > > My understanding is that the kernel version is based on the RHEL/CentOS > version as it's a known tested combination at the Distro level, even > though there are patches to the kernel and user-space. > > On the other side, the 3.10 RHEL kernel (with all the RHEL patches) may > not address all the known CVEs, so there is a concern about overall > security. Intel is looking at the newer kernel and porting the > StarlingX patches (as needed) for the Clear and Multi-OS parts of the > project. > > The overall question becomes can StarlingX take the 4.19LTS kernel as a > newer base kernel for the project, it reduces the overall patch load and > address some security issues. > > I believe you understand these objectives. > > Sau! > > -----Original Message----- > From: starlingx-discuss-request at lists.starlingx.io [mailto:starlingx-discuss-request at lists.starlingx.io] > Sent: Wednesday, November 21, 2018 4:37 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Starlingx-discuss Digest, Vol 6, Issue 70 > > Send Starlingx-discuss mailing list submissions to > starlingx-discuss at lists.starlingx.io > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > or, via email, send a message with subject or body 'help' to > starlingx-discuss-request at lists.starlingx.io > > You can reach the person managing the list at > starlingx-discuss-owner at lists.starlingx.io > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Starlingx-discuss digest..." > > > Today's Topics: > > 1. StarlingX mini-PTG Jan 15-16 in Phoenix (Jones, Bruce E) > 2. Re: stx-tools: document isn't aligned with code > (Arevalo, Mario Alfredo C) > 3. Re: Migrate Starling X kernel patches to LTS kernel (Saul Wold) > 4. Re: Migrate Starling X kernel patches to LTS kernel > (Rowsell, Brent) > 5. [build][meetings]Agenda for Build team meeting 11/22/2018 > (Lara, Cesar) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 21 Nov 2018 16:26:43 +0000 > From: "Jones, Bruce E" > To: "starlingx-discuss at lists.starlingx.io" > > Subject: [Starlingx-discuss] StarlingX mini-PTG Jan 15-16 in Phoenix > Message-ID: > <9A85D2917C58154C960D95352B22818BB1EB0050 at fmsmsx115.amr.corp.intel.com> > > Content-Type: text/plain; charset="utf-8" > > We are thinking about holding a StarlingX mini-PTG meeting in January in Phoenix, to be hosted on the Intel campus. > > I'd like to get an early headcount and make sure there are no conflicts for the dates. Please reply to this email and let me know if you can/want to attend, or if you would like to attend but have a conflict for these dates. > > Thank you! > > brucej > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > ------------------------------ > > Message: 2 > Date: Wed, 21 Nov 2018 16:55:39 +0000 > From: "Arevalo, Mario Alfredo C" > To: "Arce Moreno, Abraham" , "Liu, > Changcheng" , > "starlingx-discuss at lists.starlingx.io" > > Subject: Re: [Starlingx-discuss] stx-tools: document isn't aligned > with code > Message-ID: > <6594B51DBE477C48AAE23675314E6C466451F8E3 at fmsmsx107.amr.corp.intel.com> > > Content-Type: text/plain; charset="Windows-1252" > > Hi Changcheng and Abraham, > > I have sent a new version in order to update the documentation according > to the new changes in Dockerfile[s]. You can take a look in this link: > > https://review.openstack.org/#/c/601308/ > > sorry for any inconvenience. > > Best regards. > Mario. > ________________________________________ > From: Arce Moreno, Abraham > Sent: Wednesday, November 21, 2018 7:35 AM > To: Liu, Changcheng; starlingx-discuss at lists.starlingx.io; Arevalo, Mario Alfredo C > Subject: RE: stx-tools: document isn't aligned with code > > Hi again Changcheng, > >> I’m following below document to create-starlingx-packages. It’s not >> aligned with latest code. > > You are right... > >> https://docs.starlingx.io/developer_guide/index.html#create- >> starlingx-packages >> > packages> >> Could the man, who’s responsible for continuous-integration, clean the >> document and make it more clear? > > Under this review we will include the changes to align with Mario's cleanup: > [Developer Guide] Setup Building Docker Container [0] > > The logic behind to accommodate the new "Developer Guide" flow proposal > would look like: > > FYI "..." means content is not intended to be changed. > > - Requirements > - ... > - Development Environment Setup > - ... > - Prepare the Base Docker Image > - Configuration > - Sample localrc > - Build Base Docker Image > - Build the CentOS Mirror Repository > - Run Mirror Docker Container > - Download Packages > - Verify Packages > - Packages Structure > - Create CentOS Mirror Repository > - Create StarlingX Packages > - Run Building Docker Container > - Download Source Code Repositories > - Build Packages > - Build StarlingX ISO > - Build Installer > - ... > - Build Avoidance > - ... > > In summary, "flow proposal" could look like: > > - Prepare Base Docker Image > - Build "base image" > - Build the CentOS Mirror Repository > - Run container from "base image" > - Get mirror files > - Create StarlingX Packages > - Run container from "base image" > - Get StarlingX source code > - Build StarlingX packages > - Build StarlingX ISO > >> 1. The stx-tools code isn’t aligned with the above document since base- >> build/build target has been removed. >> 2. Besides this, README.rst is not updated in time when the build rule >> has been changed. > > README.rst from stx-tools project is going under a review process [1] so please > feel free to leave your comments. > > [0] https://review.openstack.org/#/c/619043/ > [1] https://review.openstack.org/#/c/601308/ > > > > ------------------------------ > > Message: 3 > Date: Wed, 21 Nov 2018 09:10:47 -0800 > From: Saul Wold > To: Victor Rodriguez , Brent.Rowsell at windriver.com > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Migrate Starling X kernel patches to > LTS kernel > Message-ID: > Content-Type: text/plain; charset=utf-8; format=flowed > > Victor, Brent: > > There are a couple of things not mentioned that I have heard talked > about on both sides of this discussion. > > My understanding is that the kernel version is based on the RHEL/CentOS > version as it's a known tested combination at the Distro level, even > though there are patches to the kernel and user-space. > > On the other side, the 3.10 RHEL kernel (with all the RHEL patches) may > not address all the known CVEs, so there is a concern about overall > security. Intel is looking at the newer kernel and porting the > StarlingX patches (as needed) for the Clear and Multi-OS parts of the > project. > > The overall question becomes can StarlingX take the 4.19LTS kernel as a > newer base kernel for the project, it reduces the overall patch load and > address some security issues. > > I believe you understand these objectives. > > Sau! > > > On 11/20/18 6:42 PM, Victor Rodriguez wrote: >> On Tue, Nov 20, 2018 at 8:25 PM Rowsell, Brent >> wrote: >>> >>> There are two kernels, standard and rt. >>> Both are centos 7.5 based with a small set of patches applied on top along with modified kernel config options. >>> >> >> Thanks for the clarification >> >>> Not quite understanding what you are asking. Are you proposing to replace the kernel in the starlingX project or just in your local environment ? >> >> For my local environment. I would not like to use CentOS kernel 3.10 >> but instead LTS 4.19 >> >>> What is the objective here ? >> >> To have a more stable and secure kernel on my production system, there >> are security fixes that would like to have on my kernel that LTS >> provides >> >> I know RHEL/CentOS is based on kernel 3.10 but other OSs are ot like >> ubuntu/debian/fedora >> >> Regards >> >>> >>> Brent >>> >>> -----Original Message----- >>> From: Victor Rodriguez [mailto:vm.rod25 at gmail.com] >>> Sent: Tuesday, November 20, 2018 9:20 PM >>> To: starlingx-discuss at lists.starlingx.io >>> Subject: [Starlingx-discuss] Migrate Starling X kernel patches to LTS kernel >>> >>> Hi team >>> >>> I am a new user/developer of starling X and after searching into the kernel metapatches at: >>> >>> https://git.starlingx.io/cgit/stx-integ/tree/kernel >>> >>> Some questions came to me : >>> >>> As far as I can see we are under kernel 3.10 from RHEL RT fork right? >>> There are some ( actually many ) security and functional changes that exist in the LTS kernel ( like 4.19 as an example), because of that I would like to use a more stable kernel into my starling x system >>> >>> Is there any specific reason why use that specific for from RHEL? >>> >>> What does starling X think about the migration of these patches ( some of them are already applied into the latest versions of Linux Kernel)? >>> >>> What kind of test should I perform to check that my vanilla kernel + STX patches work as expected? >>> >>> All feedback is more than welcome >>> >>> BTW thanks to Mario and Saul for the help on understand more these patches >>> >>> Regards >>> >>> Victor Rodriguez >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > > > ------------------------------ > > Message: 4 > Date: Wed, 21 Nov 2018 17:21:49 +0000 > From: "Rowsell, Brent" > To: Saul Wold , Victor Rodriguez > > Cc: "starlingx-discuss at lists.starlingx.io" > > Subject: Re: [Starlingx-discuss] Migrate Starling X kernel patches to > LTS kernel > Message-ID: > <2588653EBDFFA34B982FAF00F1B4844EBB31A592 at ALA-MBD.corp.ad.wrs.com> > Content-Type: text/plain; charset="utf-8" > > Saul, > > This is a big change. I suggest adding it to the next TSC call. > > > Brent > > -----Original Message----- > From: Saul Wold [mailto:sgw at linux.intel.com] > Sent: Wednesday, November 21, 2018 12:11 PM > To: Victor Rodriguez ; Rowsell, Brent > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Migrate Starling X kernel patches to LTS kernel > > Victor, Brent: > > There are a couple of things not mentioned that I have heard talked about on both sides of this discussion. > > My understanding is that the kernel version is based on the RHEL/CentOS version as it's a known tested combination at the Distro level, even though there are patches to the kernel and user-space. > > On the other side, the 3.10 RHEL kernel (with all the RHEL patches) may not address all the known CVEs, so there is a concern about overall security. Intel is looking at the newer kernel and porting the StarlingX patches (as needed) for the Clear and Multi-OS parts of the project. > > The overall question becomes can StarlingX take the 4.19LTS kernel as a newer base kernel for the project, it reduces the overall patch load and address some security issues. > > I believe you understand these objectives. > > Sau! > > > On 11/20/18 6:42 PM, Victor Rodriguez wrote: >> On Tue, Nov 20, 2018 at 8:25 PM Rowsell, Brent >> wrote: >>> >>> There are two kernels, standard and rt. >>> Both are centos 7.5 based with a small set of patches applied on top along with modified kernel config options. >>> >> >> Thanks for the clarification >> >>> Not quite understanding what you are asking. Are you proposing to replace the kernel in the starlingX project or just in your local environment ? >> >> For my local environment. I would not like to use CentOS kernel 3.10 >> but instead LTS 4.19 >> >>> What is the objective here ? >> >> To have a more stable and secure kernel on my production system, there >> are security fixes that would like to have on my kernel that LTS >> provides >> >> I know RHEL/CentOS is based on kernel 3.10 but other OSs are ot like >> ubuntu/debian/fedora >> >> Regards >> >>> >>> Brent >>> >>> -----Original Message----- >>> From: Victor Rodriguez [mailto:vm.rod25 at gmail.com] >>> Sent: Tuesday, November 20, 2018 9:20 PM >>> To: starlingx-discuss at lists.starlingx.io >>> Subject: [Starlingx-discuss] Migrate Starling X kernel patches to LTS >>> kernel >>> >>> Hi team >>> >>> I am a new user/developer of starling X and after searching into the kernel metapatches at: >>> >>> https://git.starlingx.io/cgit/stx-integ/tree/kernel >>> >>> Some questions came to me : >>> >>> As far as I can see we are under kernel 3.10 from RHEL RT fork right? >>> There are some ( actually many ) security and functional changes that >>> exist in the LTS kernel ( like 4.19 as an example), because of that I >>> would like to use a more stable kernel into my starling x system >>> >>> Is there any specific reason why use that specific for from RHEL? >>> >>> What does starling X think about the migration of these patches ( some of them are already applied into the latest versions of Linux Kernel)? >>> >>> What kind of test should I perform to check that my vanilla kernel + STX patches work as expected? >>> >>> All feedback is more than welcome >>> >>> BTW thanks to Mario and Saul for the help on understand more these >>> patches >>> >>> Regards >>> >>> Victor Rodriguez >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > ------------------------------ > > Message: 5 > Date: Wed, 21 Nov 2018 21:36:29 +0000 > From: "Lara, Cesar" > To: "starlingx-discuss at lists.starlingx.io" > > Subject: [Starlingx-discuss] [build][meetings]Agenda for Build team > meeting 11/22/2018 > Message-ID: > <0B566C62EC792145B40E29EFEBF1AB471056AB69 at fmsmsx104.amr.corp.intel.com> > > Content-Type: text/plain; charset="utf-8" > > Build team meeting 11/22/2018 > > Agenda > - Cengn follow up - Ken > - Mirror script refactor - Marcela > - Build team Imperatives for next release > > Most of us are in non-holiday areas, please let me know if there is a showstopper to host this meeting without people from USA > > > Regards > > Cesar Lara > Software Engineering Manager > OpenSource Technology Center > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > ------------------------------ > > End of Starlingx-discuss Digest, Vol 6, Issue 70 > ************************************************ > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From changcheng.liu at intel.com Thu Nov 22 16:16:22 2018 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Thu, 22 Nov 2018 16:16:22 +0000 Subject: [Starlingx-discuss] stx-tools: setup stx build environment In-Reply-To: <0D7994A90DD70040A9F5E77C4D23C57D50EF931C@SHSMSX104.ccr.corp.intel.com> References: <0D7994A90DD70040A9F5E77C4D23C57D50EF931C@SHSMSX104.ccr.corp.intel.com> Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50EFAC87@SHSMSX104.ccr.corp.intel.com> Hi Erich, I still met with some problems after following your method to run "download_mirror.sh". Please check the comment in https://bugs.launchpad.net/starlingx/+bug/1804412 [root at 90104f541da1 logs]# wc -l * 0 K1_failmoved_url_centos.log 0 K1_rpms_found_centos.log 0 K1_rpms_missing_centos.log 0 K1_srpms_found_centos.log 0 K1_srpms_missing_centos.log 46 L1_failmoved_url_3rdparties.log 5306 L1_failmoved_url_centos.log 394 L1_failmoved_url_centos3rdparties.log 0 L1_rpms_found_3rdparties.log 0 L1_rpms_found_centos.log 0 L1_rpms_found_centos3rdparties.log 0 L1_rpms_missing_3rdparties.log 0 L1_rpms_missing_centos.log 0 L1_rpms_missing_centos3rdparties.log 23 L1_srpms_found_3rdparties.log 1936 L1_srpms_found_centos.log 148 L1_srpms_found_centos3rdparties.log 0 L1_srpms_missing_3rdparties.log 0 L1_srpms_missing_centos.log 0 L1_srpms_missing_centos3rdparties.log 590 all_i686.txt 9858 otherfiles_centos_download.log 1 rpm-gpg-key-missing.txt 80 rpms_3rdparties_download_L1.log 490 rpms_centos3rdparties_download_L1.log 2 rpms_centos_download_K1.log 6735 rpms_centos_download_L1.log 57768 tarballs_download.log 83377 total [root at 90104f541da1 logs]# I don't know whether the "failmoved" packages will affect the ISO image build or not. I'm building another docker image for building ISO image. --Changcheng From: Liu, Changcheng Sent: Wednesday, November 21, 2018 11:24 PM To: 'starlingx-discuss at lists.starlingx.io' ; Cordoba Malibran, Erich Subject: RE: stx-tools: setup stx build environment Hi Erich, Please help check the problem. Tell me if you need more information. I'm trying to run "download_mirror.sh" again. B.R. Changcheng From: Liu, Changcheng Sent: Wednesday, November 21, 2018 6:35 PM To: 'starlingx-discuss at lists.starlingx.io' > Subject: stx-tools: setup stx build environment Could someone help check below bug? Title: stx-tools: failed to download required packaged Link: https://bugs.launchpad.net/starlingx/+bug/1804412 B.R. Changcheng From: Liu, Changcheng Sent: Friday, November 16, 2018 8:31 PM To: starlingx-discuss at lists.starlingx.io Subject: setup stx build environment Hi all, I have one question about setting up stx build environment. Why not move lots of many basic program installation process from mirror-check.sh to Dockerfile directly? Then stx community could supply one basic docker image as the base image to let developer customize it. Currently, I still need install lots of program after building Dockerfile into image. B.R. Changcheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eric.MacDonald at windriver.com Thu Nov 22 16:31:42 2018 From: Eric.MacDonald at windriver.com (MacDonald, Eric) Date: Thu, 22 Nov 2018 16:31:42 +0000 Subject: [Starlingx-discuss] build broken with mtce-guest failure in stx-nfv In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA486370@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C765FE3DD89@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA486370@ALA-MBD.corp.ad.wrs.com> Message-ID: <210898B96CA058408C55992CCAD98676B9F768AA@ALA-MBD.corp.ad.wrs.com> The fix is merged. From: Khalil, Ghada Sent: Thursday, November 22, 2018 10:41 AM To: Lin, Shuicheng; starlingx-discuss at lists.starlingx.io; MacDonald, Eric Subject: RE: build broken with mtce-guest failure in stx-nfv Importance: High Eric MacDonald is working on a fix. The Launchpad has been assigned to him. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, November 22, 2018 2:35 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] build broken with mtce-guest failure in stx-nfv Hi, I synced latest code today, and meet build failure with mtce-guest in stx-nfv. Here is the error message in the build log: BUILDSTDERR: guestServer.cpp: In function 'int _config_handler(void*, const char*, const char*, const char*)': BUILDSTDERR: guestServer.cpp:140:21: error: 'struct daemon_config_type' has no member named 'hbs_pulse_period' BUILDSTDERR: config_ptr->hbs_pulse_period = atoi(value); BUILDSTDERR: ^ It seems it is relate with patch [0], which removed "hbs_pulse_period". I have created LP issue [1]. Could anybody familiar with it help fix it? Thanks. [0]: https://review.openstack.org/617835 [1]: https://bugs.launchpad.net/starlingx/+bug/1804579 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From jose.perez.carranza at intel.com Thu Nov 22 17:00:39 2018 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Thu, 22 Nov 2018 17:00:39 +0000 Subject: [Starlingx-discuss] Modify port of an interface Message-ID: <0A5D9A624DF90343892F8F3FE7DE525A2A909A01@fmsmsx104.amr.corp.intel.com> Hi Is there a command to modify an interface port, before it was used something like ` system host-if-modify-ports` but that does not exists anymore and I don't see "port" option under `system host-if-modify` command. Regards, José From scott.little at windriver.com Thu Nov 22 17:38:47 2018 From: scott.little at windriver.com (Scott Little) Date: Thu, 22 Nov 2018 12:38:47 -0500 Subject: [Starlingx-discuss] [Build] Create mechanism to publish tarballs in StarlingX In-Reply-To: References: Message-ID: Would we want to publish tarballs on mirrors.starlingx.cengn.ca as part of the build process? Tarball would be updated nightly, rather than with every update as a zuul based solution would have it. e.g. http://mirror.starlingx.cengn.ca/mirror/starlingx//centos//outputs/tarballs/-.tar.gz or only publish the latest on branch... an in a structure more like that seen in http://tarballs.openstack.org ... http://mirror.starlingx.cengn.ca/mirror/starlingx/tarballs//-.tar.gz On 18-11-21 10:14 AM, Arce Moreno, Abraham wrote: > Hi all, > > As a result of our review for story 2003736 [0], here you have our first level of > findings but most important a request for comments: > > [ Objective ] > > "Create a new zuul check job to create tarballs from stx projects" > > Taking the existing OpenStack tarball infrastructure, we have the url tarballs @ openstack org [1] > so initial idea would be to host StarlingX tarballs in tarballs @ starlingx io [2] > > - Any question on the objective? Anything to highlight? > - Any other preference where to host the tarballs? > > [ Zuul ] > > There are some examples of jobs related to tarballs: > > - publish-openstack-artifacts > - publish-openstack-python-branch-tarball > - build-openstack-puppet-tarball > - publish-openstack-puppet-branch-tarball > > Should we target a reuse of existing jobs, probably not listed above > or create a new set of jobs? > > - build-starlingx-tarball > - publish-starlingx-tarball > > Getting your feedback in these first 2 questions will allow us to get a solid > direction for the rest of the week. > > [0] https://storyboard.openstack.org/#!/story/2003736 > [1] http://tarballs.openstack.org/ > [2] http://tarballs.starlingx.io/ > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From chris.friesen at windriver.com Thu Nov 22 17:42:17 2018 From: chris.friesen at windriver.com (Chris Friesen) Date: Thu, 22 Nov 2018 11:42:17 -0600 Subject: [Starlingx-discuss] Support IBRS cpu model. In-Reply-To: References: Message-ID: On 11/21/2018 11:46 PM, Sun, Austin wrote: > Hi Chris: > Very appreciate your review > The new PRs are > https://github.com/starlingx-staging/stx-nova/pull/17 > https://github.com/starlingx-staging/stx-glance/pull/5 What testing have you done on these changes? Chris From erich.cordoba.malibran at intel.com Thu Nov 22 17:55:12 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Thu, 22 Nov 2018 17:55:12 +0000 Subject: [Starlingx-discuss] [Build] Spec for stx-mirror tool creation. Message-ID: Hi, The spec for the mirror downloader was sent. You can find it here: https://review.openstack.org/#/c/619631/ -Erich From cindy.xie at intel.com Fri Nov 23 00:52:33 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Fri, 23 Nov 2018 00:52:33 +0000 Subject: [Starlingx-discuss] 3. Re: Migrate Starling X kernel patches to LTS kernel (Saul Wold) In-Reply-To: References: <38713B7817E1A049AB469EA7F6EEF69EBBFD7007@ALA-MBD.corp.ad.wrs.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35DCDCB6@SHSMSX104.ccr.corp.intel.com> Saul, I am trying to understand the ultimate goal for multi-OS: so if we upgrade the kernel to 4.19 LTS, then the same kernel is going to be used for Clear, Ubuntu and CentOS, right? Regardless that the official CentOS 7.x has an older version? I am not familiar w/ the OS distro concept, but for me validation effort for the new kernel plus relatively old CentOS user space might be major effort. Thx. - cindy -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Friday, November 23, 2018 12:02 AM To: Einarsson, Jim ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] 3. Re: Migrate Starling X kernel patches to LTS kernel (Saul Wold) On 11/22/18 7:06 AM, Einarsson, Jim wrote: > Saul, > We have no objections to your investigation of a kernel up version, but the forklift may be heavier than you realize. Certainly considerable work needs to be done to validate both functionality and performance aspects. I assume the investigation will happen in a sandbox side stream, to avoid disruption to the main branch. I highly recommend a spec be created and reviewed, to make sure all the necessary angles of the investigation are covered. > Exactly, we need to start this work for the Clear port we are currently doing and it will also need to be done as part of the Multi-OS effort since Ubuntu has a newer kernel. I am not proposing this happen on CentOS / master at this time, we know there is a large amount of work the forklift the patches, that work is already started against the 4.19 LTS kernel internally at Intel. We will work on a spec and address testing of the kernel. Sau! > JimE. > > Message: 3 > Date: Wed, 21 Nov 2018 09:10:47 -0800 > From: Saul Wold > To: Victor Rodriguez , Brent.Rowsell at windriver.com > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Migrate Starling X kernel patches to > LTS kernel > Message-ID: > Content-Type: text/plain; charset=utf-8; format=flowed > > Victor, Brent: > > There are a couple of things not mentioned that I have heard talked > about on both sides of this discussion. > > My understanding is that the kernel version is based on the > RHEL/CentOS version as it's a known tested combination at the Distro > level, even though there are patches to the kernel and user-space. > > On the other side, the 3.10 RHEL kernel (with all the RHEL patches) > may not address all the known CVEs, so there is a concern about > overall security. Intel is looking at the newer kernel and porting > the StarlingX patches (as needed) for the Clear and Multi-OS parts of > the project. > > The overall question becomes can StarlingX take the 4.19LTS kernel as > a newer base kernel for the project, it reduces the overall patch load > and address some security issues. > > I believe you understand these objectives. > > Sau! > > -----Original Message----- > From: starlingx-discuss-request at lists.starlingx.io > [mailto:starlingx-discuss-request at lists.starlingx.io] > Sent: Wednesday, November 21, 2018 4:37 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Starlingx-discuss Digest, Vol 6, Issue 70 > > Send Starlingx-discuss mailing list submissions to > starlingx-discuss at lists.starlingx.io > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > or, via email, send a message with subject or body 'help' to > starlingx-discuss-request at lists.starlingx.io > > You can reach the person managing the list at > starlingx-discuss-owner at lists.starlingx.io > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Starlingx-discuss digest..." > > > Today's Topics: > > 1. StarlingX mini-PTG Jan 15-16 in Phoenix (Jones, Bruce E) > 2. Re: stx-tools: document isn't aligned with code > (Arevalo, Mario Alfredo C) > 3. Re: Migrate Starling X kernel patches to LTS kernel (Saul Wold) > 4. Re: Migrate Starling X kernel patches to LTS kernel > (Rowsell, Brent) > 5. [build][meetings]Agenda for Build team meeting 11/22/2018 > (Lara, Cesar) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 21 Nov 2018 16:26:43 +0000 > From: "Jones, Bruce E" > To: "starlingx-discuss at lists.starlingx.io" > > Subject: [Starlingx-discuss] StarlingX mini-PTG Jan 15-16 in Phoenix > Message-ID: > > <9A85D2917C58154C960D95352B22818BB1EB0050 at fmsmsx115.amr.corp.intel.com > > > > Content-Type: text/plain; charset="utf-8" > > We are thinking about holding a StarlingX mini-PTG meeting in January in Phoenix, to be hosted on the Intel campus. > > I'd like to get an early headcount and make sure there are no conflicts for the dates. Please reply to this email and let me know if you can/want to attend, or if you would like to attend but have a conflict for these dates. > > Thank you! > > brucej > > -------------- next part -------------- An HTML attachment was > scrubbed... > URL: > 81121/daa8ea1b/attachment-0001.html> > > ------------------------------ > > Message: 2 > Date: Wed, 21 Nov 2018 16:55:39 +0000 > From: "Arevalo, Mario Alfredo C" > To: "Arce Moreno, Abraham" , "Liu, > Changcheng" , > "starlingx-discuss at lists.starlingx.io" > > Subject: Re: [Starlingx-discuss] stx-tools: document isn't aligned > with code > Message-ID: > > <6594B51DBE477C48AAE23675314E6C466451F8E3 at fmsmsx107.amr.corp.intel.com > > > > Content-Type: text/plain; charset="Windows-1252" > > Hi Changcheng and Abraham, > > I have sent a new version in order to update the documentation > according to the new changes in Dockerfile[s]. You can take a look in this link: > > https://review.openstack.org/#/c/601308/ > > sorry for any inconvenience. > > Best regards. > Mario. > ________________________________________ > From: Arce Moreno, Abraham > Sent: Wednesday, November 21, 2018 7:35 AM > To: Liu, Changcheng; starlingx-discuss at lists.starlingx.io; Arevalo, > Mario Alfredo C > Subject: RE: stx-tools: document isn't aligned with code > > Hi again Changcheng, > >> I’m following below document to create-starlingx-packages. It’s not >> aligned with latest code. > > You are right... > >> https://docs.starlingx.io/developer_guide/index.html#create- >> starlingx-packages >> > x- >> packages> >> Could the man, who’s responsible for continuous-integration, clean >> the document and make it more clear? > > Under this review we will include the changes to align with Mario's cleanup: > [Developer Guide] Setup Building Docker Container [0] > > The logic behind to accommodate the new "Developer Guide" flow > proposal would look like: > > FYI "..." means content is not intended to be changed. > > - Requirements > - ... > - Development Environment Setup > - ... > - Prepare the Base Docker Image > - Configuration > - Sample localrc > - Build Base Docker Image > - Build the CentOS Mirror Repository > - Run Mirror Docker Container > - Download Packages > - Verify Packages > - Packages Structure > - Create CentOS Mirror Repository > - Create StarlingX Packages > - Run Building Docker Container > - Download Source Code Repositories > - Build Packages > - Build StarlingX ISO > - Build Installer > - ... > - Build Avoidance > - ... > > In summary, "flow proposal" could look like: > > - Prepare Base Docker Image > - Build "base image" > - Build the CentOS Mirror Repository > - Run container from "base image" > - Get mirror files > - Create StarlingX Packages > - Run container from "base image" > - Get StarlingX source code > - Build StarlingX packages > - Build StarlingX ISO > >> 1. The stx-tools code isn’t aligned with the above document >> since base- build/build target has been removed. >> 2. Besides this, README.rst is not updated in time when the >> build rule has been changed. > > README.rst from stx-tools project is going under a review process [1] > so please feel free to leave your comments. > > [0] https://review.openstack.org/#/c/619043/ > [1] https://review.openstack.org/#/c/601308/ > > > > ------------------------------ > > Message: 3 > Date: Wed, 21 Nov 2018 09:10:47 -0800 > From: Saul Wold > To: Victor Rodriguez , Brent.Rowsell at windriver.com > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Migrate Starling X kernel patches to > LTS kernel > Message-ID: > Content-Type: text/plain; charset=utf-8; format=flowed > > Victor, Brent: > > There are a couple of things not mentioned that I have heard talked > about on both sides of this discussion. > > My understanding is that the kernel version is based on the > RHEL/CentOS version as it's a known tested combination at the Distro > level, even though there are patches to the kernel and user-space. > > On the other side, the 3.10 RHEL kernel (with all the RHEL patches) > may not address all the known CVEs, so there is a concern about > overall security. Intel is looking at the newer kernel and porting > the StarlingX patches (as needed) for the Clear and Multi-OS parts of > the project. > > The overall question becomes can StarlingX take the 4.19LTS kernel as > a newer base kernel for the project, it reduces the overall patch load > and address some security issues. > > I believe you understand these objectives. > > Sau! > > > On 11/20/18 6:42 PM, Victor Rodriguez wrote: >> On Tue, Nov 20, 2018 at 8:25 PM Rowsell, Brent >> wrote: >>> >>> There are two kernels, standard and rt. >>> Both are centos 7.5 based with a small set of patches applied on top along with modified kernel config options. >>> >> >> Thanks for the clarification >> >>> Not quite understanding what you are asking. Are you proposing to replace the kernel in the starlingX project or just in your local environment ? >> >> For my local environment. I would not like to use CentOS kernel 3.10 >> but instead LTS 4.19 >> >>> What is the objective here ? >> >> To have a more stable and secure kernel on my production system, >> there are security fixes that would like to have on my kernel that >> LTS provides >> >> I know RHEL/CentOS is based on kernel 3.10 but other OSs are ot like >> ubuntu/debian/fedora >> >> Regards >> >>> >>> Brent >>> >>> -----Original Message----- >>> From: Victor Rodriguez [mailto:vm.rod25 at gmail.com] >>> Sent: Tuesday, November 20, 2018 9:20 PM >>> To: starlingx-discuss at lists.starlingx.io >>> Subject: [Starlingx-discuss] Migrate Starling X kernel patches to >>> LTS kernel >>> >>> Hi team >>> >>> I am a new user/developer of starling X and after searching into the kernel metapatches at: >>> >>> https://git.starlingx.io/cgit/stx-integ/tree/kernel >>> >>> Some questions came to me : >>> >>> As far as I can see we are under kernel 3.10 from RHEL RT fork right? >>> There are some ( actually many ) security and functional changes >>> that exist in the LTS kernel ( like 4.19 as an example), because of >>> that I would like to use a more stable kernel into my starling x >>> system >>> >>> Is there any specific reason why use that specific for from RHEL? >>> >>> What does starling X think about the migration of these patches ( some of them are already applied into the latest versions of Linux Kernel)? >>> >>> What kind of test should I perform to check that my vanilla kernel + STX patches work as expected? >>> >>> All feedback is more than welcome >>> >>> BTW thanks to Mario and Saul for the help on understand more these >>> patches >>> >>> Regards >>> >>> Victor Rodriguez >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > > > ------------------------------ > > Message: 4 > Date: Wed, 21 Nov 2018 17:21:49 +0000 > From: "Rowsell, Brent" > To: Saul Wold , Victor Rodriguez > > Cc: "starlingx-discuss at lists.starlingx.io" > > Subject: Re: [Starlingx-discuss] Migrate Starling X kernel patches to > LTS kernel > Message-ID: > <2588653EBDFFA34B982FAF00F1B4844EBB31A592 at ALA-MBD.corp.ad.wrs.com> > Content-Type: text/plain; charset="utf-8" > > Saul, > > This is a big change. I suggest adding it to the next TSC call. > > > Brent > > -----Original Message----- > From: Saul Wold [mailto:sgw at linux.intel.com] > Sent: Wednesday, November 21, 2018 12:11 PM > To: Victor Rodriguez ; Rowsell, Brent > > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Migrate Starling X kernel patches to > LTS kernel > > Victor, Brent: > > There are a couple of things not mentioned that I have heard talked about on both sides of this discussion. > > My understanding is that the kernel version is based on the RHEL/CentOS version as it's a known tested combination at the Distro level, even though there are patches to the kernel and user-space. > > On the other side, the 3.10 RHEL kernel (with all the RHEL patches) may not address all the known CVEs, so there is a concern about overall security. Intel is looking at the newer kernel and porting the StarlingX patches (as needed) for the Clear and Multi-OS parts of the project. > > The overall question becomes can StarlingX take the 4.19LTS kernel as a newer base kernel for the project, it reduces the overall patch load and address some security issues. > > I believe you understand these objectives. > > Sau! > > > On 11/20/18 6:42 PM, Victor Rodriguez wrote: >> On Tue, Nov 20, 2018 at 8:25 PM Rowsell, Brent >> wrote: >>> >>> There are two kernels, standard and rt. >>> Both are centos 7.5 based with a small set of patches applied on top along with modified kernel config options. >>> >> >> Thanks for the clarification >> >>> Not quite understanding what you are asking. Are you proposing to replace the kernel in the starlingX project or just in your local environment ? >> >> For my local environment. I would not like to use CentOS kernel 3.10 >> but instead LTS 4.19 >> >>> What is the objective here ? >> >> To have a more stable and secure kernel on my production system, >> there are security fixes that would like to have on my kernel that >> LTS provides >> >> I know RHEL/CentOS is based on kernel 3.10 but other OSs are ot like >> ubuntu/debian/fedora >> >> Regards >> >>> >>> Brent >>> >>> -----Original Message----- >>> From: Victor Rodriguez [mailto:vm.rod25 at gmail.com] >>> Sent: Tuesday, November 20, 2018 9:20 PM >>> To: starlingx-discuss at lists.starlingx.io >>> Subject: [Starlingx-discuss] Migrate Starling X kernel patches to >>> LTS kernel >>> >>> Hi team >>> >>> I am a new user/developer of starling X and after searching into the kernel metapatches at: >>> >>> https://git.starlingx.io/cgit/stx-integ/tree/kernel >>> >>> Some questions came to me : >>> >>> As far as I can see we are under kernel 3.10 from RHEL RT fork right? >>> There are some ( actually many ) security and functional changes >>> that exist in the LTS kernel ( like 4.19 as an example), because of >>> that I would like to use a more stable kernel into my starling x >>> system >>> >>> Is there any specific reason why use that specific for from RHEL? >>> >>> What does starling X think about the migration of these patches ( some of them are already applied into the latest versions of Linux Kernel)? >>> >>> What kind of test should I perform to check that my vanilla kernel + STX patches work as expected? >>> >>> All feedback is more than welcome >>> >>> BTW thanks to Mario and Saul for the help on understand more these >>> patches >>> >>> Regards >>> >>> Victor Rodriguez >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > ------------------------------ > > Message: 5 > Date: Wed, 21 Nov 2018 21:36:29 +0000 > From: "Lara, Cesar" > To: "starlingx-discuss at lists.starlingx.io" > > Subject: [Starlingx-discuss] [build][meetings]Agenda for Build team > meeting 11/22/2018 > Message-ID: > > <0B566C62EC792145B40E29EFEBF1AB471056AB69 at fmsmsx104.amr.corp.intel.com > > > > Content-Type: text/plain; charset="utf-8" > > Build team meeting 11/22/2018 > > Agenda > - Cengn follow up - Ken > - Mirror script refactor - Marcela > - Build team Imperatives for next release > > Most of us are in non-holiday areas, please let me know if there is a > showstopper to host this meeting without people from USA > > > Regards > > Cesar Lara > Software Engineering Manager > OpenSource Technology Center > > -------------- next part -------------- An HTML attachment was > scrubbed... > URL: > 81121/8805e005/attachment.html> > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > ------------------------------ > > End of Starlingx-discuss Digest, Vol 6, Issue 70 > ************************************************ > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From austin.sun at intel.com Fri Nov 23 06:16:38 2018 From: austin.sun at intel.com (Sun, Austin) Date: Fri, 23 Nov 2018 06:16:38 +0000 Subject: [Starlingx-discuss] Support IBRS cpu model. In-Reply-To: References: Message-ID: Hi Chris: Due to resource limitation , I only deployed in Skylake-IBIS server , create VM enabling cpu-passthrough. Thanks. BR Austin Sun. -----Original Message----- From: Chris Friesen [mailto:chris.friesen at windriver.com] Sent: Friday, November 23, 2018 1:42 AM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Support IBRS cpu model. On 11/21/2018 11:46 PM, Sun, Austin wrote: > Hi Chris: > Very appreciate your review > The new PRs are > https://github.com/starlingx-staging/stx-nova/pull/17 > https://github.com/starlingx-staging/stx-glance/pull/5 What testing have you done on these changes? Chris From changcheng.liu at intel.com Fri Nov 23 07:18:34 2018 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Fri, 23 Nov 2018 07:18:34 +0000 Subject: [Starlingx-discuss] stx-ceph patch commit detail: Add .gitreview Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50EFAE57@SHSMSX104.ccr.corp.intel.com> Hi Dean, I'm porting stx-ceph/v10.2.6 upgrade patches to be stx-ceph/v13.2.2 Both WindRiver and I have the question about below patch: Add .gitreview https://github.com/starlingx-staging/stx-ceph/commit/9d93e43290d3a2a0399af75fcb9f7c5a0291e0cc What's the function of the above patch? Do we still need it in stx-ceph/v13.2.2? Regards, Changcheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From changcheng.liu at intel.com Fri Nov 23 13:25:49 2018 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Fri, 23 Nov 2018 13:25:49 +0000 Subject: [Starlingx-discuss] stx-tools: setup stx build environment References: <0D7994A90DD70040A9F5E77C4D23C57D50EF931C@SHSMSX104.ccr.corp.intel.com> Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50EFAF5F@SHSMSX104.ccr.corp.intel.com> Hi Erich, I hit lots of error when executing "build-pkgs". Please help check it. https://bugs.launchpad.net/starlingx/+bug/1804412 1. get stx-tools cd $HOME git clone https://git.starlingx.io/stx-tools cd stx-tools git checkout -b erich_base 1d2ecbb0be2 2. apply below patch nstcc1 at nstcloudcc1:stx-tools$ git diff Dockerfile tb.sh Makefile diff --git a/Dockerfile b/Dockerfile index 87ef00b..dd730f9 100644 --- a/Dockerfile +++ b/Dockerfile @@ -13,9 +13,9 @@ FROM centos:7.4.1708 # Proxy configuration -#ENV http_proxy "http://your.actual_http_proxy.com:your_port" -#ENV https_proxy "https://your.actual_https_proxy.com:your_port" -#ENV ftp_proxy "http://your.actual_ftp_proxy.com:your_port" +ENV http_proxy "http://child-prc.intel.com:913" +ENV https_proxy "http://child-prc.intel.com:913" +ENV ftp_proxy "ftp://child-prc.intel.com:913" # username you will docker exec into the container as. @@ -26,6 +26,8 @@ ARG MYUID=1000 ENV container=docker +RUN echo "proxy=$http_proxy" >> /etc/yum.conf && \ +echo -e "export http_proxy=$http_proxy\nexport https_proxy=$https_proxy\nexport ftp_proxy=$ftp_proxy" >> /root/.bashrc # Download required dependencies by mirror/build processes. # Notice there are 3 invocations to yum package manage. # 1) Enable EPEL repository. diff --git a/Makefile b/Makefile index c4ebff4..73f5f3a 100644 --- a/Makefile +++ b/Makefile @@ -20,6 +20,8 @@ all: docker build \ --build-arg MYUID=$(UID) \ --build-arg MYUNAME=$(MYUNAME) \ + --build-arg https_proxy=http://child-prc.intel.com:913 \ + --build-arg http_proxy=http://child-prc.intel.com:913 \ --ulimit core=0 \ --network host \ -t $(TC_CONTAINER_TAG) \ diff --git a/tb.sh b/tb.sh index e0508dd..9530efd 100755 --- a/tb.sh +++ b/tb.sh @@ -38,11 +38,14 @@ function run_container { docker run -it --rm \ --name ${TC_CONTAINER_NAME} \ --detach \ + -v /etc/localtime:/etc/localtime:ro \ -v ${LOCALDISK}:/${GUEST_LOCALDISK} \ -v ${HOST_MIRROR_DIR}:/import/mirrors:ro \ -v /sys/fs/cgroup:/sys/fs/cgroup:ro \ -v ~/.ssh:/mySSH:ro \ -e "container=docker" \ + --env https_proxy=http://child-prc.intel.com:913 \ + --env http_proxy=http://child-prc.intel.com:913 \ -e MYUNAME=${MYUNAME} \ --privileged=true \ --security-opt seccomp=unconfined \ 3. build docker image make all 4. run docker image bash tb.sh run 5. execute into docker container bash tb.sh exec 6. [nstcc1 at d8ae703a2a91 /]$ eval $(ssh-agent) Agent pid 15524 [nstcc1 at d8ae703a2a91 /]$ ssh-add Identity added: /home/nstcc1/.ssh/id_rsa (/home/nstcc1/.ssh/id_rsa) [nstcc1 at d8ae703a2a91 /]$ cd $MY_REPO_ROOT_DIR [nstcc1 at d8ae703a2a91 starlingx]$ repo init -u https://git.starlingx.io/stx-manifest -m default.xml [nstcc1 at d8ae703a2a91 starlingx]$ repo sync -j4 [nstcc1 at d8ae703a2a91 starlingx]$ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/stx/ [nstcc1 at d8ae703a2a91 starlingx]$ populate_downloads.sh /import/mirrors/CentOS/stx-r1/CentOS/pike/ 7. nstcc1 at nstcloudcc1:~$ mkdir -p $HOME/starlingx/mirror/CentOS/tis-installer nstcc1 at nstcloudcc1:~$ cp $HOME/starlingx/mirror/CentOS/stx-r1/CentOS/pike/Binary/images/pxeboot/initrd.img $HOME/starlingx/mirror/CentOS/tis-installer/initrd.img-stx-0.2 nstcc1 at nstcloudcc1:~$ cp $HOME/starlingx/mirror/CentOS/stx-r1/CentOS/pike/Binary/images/pxeboot/vmlinuz $HOME/starlingx/mirror/CentOS/tis-installer/vmlinuz-stx-0.2 nstcc1 at nstcloudcc1:~$ cp $HOME/starlingx/mirror/CentOS/stx-r1/CentOS/pike/Binary/LiveOS/squashfs.img $HOME/starlingx/mirror/CentOS/tis-installer/squashfs.img-stx-0.2 8. [nstcc1 at d8ae703a2a91 starlingx]$ generate-cgcs-centos-repo.sh /import/mirrors/CentOS/stx-r1/CentOS/pike/ 9. [nstcc1 at d8ae703a2a91 starlingx]$ build-pkgs Then, hit lots of error, the log is build-pkgs.log 21:10:47 failure: repodata/repomd.xml from TisCentos7Distro: [Errno 256] No more mirrors to try. 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 21:10:47 End build on 'b0': /localdisk/loadbuild/nstcc1/starlingx/std/rpmbuild/SRPMS/mariadb-10.1.28-1.el7.tis.15.src.rpm 21:10:47 Error building mariadb-10.1.28-1.el7.tis.15.src.rpm on 'b0'. --Thanks Changcheng From: Liu, Changcheng Sent: Friday, November 23, 2018 12:16 AM To: 'starlingx-discuss at lists.starlingx.io' ; Cordoba Malibran, Erich Subject: RE: stx-tools: setup stx build environment Hi Erich, I still met with some problems after following your method to run "download_mirror.sh". Please check the comment in https://bugs.launchpad.net/starlingx/+bug/1804412 [root at 90104f541da1 logs]# wc -l * 0 K1_failmoved_url_centos.log 0 K1_rpms_found_centos.log 0 K1_rpms_missing_centos.log 0 K1_srpms_found_centos.log 0 K1_srpms_missing_centos.log 46 L1_failmoved_url_3rdparties.log 5306 L1_failmoved_url_centos.log 394 L1_failmoved_url_centos3rdparties.log 0 L1_rpms_found_3rdparties.log 0 L1_rpms_found_centos.log 0 L1_rpms_found_centos3rdparties.log 0 L1_rpms_missing_3rdparties.log 0 L1_rpms_missing_centos.log 0 L1_rpms_missing_centos3rdparties.log 23 L1_srpms_found_3rdparties.log 1936 L1_srpms_found_centos.log 148 L1_srpms_found_centos3rdparties.log 0 L1_srpms_missing_3rdparties.log 0 L1_srpms_missing_centos.log 0 L1_srpms_missing_centos3rdparties.log 590 all_i686.txt 9858 otherfiles_centos_download.log 1 rpm-gpg-key-missing.txt 80 rpms_3rdparties_download_L1.log 490 rpms_centos3rdparties_download_L1.log 2 rpms_centos_download_K1.log 6735 rpms_centos_download_L1.log 57768 tarballs_download.log 83377 total [root at 90104f541da1 logs]# I don't know whether the "failmoved" packages will affect the ISO image build or not. I'm building another docker image for building ISO image. --Changcheng From: Liu, Changcheng Sent: Wednesday, November 21, 2018 11:24 PM To: 'starlingx-discuss at lists.starlingx.io' >; Cordoba Malibran, Erich > Subject: RE: stx-tools: setup stx build environment Hi Erich, Please help check the problem. Tell me if you need more information. I'm trying to run "download_mirror.sh" again. B.R. Changcheng From: Liu, Changcheng Sent: Wednesday, November 21, 2018 6:35 PM To: 'starlingx-discuss at lists.starlingx.io' > Subject: stx-tools: setup stx build environment Could someone help check below bug? Title: stx-tools: failed to download required packaged Link: https://bugs.launchpad.net/starlingx/+bug/1804412 B.R. Changcheng From: Liu, Changcheng Sent: Friday, November 16, 2018 8:31 PM To: starlingx-discuss at lists.starlingx.io Subject: setup stx build environment Hi all, I have one question about setting up stx build environment. Why not move lots of many basic program installation process from mirror-check.sh to Dockerfile directly? Then stx community could supply one basic docker image as the base image to let developer customize it. Currently, I still need install lots of program after building Dockerfile into image. B.R. Changcheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.cm.lists at yandex.com Fri Nov 23 13:37:17 2018 From: erich.cm.lists at yandex.com (Erich Cordoba) Date: Fri, 23 Nov 2018 05:37:17 -0800 Subject: [Starlingx-discuss] stx-tools: setup stx build environment In-Reply-To: <0D7994A90DD70040A9F5E77C4D23C57D50EFAF5F@SHSMSX104.ccr.corp.intel.com> References: <0D7994A90DD70040A9F5E77C4D23C57D50EFAF5F@SHSMSX104.ccr.corp.intel.com> <0D7994A90DD70040A9F5E77C4D23C57D50EF931C@SHSMSX104.ccr.corp.intel.com> Message-ID: <4355461542980237@sas1-87f9feb8d943.qloud-c.yandex.net> An HTML attachment was scrubbed... URL: From chris.friesen at windriver.com Fri Nov 23 15:07:43 2018 From: chris.friesen at windriver.com (Chris Friesen) Date: Fri, 23 Nov 2018 09:07:43 -0600 Subject: [Starlingx-discuss] Support IBRS cpu model. In-Reply-To: References: Message-ID: <08e3677f-39dc-bc99-2791-c88468e17c4a@windriver.com> In order to ensure that we don't break existing code, I think we'd also need to test by booting VMs built using at least a flavor that specifies a different IBRS CPU model and a different non-IBRS CPU model. Chris On 11/23/2018 12:16 AM, Sun, Austin wrote: > Hi Chris: > Due to resource limitation , I only deployed in Skylake-IBIS server , create VM enabling cpu-passthrough. > > Thanks. > BR > Austin Sun. > -----Original Message----- > From: Chris Friesen [mailto:chris.friesen at windriver.com] > Sent: Friday, November 23, 2018 1:42 AM > To: Sun, Austin ; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Support IBRS cpu model. > > On 11/21/2018 11:46 PM, Sun, Austin wrote: >> Hi Chris: >> Very appreciate your review >> The new PRs are >> https://github.com/starlingx-staging/stx-nova/pull/17 >> https://github.com/starlingx-staging/stx-glance/pull/5 > > What testing have you done on these changes? > > Chris > From erich.cordoba.malibran at intel.com Fri Nov 23 16:21:56 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Fri, 23 Nov 2018 16:21:56 +0000 Subject: [Starlingx-discuss] 3. Re: Migrate Starling X kernel patches to LTS kernel (Saul Wold) In-Reply-To: References: <38713B7817E1A049AB469EA7F6EEF69EBBFD7007@ALA-MBD.corp.ad.wrs.com> Message-ID: <14cd9c85597b75bec45966a9645e03859d72dd46.camel@intel.com> I think is a good approach to migrate to LTS kernel, however just keep in mind that isn't just a patch rebase effort. We've seen virtual networking losses only because the upgrade of kernel (on CentOs 7.5) and a patch DPDK was needed. So, it is possible to find this kind of surprises that could result in a chain of needed upgrades. We need to define a proper testing scope to know in which parts put more attention in the upgrade. On Thu, 2018-11-22 at 08:02 -0800, Saul Wold wrote: > > On 11/22/18 7:06 AM, Einarsson, Jim wrote: > > Saul, > > We have no objections to your investigation of a kernel up version, > > but the forklift may be heavier than you realize. Certainly > > considerable work needs to be done to validate both functionality > > and performance aspects. I assume the investigation will happen in > > a sandbox side stream, to avoid disruption to the main branch. I > > highly recommend a spec be created and reviewed, to make sure all > > the necessary angles of the investigation are covered. > > > > Exactly, we need to start this work for the Clear port we are > currently > doing and it will also need to be done as part of the Multi-OS > effort > since Ubuntu has a newer kernel. > > I am not proposing this happen on CentOS / master at this time, we > know > there is a large amount of work the forklift the patches, that work > is > already started against the 4.19 LTS kernel internally at Intel. > > We will work on a spec and address testing of the kernel. > > Sau! > > > > JimE. > > > > Message: 3 > > Date: Wed, 21 Nov 2018 09:10:47 -0800 > > From: Saul Wold > > To: Victor Rodriguez , Brent.Rowsell at windriver. > > com > > Cc: starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] Migrate Starling X kernel patches > > to > > LTS kernel > > Message-ID: > > Content-Type: text/plain; charset=utf-8; format=flowed > > > > Victor, Brent: > > > > There are a couple of things not mentioned that I have heard talked > > about on both sides of this discussion. > > > > My understanding is that the kernel version is based on the > > RHEL/CentOS > > version as it's a known tested combination at the Distro level, > > even > > though there are patches to the kernel and user-space. > > > > On the other side, the 3.10 RHEL kernel (with all the RHEL patches) > > may > > not address all the known CVEs, so there is a concern about overall > > security. Intel is looking at the newer kernel and porting the > > StarlingX patches (as needed) for the Clear and Multi-OS parts of > > the > > project. > > > > The overall question becomes can StarlingX take the 4.19LTS kernel > > as a > > newer base kernel for the project, it reduces the overall patch > > load and > > address some security issues. > > > > I believe you understand these objectives. > > > > Sau! > > > > -----Original Message----- > > From: starlingx-discuss-request at lists.starlingx.io [mailto:starling > > x-discuss-request at lists.starlingx.io] > > Sent: Wednesday, November 21, 2018 4:37 PM > > To: starlingx-discuss at lists.starlingx.io > > Subject: Starlingx-discuss Digest, Vol 6, Issue 70 > > > > Send Starlingx-discuss mailing list submissions to > > starlingx-discuss at lists.starlingx.io > > > > To subscribe or unsubscribe via the World Wide Web, visit > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-di > > scuss > > or, via email, send a message with subject or body 'help' to > > starlingx-discuss-request at lists.starlingx.io > > > > You can reach the person managing the list at > > starlingx-discuss-owner at lists.starlingx.io > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of Starlingx-discuss digest..." > > > > > > Today's Topics: > > > > 1. StarlingX mini-PTG Jan 15-16 in Phoenix (Jones, Bruce E) > > 2. Re: stx-tools: document isn't aligned with code > > (Arevalo, Mario Alfredo C) > > 3. Re: Migrate Starling X kernel patches to LTS kernel (Saul > > Wold) > > 4. Re: Migrate Starling X kernel patches to LTS kernel > > (Rowsell, Brent) > > 5. [build][meetings]Agenda for Build team meeting 11/22/ > > 2018 > > (Lara, Cesar) > > > > > > ----------------------------------------------------------------- > > ----- > > > > Message: 1 > > Date: Wed, 21 Nov 2018 16:26:43 +0000 > > From: "Jones, Bruce E" > > To: "starlingx-discuss at lists.starlingx.io" > > > > Subject: [Starlingx-discuss] StarlingX mini-PTG Jan 15-16 in > > Phoenix > > Message-ID: > > <9A85D2917C58154C960D95352B22818BB1EB0050 at fmsmsx115.amr.corp.in > > tel.com> > > > > Content-Type: text/plain; charset="utf-8" > > > > We are thinking about holding a StarlingX mini-PTG meeting in > > January in Phoenix, to be hosted on the Intel campus. > > > > I'd like to get an early headcount and make sure there are no > > conflicts for the dates. Please reply to this email and let me > > know if you can/want to attend, or if you would like to attend but > > have a conflict for these dates. > > > > Thank you! > > > > brucej > > > > -------------- next part -------------- > > An HTML attachment was scrubbed... > > URL: > ents/20181121/daa8ea1b/attachment-0001.html> > > > > ------------------------------ > > > > Message: 2 > > Date: Wed, 21 Nov 2018 16:55:39 +0000 > > From: "Arevalo, Mario Alfredo C" > > > > To: "Arce Moreno, Abraham" , "Liu, > > Changcheng" , > > "starlingx-discuss at lists.starlingx.io" > > > > Subject: Re: [Starlingx-discuss] stx-tools: document isn't aligned > > with code > > Message-ID: > > <6594B51DBE477C48AAE23675314E6C466451F8E3 at fmsmsx107.amr.corp.in > > tel.com> > > > > Content-Type: text/plain; charset="Windows-1252" > > > > Hi Changcheng and Abraham, > > > > I have sent a new version in order to update the documentation > > according > > to the new changes in Dockerfile[s]. You can take a look in this > > link: > > > > https://review.openstack.org/#/c/601308/ > > > > sorry for any inconvenience. > > > > Best regards. > > Mario. > > ________________________________________ > > From: Arce Moreno, Abraham > > Sent: Wednesday, November 21, 2018 7:35 AM > > To: Liu, Changcheng; starlingx-discuss at lists.starlingx.io; Arevalo, > > Mario Alfredo C > > Subject: RE: stx-tools: document isn't aligned with code > > > > Hi again Changcheng, > > > > > I’m following below document to create-starlingx-packages. It’s > > > not > > > aligned with latest code. > > > > You are right... > > > > > https://docs.starlingx.io/developer_guide/index.html#create- > > > starlingx-packages > > > > > lingx- > > > packages> > > > Could the man, who’s responsible for continuous-integration, > > > clean the > > > document and make it more clear? > > > > Under this review we will include the changes to align with Mario's > > cleanup: > > [Developer Guide] Setup Building Docker Container [0] > > > > The logic behind to accommodate the new "Developer Guide" flow > > proposal > > would look like: > > > > FYI "..." means content is not intended to be changed. > > > > - Requirements > > - ... > > - Development Environment Setup > > - ... > > - Prepare the Base Docker Image > > - Configuration > > - Sample localrc > > - Build Base Docker Image > > - Build the CentOS Mirror Repository > > - Run Mirror Docker Container > > - Download Packages > > - Verify Packages > > - Packages Structure > > - Create CentOS Mirror Repository > > - Create StarlingX Packages > > - Run Building Docker Container > > - Download Source Code Repositories > > - Build Packages > > - Build StarlingX ISO > > - Build Installer > > - ... > > - Build Avoidance > > - ... > > > > In summary, "flow proposal" could look like: > > > > - Prepare Base Docker Image > > - Build "base image" > > - Build the CentOS Mirror Repository > > - Run container from "base image" > > - Get mirror files > > - Create StarlingX Packages > > - Run container from "base image" > > - Get StarlingX source code > > - Build StarlingX packages > > - Build StarlingX ISO > > > > > 1. The stx-tools code isn’t aligned with the above document > > > since base- > > > build/build target has been removed. > > > 2. Besides this, README.rst is not updated in time when > > > the build rule > > > has been changed. > > > > README.rst from stx-tools project is going under a review process > > [1] so please > > feel free to leave your comments. > > > > [0] https://review.openstack.org/#/c/619043/ > > [1] https://review.openstack.org/#/c/601308/ > > > > > > > > ------------------------------ > > > > Message: 3 > > Date: Wed, 21 Nov 2018 09:10:47 -0800 > > From: Saul Wold > > To: Victor Rodriguez , Brent.Rowsell at windriver. > > com > > Cc: starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] Migrate Starling X kernel patches > > to > > LTS kernel > > Message-ID: > > Content-Type: text/plain; charset=utf-8; format=flowed > > > > Victor, Brent: > > > > There are a couple of things not mentioned that I have heard talked > > about on both sides of this discussion. > > > > My understanding is that the kernel version is based on the > > RHEL/CentOS > > version as it's a known tested combination at the Distro level, > > even > > though there are patches to the kernel and user-space. > > > > On the other side, the 3.10 RHEL kernel (with all the RHEL patches) > > may > > not address all the known CVEs, so there is a concern about overall > > security. Intel is looking at the newer kernel and porting the > > StarlingX patches (as needed) for the Clear and Multi-OS parts of > > the > > project. > > > > The overall question becomes can StarlingX take the 4.19LTS kernel > > as a > > newer base kernel for the project, it reduces the overall patch > > load and > > address some security issues. > > > > I believe you understand these objectives. > > > > Sau! > > > > > > On 11/20/18 6:42 PM, Victor Rodriguez wrote: > > > On Tue, Nov 20, 2018 at 8:25 PM Rowsell, Brent > > > wrote: > > > > > > > > There are two kernels, standard and rt. > > > > Both are centos 7.5 based with a small set of patches applied > > > > on top along with modified kernel config options. > > > > > > > > > > Thanks for the clarification > > > > > > > Not quite understanding what you are asking. Are you proposing > > > > to replace the kernel in the starlingX project or just in your > > > > local environment ? > > > > > > For my local environment. I would not like to use CentOS kernel > > > 3.10 > > > but instead LTS 4.19 > > > > > > > What is the objective here ? > > > > > > To have a more stable and secure kernel on my production system, > > > there > > > are security fixes that would like to have on my kernel that LTS > > > provides > > > > > > I know RHEL/CentOS is based on kernel 3.10 but other OSs are ot > > > like > > > ubuntu/debian/fedora > > > > > > Regards > > > > > > > > > > > Brent > > > > > > > > -----Original Message----- > > > > From: Victor Rodriguez [mailto:vm.rod25 at gmail.com] > > > > Sent: Tuesday, November 20, 2018 9:20 PM > > > > To: starlingx-discuss at lists.starlingx.io > > > > Subject: [Starlingx-discuss] Migrate Starling X kernel patches > > > > to LTS kernel > > > > > > > > Hi team > > > > > > > > I am a new user/developer of starling X and after searching > > > > into the kernel metapatches at: > > > > > > > > https://git.starlingx.io/cgit/stx-integ/tree/kernel > > > > > > > > Some questions came to me : > > > > > > > > As far as I can see we are under kernel 3.10 from RHEL RT fork > > > > right? > > > > There are some ( actually many ) security and functional > > > > changes that exist in the LTS kernel ( like 4.19 as an > > > > example), because of that I would like to use a more stable > > > > kernel into my starling x system > > > > > > > > Is there any specific reason why use that specific for from > > > > RHEL? > > > > > > > > What does starling X think about the migration of these patches > > > > ( some of them are already applied into the latest versions of > > > > Linux Kernel)? > > > > > > > > What kind of test should I perform to check that my vanilla > > > > kernel + STX patches work as expected? > > > > > > > > All feedback is more than welcome > > > > > > > > BTW thanks to Mario and Saul for the help on understand more > > > > these patches > > > > > > > > Regards > > > > > > > > Victor Rodriguez > > > > > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-di > > > > scuss > > > > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-disc > > > uss > > > > > > > > > > > ------------------------------ > > > > Message: 4 > > Date: Wed, 21 Nov 2018 17:21:49 +0000 > > From: "Rowsell, Brent" > > To: Saul Wold , Victor Rodriguez > > > > Cc: "starlingx-discuss at lists.starlingx.io" > > > > Subject: Re: [Starlingx-discuss] Migrate Starling X kernel patches > > to > > LTS kernel > > Message-ID: > > <2588653EBDFFA34B982FAF00F1B4844EBB31A592 at ALA-MBD.corp.ad.wrs.c > > om> > > Content-Type: text/plain; charset="utf-8" > > > > Saul, > > > > This is a big change. I suggest adding it to the next TSC call. > > > > > > Brent > > > > -----Original Message----- > > From: Saul Wold [mailto:sgw at linux.intel.com] > > Sent: Wednesday, November 21, 2018 12:11 PM > > To: Victor Rodriguez ; Rowsell, Brent > wsell at windriver.com> > > Cc: starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] Migrate Starling X kernel patches > > to LTS kernel > > > > Victor, Brent: > > > > There are a couple of things not mentioned that I have heard talked > > about on both sides of this discussion. > > > > My understanding is that the kernel version is based on the > > RHEL/CentOS version as it's a known tested combination at the > > Distro level, even though there are patches to the kernel and user- > > space. > > > > On the other side, the 3.10 RHEL kernel (with all the RHEL patches) > > may not address all the known CVEs, so there is a concern about > > overall security. Intel is looking at the newer kernel and porting > > the StarlingX patches (as needed) for the Clear and Multi-OS parts > > of the project. > > > > The overall question becomes can StarlingX take the 4.19LTS kernel > > as a newer base kernel for the project, it reduces the overall > > patch load and address some security issues. > > > > I believe you understand these objectives. > > > > Sau! > > > > > > On 11/20/18 6:42 PM, Victor Rodriguez wrote: > > > On Tue, Nov 20, 2018 at 8:25 PM Rowsell, Brent > > > wrote: > > > > > > > > There are two kernels, standard and rt. > > > > Both are centos 7.5 based with a small set of patches applied > > > > on top along with modified kernel config options. > > > > > > > > > > Thanks for the clarification > > > > > > > Not quite understanding what you are asking. Are you proposing > > > > to replace the kernel in the starlingX project or just in your > > > > local environment ? > > > > > > For my local environment. I would not like to use CentOS kernel > > > 3.10 > > > but instead LTS 4.19 > > > > > > > What is the objective here ? > > > > > > To have a more stable and secure kernel on my production system, > > > there > > > are security fixes that would like to have on my kernel that LTS > > > provides > > > > > > I know RHEL/CentOS is based on kernel 3.10 but other OSs are ot > > > like > > > ubuntu/debian/fedora > > > > > > Regards > > > > > > > > > > > Brent > > > > > > > > -----Original Message----- > > > > From: Victor Rodriguez [mailto:vm.rod25 at gmail.com] > > > > Sent: Tuesday, November 20, 2018 9:20 PM > > > > To: starlingx-discuss at lists.starlingx.io > > > > Subject: [Starlingx-discuss] Migrate Starling X kernel patches > > > > to LTS > > > > kernel > > > > > > > > Hi team > > > > > > > > I am a new user/developer of starling X and after searching > > > > into the kernel metapatches at: > > > > > > > > https://git.starlingx.io/cgit/stx-integ/tree/kernel > > > > > > > > Some questions came to me : > > > > > > > > As far as I can see we are under kernel 3.10 from RHEL RT fork > > > > right? > > > > There are some ( actually many ) security and functional > > > > changes that > > > > exist in the LTS kernel ( like 4.19 as an example), because of > > > > that I > > > > would like to use a more stable kernel into my starling x > > > > system > > > > > > > > Is there any specific reason why use that specific for from > > > > RHEL? > > > > > > > > What does starling X think about the migration of these patches > > > > ( some of them are already applied into the latest versions of > > > > Linux Kernel)? > > > > > > > > What kind of test should I perform to check that my vanilla > > > > kernel + STX patches work as expected? > > > > > > > > All feedback is more than welcome > > > > > > > > BTW thanks to Mario and Saul for the help on understand more > > > > these > > > > patches > > > > > > > > Regards > > > > > > > > Victor Rodriguez > > > > > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-di > > > > scuss > > > > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-disc > > > uss > > > > > > > ------------------------------ > > > > Message: 5 > > Date: Wed, 21 Nov 2018 21:36:29 +0000 > > From: "Lara, Cesar" > > To: "starlingx-discuss at lists.starlingx.io" > > > > Subject: [Starlingx-discuss] [build][meetings]Agenda for Build team > > meeting 11/22/2018 > > Message-ID: > > <0B566C62EC792145B40E29EFEBF1AB471056AB69 at fmsmsx104.amr.corp.in > > tel.com> > > > > Content-Type: text/plain; charset="utf-8" > > > > Build team meeting 11/22/2018 > > > > Agenda > > - Cengn follow up - Ken > > - Mirror script refactor - Marcela > > - Build team Imperatives for next release > > > > Most of us are in non-holiday areas, please let me know if there is > > a showstopper to host this meeting without people from USA > > > > > > Regards > > > > Cesar Lara > > Software Engineering Manager > > OpenSource Technology Center > > > > -------------- next part -------------- > > An HTML attachment was scrubbed... > > URL: > ents/20181121/8805e005/attachment.html> > > > > ------------------------------ > > > > Subject: Digest Footer > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > > > > > ------------------------------ > > > > End of Starlingx-discuss Digest, Vol 6, Issue 70 > > ************************************************ > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Fri Nov 23 19:46:56 2018 From: scott.little at windriver.com (Scott Little) Date: Fri, 23 Nov 2018 14:46:56 -0500 Subject: [Starlingx-discuss] [Build] go loanguage Message-ID: <5c031adb-1e32-37c5-2f88-0720e11bd569@windriver.com> I have a designer that want to introduce a GO language package into our build.  This raises the question of how to handle GO's 'imports'. First a disclaimer.  I'm not a 'GO' exports.  The following discussion points are based on my brief research. Go imports are roughly akin to a 'C' language include, with one or few major differences. 1) It points to a directory rather than a file, which could be local or relative to your GOPATH 2) The convention is to use a path that is a crude approximation of the url from which it can be obtained. e.g. import ( "github.com/docker/distribution/registry/api/errcode" ) 3) If the directory is NOT already present, it can probably be downloaded automatically with tools like 'go get' or 'dep' (aka golang-dep).  These tools attempt transform the path into a URI, trying several vcs download protocols (git, mercurial, subversion...).  Downloads are stored under a local 'vendor' sub-directory.  There are a few wrinkles, like the ability of a sire to respond with a re-direct to another site. There are centos rpms for a handful of core libraries, delivering code to /usr/share/gocode (part of your GOPATH).  However most go code has never been published as an rpm, and much of the remainder seems to be a one off rpm, with no ongoing maintenance. 'go get' just seems to grab the latest code.  Reproducibility is a big concern. 'dep init' solves the reproducibility concern.  It grabs the latest code, but also generates a 'lock' file that capture a CVS commit identifier (e.g. a git SHA).  Deliver the lock file with your code and 'dep ensure' will use the lock file to download the same code every time.  Dep does not currently ship as an RPM.  I have a working spec file for dep 0.4.1.  Dep 0.5.0 needs more work. Licenses of public go libraries seem to be permissive, at least for a statically linked binary, which is what we would want to ship. Not so sure about the inclusion of library source as an embedded vendor sub-directory in our own src.rpm packages.  That would be one for the lawyers. So our options seem to be. 1) Create rpms of all the go libraries we need, populating /usr/share/gocode.  There might be some tooling available to help with this.    Pro: Don't require network access to build.    Pro: Reproducible builds    Pro: License of each go rpm is hopefully clear.    Con: We'll be adding a lot of go libraries to our manifest. Assuming all are available via git.    Con: Maintenance headache.  Create spec files and compile rpms for the transitive set of imports. When do we upversion the rpms?    Con: More packages we need to build 2) Allow our new go packages to include a pre-populated vendor sub-directory.    Pro: Don't require network access to build    Pro: Reproducible builds    Con: We store snapshots of 3rd party code in the same src.rpm as our own code.    Con: More complicated licensing statements.    Con: Maintenance headache.  When do we upversion the snapshots? Who want's to code inspect the mess?    Con: If we have many go packages, there may multiple copies of the same library spread through our code base.    Con: Is StarlingX, and OpenStack, ok with all the go code snapshots being added to our gits? 3) Use 'dep init' to create a lock file.  Deliver only the lock file alongside our go code.  Use 'dep ensure' during the build to download the required libraries.    Pro: Lowest maintenance on our part    Pro: Don't need to store a snapshot of any go libraries, nor add it too our manifest.    Con: Need network access to build, not just in the docker container, but all the way down to the mock instance.    Con: Relies on the upstream server continuing to host the package.    Con: Relies on stability of upstream server and it's network connectivity.  Vast majority of packages seem to come from golang.org, github and go.googlesource.com, so not likely a concern. I'm inclined to option 3. Opinions? Scott From vm.rod25 at gmail.com Fri Nov 23 22:13:07 2018 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Fri, 23 Nov 2018 16:13:07 -0600 Subject: [Starlingx-discuss] [multi-os] Spec for stx multi OS architecture Message-ID: Hi This is the spec for the multi os architecture: https://review.openstack.org/#/c/619801/ Regards Victor Rodriguez From vm.rod25 at gmail.com Fri Nov 23 22:30:40 2018 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Fri, 23 Nov 2018 16:30:40 -0600 Subject: [Starlingx-discuss] [Build] go loanguage In-Reply-To: <5c031adb-1e32-37c5-2f88-0720e11bd569@windriver.com> References: <5c031adb-1e32-37c5-2f88-0720e11bd569@windriver.com> Message-ID: On Fri, Nov 23, 2018 at 1:48 PM Scott Little wrote: > > I have a designer that want to introduce a GO language package into our > build. This raises the question of how to handle GO's 'imports'. > > First a disclaimer. I'm not a 'GO' exports. The following discussion > points are based on my brief research. > > Go imports are roughly akin to a 'C' language include, with one or few > major differences. > 1) It points to a directory rather than a file, which could be local or > relative to your GOPATH > 2) The convention is to use a path that is a crude approximation of the > url from which it can be obtained. e.g. import ( > "github.com/docker/distribution/registry/api/errcode" ) > 3) If the directory is NOT already present, it can probably be > downloaded automatically with tools like 'go get' or 'dep' (aka > golang-dep). These tools attempt transform the path into a URI, trying > several vcs download protocols (git, mercurial, subversion...). > Downloads are stored under a local 'vendor' sub-directory. There are a > few wrinkles, like the ability of a sire to respond with a re-direct to > another site. > > There are centos rpms for a handful of core libraries, delivering code > to /usr/share/gocode (part of your GOPATH). However most go code has > never been published as an rpm, and much of the remainder seems to be a > one off rpm, with no ongoing maintenance. > > 'go get' just seems to grab the latest code. Reproducibility is a big > concern. > > 'dep init' solves the reproducibility concern. It grabs the latest > code, but also generates a 'lock' file that capture a CVS commit > identifier (e.g. a git SHA). Deliver the lock file with your code and > 'dep ensure' will use the lock file to download the same code every > time. Dep does not currently ship as an RPM. I have a working spec > file for dep 0.4.1. Dep 0.5.0 needs more work. > For me it works : curl https://raw.githubusercontent.com/golang/dep/master/install.sh | sh > Licenses of public go libraries seem to be permissive, at least for a > statically linked binary, which is what we would want to ship. Not so > sure about the inclusion of library source as an embedded vendor > sub-directory in our own src.rpm packages. That would be one for the > lawyers. > > > So our options seem to be. > 1) Create rpms of all the go libraries we need, populating > /usr/share/gocode. There might be some tooling available to help with this. > Pro: Don't require network access to build. > Pro: Reproducible builds > Pro: License of each go rpm is hopefully clear. > Con: We'll be adding a lot of go libraries to our manifest. Assuming > all are available via git. > Con: Maintenance headache. Create spec files and compile rpms for > the transitive set of imports. When do we upversion the rpms? > Con: More packages we need to build > > 2) Allow our new go packages to include a pre-populated vendor > sub-directory. > Pro: Don't require network access to build > Pro: Reproducible builds > Con: We store snapshots of 3rd party code in the same src.rpm as our > own code. > Con: More complicated licensing statements. > Con: Maintenance headache. When do we upversion the snapshots? Who > want's to code inspect the mess? > Con: If we have many go packages, there may multiple copies of the > same library spread through our code base. > Con: Is StarlingX, and OpenStack, ok with all the go code snapshots > being added to our gits? > > 3) Use 'dep init' to create a lock file. Deliver only the lock file > alongside our go code. Use 'dep ensure' during the build to download > the required libraries. > Pro: Lowest maintenance on our part > Pro: Don't need to store a snapshot of any go libraries, nor add it > too our manifest. > Con: Need network access to build, not just in the docker container, > but all the way down to the mock instance. > Con: Relies on the upstream server continuing to host the package. > Con: Relies on stability of upstream server and it's network > connectivity. Vast majority of packages seem to come from golang.org, > github and go.googlesource.com, so not likely a concern. > > I'm inclined to option 3. > I am in favor of providing both go get and dep since they are for different reasons https://github.com/golang/dep/issues/376 > Opinions? > > Scott > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From changcheng.liu at intel.com Sun Nov 25 04:36:31 2018 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Sun, 25 Nov 2018 04:36:31 +0000 Subject: [Starlingx-discuss] stx-tools: setup stx build environment In-Reply-To: <4355461542980237@sas1-87f9feb8d943.qloud-c.yandex.net> References: <0D7994A90DD70040A9F5E77C4D23C57D50EFAF5F@SHSMSX104.ccr.corp.intel.com> <0D7994A90DD70040A9F5E77C4D23C57D50EF931C@SHSMSX104.ccr.corp.intel.com> <4355461542980237@sas1-87f9feb8d943.qloud-c.yandex.net> Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50EFB3F0@SHSMSX104.ccr.corp.intel.com> Hi Erich, Is there anything wrong with proxy env in container as below? [nstcc1 at d8ae703a2a91 /]$ env | grep -i proxy NO_PROXY=localhost,.intel.com,127.0.0.0/8,172,16.0.0/20,192.168.0.0/16,10.0.0.0/8 http_proxy=http://child-prc.intel.com:913 FTP_PROXY=ftp://child-prc.intel.com:913 ftp_proxy=ftp://child-prc.intel.com:913 https_proxy=http://child-prc.intel.com:913 HTTPS_PROXY=http://child-prc.intel.com:913 no_proxy=localhost,.intel.com,127.0.0.0/8,172,16.0.0/20,192.168.0.0/16,10.0.0.0/8 HTTP_PROXY=http://child-prc.intel.com:913 B.R. Changcheng From: Erich Cordoba [mailto:erich.cm.lists at yandex.com] Sent: Friday, November 23, 2018 9:37 PM To: 'starlingx-discuss at lists.starlingx.io' ; Cordoba Malibran, Erich ; Liu, Changcheng Subject: Re: [Starlingx-discuss] stx-tools: setup stx build environment Hi Liu, As you need to setup a proxy, you need also to set the no_proxy=127.0.0.1 env variable, so mock can find the internal repository. This is something that we need to do in our internal build job. -Erich -- Sent from Yandex.Mail for mobile 23.11.2018, 07:27, "Liu, Changcheng" >: Hi Erich, I hit lots of error when executing “build-pkgs”. Please help check it. https://bugs.launchpad.net/starlingx/+bug/1804412 1. get stx-tools cd $HOME git clone https://git.starlingx.io/stx-tools cd stx-tools git checkout -b erich_base 1d2ecbb0be2 2. apply below patch nstcc1 at nstcloudcc1:stx-tools$ git diff Dockerfile tb.sh Makefile diff --git a/Dockerfile b/Dockerfile index 87ef00b..dd730f9 100644 --- a/Dockerfile +++ b/Dockerfile @@ -13,9 +13,9 @@ FROM centos:7.4.1708 # Proxy configuration -#ENV http_proxy "http://your.actual_http_proxy.com:your_port" -#ENV https_proxy "https://your.actual_https_proxy.com:your_port" -#ENV ftp_proxy "http://your.actual_ftp_proxy.com:your_port" +ENV http_proxy "http://child-prc.intel.com:913" +ENV https_proxy "http://child-prc.intel.com:913" +ENV ftp_proxy "ftp://child-prc.intel.com:913" # username you will docker exec into the container as. @@ -26,6 +26,8 @@ ARG MYUID=1000 ENV container=docker +RUN echo "proxy=$http_proxy" >> /etc/yum.conf && \ +echo -e "export http_proxy=$http_proxy\nexport https_proxy=$https_proxy\nexport ftp_proxy=$ftp_proxy" >> /root/.bashrc # Download required dependencies by mirror/build processes. # Notice there are 3 invocations to yum package manage. # 1) Enable EPEL repository. diff --git a/Makefile b/Makefile index c4ebff4..73f5f3a 100644 --- a/Makefile +++ b/Makefile @@ -20,6 +20,8 @@ all: docker build \ --build-arg MYUID=$(UID) \ --build-arg MYUNAME=$(MYUNAME) \ + --build-arg https_proxy=http://child-prc.intel.com:913 \ + --build-arg http_proxy=http://child-prc.intel.com:913 \ --ulimit core=0 \ --network host \ -t $(TC_CONTAINER_TAG) \ diff --git a/tb.sh b/tb.sh index e0508dd..9530efd 100755 --- a/tb.sh +++ b/tb.sh @@ -38,11 +38,14 @@ function run_container { docker run -it --rm \ --name ${TC_CONTAINER_NAME} \ --detach \ + -v /etc/localtime:/etc/localtime:ro \ -v ${LOCALDISK}:/${GUEST_LOCALDISK} \ -v ${HOST_MIRROR_DIR}:/import/mirrors:ro \ -v /sys/fs/cgroup:/sys/fs/cgroup:ro \ -v ~/.ssh:/mySSH:ro \ -e "container=docker" \ + --env https_proxy=http://child-prc.intel.com:913 \ + --env http_proxy=http://child-prc.intel.com:913 \ -e MYUNAME=${MYUNAME} \ --privileged=true \ --security-opt seccomp=unconfined \ 3. build docker image make all 4. run docker image bash tb.sh run 5. execute into docker container bash tb.sh exec 6. [nstcc1 at d8ae703a2a91 /]$ eval $(ssh-agent) Agent pid 15524 [nstcc1 at d8ae703a2a91 /]$ ssh-add Identity added: /home/nstcc1/.ssh/id_rsa (/home/nstcc1/.ssh/id_rsa) [nstcc1 at d8ae703a2a91 /]$ cd $MY_REPO_ROOT_DIR [nstcc1 at d8ae703a2a91 starlingx]$ repo init -u https://git.starlingx.io/stx-manifest -m default.xml [nstcc1 at d8ae703a2a91 starlingx]$ repo sync -j4 [nstcc1 at d8ae703a2a91 starlingx]$ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/stx/ [nstcc1 at d8ae703a2a91 starlingx]$ populate_downloads.sh /import/mirrors/CentOS/stx-r1/CentOS/pike/ 7. nstcc1 at nstcloudcc1:~$ mkdir -p $HOME/starlingx/mirror/CentOS/tis-installer nstcc1 at nstcloudcc1:~$ cp $HOME/starlingx/mirror/CentOS/stx-r1/CentOS/pike/Binary/images/pxeboot/initrd.img $HOME/starlingx/mirror/CentOS/tis-installer/initrd.img-stx-0.2 nstcc1 at nstcloudcc1:~$ cp $HOME/starlingx/mirror/CentOS/stx-r1/CentOS/pike/Binary/images/pxeboot/vmlinuz $HOME/starlingx/mirror/CentOS/tis-installer/vmlinuz-stx-0.2 nstcc1 at nstcloudcc1:~$ cp $HOME/starlingx/mirror/CentOS/stx-r1/CentOS/pike/Binary/LiveOS/squashfs.img $HOME/starlingx/mirror/CentOS/tis-installer/squashfs.img-stx-0.2 8. [nstcc1 at d8ae703a2a91 starlingx]$ generate-cgcs-centos-repo.sh /import/mirrors/CentOS/stx-r1/CentOS/pike/ 9. [nstcc1 at d8ae703a2a91 starlingx]$ build-pkgs Then, hit lots of error, the log is build-pkgs.log 21:10:47 failure: repodata/repomd.xml from TisCentos7Distro: [Errno 256] No more mirrors to try. 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 21:10:47 End build on 'b0': /localdisk/loadbuild/nstcc1/starlingx/std/rpmbuild/SRPMS/mariadb-10.1.28-1.el7.tis.15.src.rpm 21:10:47 Error building mariadb-10.1.28-1.el7.tis.15.src.rpm on 'b0'. --Thanks Changcheng From: Liu, Changcheng Sent: Friday, November 23, 2018 12:16 AM To: 'starlingx-discuss at lists.starlingx.io' >; Cordoba Malibran, Erich > Subject: RE: stx-tools: setup stx build environment Hi Erich, I still met with some problems after following your method to run “download_mirror.sh”. Please check the comment in https://bugs.launchpad.net/starlingx/+bug/1804412 [root at 90104f541da1 logs]# wc -l * 0 K1_failmoved_url_centos.log 0 K1_rpms_found_centos.log 0 K1_rpms_missing_centos.log 0 K1_srpms_found_centos.log 0 K1_srpms_missing_centos.log 46 L1_failmoved_url_3rdparties.log 5306 L1_failmoved_url_centos.log 394 L1_failmoved_url_centos3rdparties.log 0 L1_rpms_found_3rdparties.log 0 L1_rpms_found_centos.log 0 L1_rpms_found_centos3rdparties.log 0 L1_rpms_missing_3rdparties.log 0 L1_rpms_missing_centos.log 0 L1_rpms_missing_centos3rdparties.log 23 L1_srpms_found_3rdparties.log 1936 L1_srpms_found_centos.log 148 L1_srpms_found_centos3rdparties.log 0 L1_srpms_missing_3rdparties.log 0 L1_srpms_missing_centos.log 0 L1_srpms_missing_centos3rdparties.log 590 all_i686.txt 9858 otherfiles_centos_download.log 1 rpm-gpg-key-missing.txt 80 rpms_3rdparties_download_L1.log 490 rpms_centos3rdparties_download_L1.log 2 rpms_centos_download_K1.log 6735 rpms_centos_download_L1.log 57768 tarballs_download.log 83377 total [root at 90104f541da1 logs]# I don’t know whether the “failmoved” packages will affect the ISO image build or not. I’m building another docker image for building ISO image. --Changcheng From: Liu, Changcheng Sent: Wednesday, November 21, 2018 11:24 PM To: 'starlingx-discuss at lists.starlingx.io' >; Cordoba Malibran, Erich > Subject: RE: stx-tools: setup stx build environment Hi Erich, Please help check the problem. Tell me if you need more information. I’m trying to run “download_mirror.sh” again. B.R. Changcheng From: Liu, Changcheng Sent: Wednesday, November 21, 2018 6:35 PM To: 'starlingx-discuss at lists.starlingx.io' > Subject: stx-tools: setup stx build environment Could someone help check below bug? Title: stx-tools: failed to download required packaged Link: https://bugs.launchpad.net/starlingx/+bug/1804412 B.R. Changcheng From: Liu, Changcheng Sent: Friday, November 16, 2018 8:31 PM To: starlingx-discuss at lists.starlingx.io Subject: setup stx build environment Hi all, I have one question about setting up stx build environment. Why not move lots of many basic program installation process from mirror-check.sh to Dockerfile directly? Then stx community could supply one basic docker image as the base image to let developer customize it. Currently, I still need install lots of program after building Dockerfile into image. B.R. Changcheng _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From liang.a.fang at intel.com Sun Nov 25 16:44:03 2018 From: liang.a.fang at intel.com (Fang, Liang A) Date: Sun, 25 Nov 2018 16:44:03 +0000 Subject: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming Message-ID: Hi Irina Code review: https://review.openstack.org/#/c/618976/ I'm working of upstreaming this patch. Could you please help to address one doubt: why image is converted in the same location with image itself? This patch is to create a volume from image, right? I take a look of related code, the destination location would be the newly created volume and the source location is configured in cinder.conf, something like: image_conversion_dir = /mnt/d100m/image_conversion_dir I did an experiment, in the latest master branch of cinder upstream repo: - If image_conversion_dir has no space to store the downloading image, the exception ImageTooBig will be caught in the beginning of _create_from_image_cache_or_download(). - If has space to store the image, but dest volume size is smaller than image's virtual size, an exception "ImageUnacceptable" will raised by check_virtual_size. So it seems no chance to go to the situation this patch aimed to solve. Could you please help to give more background of this patch? Or if you think this patch is invalid now, please just tell me, I will mark this patch as abandoned. Thanks Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Mon Nov 26 01:00:34 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Mon, 26 Nov 2018 01:00:34 +0000 Subject: [Starlingx-discuss] Refactor task related: Bind config package 1:1 with original package Message-ID: <9700A18779F35F49AF027300A49E7C765FE3E4DB@SHSMSX101.ccr.corp.intel.com> Hi all, In recent refactor task [0], we created several config packages to handle configuration files related patch in original package. Such as initscripts-config (stx-integ/base/initscripts-config) package for initscripts (stx-integ/base/initscripts). For these two packages, we set initscripts-config depends on initscripts in spec file currently like below: Requires: initscripts (from initscripts-config.spec) I prefer to add specific version info into this field, like below: BuildRequires: systemd = 219-57.el7 (from systemd-config.spec) Requires: systemd The reason is that, if we upgrade original package only, but forget to upgrade config package, it may cause potential issue if the new package also modified config files in the config package. With the specific version info in the Requires field, build will break to reminder the upgrader to check the config package. This case will have more chance to happen when the original package is already replaced with RPM, such as iptables-config. With this change, it means upgrader need upgrade both packages together, regardless there is change in the configuration file or not. Please share your thoughts with me. Thanks. [0]: https://storyboard.openstack.org/#!/story/2003768 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From changcheng.liu at intel.com Mon Nov 26 01:28:15 2018 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Mon, 26 Nov 2018 01:28:15 +0000 Subject: [Starlingx-discuss] stx-tools: setup stx build environment References: <0D7994A90DD70040A9F5E77C4D23C57D50EFAF5F@SHSMSX104.ccr.corp.intel.com> <0D7994A90DD70040A9F5E77C4D23C57D50EF931C@SHSMSX104.ccr.corp.intel.com> <4355461542980237@sas1-87f9feb8d943.qloud-c.yandex.net> <0D7994A90DD70040A9F5E77C4D23C57D50EFB3F0@SHSMSX104.ccr.corp.intel.com> Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50EFB7D5@SHSMSX104.ccr.corp.intel.com> Hi Yong, Yes. The proxy should be right. But the error is still there. BTW, I also hit below error: 09:23:46 b3: INFO: mounting tmpfs at /localdisk/loadbuild/nstcc1/starlingx/std/mock/b3/root. 09:23:46 b3: ERROR: Command failed: 09:23:46 b3: # mount -n -t tmpfs -o mode=0755 -o nr_inodes=0 -o size=11g mock_chroot_tmpfs /localdisk/loadbuild/nstcc1/starlingx/std/mock/b3/root B.R. Changcheng From: Hu, Yong Sent: Monday, November 26, 2018 9:10 AM To: Liu, Changcheng >; Erich Cordoba >; 'starlingx-discuss at lists.starlingx.io' >; Cordoba Malibran, Erich > Subject: Re: [Starlingx-discuss] stx-tools: setup stx build environment Your no_proxy env setting should resolve the following error, are you still seeing it? 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable From: "Liu, Changcheng" > Date: Sunday, 25 November 2018 at 3:24 PM To: Erich Cordoba >, "'starlingx-discuss at lists.starlingx.io'" >, "Cordoba Malibran, Erich" > Subject: Re: [Starlingx-discuss] stx-tools: setup stx build environment Hi Erich, Is there anything wrong with proxy env in container as below? [nstcc1 at d8ae703a2a91 /]$ env | grep -i proxy NO_PROXY=localhost,.intel.com,127.0.0.0/8,172,16.0.0/20,192.168.0.0/16,10.0.0.0/8 http_proxy=http://child-prc.intel.com:913 FTP_PROXY=ftp://child-prc.intel.com:913 ftp_proxy=ftp://child-prc.intel.com:913 https_proxy=http://child-prc.intel.com:913 HTTPS_PROXY=http://child-prc.intel.com:913 no_proxy=localhost,.intel.com,127.0.0.0/8,172,16.0.0/20,192.168.0.0/16,10.0.0.0/8 HTTP_PROXY=http://child-prc.intel.com:913 B.R. Changcheng From: Erich Cordoba [mailto:erich.cm.lists at yandex.com] Sent: Friday, November 23, 2018 9:37 PM To: 'starlingx-discuss at lists.starlingx.io' >; Cordoba Malibran, Erich >; Liu, Changcheng > Subject: Re: [Starlingx-discuss] stx-tools: setup stx build environment Hi Liu, As you need to setup a proxy, you need also to set the no_proxy=127.0.0.1 env variable, so mock can find the internal repository. This is something that we need to do in our internal build job. -Erich -- Sent from Yandex.Mail for mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Mon Nov 26 01:35:34 2018 From: yong.hu at intel.com (Hu, Yong) Date: Mon, 26 Nov 2018 01:35:34 +0000 Subject: [Starlingx-discuss] stx-tools: setup stx build environment In-Reply-To: <0D7994A90DD70040A9F5E77C4D23C57D50EFB7D5@SHSMSX104.ccr.corp.intel.com> References: <0D7994A90DD70040A9F5E77C4D23C57D50EFAF5F@SHSMSX104.ccr.corp.intel.com> <0D7994A90DD70040A9F5E77C4D23C57D50EF931C@SHSMSX104.ccr.corp.intel.com> <4355461542980237@sas1-87f9feb8d943.qloud-c.yandex.net> <0D7994A90DD70040A9F5E77C4D23C57D50EFB3F0@SHSMSX104.ccr.corp.intel.com> <0D7994A90DD70040A9F5E77C4D23C57D50EFB7D5@SHSMSX104.ccr.corp.intel.com> Message-ID: <4E302436-B560-49F8-93F5-8D0173CBDF33@intel.com> You can use this command to fix the limitation issue in your build container (CentOS): sudo sed -i 's/nr_inodes=0/nr_inodes=100k/g' /usr/lib/python2.7/site-packages/mockbuild/plugins/tmpfs.py From: "Liu, Changcheng" Date: Monday, 26 November 2018 at 9:28 AM To: "Hu, Yong" , Erich Cordoba , "'starlingx-discuss at lists.starlingx.io'" , "Cordoba Malibran, Erich" Subject: RE: [Starlingx-discuss] stx-tools: setup stx build environment Hi Yong, Yes. The proxy should be right. But the error is still there. BTW, I also hit below error: 09:23:46 b3: INFO: mounting tmpfs at /localdisk/loadbuild/nstcc1/starlingx/std/mock/b3/root. 09:23:46 b3: ERROR: Command failed: 09:23:46 b3: # mount -n -t tmpfs -o mode=0755 -o nr_inodes=0 -o size=11g mock_chroot_tmpfs /localdisk/loadbuild/nstcc1/starlingx/std/mock/b3/root B.R. Changcheng From: Hu, Yong Sent: Monday, November 26, 2018 9:10 AM To: Liu, Changcheng >; Erich Cordoba >; 'starlingx-discuss at lists.starlingx.io' >; Cordoba Malibran, Erich > Subject: Re: [Starlingx-discuss] stx-tools: setup stx build environment Your no_proxy env setting should resolve the following error, are you still seeing it? 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable From: "Liu, Changcheng" > Date: Sunday, 25 November 2018 at 3:24 PM To: Erich Cordoba >, "'starlingx-discuss at lists.starlingx.io'" >, "Cordoba Malibran, Erich" > Subject: Re: [Starlingx-discuss] stx-tools: setup stx build environment Hi Erich, Is there anything wrong with proxy env in container as below? [nstcc1 at d8ae703a2a91 /]$ env | grep -i proxy NO_PROXY=localhost,.intel.com,127.0.0.0/8,172,16.0.0/20,192.168.0.0/16,10.0.0.0/8 http_proxy=http://child-prc.intel.com:913 FTP_PROXY=ftp://child-prc.intel.com:913 ftp_proxy=ftp://child-prc.intel.com:913 https_proxy=http://child-prc.intel.com:913 HTTPS_PROXY=http://child-prc.intel.com:913 no_proxy=localhost,.intel.com,127.0.0.0/8,172,16.0.0/20,192.168.0.0/16,10.0.0.0/8 HTTP_PROXY=http://child-prc.intel.com:913 B.R. Changcheng From: Erich Cordoba [mailto:erich.cm.lists at yandex.com] Sent: Friday, November 23, 2018 9:37 PM To: 'starlingx-discuss at lists.starlingx.io' >; Cordoba Malibran, Erich >; Liu, Changcheng > Subject: Re: [Starlingx-discuss] stx-tools: setup stx build environment Hi Liu, As you need to setup a proxy, you need also to set the no_proxy=127.0.0.1 env variable, so mock can find the internal repository. This is something that we need to do in our internal build job. -Erich -- Sent from Yandex.Mail for mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: From changcheng.liu at intel.com Mon Nov 26 01:45:33 2018 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Mon, 26 Nov 2018 01:45:33 +0000 Subject: [Starlingx-discuss] stx-tools: setup stx build environment In-Reply-To: <4E302436-B560-49F8-93F5-8D0173CBDF33@intel.com> References: <0D7994A90DD70040A9F5E77C4D23C57D50EFAF5F@SHSMSX104.ccr.corp.intel.com> <0D7994A90DD70040A9F5E77C4D23C57D50EF931C@SHSMSX104.ccr.corp.intel.com> <4355461542980237@sas1-87f9feb8d943.qloud-c.yandex.net> <0D7994A90DD70040A9F5E77C4D23C57D50EFB3F0@SHSMSX104.ccr.corp.intel.com> <0D7994A90DD70040A9F5E77C4D23C57D50EFB7D5@SHSMSX104.ccr.corp.intel.com> <4E302436-B560-49F8-93F5-8D0173CBDF33@intel.com> Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50EFB807@SHSMSX104.ccr.corp.intel.com> Hi Yong, Thanks for your BKM sharing. With your method, “build-pkgs” is running without serious error until now. I’ll feedback the build result later. B.R. Changcheng From: Hu, Yong Sent: Monday, November 26, 2018 9:36 AM To: Liu, Changcheng ; Erich Cordoba ; 'starlingx-discuss at lists.starlingx.io' ; Cordoba Malibran, Erich Subject: Re: [Starlingx-discuss] stx-tools: setup stx build environment You can use this command to fix the limitation issue in your build container (CentOS): sudo sed -i 's/nr_inodes=0/nr_inodes=100k/g' /usr/lib/python2.7/site-packages/mockbuild/plugins/tmpfs.py From: "Liu, Changcheng" > Date: Monday, 26 November 2018 at 9:28 AM To: "Hu, Yong" >, Erich Cordoba >, "'starlingx-discuss at lists.starlingx.io'" >, "Cordoba Malibran, Erich" > Subject: RE: [Starlingx-discuss] stx-tools: setup stx build environment Hi Yong, Yes. The proxy should be right. But the error is still there. BTW, I also hit below error: 09:23:46 b3: INFO: mounting tmpfs at /localdisk/loadbuild/nstcc1/starlingx/std/mock/b3/root. 09:23:46 b3: ERROR: Command failed: 09:23:46 b3: # mount -n -t tmpfs -o mode=0755 -o nr_inodes=0 -o size=11g mock_chroot_tmpfs /localdisk/loadbuild/nstcc1/starlingx/std/mock/b3/root B.R. Changcheng From: Hu, Yong Sent: Monday, November 26, 2018 9:10 AM To: Liu, Changcheng >; Erich Cordoba >; 'starlingx-discuss at lists.starlingx.io' >; Cordoba Malibran, Erich > Subject: Re: [Starlingx-discuss] stx-tools: setup stx build environment Your no_proxy env setting should resolve the following error, are you still seeing it? 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable From: "Liu, Changcheng" > Date: Sunday, 25 November 2018 at 3:24 PM To: Erich Cordoba >, "'starlingx-discuss at lists.starlingx.io'" >, "Cordoba Malibran, Erich" > Subject: Re: [Starlingx-discuss] stx-tools: setup stx build environment Hi Erich, Is there anything wrong with proxy env in container as below? [nstcc1 at d8ae703a2a91 /]$ env | grep -i proxy NO_PROXY=localhost,.intel.com,127.0.0.0/8,172,16.0.0/20,192.168.0.0/16,10.0.0.0/8 http_proxy=http://child-prc.intel.com:913 FTP_PROXY=ftp://child-prc.intel.com:913 ftp_proxy=ftp://child-prc.intel.com:913 https_proxy=http://child-prc.intel.com:913 HTTPS_PROXY=http://child-prc.intel.com:913 no_proxy=localhost,.intel.com,127.0.0.0/8,172,16.0.0/20,192.168.0.0/16,10.0.0.0/8 HTTP_PROXY=http://child-prc.intel.com:913 B.R. Changcheng From: Erich Cordoba [mailto:erich.cm.lists at yandex.com] Sent: Friday, November 23, 2018 9:37 PM To: 'starlingx-discuss at lists.starlingx.io' >; Cordoba Malibran, Erich >; Liu, Changcheng > Subject: Re: [Starlingx-discuss] stx-tools: setup stx build environment Hi Liu, As you need to setup a proxy, you need also to set the no_proxy=127.0.0.1 env variable, so mock can find the internal repository. This is something that we need to do in our internal build job. -Erich -- Sent from Yandex.Mail for mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Mon Nov 26 01:10:19 2018 From: yong.hu at intel.com (Hu, Yong) Date: Mon, 26 Nov 2018 01:10:19 +0000 Subject: [Starlingx-discuss] stx-tools: setup stx build environment In-Reply-To: <0D7994A90DD70040A9F5E77C4D23C57D50EFB3F0@SHSMSX104.ccr.corp.intel.com> References: <0D7994A90DD70040A9F5E77C4D23C57D50EFAF5F@SHSMSX104.ccr.corp.intel.com> <0D7994A90DD70040A9F5E77C4D23C57D50EF931C@SHSMSX104.ccr.corp.intel.com> <4355461542980237@sas1-87f9feb8d943.qloud-c.yandex.net> <0D7994A90DD70040A9F5E77C4D23C57D50EFB3F0@SHSMSX104.ccr.corp.intel.com> Message-ID: Your no_proxy env setting should resolve the following error, are you still seeing it? 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable From: "Liu, Changcheng" Date: Sunday, 25 November 2018 at 3:24 PM To: Erich Cordoba , "'starlingx-discuss at lists.starlingx.io'" , "Cordoba Malibran, Erich" Subject: Re: [Starlingx-discuss] stx-tools: setup stx build environment Hi Erich, Is there anything wrong with proxy env in container as below? [nstcc1 at d8ae703a2a91 /]$ env | grep -i proxy NO_PROXY=localhost,.intel.com,127.0.0.0/8,172,16.0.0/20,192.168.0.0/16,10.0.0.0/8 http_proxy=http://child-prc.intel.com:913 FTP_PROXY=ftp://child-prc.intel.com:913 ftp_proxy=ftp://child-prc.intel.com:913 https_proxy=http://child-prc.intel.com:913 HTTPS_PROXY=http://child-prc.intel.com:913 no_proxy=localhost,.intel.com,127.0.0.0/8,172,16.0.0/20,192.168.0.0/16,10.0.0.0/8 HTTP_PROXY=http://child-prc.intel.com:913 B.R. Changcheng From: Erich Cordoba [mailto:erich.cm.lists at yandex.com] Sent: Friday, November 23, 2018 9:37 PM To: 'starlingx-discuss at lists.starlingx.io' ; Cordoba Malibran, Erich ; Liu, Changcheng Subject: Re: [Starlingx-discuss] stx-tools: setup stx build environment Hi Liu, As you need to setup a proxy, you need also to set the no_proxy=127.0.0.1 env variable, so mock can find the internal repository. This is something that we need to do in our internal build job. -Erich -- Sent from Yandex.Mail for mobile 23.11.2018, 07:27, "Liu, Changcheng" >: Hi Erich, I hit lots of error when executing “build-pkgs”. Please help check it. https://bugs.launchpad.net/starlingx/+bug/1804412 1. get stx-tools cd $HOME git clone https://git.starlingx.io/stx-tools cd stx-tools git checkout -b erich_base 1d2ecbb0be2 2. apply below patch nstcc1 at nstcloudcc1:stx-tools$ git diff Dockerfile tb.sh Makefile diff --git a/Dockerfile b/Dockerfile index 87ef00b..dd730f9 100644 --- a/Dockerfile +++ b/Dockerfile @@ -13,9 +13,9 @@ FROM centos:7.4.1708 # Proxy configuration -#ENV http_proxy "http://your.actual_http_proxy.com:your_port" -#ENV https_proxy "https://your.actual_https_proxy.com:your_port" -#ENV ftp_proxy "http://your.actual_ftp_proxy.com:your_port" +ENV http_proxy "http://child-prc.intel.com:913" +ENV https_proxy "http://child-prc.intel.com:913" +ENV ftp_proxy "ftp://child-prc.intel.com:913" # username you will docker exec into the container as. @@ -26,6 +26,8 @@ ARG MYUID=1000 ENV container=docker +RUN echo "proxy=$http_proxy" >> /etc/yum.conf && \ +echo -e "export http_proxy=$http_proxy\nexport https_proxy=$https_proxy\nexport ftp_proxy=$ftp_proxy" >> /root/.bashrc # Download required dependencies by mirror/build processes. # Notice there are 3 invocations to yum package manage. # 1) Enable EPEL repository. diff --git a/Makefile b/Makefile index c4ebff4..73f5f3a 100644 --- a/Makefile +++ b/Makefile @@ -20,6 +20,8 @@ all: docker build \ --build-arg MYUID=$(UID) \ --build-arg MYUNAME=$(MYUNAME) \ + --build-arg https_proxy=http://child-prc.intel.com:913 \ + --build-arg http_proxy=http://child-prc.intel.com:913 \ --ulimit core=0 \ --network host \ -t $(TC_CONTAINER_TAG) \ diff --git a/tb.sh b/tb.sh index e0508dd..9530efd 100755 --- a/tb.sh +++ b/tb.sh @@ -38,11 +38,14 @@ function run_container { docker run -it --rm \ --name ${TC_CONTAINER_NAME} \ --detach \ + -v /etc/localtime:/etc/localtime:ro \ -v ${LOCALDISK}:/${GUEST_LOCALDISK} \ -v ${HOST_MIRROR_DIR}:/import/mirrors:ro \ -v /sys/fs/cgroup:/sys/fs/cgroup:ro \ -v ~/.ssh:/mySSH:ro \ -e "container=docker" \ + --env https_proxy=http://child-prc.intel.com:913 \ + --env http_proxy=http://child-prc.intel.com:913 \ -e MYUNAME=${MYUNAME} \ --privileged=true \ --security-opt seccomp=unconfined \ 3. build docker image make all 4. run docker image bash tb.sh run 5. execute into docker container bash tb.sh exec 6. [nstcc1 at d8ae703a2a91 /]$ eval $(ssh-agent) Agent pid 15524 [nstcc1 at d8ae703a2a91 /]$ ssh-add Identity added: /home/nstcc1/.ssh/id_rsa (/home/nstcc1/.ssh/id_rsa) [nstcc1 at d8ae703a2a91 /]$ cd $MY_REPO_ROOT_DIR [nstcc1 at d8ae703a2a91 starlingx]$ repo init -u https://git.starlingx.io/stx-manifest -m default.xml [nstcc1 at d8ae703a2a91 starlingx]$ repo sync -j4 [nstcc1 at d8ae703a2a91 starlingx]$ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/stx/ [nstcc1 at d8ae703a2a91 starlingx]$ populate_downloads.sh /import/mirrors/CentOS/stx-r1/CentOS/pike/ 7. nstcc1 at nstcloudcc1:~$ mkdir -p $HOME/starlingx/mirror/CentOS/tis-installer nstcc1 at nstcloudcc1:~$ cp $HOME/starlingx/mirror/CentOS/stx-r1/CentOS/pike/Binary/images/pxeboot/initrd.img $HOME/starlingx/mirror/CentOS/tis-installer/initrd.img-stx-0.2 nstcc1 at nstcloudcc1:~$ cp $HOME/starlingx/mirror/CentOS/stx-r1/CentOS/pike/Binary/images/pxeboot/vmlinuz $HOME/starlingx/mirror/CentOS/tis-installer/vmlinuz-stx-0.2 nstcc1 at nstcloudcc1:~$ cp $HOME/starlingx/mirror/CentOS/stx-r1/CentOS/pike/Binary/LiveOS/squashfs.img $HOME/starlingx/mirror/CentOS/tis-installer/squashfs.img-stx-0.2 8. [nstcc1 at d8ae703a2a91 starlingx]$ generate-cgcs-centos-repo.sh /import/mirrors/CentOS/stx-r1/CentOS/pike/ 9. [nstcc1 at d8ae703a2a91 starlingx]$ build-pkgs Then, hit lots of error, the log is build-pkgs.log 21:10:47 failure: repodata/repomd.xml from TisCentos7Distro: [Errno 256] No more mirrors to try. 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 21:10:47 End build on 'b0': /localdisk/loadbuild/nstcc1/starlingx/std/rpmbuild/SRPMS/mariadb-10.1.28-1.el7.tis.15.src.rpm 21:10:47 Error building mariadb-10.1.28-1.el7.tis.15.src.rpm on 'b0'. --Thanks Changcheng From: Liu, Changcheng Sent: Friday, November 23, 2018 12:16 AM To: 'starlingx-discuss at lists.starlingx.io' >; Cordoba Malibran, Erich > Subject: RE: stx-tools: setup stx build environment Hi Erich, I still met with some problems after following your method to run “download_mirror.sh”. Please check the comment in https://bugs.launchpad.net/starlingx/+bug/1804412 [root at 90104f541da1 logs]# wc -l * 0 K1_failmoved_url_centos.log 0 K1_rpms_found_centos.log 0 K1_rpms_missing_centos.log 0 K1_srpms_found_centos.log 0 K1_srpms_missing_centos.log 46 L1_failmoved_url_3rdparties.log 5306 L1_failmoved_url_centos.log 394 L1_failmoved_url_centos3rdparties.log 0 L1_rpms_found_3rdparties.log 0 L1_rpms_found_centos.log 0 L1_rpms_found_centos3rdparties.log 0 L1_rpms_missing_3rdparties.log 0 L1_rpms_missing_centos.log 0 L1_rpms_missing_centos3rdparties.log 23 L1_srpms_found_3rdparties.log 1936 L1_srpms_found_centos.log 148 L1_srpms_found_centos3rdparties.log 0 L1_srpms_missing_3rdparties.log 0 L1_srpms_missing_centos.log 0 L1_srpms_missing_centos3rdparties.log 590 all_i686.txt 9858 otherfiles_centos_download.log 1 rpm-gpg-key-missing.txt 80 rpms_3rdparties_download_L1.log 490 rpms_centos3rdparties_download_L1.log 2 rpms_centos_download_K1.log 6735 rpms_centos_download_L1.log 57768 tarballs_download.log 83377 total [root at 90104f541da1 logs]# I don’t know whether the “failmoved” packages will affect the ISO image build or not. I’m building another docker image for building ISO image. --Changcheng From: Liu, Changcheng Sent: Wednesday, November 21, 2018 11:24 PM To: 'starlingx-discuss at lists.starlingx.io' >; Cordoba Malibran, Erich > Subject: RE: stx-tools: setup stx build environment Hi Erich, Please help check the problem. Tell me if you need more information. I’m trying to run “download_mirror.sh” again. B.R. Changcheng From: Liu, Changcheng Sent: Wednesday, November 21, 2018 6:35 PM To: 'starlingx-discuss at lists.starlingx.io' > Subject: stx-tools: setup stx build environment Could someone help check below bug? Title: stx-tools: failed to download required packaged Link: https://bugs.launchpad.net/starlingx/+bug/1804412 B.R. Changcheng From: Liu, Changcheng Sent: Friday, November 16, 2018 8:31 PM To: starlingx-discuss at lists.starlingx.io Subject: setup stx build environment Hi all, I have one question about setting up stx build environment. Why not move lots of many basic program installation process from mirror-check.sh to Dockerfile directly? Then stx community could supply one basic docker image as the base image to let developer customize it. Currently, I still need install lots of program after building Dockerfile into image. B.R. Changcheng _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From changcheng.liu at intel.com Mon Nov 26 01:26:09 2018 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Mon, 26 Nov 2018 01:26:09 +0000 Subject: [Starlingx-discuss] stx-tools: setup stx build environment In-Reply-To: References: <0D7994A90DD70040A9F5E77C4D23C57D50EFAF5F@SHSMSX104.ccr.corp.intel.com> <0D7994A90DD70040A9F5E77C4D23C57D50EF931C@SHSMSX104.ccr.corp.intel.com> <4355461542980237@sas1-87f9feb8d943.qloud-c.yandex.net> <0D7994A90DD70040A9F5E77C4D23C57D50EFB3F0@SHSMSX104.ccr.corp.intel.com> Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50EFB7BF@SHSMSX104.ccr.corp.intel.com> Hi Yong, Yes. The proxy should be right. But the error is still there. BTW, I also hit below error: 09:23:46 b3: INFO: mounting tmpfs at /localdisk/loadbuild/nstcc1/starlingx/std/mock/b3/root. 09:23:46 b3: ERROR: Command failed: 09:23:46 b3: # mount -n -t tmpfs -o mode=0755 -o nr_inodes=0 -o size=11g mock_chroot_tmpfs /localdisk/loadbuild/nstcc1/starlingx/std/mock/b3/root B.R. Changcheng From: Hu, Yong Sent: Monday, November 26, 2018 9:10 AM To: Liu, Changcheng ; Erich Cordoba ; 'starlingx-discuss at lists.starlingx.io' ; Cordoba Malibran, Erich Subject: Re: [Starlingx-discuss] stx-tools: setup stx build environment Your no_proxy env setting should resolve the following error, are you still seeing it? 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable From: "Liu, Changcheng" > Date: Sunday, 25 November 2018 at 3:24 PM To: Erich Cordoba >, "'starlingx-discuss at lists.starlingx.io'" >, "Cordoba Malibran, Erich" > Subject: Re: [Starlingx-discuss] stx-tools: setup stx build environment Hi Erich, Is there anything wrong with proxy env in container as below? [nstcc1 at d8ae703a2a91 /]$ env | grep -i proxy NO_PROXY=localhost,.intel.com,127.0.0.0/8,172,16.0.0/20,192.168.0.0/16,10.0.0.0/8 http_proxy=http://child-prc.intel.com:913 FTP_PROXY=ftp://child-prc.intel.com:913 ftp_proxy=ftp://child-prc.intel.com:913 https_proxy=http://child-prc.intel.com:913 HTTPS_PROXY=http://child-prc.intel.com:913 no_proxy=localhost,.intel.com,127.0.0.0/8,172,16.0.0/20,192.168.0.0/16,10.0.0.0/8 HTTP_PROXY=http://child-prc.intel.com:913 B.R. Changcheng From: Erich Cordoba [mailto:erich.cm.lists at yandex.com] Sent: Friday, November 23, 2018 9:37 PM To: 'starlingx-discuss at lists.starlingx.io' >; Cordoba Malibran, Erich >; Liu, Changcheng > Subject: Re: [Starlingx-discuss] stx-tools: setup stx build environment Hi Liu, As you need to setup a proxy, you need also to set the no_proxy=127.0.0.1 env variable, so mock can find the internal repository. This is something that we need to do in our internal build job. -Erich -- Sent from Yandex.Mail for mobile 23.11.2018, 07:27, "Liu, Changcheng" >: Hi Erich, I hit lots of error when executing “build-pkgs”. Please help check it. https://bugs.launchpad.net/starlingx/+bug/1804412 1. get stx-tools cd $HOME git clone https://git.starlingx.io/stx-tools cd stx-tools git checkout -b erich_base 1d2ecbb0be2 2. apply below patch nstcc1 at nstcloudcc1:stx-tools$ git diff Dockerfile tb.sh Makefile diff --git a/Dockerfile b/Dockerfile index 87ef00b..dd730f9 100644 --- a/Dockerfile +++ b/Dockerfile @@ -13,9 +13,9 @@ FROM centos:7.4.1708 # Proxy configuration -#ENV http_proxy "http://your.actual_http_proxy.com:your_port" -#ENV https_proxy "https://your.actual_https_proxy.com:your_port" -#ENV ftp_proxy "http://your.actual_ftp_proxy.com:your_port" +ENV http_proxy "http://child-prc.intel.com:913" +ENV https_proxy "http://child-prc.intel.com:913" +ENV ftp_proxy "ftp://child-prc.intel.com:913" # username you will docker exec into the container as. @@ -26,6 +26,8 @@ ARG MYUID=1000 ENV container=docker +RUN echo "proxy=$http_proxy" >> /etc/yum.conf && \ +echo -e "export http_proxy=$http_proxy\nexport https_proxy=$https_proxy\nexport ftp_proxy=$ftp_proxy" >> /root/.bashrc # Download required dependencies by mirror/build processes. # Notice there are 3 invocations to yum package manage. # 1) Enable EPEL repository. diff --git a/Makefile b/Makefile index c4ebff4..73f5f3a 100644 --- a/Makefile +++ b/Makefile @@ -20,6 +20,8 @@ all: docker build \ --build-arg MYUID=$(UID) \ --build-arg MYUNAME=$(MYUNAME) \ + --build-arg https_proxy=http://child-prc.intel.com:913 \ + --build-arg http_proxy=http://child-prc.intel.com:913 \ --ulimit core=0 \ --network host \ -t $(TC_CONTAINER_TAG) \ diff --git a/tb.sh b/tb.sh index e0508dd..9530efd 100755 --- a/tb.sh +++ b/tb.sh @@ -38,11 +38,14 @@ function run_container { docker run -it --rm \ --name ${TC_CONTAINER_NAME} \ --detach \ + -v /etc/localtime:/etc/localtime:ro \ -v ${LOCALDISK}:/${GUEST_LOCALDISK} \ -v ${HOST_MIRROR_DIR}:/import/mirrors:ro \ -v /sys/fs/cgroup:/sys/fs/cgroup:ro \ -v ~/.ssh:/mySSH:ro \ -e "container=docker" \ + --env https_proxy=http://child-prc.intel.com:913 \ + --env http_proxy=http://child-prc.intel.com:913 \ -e MYUNAME=${MYUNAME} \ --privileged=true \ --security-opt seccomp=unconfined \ 3. build docker image make all 4. run docker image bash tb.sh run 5. execute into docker container bash tb.sh exec 6. [nstcc1 at d8ae703a2a91 /]$ eval $(ssh-agent) Agent pid 15524 [nstcc1 at d8ae703a2a91 /]$ ssh-add Identity added: /home/nstcc1/.ssh/id_rsa (/home/nstcc1/.ssh/id_rsa) [nstcc1 at d8ae703a2a91 /]$ cd $MY_REPO_ROOT_DIR [nstcc1 at d8ae703a2a91 starlingx]$ repo init -u https://git.starlingx.io/stx-manifest -m default.xml [nstcc1 at d8ae703a2a91 starlingx]$ repo sync -j4 [nstcc1 at d8ae703a2a91 starlingx]$ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/stx/ [nstcc1 at d8ae703a2a91 starlingx]$ populate_downloads.sh /import/mirrors/CentOS/stx-r1/CentOS/pike/ 7. nstcc1 at nstcloudcc1:~$ mkdir -p $HOME/starlingx/mirror/CentOS/tis-installer nstcc1 at nstcloudcc1:~$ cp $HOME/starlingx/mirror/CentOS/stx-r1/CentOS/pike/Binary/images/pxeboot/initrd.img $HOME/starlingx/mirror/CentOS/tis-installer/initrd.img-stx-0.2 nstcc1 at nstcloudcc1:~$ cp $HOME/starlingx/mirror/CentOS/stx-r1/CentOS/pike/Binary/images/pxeboot/vmlinuz $HOME/starlingx/mirror/CentOS/tis-installer/vmlinuz-stx-0.2 nstcc1 at nstcloudcc1:~$ cp $HOME/starlingx/mirror/CentOS/stx-r1/CentOS/pike/Binary/LiveOS/squashfs.img $HOME/starlingx/mirror/CentOS/tis-installer/squashfs.img-stx-0.2 8. [nstcc1 at d8ae703a2a91 starlingx]$ generate-cgcs-centos-repo.sh /import/mirrors/CentOS/stx-r1/CentOS/pike/ 9. [nstcc1 at d8ae703a2a91 starlingx]$ build-pkgs Then, hit lots of error, the log is build-pkgs.log 21:10:47 failure: repodata/repomd.xml from TisCentos7Distro: [Errno 256] No more mirrors to try. 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 http://127.0.0.1:8088/localdisk/designer/nstcc1/starlingx/cgcs-root/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 503 - Service Unavailable 21:10:47 21:10:47 End build on 'b0': /localdisk/loadbuild/nstcc1/starlingx/std/rpmbuild/SRPMS/mariadb-10.1.28-1.el7.tis.15.src.rpm 21:10:47 Error building mariadb-10.1.28-1.el7.tis.15.src.rpm on 'b0'. --Thanks Changcheng From: Liu, Changcheng Sent: Friday, November 23, 2018 12:16 AM To: 'starlingx-discuss at lists.starlingx.io' >; Cordoba Malibran, Erich > Subject: RE: stx-tools: setup stx build environment Hi Erich, I still met with some problems after following your method to run “download_mirror.sh”. Please check the comment in https://bugs.launchpad.net/starlingx/+bug/1804412 [root at 90104f541da1 logs]# wc -l * 0 K1_failmoved_url_centos.log 0 K1_rpms_found_centos.log 0 K1_rpms_missing_centos.log 0 K1_srpms_found_centos.log 0 K1_srpms_missing_centos.log 46 L1_failmoved_url_3rdparties.log 5306 L1_failmoved_url_centos.log 394 L1_failmoved_url_centos3rdparties.log 0 L1_rpms_found_3rdparties.log 0 L1_rpms_found_centos.log 0 L1_rpms_found_centos3rdparties.log 0 L1_rpms_missing_3rdparties.log 0 L1_rpms_missing_centos.log 0 L1_rpms_missing_centos3rdparties.log 23 L1_srpms_found_3rdparties.log 1936 L1_srpms_found_centos.log 148 L1_srpms_found_centos3rdparties.log 0 L1_srpms_missing_3rdparties.log 0 L1_srpms_missing_centos.log 0 L1_srpms_missing_centos3rdparties.log 590 all_i686.txt 9858 otherfiles_centos_download.log 1 rpm-gpg-key-missing.txt 80 rpms_3rdparties_download_L1.log 490 rpms_centos3rdparties_download_L1.log 2 rpms_centos_download_K1.log 6735 rpms_centos_download_L1.log 57768 tarballs_download.log 83377 total [root at 90104f541da1 logs]# I don’t know whether the “failmoved” packages will affect the ISO image build or not. I’m building another docker image for building ISO image. --Changcheng From: Liu, Changcheng Sent: Wednesday, November 21, 2018 11:24 PM To: 'starlingx-discuss at lists.starlingx.io' >; Cordoba Malibran, Erich > Subject: RE: stx-tools: setup stx build environment Hi Erich, Please help check the problem. Tell me if you need more information. I’m trying to run “download_mirror.sh” again. B.R. Changcheng From: Liu, Changcheng Sent: Wednesday, November 21, 2018 6:35 PM To: 'starlingx-discuss at lists.starlingx.io' > Subject: stx-tools: setup stx build environment Could someone help check below bug? Title: stx-tools: failed to download required packaged Link: https://bugs.launchpad.net/starlingx/+bug/1804412 B.R. Changcheng From: Liu, Changcheng Sent: Friday, November 16, 2018 8:31 PM To: starlingx-discuss at lists.starlingx.io Subject: setup stx build environment Hi all, I have one question about setting up stx build environment. Why not move lots of many basic program installation process from mirror-check.sh to Dockerfile directly? Then stx community could supply one basic docker image as the base image to let developer customize it. Currently, I still need install lots of program after building Dockerfile into image. B.R. Changcheng _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From sajuptpm at gmail.com Mon Nov 26 09:38:53 2018 From: sajuptpm at gmail.com (Saju M) Date: Mon, 26 Nov 2018 15:08:53 +0530 Subject: [Starlingx-discuss] Use of sysinv_api_bind_ip and sysinv_api_pxeboot_ip, Difference ? Message-ID: HI, I have noticed that sysinv is trying to listen to 6385 with 2 different IPs. I dont know, How 169.254.202.2 came in etc/sysinv/sysinv.conf, I could not find that IP in hiera. Error from /var/log/sysinv.log ========================== 2018-11-26 08:46:09.298 18046 INFO oslo.service.wsgi [-] sysinv_api listening on *0.0.0.0:6385 * ERROR oslo.service.wsgi [-] Could not bind to *169.254.202.2:6385 * http://paste.openstack.org/show/735998/ Somebody please explain the use of sysinv_api() and sysinv_pxe() ========================================== https://github.com/openstack/stx-config/blob/ddb407fccbf5d5490400f21d26973ff5a148d737/sysinv/sysinv/sysinv/sysinv/cmd/api.py#L68 https://github.com/openstack/stx-config/blob/ddb407fccbf5d5490400f21d26973ff5a148d737/sysinv/sysinv/sysinv/sysinv/api/__init__.py#L28 Regards Saju Madhavan +91 09535134654 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ovidiu.Poncea at windriver.com Mon Nov 26 15:15:00 2018 From: Ovidiu.Poncea at windriver.com (Poncea, Ovidiu) Date: Mon, 26 Nov 2018 15:15:00 +0000 Subject: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching In-Reply-To: References: <2588653EBDFFA34B982FAF00F1B4844EBB25D46B@ALA-MBD.corp.ad.wrs.com> , <4C60D9C5C8176C47874FFF36647AA19E9D5F8E8F@ALA-MBD.corp.ad.wrs.com> , Message-ID: <4C60D9C5C8176C47874FFF36647AA19E9D5FAA8C@ALA-MBD.corp.ad.wrs.com> Hi Lisa, Yeah, even if we refactor raw caching, it's most likely going to be rejected by upstream due to replicating existing functionality in cinder. Yet, imho, we should have an working replacement before retiring raw caching and we should have some agreed mitigations in place for cinder's disadvantages (if we can't live with them, Brent please help here). See my questions bellow & inline. Also, please correct text bellow if I made wrong assumptions as you know cinder's caching better than me. Short comparison of the two: Raw caching Uses --raw-cache cli option in Glance to trigger a background process that converts the image. Once cached, new volumes get created on Ceph instantly by levereging Ceph's copy-on-write. Cache is allocated from the "images" RBD pool. Advantages: - user can select the images it wants to cache - user can monitor the progress and can check used space for each image (cli + dashboard). - on image delete the cache is also cleared if there is no volume using it. Else it is cleared with the last volume keeping the cache data in-use. - no wasted space - complete control by user Disadvantages: - There is almost no way this is going to be accepted upstream. Maybe, yet with small hopes, if we refactor everything as a 3rd party glance feature, but we may need to push some hooks upstream to make it work. - Ceph only Cinder's caching Uses a "shadow" tenant to store shadow volumes. Cache is created with the first volume from that images. Next volume will be created instantly by leveraging copy-on-write if backend provides support for it (e.g. on Ceph). Space for cache is allocated on one of the cinder backends, has a configurable threshold. Advantages: - already upstream - works with all backends - all cached images are displayed for the "admin" if he changes to the shadow tenant and lists volumes. - admin (not user, only admin) can free cache by deleting volumes of the shadow tenant (need confirmation) Disadvantages: 1. it's either globally enabled or disabled => needs sysinv configuration option 2. it caches every image. No way to select what image to cache nor with what backend (question bellow) => space waste 3. cached images are not removed. It needs to hit a space provision to do that, and it will remove the oldest image, although that image cache may be important. 4. less control: Images are cached on first use and are removed when provisioned space hits threshold. This means that user does not have control over what images are converted and what images are in cache. So, sometimes volume creation works fast, other times it's slow. This can be a problem especially on parallel volume creation through helm charts as, if the image did not have a cache, then stack creation may timeout. Another problem may be if cache is small and images get rotated in the cache => we need alarms when threshold is hit. 5. needs the shadow tenant created before use => puppet / helm chart chart update (for --kubernates) Mitigations of disadvantages above - possible solutions and alternatives: #1: Customers may not want to enable it, we should allow customers to choose when to enable it (it can be added as a custom capabilities parameter to "system storage-backend-add/system storage-backend-modify") #2: No workaround comes to my mind - we can probably live with it #3: A simple solution would be to implement a cron job to clean cache periodically or a more elaborate solution would be remove the cache with the last volume that used that image (need a cinder upstream feature for it) #4: Two options comes to mind: 1. To get some control we should not limit the cache size, given that we do propper cleanup in #3. 2. If we limit the cache, we have to make the limit configurable and raise an alarm once cache gets near full so that admin takes preventive measures and either increases provisioned space or #5: This is mandatory, otherwise cinder's caching won't work at all. Questions, (maybe if you get time to play with cinder's caching to get a better understanding): 1. How does cinder's caching behaves when multiple volumes are created in parallel from a newly created image? Will it wait for the cache to be created before creating the volumes or just start all volume creations in parallel? 2. What is the cinder backend that store the cache? If it is the one used by the volume, will this lead to multiple cached volumes of the same image? Can we chose the backend? 3. How is cache space provisioned? Do we need to restart cinder-volume for changes to take effect? 4. Is admin able to clean up individual cached images in the shadow tenant? Maybe also user? Ovidiu ________________________________ From: Li, Xiaoyan [xiaoyan.li at intel.com] Sent: Thursday, November 22, 2018 2:41 AM To: Poncea, Ovidiu; Rowsell, Brent; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi Brent and Ovidiu, As this email has a long history, I re-summarize the raw cache in StarlingX and Cinder upstream image cache. Please vote whether we can abandon raw cache in StarlingX. StarlingX Create an image cache in ceph when Glance creates an image. And delete the cached image in ceph when deleting the original image in Glance. Cinder: When creating a volume from an image in a backend storage at the first time, Cinder creates a volume from this image, and uses it as the image cache. So next time if users create another volume from this image in the same backend storage, Cinder at first finds out the cached image volume and clones a new volume from it. Cinder allows capacity configuration for cached images. If the space is used up, Cinder will evict the cached image volumes. >From my viewpoint, Cinder image cache can achieve same functionality as Raw cache in StarlingX with more enhancement. It is for all Cinder supported backend storage, not just for Ceph. Best wishes Lisa From: Li, Xiaoyan Sent: Monday, November 19, 2018 9:44 AM To: Poncea, Ovidiu ; Rowsell, Brent ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi Ovidiu, A cached image ( new volume from this image) is created on a storage backend when Cinder firstly creates a volume in the same backend storage from the image. All the information are stored in Cinder, including volume id, image id etc. https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/manager.py#L1368 https://github.com/openstack/cinder/blob/stable/pike/cinder/image/cache.py#L82 A cached image is deleted when the configure space for cache is used up. So currently Cinder doesn’t delete the cached image volumes even if the image is deleted. But this can be an enhancement of current cinder image cache. https://github.com/openstack/cinder/blob/stable/pike/cinder/image/cache.py#L117 https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/manager.py#L1351 Best wishes Lisa From: Poncea, Ovidiu [mailto:Ovidiu.Poncea at windriver.com] Sent: Friday, November 16, 2018 4:57 PM To: Li, Xiaoyan >; Rowsell, Brent >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi Li, Quick question: Is cache going to be freed when an image is deleted from glance? It would be a waste to cache images that are no longer needed. Thanks, Ovidiu ________________________________ From: Li, Xiaoyan [xiaoyan.li at intel.com] Sent: Tuesday, November 13, 2018 9:19 AM To: Rowsell, Brent; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi, About the raw cache function in StarlingX Cinder and Glance, I would like to remove it as Cinder has similar function. Please see following detail. And if I would like to remove the function in StarlingX, there are two methods: 1. Submit a patch to revert the changes in Glance and Cinder. 2. Ignore these patches during upgrading StarlingX/Cinder to new Cinder release. Which way do we prefer to? Best wishes Lisa From: Li, Xiaoyan Sent: Thursday, September 20, 2018 10:17 AM To: Rowsell, Brent >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi, Brent The following are mechanism of Cinder volume cache. Creation of cached volume: It creates a cached volume in the backend storage when creating from an image. 1. Create_from_image: https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L890 2. Return image cache entry: If not existed, it creates a new entry. https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L746 3. Create a new image-volume and cache entry for it: https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L872 Use a cached volume when creating a volume: https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L723-L735 Delete the cache volume: When capacity and number of cache entries exceed specified limit, it deletes cache entries (cached volumes). https://github.com/openstack/cinder/blob/stable/pike/cinder/image/cache.py#L164 Best wishes Lisa From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Thursday, September 6, 2018 10:02 AM To: Li, Xiaoyan >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching We would need to review this feature to ensure it provides equivalent functionality first. If it does, great, we can look at reverting and enabling this cinder functionality. Brent From: Li, Xiaoyan [mailto:xiaoyan.li at intel.com] Sent: Wednesday, September 5, 2018 9:59 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi all, This email is about Raw caching function in StarlingX. This feature is to cache an image in backend storage like Ceph when we first create a volume in this backend storage. In fact, Cinder upstream has already had a similar function in Pike release. https://specs.openstack.org/openstack/cinder-specs/specs/liberty/image-volume-cache.html So I want to revert Raw caching function in StarlingX, and use Cinder generic image cache instead. The problem is that we need to update Cinder config in StarlingX. Any comments? Best wishes Lisa -------------- next part -------------- An HTML attachment was scrubbed... URL: From abraham.arce.moreno at intel.com Mon Nov 26 16:52:44 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Mon, 26 Nov 2018 16:52:44 +0000 Subject: [Starlingx-discuss] [Build] Create mechanism to publish tarballs in StarlingX In-Reply-To: References: Message-ID: Thanks Scott, > Would we want to publish tarballs on mirrors.starlingx.cengn.ca as part > of the build process? Yes, another path to go: [ Hosting Site ] Everyone: Pros? Cons? 1. tarballs.starlingx.io 2. mirrors.starlingx.cengn.ca Then let me put high level [ Zuul ] implementation on hold and focus for now on how to reach our rephrased [ Objective ]: "Create a new job to create tarballs from stx projects in our path to have a build system architecture for Multi OS" Everyone? Is this a reasonable objective for this story? > Tarball would be updated nightly, rather than with every update as a > zuul based solution would have it. > > e.g. > http://mirror.starlingx.cengn.ca/mirror/starlingx//centos/ mp>/outputs/tarballs/-.tar.gz > > or only publish the latest on branch... an in a structure more like that > seen in http://tarballs.openstack.org ... > > http://mirror.starlingx.cengn.ca/mirror/starlingx/tarballs/ name>/-.tar.gz I am taking your feedback to line up the following 2 procedures: - Build Process - Updates every night - Zuul - Updates every change merged Everyone: Pros? Cons? Future Limitations? From Irina.Mihai at windriver.com Mon Nov 26 17:24:47 2018 From: Irina.Mihai at windriver.com (Mihai, Irina) Date: Mon, 26 Nov 2018 17:24:47 +0000 Subject: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming In-Reply-To: References: Message-ID: Hi Liang, This patch was covering the scenario when we're trying to create multiple volumes from image at the same time. In this situation, multiple downloads/convertions would be allowed to start since there would still be conversion space left, but eventually the operation would fail because of the disk being full. This is not caught by any of the "ImageTooBig" or "ImageUnacceptable" exceptions. Could you please help to address one doubt: why image is converted in the same location with image itself? This patch is to create a volume from image, right? Right, but I'm not aware of the reasoning behind this. However, if the used image is qcow2 then it needs to be converted to raw before being saved to the volume. Please let me know if I can help in any other way. Thanks, Irina ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Sunday, November 25, 2018 11:44 AM To: Mihai, Irina Cc: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming Hi Irina Code review: https://review.openstack.org/#/c/618976/ I’m working of upstreaming this patch. Could you please help to address one doubt: why image is converted in the same location with image itself? This patch is to create a volume from image, right? I take a look of related code, the destination location would be the newly created volume and the source location is configured in cinder.conf, something like: image_conversion_dir = /mnt/d100m/image_conversion_dir I did an experiment, in the latest master branch of cinder upstream repo: - If image_conversion_dir has no space to store the downloading image, the exception ImageTooBig will be caught in the beginning of _create_from_image_cache_or_download(). - If has space to store the image, but dest volume size is smaller than image’s virtual size, an exception “ImageUnacceptable” will raised by check_virtual_size. So it seems no chance to go to the situation this patch aimed to solve. Could you please help to give more background of this patch? Or if you think this patch is invalid now, please just tell me, I will mark this patch as abandoned. Thanks Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Mon Nov 26 18:59:24 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 26 Nov 2018 18:59:24 +0000 Subject: [Starlingx-discuss] Issue w/ openssh blocking sanity execution Message-ID: <151EE31B9FCCA54397A757BC674650F0BA48770A@ALA-MBD.corp.ad.wrs.com> Hello all, We are seeing issues with ssh after installing controller-0 with a load built on 2018-11-25. The ssh daemon is not started by default on the controller. This issue is seen in multiple labs and is blocking automated sanity execution. This issue was not seen in a load built on 2018-11-22. Is anyone else testing in master and seeing this issue? Looking at the code submissions between 2018-11-22 & 2018-11-25, I see the following change: ./cgcs-root/stx/stx-integ 36dc17738d9e2ef5dab689a556d7d8f33415861e Fri Nov 23 22:09:59 2018 +0000 Gerrit Code Review Merge "Refactor patches for openssh package" ./cgcs-root/stx/stx-integ 1c8c71654ff6f20cf13bcceeb861d969fd5b53a8 Wed Nov 21 01:21:12 2018 +0000 zhipeng liu Refactor patches for openssh package I'm not sure if that's the root-cause, but it needs to be investigated. Zhipeng/Cindy, Please investigate. Launchpad: https://bugs.launchpad.net/starlingx/+bug/1805157 Thanks, Ghada -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Mon Nov 26 19:10:48 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Mon, 26 Nov 2018 19:10:48 +0000 Subject: [Starlingx-discuss] Issue w/ openssh blocking sanity execution In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA48770A@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA48770A@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA3F23FC@ALA-MBD.corp.ad.wrs.com> The update added a new openssh-config package for the customizations we have to the configuration files. However, it also has a %post script command that disables sshd: https://review.openstack.org/#/c/619003/4/base/openssh-config/centos/openssh-config.spec %{_bindir}/systemctl disable sshd.service > /dev/null 2>&1 || : I don't know why that would be added, as we don't do that in the openssh package today. Maybe it was intended to be a restart to pick up the config changes, but it wouldn't strictly be needed for the install. The commit message says the following testing was done: Deployment test and ping test between VMs pass Config files check pass. so I'm surprised this issue wasn't seen during testing for this update. From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Monday, November 26, 2018 1:59 PM To: starlingx-discuss at lists.starlingx.io; Liu, ZhipengS; Xie, Cindy Subject: [Starlingx-discuss] Issue w/ openssh blocking sanity execution Importance: High Hello all, We are seeing issues with ssh after installing controller-0 with a load built on 2018-11-25. The ssh daemon is not started by default on the controller. This issue is seen in multiple labs and is blocking automated sanity execution. This issue was not seen in a load built on 2018-11-22. Is anyone else testing in master and seeing this issue? Looking at the code submissions between 2018-11-22 & 2018-11-25, I see the following change: ./cgcs-root/stx/stx-integ 36dc17738d9e2ef5dab689a556d7d8f33415861e Fri Nov 23 22:09:59 2018 +0000 Gerrit Code Review Merge "Refactor patches for openssh package" ./cgcs-root/stx/stx-integ 1c8c71654ff6f20cf13bcceeb861d969fd5b53a8 Wed Nov 21 01:21:12 2018 +0000 zhipeng liu Refactor patches for openssh package I'm not sure if that's the root-cause, but it needs to be investigated. Zhipeng/Cindy, Please investigate. Launchpad: https://bugs.launchpad.net/starlingx/+bug/1805157 Thanks, Ghada -------------- next part -------------- An HTML attachment was scrubbed... URL: From vm.rod25 at gmail.com Mon Nov 26 21:07:20 2018 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Mon, 26 Nov 2018 15:07:20 -0600 Subject: [Starlingx-discuss] [Build] Create mechanism to publish tarballs in StarlingX In-Reply-To: References: Message-ID: On Mon, Nov 26, 2018 at 10:53 AM Arce Moreno, Abraham wrote: > > Thanks Scott, > > > Would we want to publish tarballs on mirrors.starlingx.cengn.ca as part > > of the build process? > > Yes, another path to go: > > [ Hosting Site ] > > Everyone: Pros? Cons? > > 1. tarballs.starlingx.io > 2. mirrors.starlingx.cengn.ca > > Then let me put high level [ Zuul ] implementation on hold and focus for now > on how to reach our rephrased [ Objective ]: > > "Create a new job to create tarballs from stx projects in our path to have > a build system architecture for Multi OS" > > Everyone? Is this a reasonable objective for this story? > yes +1 > > Tarball would be updated nightly, rather than with every update as a > > zuul based solution would have it. > > > > e.g. > > http://mirror.starlingx.cengn.ca/mirror/starlingx//centos/ > mp>/outputs/tarballs/-.tar.gz > > > > or only publish the latest on branch... an in a structure more like that > > seen in http://tarballs.openstack.org ... > > > > http://mirror.starlingx.cengn.ca/mirror/starlingx/tarballs/ > name>/-.tar.gz Are we going to increase the version of the tar.gz on every change? > > I am taking your feedback to line up the following 2 procedures: > > - Build Process > - Updates every night > - Zuul > - Updates every change merged > > Everyone: Pros? Cons? Future Limitations? This is necessary from the SW release perspective. If we can separate the STX SW from the distro management is much more easy to deploy a MultiOS solution for STX Let's take for example httpd: httpd community creates a release, let's say httpd-2.4.35. They create a tarball for every release with release notes of what they fix/improve Other distributions can generate spec files or debs acording to their needs and installing httpd as they prefer on their Linux distributions Son in general +1 to this Abraham I refer to this change in my multi OS spec : https://review.openstack.org/#/c/619801/ Regards > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From luis.ramirez at opencloud.es Mon Nov 26 22:03:32 2018 From: luis.ramirez at opencloud.es (Luis Ramirez) Date: Mon, 26 Nov 2018 23:03:32 +0100 Subject: [Starlingx-discuss] Use of sysinv_api_bind_ip and sysinv_api_pxeboot_ip, Difference ? In-Reply-To: References: Message-ID: Hi, This IP is provided by Automatic Private IP Addressing. This process assigns an IP address even in the absence of a DHCP server. If a DISCOVER message is not answered, the client picks a random 16-bit number and prepends it with 169.254.x.x. It performs a gratuitous ARP and assigns that address to itself. It means that the DHCP server is not reachable. Br, Luis Rmz Blockchain, DevOps & Open Source Cloud Solutions Architect ---------------------------------------- Founder & CEO OpenCloud.es luis.ramirez at opencloud.es Skype ID: d.overload Hangouts: luis.ramirez at opencloud.es [image: ] +34 682 740 973 / [image: ]+39 392 1289553 / [image: ]+49 152 26917722 / Česká republika: +420 774 274 882 ----------------------------------------------------- El lun., 26 nov. 2018 a las 10:39, Saju M () escribió: > HI, > > I have noticed that sysinv is trying to listen to 6385 with 2 different > IPs. > I dont know, How 169.254.202.2 came in etc/sysinv/sysinv.conf, I could not > find that IP in hiera. > > Error from /var/log/sysinv.log > ========================== > 2018-11-26 08:46:09.298 18046 INFO oslo.service.wsgi [-] sysinv_api > listening on *0.0.0.0:6385 * > ERROR oslo.service.wsgi [-] Could not bind to *169.254.202.2:6385 > * > > http://paste.openstack.org/show/735998/ > > Somebody please explain the use of sysinv_api() and sysinv_pxe() > ========================================== > > https://github.com/openstack/stx-config/blob/ddb407fccbf5d5490400f21d26973ff5a148d737/sysinv/sysinv/sysinv/sysinv/cmd/api.py#L68 > > > https://github.com/openstack/stx-config/blob/ddb407fccbf5d5490400f21d26973ff5a148d737/sysinv/sysinv/sysinv/sysinv/api/__init__.py#L28 > > > > Regards > Saju Madhavan > +91 09535134654 > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ian.Jolliffe at windriver.com Mon Nov 26 22:08:13 2018 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Mon, 26 Nov 2018 22:08:13 +0000 Subject: [Starlingx-discuss] TSC meeting minutes - November 22nd Message-ID: <9F535FC4-C5D7-405D-9EF1-ED8CA9968FC6@windriver.com> Hi all; Below are the outcomes of last week’s meeting: Standing topics: ============= Pending reviews for stx-governance https://review.openstack.org/#/q/project:openstack/stx-governance,n,z Pending reviews for stx-specs – we had a quick look – 2 new specs – TSC members please review https://review.openstack.org/#/c/619053/ https://review.openstack.org/#/c/618587/ And 2 additional new ones have been posted since the meeting – the query is below for easy reference.[0] Query: [0] https://review.openstack.org/#/q/status:open+AND+project:%255Eopenstack/stx-specs 11/22/18: Meeting ================ Next release - discussed items on ethercalc [0] - help new TSC members understand the scope and proposals We reviewed roughly half the items on the list - tagged as H,M,L - we ended up with too many highs. We agreed the first order prioritization would be based on H/M/L priority. We updated the notes in the ethercalc in real time for future reference. The new TSC members appreciated getting more context around the new items. [1] https://ethercalc.openstack.org/fafyo2729fnr https://wiki.openstack.org/wiki/Edge_Computing_Group/Edge_Reference_Architectures MiniPTG/mid-cycle proposal in Phoenix, Jan 15/16: http://lists.starlingx.io/pipermail/starlingx-discuss/2018-November/001932.html Need input from PL/TL from sub teams - attend next TSC meeting on what they feel they can help with on the high priority items. * No new items posted to the ethercalc Need a focused TSC discussion around test - item for future meeting TSC members present: Curtis, Shuquan, Ana, Ian, Brent, Saul -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Mon Nov 26 22:13:15 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Mon, 26 Nov 2018 22:13:15 +0000 Subject: [Starlingx-discuss] Use of sysinv_api_bind_ip and sysinv_api_pxeboot_ip, Difference ? In-Reply-To: References: Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA3F2564@ALA-MBD.corp.ad.wrs.com> The 169.254.202.2 address is assigned for pxeboot: controller-0:~$ sudo grep -r 169.254.202.2 /etc 2>/dev/null /etc/sysinv/sysinv.conf:sysinv_api_pxeboot_ip=169.254.202.2 /etc/dnsmasq.conf:dhcp-range=set:pxeboot,169.254.202.2,169.254.202.254,255.255.255.0,1h /etc/dnsmasq.conf:dhcp-option=tag:pxeboot,option:dns-server,169.254.202.2 /etc/dnsmasq.conf:dhcp-boot=tag:bios,tag:pxeboot,pxelinux.0,pxecontroller,169.254.202.2 /etc/dnsmasq.conf:dhcp-boot=tag:efi,tag:pxeboot,EFI/grubx64.efi,pxecontroller,169.254.202.2 /etc/hosts:169.254.202.2 pxecontroller The address gets added to the mgmt interface on the active controller, for responding to pxeboot/dhcp requests from hosts during installation from the active controller. Sysinv binds to the address so that it can respond to limited API queries and notifications that occur during the installation process. From: Luis Ramirez [mailto:luis.ramirez at opencloud.es] Sent: Monday, November 26, 2018 5:04 PM To: sajuptpm at gmail.com Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Use of sysinv_api_bind_ip and sysinv_api_pxeboot_ip, Difference ? Hi, This IP is provided by Automatic Private IP Addressing. This process assigns an IP address even in the absence of a DHCP server. If a DISCOVER message is not answered, the client picks a random 16-bit number and prepends it with 169.254.x.x. It performs a gratuitous ARP and assigns that address to itself. It means that the DHCP server is not reachable. Br, Luis Rmz Blockchain, DevOps & Open Source Cloud Solutions Architect ---------------------------------------- Founder & CEO OpenCloud.es luis.ramirez at opencloud.es Skype ID: d.overload Hangouts: luis.ramirez at opencloud.es [Image removed by sender. ] +34 682 740 973 / [Image removed by sender. ] +39 392 1289553 / [Image removed by sender. ] +49 152 26917722 / Česká republika: +420 774 274 882 ----------------------------------------------------- El lun., 26 nov. 2018 a las 10:39, Saju M (>) escribió: HI, I have noticed that sysinv is trying to listen to 6385 with 2 different IPs. I dont know, How 169.254.202.2 came in etc/sysinv/sysinv.conf, I could not find that IP in hiera. Error from /var/log/sysinv.log ========================== 2018-11-26 08:46:09.298 18046 INFO oslo.service.wsgi [-] sysinv_api listening on 0.0.0.0:6385 ERROR oslo.service.wsgi [-] Could not bind to 169.254.202.2:6385 http://paste.openstack.org/show/735998/ Somebody please explain the use of sysinv_api() and sysinv_pxe() ========================================== https://github.com/openstack/stx-config/blob/ddb407fccbf5d5490400f21d26973ff5a148d737/sysinv/sysinv/sysinv/sysinv/cmd/api.py#L68 https://github.com/openstack/stx-config/blob/ddb407fccbf5d5490400f21d26973ff5a148d737/sysinv/sysinv/sysinv/sysinv/api/__init__.py#L28 Regards Saju Madhavan +91 09535134654 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ~WRD000.jpg Type: image/jpeg Size: 823 bytes Desc: ~WRD000.jpg URL: From zhipengs.liu at intel.com Tue Nov 27 01:35:27 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Tue, 27 Nov 2018 01:35:27 +0000 Subject: [Starlingx-discuss] Issue w/ openssh blocking sanity execution In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA3F23FC@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA48770A@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA3F23FC@ALA-MBD.corp.ad.wrs.com> Message-ID: <93814834B4855241994F290E959305C752FFA1B7@SHSMSX104.ccr.corp.intel.com> Hi Ghada and Don, I will check and update it today, thanks for your information! Zhipeng From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: 2018年11月27日 3:11 To: Khalil, Ghada ; starlingx-discuss at lists.starlingx.io; Liu, ZhipengS ; Xie, Cindy Subject: RE: Issue w/ openssh blocking sanity execution The update added a new openssh-config package for the customizations we have to the configuration files. However, it also has a %post script command that disables sshd: https://review.openstack.org/#/c/619003/4/base/openssh-config/centos/openssh-config.spec %{_bindir}/systemctl disable sshd.service > /dev/null 2>&1 || : I don’t know why that would be added, as we don’t do that in the openssh package today. Maybe it was intended to be a restart to pick up the config changes, but it wouldn’t strictly be needed for the install. The commit message says the following testing was done: Deployment test and ping test between VMs pass Config files check pass. so I’m surprised this issue wasn’t seen during testing for this update. From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Monday, November 26, 2018 1:59 PM To: starlingx-discuss at lists.starlingx.io; Liu, ZhipengS; Xie, Cindy Subject: [Starlingx-discuss] Issue w/ openssh blocking sanity execution Importance: High Hello all, We are seeing issues with ssh after installing controller-0 with a load built on 2018-11-25. The ssh daemon is not started by default on the controller. This issue is seen in multiple labs and is blocking automated sanity execution. This issue was not seen in a load built on 2018-11-22. Is anyone else testing in master and seeing this issue? Looking at the code submissions between 2018-11-22 & 2018-11-25, I see the following change: ./cgcs-root/stx/stx-integ 36dc17738d9e2ef5dab689a556d7d8f33415861e Fri Nov 23 22:09:59 2018 +0000 Gerrit Code Review Merge "Refactor patches for openssh package" ./cgcs-root/stx/stx-integ 1c8c71654ff6f20cf13bcceeb861d969fd5b53a8 Wed Nov 21 01:21:12 2018 +0000 zhipeng liu Refactor patches for openssh package I’m not sure if that’s the root-cause, but it needs to be investigated. Zhipeng/Cindy, Please investigate. Launchpad: https://bugs.launchpad.net/starlingx/+bug/1805157 Thanks, Ghada -------------- next part -------------- An HTML attachment was scrubbed... URL: From xiaoyan.li at intel.com Tue Nov 27 02:30:27 2018 From: xiaoyan.li at intel.com (Li, Xiaoyan) Date: Tue, 27 Nov 2018 02:30:27 +0000 Subject: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching In-Reply-To: <4C60D9C5C8176C47874FFF36647AA19E9D5FAA8C@ALA-MBD.corp.ad.wrs.com> References: <2588653EBDFFA34B982FAF00F1B4844EBB25D46B@ALA-MBD.corp.ad.wrs.com> , <4C60D9C5C8176C47874FFF36647AA19E9D5F8E8F@ALA-MBD.corp.ad.wrs.com> , <4C60D9C5C8176C47874FFF36647AA19E9D5FAA8C@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Ovidiu, As far as I'm concerned, Cinder image cache is an cache mechanism. So overall, users don't need to clean it manually. Currently when capacity for cache is full, it removes the cached image volumes with LRU policy. More detailed please see the following comments. Best wishes Lisa From: Poncea, Ovidiu [mailto:Ovidiu.Poncea at windriver.com] Sent: Monday, November 26, 2018 11:15 PM To: Li, Xiaoyan ; Rowsell, Brent ; 'starlingx-discuss at lists.starlingx.io' Cc: Miller, Frank Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi Lisa, Yeah, even if we refactor raw caching, it's most likely going to be rejected by upstream due to replicating existing functionality in cinder. Yet, imho, we should have an working replacement before retiring raw caching and we should have some agreed mitigations in place for cinder's disadvantages (if we can't live with them, Brent please help here). See my questions bellow & inline. Also, please correct text bellow if I made wrong assumptions as you know cinder's caching better than me. Short comparison of the two: Raw caching Uses --raw-cache cli option in Glance to trigger a background process that converts the image. Once cached, new volumes get created on Ceph instantly by levereging Ceph's copy-on-write. Cache is allocated from the "images" RBD pool. Advantages: - user can select the images it wants to cache - user can monitor the progress and can check used space for each image (cli + dashboard). - on image delete the cache is also cleared if there is no volume using it. Else it is cleared with the last volume keeping the cache data in-use. - no wasted space - complete control by user Disadvantages: - There is almost no way this is going to be accepted upstream. Maybe, yet with small hopes, if we refactor everything as a 3rd party glance feature, but we may need to push some hooks upstream to make it work. - Ceph only Cinder's caching Uses a "shadow" tenant to store shadow volumes. Cache is created with the first volume from that images. Next volume will be created instantly by leveraging copy-on-write if backend provides support for it (e.g. on Ceph). Space for cache is allocated on one of the cinder backends, has a configurable threshold. Advantages: - already upstream - works with all backends - all cached images are displayed for the "admin" if he changes to the shadow tenant and lists volumes. - admin (not user, only admin) can free cache by deleting volumes of the shadow tenant (need confirmation) Disadvantages: 1. it's either globally enabled or disabled => needs sysinv configuration option 2. it caches every image. No way to select what image to cache nor with what backend (question bellow) => space waste 3. cached images are not removed. It needs to hit a space provision to do that, and it will remove the oldest image, although that image cache may be important. 4. less control: Images are cached on first use and are removed when provisioned space hits threshold. This means that user does not have control over what images are converted and what images are in cache. So, sometimes volume creation works fast, other times it's slow. This can be a problem especially on parallel volume creation through helm charts as, if the image did not have a cache, then stack creation may timeout. Another problem may be if cache is small and images get rotated in the cache => we need alarms when threshold is hit. 5. needs the shadow tenant created before use => puppet / helm chart chart update (for --kubernates) Mitigations of disadvantages above - possible solutions and alternatives: #1: Customers may not want to enable it, we should allow customers to choose when to enable it (it can be added as a custom capabilities parameter to "system storage-backend-add/system storage-backend-modify") [Li, Xiaoyan] Currently image cache can be enabled/disabled per backend storage. https://docs.openstack.org/cinder/latest/admin/blockstorage-image-volume-cache.html I think it is enough. #2: No workaround comes to my mind - we can probably live with it #3: A simple solution would be to implement a cron job to clean cache periodically or a more elaborate solution would be remove the cache with the last volume that used that image (need a cinder upstream feature for it) [Li, Xiaoyan] From doc, currently Cinder removes cached images from least used to recently used. Every time Cinder uses a cached image volume, it updates its last_used field. This is the normal policy for data eviction. As it is cache and should be transparent for users, why do we need users to evict data? #4: Two options comes to mind: 1. To get some control we should not limit the cache size, given that we do propper cleanup in #3. [Li, Xiaoyan] Even we do cleanup, the limit can't be removed. 2. If we limit the cache, we have to make the limit configurable and raise an alarm once cache gets near full so that admin takes preventive measures and either increases provisioned space or #5: This is mandatory, otherwise cinder's caching won't work at all. [Li, Xiaoyan] It has to set cinder_internal_tenant_project_id and cinder_internal_tenant_user_id before enabling cache images. As this user can manage these cached image volumes. Why can't it work with Kubernetes? Questions, (maybe if you get time to play with cinder's caching to get a better understanding): 1. How does cinder's caching behaves when multiple volumes are created in parallel from a newly created image? Will it wait for the cache to be created before creating the volumes or just start all volume creations in parallel? [Li, Xiaoyan] Inside a volume service it is sequential to run volume creation tasks. But as we have HA. For image cache, it creates an entry in cinder db at first and then creates volumes. The primary key is not image_id+backend_storage. It is possible that several entries or volumes will be created in same backend storage. 2. What is the cinder backend that store the cache? If it is the one used by the volume, will this lead to multiple cached volumes of the same image? Can we chose the backend? [Li, Xiaoyan] We can set whether enabled cache per backend. If users create a volume in backend ceph from an image, an cached image volume will be created in Ceph if it is enabled. Next time if users create a volume in IBM storage from the same image, it will create another image cached volume in IBM storage if it is enabled. 3. How is cache space provisioned? Do we need to restart cinder-volume for changes to take effect? [Li, Xiaoyan] These config needs to be done in config file. So it needs to restart cinder volume services once config are changed. 4. Is admin able to clean up individual cached images in the shadow tenant? Maybe also user? [Li, Xiaoyan] Admin and shadow tenants can both do cleanup. Ovidiu ________________________________ From: Li, Xiaoyan [xiaoyan.li at intel.com] Sent: Thursday, November 22, 2018 2:41 AM To: Poncea, Ovidiu; Rowsell, Brent; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi Brent and Ovidiu, As this email has a long history, I re-summarize the raw cache in StarlingX and Cinder upstream image cache. Please vote whether we can abandon raw cache in StarlingX. StarlingX Create an image cache in ceph when Glance creates an image. And delete the cached image in ceph when deleting the original image in Glance. Cinder: When creating a volume from an image in a backend storage at the first time, Cinder creates a volume from this image, and uses it as the image cache. So next time if users create another volume from this image in the same backend storage, Cinder at first finds out the cached image volume and clones a new volume from it. Cinder allows capacity configuration for cached images. If the space is used up, Cinder will evict the cached image volumes. >From my viewpoint, Cinder image cache can achieve same functionality as Raw cache in StarlingX with more enhancement. It is for all Cinder supported backend storage, not just for Ceph. Best wishes Lisa From: Li, Xiaoyan Sent: Monday, November 19, 2018 9:44 AM To: Poncea, Ovidiu >; Rowsell, Brent >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi Ovidiu, A cached image ( new volume from this image) is created on a storage backend when Cinder firstly creates a volume in the same backend storage from the image. All the information are stored in Cinder, including volume id, image id etc. https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/manager.py#L1368 https://github.com/openstack/cinder/blob/stable/pike/cinder/image/cache.py#L82 A cached image is deleted when the configure space for cache is used up. So currently Cinder doesn't delete the cached image volumes even if the image is deleted. But this can be an enhancement of current cinder image cache. https://github.com/openstack/cinder/blob/stable/pike/cinder/image/cache.py#L117 https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/manager.py#L1351 Best wishes Lisa From: Poncea, Ovidiu [mailto:Ovidiu.Poncea at windriver.com] Sent: Friday, November 16, 2018 4:57 PM To: Li, Xiaoyan >; Rowsell, Brent >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi Li, Quick question: Is cache going to be freed when an image is deleted from glance? It would be a waste to cache images that are no longer needed. Thanks, Ovidiu ________________________________ From: Li, Xiaoyan [xiaoyan.li at intel.com] Sent: Tuesday, November 13, 2018 9:19 AM To: Rowsell, Brent; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi, About the raw cache function in StarlingX Cinder and Glance, I would like to remove it as Cinder has similar function. Please see following detail. And if I would like to remove the function in StarlingX, there are two methods: 1. Submit a patch to revert the changes in Glance and Cinder. 2. Ignore these patches during upgrading StarlingX/Cinder to new Cinder release. Which way do we prefer to? Best wishes Lisa From: Li, Xiaoyan Sent: Thursday, September 20, 2018 10:17 AM To: Rowsell, Brent >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi, Brent The following are mechanism of Cinder volume cache. Creation of cached volume: It creates a cached volume in the backend storage when creating from an image. 1. Create_from_image: https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L890 2. Return image cache entry: If not existed, it creates a new entry. https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L746 3. Create a new image-volume and cache entry for it: https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L872 Use a cached volume when creating a volume: https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L723-L735 Delete the cache volume: When capacity and number of cache entries exceed specified limit, it deletes cache entries (cached volumes). https://github.com/openstack/cinder/blob/stable/pike/cinder/image/cache.py#L164 Best wishes Lisa From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Thursday, September 6, 2018 10:02 AM To: Li, Xiaoyan >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching We would need to review this feature to ensure it provides equivalent functionality first. If it does, great, we can look at reverting and enabling this cinder functionality. Brent From: Li, Xiaoyan [mailto:xiaoyan.li at intel.com] Sent: Wednesday, September 5, 2018 9:59 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi all, This email is about Raw caching function in StarlingX. This feature is to cache an image in backend storage like Ceph when we first create a volume in this backend storage. In fact, Cinder upstream has already had a similar function in Pike release. https://specs.openstack.org/openstack/cinder-specs/specs/liberty/image-volume-cache.html So I want to revert Raw caching function in StarlingX, and use Cinder generic image cache instead. The problem is that we need to update Cinder config in StarlingX. Any comments? Best wishes Lisa -------------- next part -------------- An HTML attachment was scrubbed... URL: From sajuptpm at gmail.com Tue Nov 27 08:35:08 2018 From: sajuptpm at gmail.com (Saju M) Date: Tue, 27 Nov 2018 14:05:08 +0530 Subject: [Starlingx-discuss] Use of sysinv_api_bind_ip and sysinv_api_pxeboot_ip, Difference ? In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA3F2564@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA3F2564@ALA-MBD.corp.ad.wrs.com> Message-ID: HI, Thanks Luis and Penny. *1)* I am getting error "Cannot assign requested address" when I start sysinv-api.service. 2018-11-26 08:46:09.324 18046 ERROR oslo.service.wsgi [-] Could not bind to 169.254.202.2:6385 <===Error 2018-11-26 08:46:09.326 18046 CRITICAL sysinv [-] [Errno 99] Cannot assign requested address Error: http://paste.openstack.org/show/735998/ *2)* I can't ping to 169.254.202.2. Do I miss any network configuration. I am trying "Simplex" mode. controller-0:~$ controller-0:~$ ping 169.254.202.2 PING 169.254.202.2 (169.254.202.2) 56(84) bytes of data. ^C --- 169.254.202.2 ping statistics --- 23 packets transmitted, 0 received, 100% packet loss, time 22005ms *3)* Attached "/tmp/config/cgcs_config" and output of "ifconfig -a" http://dpaste.com/0TW920F Regards Saju Madhavan +91 09535134654 On Tue, Nov 27, 2018 at 3:43 AM Penney, Don wrote: > The 169.254.202.2 address is assigned for pxeboot: > > > > controller-0:~$ sudo grep -r 169.254.202.2 /etc 2>/dev/null > > /etc/sysinv/sysinv.conf:sysinv_api_pxeboot_ip=169.254.202.2 > > > /etc/dnsmasq.conf:dhcp-range=set:pxeboot,169.254.202.2,169.254.202.254,255.255.255.0,1h > > /etc/dnsmasq.conf:dhcp-option=tag:pxeboot,option:dns-server,169.254.202.2 > > > /etc/dnsmasq.conf:dhcp-boot=tag:bios,tag:pxeboot,pxelinux.0,pxecontroller,169.254.202.2 > > > /etc/dnsmasq.conf:dhcp-boot=tag:efi,tag:pxeboot,EFI/grubx64.efi,pxecontroller,169.254.202.2 > > /etc/hosts:169.254.202.2 pxecontroller > > > > The address gets added to the mgmt interface on the active controller, for > responding to pxeboot/dhcp requests from hosts during installation from the > active controller. Sysinv binds to the address so that it can respond to > limited API queries and notifications that occur during the installation > process. > > > > > > *From:* Luis Ramirez [mailto:luis.ramirez at opencloud.es] > *Sent:* Monday, November 26, 2018 5:04 PM > *To:* sajuptpm at gmail.com > *Cc:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] Use of sysinv_api_bind_ip and > sysinv_api_pxeboot_ip, Difference ? > > > > Hi, > > > > This IP is provided by Automatic Private IP Addressing. This process > assigns an IP address even in the absence of a DHCP server. If a DISCOVER > message is not answered, the client picks a random 16-bit number and > prepends it with 169.254.x.x. It performs a gratuitous ARP and assigns that > address to itself. It means that the DHCP server is not reachable. > > > > Br, > > Luis Rmz > > Blockchain, DevOps & Open Source Cloud Solutions Architect > > ---------------------------------------- > > Founder & CEO > > OpenCloud.es > > luis.ramirez at opencloud.es > > Skype ID: d.overload > > Hangouts: luis.ramirez at opencloud.es > > [image: Image removed by sender. ] +34 682 740 973 / [image: Image > removed by sender. ]+39 392 1289553 / [image: Image removed by sender. ]+49 > 152 26917722 / Česká republika: +420 774 274 882 > > ----------------------------------------------------- > > > > > > El lun., 26 nov. 2018 a las 10:39, Saju M () escribió: > > HI, > > > > I have noticed that sysinv is trying to listen to 6385 with 2 different > IPs. > > I dont know, How 169.254.202.2 came in etc/sysinv/sysinv.conf, I could not > find that IP in hiera. > > > > Error from /var/log/sysinv.log > > ========================== > > 2018-11-26 08:46:09.298 18046 INFO oslo.service.wsgi [-] sysinv_api > listening on *0.0.0.0:6385 * > > ERROR oslo.service.wsgi [-] Could not bind to *169.254.202.2:6385 > * > > > > http://paste.openstack.org/show/735998/ > > > > Somebody please explain the use of sysinv_api() and sysinv_pxe() > > ========================================== > > > https://github.com/openstack/stx-config/blob/ddb407fccbf5d5490400f21d26973ff5a148d737/sysinv/sysinv/sysinv/sysinv/cmd/api.py#L68 > > > > > https://github.com/openstack/stx-config/blob/ddb407fccbf5d5490400f21d26973ff5a148d737/sysinv/sysinv/sysinv/sysinv/api/__init__.py#L28 > > > > Regards > Saju Madhavan > +91 09535134654 > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ~WRD000.jpg Type: image/jpeg Size: 823 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ~WRD000.jpg Type: image/jpeg Size: 823 bytes Desc: not available URL: From austin.sun at intel.com Tue Nov 27 09:18:23 2018 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 27 Nov 2018 09:18:23 +0000 Subject: [Starlingx-discuss] Support IBRS cpu model. In-Reply-To: <08e3677f-39dc-bc99-2791-c88468e17c4a@windriver.com> References: <08e3677f-39dc-bc99-2791-c88468e17c4a@windriver.com> Message-ID: Hi Chris: Thanks your suggestion. I have done some more test . Here is the result. Compute CPU: Skylake-IBRS, If we created VM with non-IBRS CPU model(Skylake-server, Broadwell etc), it worked fine with patch. But when create VM with IBRS CPU model, Qemu will report below error "2018-11-27T08:42:23.764924Z qemu-kvm: can't apply global Broadwell-x86_64-cpu.spec-ctrl=on: Property '.spec-ctrl' not found" Or "qemu-kvm: can't apply global Skylake-Server-x86_64-cpu.spec-ctrl=on: Property '.spec-ctrl' not found" From link[1]: it seems we have to upgrade qemu to check if we can fully support *IBRS cpu model. Currently we can only create non-IBRS CPU model or passthrough with those two patches [2] and [3] [1] https://bugzilla.redhat.com/show_bug.cgi?id=1532401 [2] https://github.com/starlingx-staging/stx-nova/pull/17 [3] https://github.com/starlingx-staging/stx-glance/pull/5 Thanks. BR Austin Sun. -----Original Message----- From: Chris Friesen [mailto:chris.friesen at windriver.com] Sent: Friday, November 23, 2018 11:08 PM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Support IBRS cpu model. In order to ensure that we don't break existing code, I think we'd also need to test by booting VMs built using at least a flavor that specifies a different IBRS CPU model and a different non-IBRS CPU model. Chris On 11/23/2018 12:16 AM, Sun, Austin wrote: > Hi Chris: > Due to resource limitation , I only deployed in Skylake-IBIS server , create VM enabling cpu-passthrough. > > Thanks. > BR > Austin Sun. > -----Original Message----- > From: Chris Friesen [mailto:chris.friesen at windriver.com] > Sent: Friday, November 23, 2018 1:42 AM > To: Sun, Austin ; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Support IBRS cpu model. > > On 11/21/2018 11:46 PM, Sun, Austin wrote: >> Hi Chris: >> Very appreciate your review >> The new PRs are >> https://github.com/starlingx-staging/stx-nova/pull/17 >> https://github.com/starlingx-staging/stx-glance/pull/5 > > What testing have you done on these changes? > > Chris > From cindy.xie at intel.com Tue Nov 27 09:47:37 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 27 Nov 2018 09:47:37 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack Distro meeting, 11/28 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35DD196C@SHSMSX104.ccr.corp.intel.com> Agenda for 11/28 meeting: 1. Kernel upgrade to 4.19 (LTS) feasibility discussion (Saul/Victor) 2. kernel driver upgrade testing status update (Ada/Ricardo/Shuicheng) 3. non-Openstack patch refactoring status (Zhipeng) 4. non-Openstack source patch upstream study (Saul) 5. Python2to3 non-Openstack status (Austin) 6. Ceph upgrade status (Vivian/Dehao) 7. DevStack flocks plug-in status (Erick/Mingyuan/Yi/Dean) 8. Opens (all) -----Original Appointment----- From: Xie, Cindy Sent: Monday, November 5, 2018 2:27 PM To: Xie, Cindy; Wold, Saul; 'Rowsell, Brent'; Jones, Bruce E; Troyer, Dean; 'Khalil, Ghada'; Waheed, Numan; Lin, Shuicheng; Zhu, Vivian; Shang, Dehao; Liu, ZhipengS; Hu, Yong; Sun, Austin; Somerville, Jim; starlingx-discuss at lists.starlingx.io Cc: Perez Carranza, Jose; 'Hellmann, Gil'; 'Waines, Greg'; 'Chen, Jacky'; Armstrong, Robert H; Perez Rodriguez, Humberto I; Martinez Landa, Hayde; Martinez Monroy, Elio; Hu, Wei W; 'Seiler, Glenn'; 'Eslimi, Dariush'; Gomez, Juan P; Lara, Cesar; Young, Ken; Arce Moreno, Abraham Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, November 28, 2018 6:00 AM-7:00 AM (UTC-08:00) Pacific Time (US & Canada). Where: https://zoom.us/j/342730236 . Cadence and time slot: o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) . Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ . Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other From zhang.kunpeng at 99cloud.net Tue Nov 27 10:32:02 2018 From: zhang.kunpeng at 99cloud.net (=?gb2312?B?1cX278X0?=) Date: Tue, 27 Nov 2018 18:32:02 +0800 Subject: [Starlingx-discuss] How does the function of Sensors in Host Inventory work? Message-ID: <5318C81C-3B38-45E2-AF39-CEBA93DE2335@99cloud.net> Hi, I deployed a simplex starlingx with bare metal. Nothing were shown when I execute " system host-sensor-list controller-0” ``` [wrsroot at controller-0 ~(keystone_admin)]$ system host-sensor-list controller-0 [wrsroot at controller-0 ~(keystone_admin)]$ ``` Is this correct? Which sensor will be shown? I am a beginner, and I don’t know who I can ask. Is anybody tell me how to use the sensors function? From liang.a.fang at intel.com Tue Nov 27 10:36:50 2018 From: liang.a.fang at intel.com (Fang, Liang A) Date: Tue, 27 Nov 2018 10:36:50 +0000 Subject: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming In-Reply-To: References: Message-ID: Hi Irina Thanks for the info. Some status: - I can reproduce the issue that solved in _convert_image(). The issue I reproduced may be not the same one as the original issue this patch to fix. Reproduced by: uploading a volume to image, but with insufficient space in image_conversion_dir. - But I still cannot reproduce the issue solved in _create_from_image_cache_or_download() even with multiple volume creating requests. Take two requests as example, the second request will be rejected by image_utils.check_available_space() at the beginning of _create_from_image_cache_or_download(). If I add debug code - sleep(60) after the line of image_utils.check_available_space, so that both two requests can pass the check, but the second request will raise exception(ImageTooBig) and be caught in the line 777, 810: "image_utils.TemporaryImages.fetch". And I take a look of other code following, don't find any chance of raising "IOError". o verify_glance_image_signature o volume_glance_metadata_bulk_create o qemu_img_info o check_virtual_size o _create_from_image_download: This will re-use image file. Even insufficient space happen, the exception be re-raised is exception.InsufficientConversionSpace, not "IOError". If you can get the original reproduce steps, that would be great! Some info related: Change-Id: Ie5eba32f92eb1740554bfc44baf612e326d6fde5, submitted in this year, with 4 commits, shows dest will be a volume. So unlikely be the same as image_conversion_dir. Thanks, Liang From: Mihai, Irina [mailto:Irina.Mihai at windriver.com] Sent: Tuesday, November 27, 2018 1:25 AM To: Fang, Liang A Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming Hi Liang, This patch was covering the scenario when we're trying to create multiple volumes from image at the same time. In this situation, multiple downloads/convertions would be allowed to start since there would still be conversion space left, but eventually the operation would fail because of the disk being full. This is not caught by any of the "ImageTooBig" or "ImageUnacceptable" exceptions. Could you please help to address one doubt: why image is converted in the same location with image itself? This patch is to create a volume from image, right? Right, but I'm not aware of the reasoning behind this. However, if the used image is qcow2 then it needs to be converted to raw before being saved to the volume. Please let me know if I can help in any other way. Thanks, Irina ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Sunday, November 25, 2018 11:44 AM To: Mihai, Irina Cc: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming Hi Irina Code review: https://review.openstack.org/#/c/618976/ I'm working of upstreaming this patch. Could you please help to address one doubt: why image is converted in the same location with image itself? This patch is to create a volume from image, right? I take a look of related code, the destination location would be the newly created volume and the source location is configured in cinder.conf, something like: image_conversion_dir = /mnt/d100m/image_conversion_dir I did an experiment, in the latest master branch of cinder upstream repo: - If image_conversion_dir has no space to store the downloading image, the exception ImageTooBig will be caught in the beginning of _create_from_image_cache_or_download(). - If has space to store the image, but dest volume size is smaller than image's virtual size, an exception "ImageUnacceptable" will raised by check_virtual_size. So it seems no chance to go to the situation this patch aimed to solve. Could you please help to give more background of this patch? Or if you think this patch is invalid now, please just tell me, I will mark this patch as abandoned. Thanks Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Nov 27 14:24:38 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 27 Nov 2018 14:24:38 +0000 Subject: [Starlingx-discuss] Use of sysinv_api_bind_ip and sysinv_api_pxeboot_ip, Difference ? In-Reply-To: References: <6703202FD9FDFF4A8DA9ACF104AE129FBA3F2564@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA3F28D0@ALA-MBD.corp.ad.wrs.com> Are you trying to manually start sysinv-api.service? This and other controller platform services are managed by SM, as are the floating controller and pxecontroller (169.254.202.2) IP addresses. I’m assuming you have successfully run config_controller? Have you checked the state of services under SM (sudo sm-dump)? From: Saju M [mailto:sajuptpm at gmail.com] Sent: Tuesday, November 27, 2018 3:35 AM To: Penney, Don Cc: luis.ramirez at opencloud.es; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Use of sysinv_api_bind_ip and sysinv_api_pxeboot_ip, Difference ? HI, Thanks Luis and Penny. 1) I am getting error "Cannot assign requested address" when I start sysinv-api.service. 2018-11-26 08:46:09.324 18046 ERROR oslo.service.wsgi [-] Could not bind to 169.254.202.2:6385 <===Error 2018-11-26 08:46:09.326 18046 CRITICAL sysinv [-] [Errno 99] Cannot assign requested address Error: http://paste.openstack.org/show/735998/ 2) I can't ping to 169.254.202.2. Do I miss any network configuration. I am trying "Simplex" mode. controller-0:~$ controller-0:~$ ping 169.254.202.2 PING 169.254.202.2 (169.254.202.2) 56(84) bytes of data. ^C --- 169.254.202.2 ping statistics --- 23 packets transmitted, 0 received, 100% packet loss, time 22005ms 3) Attached "/tmp/config/cgcs_config" and output of "ifconfig -a" http://dpaste.com/0TW920F Regards Saju Madhavan +91 09535134654 On Tue, Nov 27, 2018 at 3:43 AM Penney, Don > wrote: The 169.254.202.2 address is assigned for pxeboot: controller-0:~$ sudo grep -r 169.254.202.2 /etc 2>/dev/null /etc/sysinv/sysinv.conf:sysinv_api_pxeboot_ip=169.254.202.2 /etc/dnsmasq.conf:dhcp-range=set:pxeboot,169.254.202.2,169.254.202.254,255.255.255.0,1h /etc/dnsmasq.conf:dhcp-option=tag:pxeboot,option:dns-server,169.254.202.2 /etc/dnsmasq.conf:dhcp-boot=tag:bios,tag:pxeboot,pxelinux.0,pxecontroller,169.254.202.2 /etc/dnsmasq.conf:dhcp-boot=tag:efi,tag:pxeboot,EFI/grubx64.efi,pxecontroller,169.254.202.2 /etc/hosts:169.254.202.2 pxecontroller The address gets added to the mgmt interface on the active controller, for responding to pxeboot/dhcp requests from hosts during installation from the active controller. Sysinv binds to the address so that it can respond to limited API queries and notifications that occur during the installation process. From: Luis Ramirez [mailto:luis.ramirez at opencloud.es] Sent: Monday, November 26, 2018 5:04 PM To: sajuptpm at gmail.com Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Use of sysinv_api_bind_ip and sysinv_api_pxeboot_ip, Difference ? Hi, This IP is provided by Automatic Private IP Addressing. This process assigns an IP address even in the absence of a DHCP server. If a DISCOVER message is not answered, the client picks a random 16-bit number and prepends it with 169.254.x.x. It performs a gratuitous ARP and assigns that address to itself. It means that the DHCP server is not reachable. Br, Luis Rmz Blockchain, DevOps & Open Source Cloud Solutions Architect ---------------------------------------- Founder & CEO OpenCloud.es luis.ramirez at opencloud.es Skype ID: d.overload Hangouts: luis.ramirez at opencloud.es [Image removed by sender. ] +34 682 740 973 / [Image removed by sender. ] +39 392 1289553 / [Image removed by sender. ] +49 152 26917722 / Česká republika: +420 774 274 882 ----------------------------------------------------- El lun., 26 nov. 2018 a las 10:39, Saju M (>) escribió: HI, I have noticed that sysinv is trying to listen to 6385 with 2 different IPs. I dont know, How 169.254.202.2 came in etc/sysinv/sysinv.conf, I could not find that IP in hiera. Error from /var/log/sysinv.log ========================== 2018-11-26 08:46:09.298 18046 INFO oslo.service.wsgi [-] sysinv_api listening on 0.0.0.0:6385 ERROR oslo.service.wsgi [-] Could not bind to 169.254.202.2:6385 http://paste.openstack.org/show/735998/ Somebody please explain the use of sysinv_api() and sysinv_pxe() ========================================== https://github.com/openstack/stx-config/blob/ddb407fccbf5d5490400f21d26973ff5a148d737/sysinv/sysinv/sysinv/sysinv/cmd/api.py#L68 https://github.com/openstack/stx-config/blob/ddb407fccbf5d5490400f21d26973ff5a148d737/sysinv/sysinv/sysinv/sysinv/api/__init__.py#L28 Regards Saju Madhavan +91 09535134654 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: image001.jpg URL: From changcheng.liu at intel.com Tue Nov 27 14:48:14 2018 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Tue, 27 Nov 2018 14:48:14 +0000 Subject: [Starlingx-discuss] stx-ceph patch commit detail: Add .gitreview In-Reply-To: <0D7994A90DD70040A9F5E77C4D23C57D50EFAE57@SHSMSX104.ccr.corp.intel.com> References: <0D7994A90DD70040A9F5E77C4D23C57D50EFAE57@SHSMSX104.ccr.corp.intel.com> Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50EFC3E1@SHSMSX104.ccr.corp.intel.com> Hi Dean, Please help us understand your patch if you're available. B.R. Changcheng From: Liu, Changcheng Sent: Friday, November 23, 2018 3:19 PM To: Troyer, Dean ; 'starlingx-discuss at lists.starlingx.io' Cc: Poncea, Ovidiu Subject: stx-ceph patch commit detail: Add .gitreview Hi Dean, I'm porting stx-ceph/v10.2.6 upgrade patches to be stx-ceph/v13.2.2 Both WindRiver and I have the question about below patch: Add .gitreview https://github.com/starlingx-staging/stx-ceph/commit/9d93e43290d3a2a0399af75fcb9f7c5a0291e0cc What's the function of the above patch? Do we still need it in stx-ceph/v13.2.2? Regards, Changcheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From changcheng.liu at intel.com Tue Nov 27 14:48:32 2018 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Tue, 27 Nov 2018 14:48:32 +0000 Subject: [Starlingx-discuss] stx-ceph patch commit detail: StarlingX open source release updates In-Reply-To: <0D7994A90DD70040A9F5E77C4D23C57D50EF968C@SHSMSX104.ccr.corp.intel.com> References: <0D7994A90DD70040A9F5E77C4D23C57D50EF968C@SHSMSX104.ccr.corp.intel.com> Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50EFC3EF@SHSMSX104.ccr.corp.intel.com> Hi Dean, Please help us understand your patch if you're available. B.R. Changcheng From: Liu, Changcheng Sent: Thursday, November 22, 2018 7:27 AM To: Troyer, Dean ; starlingx-discuss at lists.starlingx.io Subject: stx-ceph patch commit detail: StarlingX open source release updates Hi Dean, I'm porting stx-ceph/v10.2.6 upgrade patches to be v13.2.2 There's one giant below patch submitted by you. StarlingX open source release updates https://github.com/starlingx-staging/stx-ceph/commit/3f07f7ff1a5c7bfa8d0de12c966594d5fb7cf4ec Please confirm whether the above patch is generated by below method. 1) git clone https://github.intel.com/Madawaska/download.ceph.com.rpm.jewel.el7; cd download.ceph.com.rpm.jewel.el7 2) git reset --soft db5aab71333112e1afc170b685c7599cf1f848ce 3) squash all below patches into one giant patch and applied on the code repository in 2) https://github.intel.com/Madawaska/download.ceph.com.rpm.jewel.el7/compare/db5aab713...868280aa8 4) git commit -s -m "StarlingX open source release updates" Besides that above changes, please let us know whether there're separate changes in the commit "StarlingX open source release updates". This is quiet important. B.R. Changcheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From sajuptpm at gmail.com Tue Nov 27 15:27:33 2018 From: sajuptpm at gmail.com (Saju M) Date: Tue, 27 Nov 2018 20:57:33 +0530 Subject: [Starlingx-discuss] Use of sysinv_api_bind_ip and sysinv_api_pxeboot_ip, Difference ? In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA3F28D0@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA3F2564@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA3F28D0@ALA-MBD.corp.ad.wrs.com> Message-ID: HI, I am not trying to start sysinv-api.service manually. I am trying simplex mode installation. 1) “sudo config_controller” failing at “04/08 Populating initial system inventory” https://ibb.co/x7yySdz I have been debugging this issue and find that “sysinv” service is not running. 2) You can see the error here. /var/log/sysinv.log http://dpaste.com/25WYG10 3) output of “sudo sm-dump” and “sudo systemctl status sysinv-api.service” http://dpaste.com/3CSSCK9 4) Since “sysinv” service is not up, _populate_system_config(self, client) call is not getting result. https://github.com/openstack/stx-config/blob/e0219a96d2d51076d9edb607cada7c148570544a/controllerconfig/controllerconfig/controllerconfig/configassistant.py#L3667 systems = client.sysinv.isystem.list() Regards Saju Madhavan +91 09535134654 On Tue, Nov 27, 2018 at 7:55 PM Penney, Don wrote: > Are you trying to manually start sysinv-api.service? This and other > controller platform services are managed by SM, as are the floating > controller and pxecontroller (169.254.202.2) IP addresses. I’m assuming you > have successfully run config_controller? Have you checked the state of > services under SM (sudo sm-dump)? > > > > > > *From:* Saju M [mailto:sajuptpm at gmail.com] > *Sent:* Tuesday, November 27, 2018 3:35 AM > *To:* Penney, Don > *Cc:* luis.ramirez at opencloud.es; starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] Use of sysinv_api_bind_ip and > sysinv_api_pxeboot_ip, Difference ? > > > > HI, > > > > Thanks Luis and Penny. > > > > *1)* > > I am getting error "Cannot assign requested address" when I start > sysinv-api.service. > > 2018-11-26 08:46:09.324 18046 ERROR oslo.service.wsgi [-] Could not bind to 169.254.202.2:6385 <===Error > > 2018-11-26 08:46:09.326 18046 CRITICAL sysinv [-] [Errno 99] Cannot assign requested address > > Error: http://paste.openstack.org/show/735998/ > > > > *2)* > > I can't ping to 169.254.202.2. Do I miss any network configuration. I am > trying "Simplex" mode. > > > > controller-0:~$ > > controller-0:~$ ping 169.254.202.2 > PING 169.254.202.2 (169.254.202.2) 56(84) bytes of data. > ^C > --- 169.254.202.2 ping statistics --- > 23 packets transmitted, 0 received, 100% packet loss, time 22005ms > > *3)* > > Attached "/tmp/config/cgcs_config" and output of "ifconfig -a" > > http://dpaste.com/0TW920F > > > > Regards > Saju Madhavan > +91 09535134654 > > > > > > On Tue, Nov 27, 2018 at 3:43 AM Penney, Don > wrote: > > The 169.254.202.2 address is assigned for pxeboot: > > > > controller-0:~$ sudo grep -r 169.254.202.2 /etc 2>/dev/null > > /etc/sysinv/sysinv.conf:sysinv_api_pxeboot_ip=169.254.202.2 > > > /etc/dnsmasq.conf:dhcp-range=set:pxeboot,169.254.202.2,169.254.202.254,255.255.255.0,1h > > /etc/dnsmasq.conf:dhcp-option=tag:pxeboot,option:dns-server,169.254.202.2 > > > /etc/dnsmasq.conf:dhcp-boot=tag:bios,tag:pxeboot,pxelinux.0,pxecontroller,169.254.202.2 > > > /etc/dnsmasq.conf:dhcp-boot=tag:efi,tag:pxeboot,EFI/grubx64.efi,pxecontroller,169.254.202.2 > > /etc/hosts:169.254.202.2 pxecontroller > > > > The address gets added to the mgmt interface on the active controller, for > responding to pxeboot/dhcp requests from hosts during installation from the > active controller. Sysinv binds to the address so that it can respond to > limited API queries and notifications that occur during the installation > process. > > > > > > *From:* Luis Ramirez [mailto:luis.ramirez at opencloud.es] > *Sent:* Monday, November 26, 2018 5:04 PM > *To:* sajuptpm at gmail.com > *Cc:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] Use of sysinv_api_bind_ip and > sysinv_api_pxeboot_ip, Difference ? > > > > Hi, > > > > This IP is provided by Automatic Private IP Addressing. This process > assigns an IP address even in the absence of a DHCP server. If a DISCOVER > message is not answered, the client picks a random 16-bit number and > prepends it with 169.254.x.x. It performs a gratuitous ARP and assigns that > address to itself. It means that the DHCP server is not reachable. > > > > Br, > > Luis Rmz > > Blockchain, DevOps & Open Source Cloud Solutions Architect > > ---------------------------------------- > > Founder & CEO > > OpenCloud.es > > luis.ramirez at opencloud.es > > Skype ID: d.overload > > Hangouts: luis.ramirez at opencloud.es > > [image: Image removed by sender. ] +34 682 740 973 / [image: Image > removed by sender. ]+39 392 1289553 / [image: Image removed by sender. ]+49 > 152 26917722 / Česká republika: +420 774 274 882 > > ----------------------------------------------------- > > > > > > El lun., 26 nov. 2018 a las 10:39, Saju M () escribió: > > HI, > > > > I have noticed that sysinv is trying to listen to 6385 with 2 different > IPs. > > I dont know, How 169.254.202.2 came in etc/sysinv/sysinv.conf, I could not > find that IP in hiera. > > > > Error from /var/log/sysinv.log > > ========================== > > 2018-11-26 08:46:09.298 18046 INFO oslo.service.wsgi [-] sysinv_api > listening on *0.0.0.0:6385 * > > ERROR oslo.service.wsgi [-] Could not bind to *169.254.202.2:6385 > * > > > > http://paste.openstack.org/show/735998/ > > > > Somebody please explain the use of sysinv_api() and sysinv_pxe() > > ========================================== > > > https://github.com/openstack/stx-config/blob/ddb407fccbf5d5490400f21d26973ff5a148d737/sysinv/sysinv/sysinv/sysinv/cmd/api.py#L68 > > > > > https://github.com/openstack/stx-config/blob/ddb407fccbf5d5490400f21d26973ff5a148d737/sysinv/sysinv/sysinv/sysinv/api/__init__.py#L28 > > > > Regards > Saju Madhavan > +91 09535134654 > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: not available URL: From saul.wold at intel.com Tue Nov 27 16:26:41 2018 From: saul.wold at intel.com (Wold, Saul) Date: Tue, 27 Nov 2018 16:26:41 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack Distro meeting, 11/28 In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F35DD196C@SHSMSX104.ccr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F35DD196C@SHSMSX104.ccr.corp.intel.com> Message-ID: <413BC967A3F41F49851BDEF27A77637C558DAD53@ORSMSX113.amr.corp.intel.com> Please add Qemu Update (Ghada) to the adgenda. I am not sure we are ready to talk about 4.19 kernel upgrade, that's more a Clear, Multi-OS (for Ubuntu) discussion currently. Sau! ________________________________________ From: Xie, Cindy Sent: Tuesday, November 27, 2018 1:47 AM To: Rowsell, Brent; Wold, Saul; Rodriguez Bahena, Victor; Cabrales, Ada; Perez, Ricardo O; Lin, Shuicheng; Liu, ZhipengS; Sun, Austin; Zhu, Vivian; Shang, Dehao; Cardona Ruiz, Erick; Qi, Mingyuan; Wang, Yi C; Troyer, Dean; starlingx-discuss at lists.starlingx.io Subject: Agenda: Weekly StarlingX non-OpenStack Distro meeting, 11/28 Agenda for 11/28 meeting: 1. Kernel upgrade to 4.19 (LTS) feasibility discussion (Saul/Victor) 2. kernel driver upgrade testing status update (Ada/Ricardo/Shuicheng) 3. non-Openstack patch refactoring status (Zhipeng) 4. non-Openstack source patch upstream study (Saul) 5. Python2to3 non-Openstack status (Austin) 6. Ceph upgrade status (Vivian/Dehao) 7. DevStack flocks plug-in status (Erick/Mingyuan/Yi/Dean) 8. Opens (all) -----Original Appointment----- From: Xie, Cindy Sent: Monday, November 5, 2018 2:27 PM To: Xie, Cindy; Wold, Saul; 'Rowsell, Brent'; Jones, Bruce E; Troyer, Dean; 'Khalil, Ghada'; Waheed, Numan; Lin, Shuicheng; Zhu, Vivian; Shang, Dehao; Liu, ZhipengS; Hu, Yong; Sun, Austin; Somerville, Jim; starlingx-discuss at lists.starlingx.io Cc: Perez Carranza, Jose; 'Hellmann, Gil'; 'Waines, Greg'; 'Chen, Jacky'; Armstrong, Robert H; Perez Rodriguez, Humberto I; Martinez Landa, Hayde; Martinez Monroy, Elio; Hu, Wei W; 'Seiler, Glenn'; 'Eslimi, Dariush'; Gomez, Juan P; Lara, Cesar; Young, Ken; Arce Moreno, Abraham Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, November 28, 2018 6:00 AM-7:00 AM (UTC-08:00) Pacific Time (US & Canada). Where: https://zoom.us/j/342730236 • Cadence and time slot: o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) • Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ • Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other From cesar.lara at intel.com Tue Nov 27 17:52:19 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Tue, 27 Nov 2018 17:52:19 +0000 Subject: [Starlingx-discuss] [build][meetings] Build team meeting minutes 11/22/2018 Message-ID: <0B566C62EC792145B40E29EFEBF1AB471056F6E5@fmsmsx104.amr.corp.intel.com> Build team meeting minutes 11/22/2018 Attendees Ken, Scott, Jason, Saul, Marcela, Mario, Abraham, Memo, Erich, Victor, Cesar, Felipe Agenda - Cengn follow up - Ken - Mirror script refactor - Marcela - Build team Imperatives for next release Meeting Minutes Cengn follow up - we are getting close to have a daily build against master branch for StarlingX and generate the ISO and the build artifacts like the installer. On the build issues we were having on the Intel Infrastructure, where it fails based on changes to the .lst files containing the packages required, we agreed upon to have a higher frequency on the update of this files. These specific failures were due the order in which the PRs were accepted in our Gerrit queue. AR - Scott and Jason to post the right order for changing packages and summiting patches around those, and also writing an Spec about it. Build team Imperatives for next release - - Support containerization of StarlingX bits - Enable users on the mirror - Include support for Golang packages Mirror script refactor Presentation on the proposal, the code and spec will follow up. Questions - About the plan to integrate this tool? We will have to live with both scripts for at least a release cycle until we can deprecate the old script. We need to discuss further about the options with the Yaml files that this new script relies on. Opens AR - Abraham to follow up on changes to the documentation for using a single Docker file, need this readme file to be posted to wiki and fed to StarlingX official documentation AR - All - need to +1 +2 the PR about the consolidation of the Docker files and the changes to this documentation Scott - Discussion around the enabling of GO for distros, not an easy problem to solve since it requires network connectivity during build time. Discussion of options to be followed up on Mailing List. Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From Irina.Mihai at windriver.com Tue Nov 27 18:01:41 2018 From: Irina.Mihai at windriver.com (Mihai, Irina) Date: Tue, 27 Nov 2018 18:01:41 +0000 Subject: [Starlingx-discuss] Build Broken Message-ID: Hi, I've just pulled the latest code from master and see the error below in stx-integ. It gets passed that if you checkout HEAD~ Thanks, Irina +++++++++++++++++++ 17:41:54 ============ Build failed ============= 17:41:54 b2: ===== Build SRPM for 'resource-agents' ===== 17:41:54 b2: PKG_BASE=/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents 17:41:54 b2: BUILD_DIR=resource-agents/rpmbuild 17:41:54 b2: SRPM_DIR=/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS 17:41:54 b2: Wrote: /localdisk/loadbuild/wrsroot/starlingx-0-clean/std/rpmbuild/SOURCES/resource-agents/srpm_input.md5 17:41:54 b2: Rebuild required due to new or changed file: stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/PATCH_ORDER 17:41:54 b2: Rebuild required due to missing directory: '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS' 17:41:54 b2: clean_srpm_dir build_idx=2 DIR=/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS 17:41:54 b2: find: ‘/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS’: No such file or directory 17:41:54 b2: resource-agents.spec 17:41:54 b2: resource-agents-3.9.5 17:41:54 b2: srpm_apply_meta_patches '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild' '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents' 0 'centos' 'resource-agents-3.9.5-124.el7' 17:41:54 b2: Applying metadata patches 17:41:54 b2: srpm_apply_patch '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch' '-p1' '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild' 0 'WRS: ' '0' '' '' '' '' 0 'resource-agents-3.9.5-124.el7' '' 17:41:54 b2: patch -p1 < /localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch 17:41:54 b2: patching file SPECS/resource-agents.spec 17:41:54 b2: patch: **** malformed patch at line 67: ./autogen.sh 17:41:54 b2: 17:41:54 b2: failed to apply patch '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch' 17:41:54 b2: ERROR: srpm_apply_meta_patches (1420): failed to apply patch 'spec-include-TiS-patches.patch' 17:41:54 b2: ERROR: build_dir_srpm (785): failed to extract srpm '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/cgcs-centos-repo/Source/resource-agents-3.9.5-124.el7.src.rpm' 17:41:54 ERROR: reaper (1303): Failed to build src.rpm from source at 'b2' -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Tue Nov 27 18:08:21 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Tue, 27 Nov 2018 18:08:21 +0000 Subject: [Starlingx-discuss] Build Broken In-Reply-To: References: Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB324F7F@ALA-MBD.corp.ad.wrs.com> Not sure if this is the cause, but this was pushed this morning https://review.openstack.org/#/c/619398/ Brent From: Mihai, Irina [mailto:Irina.Mihai at windriver.com] Sent: Tuesday, November 27, 2018 1:02 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Build Broken Hi, I've just pulled the latest code from master and see the error below in stx-integ. It gets passed that if you checkout HEAD~ Thanks, Irina +++++++++++++++++++ 17:41:54 ============ Build failed ============= 17:41:54 b2: ===== Build SRPM for 'resource-agents' ===== 17:41:54 b2: PKG_BASE=/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents 17:41:54 b2: BUILD_DIR=resource-agents/rpmbuild 17:41:54 b2: SRPM_DIR=/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS 17:41:54 b2: Wrote: /localdisk/loadbuild/wrsroot/starlingx-0-clean/std/rpmbuild/SOURCES/resource-agents/srpm_input.md5 17:41:54 b2: Rebuild required due to new or changed file: stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/PATCH_ORDER 17:41:54 b2: Rebuild required due to missing directory: '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS' 17:41:54 b2: clean_srpm_dir build_idx=2 DIR=/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS 17:41:54 b2: find: '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS': No such file or directory 17:41:54 b2: resource-agents.spec 17:41:54 b2: resource-agents-3.9.5 17:41:54 b2: srpm_apply_meta_patches '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild' '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents' 0 'centos' 'resource-agents-3.9.5-124.el7' 17:41:54 b2: Applying metadata patches 17:41:54 b2: srpm_apply_patch '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch' '-p1' '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild' 0 'WRS: ' '0' '' '' '' '' 0 'resource-agents-3.9.5-124.el7' '' 17:41:54 b2: patch -p1 < /localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch 17:41:54 b2: patching file SPECS/resource-agents.spec 17:41:54 b2: patch: **** malformed patch at line 67: ./autogen.sh 17:41:54 b2: 17:41:54 b2: failed to apply patch '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch' 17:41:54 b2: ERROR: srpm_apply_meta_patches (1420): failed to apply patch 'spec-include-TiS-patches.patch' 17:41:54 b2: ERROR: build_dir_srpm (785): failed to extract srpm '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/cgcs-centos-repo/Source/resource-agents-3.9.5-124.el7.src.rpm' 17:41:54 ERROR: reaper (1303): Failed to build src.rpm from source at 'b2' -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Nov 27 19:21:49 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 27 Nov 2018 19:21:49 +0000 Subject: [Starlingx-discuss] Build Broken In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB324F7F@ALA-MBD.corp.ad.wrs.com> References: <2588653EBDFFA34B982FAF00F1B4844EBB324F7F@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA3F2B4A@ALA-MBD.corp.ad.wrs.com> I did a repo sync and built just that package: $ build-pkgs --serial --no-descendants --no-required --no-build-info resource-agents And the build failed with the same error. Reverting the commit Brent indicated resolves the build issue. I don't know why the patch would be "malformed". Nothing jumps out at me. Should we just revert it via gerrit and let Zhipeng revisit it when he's online? From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Tuesday, November 27, 2018 1:08 PM To: Mihai, Irina; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Build Broken Not sure if this is the cause, but this was pushed this morning https://review.openstack.org/#/c/619398/ Brent From: Mihai, Irina [mailto:Irina.Mihai at windriver.com] Sent: Tuesday, November 27, 2018 1:02 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Build Broken Hi, I've just pulled the latest code from master and see the error below in stx-integ. It gets passed that if you checkout HEAD~ Thanks, Irina +++++++++++++++++++ 17:41:54 ============ Build failed ============= 17:41:54 b2: ===== Build SRPM for 'resource-agents' ===== 17:41:54 b2: PKG_BASE=/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents 17:41:54 b2: BUILD_DIR=resource-agents/rpmbuild 17:41:54 b2: SRPM_DIR=/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS 17:41:54 b2: Wrote: /localdisk/loadbuild/wrsroot/starlingx-0-clean/std/rpmbuild/SOURCES/resource-agents/srpm_input.md5 17:41:54 b2: Rebuild required due to new or changed file: stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/PATCH_ORDER 17:41:54 b2: Rebuild required due to missing directory: '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS' 17:41:54 b2: clean_srpm_dir build_idx=2 DIR=/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS 17:41:54 b2: find: '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS': No such file or directory 17:41:54 b2: resource-agents.spec 17:41:54 b2: resource-agents-3.9.5 17:41:54 b2: srpm_apply_meta_patches '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild' '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents' 0 'centos' 'resource-agents-3.9.5-124.el7' 17:41:54 b2: Applying metadata patches 17:41:54 b2: srpm_apply_patch '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch' '-p1' '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild' 0 'WRS: ' '0' '' '' '' '' 0 'resource-agents-3.9.5-124.el7' '' 17:41:54 b2: patch -p1 < /localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch 17:41:54 b2: patching file SPECS/resource-agents.spec 17:41:54 b2: patch: **** malformed patch at line 67: ./autogen.sh 17:41:54 b2: 17:41:54 b2: failed to apply patch '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch' 17:41:54 b2: ERROR: srpm_apply_meta_patches (1420): failed to apply patch 'spec-include-TiS-patches.patch' 17:41:54 b2: ERROR: build_dir_srpm (785): failed to extract srpm '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/cgcs-centos-repo/Source/resource-agents-3.9.5-124.el7.src.rpm' 17:41:54 ERROR: reaper (1303): Failed to build src.rpm from source at 'b2' -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Tue Nov 27 19:23:17 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Tue, 27 Nov 2018 19:23:17 +0000 Subject: [Starlingx-discuss] Build Broken In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA3F2B4A@ALA-MBD.corp.ad.wrs.com> References: <2588653EBDFFA34B982FAF00F1B4844EBB324F7F@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA3F2B4A@ALA-MBD.corp.ad.wrs.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB3253FF@ALA-MBD.corp.ad.wrs.com> Suggest we revert Brent From: Penney, Don Sent: Tuesday, November 27, 2018 2:22 PM To: Rowsell, Brent ; Mihai, Irina ; starlingx-discuss at lists.starlingx.io Subject: RE: Build Broken I did a repo sync and built just that package: $ build-pkgs --serial --no-descendants --no-required --no-build-info resource-agents And the build failed with the same error. Reverting the commit Brent indicated resolves the build issue. I don't know why the patch would be "malformed". Nothing jumps out at me. Should we just revert it via gerrit and let Zhipeng revisit it when he's online? From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Tuesday, November 27, 2018 1:08 PM To: Mihai, Irina; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Build Broken Not sure if this is the cause, but this was pushed this morning https://review.openstack.org/#/c/619398/ Brent From: Mihai, Irina [mailto:Irina.Mihai at windriver.com] Sent: Tuesday, November 27, 2018 1:02 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Build Broken Hi, I've just pulled the latest code from master and see the error below in stx-integ. It gets passed that if you checkout HEAD~ Thanks, Irina +++++++++++++++++++ 17:41:54 ============ Build failed ============= 17:41:54 b2: ===== Build SRPM for 'resource-agents' ===== 17:41:54 b2: PKG_BASE=/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents 17:41:54 b2: BUILD_DIR=resource-agents/rpmbuild 17:41:54 b2: SRPM_DIR=/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS 17:41:54 b2: Wrote: /localdisk/loadbuild/wrsroot/starlingx-0-clean/std/rpmbuild/SOURCES/resource-agents/srpm_input.md5 17:41:54 b2: Rebuild required due to new or changed file: stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/PATCH_ORDER 17:41:54 b2: Rebuild required due to missing directory: '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS' 17:41:54 b2: clean_srpm_dir build_idx=2 DIR=/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS 17:41:54 b2: find: '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS': No such file or directory 17:41:54 b2: resource-agents.spec 17:41:54 b2: resource-agents-3.9.5 17:41:54 b2: srpm_apply_meta_patches '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild' '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents' 0 'centos' 'resource-agents-3.9.5-124.el7' 17:41:54 b2: Applying metadata patches 17:41:54 b2: srpm_apply_patch '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch' '-p1' '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild' 0 'WRS: ' '0' '' '' '' '' 0 'resource-agents-3.9.5-124.el7' '' 17:41:54 b2: patch -p1 < /localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch 17:41:54 b2: patching file SPECS/resource-agents.spec 17:41:54 b2: patch: **** malformed patch at line 67: ./autogen.sh 17:41:54 b2: 17:41:54 b2: failed to apply patch '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch' 17:41:54 b2: ERROR: srpm_apply_meta_patches (1420): failed to apply patch 'spec-include-TiS-patches.patch' 17:41:54 b2: ERROR: build_dir_srpm (785): failed to extract srpm '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/cgcs-centos-repo/Source/resource-agents-3.9.5-124.el7.src.rpm' 17:41:54 ERROR: reaper (1303): Failed to build src.rpm from source at 'b2' -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Nov 27 19:50:13 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 27 Nov 2018 19:50:13 +0000 Subject: [Starlingx-discuss] Build Broken In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB3253FF@ALA-MBD.corp.ad.wrs.com> References: <2588653EBDFFA34B982FAF00F1B4844EBB324F7F@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA3F2B4A@ALA-MBD.corp.ad.wrs.com> <2588653EBDFFA34B982FAF00F1B4844EBB3253FF@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA3F2B98@ALA-MBD.corp.ad.wrs.com> It looks like maybe the patch was manually modified to try to add a blank line, without rebuilding, which causes line counts and numbers to be incorrect. The following change fixes the malformation: $ git diff diff --git a/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch b/base/cluster-resource-agents/centos/meta_pat index 19877b1..566c23c 100644 --- a/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch +++ b/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch @@ -61,7 +61,6 @@ index a16660a..ec85fc2 100644 +%patch1120 -p1 +%patch1121 -p1 +%patch1122 -p1 -+ %build if [ ! -f configure ]; then ./autogen.sh Is there a bug raised for it? I can just push this change to resolve the issue, rather than reverting From: Rowsell, Brent Sent: Tuesday, November 27, 2018 2:23 PM To: Penney, Don; Mihai, Irina; starlingx-discuss at lists.starlingx.io Subject: RE: Build Broken Suggest we revert Brent From: Penney, Don Sent: Tuesday, November 27, 2018 2:22 PM To: Rowsell, Brent ; Mihai, Irina ; starlingx-discuss at lists.starlingx.io Subject: RE: Build Broken I did a repo sync and built just that package: $ build-pkgs --serial --no-descendants --no-required --no-build-info resource-agents And the build failed with the same error. Reverting the commit Brent indicated resolves the build issue. I don't know why the patch would be "malformed". Nothing jumps out at me. Should we just revert it via gerrit and let Zhipeng revisit it when he's online? From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Tuesday, November 27, 2018 1:08 PM To: Mihai, Irina; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Build Broken Not sure if this is the cause, but this was pushed this morning https://review.openstack.org/#/c/619398/ Brent From: Mihai, Irina [mailto:Irina.Mihai at windriver.com] Sent: Tuesday, November 27, 2018 1:02 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Build Broken Hi, I've just pulled the latest code from master and see the error below in stx-integ. It gets passed that if you checkout HEAD~ Thanks, Irina +++++++++++++++++++ 17:41:54 ============ Build failed ============= 17:41:54 b2: ===== Build SRPM for 'resource-agents' ===== 17:41:54 b2: PKG_BASE=/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents 17:41:54 b2: BUILD_DIR=resource-agents/rpmbuild 17:41:54 b2: SRPM_DIR=/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS 17:41:54 b2: Wrote: /localdisk/loadbuild/wrsroot/starlingx-0-clean/std/rpmbuild/SOURCES/resource-agents/srpm_input.md5 17:41:54 b2: Rebuild required due to new or changed file: stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/PATCH_ORDER 17:41:54 b2: Rebuild required due to missing directory: '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS' 17:41:54 b2: clean_srpm_dir build_idx=2 DIR=/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS 17:41:54 b2: find: '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS': No such file or directory 17:41:54 b2: resource-agents.spec 17:41:54 b2: resource-agents-3.9.5 17:41:54 b2: srpm_apply_meta_patches '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild' '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents' 0 'centos' 'resource-agents-3.9.5-124.el7' 17:41:54 b2: Applying metadata patches 17:41:54 b2: srpm_apply_patch '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch' '-p1' '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild' 0 'WRS: ' '0' '' '' '' '' 0 'resource-agents-3.9.5-124.el7' '' 17:41:54 b2: patch -p1 < /localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch 17:41:54 b2: patching file SPECS/resource-agents.spec 17:41:54 b2: patch: **** malformed patch at line 67: ./autogen.sh 17:41:54 b2: 17:41:54 b2: failed to apply patch '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch' 17:41:54 b2: ERROR: srpm_apply_meta_patches (1420): failed to apply patch 'spec-include-TiS-patches.patch' 17:41:54 b2: ERROR: build_dir_srpm (785): failed to extract srpm '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/cgcs-centos-repo/Source/resource-agents-3.9.5-124.el7.src.rpm' 17:41:54 ERROR: reaper (1303): Failed to build src.rpm from source at 'b2' -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Nov 27 19:51:03 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 27 Nov 2018 19:51:03 +0000 Subject: [Starlingx-discuss] Build Broken References: <2588653EBDFFA34B982FAF00F1B4844EBB324F7F@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA3F2B4A@ALA-MBD.corp.ad.wrs.com> <2588653EBDFFA34B982FAF00F1B4844EBB3253FF@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA3F2BBB@ALA-MBD.corp.ad.wrs.com> Never mind. Looks like Scott just pushed a review to fix the line count From: Penney, Don Sent: Tuesday, November 27, 2018 2:50 PM To: Rowsell, Brent; Mihai, Irina; starlingx-discuss at lists.starlingx.io Subject: RE: Build Broken It looks like maybe the patch was manually modified to try to add a blank line, without rebuilding, which causes line counts and numbers to be incorrect. The following change fixes the malformation: $ git diff diff --git a/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch b/base/cluster-resource-agents/centos/meta_pat index 19877b1..566c23c 100644 --- a/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch +++ b/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch @@ -61,7 +61,6 @@ index a16660a..ec85fc2 100644 +%patch1120 -p1 +%patch1121 -p1 +%patch1122 -p1 -+ %build if [ ! -f configure ]; then ./autogen.sh Is there a bug raised for it? I can just push this change to resolve the issue, rather than reverting From: Rowsell, Brent Sent: Tuesday, November 27, 2018 2:23 PM To: Penney, Don; Mihai, Irina; starlingx-discuss at lists.starlingx.io Subject: RE: Build Broken Suggest we revert Brent From: Penney, Don Sent: Tuesday, November 27, 2018 2:22 PM To: Rowsell, Brent ; Mihai, Irina ; starlingx-discuss at lists.starlingx.io Subject: RE: Build Broken I did a repo sync and built just that package: $ build-pkgs --serial --no-descendants --no-required --no-build-info resource-agents And the build failed with the same error. Reverting the commit Brent indicated resolves the build issue. I don't know why the patch would be "malformed". Nothing jumps out at me. Should we just revert it via gerrit and let Zhipeng revisit it when he's online? From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Tuesday, November 27, 2018 1:08 PM To: Mihai, Irina; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Build Broken Not sure if this is the cause, but this was pushed this morning https://review.openstack.org/#/c/619398/ Brent From: Mihai, Irina [mailto:Irina.Mihai at windriver.com] Sent: Tuesday, November 27, 2018 1:02 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Build Broken Hi, I've just pulled the latest code from master and see the error below in stx-integ. It gets passed that if you checkout HEAD~ Thanks, Irina +++++++++++++++++++ 17:41:54 ============ Build failed ============= 17:41:54 b2: ===== Build SRPM for 'resource-agents' ===== 17:41:54 b2: PKG_BASE=/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents 17:41:54 b2: BUILD_DIR=resource-agents/rpmbuild 17:41:54 b2: SRPM_DIR=/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS 17:41:54 b2: Wrote: /localdisk/loadbuild/wrsroot/starlingx-0-clean/std/rpmbuild/SOURCES/resource-agents/srpm_input.md5 17:41:54 b2: Rebuild required due to new or changed file: stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/PATCH_ORDER 17:41:54 b2: Rebuild required due to missing directory: '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS' 17:41:54 b2: clean_srpm_dir build_idx=2 DIR=/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS 17:41:54 b2: find: '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS': No such file or directory 17:41:54 b2: resource-agents.spec 17:41:54 b2: resource-agents-3.9.5 17:41:54 b2: srpm_apply_meta_patches '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild' '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents' 0 'centos' 'resource-agents-3.9.5-124.el7' 17:41:54 b2: Applying metadata patches 17:41:54 b2: srpm_apply_patch '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch' '-p1' '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild' 0 'WRS: ' '0' '' '' '' '' 0 'resource-agents-3.9.5-124.el7' '' 17:41:54 b2: patch -p1 < /localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch 17:41:54 b2: patching file SPECS/resource-agents.spec 17:41:54 b2: patch: **** malformed patch at line 67: ./autogen.sh 17:41:54 b2: 17:41:54 b2: failed to apply patch '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch' 17:41:54 b2: ERROR: srpm_apply_meta_patches (1420): failed to apply patch 'spec-include-TiS-patches.patch' 17:41:54 b2: ERROR: build_dir_srpm (785): failed to extract srpm '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/cgcs-centos-repo/Source/resource-agents-3.9.5-124.el7.src.rpm' 17:41:54 ERROR: reaper (1303): Failed to build src.rpm from source at 'b2' -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Tue Nov 27 20:15:44 2018 From: scott.little at windriver.com (Scott Little) Date: Tue, 27 Nov 2018 15:15:44 -0500 Subject: [Starlingx-discuss] Build Broken In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA3F2BBB@ALA-MBD.corp.ad.wrs.com> References: <2588653EBDFFA34B982FAF00F1B4844EBB324F7F@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA3F2B4A@ALA-MBD.corp.ad.wrs.com> <2588653EBDFFA34B982FAF00F1B4844EBB3253FF@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA3F2BBB@ALA-MBD.corp.ad.wrs.com> Message-ID: My proposed fix for the line count error in the patch is here.... https://review.openstack.org/620394 Scott On 18-11-27 02:51 PM, Penney, Don wrote: > > Never mind. Looks like Scott just pushed a review to fix the line count > > *From:*Penney, Don > *Sent:* Tuesday, November 27, 2018 2:50 PM > *To:* Rowsell, Brent; Mihai, Irina; starlingx-discuss at lists.starlingx.io > *Subject:* RE: Build Broken > > It looks like maybe the patch was manually modified to try to add a > blank line, without rebuilding, which causes line counts and numbers > to be incorrect. The following change fixes the malformation: > > $ git diff > > diff --git > a/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch > b/base/cluster-resource-agents/centos/meta_pat > > index 19877b1..566c23c 100644 > > --- > a/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch > > +++ > b/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch > > @@ -61,7 +61,6 @@ index a16660a..ec85fc2 100644 > > +%patch1120 -p1 > > +%patch1121 -p1 > > +%patch1122 -p1 > > -+ > >   %build > >   if [ ! -f configure ]; then > >         ./autogen.sh > > Is there a bug raised for it? I can just push this change to resolve > the issue, rather than reverting > > *From:*Rowsell, Brent > *Sent:* Tuesday, November 27, 2018 2:23 PM > *To:* Penney, Don; Mihai, Irina; starlingx-discuss at lists.starlingx.io > *Subject:* RE: Build Broken > > Suggest we revert > > Brent > > *From:* Penney, Don > *Sent:* Tuesday, November 27, 2018 2:22 PM > *To:* Rowsell, Brent ; Mihai, Irina > ; starlingx-discuss at lists.starlingx.io > *Subject:* RE: Build Broken > > I did a repo sync and built just that package: > > $ build-pkgs --serial --no-descendants --no-required --no-build-info > resource-agents > > And the build failed with the same error. Reverting the commit Brent > indicated resolves the build issue. > > I don’t know why the patch would be “malformed”. Nothing jumps out at > me. Should we just revert it via gerrit and let Zhipeng revisit it > when he’s online? > > *From:*Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] > *Sent:* Tuesday, November 27, 2018 1:08 PM > *To:* Mihai, Irina; starlingx-discuss at lists.starlingx.io > > *Subject:* Re: [Starlingx-discuss] Build Broken > > Not sure if this is the cause, but this was pushed this morning > https://review.openstack.org/#/c/619398/ > > Brent > > *From:* Mihai, Irina [mailto:Irina.Mihai at windriver.com] > *Sent:* Tuesday, November 27, 2018 1:02 PM > *To:* starlingx-discuss at lists.starlingx.io > > *Subject:* [Starlingx-discuss] Build Broken > > Hi, > > I've just pulled the latest code from master and see the error below > in stx-integ. > > It gets passed that if you checkout HEAD~ > > Thanks, > > Irina > > +++++++++++++++++++ > > 17:41:54 ============ Build failed ============= > 17:41:54 b2: ===== Build SRPM for 'resource-agents' ===== > 17:41:54 b2: > PKG_BASE=/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents > 17:41:54 b2: BUILD_DIR=resource-agents/rpmbuild > 17:41:54 b2: > SRPM_DIR=/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS > 17:41:54 b2: Wrote: > /localdisk/loadbuild/wrsroot/starlingx-0-clean/std/rpmbuild/SOURCES/resource-agents/srpm_input.md5 > 17:41:54 b2: Rebuild required due to new or changed file: > stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/PATCH_ORDER > 17:41:54 b2: Rebuild required due to missing directory: > '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS' > 17:41:54 b2: clean_srpm_dir build_idx=2 > DIR=/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS > 17:41:54 b2: find: > ‘/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS’: > No such file or directory > 17:41:54 b2: resource-agents.spec > 17:41:54 b2:    resource-agents-3.9.5 > 17:41:54 b2: srpm_apply_meta_patches > '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild' > '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents' > 0 'centos' 'resource-agents-3.9.5-124.el7' > 17:41:54 b2: Applying metadata patches > 17:41:54 b2: srpm_apply_patch > '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch' > '-p1' > '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild' > 0 'WRS: ' '0' '' '' '' '' 0 'resource-agents-3.9.5-124.el7' '' > 17:41:54 b2: patch -p1 < > /localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch > 17:41:54 b2: patching file SPECS/resource-agents.spec > 17:41:54 b2: patch: **** malformed patch at line 67:     ./autogen.sh > 17:41:54 b2: > 17:41:54 b2: failed to apply patch > '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch' > 17:41:54 b2: ERROR: srpm_apply_meta_patches (1420): failed to apply > patch 'spec-include-TiS-patches.patch' > 17:41:54 b2: ERROR: build_dir_srpm (785): failed to extract srpm > '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/cgcs-centos-repo/Source/resource-agents-3.9.5-124.el7.src.rpm' > 17:41:54 ERROR: reaper (1303): Failed to build src.rpm from source at 'b2' > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Marvin.Huang at windriver.com Tue Nov 27 20:42:02 2018 From: Marvin.Huang at windriver.com (Huang, Marvin) Date: Tue, 27 Nov 2018 20:42:02 +0000 Subject: [Starlingx-discuss] which version is working for devstack support? Message-ID: <74D9C1EDDC44EF468303629CF9A2832C9CE073CB@ALA-MBD.corp.ad.wrs.com> Hi all, I hit issues when tried to bring up stx-conf with devstack using the local.conf at https://wiki.openstack.org/wiki/StarlingX/Devstack/stx-config. I was following the DevStack procedures but using the above configuration file. One problem is: ++functions-common:git_clone:568 cd /opt/stack/devstack ++/opt/stack/stx-config/devstack/lib/stx-config:install_stx_utils:123 pushd /opt/stack/stx-utils/middleware/util/recipes-common/platform-util/platform-util/ /opt/stack/stx-config/devstack/lib/stx-config: line 123: pushd: /opt/stack/stx-utils/middleware/util/recipes-common/platform-util/platform-util/: No such file or directory +/opt/stack/stx-config/devstack/lib/stx-config:install_stx_utils:1 exit_trap I also tried with latest STX_BRANCH by comment off the line in local.conf STX_BRANCH=refs/changes/43/586443/3 But the same problem was hit. Anybody has any idea what's the status of DevStack support for STX? Where can I find more information besides https://wiki.openstack.org/wiki/StarlingX/Devstack/? Thanks! Marvin -------------- next part -------------- An HTML attachment was scrubbed... URL: From Irina.Mihai at windriver.com Tue Nov 27 21:45:15 2018 From: Irina.Mihai at windriver.com (Mihai, Irina) Date: Tue, 27 Nov 2018 21:45:15 +0000 Subject: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming In-Reply-To: References: , Message-ID: Hey Liang, When we saw the IO error, we had created 20 boot from volume instances at once with the following flavor: 8gb rootfs, 8gb ephemeral and 512 meg swap, using a qcow2 Centos7 image (quite large, not sure what you've been using in your tests). Irina ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Tuesday, November 27, 2018 5:36 AM To: Mihai, Irina Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming Hi Irina Thanks for the info. Some status: - I can reproduce the issue that solved in _convert_image(). The issue I reproduced may be not the same one as the original issue this patch to fix. Reproduced by: uploading a volume to image, but with insufficient space in image_conversion_dir. - But I still cannot reproduce the issue solved in _create_from_image_cache_or_download() even with multiple volume creating requests. Take two requests as example, the second request will be rejected by image_utils.check_available_space() at the beginning of _create_from_image_cache_or_download(). If I add debug code - sleep(60) after the line of image_utils.check_available_space, so that both two requests can pass the check, but the second request will raise exception(ImageTooBig) and be caught in the line 777, 810: “image_utils.TemporaryImages.fetch”. And I take a look of other code following, don’t find any chance of raising “IOError”. o verify_glance_image_signature o volume_glance_metadata_bulk_create o qemu_img_info o check_virtual_size o _create_from_image_download: This will re-use image file. Even insufficient space happen, the exception be re-raised is exception.InsufficientConversionSpace, not “IOError”. If you can get the original reproduce steps, that would be great! Some info related: Change-Id: Ie5eba32f92eb1740554bfc44baf612e326d6fde5, submitted in this year, with 4 commits, shows dest will be a volume. So unlikely be the same as image_conversion_dir. Thanks, Liang From: Mihai, Irina [mailto:Irina.Mihai at windriver.com] Sent: Tuesday, November 27, 2018 1:25 AM To: Fang, Liang A Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming Hi Liang, This patch was covering the scenario when we're trying to create multiple volumes from image at the same time. In this situation, multiple downloads/convertions would be allowed to start since there would still be conversion space left, but eventually the operation would fail because of the disk being full. This is not caught by any of the "ImageTooBig" or "ImageUnacceptable" exceptions. Could you please help to address one doubt: why image is converted in the same location with image itself? This patch is to create a volume from image, right? Right, but I'm not aware of the reasoning behind this. However, if the used image is qcow2 then it needs to be converted to raw before being saved to the volume. Please let me know if I can help in any other way. Thanks, Irina ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Sunday, November 25, 2018 11:44 AM To: Mihai, Irina Cc: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming Hi Irina Code review: https://review.openstack.org/#/c/618976/ I’m working of upstreaming this patch. Could you please help to address one doubt: why image is converted in the same location with image itself? This patch is to create a volume from image, right? I take a look of related code, the destination location would be the newly created volume and the source location is configured in cinder.conf, something like: image_conversion_dir = /mnt/d100m/image_conversion_dir I did an experiment, in the latest master branch of cinder upstream repo: - If image_conversion_dir has no space to store the downloading image, the exception ImageTooBig will be caught in the beginning of _create_from_image_cache_or_download(). - If has space to store the image, but dest volume size is smaller than image’s virtual size, an exception “ImageUnacceptable” will raised by check_virtual_size. So it seems no chance to go to the situation this patch aimed to solve. Could you please help to give more background of this patch? Or if you think this patch is invalid now, please just tell me, I will mark this patch as abandoned. Thanks Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From ada.cabrales at intel.com Tue Nov 27 21:59:14 2018 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Tue, 27 Nov 2018 21:59:14 +0000 Subject: [Starlingx-discuss] Bi-Weekly StarlingX Test meeting - 9:00 PDT Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7C374750@fmsmsx104.amr.corp.intel.com> Bi-weekly meetings on Tuesdays at 9am PDT / 1600 UTC * Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes: https://etherpad.openstack.org/p/stx-test -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2076 bytes Desc: not available URL: From changcheng.liu at intel.com Wed Nov 28 01:18:01 2018 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Wed, 28 Nov 2018 01:18:01 +0000 Subject: [Starlingx-discuss] stx-ceph patch commit detail: Add .gitreview In-Reply-To: References: <0D7994A90DD70040A9F5E77C4D23C57D50EFAE57@SHSMSX104.ccr.corp.intel.com> <0D7994A90DD70040A9F5E77C4D23C57D50EFC3E1@SHSMSX104.ccr.corp.intel.com> Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50EFCA19@SHSMSX104.ccr.corp.intel.com> Thanks Dean. We'll abandon this patch. -----Original Message----- From: Troyer, Dean Sent: Wednesday, November 28, 2018 6:49 AM To: Liu, Changcheng Cc: Troyer, Dean ; 'starlingx-discuss at lists.starlingx.io' ; 'Poncea, Ovidiu' Subject: RE: stx-ceph patch commit detail: Add .gitreview On Tue, 27 Nov 2018, Liu, Changcheng wrote: >       Please help us understand your patch if you’re available. The .gitreview file is only used for repos in OpenStack's Gerrit. I initally added it under the plan that all repos would be there, we ended up with many not in Gerrit, the .gitreview file is not needed now. dt -- Dean Troyer dean.troyer at intel.com From liang.a.fang at intel.com Wed Nov 28 01:24:30 2018 From: liang.a.fang at intel.com (Fang, Liang A) Date: Wed, 28 Nov 2018 01:24:30 +0000 Subject: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming In-Reply-To: References: , Message-ID: Hi Irina The image I'm using is small (~20MB), but added debug code (sleep) to help simulate and analyze. Free disk space for image_conversion_dir is about 30MB. Do you remember which line of code raising the IOError exception in this case? Thanks Liang From: Mihai, Irina [mailto:Irina.Mihai at windriver.com] Sent: Wednesday, November 28, 2018 5:45 AM To: Fang, Liang A Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming Hey Liang, When we saw the IO error, we had created 20 boot from volume instances at once with the following flavor: 8gb rootfs, 8gb ephemeral and 512 meg swap, using a qcow2 Centos7 image (quite large, not sure what you've been using in your tests). Irina ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Tuesday, November 27, 2018 5:36 AM To: Mihai, Irina Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming Hi Irina Thanks for the info. Some status: - I can reproduce the issue that solved in _convert_image(). The issue I reproduced may be not the same one as the original issue this patch to fix. Reproduced by: uploading a volume to image, but with insufficient space in image_conversion_dir. - But I still cannot reproduce the issue solved in _create_from_image_cache_or_download() even with multiple volume creating requests. Take two requests as example, the second request will be rejected by image_utils.check_available_space() at the beginning of _create_from_image_cache_or_download(). If I add debug code - sleep(60) after the line of image_utils.check_available_space, so that both two requests can pass the check, but the second request will raise exception(ImageTooBig) and be caught in the line 777, 810: "image_utils.TemporaryImages.fetch". And I take a look of other code following, don't find any chance of raising "IOError". o verify_glance_image_signature o volume_glance_metadata_bulk_create o qemu_img_info o check_virtual_size o _create_from_image_download: This will re-use image file. Even insufficient space happen, the exception be re-raised is exception.InsufficientConversionSpace, not "IOError". If you can get the original reproduce steps, that would be great! Some info related: Change-Id: Ie5eba32f92eb1740554bfc44baf612e326d6fde5, submitted in this year, with 4 commits, shows dest will be a volume. So unlikely be the same as image_conversion_dir. Thanks, Liang From: Mihai, Irina [mailto:Irina.Mihai at windriver.com] Sent: Tuesday, November 27, 2018 1:25 AM To: Fang, Liang A > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming Hi Liang, This patch was covering the scenario when we're trying to create multiple volumes from image at the same time. In this situation, multiple downloads/convertions would be allowed to start since there would still be conversion space left, but eventually the operation would fail because of the disk being full. This is not caught by any of the "ImageTooBig" or "ImageUnacceptable" exceptions. Could you please help to address one doubt: why image is converted in the same location with image itself? This patch is to create a volume from image, right? Right, but I'm not aware of the reasoning behind this. However, if the used image is qcow2 then it needs to be converted to raw before being saved to the volume. Please let me know if I can help in any other way. Thanks, Irina ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Sunday, November 25, 2018 11:44 AM To: Mihai, Irina Cc: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming Hi Irina Code review: https://review.openstack.org/#/c/618976/ I'm working of upstreaming this patch. Could you please help to address one doubt: why image is converted in the same location with image itself? This patch is to create a volume from image, right? I take a look of related code, the destination location would be the newly created volume and the source location is configured in cinder.conf, something like: image_conversion_dir = /mnt/d100m/image_conversion_dir I did an experiment, in the latest master branch of cinder upstream repo: - If image_conversion_dir has no space to store the downloading image, the exception ImageTooBig will be caught in the beginning of _create_from_image_cache_or_download(). - If has space to store the image, but dest volume size is smaller than image's virtual size, an exception "ImageUnacceptable" will raised by check_virtual_size. So it seems no chance to go to the situation this patch aimed to solve. Could you please help to give more background of this patch? Or if you think this patch is invalid now, please just tell me, I will mark this patch as abandoned. Thanks Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Wed Nov 28 01:57:07 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Wed, 28 Nov 2018 01:57:07 +0000 Subject: [Starlingx-discuss] Build Broken In-Reply-To: References: <2588653EBDFFA34B982FAF00F1B4844EBB324F7F@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA3F2B4A@ALA-MBD.corp.ad.wrs.com> <2588653EBDFFA34B982FAF00F1B4844EBB3253FF@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA3F2BBB@ALA-MBD.corp.ad.wrs.com> Message-ID: <93814834B4855241994F290E959305C752FFA9F9@SHSMSX104.ccr.corp.intel.com> Really sorry for that! When I did patch rebase and fixed merge conflict issue, one blank line was introduced which Cause build error. I really need to take more careful for patch version update every time. Thanks for the team to fix the error introduced by me immediately! Zhipeng From: Scott Little [mailto:scott.little at windriver.com] Sent: 2018年11月28日 4:16 To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Build Broken My proposed fix for the line count error in the patch is here.... https://review.openstack.org/620394 Scott On 18-11-27 02:51 PM, Penney, Don wrote: Never mind. Looks like Scott just pushed a review to fix the line count From: Penney, Don Sent: Tuesday, November 27, 2018 2:50 PM To: Rowsell, Brent; Mihai, Irina; starlingx-discuss at lists.starlingx.io Subject: RE: Build Broken It looks like maybe the patch was manually modified to try to add a blank line, without rebuilding, which causes line counts and numbers to be incorrect. The following change fixes the malformation: $ git diff diff --git a/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch b/base/cluster-resource-agents/centos/meta_pat index 19877b1..566c23c 100644 --- a/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch +++ b/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch @@ -61,7 +61,6 @@ index a16660a..ec85fc2 100644 +%patch1120 -p1 +%patch1121 -p1 +%patch1122 -p1 -+ %build if [ ! -f configure ]; then ./autogen.sh Is there a bug raised for it? I can just push this change to resolve the issue, rather than reverting From: Rowsell, Brent Sent: Tuesday, November 27, 2018 2:23 PM To: Penney, Don; Mihai, Irina; starlingx-discuss at lists.starlingx.io Subject: RE: Build Broken Suggest we revert Brent From: Penney, Don Sent: Tuesday, November 27, 2018 2:22 PM To: Rowsell, Brent ; Mihai, Irina ; starlingx-discuss at lists.starlingx.io Subject: RE: Build Broken I did a repo sync and built just that package: $ build-pkgs --serial --no-descendants --no-required --no-build-info resource-agents And the build failed with the same error. Reverting the commit Brent indicated resolves the build issue. I don’t know why the patch would be “malformed”. Nothing jumps out at me. Should we just revert it via gerrit and let Zhipeng revisit it when he’s online? From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Tuesday, November 27, 2018 1:08 PM To: Mihai, Irina; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Build Broken Not sure if this is the cause, but this was pushed this morning https://review.openstack.org/#/c/619398/ Brent From: Mihai, Irina [mailto:Irina.Mihai at windriver.com] Sent: Tuesday, November 27, 2018 1:02 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Build Broken Hi, I've just pulled the latest code from master and see the error below in stx-integ. It gets passed that if you checkout HEAD~ Thanks, Irina +++++++++++++++++++ 17:41:54 ============ Build failed ============= 17:41:54 b2: ===== Build SRPM for 'resource-agents' ===== 17:41:54 b2: PKG_BASE=/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents 17:41:54 b2: BUILD_DIR=resource-agents/rpmbuild 17:41:54 b2: SRPM_DIR=/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS 17:41:54 b2: Wrote: /localdisk/loadbuild/wrsroot/starlingx-0-clean/std/rpmbuild/SOURCES/resource-agents/srpm_input.md5 17:41:54 b2: Rebuild required due to new or changed file: stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/PATCH_ORDER 17:41:54 b2: Rebuild required due to missing directory: '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS' 17:41:54 b2: clean_srpm_dir build_idx=2 DIR=/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS 17:41:54 b2: find: ‘/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild/SRPMS’: No such file or directory 17:41:54 b2: resource-agents.spec 17:41:54 b2: resource-agents-3.9.5 17:41:54 b2: srpm_apply_meta_patches '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild' '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents' 0 'centos' 'resource-agents-3.9.5-124.el7' 17:41:54 b2: Applying metadata patches 17:41:54 b2: srpm_apply_patch '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch' '-p1' '/localdisk/loadbuild/wrsroot/starlingx-0-clean/std/srpm_assemble/resource-agents/rpmbuild' 0 'WRS: ' '0' '' '' '' '' 0 'resource-agents-3.9.5-124.el7' '' 17:41:54 b2: patch -p1 < /localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch 17:41:54 b2: patching file SPECS/resource-agents.spec 17:41:54 b2: patch: **** malformed patch at line 67: ./autogen.sh 17:41:54 b2: 17:41:54 b2: failed to apply patch '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/stx/stx-integ/base/cluster-resource-agents/centos/meta_patches/spec-include-TiS-patches.patch' 17:41:54 b2: ERROR: srpm_apply_meta_patches (1420): failed to apply patch 'spec-include-TiS-patches.patch' 17:41:54 b2: ERROR: build_dir_srpm (785): failed to extract srpm '/localdisk/designer/wrsroot/starlingx-0-clean/cgcs-root/cgcs-centos-repo/Source/resource-agents-3.9.5-124.el7.src.rpm' 17:41:54 ERROR: reaper (1303): Failed to build src.rpm from source at 'b2' _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Irina.Mihai at windriver.com Wed Nov 28 02:29:21 2018 From: Irina.Mihai at windriver.com (Mihai, Irina) Date: Wed, 28 Nov 2018 02:29:21 +0000 Subject: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming In-Reply-To: References: , , Message-ID: Hi Liang, Please find bellow the testcase initially used for this issue, together with the seen Cinder error. Irina +++++++++++++++++++++++ Testcase 1. Create an image with 8gb rootfs, using a qcow2 Centos7 image (I've used the following image: image: /home/wrsroot/CentOS-7-x86_64-GenericCloud.qcow2 file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 857M cluster_size: 65536 Format specific information: compat: 0.10 refcount bits: 16 ). 2. Occupy the conversions partition until you remain with 5-6GB free (I used the CentOS-7-x86_64-GenericCloud.qcow2 to fill the space) 3. Launch 4 VMs using the centos7 image and choose the "Create New Volume" option Error ERROR cinder.volume.flows.manager.create_volume [req-d3ec7b32-2599-4a14-93bc-f8051e74c52f d57645567e284958b293ffe92c391024 75602a3f79b343cb891da84d1519aaef - - -] Failed to copy image 7c662b9b-fa75-4cb1-ae8f-b38a95094fb1 to volume: 1468a764-81cb-45b2-af4a-66d006cd9401, error: qemu-img: error while writing sector 587904: No space left on device ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Tuesday, November 27, 2018 8:24 PM To: Mihai, Irina Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming Hi Irina The image I’m using is small (~20MB), but added debug code (sleep) to help simulate and analyze. Free disk space for image_conversion_dir is about 30MB. Do you remember which line of code raising the IOError exception in this case? Thanks Liang From: Mihai, Irina [mailto:Irina.Mihai at windriver.com] Sent: Wednesday, November 28, 2018 5:45 AM To: Fang, Liang A Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming Hey Liang, When we saw the IO error, we had created 20 boot from volume instances at once with the following flavor: 8gb rootfs, 8gb ephemeral and 512 meg swap, using a qcow2 Centos7 image (quite large, not sure what you've been using in your tests). Irina ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Tuesday, November 27, 2018 5:36 AM To: Mihai, Irina Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming Hi Irina Thanks for the info. Some status: - I can reproduce the issue that solved in _convert_image(). The issue I reproduced may be not the same one as the original issue this patch to fix. Reproduced by: uploading a volume to image, but with insufficient space in image_conversion_dir. - But I still cannot reproduce the issue solved in _create_from_image_cache_or_download() even with multiple volume creating requests. Take two requests as example, the second request will be rejected by image_utils.check_available_space() at the beginning of _create_from_image_cache_or_download(). If I add debug code - sleep(60) after the line of image_utils.check_available_space, so that both two requests can pass the check, but the second request will raise exception(ImageTooBig) and be caught in the line 777, 810: “image_utils.TemporaryImages.fetch”. And I take a look of other code following, don’t find any chance of raising “IOError”. o verify_glance_image_signature o volume_glance_metadata_bulk_create o qemu_img_info o check_virtual_size o _create_from_image_download: This will re-use image file. Even insufficient space happen, the exception be re-raised is exception.InsufficientConversionSpace, not “IOError”. If you can get the original reproduce steps, that would be great! Some info related: Change-Id: Ie5eba32f92eb1740554bfc44baf612e326d6fde5, submitted in this year, with 4 commits, shows dest will be a volume. So unlikely be the same as image_conversion_dir. Thanks, Liang From: Mihai, Irina [mailto:Irina.Mihai at windriver.com] Sent: Tuesday, November 27, 2018 1:25 AM To: Fang, Liang A > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming Hi Liang, This patch was covering the scenario when we're trying to create multiple volumes from image at the same time. In this situation, multiple downloads/convertions would be allowed to start since there would still be conversion space left, but eventually the operation would fail because of the disk being full. This is not caught by any of the "ImageTooBig" or "ImageUnacceptable" exceptions. Could you please help to address one doubt: why image is converted in the same location with image itself? This patch is to create a volume from image, right? Right, but I'm not aware of the reasoning behind this. However, if the used image is qcow2 then it needs to be converted to raw before being saved to the volume. Please let me know if I can help in any other way. Thanks, Irina ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Sunday, November 25, 2018 11:44 AM To: Mihai, Irina Cc: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming Hi Irina Code review: https://review.openstack.org/#/c/618976/ I’m working of upstreaming this patch. Could you please help to address one doubt: why image is converted in the same location with image itself? This patch is to create a volume from image, right? I take a look of related code, the destination location would be the newly created volume and the source location is configured in cinder.conf, something like: image_conversion_dir = /mnt/d100m/image_conversion_dir I did an experiment, in the latest master branch of cinder upstream repo: - If image_conversion_dir has no space to store the downloading image, the exception ImageTooBig will be caught in the beginning of _create_from_image_cache_or_download(). - If has space to store the image, but dest volume size is smaller than image’s virtual size, an exception “ImageUnacceptable” will raised by check_virtual_size. So it seems no chance to go to the situation this patch aimed to solve. Could you please help to give more background of this patch? Or if you think this patch is invalid now, please just tell me, I will mark this patch as abandoned. Thanks Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From mingyuan.qi at intel.com Wed Nov 28 02:42:42 2018 From: mingyuan.qi at intel.com (Mingyuan Qi) Date: Wed, 28 Nov 2018 10:42:42 +0800 Subject: [Starlingx-discuss] which version is working for devstack support? In-Reply-To: <74D9C1EDDC44EF468303629CF9A2832C9CE073CB@ALA-MBD.corp.ad.wrs.com> References: <74D9C1EDDC44EF468303629CF9A2832C9CE073CB@ALA-MBD.corp.ad.wrs.com> Message-ID: <1543372962.17860.28.camel@intel.com> Marvin, I can work with refs/changes/65/595865/27 about 2 weeks ago where install_stx_utils was removed, but now the updated patch https://review .openstack.org/#/c/618956/ was also merged to master branch. You can try with that code.  On Tue, 2018-11-27 at 20:42 +0000, Huang, Marvin wrote: > Hi all, >   > I hit issues when tried to bring up stx-conf with devstack using the > local.conf at https://wiki.openstack.org/wiki/StarlingX/Devstack/stx- > config. >   > I was following the DevStack procedures but using the above > configuration file. > One problem is: >     ++functions-common:git_clone:568            cd > /opt/stack/devstack >     ++/opt/stack/stx-config/devstack/lib/stx- > config:install_stx_utils:123  pushd /opt/stack/stx- > utils/middleware/util/recipes-common/platform-util/platform-util/ >     /opt/stack/stx-config/devstack/lib/stx-config: line 123: pushd: > /opt/stack/stx-utils/middleware/util/recipes-common/platform- > util/platform-util/: No such file or directory > +/opt/stack/stx-config/devstack/lib/stx-config:install_stx_utils:1  > exit_trap >   >   > I also tried with latest STX_BRANCH by comment off the line in > local.conf > STX_BRANCH=refs/changes/43/586443/3 >   > But the same problem was hit. >   > Anybody has any idea what’s the status of DevStack support for STX? > Where can I find more information besides https://wiki.openstack.org/ > wiki/StarlingX/Devstack/? >   > Thanks! > Marvin > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From austin.sun at intel.com Wed Nov 28 03:11:27 2018 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 28 Nov 2018 03:11:27 +0000 Subject: [Starlingx-discuss] which version is working for devstack support? In-Reply-To: <74D9C1EDDC44EF468303629CF9A2832C9CE073CB@ALA-MBD.corp.ad.wrs.com> References: <74D9C1EDDC44EF468303629CF9A2832C9CE073CB@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Marvin: I have updated my localrc [1] and updated the summary for devstack in sysinv module [2] In short , sysinv-api, sysinv-cond and sysinv-agent services can be running successfully in devstack env. [1] https://wiki.openstack.org/wiki/StarlingX/Devstack/stx-config/localrc [2] https://wiki.openstack.org/wiki/StarlingX/Devstack/stx-config Thanks. BR Austin Sun. From: Huang, Marvin [mailto:Marvin.Huang at windriver.com] Sent: Wednesday, November 28, 2018 4:42 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] which version is working for devstack support? Hi all, I hit issues when tried to bring up stx-conf with devstack using the local.conf at https://wiki.openstack.org/wiki/StarlingX/Devstack/stx-config. I was following the DevStack procedures but using the above configuration file. One problem is: ++functions-common:git_clone:568 cd /opt/stack/devstack ++/opt/stack/stx-config/devstack/lib/stx-config:install_stx_utils:123 pushd /opt/stack/stx-utils/middleware/util/recipes-common/platform-util/platform-util/ /opt/stack/stx-config/devstack/lib/stx-config: line 123: pushd: /opt/stack/stx-utils/middleware/util/recipes-common/platform-util/platform-util/: No such file or directory +/opt/stack/stx-config/devstack/lib/stx-config:install_stx_utils:1 exit_trap I also tried with latest STX_BRANCH by comment off the line in local.conf STX_BRANCH=refs/changes/43/586443/3 But the same problem was hit. Anybody has any idea what's the status of DevStack support for STX? Where can I find more information besides https://wiki.openstack.org/wiki/StarlingX/Devstack/? Thanks! Marvin -------------- next part -------------- An HTML attachment was scrubbed... URL: From liang.a.fang at intel.com Wed Nov 28 05:22:33 2018 From: liang.a.fang at intel.com (Fang, Liang A) Date: Wed, 28 Nov 2018 05:22:33 +0000 Subject: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming In-Reply-To: References: , , Message-ID: Hi Irina Thank you that you gave the initial test case and the error log. I think I have found the error point now. The error message is raised in _copy_image_to_volume, meanwhile the cinder backend must be rbd. Rbd driver did one more action: convert the image to a temp file, and then import the temp file to volume inside rbd. Thank you for the support! Thanks Liang From: Mihai, Irina [mailto:Irina.Mihai at windriver.com] Sent: Wednesday, November 28, 2018 10:29 AM To: Fang, Liang A Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming Hi Liang, Please find bellow the testcase initially used for this issue, together with the seen Cinder error. Irina +++++++++++++++++++++++ Testcase 1. Create an image with 8gb rootfs, using a qcow2 Centos7 image (I've used the following image: image: /home/wrsroot/CentOS-7-x86_64-GenericCloud.qcow2 file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 857M cluster_size: 65536 Format specific information: compat: 0.10 refcount bits: 16 ). 2. Occupy the conversions partition until you remain with 5-6GB free (I used the CentOS-7-x86_64-GenericCloud.qcow2 to fill the space) 3. Launch 4 VMs using the centos7 image and choose the "Create New Volume" option Error ERROR cinder.volume.flows.manager.create_volume [req-d3ec7b32-2599-4a14-93bc-f8051e74c52f d57645567e284958b293ffe92c391024 75602a3f79b343cb891da84d1519aaef - - -] Failed to copy image 7c662b9b-fa75-4cb1-ae8f-b38a95094fb1 to volume: 1468a764-81cb-45b2-af4a-66d006cd9401, error: qemu-img: error while writing sector 587904: No space left on device ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Tuesday, November 27, 2018 8:24 PM To: Mihai, Irina Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming Hi Irina The image I'm using is small (~20MB), but added debug code (sleep) to help simulate and analyze. Free disk space for image_conversion_dir is about 30MB. Do you remember which line of code raising the IOError exception in this case? Thanks Liang From: Mihai, Irina [mailto:Irina.Mihai at windriver.com] Sent: Wednesday, November 28, 2018 5:45 AM To: Fang, Liang A > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming Hey Liang, When we saw the IO error, we had created 20 boot from volume instances at once with the following flavor: 8gb rootfs, 8gb ephemeral and 512 meg swap, using a qcow2 Centos7 image (quite large, not sure what you've been using in your tests). Irina ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Tuesday, November 27, 2018 5:36 AM To: Mihai, Irina Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming Hi Irina Thanks for the info. Some status: - I can reproduce the issue that solved in _convert_image(). The issue I reproduced may be not the same one as the original issue this patch to fix. Reproduced by: uploading a volume to image, but with insufficient space in image_conversion_dir. - But I still cannot reproduce the issue solved in _create_from_image_cache_or_download() even with multiple volume creating requests. Take two requests as example, the second request will be rejected by image_utils.check_available_space() at the beginning of _create_from_image_cache_or_download(). If I add debug code - sleep(60) after the line of image_utils.check_available_space, so that both two requests can pass the check, but the second request will raise exception(ImageTooBig) and be caught in the line 777, 810: "image_utils.TemporaryImages.fetch". And I take a look of other code following, don't find any chance of raising "IOError". o verify_glance_image_signature o volume_glance_metadata_bulk_create o qemu_img_info o check_virtual_size o _create_from_image_download: This will re-use image file. Even insufficient space happen, the exception be re-raised is exception.InsufficientConversionSpace, not "IOError". If you can get the original reproduce steps, that would be great! Some info related: Change-Id: Ie5eba32f92eb1740554bfc44baf612e326d6fde5, submitted in this year, with 4 commits, shows dest will be a volume. So unlikely be the same as image_conversion_dir. Thanks, Liang From: Mihai, Irina [mailto:Irina.Mihai at windriver.com] Sent: Tuesday, November 27, 2018 1:25 AM To: Fang, Liang A > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming Hi Liang, This patch was covering the scenario when we're trying to create multiple volumes from image at the same time. In this situation, multiple downloads/convertions would be allowed to start since there would still be conversion space left, but eventually the operation would fail because of the disk being full. This is not caught by any of the "ImageTooBig" or "ImageUnacceptable" exceptions. Could you please help to address one doubt: why image is converted in the same location with image itself? This patch is to create a volume from image, right? Right, but I'm not aware of the reasoning behind this. However, if the used image is qcow2 then it needs to be converted to raw before being saved to the volume. Please let me know if I can help in any other way. Thanks, Irina ________________________________ From: Fang, Liang A [liang.a.fang at intel.com] Sent: Sunday, November 25, 2018 11:44 AM To: Mihai, Irina Cc: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] [cinder] Analysis of patch c45bb0e for StartlingX upstreaming Hi Irina Code review: https://review.openstack.org/#/c/618976/ I'm working of upstreaming this patch. Could you please help to address one doubt: why image is converted in the same location with image itself? This patch is to create a volume from image, right? I take a look of related code, the destination location would be the newly created volume and the source location is configured in cinder.conf, something like: image_conversion_dir = /mnt/d100m/image_conversion_dir I did an experiment, in the latest master branch of cinder upstream repo: - If image_conversion_dir has no space to store the downloading image, the exception ImageTooBig will be caught in the beginning of _create_from_image_cache_or_download(). - If has space to store the image, but dest volume size is smaller than image's virtual size, an exception "ImageUnacceptable" will raised by check_virtual_size. So it seems no chance to go to the situation this patch aimed to solve. Could you please help to give more background of this patch? Or if you think this patch is invalid now, please just tell me, I will mark this patch as abandoned. Thanks Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From dean.troyer at intel.com Tue Nov 27 22:48:31 2018 From: dean.troyer at intel.com (Dean Troyer) Date: Tue, 27 Nov 2018 16:48:31 -0600 (CST) Subject: [Starlingx-discuss] stx-ceph patch commit detail: Add .gitreview In-Reply-To: <0D7994A90DD70040A9F5E77C4D23C57D50EFC3E1@SHSMSX104.ccr.corp.intel.com> References: <0D7994A90DD70040A9F5E77C4D23C57D50EFAE57@SHSMSX104.ccr.corp.intel.com> <0D7994A90DD70040A9F5E77C4D23C57D50EFC3E1@SHSMSX104.ccr.corp.intel.com> Message-ID: On Tue, 27 Nov 2018, Liu, Changcheng wrote: >       Please help us understand your patch if you’re available. The .gitreview file is only used for repos in OpenStack's Gerrit. I initally added it under the plan that all repos would be there, we ended up with many not in Gerrit, the .gitreview file is not needed now. dt -- Dean Troyer dean.troyer at intel.com From cindy.xie at intel.com Wed Nov 28 00:22:57 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 28 Nov 2018 00:22:57 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack Distro meeting, 11/28 In-Reply-To: <413BC967A3F41F49851BDEF27A77637C558DAD53@ORSMSX113.amr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F35DD196C@SHSMSX104.ccr.corp.intel.com> <413BC967A3F41F49851BDEF27A77637C558DAD53@ORSMSX113.amr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35DD2789@SHSMSX104.ccr.corp.intel.com> Agenda update: kernel upgrade topic dropped, added Qemu 3.0 upgrade status update. Thx. - cindy -----Original Message----- From: Wold, Saul Sent: Wednesday, November 28, 2018 12:27 AM To: Xie, Cindy ; Rowsell, Brent ; Rodriguez Bahena, Victor ; Cabrales, Ada ; Perez, Ricardo O ; Lin, Shuicheng ; Liu, ZhipengS ; Sun, Austin ; Zhu, Vivian ; Shang, Dehao ; Cardona Ruiz, Erick ; Qi, Mingyuan ; Wang, Yi C ; Troyer, Dean ; starlingx-discuss at lists.starlingx.io Subject: RE: Agenda: Weekly StarlingX non-OpenStack Distro meeting, 11/28 Please add Qemu Update (Ghada) to the adgenda. I am not sure we are ready to talk about 4.19 kernel upgrade, that's more a Clear, Multi-OS (for Ubuntu) discussion currently. Sau! ________________________________________ From: Xie, Cindy Sent: Tuesday, November 27, 2018 1:47 AM To: Rowsell, Brent; Wold, Saul; Rodriguez Bahena, Victor; Cabrales, Ada; Perez, Ricardo O; Lin, Shuicheng; Liu, ZhipengS; Sun, Austin; Zhu, Vivian; Shang, Dehao; Cardona Ruiz, Erick; Qi, Mingyuan; Wang, Yi C; Troyer, Dean; starlingx-discuss at lists.starlingx.io Subject: Agenda: Weekly StarlingX non-OpenStack Distro meeting, 11/28 Agenda for 11/28 meeting: 1. Kernel upgrade to 4.19 (LTS) feasibility discussion (Saul/Victor) 2. kernel driver upgrade testing status update (Ada/Ricardo/Shuicheng) 3. non-Openstack patch refactoring status (Zhipeng) 4. non-Openstack source patch upstream study (Saul) 5. Python2to3 non-Openstack status (Austin) 6. Ceph upgrade status (Vivian/Dehao) 7. DevStack flocks plug-in status (Erick/Mingyuan/Yi/Dean) 8. Opens (all) -----Original Appointment----- From: Xie, Cindy Sent: Monday, November 5, 2018 2:27 PM To: Xie, Cindy; Wold, Saul; 'Rowsell, Brent'; Jones, Bruce E; Troyer, Dean; 'Khalil, Ghada'; Waheed, Numan; Lin, Shuicheng; Zhu, Vivian; Shang, Dehao; Liu, ZhipengS; Hu, Yong; Sun, Austin; Somerville, Jim; starlingx-discuss at lists.starlingx.io Cc: Perez Carranza, Jose; 'Hellmann, Gil'; 'Waines, Greg'; 'Chen, Jacky'; Armstrong, Robert H; Perez Rodriguez, Humberto I; Martinez Landa, Hayde; Martinez Monroy, Elio; Hu, Wei W; 'Seiler, Glenn'; 'Eslimi, Dariush'; Gomez, Juan P; Lara, Cesar; Young, Ken; Arce Moreno, Abraham Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, November 28, 2018 6:00 AM-7:00 AM (UTC-08:00) Pacific Time (US & Canada). Where: https://zoom.us/j/342730236 * Cadence and time slot: o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) * Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ * Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other From austin.sun at intel.com Wed Nov 28 06:45:06 2018 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 28 Nov 2018 06:45:06 +0000 Subject: [Starlingx-discuss] Support IBRS cpu model. References: <08e3677f-39dc-bc99-2791-c88468e17c4a@windriver.com> Message-ID: Hi Chris and All: More info for Qemu to support IBRS. Qemu 2.10 is used in StarlingX. From [1] and [2], Qemu 2.12.1 will start supporting spec-ctrl/IBRS chip support. [1] https://www.qemu.org/2018/02/14/qemu-2-11-1-and-spectre-update/ [2] https://wiki.qemu.org/ChangeLog/2.12 Thanks. BR Austin Sun. -----Original Message----- From: Sun, Austin Sent: Tuesday, November 27, 2018 5:18 PM To: 'Chris Friesen' ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Support IBRS cpu model. Hi Chris: Thanks your suggestion. I have done some more test . Here is the result. Compute CPU: Skylake-IBRS, If we created VM with non-IBRS CPU model(Skylake-server, Broadwell etc), it worked fine with patch. But when create VM with IBRS CPU model, Qemu will report below error "2018-11-27T08:42:23.764924Z qemu-kvm: can't apply global Broadwell-x86_64-cpu.spec-ctrl=on: Property '.spec-ctrl' not found" Or "qemu-kvm: can't apply global Skylake-Server-x86_64-cpu.spec-ctrl=on: Property '.spec-ctrl' not found" From link[1]: it seems we have to upgrade qemu to check if we can fully support *IBRS cpu model. Currently we can only create non-IBRS CPU model or passthrough with those two patches [2] and [3] [1] https://bugzilla.redhat.com/show_bug.cgi?id=1532401 [2] https://github.com/starlingx-staging/stx-nova/pull/17 [3] https://github.com/starlingx-staging/stx-glance/pull/5 Thanks. BR Austin Sun. -----Original Message----- From: Chris Friesen [mailto:chris.friesen at windriver.com] Sent: Friday, November 23, 2018 11:08 PM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Support IBRS cpu model. In order to ensure that we don't break existing code, I think we'd also need to test by booting VMs built using at least a flavor that specifies a different IBRS CPU model and a different non-IBRS CPU model. Chris On 11/23/2018 12:16 AM, Sun, Austin wrote: > Hi Chris: > Due to resource limitation , I only deployed in Skylake-IBIS server , create VM enabling cpu-passthrough. > > Thanks. > BR > Austin Sun. > -----Original Message----- > From: Chris Friesen [mailto:chris.friesen at windriver.com] > Sent: Friday, November 23, 2018 1:42 AM > To: Sun, Austin ; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Support IBRS cpu model. > > On 11/21/2018 11:46 PM, Sun, Austin wrote: >> Hi Chris: >> Very appreciate your review >> The new PRs are >> https://github.com/starlingx-staging/stx-nova/pull/17 >> https://github.com/starlingx-staging/stx-glance/pull/5 > > What testing have you done on these changes? > > Chris > From jagdish.patil at atosicloud.com Wed Nov 28 10:53:59 2018 From: jagdish.patil at atosicloud.com (Jagdish Patil) Date: Wed, 28 Nov 2018 16:23:59 +0530 (IST) Subject: [Starlingx-discuss] Starlingx stable ISO Any update on Message-ID: <1591718060.202.1543402439128.JavaMail.zimbra@atosicloud.com> Hi , Any update when starling ISO will be available for community? Cheers Jagdish -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Wed Nov 28 11:37:30 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Wed, 28 Nov 2018 11:37:30 +0000 Subject: [Starlingx-discuss] Support IBRS cpu model. In-Reply-To: References: <08e3677f-39dc-bc99-2791-c88468e17c4a@windriver.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB327507@ALA-MBD.corp.ad.wrs.com> Just a fyi. QEMU is in the process of being up versioned to 3.0 Brent -----Original Message----- From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Wednesday, November 28, 2018 1:45 AM To: Friesen, Chris ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Support IBRS cpu model. Hi Chris and All: More info for Qemu to support IBRS. Qemu 2.10 is used in StarlingX. From [1] and [2], Qemu 2.12.1 will start supporting spec-ctrl/IBRS chip support. [1] https://www.qemu.org/2018/02/14/qemu-2-11-1-and-spectre-update/ [2] https://wiki.qemu.org/ChangeLog/2.12 Thanks. BR Austin Sun. -----Original Message----- From: Sun, Austin Sent: Tuesday, November 27, 2018 5:18 PM To: 'Chris Friesen' ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Support IBRS cpu model. Hi Chris: Thanks your suggestion. I have done some more test . Here is the result. Compute CPU: Skylake-IBRS, If we created VM with non-IBRS CPU model(Skylake-server, Broadwell etc), it worked fine with patch. But when create VM with IBRS CPU model, Qemu will report below error "2018-11-27T08:42:23.764924Z qemu-kvm: can't apply global Broadwell-x86_64-cpu.spec-ctrl=on: Property '.spec-ctrl' not found" Or "qemu-kvm: can't apply global Skylake-Server-x86_64-cpu.spec-ctrl=on: Property '.spec-ctrl' not found" From link[1]: it seems we have to upgrade qemu to check if we can fully support *IBRS cpu model. Currently we can only create non-IBRS CPU model or passthrough with those two patches [2] and [3] [1] https://bugzilla.redhat.com/show_bug.cgi?id=1532401 [2] https://github.com/starlingx-staging/stx-nova/pull/17 [3] https://github.com/starlingx-staging/stx-glance/pull/5 Thanks. BR Austin Sun. -----Original Message----- From: Chris Friesen [mailto:chris.friesen at windriver.com] Sent: Friday, November 23, 2018 11:08 PM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Support IBRS cpu model. In order to ensure that we don't break existing code, I think we'd also need to test by booting VMs built using at least a flavor that specifies a different IBRS CPU model and a different non-IBRS CPU model. Chris On 11/23/2018 12:16 AM, Sun, Austin wrote: > Hi Chris: > Due to resource limitation , I only deployed in Skylake-IBIS server , create VM enabling cpu-passthrough. > > Thanks. > BR > Austin Sun. > -----Original Message----- > From: Chris Friesen [mailto:chris.friesen at windriver.com] > Sent: Friday, November 23, 2018 1:42 AM > To: Sun, Austin ; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Support IBRS cpu model. > > On 11/21/2018 11:46 PM, Sun, Austin wrote: >> Hi Chris: >> Very appreciate your review >> The new PRs are >> https://github.com/starlingx-staging/stx-nova/pull/17 >> https://github.com/starlingx-staging/stx-glance/pull/5 > > What testing have you done on these changes? > > Chris > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Brent.Rowsell at windriver.com Wed Nov 28 12:15:02 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Wed, 28 Nov 2018 12:15:02 +0000 Subject: [Starlingx-discuss] Starlingx stable ISO Any update on In-Reply-To: <1591718060.202.1543402439128.JavaMail.zimbra@atosicloud.com> References: <1591718060.202.1543402439128.JavaMail.zimbra@atosicloud.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB32761B@ALA-MBD.corp.ad.wrs.com> Hi, Pre-built iso is now available, http://lists.starlingx.io/pipermail/starlingx-discuss/2018-November/001856.html Brent From: Jagdish Patil [mailto:jagdish.patil at atosicloud.com] Sent: Wednesday, November 28, 2018 5:54 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Starlingx stable ISO Any update on Hi , Any update when starling ISO will be available for community? Cheers Jagdish -------------- next part -------------- An HTML attachment was scrubbed... URL: From SkyDiablo at gmx.net Wed Nov 28 12:55:50 2018 From: SkyDiablo at gmx.net (SkyDiablo) Date: Wed, 28 Nov 2018 13:55:50 +0100 Subject: [Starlingx-discuss] no DHCP response for instance Message-ID: An HTML attachment was scrubbed... URL: From Marvin.Huang at windriver.com Wed Nov 28 14:43:30 2018 From: Marvin.Huang at windriver.com (Huang, Marvin) Date: Wed, 28 Nov 2018 14:43:30 +0000 Subject: [Starlingx-discuss] which version is working for devstack support? In-Reply-To: <1543372962.17860.28.camel@intel.com> References: <74D9C1EDDC44EF468303629CF9A2832C9CE073CB@ALA-MBD.corp.ad.wrs.com> <1543372962.17860.28.camel@intel.com> Message-ID: <74D9C1EDDC44EF468303629CF9A2832C9CE07588@ALA-MBD.corp.ad.wrs.com> Thanks Mingyuan! I'll try with the updated repos/files. Regards, Marvin >> -----Original Message----- >> From: Mingyuan Qi [mailto:mingyuan.qi at intel.com] >> Sent: Tuesday, November 27, 2018 9:43 PM >> To: Huang, Marvin; starlingx-discuss at lists.starlingx.io >> Subject: Re: [Starlingx-discuss] which version is working for devstack >> support? >> >> Marvin, >> >> I can work with refs/changes/65/595865/27 about 2 weeks ago where >> install_stx_utils was removed, but now the updated patch https://review >> .openstack.org/#/c/618956/ was also merged to master branch. You can >> try with that code. >> >> On Tue, 2018-11-27 at 20:42 +0000, Huang, Marvin wrote: >> > Hi all, >> > >> > I hit issues when tried to bring up stx-conf with devstack using the >> > local.conf at https://wiki.openstack.org/wiki/StarlingX/Devstack/stx- >> > config. >> > >> > I was following the DevStack procedures but using the above >> > configuration file. >> > One problem is: >> >     ++functions-common:git_clone:568            cd >> > /opt/stack/devstack >> >     ++/opt/stack/stx-config/devstack/lib/stx- >> > config:install_stx_utils:123  pushd /opt/stack/stx- >> > utils/middleware/util/recipes-common/platform-util/platform-util/ >> >     /opt/stack/stx-config/devstack/lib/stx-config: line 123: pushd: >> > /opt/stack/stx-utils/middleware/util/recipes-common/platform- >> > util/platform-util/: No such file or directory >> > +/opt/stack/stx-config/devstack/lib/stx-config:install_stx_utils:1 >> > exit_trap >> > >> > >> > I also tried with latest STX_BRANCH by comment off the line in >> > local.conf >> > STX_BRANCH=refs/changes/43/586443/3 >> > >> > But the same problem was hit. >> > >> > Anybody has any idea what’s the status of DevStack support for STX? >> > Where can I find more information besides https://wiki.openstack.org/ >> > wiki/StarlingX/Devstack/? >> > >> > Thanks! >> > Marvin >> > _______________________________________________ >> > Starlingx-discuss mailing list >> > Starlingx-discuss at lists.starlingx.io >> > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Marvin.Huang at windriver.com Wed Nov 28 14:43:53 2018 From: Marvin.Huang at windriver.com (Huang, Marvin) Date: Wed, 28 Nov 2018 14:43:53 +0000 Subject: [Starlingx-discuss] which version is working for devstack support? In-Reply-To: References: <74D9C1EDDC44EF468303629CF9A2832C9CE073CB@ALA-MBD.corp.ad.wrs.com> Message-ID: <74D9C1EDDC44EF468303629CF9A2832C9CE0758F@ALA-MBD.corp.ad.wrs.com> Thanks Austin! I'll try it with the updated files. Regards, Marvin From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, November 27, 2018 10:11 PM To: Huang, Marvin; starlingx-discuss at lists.starlingx.io Subject: RE: which version is working for devstack support? Hi Marvin: I have updated my localrc [1] and updated the summary for devstack in sysinv module [2] In short , sysinv-api, sysinv-cond and sysinv-agent services can be running successfully in devstack env. [1] https://wiki.openstack.org/wiki/StarlingX/Devstack/stx-config/localrc [2] https://wiki.openstack.org/wiki/StarlingX/Devstack/stx-config Thanks. BR Austin Sun. From: Huang, Marvin [mailto:Marvin.Huang at windriver.com] Sent: Wednesday, November 28, 2018 4:42 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] which version is working for devstack support? Hi all, I hit issues when tried to bring up stx-conf with devstack using the local.conf at https://wiki.openstack.org/wiki/StarlingX/Devstack/stx-config. I was following the DevStack procedures but using the above configuration file. One problem is: ++functions-common:git_clone:568 cd /opt/stack/devstack ++/opt/stack/stx-config/devstack/lib/stx-config:install_stx_utils:123 pushd /opt/stack/stx-utils/middleware/util/recipes-common/platform-util/platform-util/ /opt/stack/stx-config/devstack/lib/stx-config: line 123: pushd: /opt/stack/stx-utils/middleware/util/recipes-common/platform-util/platform-util/: No such file or directory +/opt/stack/stx-config/devstack/lib/stx-config:install_stx_utils:1 exit_trap I also tried with latest STX_BRANCH by comment off the line in local.conf STX_BRANCH=refs/changes/43/586443/3 But the same problem was hit. Anybody has any idea what's the status of DevStack support for STX? Where can I find more information besides https://wiki.openstack.org/wiki/StarlingX/Devstack/? Thanks! Marvin -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Wed Nov 28 14:53:19 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 28 Nov 2018 14:53:19 +0000 Subject: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack Distro meeting, 11/28 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35DDCEDF@SHSMSX104.ccr.corp.intel.com> Agenda & Notes for 11/28 meeting: 1. Kernel upgrade to 4.19 (LTS) feasibility discussion (Saul/Victor) - will skip for today 2. kernel driver upgrade testing status update (Ada/Ricardo/Shuicheng) Ricardo / Ada: We have recived the ISO image from Shuicheng, we have already installed the borrowe QAT enabled platforms, the installation was successful, and the config controller, however, when we tried to start creating the providernet, an error is shown by the API (HTTP error 500, using CLI commands) using such QAT enabled systems (silver config). The issue seems to be related to such systems, we have installed latest ISO from Shuicheng in our Wolf Pass servers, both ISO files provided successfully, being able to perform the config controller and provisioning. However we don't have QAT hardware in such Wolf Pass systems. To mitigate this, we get borrowed a PCIe card from another team in GDC, such card is a: Lewis Hill, QAT 8970 Adapter, X16,OEM,S,DUAL-CC - J39967-001, we are going to install such card on our Wolf Pass server and see if it works with the latest ISO provided. If no success, we are going to skip (by now, and until we get the proper QAT ready hardware, such validation), and continue with DRDB. 3. non-Openstack patch refactoring status (Zhipeng) 27 tasks for init/config refactoring, 24 tasks finished w/ patches merged. 3 under review. 117 meta-patches and 32 src patch got removed through the activity. total patches are 156 removed from the upstream srpm packages. 13 srpm packages can be replaced by rpm packages instead. 4. non-Openstack source patch upstream study (Saul) nothing new - still working on study and making stories for each of them. 5. Python2to3 non-Openstack status (Austin) Austin :5.1 which python3 should be target, AR: Austin to check w/ Dean about how Openstack community handle Python3 version. current StarlingX status for the 3rd party OS packages: 1) 313 packages are compatible for python 2 and 3 2) 28 packages are need upgrade or need replacement package. 3) 35 packages are low risk since some small python code included -----> we might add more patch. high level guiance is that we do not want to add more patches on those upstream packages. Need to have solution as well. 4) 21 packages are high risk or cannot find any info to support python3 ------> we need find proper solution to solve this . Next step: bring those 21 packages into the mailing list Some other topic need to consider and discuss : 1) which python3 will be target ? 3.5 or 3.6 , from Openstack community , it seems Openstack does not fully support python 3.6 yet. 2) we have to some more task to work , in some component , the "C" or other language will call python2 head files. We did not consider such situation before. For example stx-fault/fm-common/sources/fm_python_mod_main.cpp, #include . 6. Qemu 3.0 upgrade (Ghada/Jim) addressed all tecnical issues related to qemu 3.0 upgrade. all regression tests success. will work on submission the patches. Needs to push the branch to staging first. IBRS issue depends on qemu upgrade: Austin can work w/ the qemu 3.0 branch to validate the bug can be resolved w/ qemu 3.0. new feature documented in qemu release notes. 7. Ceph upgrade status (Vivian/Dehao) Dehao: 6 patches about ceph upgrade and under review now. 4 patches to starlingx - scott is reviewing them. other 2 patches under staging (stx-ceph), Dean is reviewing them. Needs to break down into small patches. Changcheng: for the 42 ceph patch rebase: 14/42 can be abandon; 28 patches will be split to 38 patches. Needs to do validation against Ceph 13.2 environment. https://bugs.launchpad.net/starlingx/+bug/1804412, bug cannot be reproduced and can be closed. (during mirror download, missing packages are downloaded manually). mem limitation: needs to have workaround for low mem system. No patch has been submitted to the build scripts. 1st item has been covered in build project; and Yong can bring the WR to Erich for 2nd issues (low mem system). Changcheng's patch is depends on Ceph spec patches that Dehao is working on. PR pending on stx-ceph on staging. 8. DevStack flocks plug-in status (Erick/Mingyuan/Yi/Dean) stx-metal devstack plug-in patches pending for review. Service can be started w/ the patch; stx-nfv plug-in, Erick already patch merged for stx-nfv services installation. Yi is working on start those services. patch is WIP to config the services correctly. stx-ha is pending review, check w/ Erick. 9. Opens (all) -----Original Appointment----- From: Xie, Cindy Sent: Monday, November 5, 2018 2:27 PM To: Xie, Cindy; Wold, Saul; 'Rowsell, Brent'; Jones, Bruce E; Troyer, Dean; 'Khalil, Ghada'; Waheed, Numan; Lin, Shuicheng; Zhu, Vivian; Shang, Dehao; Liu, ZhipengS; Hu, Yong; Sun, Austin; Somerville, Jim; starlingx-discuss at lists.starlingx.io Cc: Perez Carranza, Jose; 'Hellmann, Gil'; 'Waines, Greg'; 'Chen, Jacky'; Armstrong, Robert H; Perez Rodriguez, Humberto I; Martinez Landa, Hayde; Martinez Monroy, Elio; Hu, Wei W; 'Seiler, Glenn'; 'Eslimi, Dariush'; Gomez, Juan P; Lara, Cesar; Young, Ken; Arce Moreno, Abraham; Cobbley, David A Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, November 28, 2018 6:00 AM-7:00 AM (UTC-08:00) Pacific Time (US & Canada). Where: https://zoom.us/j/342730236 . Cadence and time slot: o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) . Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ . Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other From chenjie.xu at intel.com Wed Nov 28 15:10:54 2018 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Wed, 28 Nov 2018 15:10:54 +0000 Subject: [Starlingx-discuss] Analysis of patch 88b7bc7 for StartlingX upstreaming Message-ID: Hi Matt, I think that there exists a bug in patch 88b7bc7. Function _get_fdb_entries will call function _create_agent_fdb by following line: https://github.com/starlingx-staging/stx-neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/mech_driver.py#L441 The variable "host" will be used to call _create_agent_fdb. However function _create_agent_fdb expects variable "agent": https://github.com/starlingx-staging/stx-neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/mech_driver.py#L264 I think this should be a bug. Could you please help review and comment? Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From changcheng.liu at intel.com Wed Nov 28 16:04:58 2018 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Wed, 28 Nov 2018 16:04:58 +0000 Subject: [Starlingx-discuss] stx document mismatch: Virtual Environment/Dedicated Storage Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50F082A7@SHSMSX104.ccr.corp.intel.com> Hi Abraham, Could you help check the integrity of below document? https://docs.starlingx.io/installation_guide/dedicated_storage.html#dedicated-storage "setup_dedicated_storage.sh" script doesn't exist at all in stx-tools ( https://github.com/openstack/stx-tools/tree/master/deployment/libvirt ). There're lots of values need to be configured instead of just accepting the default values when installing stx-2018-11-01-8-master.iso as controller node. Could you add more information about "Accept all the default values immediately after 'system date and time'" in the above document? B.R. Changcheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Peters at windriver.com Wed Nov 28 17:43:07 2018 From: Matt.Peters at windriver.com (Peters, Matt) Date: Wed, 28 Nov 2018 17:43:07 +0000 Subject: [Starlingx-discuss] Analysis of patch 88b7bc7 for StartlingX upstreaming In-Reply-To: References: Message-ID: <2D8849FB-AB0B-4385-9DAC-9BF4BEF41960@windriver.com> Hello Chenjie, I agree, this is a bug. I think the only reason it hasn’t been an issue is because the only user of the get_fdb_entries RPC is the BGP agent and it is not passing a host in the request (it is None), therefore it excludes the attempt to try and access the parameter as an agent based on the condition in _create_agent_fdb. Here is the BGP caller: https://github.com/starlingx-staging/stx-neutron-dynamic-routing/blob/master/neutron_dynamic_routing/services/bgp/agent/bgp_dragent.py#L1498 From: "Xu, Chenjie" Date: Wednesday, November 28, 2018 at 10:11 AM To: "Peters, Matt" Cc: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Analysis of patch 88b7bc7 for StartlingX upstreaming Hi Matt, I think that there exists a bug in patch 88b7bc7. Function _get_fdb_entries will call function _create­_agent_fdb by following line: https://github.com/starlingx-staging/stx-neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/mech_driver.py#L441 The variable “host” will be used to call _create_agent_fdb. However function _create_agent_fdb expects variable “agent”: https://github.com/starlingx-staging/stx-neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/mech_driver.py#L264 I think this should be a bug. Could you please help review and comment? Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Wed Nov 28 18:25:29 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 28 Nov 2018 18:25:29 +0000 Subject: [Starlingx-discuss] Phoenix mini-PTG agenda open Message-ID: <9A85D2917C58154C960D95352B22818BB1EBBB30@fmsmsx117.amr.corp.intel.com> I've created a new etherpad for the agenda [0] for the mini-PTG meeting in January. Please feel free to add items to be discussed. There is a link to the etherpad on the main wiki page in the PTG Meeting section. Brucej [0] https://etherpad.openstack.org/p/Chandler_mini_PTG_agenda -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Wed Nov 28 17:54:09 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 28 Nov 2018 17:54:09 +0000 Subject: [Starlingx-discuss] Notes from the Nov 28th 2018 community meeting Message-ID: <9A85D2917C58154C960D95352B22818BB1EBBA58@fmsmsx117.amr.corp.intel.com> Agenda and Notes - Nov 28th call * We are looking into holding an in person community meeting in January to discuss planning for these changes. Hostsed by Intel in Phoenix (Chandler). Target date is January 15-16. Intel side we plan to send Bruce, David, Cindy, Cesar, Ada, Dean, Saul, Victor. Would like to see TSC & key folks from WR attend. All are welcome. Can we close on the dates and attendees? o Dates are confirmed. Please start your travel arrangements. o Bruce to get with Ildiko on eventbrite support. * Patch resolution strategy update - Brent? o To be discussed at this week's TSC call and then shared here next week. * Sub-project status / help needed / issues? o Build - there are a couple things in flight right now. ? We have a request to enable Go in the build. Will require network access during that part of the build. Needed for K8S. There are some tensions between how OpenStack works and how Go works. Devil in the details. Go handles dependencies by checking out master during builds, we need to figure out if we want to copy the dependent packages into our build (vendoring) or rely on upstream master. We need a strategy for how to handle builds and for how (if) to handle vendoring and rebasing vendored dependencies. ? We are working on a new download tool and have a new faster version. Working on a transition plan, adding support for Cengn mirror. Spec is posted. ? Cengn mirror is on a daily cadence - new ISO's coming out every day. Spec not yet closed. * Ada - should we start running daily sanity on the Cengn ISO's? Yes! Ken - can we create a dashboard with the status of the sanity tests and links to any LP's filed? Ken - let's collaborate on that. * Ian - how often / when do we clean up the Cengn servers? Do we have a retention policy? Ken - initial thoughts is to keep build artifacts for 7 days and ISOs for 14 days. Let's document the policy and automate the cleanup. * Dean will do a monthly branch/MS release this week to keep the gears running. * Test - Continue to work on test automation, dealing with some internal issues. Discussing how to move some testing into the open. We are evaluating our initial performance testing results with Wind River and working on how to change our testing. We are measuring VM recovery time, swact time, etc.. ? Ian - we do not have an stx-test repo yet. Ada - our code is in internal git hub right now. We are discussing about how to migrate the code to open source. Ada to review a proposal to the TSC next week. * Dist Cloud - Greg - we have a couple of specs out for review - stx spec out on synchronized keystone functionality (from the Edge WG). We have also submitted a glance spec out for review with the glance community for Stein. * Docs - We have a direction for how to version the stx-docs repo / documents. Waiting on OSF to grant access to the web content. AR Bruce to ping Ildiko. Big changes coming to the API documentation, to start with stx-ha - we are reviewing each API against the docs, not expecting big changes but it's a lot of work. Working to update the build/install docs to take advantage of the Cengn repo and to document the new download tool. * Distro - We discussed the kernel driver update patches - 6 pending testing. Team does not have QIT enabled hardware to test those changes. Machines on order. MIght not be available until next year. Testing for the rest of the drivers can proceed. Team is working on the init/config patches - we have completed 24/27 tasks in the SB entry. 3 changes out for review. This will eliminate 150+ patches. We can replace 13 SRPM packages with binary RPMs. Working on planning for next steps. ? Working on python2->3 upgrade in the distro code. Should be finished by EOY. Working on 3rd party OS packages - looking at 400 packages - 313 of them are believed to be safe, 28 packages need to be upgraded from 2 to 3. Remaining 56 do not have P3 support or need further work. We should look into which applications are using these packages and then discuss next steps. ? What Python3 version should we use - 3.5, .6, .7? Guidance is to follow OpenStack community practice - 3.5 is a safe bet but RHEL 8 beta has 3.6 in it and will likely be the "official" Stein version. ? QEMU upgrade - we need a branch on the staging trees to enable the code to be checked in. * Security - All of our medium and higher security issues have been resolved, thank you all! We have two open Low priority issues, once a CVE that has not been fixed upstream yet. We have a few other hardening issues to address. We are working on our policy and process documents, community review would be welcome. We've posted a banned C function document for review, please take a look at the Security page on the wiki. * Containers - We have been focused on the building blocks. We have most in place and can bring up a single server with openstack services in containers. We want to enable the community and will start by uploading docker images. Next steps is to focus on the larger configurations. Setting up Monday team meetings 1600 UTC 8AM PST. * Releases - Mostly still resting. :) We need to update and/or confirm our release plans. Want to see the big deliverables / items and how they map over time. To be discussed at the TSC meeting. * Networking - Focus continues on upstreaming against a prioritized list. Top of the list is the network segment spec which is central to the patch elimination strategy for the broader system. To be discussed at the next meeting with Miguel. * MultiOS - * DevStack - We have DevStack running with two services integrated with very minimal functionality. Dean's goal is to enable development of the Flock services using DevStack. We are working on installing the services now. Long term testing of APIs can be provided. * Zuul - -------------- next part -------------- An HTML attachment was scrubbed... URL: From abraham.arce.moreno at intel.com Wed Nov 28 20:24:03 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Wed, 28 Nov 2018 20:24:03 +0000 Subject: [Starlingx-discuss] API requests: stx-metal Message-ID: stx-metal team, As a result of time spent within stx-metal, we have some initial questions with respect to documentation and source code so we are kindly requesting your comments for questions "?" under each section [ Section ] [Sub Section] Please assume: - The require X-Auth-Token is in place to authenticate, only URLs might be shown. - StarlingX is configured as Standard Controller: 2 Controllers, 2 Computes. [ Project Information ] When we look at the name and description reported out by curl -i http://10.10.10.2:6385/ there is a mismatch between documentation [0] and information via API Query: API Documentation: Name: StarlingX SysInv API Description: StarlingX System API allows for the management of physical servers. This includes inventory collection and configuration of hosts, ports, interfaces, CPUs, disk, memory, and system configuration. The API also supports the configuration of the cloud's SNMP interface. Source Code via API Query: Name: Titanium SysInv API Description: Titanium Cloud System API allows for the management of physical servers. This includes inventory collection and configuration of hosts, ports, interfaces, CPUs, disk, memory, and system configuration. The API also supports alarms and fault collection for the cloud itself as well as the configuration of the cloud's SNMP interface. ? Can you please let us know where the modifications are required? API Documentation or Source Code? [ v1/ ] Here we are showing 3 different views of what we are seeing within stx-metal project: - Our initial "Migration WADL to RST", see history here [1] - What we have documented in our "Current Official API Documentation" pages [0] - What the "API Query Output" is actually showing with curl -i http://10.10.10.2:6385/v1/... [ v1/ ] [ Migration WADL to RST ] Migration analysis from WADL to RST format gave us the endpoints below to include, we are adding in the second column what it seems to be the match for the valid API endpoint name: Hosts > ihosts Ports > ports CPUs > icpu Memory > imemorys Disks > idisks SensorGroup > isensorgroups Sensor > isensors LLDP Agents > lldp_agents LLDP Neighbors > lldp_neighbours ? Are all the names and API nodes correctly matched? ? Are all the valid API node names correct? E.g. imemorys Vs imemories [ v1/ ] [ Current Official API Documentation ] Current Official API documentation [0] includes the following 5 endpoints under "API Versions" v1/ details: - LLDP Neighbors: http://10.10.10.2:6385/v1/lldp_neighbours/ - Hosts: http://10.10.10.2:6385/v1/ihosts/ - CPUs: http://10.10.10.2:6385/v1/icpu/ - LLDP Agents: http://10.10.10.2:6385/v1/lldp_agents/ - Ports: http://10.10.10.2:6385/v1/iports/ ? All of them are valid endpoints except for: - icpu is not found, the correct working endpoint is: http://10.10.10.2:6385/v1/icpus/ - iports is not found, the correct working endpoint is: http://10.10.10.2:6385/v1/ports/ Any objection to make the documentation change? The following 3 endpoints are not shown under "API Versions" v1/ details but they have a valid top level v1/ endpoint: - Memory Documentation pointing to: /v1/ihosts/{host_id}/imemorys and a valid top level v1/ endpoint: http://10.10.10.2:6385/v1/imemorys/ - SensorGroup Documentation pointing to: /v1/ihosts/{host_id}/isensorgroups and a valid top level v1/ endpoint: http://10.10.10.2:6385/v1/isensorgroups/ - Sensor Documentation pointing to: /v1/ihosts/{host_id}/isensors and a valid top level v1/ endpoint: http://10.10.10.2:6385/v1/isensors/ ? Since they a valid top level v1/ endpoint, do we need to add them under our "API Versions" v1/ details documentation [2]? idisks does not have a valid v1/ endpoint, it is accessed only through v1/ihosts: - Disks > http://10.10.10.2:6385/v1/ihosts/{host_id}/idisks/ ? It seems ok, anything to add here? anything to modify? [ v1/ ] [ API Query Output ] API queries output shows these endpoints: - lldp_neighbours - ihosts - icpu - lldp_agents Plus additional ones, some other are assigned to other StarlingX repos: - firewallrules - addresses - links - remotelogging - ceph_mon - itrapdest - iextoam - intp - storage_file - storage_lvm - interface_networks - inode - id - ptp - media_types - servicegroup - upgrade - imemory - networks - storage_ceph_external - health - clusters - drbdconfig - icommunity - helm_charts - iprofile - servicenodes - iinfra - storage_backend - controller_fs - services - sdn_controller - addrpools - license - service_parameter - storage_ceph - idns - isystems - storage_external - iuser Important! Focusing on endpoints related to stx-metal, let's take a look at this v1/ API Query Output and choose "imemory": "imemory": [ { "href": "http://10.10.10.2:6385/v1/imemory/", "rel": "self" }, { "href": "http://10.10.10.2:6385/imemory/", "rel": "bookmark" } ], When we query "imemory" endpoint based in the information presented above, we find this endpoint as not valid, knowing from previous procedures the endpoint name "imemorys" is the valid one. ? Do we need another level of review? ? Should we target an update to the documentation in terms of number of services we are documenting comparing the 3 perspectives? [ v1/ihosts ] Some fields might be different. API Documentation does not include the field "tboot" but our API query shows this "tboot" field under each host: "tboot": "false", ? Is this different since it could have been queried in a AIO Vs a our Controller Storage? In general: ? Is there any need to go deeper into reviewing the content fo the rest of the endpoints outputs? We understand this might be a job for the API testing @ Zuul so let us know how can we help from the documentation perspective. ? Anything else to add? mention? required? Thanks for your initial support. [0] https://docs.starlingx.io/api-ref/stx-metal/ [1] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide/API_Documentation#Analysis [2] https://docs.starlingx.io/api-ref/stx-metal/api-ref-sysinv-v1-metal.html?expanded=shows-details-for-bare-metal-api-v1-detail#api-versions [3] https://docs.starlingx.io/api-ref/stx-metal/api-ref-sysinv-v1-metal.html?expanded=shows-details-for-bare-metal-api-v1-detail#memory From Numan.Waheed at windriver.com Wed Nov 28 22:07:38 2018 From: Numan.Waheed at windriver.com (Waheed, Numan) Date: Wed, 28 Nov 2018 22:07:38 +0000 Subject: [Starlingx-discuss] STX Test Strategy Message-ID: <3CAA827B7A79BA46B15B280EC82088FE4823680D@ALA-MBD.corp.ad.wrs.com> Hi Ada, I was wondering that we don't have an STX Test Strategy that has been discussed with community. It is possible that you might have some test strategy and I also have a test strategy but these have not been discussed and known to the community. As STX community is growing, there is need to define a test strategy and make it public so that community can follow it. Can we please discuss it in our next Test meeting. Thanks, Numan. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cesar.lara at intel.com Thu Nov 29 01:48:16 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Thu, 29 Nov 2018 01:48:16 +0000 Subject: [Starlingx-discuss] [build] [meetings] Build team meeting agenda for 11/29/2018 Message-ID: <0B566C62EC792145B40E29EFEBF1AB4710571D58@fmsmsx104.amr.corp.intel.com> Build team meeting 11/29/2018 Agenda - Cengn Artifact and ISO files generation cadence - Cengn tooling required - Golang implementations - Opens Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From chenjie.xu at intel.com Thu Nov 29 02:21:15 2018 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Thu, 29 Nov 2018 02:21:15 +0000 Subject: [Starlingx-discuss] Analysis of patch 88b7bc7 for StartlingX upstreaming In-Reply-To: <2D8849FB-AB0B-4385-9DAC-9BF4BEF41960@windriver.com> References: <2D8849FB-AB0B-4385-9DAC-9BF4BEF41960@windriver.com> Message-ID: Hi Matt, Thanks for your comments! An RFE has been written to upstream patch 88b7bc7. Before I submit the code, I think we should fix this bug. I think we can change the parameter “host” to “agent” in the following lines: https://github.com/starlingx-staging/stx-neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/rpc_manager/l2population_rpc.py#L44 https://github.com/starlingx-staging/stx-neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/rpc_manager/l2population_rpc.py#L57 https://github.com/starlingx-staging/stx-neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/mech_driver.py#L444 https://github.com/starlingx-staging/stx-neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/mech_driver.py#L434 Please let me know what you think of the proposal. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Thursday, November 29, 2018 1:43 AM To: Xu, Chenjie Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Analysis of patch 88b7bc7 for StartlingX upstreaming Hello Chenjie, I agree, this is a bug. I think the only reason it hasn’t been an issue is because the only user of the get_fdb_entries RPC is the BGP agent and it is not passing a host in the request (it is None), therefore it excludes the attempt to try and access the parameter as an agent based on the condition in _create_agent_fdb. Here is the BGP caller: https://github.com/starlingx-staging/stx-neutron-dynamic-routing/blob/master/neutron_dynamic_routing/services/bgp/agent/bgp_dragent.py#L1498 From: "Xu, Chenjie" > Date: Wednesday, November 28, 2018 at 10:11 AM To: "Peters, Matt" > Cc: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] Analysis of patch 88b7bc7 for StartlingX upstreaming Hi Matt, I think that there exists a bug in patch 88b7bc7. Function _get_fdb_entries will call function _create­_agent_fdb by following line: https://github.com/starlingx-staging/stx-neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/mech_driver.py#L441 The variable “host” will be used to call _create_agent_fdb. However function _create_agent_fdb expects variable “agent”: https://github.com/starlingx-staging/stx-neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/mech_driver.py#L264 I think this should be a bug. Could you please help review and comment? Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From xuyun at jxresearch.com Thu Nov 29 07:29:07 2018 From: xuyun at jxresearch.com (=?gb2312?B?0OzUzA==?=) Date: Thu, 29 Nov 2018 15:29:07 +0800 Subject: [Starlingx-discuss] Unable to mount squashfs.img Message-ID: <840F9C42-9C1E-4E5F-A7D3-65BF54C4B715@jxresearch.com> Hi, I’m trying to build a StarlingX ISO. I got an error at step 'update-pxe-network-installer’: -rw-r--r-- 1 root root 55629360 Nov 29 07:11 /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/output/new-initrd.img -rwxr-xr-x 1 root root 6588016 Nov 29 07:09 /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/output/new-vmlinuz ---------------- start to make new squashfs.img ------------- /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/orig/squashfs.img /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/squashfs.mnt mount: wrong fs type, bad option, bad superblock on /dev/loop2, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. Any suggestion how to fix it? Thank you. br, Xu Yun From yong.hu at intel.com Thu Nov 29 07:41:04 2018 From: yong.hu at intel.com (Hu, Yong) Date: Thu, 29 Nov 2018 07:41:04 +0000 Subject: [Starlingx-discuss] Unable to mount squashfs.img In-Reply-To: <840F9C42-9C1E-4E5F-A7D3-65BF54C4B715@jxresearch.com> References: <840F9C42-9C1E-4E5F-A7D3-65BF54C4B715@jxresearch.com> Message-ID: Can you confirm the following file exists in your mirror? /import/mirrors/CentOS/stx-r1-centos75/CentOS/pike/Binary/LiveOS/squashfs.img If the file does exit, very likely it was *corrupted* because it seemed the failure came from: mount -o loop -t squashfs $ORIG_SQUASHFS $work_dir/squashfs.mnt in script: "~/cgcs-root/build-tools/make-installer-images.sh" You can manually mount "squashfs.img" to confirm it is not corrupted. On 29/11/2018, 3:30 PM, "徐蕴" wrote: Hi, I’m trying to build a StarlingX ISO. I got an error at step 'update-pxe-network-installer’: -rw-r--r-- 1 root root 55629360 Nov 29 07:11 /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/output/new-initrd.img -rwxr-xr-x 1 root root 6588016 Nov 29 07:09 /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/output/new-vmlinuz ---------------- start to make new squashfs.img ------------- /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/orig/squashfs.img /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/squashfs.mnt mount: wrong fs type, bad option, bad superblock on /dev/loop2, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. Any suggestion how to fix it? Thank you. br, Xu Yun _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From xuyun at jxresearch.com Thu Nov 29 07:44:11 2018 From: xuyun at jxresearch.com (=?gb2312?B?0OzUzA==?=) Date: Thu, 29 Nov 2018 15:44:11 +0800 Subject: [Starlingx-discuss] Unable to mount squashfs.img In-Reply-To: References: <840F9C42-9C1E-4E5F-A7D3-65BF54C4B715@jxresearch.com> Message-ID: Hello Hu Yong, Thank you for your quick help! Yes, my download of squashes.img is corrupted (only has size of 384k). I’m downloading it manually. Thanks again. Br, Xu Yun > 在 2018年11月29日,下午3:41,Hu, Yong 写道: > > Can you confirm the following file exists in your mirror? > > /import/mirrors/CentOS/stx-r1-centos75/CentOS/pike/Binary/LiveOS/squashfs.img > > If the file does exit, very likely it was *corrupted* because it seemed the failure came from: > > mount -o loop -t squashfs $ORIG_SQUASHFS $work_dir/squashfs.mnt > > in script: "~/cgcs-root/build-tools/make-installer-images.sh" > > You can manually mount "squashfs.img" to confirm it is not corrupted. > > > On 29/11/2018, 3:30 PM, "徐蕴" wrote: > > Hi, > > I’m trying to build a StarlingX ISO. I got an error at step 'update-pxe-network-installer’: > > -rw-r--r-- 1 root root 55629360 Nov 29 07:11 /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/output/new-initrd.img > -rwxr-xr-x 1 root root 6588016 Nov 29 07:09 /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/output/new-vmlinuz > ---------------- start to make new squashfs.img ------------- > /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/orig/squashfs.img > /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/squashfs.mnt > mount: wrong fs type, bad option, bad superblock on /dev/loop2, > missing codepage or helper program, or other error > > In some cases useful info is found in syslog - try > dmesg | tail or so. > > Any suggestion how to fix it? Thank you. > > br, > Xu Yun > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > From yan.chen at intel.com Thu Nov 29 08:30:06 2018 From: yan.chen at intel.com (Chen, Yan) Date: Thu, 29 Nov 2018 08:30:06 +0000 Subject: [Starlingx-discuss] Please help to review the patch https://review.openstack.org/#/c/619462/ Message-ID: <72AD03D27224C74982BE13246D75B3973999F8AD@SHSMSX103.ccr.corp.intel.com> Hi Please help to review the patch https://review.openstack.org/#/c/619462/. It is found by a higher version gcc, but it is still an obvious issue. Yan -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Peters at windriver.com Thu Nov 29 12:58:31 2018 From: Matt.Peters at windriver.com (Peters, Matt) Date: Thu, 29 Nov 2018 12:58:31 +0000 Subject: [Starlingx-discuss] Analysis of patch 88b7bc7 for StartlingX upstreaming In-Reply-To: References: <2D8849FB-AB0B-4385-9DAC-9BF4BEF41960@windriver.com> Message-ID: <6A51E55B-3A78-4182-9605-FE97AF2A0A62@windriver.com> Hi Chenjie, Since this isn’t causing a runtime issue at the moment, I think this can be fixed as part of the upstreaming where it can be reviewed in Gerrit. If you are looking for confirmation of the changes prior to that I would create a pull request so it can be reviewed/merged prior. -Matt From: "Xu, Chenjie" Date: Wednesday, November 28, 2018 at 9:22 PM To: "Peters, Matt" Cc: "starlingx-discuss at lists.starlingx.io" Subject: RE: [Starlingx-discuss] Analysis of patch 88b7bc7 for StartlingX upstreaming Hi Matt, Thanks for your comments! An RFE has been written to upstream patch 88b7bc7. Before I submit the code, I think we should fix this bug. I think we can change the parameter “host” to “agent” in the following lines: https://github.com/starlingx-staging/stx-neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/rpc_manager/l2population_rpc.py#L44 https://github.com/starlingx-staging/stx-neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/rpc_manager/l2population_rpc.py#L57 https://github.com/starlingx-staging/stx-neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/mech_driver.py#L444 https://github.com/starlingx-staging/stx-neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/mech_driver.py#L434 Please let me know what you think of the proposal. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Thursday, November 29, 2018 1:43 AM To: Xu, Chenjie Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Analysis of patch 88b7bc7 for StartlingX upstreaming Hello Chenjie, I agree, this is a bug. I think the only reason it hasn’t been an issue is because the only user of the get_fdb_entries RPC is the BGP agent and it is not passing a host in the request (it is None), therefore it excludes the attempt to try and access the parameter as an agent based on the condition in _create_agent_fdb. Here is the BGP caller: https://github.com/starlingx-staging/stx-neutron-dynamic-routing/blob/master/neutron_dynamic_routing/services/bgp/agent/bgp_dragent.py#L1498 From: "Xu, Chenjie" > Date: Wednesday, November 28, 2018 at 10:11 AM To: "Peters, Matt" > Cc: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] Analysis of patch 88b7bc7 for StartlingX upstreaming Hi Matt, I think that there exists a bug in patch 88b7bc7. Function _get_fdb_entries will call function _create­_agent_fdb by following line: https://github.com/starlingx-staging/stx-neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/mech_driver.py#L441 The variable “host” will be used to call _create_agent_fdb. However function _create_agent_fdb expects variable “agent”: https://github.com/starlingx-staging/stx-neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/mech_driver.py#L264 I think this should be a bug. Could you please help review and comment? Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From chenjie.xu at intel.com Thu Nov 29 15:29:01 2018 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Thu, 29 Nov 2018 15:29:01 +0000 Subject: [Starlingx-discuss] Analysis of patch 88b7bc7 for StartlingX upstreaming In-Reply-To: <6A51E55B-3A78-4182-9605-FE97AF2A0A62@windriver.com> References: <2D8849FB-AB0B-4385-9DAC-9BF4BEF41960@windriver.com> <6A51E55B-3A78-4182-9605-FE97AF2A0A62@windriver.com> Message-ID: Hi Matt, Thanks for your reply! Yes, we can fix this bug as part of the upstreaming. The code can be viewed by following link: https://review.openstack.org/#/c/620929/ Please help comment and fix the bug. The RFE for patch 88b7bc7 is attached. Could you please help review and comment? Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Thursday, November 29, 2018 8:59 PM To: Xu, Chenjie Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Analysis of patch 88b7bc7 for StartlingX upstreaming Hi Chenjie, Since this isn’t causing a runtime issue at the moment, I think this can be fixed as part of the upstreaming where it can be reviewed in Gerrit. If you are looking for confirmation of the changes prior to that I would create a pull request so it can be reviewed/merged prior. -Matt From: "Xu, Chenjie" > Date: Wednesday, November 28, 2018 at 9:22 PM To: "Peters, Matt" > Cc: "starlingx-discuss at lists.starlingx.io" > Subject: RE: [Starlingx-discuss] Analysis of patch 88b7bc7 for StartlingX upstreaming Hi Matt, Thanks for your comments! An RFE has been written to upstream patch 88b7bc7. Before I submit the code, I think we should fix this bug. I think we can change the parameter “host” to “agent” in the following lines: https://github.com/starlingx-staging/stx-neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/rpc_manager/l2population_rpc.py#L44 https://github.com/starlingx-staging/stx-neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/rpc_manager/l2population_rpc.py#L57 https://github.com/starlingx-staging/stx-neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/mech_driver.py#L444 https://github.com/starlingx-staging/stx-neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/mech_driver.py#L434 Please let me know what you think of the proposal. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Thursday, November 29, 2018 1:43 AM To: Xu, Chenjie > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Analysis of patch 88b7bc7 for StartlingX upstreaming Hello Chenjie, I agree, this is a bug. I think the only reason it hasn’t been an issue is because the only user of the get_fdb_entries RPC is the BGP agent and it is not passing a host in the request (it is None), therefore it excludes the attempt to try and access the parameter as an agent based on the condition in _create_agent_fdb. Here is the BGP caller: https://github.com/starlingx-staging/stx-neutron-dynamic-routing/blob/master/neutron_dynamic_routing/services/bgp/agent/bgp_dragent.py#L1498 From: "Xu, Chenjie" > Date: Wednesday, November 28, 2018 at 10:11 AM To: "Peters, Matt" > Cc: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] Analysis of patch 88b7bc7 for StartlingX upstreaming Hi Matt, I think that there exists a bug in patch 88b7bc7. Function _get_fdb_entries will call function _create­_agent_fdb by following line: https://github.com/starlingx-staging/stx-neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/mech_driver.py#L441 The variable “host” will be used to call _create_agent_fdb. However function _create_agent_fdb expects variable “agent”: https://github.com/starlingx-staging/stx-neutron/blob/master/neutron/plugins/ml2/drivers/l2pop/mech_driver.py#L264 I think this should be a bug. Could you please help review and comment? Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: RFE_ADD_RPC_QUERY_API_TO_L2POP_FOR_FDB_RESYNC.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 17671 bytes Desc: RFE_ADD_RPC_QUERY_API_TO_L2POP_FOR_FDB_RESYNC.docx URL: From Frank.Miller at windriver.com Thu Nov 29 16:37:22 2018 From: Frank.Miller at windriver.com (Miller, Frank) Date: Thu, 29 Nov 2018 16:37:22 +0000 Subject: [Starlingx-discuss] How to post a PPT on StarlingX wiki? Message-ID: Does anyone know the best way to take a powerpoint presentation and put it into a format that could be posted on the wiki? Would appreciate your suggestions - thanks in advance. Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From vm.rod25 at gmail.com Thu Nov 29 16:43:21 2018 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Thu, 29 Nov 2018 10:43:21 -0600 Subject: [Starlingx-discuss] [Build] go loanguage In-Reply-To: References: <5c031adb-1e32-37c5-2f88-0720e11bd569@windriver.com> Message-ID: On Fri, Nov 23, 2018 at 4:30 PM Victor Rodriguez wrote: > > On Fri, Nov 23, 2018 at 1:48 PM Scott Little wrote: > > > > I have a designer that want to introduce a GO language package into our > > build. This raises the question of how to handle GO's 'imports'. > > > > First a disclaimer. I'm not a 'GO' exports. The following discussion > > points are based on my brief research. > > > > Go imports are roughly akin to a 'C' language include, with one or few > > major differences. > > 1) It points to a directory rather than a file, which could be local or > > relative to your GOPATH > > 2) The convention is to use a path that is a crude approximation of the > > url from which it can be obtained. e.g. import ( > > "github.com/docker/distribution/registry/api/errcode" ) > > 3) If the directory is NOT already present, it can probably be > > downloaded automatically with tools like 'go get' or 'dep' (aka > > golang-dep). These tools attempt transform the path into a URI, trying > > several vcs download protocols (git, mercurial, subversion...). > > Downloads are stored under a local 'vendor' sub-directory. There are a > > few wrinkles, like the ability of a sire to respond with a re-direct to > > another site. > > > > There are centos rpms for a handful of core libraries, delivering code > > to /usr/share/gocode (part of your GOPATH). However most go code has > > never been published as an rpm, and much of the remainder seems to be a > > one off rpm, with no ongoing maintenance. > > > > 'go get' just seems to grab the latest code. Reproducibility is a big > > concern. > > > > 'dep init' solves the reproducibility concern. It grabs the latest > > code, but also generates a 'lock' file that capture a CVS commit > > > identifier (e.g. a git SHA). Deliver the lock file with your code and > > 'dep ensure' will use the lock file to download the same code every > > time. Dep does not currently ship as an RPM. I have a working spec > > file for dep 0.4.1. Dep 0.5.0 needs more work. > > > > For me it works : curl > https://raw.githubusercontent.com/golang/dep/master/install.sh | sh > > > > Licenses of public go libraries seem to be permissive, at least for a > > statically linked binary, which is what we would want to ship. Not so > > sure about the inclusion of library source as an embedded vendor > > sub-directory in our own src.rpm packages. That would be one for the > > lawyers. > > > > > > So our options seem to be. > > 1) Create rpms of all the go libraries we need, populating > > /usr/share/gocode. There might be some tooling available to help with this. > > Pro: Don't require network access to build. > > Pro: Reproducible builds > > Pro: License of each go rpm is hopefully clear. > > Con: We'll be adding a lot of go libraries to our manifest. Assuming > > all are available via git. > > Con: Maintenance headache. Create spec files and compile rpms for > > the transitive set of imports. When do we upversion the rpms? > > Con: More packages we need to build > > > > 2) Allow our new go packages to include a pre-populated vendor > > sub-directory. > > Pro: Don't require network access to build > > Pro: Reproducible builds > > Con: We store snapshots of 3rd party code in the same src.rpm as our > > own code. > > Con: More complicated licensing statements. > > Con: Maintenance headache. When do we upversion the snapshots? Who > > want's to code inspect the mess? > > Con: If we have many go packages, there may multiple copies of the > > same library spread through our code base. > > Con: Is StarlingX, and OpenStack, ok with all the go code snapshots > > being added to our gits? > > > > 3) Use 'dep init' to create a lock file. Deliver only the lock file > > alongside our go code. Use 'dep ensure' during the build to download > > the required libraries. > > Pro: Lowest maintenance on our part > > Pro: Don't need to store a snapshot of any go libraries, nor add it > > too our manifest. > > Con: Need network access to build, not just in the docker container, > > but all the way down to the mock instance. > > Con: Relies on the upstream server continuing to host the package. > > Con: Relies on stability of upstream server and it's network > > connectivity. Vast majority of packages seem to come from golang.org, > > github and go.googlesource.com, so not likely a concern. > > > > I'm inclined to option 3. > > > > I am in favor of providing both go get and dep since they are for > different reasons > > https://github.com/golang/dep/issues/376 > diference between go get and dep ensure : go get: I want to download the source code for a go project so that I can work on it myself, or to install a tool. This clones the repo under GOPATH for all to use. dep ensure: I have imported a new dependency in my code and want to download the dependency so I can start using it. My workflow is "add the import to the code, and then run dep ensure so that the manifest/lock/vendor are updated". This clones the repo under my project's vendor directory, and remembers the revision used so that everyone who works on my project is guaranteed to be using the same version of dependencies. > > Opinions? > > > > Scott > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Thu Nov 29 16:45:56 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 29 Nov 2018 16:45:56 +0000 Subject: [Starlingx-discuss] How to post a PPT on StarlingX wiki? In-Reply-To: References: Message-ID: <9A85D2917C58154C960D95352B22818BB1EBF2AA@fmsmsx117.amr.corp.intel.com> The wiki has file size limits. You might be able to get a .pdf version posted if it's small enough. In general we have needed Ildiko's help to get documents posted to the infrastructure e.g. the onboarding slides linked off starlingX.io. brucej From: Miller, Frank [mailto:Frank.Miller at windriver.com] Sent: Thursday, November 29, 2018 8:37 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] How to post a PPT on StarlingX wiki? Does anyone know the best way to take a powerpoint presentation and put it into a format that could be posted on the wiki? Would appreciate your suggestions - thanks in advance. Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Thu Nov 29 16:45:34 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Thu, 29 Nov 2018 16:45:34 +0000 Subject: [Starlingx-discuss] Openstack Patch Elimination Strategy Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB32BC10@ALA-MBD.corp.ad.wrs.com> Folks, Slides from the patch elimination discussion from the TSC call this morning. If you have any questions, please let me know Brent -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: stx_openstack_patch_elimination_v1.pdf Type: application/pdf Size: 524875 bytes Desc: stx_openstack_patch_elimination_v1.pdf URL: From david.a.cobbley at intel.com Thu Nov 29 17:16:27 2018 From: david.a.cobbley at intel.com (Cobbley, David A) Date: Thu, 29 Nov 2018 17:16:27 +0000 Subject: [Starlingx-discuss] How to post a PPT on StarlingX wiki? Message-ID: <7B2CD0AF-ABF6-4700-9B46-7F2F3B77E486@intel.com> Until this frustrating problem is solved, you can also break a larger presentation into individual slides as pdf’s or jpeg files. -- David C From: "Jones, Bruce E" Date: Thursday, November 29, 2018 at 8:46 AM To: "Miller, Frank" , Ildiko Vancsa Cc: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] How to post a PPT on StarlingX wiki? The wiki has file size limits. You might be able to get a .pdf version posted if it’s small enough. In general we have needed Ildiko’s help to get documents posted to the infrastructure e.g. the onboarding slides linked off starlingX.io. brucej From: Miller, Frank [mailto:Frank.Miller at windriver.com] Sent: Thursday, November 29, 2018 8:37 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] How to post a PPT on StarlingX wiki? Does anyone know the best way to take a powerpoint presentation and put it into a format that could be posted on the wiki? Would appreciate your suggestions – thanks in advance. Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Peters at windriver.com Thu Nov 29 18:04:38 2018 From: Matt.Peters at windriver.com (Peters, Matt) Date: Thu, 29 Nov 2018 18:04:38 +0000 Subject: [Starlingx-discuss] no DHCP response for instance In-Reply-To: References: Message-ID: <3D52F808-7125-4EE0-9963-4B12DB754F0F@windriver.com> Hello, Do you have additional information regarding your test setup? * Can you provide a description (or output) of your tenant network topology? * Are you running a single node or multi-node setup? * Are you running in a virtual environment or on physical hardware? * Have you validated connectivity between the compute hosts? * What is the guest image that you are using for the test? * If you assign the IP manually, do you have proper connectivity – i.e. is it just a DHCP issue or underlying network topology issue? Are you following the instructions from the StarlingX wiki? https://docs.starlingx.io/installation_guide/index.html Hopefully with some of the information you can provide above we may be able to offer additional assistance. Regards, Matt From: SkyDiablo Date: Wednesday, November 28, 2018 at 8:03 AM To: starlingx Subject: [Starlingx-discuss] no DHCP response for instance Hello, now I had spent really a lot of time and patience with the whole topic openstack. I always think now I've managed it, now everything runs but always comes something new which does not work :( but i really don't understand it anymore, if i create an instance it will not be assigned an IP anymore via DHCP? according to the configuration a port with IP has been created, but this information doesn't arrive at client? what really irritates me is that everything worked? i use the pre-compiled ISO of starlingX. i don't know exactly where to look, can someone give me some tips where to look for to narrow down the problem? greez & thx, volker... -------------- next part -------------- An HTML attachment was scrubbed... URL: From ada.cabrales at intel.com Thu Nov 29 18:23:10 2018 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Thu, 29 Nov 2018 18:23:10 +0000 Subject: [Starlingx-discuss] STX Test Strategy In-Reply-To: <3CAA827B7A79BA46B15B280EC82088FE4823680D@ALA-MBD.corp.ad.wrs.com> References: <3CAA827B7A79BA46B15B280EC82088FE4823680D@ALA-MBD.corp.ad.wrs.com> Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7C375B61@fmsmsx104.amr.corp.intel.com> That's right, Numan. I've added the topic to the agenda for next week. Regards Ada From: Waheed, Numan [mailto:Numan.Waheed at windriver.com] Sent: Wednesday, November 28, 2018 4:08 PM To: Cabrales, Ada ; starlingx-discuss at lists.starlingx.io Subject: STX Test Strategy Hi Ada, I was wondering that we don't have an STX Test Strategy that has been discussed with community. It is possible that you might have some test strategy and I also have a test strategy but these have not been discussed and known to the community. As STX community is growing, there is need to define a test strategy and make it public so that community can follow it. Can we please discuss it in our next Test meeting. Thanks, Numan. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openstack.org Thu Nov 29 18:26:28 2018 From: ildiko at openstack.org (Ildiko Vancsa) Date: Thu, 29 Nov 2018 19:26:28 +0100 Subject: [Starlingx-discuss] How to post a PPT on StarlingX wiki? In-Reply-To: <7B2CD0AF-ABF6-4700-9B46-7F2F3B77E486@intel.com> References: <7B2CD0AF-ABF6-4700-9B46-7F2F3B77E486@intel.com> Message-ID: Hi, The reason for the limitations on the wiki is that self-service upload of arbitrary files is prone to abuse. A quick solution is to setup a separate git repository to store these files and we could leverage Zuul to get them uploaded to the docs webpage. On the longer term it would be beneficial to look into what is sensible to be presented and stored as a pptx or pdf file versus something plain text based format or wiki page. Design documents or artifacts such as gap analysis work could live better as .rst documents for instance in git to provide version control to it as well in case it needs discussion and/or evolution. Another aspect to consider is how valuable just the presentation file itself is considering that only a subset of the community attended the call or face to face meeting where it was presented? I’m bringing up the question from the perspective of how we structure information in order to make it informative for new comers as well as current active community members and whether it would be valuable to rethink how we share information as opposed to treating the symptom which is the limitations on storing arbitrary files. What do you think? Thanks, Ildikó > On 2018. Nov 29., at 18:16, Cobbley, David A wrote: > > Until this frustrating problem is solved, you can also break a larger presentation into individual slides as pdf’s or jpeg files. > > -- David C > > > From: "Jones, Bruce E" > Date: Thursday, November 29, 2018 at 8:46 AM > To: "Miller, Frank" , Ildiko Vancsa > Cc: "starlingx-discuss at lists.starlingx.io" > Subject: Re: [Starlingx-discuss] How to post a PPT on StarlingX wiki? > > The wiki has file size limits. You might be able to get a .pdf version posted if it’s small enough. > > In general we have needed Ildiko’s help to get documents posted to the infrastructure e.g. the onboarding slides linked off starlingX.io. > > brucej > > From: Miller, Frank [mailto:Frank.Miller at windriver.com] > Sent: Thursday, November 29, 2018 8:37 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] How to post a PPT on StarlingX wiki? > > Does anyone know the best way to take a powerpoint presentation and put it into a format that could be posted on the wiki? Would appreciate your suggestions – thanks in advance. > > Frank From Frank.Miller at windriver.com Thu Nov 29 21:54:50 2018 From: Frank.Miller at windriver.com (Miller, Frank) Date: Thu, 29 Nov 2018 21:54:50 +0000 Subject: [Starlingx-discuss] StarlingX Infrastructure Containerization Message-ID: For those contributing to or interested in the Containerization subproject a weekly meeting has been set up: Timeslot: 11am EST / 8am PDT / 1600 UTC Call details * Zoom link: https://zoom.us/j/342730236 * Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes Project notes are at https://etherpad.openstack.org/p/stx-containerization Containerization subproject wiki: https://wiki.openstack.org/wiki/StarlingX/Containers -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2303 bytes Desc: not available URL: From Ghada.Khalil at windriver.com Thu Nov 29 23:41:49 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 29 Nov 2018 23:41:49 +0000 Subject: [Starlingx-discuss] Minutes: StartlingX Networking Meeting -- 11/29 Message-ID: <151EE31B9FCCA54397A757BC674650F0BA489719@ALA-MBD.corp.ad.wrs.com> Meeting minutes/agenda are captured at: https://etherpad.openstack.org/p/stx-networking Team Meeting Agenda/Notes - Nov 29/2018 * Network Segment Range Management * spec merged on Nov 29: https://review.openstack.org/#/c/599980 * Discuss next steps for implementation ? Kailun started implementation a week ago ? Miguel indicated that code can be merged at any time until the end of the cycle. The later the submission, the more pressure there is as the reviewers' becomes busier, so the sooner the better. Additionally, smaller submissions are better and easier to merge. Miguel will continue to highlight this blueprint in the regular neutron meeting in the blueprint section. ? For StarlingX point of view, the target date for the code to merge is end of January as this is a key dependency for other StarlingX re-factoring work. ? Next Step: * Kailun to prepare a set of work items and effort for next week's meeting. * From Miguel, having a set of patches early (target: Dec 13) would be great. Miguel will mention this in the next neutron meeting to align the code reviewers. * e490b5a -- https://bugs.launchpad.net/neutron/+bug/1800417 * Current theory is that this issue is no longer reproducible in upstream. * Allain to review the latest data * 8e7249 -- https://bugs.launchpad.net/neutron/+bug/1800599 * Based on testing, Huifeng believes that this issue is addressed by the new wsgi-based web server. * If the results are ok, Huifeng can propose to the neutron community to move from the current eventlet-based web server to the wsgi-based web server. * Allain to review the latest data and provide his feedback. Also added Miguel on the thread for his input. * 6ed8fe -- Confirmed with Allain that this is a bug. Next step is to create a neutron launchpad bug * fd6cfc0 -- RFE - https://bugs.launchpad.net/neutron/+bug/1795212 (Prevent DHCP agent from processing stale RPC messages) * Community questions in the RFE were answered. Request for Miguel to review in the next neutron driver meeting. Need the community to valiate the requirement. * The patch is in good change and can proceed once the community approves the RFE: https://review.openstack.org/#/c/609463/ * MattW still looking at BGP EVPN lower priority items. Requested for him to follow up with Forrest to see if he can take on some of the higher priority commits instead. * For reference, high priority commits for neutron upstreaming: * 0005-pnet-extension-to-expose-providernet-management-at-a.patch In Progress 021ae1a * 0014-CGTS-3059-prevent-dhcp-agent-from-processing-stale-R.patch In Review fd6cfc0 * 0018-US86444-patching-scripts-for-neutron-processes.patch Not started 87a8c625 * 0023-trunk-add-support-to-delete-bound-trunk.patch In Review 6955351 * 0037-CGTS-3239-add-process-synchronization-around-segment.patch In Progress e490b5a * 0039-CGTS-3885-dhcp-handle-concurrent-port-creation-error.patch In Progress a38f89 * 0040-CGTS-4971-rpc-removing-timeout-backoff-multiplier.patch In Progress 2e4ca00 * 0047-CGTS-6926-wsgi-prevent-accepting-socket-without-a-gr.patch In Progress 8e72491 * 0062-CGTS-5759-dvr-force-admin-state-update-before-distri.patch Not started edf9731 * 0065-CGTS-8104-dvr-do-not-create-agent-gateway-ports-unle.patch Not started 2857911 * 0077-CGTS-8130-api-reject-routes-with-invalid-network-val.patch Not started 6ed8fe6 * 0081-l2pop-added-rpc-query-api-for-resync.patch In Progress 88b7bc7 * 0087-l2pop-support-for-FDB-extenders-from-other-projects.patch In Review 4ae5a58 * 0092-l3-add-l2pop-support-for-floatingip-resources.patch In Progress 9f926a5 * 0147-CGTS-8844-ml2-use-new-bindings-when-failing-concurre.patch In Review da31d0 * 0009-CGTS-2592-allow-admin-password-changes-on-controller.patch Not started c3fa9d9b3303433f09ca16c089b2db52e116dfba * 0014-US106792-add-support-for-querying-quotas-with-usage.patch Not started 71c07d7b22bb5aaea8c39d4d4b97883a0bae5c1b * Email on stx-discuss regarding no dhcp response to VM. Not enough information provided. MattP to respond requesting more info. -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhaowei7146 at fiberhome.com Fri Nov 30 01:43:31 2018 From: zhaowei7146 at fiberhome.com (=?utf-8?B?6LW15Lyf?=) Date: Fri, 30 Nov 2018 09:43:31 +0800 Subject: [Starlingx-discuss] When is the StarlingX Infrastructure Containerization feature released? Message-ID: <000c01d4884e$194f21b0$4bed6510$@fiberhome.com> Hello everyone, StarlingX plan to use k8s + helm to containerize openstack, but I didn't see the specific R&D plan online. When is the StarlingX Infrastructure Containerization feature released? March, July, or November 2019? Best regards -------------- next part -------------- An HTML attachment was scrubbed... URL: From quickconvey at gmail.com Fri Nov 30 16:05:17 2018 From: quickconvey at gmail.com (Quick Convey) Date: Fri, 30 Nov 2018 21:35:17 +0530 Subject: [Starlingx-discuss] Starlingx Features List and 101 document Message-ID: Hi, I have installed Starlingx simplex mode. Could you please guide me to explore the features of Starlingx. Is there any Starlingx 101 document. I have openstack and nfv knowledge. *Which document I should explore after the installation of Starlingx.* Thanks, -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Fri Nov 30 16:10:22 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 30 Nov 2018 16:10:22 +0000 Subject: [Starlingx-discuss] When is the StarlingX Infrastructure Containerization feature released? In-Reply-To: <000c01d4884e$194f21b0$4bed6510$@fiberhome.com> References: <000c01d4884e$194f21b0$4bed6510$@fiberhome.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA489928@ALA-MBD.corp.ad.wrs.com> Hello, The content and plan for the next release of StarlingX is under review. It will be published to the community in the next few weeks. Regards, Ghada StarlingX Release Prime From: 赵伟 [mailto:zhaowei7146 at fiberhome.com] Sent: Thursday, November 29, 2018 8:44 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] When is the StarlingX Infrastructure Containerization feature released? Hello everyone, StarlingX plan to use k8s + helm to containerize openstack, but I didn’t see the specific R&D plan online. When is the StarlingX Infrastructure Containerization feature released? March, July, or November 2019? Best regards -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Fri Nov 30 17:44:41 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 30 Nov 2018 17:44:41 +0000 Subject: [Starlingx-discuss] New location for January meeting Etherpad Message-ID: <9A85D2917C58154C960D95352B22818BB1EC016B@fmsmsx117.amr.corp.intel.com> I have moved the info and draft agenda for the January community meet-up to a new Etherpad https://etherpad.openstack.org/p/stx-chandler-meetup. The wiki link has been moved to the Meetings section. Content is unchanged and feedback/additions for the agenda is welcome! The location for the meet-up is unchanged - Intel's Chandler campus in sunny Arizona. brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Fri Nov 30 17:58:06 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 30 Nov 2018 17:58:06 +0000 Subject: [Starlingx-discuss] StarlingX.io modifications Message-ID: <9A85D2917C58154C960D95352B22818BB1EC01D3@fmsmsx117.amr.corp.intel.com> We now have access to the github source repo for the www.starlingx.io page. If you'd like to see changes made, please open a LaunchPad or StoryBoard entry for the Docs team to handle (tag stx.docs). Thanks! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ken.Young at windriver.com Fri Nov 30 18:24:03 2018 From: Ken.Young at windriver.com (Young, Ken) Date: Fri, 30 Nov 2018 18:24:03 +0000 Subject: [Starlingx-discuss] Sanity of Mirror Builds Message-ID: Ada, I have updated the Build team Wiki to highlight the location of the nightly builds. For your convenience, you can find them here: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ As we discussed on the community call, I would like to discuss next steps for the usage of these builds. Are you planning to have a test meeting on Tuesday, Dec 4th @ 9 PST? Regards, Ken Y -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Fri Nov 30 23:48:54 2018 From: sgw at linux.intel.com (Saul Wold) Date: Fri, 30 Nov 2018 15:48:54 -0800 Subject: [Starlingx-discuss] Centos Distro Direction Message-ID: <9aed8be1-2aca-c537-2d48-25bac32354ed@linux.intel.com> Folks, As we move forward into the spring release (Stein based), we will also be dealing with another CentOS update. RHEL has already released the 7.6 Update on Oct 30th, typically we should expect the CentOS 7.6 update shortl, about 30 days after RHEL releases. We should do the 7.6 Update as we did the 7.5 Update on a feature branch, it took about 2 months last time (including initial setup, rebasing, and de-fuzzing), I expect it will be shorter this time based on our past learning. We should start out with creating the feature branches (I will work with Dean on this) for stx-integ, stx-root, stx-tools, and stx-upstream repos. When we start the work, we need to remember to rebase the feature branches regularly and check for patch fuzzing issues. Cindy, can you please put this on your agenda for the next Non-Openstack Distro meeting. While on the topic of Cento Distro updates, many of you may have heard that RHEL 8 Beta was announced on Nov 14 [0], while this is not a CentOS release we should start thinking about that upgrade as it will be a larger effort as it includes the 4.18 kernel (alas not the 4.19 LTS kernel) along with many other upgrades. We should start a feature branch for CentOS 8 as well to do the updates, This will help reduce some of the patch load from the backported patches. Since we don't know exactly when CentOS 8 will be available this should be a Train-based release target (Fall 2019) (at the earliest) [0] https://www.redhat.com/en/blog/powering-its-future-while-preserving-present-introducing-red-hat-enterprise-linux-8-beta Thanks Sau!