From juan.carlos.alonso at intel.com Fri Mar 1 05:53:57 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Fri, 1 Mar 2019 05:53:57 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190227 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9EC99@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO - f/Stein branch: bootimage.iso from 2019-Feb-27 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment Duplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack 55 TCs [PASS] Sanity Platform In Development TOTAL: [ 55 TCs PASS ] =========================================== Sanity Test is executed in a Containers - Virtual Environment Simplex Setup 04 TCs [PASS] Provisioning Manual [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 02 TCs [PASS] TOTAL: [ 58 TCs PASS ] Duplex Setup 04 TCs [PASS] Provisioning Manual [PASS] Sanity OpenStack 55 TCs [PASS] Sanity Platform In Development TOTAL: [ 59 TCs PASS ] ------------------------------------------------------------------ Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From Barton.Wensley at windriver.com Fri Mar 1 12:57:55 2019 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Fri, 1 Mar 2019 12:57:55 +0000 Subject: [Starlingx-discuss] Feedback needed on updated overview diagram In-Reply-To: <9A85D2917C58154C960D95352B22818BC3AD863A@fmsmsx121.amr.corp.intel.com> References: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA6763F@ALA-MBD.corp.ad.wrs.com> <53B57CC9-F9C3-4C88-BE19-F48DED4F7281@windriver.com> <14A48C18-A4AD-4452-9B21-9A51541FC711@gmail.com> <9A85D2917C58154C960D95352B22818BC3AD863A@fmsmsx121.amr.corp.intel.com> Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA695D6@ALA-MBD.corp.ad.wrs.com> +1 -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: February 28, 2019 5:55 PM To: Ildiko Vancsa; Gowan, Jeff; Wensley, Barton Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Feedback needed on updated overview diagram LGTM, nicely done. -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: Thursday, February 28, 2019 1:32 PM To: Gowan, Jeff ; Wensley, Barton Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Feedback needed on updated overview diagram Hi, Thank you for the feedback. Here is an updated diagram incorporating your comments: https://www.dropbox.com/s/0qczsc6pl55j9i4/StarlingX_Diagram_SimplifiedArchitecture.jpg?dl=0 Please let me know your thoughts. Thanks, Ildikó > On 2019. Feb 22., at 21:42, Gowan, Jeff wrote: > > I agree with Bart. > -Jeff > > On 2/22/19, 5:14 AM, "Wensley, Barton" wrote: > > Ildikó, > > I like version -01 - with the kubernetes component names. Each component is already in the "Kubernetes Components" box so you aren't losing any detail by dropping the "kube-" prefix. > > For the OpenStack components, I'd lean towards using the functional names (Compute, Identity, Block Storage) instead of the code names. Anyone familiar with OpenStack will understand either, but for those less OpenStack knowledge, the functional names will be easier to understand. > > Bart > > -----Original Message----- > From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] > Sent: February 22, 2019 4:09 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Feedback needed on updated overview diagram > > Hi StarlingX Community, > > We are working on an updated overview diagram for StarlingX to highlight the work on containerization: https://www.dropbox.com/sh/7fz6ae9moi89e5l/AABBG5PzzJAv7BKKJ1aEdBDja?dl=0 > > We have two versions adding Kubernetes components to the diagram in a dedicated section and update the open source components on the bottom. The difference between the two versions is the way to refer to the Kubernetes items, -01 is using component names and -02 is using the CLI reference where applicable. > > I would prefer version -01 for simplicity as well as making it clear that this is an overview diagram as opposed to a detailed architecture diagram. What do you think? > > > Another angle to think about is readability of the diagram for which it would be good to reduce the number of boxes with text. We could do the same approach with the OpenStack components as I described above and switch to ‘Compute’, ‘Identity’, ‘Block Storage’, etc and drop a few of the currently listed components and indicate it is not a comprehensive list. What would be your preference? > > > 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 Brent.Rowsell at windriver.com Fri Mar 1 13:09:00 2019 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Fri, 1 Mar 2019 13:09:00 +0000 Subject: [Starlingx-discuss] Feedback needed on updated overview diagram In-Reply-To: <14A48C18-A4AD-4452-9B21-9A51541FC711@gmail.com> References: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA6763F@ALA-MBD.corp.ad.wrs.com> <53B57CC9-F9C3-4C88-BE19-F48DED4F7281@windriver.com> <14A48C18-A4AD-4452-9B21-9A51541FC711@gmail.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB3F45A4@ALA-MBD.corp.ad.wrs.com> LGTM. Thanks, Brent -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: Thursday, February 28, 2019 4:32 PM To: Gowan, Jeff ; Wensley, Barton Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Feedback needed on updated overview diagram Hi, Thank you for the feedback. Here is an updated diagram incorporating your comments: https://www.dropbox.com/s/0qczsc6pl55j9i4/StarlingX_Diagram_SimplifiedArchitecture.jpg?dl=0 Please let me know your thoughts. Thanks, Ildikó > On 2019. Feb 22., at 21:42, Gowan, Jeff wrote: > > I agree with Bart. > -Jeff > > On 2/22/19, 5:14 AM, "Wensley, Barton" wrote: > > Ildikó, > > I like version -01 - with the kubernetes component names. Each component is already in the "Kubernetes Components" box so you aren't losing any detail by dropping the "kube-" prefix. > > For the OpenStack components, I'd lean towards using the functional names (Compute, Identity, Block Storage) instead of the code names. Anyone familiar with OpenStack will understand either, but for those less OpenStack knowledge, the functional names will be easier to understand. > > Bart > > -----Original Message----- > From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] > Sent: February 22, 2019 4:09 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Feedback needed on updated overview diagram > > Hi StarlingX Community, > > We are working on an updated overview diagram for StarlingX to highlight the work on containerization: https://www.dropbox.com/sh/7fz6ae9moi89e5l/AABBG5PzzJAv7BKKJ1aEdBDja?dl=0 > > We have two versions adding Kubernetes components to the diagram in a dedicated section and update the open source components on the bottom. The difference between the two versions is the way to refer to the Kubernetes items, -01 is using component names and -02 is using the CLI reference where applicable. > > I would prefer version -01 for simplicity as well as making it clear that this is an overview diagram as opposed to a detailed architecture diagram. What do you think? > > > Another angle to think about is readability of the diagram for which it would be good to reduce the number of boxes with text. We could do the same approach with the OpenStack components as I described above and switch to ‘Compute’, ‘Identity’, ‘Block Storage’, etc and drop a few of the currently listed components and indicate it is not a comprehensive list. What would be your preference? > > > 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 Brent.Rowsell at windriver.com Fri Mar 1 13:19:43 2019 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Fri, 1 Mar 2019 13:19:43 +0000 Subject: [Starlingx-discuss] Is there any plan of containerize the flock services ? In-Reply-To: References: <3E6E6B86-E9C2-4159-B3B4-9105C79700D5@windriver.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB3F4676@ALA-MBD.corp.ad.wrs.com> Hi Victor, See inline Brent -----Original Message----- From: Victor Rodriguez [mailto:vm.rod25 at gmail.com] Sent: Wednesday, February 27, 2019 12:00 PM To: Rowsell, Brent Cc: starlingx-discuss at lists.starlingx.io; Miller, Frank Subject: Re: [Starlingx-discuss] Is there any plan of containerize the flock services ? On Tue, Feb 26, 2019 at 8:14 PM Rowsell, Brent wrote: > > Hi Victor, > > For R2 only the openstack and some of it’s supporting services will be containerized. > > A longer term objective is to containerize as much of the flock services as possible. This is a candidate for the next release and will be discussed as part of the R3 planning later this year. > > Brent > Thanks a lot for your repply Brent I definitely support the approach of containers, now, one question, if the goal is to containerize as much of the flock services as possible, can we have the list of what services are not going to be on containers? based on that we can minimize the efforts of packaging for Ubuntu and maybe help more on the containerization of the flock services. The more we have in containers the easier is for us to migrate to other OS ( the packages that might need be ported to other OS might be: kernel, horizon, and keystone right ? ) [BR] Unfortunately I will not have that view of what can/will be containerized until we start the R3 planning. So far we have a POC of fm-manager and fm-common [1], what I don't want is to spend time building debs that will not be useful in the future. Regards Victor Rodriguez [1] https://github.com/marcelarosalesj/stx-packaging/commit/4bf237bf5f97e68b96a5be14a3e260467190e767 > Sent from my iPhone > > > On Feb 26, 2019, at 11:59 AM, Victor Rodriguez wrote: > > > > Hi Frank and STX community > > > > Based on the presentation discuss during phoenix meeting last > > January I had the impression that flock services were meant to be on > > the host OS where the containers are running, is this still valid > > for the long term? > > > > I am asking this because on today multi-OS meeting we present the > > following architecture/plan: > > > > https://docs.google.com/presentation/d/1ck7vGH50AIAjUx9GNrIGtowG5qg7 > > OYUBNdJyY-5ZvDc/edit?usp=sharing > > > > Where we are considering the task of build all the flock services on > > Ubuntu, However, based on this task: > > > > https://storyboard.openstack.org/#!/story/2004008 > > > > Gives me the impression that there is a plan for reducing the number > > of flock services running on the host OS, If that is the case, Could > > you please share the list of what flock services that you have in > > mind to put in a container? this will help us to reduce the list of > > packages we need to build. > > > > On the same topic, for the none open stack packages like systemd, > > bash or python, do you have the list of packages that need to run > > outside the containers on the host OS? Having this exact list of > > packages will help us to focus on the exact packages to build on Ubuntu. > > > > Regards > > > > Victor Rodriguez > > > > _______________________________________________ > > 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 Mar 1 14:38:13 2019 From: scott.little at windriver.com (Scott Little) Date: Fri, 1 Mar 2019 09:38:13 -0500 Subject: [Starlingx-discuss] Cutover to containers. Message-ID: <2f7cc6b5-b864-1e0c-cebd-3e09964a6e68@windriver.com> The cutover to containers has been given the green light. I will be preforming the merge today. It would be helpful to not have any churn in the following repos...    stx-clients, stx-config, stx-integ, stx-nfv, stx-upstream, stx-gui, stx-tools, stx-manifest. So please hold off on you WF+1 against those gits. Thank you Scott Little From scott.little at windriver.com Fri Mar 1 18:09:22 2019 From: scott.little at windriver.com (Scott Little) Date: Fri, 1 Mar 2019 13:09:22 -0500 Subject: [Starlingx-discuss] Cutover to containers. In-Reply-To: <2f7cc6b5-b864-1e0c-cebd-3e09964a6e68@windriver.com> References: <2f7cc6b5-b864-1e0c-cebd-3e09964a6e68@windriver.com> Message-ID: Stein has been merged back into master.  Reviews are as follows... stx-manifest: https://review.openstack.org/640456 stx-clients: https://review.openstack.org/640459 stx-config: https://review.openstack.org/640464 stx-integ: https://review.openstack.org/640466 stx-nfv: https://review.openstack.org/640468 stx-upstream: https://review.openstack.org/640470 stx-gui: https://review.openstack.org/640472 stx-tools: https://review.openstack.org/640473 Scott On 2019-03-01 9:38 a.m., Scott Little wrote: > The cutover to containers has been given the green light. > > I will be preforming the merge today. > > It would be helpful to not have any churn in the following repos... > >    stx-clients, stx-config, stx-integ, stx-nfv, stx-upstream, stx-gui, > stx-tools, stx-manifest. > > So please hold off on you WF+1 against those gits. > > Thank you > > Scott Little > > > _______________________________________________ > 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 Mar 1 19:54:24 2019 From: scott.little at windriver.com (Scott Little) Date: Fri, 1 Mar 2019 14:54:24 -0500 Subject: [Starlingx-discuss] Cutover to containers. In-Reply-To: References: <2f7cc6b5-b864-1e0c-cebd-3e09964a6e68@windriver.com> Message-ID: All components have passed review and have been merged by Zuul. A CENGN build has been launched. Publication path for the iso will be http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ Containers will now be tagged dev-centos-master- or dev-centos-master-latest . Scott On 2019-03-01 1:09 p.m., Scott Little wrote: > Stein has been merged back into master.  Reviews are as follows... > > > stx-manifest: https://review.openstack.org/640456 > > stx-clients: https://review.openstack.org/640459 > > stx-config: https://review.openstack.org/640464 > > stx-integ: https://review.openstack.org/640466 > > stx-nfv: https://review.openstack.org/640468 > > stx-upstream: https://review.openstack.org/640470 > > stx-gui: https://review.openstack.org/640472 > > stx-tools: https://review.openstack.org/640473 > > > > Scott > > > > On 2019-03-01 9:38 a.m., Scott Little wrote: >> The cutover to containers has been given the green light. >> >> I will be preforming the merge today. >> >> It would be helpful to not have any churn in the following repos... >> >>    stx-clients, stx-config, stx-integ, stx-nfv, stx-upstream, >> stx-gui, stx-tools, stx-manifest. >> >> So please hold off on you WF+1 against those gits. >> >> Thank you >> >> Scott Little >> >> >> _______________________________________________ >> 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 Frank.Miller at windriver.com Sat Mar 2 00:14:31 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Sat, 2 Mar 2019 00:14:31 +0000 Subject: [Starlingx-discuss] Cutover to containers. In-Reply-To: References: <2f7cc6b5-b864-1e0c-cebd-3e09964a6e68@windriver.com> Message-ID: Thank-you Scott. A couple of quick notes for the Community: · All ISOs will now be configured to use containerized services. · StarlingX is now using docker images built off OpenStack master for the OpenStack services. · Commits can now be merged again as per usual. Frank From: Scott Little [mailto:scott.little at windriver.com] Sent: Friday, March 01, 2019 2:54 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cutover to containers. All components have passed review and have been merged by Zuul. A CENGN build has been launched. Publication path for the iso will be http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ Containers will now be tagged dev-centos-master- or dev-centos-master-latest . Scott On 2019-03-01 1:09 p.m., Scott Little wrote: Stein has been merged back into master. Reviews are as follows... stx-manifest: https://review.openstack.org/640456 stx-clients: https://review.openstack.org/640459 stx-config: https://review.openstack.org/640464 stx-integ: https://review.openstack.org/640466 stx-nfv: https://review.openstack.org/640468 stx-upstream: https://review.openstack.org/640470 stx-gui: https://review.openstack.org/640472 stx-tools: https://review.openstack.org/640473 Scott On 2019-03-01 9:38 a.m., Scott Little wrote: The cutover to containers has been given the green light. I will be preforming the merge today. It would be helpful to not have any churn in the following repos... stx-clients, stx-config, stx-integ, stx-nfv, stx-upstream, stx-gui, stx-tools, stx-manifest. So please hold off on you WF+1 against those gits. Thank you Scott Little _______________________________________________ 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 cesar.lara at intel.com Sat Mar 2 00:18:47 2019 From: cesar.lara at intel.com (Lara, Cesar) Date: Sat, 2 Mar 2019 00:18:47 +0000 Subject: [Starlingx-discuss] Cutover to containers. In-Reply-To: References: <2f7cc6b5-b864-1e0c-cebd-3e09964a6e68@windriver.com> , Message-ID: <7070a800-8afa-4ac7-8ddb-811c3f068ae3@intel.com> This is definitely a great milestone, thank you all for the hard work to make it happen! Regards Cesar Lara ________________________________ From: "Miller, Frank" Sent: Friday, March 1, 2019 6:16 PM To: Little, Scott; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cutover to containers. Thank-you Scott. A couple of quick notes for the Community: · All ISOs will now be configured to use containerized services. · StarlingX is now using docker images built off OpenStack master for the OpenStack services. · Commits can now be merged again as per usual. Frank From: Scott Little [mailto:scott.little at windriver.com] Sent: Friday, March 01, 2019 2:54 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cutover to containers. All components have passed review and have been merged by Zuul. A CENGN build has been launched. Publication path for the iso will be http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ Containers will now be tagged dev-centos-master- or dev-centos-master-latest . Scott On 2019-03-01 1:09 p.m., Scott Little wrote: Stein has been merged back into master. Reviews are as follows... stx-manifest: https://review.openstack.org/640456 stx-clients: https://review.openstack.org/640459 stx-config: https://review.openstack.org/640464 stx-integ: https://review.openstack.org/640466 stx-nfv: https://review.openstack.org/640468 stx-upstream: https://review.openstack.org/640470 stx-gui: https://review.openstack.org/640472 stx-tools: https://review.openstack.org/640473 Scott On 2019-03-01 9:38 a.m., Scott Little wrote: The cutover to containers has been given the green light. I will be preforming the merge today. It would be helpful to not have any churn in the following repos... stx-clients, stx-config, stx-integ, stx-nfv, stx-upstream, stx-gui, stx-tools, stx-manifest. So please hold off on you WF+1 against those gits. Thank you Scott Little _______________________________________________ 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 serverascode at gmail.com Sat Mar 2 02:55:40 2019 From: serverascode at gmail.com (Curtis) Date: Fri, 1 Mar 2019 21:55:40 -0500 Subject: [Starlingx-discuss] StarlingX cutting over to containers In-Reply-To: References: Message-ID: On Thu, Feb 28, 2019 at 2:13 PM Miller, Frank wrote: > StarlingX Community: > > > > I am pleased on behalf of the entire containers subteam to announce that > the StarlingX project is ready to use containerized services. The subteam > has pulled together a ton of feature devlopment, integration, testing and > issue resolution to achieve stability in our four major configurations. > Sanities are passing on these configs in both a no proxy/no mirror > environment as well as in a proxy/mirror environment. Scott will be > merging the f/stein feature branch onto master Friday morning and all > builds after that point will only support a containers configuration > [1,2]. *We would ask that community members hold off merging commits > during the day on Friday. * > > > > There will be some expected limitations at this point in the project as > there are a number of planned stories still in progress and a number of > medium or lower priority LPs open. However, we are confident that we are > ready to get a wider use across the community. For more information on > containers including the recipe to bring up containers, current limitations > and an FAQ see: https://wiki.openstack.org/wiki/StarlingX/Containers > Thanks all! This is awesome to see. :) Thanks, Curtis > > > Frank > > Containers Project Lead > > > > [1] The config_controller script will now only support bringing up the > platform services in containers > > [2] the –kubernetes option for config_controller is being removed as the > script will only support a containers configuration as of Friday > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Sat Mar 2 03:38:25 2019 From: serverascode at gmail.com (Curtis) Date: Fri, 1 Mar 2019 22:38:25 -0500 Subject: [Starlingx-discuss] [StarlingX in a box] Community Feedback Required In-Reply-To: <38A5F0A7-4C20-436F-8B5F-D0AD64EB04D5@intel.com> References: <38A5F0A7-4C20-436F-8B5F-D0AD64EB04D5@intel.com> Message-ID: On Thu, Feb 28, 2019 at 1:01 PM Martinez Landa, Hayde < hayde.martinez.landa at intel.com> wrote: > Hi All, > > Guillermo and I are currently working on the StarlingX in a box project, > we are helding weekly meetings on Thursdays at 9:30 am PDT, > We’ll send an update with the Zoom link soon, if anyone is interested in > joining the efforts we welcome you. > > We’ve been doing some research and looking for different options, first of > all we were told to consider the python vbox installer > As part of this effort [0], but we want to bring to the table another > options. > > 1) Vagrant [1] - This tool has proven itself over time to provide > solutions for development environments easily and fast. > 2) GoVM [2]- This tool is young in comparison and it's currently under > development but so far has proven itself to be faster and more flexible > than vagrant. > > Vagrant: > Pros: > - Has been around for a long time > - It is well documented > - A lot of people is used to it > - Has a lot of provisioning plug-ins > - Flexible and easy. > Cons: > - It is not as fast as GoVM. > - It has a lot of overhead taking in count what we need > from it > - The ramp up is slower compare to GoVM. > GoVM: > Pros: > - It has a small footprint. > - It runs very fast (it is made on Go) > - The ramp up is faster. > - The main developers sits three desks from us (hehe (:) > - It has a "compose" like option > Cons: > - It is not well known yet > - The documentation is still lacking > - It does not have that many plug ins > - It is still under development (which can also be a pro > because it will get better) > > We also are considering to use Packer[3] to create the main images we are > going to work with. > Packer is a tool that is well integrated with vagrant since it is also > from hashicorp but GoVM can work with those images as well. > Right now we are having an issue with creating the base images from > starlingx ISO since the installation method is not standard and it requires > to create send an user and double password, We are working on solutions for > this, will keep you updated. > Overall, I'm not sure that STX should only generate an ISO image. From a high level I'm not sure of the model of the project generating an ISO and then other code using that singular ISO to generate other binary images. I'm especially thinking of potential future Zero Touch Provisioning (ZTP) work. I'm also wondering how this might relate, eventually or not, to devstack. I think this in a box concept is not a localized issue, that this is project wide, and has impact in other areas in terms of our ability to provide important installation and automation capabilities. The discussion area is probably larger than whether to use virtual box, vagrant, govm, or some other tool. So on one hand, getting the vbox code in is important (ie. quick dev environment), but we also have to balance that with future capabilities that to me, look very similar to providing support necessary to systems to get a quick dev environment. That's my $0.02. :) Thanks, Curtis > Please share your thoughts and comments, let us know if you need more > information or details on these, and also if you now another tool that > works well and can help us in this effort. > > [0] https://review.openstack.org/#/c/637958/ > [1] https://www.vagrantup.com/ > [2] https://github.com/govm-project/govm > [3] https://packer.io/ > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Sat Mar 2 08:45:30 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 2 Mar 2019 03:45:30 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 2 - Failure! Message-ID: <1011795844.39.1551516337517.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 2 Status: Failure Timestamp: 20190302T060000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190302T060000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false From build.starlingx at gmail.com Sun Mar 3 08:44:34 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 3 Mar 2019 03:44:34 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 3 - Still Failing! In-Reply-To: <1219645176.37.1551516326641.JavaMail.javamailuser@localhost> References: <1219645176.37.1551516326641.JavaMail.javamailuser@localhost> Message-ID: <1974826206.42.1551602676669.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 3 Status: Still Failing Timestamp: 20190303T060000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190303T060000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false From zhipengs.liu at intel.com Mon Mar 4 02:34:24 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Mon, 4 Mar 2019 02:34:24 +0000 Subject: [Starlingx-discuss] PCI Interrupt affinity task In-Reply-To: <8E5740EC88EF3E4BA3196F2545DC8625BA1D5543@ALA-MBD.corp.ad.wrs.com> References: <93814834B4855241994F290E959305C753042E86@SHSMSX104.ccr.corp.intel.com> <8E5740EC88EF3E4BA3196F2545DC8625BA1D5543@ALA-MBD.corp.ad.wrs.com> Message-ID: <93814834B4855241994F290E959305C753052590@SHSMSX104.ccr.corp.intel.com> Hi Jim and all, I have submitted all my patches for PCI Interrupt affinity feature as below link. https://review.openstack.org/#/c/640264/ https://review.openstack.org/#/c/640263/ Below one is the patch for removing pci-irq-affinity function from nova. https://github.com/hustlzp1981/stx-nova/commit/c52432b3e7a240817a2de06321a2459f4862ab6a Your comments are appreciated! Thanks! Zhipeng From: Gauld, James [mailto:James.Gauld at windriver.com] Sent: 2019年2月26日 22:07 To: Liu, ZhipengS ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] PCI Interrupt affinity task Zhipeng, Option 1) is a reasonable choice. I agree with your reasoning. FYI, I don’t think we depend on nova-sriov script anymore, but we haven't actually tested with that removed. Please add me to your code inspection. -Jim From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: February-21-19 10:24 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] PCI Interrupt affinity task Hi all Recently, I have being working on pci interrupt affinity task (https://storyboard.openstack.org/#!/story/2004600) So far I have finished coding, basic deployment test and function test. Now, I’m preparing for uploading my patch for code review. However, I need to decide where to put code folder. >From my point, there are two options below. 1) stx-integ/utilities/nova-utils/pci-affinity-agent 2) stx-config/sysinv/pci-affinity-agent (I put code here currently) I prefer option 1 as nova-utils is just used to install nova-sriov script only and pci affinity is also an extended feature for nova. We can reuse nova-utils package with additional RPM for pci-affinity-agent Any comment from you? Thanks! zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Mon Mar 4 07:58:32 2019 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Mon, 4 Mar 2019 07:58:32 +0000 Subject: [Starlingx-discuss] Cutover to containers. In-Reply-To: <7070a800-8afa-4ac7-8ddb-811c3f068ae3@intel.com> References: <2f7cc6b5-b864-1e0c-cebd-3e09964a6e68@windriver.com> , <7070a800-8afa-4ac7-8ddb-811c3f068ae3@intel.com> Message-ID: WOW ! this is realy a great step! So, we have a new stable version for starlingX!? Is there any way to upgrade the first stable version to stein without reinstall the complete stack? Greez & thx, Volker Von: Lara, Cesar [mailto:cesar.lara at intel.com] Gesendet: Samstag, 2. März 2019 01:19 An: Miller, Frank; Little, Scott; starlingx-discuss at lists.starlingx.io Betreff: Re: [Starlingx-discuss] Cutover to containers. This is definitely a great milestone, thank you all for the hard work to make it happen! Regards Cesar Lara ________________________________ From: "Miller, Frank" Sent: Friday, March 1, 2019 6:16 PM To: Little, Scott; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cutover to containers. Thank-you Scott. A couple of quick notes for the Community: * All ISOs will now be configured to use containerized services. * StarlingX is now using docker images built off OpenStack master for the OpenStack services. * Commits can now be merged again as per usual. Frank From: Scott Little [mailto:scott.little at windriver.com] Sent: Friday, March 01, 2019 2:54 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cutover to containers. All components have passed review and have been merged by Zuul. A CENGN build has been launched. Publication path for the iso will be http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ Containers will now be tagged dev-centos-master- or dev-centos-master-latest . Scott On 2019-03-01 1:09 p.m., Scott Little wrote: Stein has been merged back into master. Reviews are as follows... stx-manifest: https://review.openstack.org/640456 stx-clients: https://review.openstack.org/640459 stx-config: https://review.openstack.org/640464 stx-integ: https://review.openstack.org/640466 stx-nfv: https://review.openstack.org/640468 stx-upstream: https://review.openstack.org/640470 stx-gui: https://review.openstack.org/640472 stx-tools: https://review.openstack.org/640473 Scott On 2019-03-01 9:38 a.m., Scott Little wrote: The cutover to containers has been given the green light. I will be preforming the merge today. It would be helpful to not have any churn in the following repos... stx-clients, stx-config, stx-integ, stx-nfv, stx-upstream, stx-gui, stx-tools, stx-manifest. So please hold off on you WF+1 against those gits. Thank you Scott Little _______________________________________________ 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 build.starlingx at gmail.com Mon Mar 4 08:48:33 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 4 Mar 2019 03:48:33 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 4 - Still Failing! In-Reply-To: <854603264.40.1551602670044.JavaMail.javamailuser@localhost> References: <854603264.40.1551602670044.JavaMail.javamailuser@localhost> Message-ID: <1663139903.45.1551689314492.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 4 Status: Still Failing Timestamp: 20190304T060000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190304T060000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false From ildiko.vancsa at gmail.com Mon Mar 4 12:51:07 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Mon, 4 Mar 2019 13:51:07 +0100 Subject: [Starlingx-discuss] StarlingX activity metrics Message-ID: Hi StarlingX Community, As some of you already heard, the OSF staff has been working with Bitergia to provide a proof-of-concept dashboard of community activity metrics for StarlingX. This dashboard is now available at: https://starlingx.biterg.io/ It currently contains the default set of Bitergia dashboards, so you might find some panels more interesting than others. It tracks Git data, Gerrit activity, and mailing-list activity. We have the possibility to customize or add panels, so if you see some analysis or panel that would be specifically useful for StarlingX, let us know! Some identities are duplicated (especially across data sources as people don't use the same email address in for example git and the ML) -- although we did a pass at correcting those, there may be a few persisting. In the same vein, some affiliations may still be "unknown" -- we are trying to see if there would be a way for people to fix that data directly, rather than relying on a community manager to do so. Please also note that the database changes need some time to take effect on the dashboard. We'll run this proof-of-concept for a year, to confirm that the data is useful and accurate before we pursue this further. During this period, don't hesitate to report issues or start a discussion about features. The mailing-list is a good venue for that, until we set up a more formal issue reporting channel (Bitergia is using Gitlab). Thanks, Ildikó From Frank.Miller at windriver.com Mon Mar 4 13:44:44 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 4 Mar 2019 13:44:44 +0000 Subject: [Starlingx-discuss] Cutover to containers. In-Reply-To: References: <2f7cc6b5-b864-1e0c-cebd-3e09964a6e68@windriver.com> , <7070a800-8afa-4ac7-8ddb-811c3f068ae3@intel.com> Message-ID: Volker: In order to use any StarlingX load on the master branch a re-install is required. Frank From: von Hoesslin, Volker [mailto:Volker.Hoesslin at swsn.de] Sent: Monday, March 04, 2019 2:59 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cutover to containers. WOW ! this is realy a great step! So, we have a new stable version for starlingX!? Is there any way to upgrade the first stable version to stein without reinstall the complete stack? Greez & thx, Volker Von: Lara, Cesar [mailto:cesar.lara at intel.com] Gesendet: Samstag, 2. März 2019 01:19 An: Miller, Frank; Little, Scott; starlingx-discuss at lists.starlingx.io Betreff: Re: [Starlingx-discuss] Cutover to containers. This is definitely a great milestone, thank you all for the hard work to make it happen! Regards Cesar Lara ________________________________ From: "Miller, Frank" > Sent: Friday, March 1, 2019 6:16 PM To: Little, Scott; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cutover to containers. Thank-you Scott. A couple of quick notes for the Community: * All ISOs will now be configured to use containerized services. * StarlingX is now using docker images built off OpenStack master for the OpenStack services. * Commits can now be merged again as per usual. Frank From: Scott Little [mailto:scott.little at windriver.com] Sent: Friday, March 01, 2019 2:54 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cutover to containers. All components have passed review and have been merged by Zuul. A CENGN build has been launched. Publication path for the iso will be http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ Containers will now be tagged dev-centos-master- or dev-centos-master-latest . Scott On 2019-03-01 1:09 p.m., Scott Little wrote: Stein has been merged back into master. Reviews are as follows... stx-manifest: https://review.openstack.org/640456 stx-clients: https://review.openstack.org/640459 stx-config: https://review.openstack.org/640464 stx-integ: https://review.openstack.org/640466 stx-nfv: https://review.openstack.org/640468 stx-upstream: https://review.openstack.org/640470 stx-gui: https://review.openstack.org/640472 stx-tools: https://review.openstack.org/640473 Scott On 2019-03-01 9:38 a.m., Scott Little wrote: The cutover to containers has been given the green light. I will be preforming the merge today. It would be helpful to not have any churn in the following repos... stx-clients, stx-config, stx-integ, stx-nfv, stx-upstream, stx-gui, stx-tools, stx-manifest. So please hold off on you WF+1 against those gits. Thank you Scott Little _______________________________________________ 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 bruce.e.jones at intel.com Mon Mar 4 14:05:52 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 4 Mar 2019 14:05:52 +0000 Subject: [Starlingx-discuss] Cutover to containers. In-Reply-To: References: <2f7cc6b5-b864-1e0c-cebd-3e09964a6e68@windriver.com> , <7070a800-8afa-4ac7-8ddb-811c3f068ae3@intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BC3ADA3ED@fmsmsx121.amr.corp.intel.com> Our goal is to have a new stable version in May for the stx.2019.05 release. It's not upgradable from the previous stable build. We agreed at the recent community meeting in Arizona to make the November 2019 release upgradable from the May release. brucej From: von Hoesslin, Volker [mailto:Volker.Hoesslin at swsn.de] Sent: Sunday, March 3, 2019 11:59 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cutover to containers. WOW ! this is realy a great step! So, we have a new stable version for starlingX!? Is there any way to upgrade the first stable version to stein without reinstall the complete stack? Greez & thx, Volker Von: Lara, Cesar [mailto:cesar.lara at intel.com] Gesendet: Samstag, 2. März 2019 01:19 An: Miller, Frank; Little, Scott; starlingx-discuss at lists.starlingx.io Betreff: Re: [Starlingx-discuss] Cutover to containers. This is definitely a great milestone, thank you all for the hard work to make it happen! Regards Cesar Lara ________________________________ From: "Miller, Frank" > Sent: Friday, March 1, 2019 6:16 PM To: Little, Scott; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cutover to containers. Thank-you Scott. A couple of quick notes for the Community: * All ISOs will now be configured to use containerized services. * StarlingX is now using docker images built off OpenStack master for the OpenStack services. * Commits can now be merged again as per usual. Frank From: Scott Little [mailto:scott.little at windriver.com] Sent: Friday, March 01, 2019 2:54 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cutover to containers. All components have passed review and have been merged by Zuul. A CENGN build has been launched. Publication path for the iso will be http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ Containers will now be tagged dev-centos-master- or dev-centos-master-latest . Scott On 2019-03-01 1:09 p.m., Scott Little wrote: Stein has been merged back into master. Reviews are as follows... stx-manifest: https://review.openstack.org/640456 stx-clients: https://review.openstack.org/640459 stx-config: https://review.openstack.org/640464 stx-integ: https://review.openstack.org/640466 stx-nfv: https://review.openstack.org/640468 stx-upstream: https://review.openstack.org/640470 stx-gui: https://review.openstack.org/640472 stx-tools: https://review.openstack.org/640473 Scott On 2019-03-01 9:38 a.m., Scott Little wrote: The cutover to containers has been given the green light. I will be preforming the merge today. It would be helpful to not have any churn in the following repos... stx-clients, stx-config, stx-integ, stx-nfv, stx-upstream, stx-gui, stx-tools, stx-manifest. So please hold off on you WF+1 against those gits. Thank you Scott Little _______________________________________________ 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 bruce.e.jones at intel.com Mon Mar 4 16:45:38 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 4 Mar 2019 16:45:38 +0000 Subject: [Starlingx-discuss] Distro.openstack meeting agenda for Mar 5th Message-ID: <9A85D2917C58154C960D95352B22818BC3ADA502@fmsmsx121.amr.corp.intel.com> The agenda can be found at [0] please feel free to add issues or topics. * NUMA live migration update * Review open LPs [1] * Review upstreaming progress [2] [0] https://etherpad.openstack.org/p/stx-distro-openstack-meetings [1] https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack [2] https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit?ts=5c1933cc#gid=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Mon Mar 4 17:07:12 2019 From: scott.little at windriver.com (Scott Little) Date: Mon, 4 Mar 2019 12:07:12 -0500 Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 4 - Still Failing! In-Reply-To: <1663139903.45.1551689314492.JavaMail.javamailuser@localhost> References: <854603264.40.1551602670044.JavaMail.javamailuser@localhost> <1663139903.45.1551689314492.JavaMail.javamailuser@localhost> Message-ID: STX_build_master_master is the new daily build job for CENGN loads.  It replaces STX_build_master_pike.  i.e. it's content is  ...    stx branch: master    openstack branch: master Build #1 was a success. Build #2-4 failed when we tried to tie in the build of a second set of docker images based upon pike... as a stable fall back in case the master derived docker images are unstable. We'll put the pike images on hold while we sort out the issues. Scott On 2019-03-04 3:48 a.m., build.starlingx at gmail.com wrote: > Project: STX_build_master_master > Build #: 4 > Status: Still Failing > Timestamp: 20190304T060000Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190304T060000Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS: false > > _______________________________________________ > 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 vm.rod25 at gmail.com Mon Mar 4 17:14:04 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Mon, 4 Mar 2019 11:14:04 -0600 Subject: [Starlingx-discuss] Is there any plan of containerize the flock services ? In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB3F4676@ALA-MBD.corp.ad.wrs.com> References: <3E6E6B86-E9C2-4159-B3B4-9105C79700D5@windriver.com> <2588653EBDFFA34B982FAF00F1B4844EBB3F4676@ALA-MBD.corp.ad.wrs.com> Message-ID: On Fri, Mar 1, 2019 at 7:20 AM Rowsell, Brent wrote: > Hi Victor, > > See inline > > Brent > > -----Original Message----- > From: Victor Rodriguez [mailto:vm.rod25 at gmail.com] > Sent: Wednesday, February 27, 2019 12:00 PM > To: Rowsell, Brent > Cc: starlingx-discuss at lists.starlingx.io; Miller, Frank < > Frank.Miller at windriver.com> > Subject: Re: [Starlingx-discuss] Is there any plan of containerize the > flock services ? > > On Tue, Feb 26, 2019 at 8:14 PM Rowsell, Brent < > Brent.Rowsell at windriver.com> wrote: > > > > Hi Victor, > > > > For R2 only the openstack and some of it’s supporting services will be > containerized. > > > > A longer term objective is to containerize as much of the flock services > as possible. This is a candidate for the next release and will be > discussed as part of the R3 planning later this year. > > > > Brent > > > > Thanks a lot for your repply Brent > > I definitely support the approach of containers, now, one question, if the > goal is to containerize as much of the flock services as possible, can we > have the list of what services are not going to be on containers? based on > that we can minimize the efforts of packaging for Ubuntu and maybe help > more on the containerization of the flock services. The more we have in > containers the easier is for us to migrate to other OS ( the packages that > might need be ported to other OS might be: kernel, horizon, and keystone > right ? ) > [BR] Unfortunately I will not have that view of what can/will be > containerized until we start the R3 planning. > > Thanks a lot for the reply Brent, as discussed on the multiOS meeting we will focus for now on the build of one STX flock service in Ubuntu as preparation for the build of maybe more. During today containers meeting I heard that the only one that is a target for R2 is sxt fault , is that correct ? that was the one we were taking as POC to build, but if it is already targeted to be in a container we might choose a different one, Brent, Frank, which one do you recommend we take one, that we all be aware that we are working on? Regards Victor Rodriguez So far we have a POC of fm-manager and fm-common [1], what I don't want is > to spend time building debs that will not be useful in the future. > > Regards > > Victor Rodriguez > > [1] > https://github.com/marcelarosalesj/stx-packaging/commit/4bf237bf5f97e68b96a5be14a3e260467190e767 > > > > > Sent from my iPhone > > > > > On Feb 26, 2019, at 11:59 AM, Victor Rodriguez > wrote: > > > > > > Hi Frank and STX community > > > > > > Based on the presentation discuss during phoenix meeting last > > > January I had the impression that flock services were meant to be on > > > the host OS where the containers are running, is this still valid > > > for the long term? > > > > > > I am asking this because on today multi-OS meeting we present the > > > following architecture/plan: > > > > > > https://docs.google.com/presentation/d/1ck7vGH50AIAjUx9GNrIGtowG5qg7 > > > OYUBNdJyY-5ZvDc/edit?usp=sharing > > > > > > Where we are considering the task of build all the flock services on > > > Ubuntu, However, based on this task: > > > > > > https://storyboard.openstack.org/#!/story/2004008 > > > > > > Gives me the impression that there is a plan for reducing the number > > > of flock services running on the host OS, If that is the case, Could > > > you please share the list of what flock services that you have in > > > mind to put in a container? this will help us to reduce the list of > > > packages we need to build. > > > > > > On the same topic, for the none open stack packages like systemd, > > > bash or python, do you have the list of packages that need to run > > > outside the containers on the host OS? Having this exact list of > > > packages will help us to focus on the exact packages to build on > Ubuntu. > > > > > > Regards > > > > > > Victor Rodriguez > > > > > > _______________________________________________ > > > 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 Don.Penney at windriver.com Mon Mar 4 17:21:30 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Mon, 4 Mar 2019 17:21:30 +0000 Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 4 - Still Failing! In-Reply-To: References: <854603264.40.1551602670044.JavaMail.javamailuser@localhost> <1663139903.45.1551689314492.JavaMail.javamailuser@localhost> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA458EC4@ALA-MBD.corp.ad.wrs.com> There are two pending reviews related to the pike image build issue: stx-upstream: https://review.openstack.org/#/c/640571/ stx-root: https://review.openstack.org/#/c/640569/ From: Scott Little [mailto:scott.little at windriver.com] Sent: Monday, March 04, 2019 12:07 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 4 - Still Failing! STX_build_master_master is the new daily build job for CENGN loads. It replaces STX_build_master_pike. i.e. it's content is ... stx branch: master openstack branch: master Build #1 was a success. Build #2-4 failed when we tried to tie in the build of a second set of docker images based upon pike... as a stable fall back in case the master derived docker images are unstable. We'll put the pike images on hold while we sort out the issues. Scott On 2019-03-04 3:48 a.m., build.starlingx at gmail.com wrote: Project: STX_build_master_master Build #: 4 Status: Still Failing Timestamp: 20190304T060000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190304T060000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false _______________________________________________ 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 chenjie.xu at intel.com Fri Mar 1 14:55:13 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Fri, 1 Mar 2019 14:55:13 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Message-ID: Hi Joseph, I'm responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don't know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing "system host-unlock compute-0", it will report "Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address". But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng Cc: Martinez Monroy, Elio ; Zhao, Forrest ; Xie, Cindy ; Cabrales, Ada ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: BUG_system_host_port_list_pdevice.PNG Type: image/png Size: 40404 bytes Desc: BUG_system_host_port_list_pdevice.PNG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: enp4s0f1_ip.PNG Type: image/png Size: 33144 bytes Desc: enp4s0f1_ip.PNG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: vxlan-lack-ip-address.PNG Type: image/png Size: 47794 bytes Desc: vxlan-lack-ip-address.PNG URL: From Joseph.Richard at windriver.com Fri Mar 1 16:41:08 2019 From: Joseph.Richard at windriver.com (Richard, Joseph) Date: Fri, 1 Mar 2019 16:41:08 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: References: Message-ID: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I'm responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don't know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing "system host-unlock compute-0", it will report "Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address". But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng Cc: Martinez Monroy, Elio ; Zhao, Forrest ; Xie, Cindy ; Cabrales, Ada ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From chenjie.xu at intel.com Mon Mar 4 14:07:45 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Mon, 4 Mar 2019 14:07:45 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Joseph, Thank you for your reply! For now I'm trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie ; Khalil, Ghada ; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng ; Martinez Monroy, Elio ; Zhao, Forrest ; Xie, Cindy ; Cabrales, Ada ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I'm responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don't know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing "system host-unlock compute-0", it will report "Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address". But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Mon Mar 4 16:07:11 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 4 Mar 2019 16:07:11 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4C787E@ALA-MBD.corp.ad.wrs.com> Chenjie / Shuicheng, I suggest re-building the load to include the latest container support which was merged to master on Friday. This way the testing is done with the latest content, including the openstack stein images. Testing should be done using containers. Instructions/wiki links were sent previously by Frank Miller. Thanks, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Monday, March 04, 2019 10:39 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I'm trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I'm responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don't know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing "system host-unlock compute-0", it will report "Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address". But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From chenjie.xu at intel.com Mon Mar 4 15:38:44 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Mon, 4 Mar 2019 15:38:44 +0000 Subject: [Starlingx-discuss] FW: OVS-DPDK Upgrade Testing In-Reply-To: References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph ; Ghada.Khalil at windriver.com; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng ; Martinez Monroy, Elio ; Zhao, Forrest ; Xie, Cindy ; Cabrales, Ada ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I'm trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I'm responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don't know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing "system host-unlock compute-0", it will report "Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address". But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: controller.sysinv.log Type: application/octet-stream Size: 2920856 bytes Desc: controller.sysinv.log URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: compute-1.sysinv.log Type: application/octet-stream Size: 643961 bytes Desc: compute-1.sysinv.log URL: From bruce.e.jones at intel.com Mon Mar 4 21:39:12 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 4 Mar 2019 21:39:12 +0000 Subject: [Starlingx-discuss] New StarlingX meeting wiki content Message-ID: <9A85D2917C58154C960D95352B22818BC3ADA6ED@fmsmsx121.amr.corp.intel.com> I've just did a re-factoring on the meeting wiki page [0]. I've been frustrated by needing to scroll down to find the info on the meetings I want to attend, so I built a big table with everything right up front. I'm looking for feedback from the community on the updates. Thanks in advance! brucej [0] https://wiki.openstack.org/wiki/Starlingx/Meetings -------------- next part -------------- An HTML attachment was scrubbed... URL: From scottx.rifenbark at intel.com Mon Mar 4 21:46:38 2019 From: scottx.rifenbark at intel.com (Rifenbark, ScottX) Date: Mon, 4 Mar 2019 21:46:38 +0000 Subject: [Starlingx-discuss] New StarlingX meeting wiki content In-Reply-To: <9A85D2917C58154C960D95352B22818BC3ADA6ED@fmsmsx121.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BC3ADA6ED@fmsmsx121.amr.corp.intel.com> Message-ID: +1 - Useful table! From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Monday, March 4, 2019 1:39 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] New StarlingX meeting wiki content I've just did a re-factoring on the meeting wiki page [0]. I've been frustrated by needing to scroll down to find the info on the meetings I want to attend, so I built a big table with everything right up front. I'm looking for feedback from the community on the updates. Thanks in advance! brucej [0] https://wiki.openstack.org/wiki/Starlingx/Meetings -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Mon Mar 4 21:49:04 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Mon, 4 Mar 2019 21:49:04 +0000 Subject: [Starlingx-discuss] New StarlingX meeting wiki content In-Reply-To: References: <9A85D2917C58154C960D95352B22818BC3ADA6ED@fmsmsx121.amr.corp.intel.com> Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC0A13D06@ALA-MBD.corp.ad.wrs.com> Agreed : ) From: Rifenbark, ScottX Sent: Monday, March 4, 2019 4:47 PM To: Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] New StarlingX meeting wiki content +1 - Useful table! From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Monday, March 4, 2019 1:39 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] New StarlingX meeting wiki content I've just did a re-factoring on the meeting wiki page [0]. I've been frustrated by needing to scroll down to find the info on the meetings I want to attend, so I built a big table with everything right up front. I'm looking for feedback from the community on the updates. Thanks in advance! brucej [0] https://wiki.openstack.org/wiki/Starlingx/Meetings -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Mon Mar 4 21:49:52 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 4 Mar 2019 21:49:52 +0000 Subject: [Starlingx-discuss] Reviews for the Docs mega-spec Message-ID: <9A85D2917C58154C960D95352B22818BC3ADA773@fmsmsx121.amr.corp.intel.com> I'd like to close out the Docs mega spec review this week. Thank you to all of the reviewers. I believe I have addressed all of your comments. If I have not, please let me know. More reviews are welcome, of course. https://review.openstack.org/#/c/635641/ brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.hernandez.gonzalez at intel.com Mon Mar 4 21:59:59 2019 From: fernando.hernandez.gonzalez at intel.com (Hernandez Gonzalez, Fernando) Date: Mon, 4 Mar 2019 21:59:59 +0000 Subject: [Starlingx-discuss] New StarlingX meeting wiki content In-Reply-To: <9A85D2917C58154C960D95352B22818BC3ADA6ED@fmsmsx121.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BC3ADA6ED@fmsmsx121.amr.corp.intel.com> Message-ID: <03D458D5BAFF6041973594B00B4E58CE5D688D86@CRSMSX104.amr.corp.intel.com> Many Thanks Bruce, nice table we can see all meetings in just one glance :) Do not want to create any bias from the community but could we add Mexico and China International number in Zoom calling information section ? That would be great, Thanks! Fernando Hernandez Gonzalez Software Engineer Avenida del Bosque #1001 Col, El Bajío Zapopan, Jalisco MX, 45019 ____________________________________ Office: +52.33.16.45.01.34 inet 86450134 From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Monday, March 4, 2019 3:39 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] New StarlingX meeting wiki content I've just did a re-factoring on the meeting wiki page [0]. I've been frustrated by needing to scroll down to find the info on the meetings I want to attend, so I built a big table with everything right up front. I'm looking for feedback from the community on the updates. Thanks in advance! brucej [0] https://wiki.openstack.org/wiki/Starlingx/Meetings -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Mon Mar 4 22:03:41 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 4 Mar 2019 22:03:41 +0000 Subject: [Starlingx-discuss] New StarlingX meeting wiki content In-Reply-To: <03D458D5BAFF6041973594B00B4E58CE5D688D86@CRSMSX104.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BC3ADA6ED@fmsmsx121.amr.corp.intel.com> <03D458D5BAFF6041973594B00B4E58CE5D688D86@CRSMSX104.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BC3ADA7A4@fmsmsx121.amr.corp.intel.com> It's a wiki, Fernando :) - please edit as needed. Putting in the Mexico and China numbers makes perfect sense. brucej From: Hernandez Gonzalez, Fernando Sent: Monday, March 4, 2019 2:00 PM To: Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: RE: New StarlingX meeting wiki content Many Thanks Bruce, nice table we can see all meetings in just one glance :) Do not want to create any bias from the community but could we add Mexico and China International number in Zoom calling information section ? That would be great, Thanks! Fernando Hernandez Gonzalez Software Engineer Avenida del Bosque #1001 Col, El Bajío Zapopan, Jalisco MX, 45019 ____________________________________ Office: +52.33.16.45.01.34 inet 86450134 From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Monday, March 4, 2019 3:39 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] New StarlingX meeting wiki content I've just did a re-factoring on the meeting wiki page [0]. I've been frustrated by needing to scroll down to find the info on the meetings I want to attend, so I built a big table with everything right up front. I'm looking for feedback from the community on the updates. Thanks in advance! brucej [0] https://wiki.openstack.org/wiki/Starlingx/Meetings -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Mon Mar 4 22:06:23 2019 From: serverascode at gmail.com (Curtis) Date: Mon, 4 Mar 2019 17:06:23 -0500 Subject: [Starlingx-discuss] Reviews for the Docs mega-spec In-Reply-To: <9A85D2917C58154C960D95352B22818BC3ADA773@fmsmsx121.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BC3ADA773@fmsmsx121.amr.corp.intel.com> Message-ID: On Mon, Mar 4, 2019 at 4:50 PM Jones, Bruce E wrote: > I’d like to close out the Docs mega spec review this week. Thank you to > all of the reviewers. I believe I have addressed all of your comments. If > I have not, please let me know. More reviews are welcome, of course. > I still have a couple outstanding questions that were part of the reviews but are easy to miss. :) * Is multi-region a thing in STX? Will we be doing both distributed cloud and multi-region? There's a fairly long history of the term "multi-region" in openstack and I'm wondering if that is the same thing or not? * Can we point to upstream docs for things like provider networks? * Overall, if we did all this documentation, which is fairly aggressive in a good way, a lot of it would be valuable upstream. Does it make sense to try to work with openstack docs? I think it would be useful to get other people introduced to StarlingX and help to show how STX relates to OpenStack. The multi-region question is really more me trying to understand what the project is doing, ie. if we aren't actually doing both then we don't need to document both. Otherwise I like the direction and am happy to add my +2. Thanks for all your effort in this. :) Thanks, Curtis > > > https://review.openstack.org/#/c/635641/ > > > > brucej > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Mon Mar 4 22:22:01 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 4 Mar 2019 22:22:01 +0000 Subject: [Starlingx-discuss] Reviews for the Docs mega-spec In-Reply-To: References: <9A85D2917C58154C960D95352B22818BC3ADA773@fmsmsx121.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BC3ADA804@fmsmsx121.amr.corp.intel.com> * Is multi-region a thing in STX? Will we be doing both distributed cloud and multi-region? There's a fairly long history of the term "multi-region" in openstack and I'm wondering if that is the same thing or not? I’ve heard conflicting views from multiple folks on whether Multi-Region will be supported in the May release. Given that the work to implement the Mega-spec spans multiple releases, we could leave it in as a placeholder if the feature isn’t ready for May but will be in November. * Can we point to upstream docs for things like provider networks? Of course. My assumption was that such would be a level of detail for that document’s author to address. * Overall, if we did all this documentation, which is fairly aggressive in a good way, a lot of it would be valuable upstream. Does it make sense to try to work with openstack docs? We are already using the standard OpenStack docs tools and processes. Speaking just for me and not for the Docs team, I think it would make sense to collaborate more with them. brucej From: Curtis [mailto:serverascode at gmail.com] Sent: Monday, March 4, 2019 2:06 PM To: Jones, Bruce E Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Reviews for the Docs mega-spec On Mon, Mar 4, 2019 at 4:50 PM Jones, Bruce E > wrote: I’d like to close out the Docs mega spec review this week. Thank you to all of the reviewers. I believe I have addressed all of your comments. If I have not, please let me know. More reviews are welcome, of course. I still have a couple outstanding questions that were part of the reviews but are easy to miss. :) * Is multi-region a thing in STX? Will we be doing both distributed cloud and multi-region? There's a fairly long history of the term "multi-region" in openstack and I'm wondering if that is the same thing or not? * Can we point to upstream docs for things like provider networks? * Overall, if we did all this documentation, which is fairly aggressive in a good way, a lot of it would be valuable upstream. Does it make sense to try to work with openstack docs? I think it would be useful to get other people introduced to StarlingX and help to show how STX relates to OpenStack. The multi-region question is really more me trying to understand what the project is doing, ie. if we aren't actually doing both then we don't need to document both. Otherwise I like the direction and am happy to add my +2. Thanks for all your effort in this. :) Thanks, Curtis https://review.openstack.org/#/c/635641/ brucej _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From ada.cabrales at intel.com Tue Mar 5 00:14:37 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Tue, 5 Mar 2019 00:14:37 +0000 Subject: [Starlingx-discuss] [ Testing ] Meeting agenda - 03/05/2019 Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CD83567@FMSMSX112.amr.corp.intel.com> Agenda for 03/05/2019 1. Plan progress check - 30 min Regression suite submissions to the repo Distro.OpenStack patch elimination - progress on testing plan definition OVS-DPDK upgrade Test cases automation Stress and stability Performance 2. Dashboard follow-up - 15 min 3. Opens - 15 min Regards Ada From huifeng.le at intel.com Tue Mar 5 02:26:03 2019 From: huifeng.le at intel.com (Le, Huifeng) Date: Tue, 5 Mar 2019 02:26:03 +0000 Subject: [Starlingx-discuss] [Neutron] Question on uwsgi based web server support for neutron Message-ID: <76647BD697F40748B1FA4F56DA02AA0B4D595BCF@SHSMSX104.ccr.corp.intel.com> Miguel, During STX deployment process, it is found the current neutron eventlet based web server has some unexpected behavior for multiple long live clients and it is also verified that apache WSGI/uwsgi based web server can solve such issues. the detail information of this issue can be found at https://bugs.launchpad.net/neutron/+bug/1800599. So is there any plan or roadmap to switch to the new apache WSGI/uswgi based web server for Neutron in Stein release? Thanks much! Best Regards, Le, Huifeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Tue Mar 5 02:41:07 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Tue, 5 Mar 2019 02:41:07 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190304 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9F38B@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Mar-04 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment Simplex Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 02 TCs [PASS] TOTAL: [ 55 TCs PASS ] Duplex Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform In Development TOTAL: [ 53 TCs PASS ] Standard Local Storage (2+2) Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform In Development TOTAL: [ 52 TCs PASS ] =========================================== Sanity Test is executed in a Containers - Virtual Environment Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 02 TCs [PASS] TOTAL: [ 59 TCs PASS ] Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform In Development TOTAL: [ 57 TCs PASS ] ------------------------------------------------------------------ This is the list of test cases executed: https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From huifeng.le at intel.com Tue Mar 5 07:37:09 2019 From: huifeng.le at intel.com (Le, Huifeng) Date: Tue, 5 Mar 2019 07:37:09 +0000 Subject: [Starlingx-discuss] [Neutron] Question on uwsgi based web server support for neutron In-Reply-To: <7B5D39C4-7B28-488F-A731-0831D0B44F7C@redhat.com> References: <76647BD697F40748B1FA4F56DA02AA0B4D595BCF@SHSMSX104.ccr.corp.intel.com> <7B5D39C4-7B28-488F-A731-0831D0B44F7C@redhat.com> Message-ID: <76647BD697F40748B1FA4F56DA02AA0B4D595D05@SHSMSX104.ccr.corp.intel.com> Slawek, Thanks much for the information. Yes, it is already possible to configure using uswgi for neutron API which is also the way I used to verify the issue. So will it be used as default configuration (as other openstack projects) for neutron in any planned release? or it supposed to require the system admin to apply this configuration manually when deployment? thanks much! Best Regards, Le, Huifeng -----Original Message----- From: Slawomir Kaplonski [mailto:skaplons at redhat.com] Sent: Tuesday, March 5, 2019 3:20 PM To: Le, Huifeng Cc: Miguel Lavalle ; Khalil, Ghada ; starlingx-discuss at lists.starlingx.io; openstack-dev at lists.openstack.org Subject: Re: [Neutron] Question on uwsgi based web server support for neutron Hi, > Wiadomość napisana przez Le, Huifeng w dniu 05.03.2019, o godz. 03:26: > > Miguel, > > During STX deployment process, it is found the current neutron eventlet based web server has some unexpected behavior for multiple long live clients and it is also verified that apache WSGI/uwsgi based web server can solve such issues. the detail information of this issue can be found at https://bugs.launchpad.net/neutron/+bug/1800599. > > So is there any plan or roadmap to switch to the new apache WSGI/uswgi based web server for Neutron in Stein release? Thanks much! AFAIK it is already possible since Rocky https://docs.openstack.org/neutron/rocky/admin/config-wsgi.html Is it what You are asking for? > > Best Regards, > Le, Huifeng — Slawek Kaplonski Senior software engineer Red Hat From Greg.Waines at windriver.com Tue Mar 5 12:29:52 2019 From: Greg.Waines at windriver.com (Waines, Greg) Date: Tue, 5 Mar 2019 12:29:52 +0000 Subject: [Starlingx-discuss] Reviews for the Docs mega-spec In-Reply-To: <9A85D2917C58154C960D95352B22818BC3ADA804@fmsmsx121.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BC3ADA773@fmsmsx121.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BC3ADA804@fmsmsx121.amr.corp.intel.com> Message-ID: <3B53AA14-141D-407D-BF5D-7F5032CA34E2@windriver.com> See comments in-lined below, Greg. From: "Jones, Bruce E" Date: Monday, March 4, 2019 at 5:23 PM To: Curtis Cc: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Reviews for the Docs mega-spec * Is multi-region a thing in STX? Will we be doing both distributed cloud and multi-region? There's a fairly long history of the term "multi-region" in openstack and I'm wondering if that is the same thing or not? I’ve heard conflicting views from multiple folks on whether Multi-Region will be supported in the May release. Given that the work to implement the Mega-spec spans multiple releases, we could leave it in as a placeholder if the feature isn’t ready for May but will be in November. [Greg] yeah ... still TBD whether we continue to support Multi-Region in STX ... it has not had a lot of uptake. It still makes sense as a possible scenario ... i.e. a Primary Region and multiple Secondary Regions sharing some services of the Primary. It addresses some of the Controller Services scalability issues in OpenStack. * Can we point to upstream docs for things like provider networks? Of course. My assumption was that such would be a level of detail for that document’s author to address. [Greg] Yeah ... we’ll point upstream where we can ... but provider networks are not fully modelled in Neutron. We tried to upstream this to Neutron but it was turned down. So the high level modelling of the configuration of the provider networks themselves was moved to STX as part of the infrastructure. * Overall, if we did all this documentation, which is fairly aggressive in a good way, a lot of it would be valuable upstream. Does it make sense to try to work with openstack docs? We are already using the standard OpenStack docs tools and processes. Speaking just for me and not for the Docs team, I think it would make sense to collaborate more with them. [Greg] yeah not sure I understand your comment Curtis, this is upstream openstack documentation. Greg. brucej From: Curtis [mailto:serverascode at gmail.com] Sent: Monday, March 4, 2019 2:06 PM To: Jones, Bruce E Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Reviews for the Docs mega-spec On Mon, Mar 4, 2019 at 4:50 PM Jones, Bruce E > wrote: I’d like to close out the Docs mega spec review this week. Thank you to all of the reviewers. I believe I have addressed all of your comments. If I have not, please let me know. More reviews are welcome, of course. I still have a couple outstanding questions that were part of the reviews but are easy to miss. :) * Is multi-region a thing in STX? Will we be doing both distributed cloud and multi-region? There's a fairly long history of the term "multi-region" in openstack and I'm wondering if that is the same thing or not? * Can we point to upstream docs for things like provider networks? * Overall, if we did all this documentation, which is fairly aggressive in a good way, a lot of it would be valuable upstream. Does it make sense to try to work with openstack docs? I think it would be useful to get other people introduced to StarlingX and help to show how STX relates to OpenStack. The multi-region question is really more me trying to understand what the project is doing, ie. if we aren't actually doing both then we don't need to document both. Otherwise I like the direction and am happy to add my +2. Thanks for all your effort in this. :) Thanks, Curtis https://review.openstack.org/#/c/635641/ brucej _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Tue Mar 5 13:29:35 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 5 Mar 2019 13:29:35 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack Distro meeting, 3/6 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35EB8058@SHSMSX104.ccr.corp.intel.com> Agenda for 3/6 meeting: 1. Ceph upgrade status (Ovidiu/Daniel, Changcheng/Tingjie) 2. CentOS 7.6 feature branch merge to master readiness review (Shuicheng) 3. DevStack update (Dean/Yi) 4. Opens (all) -----Original Appointment----- From: Xie, Cindy Sent: Monday, November 5, 2018 2:27 PM To: Xie, Cindy; Troyer, Dean; Zhu, Vivian; Hu, Yong; Lin, Shuicheng; Shang, Dehao; Somerville, Jim; Wold, Saul; Sun, Austin; Jones, Bruce E; Liu, ZhipengS; 'Rowsell, Brent'; 'Khalil, Ghada'; starlingx-discuss at lists.starlingx.io; Waheed, Numan Cc: Perez Carranza, Jose; 'Hellmann, Gil'; 'Seiler, Glenn'; 'Young, Ken'; Arce Moreno, Abraham; Cobbley, David A; Fang, Liang A; 'Eslimi, Dariush'; Hu, Wei W; Martinez Monroy, Elio; 'Waines, Greg'; Lara, Cesar; Armstrong, Robert H; 'Chen, Jacky'; Martinez Landa, Hayde; 'Poncea, Ovidiu'; Perez Rodriguez, Humberto I; Gomez, Juan P; Shuquan Huang Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, March 6, 2019 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 serverascode at gmail.com Tue Mar 5 13:44:42 2019 From: serverascode at gmail.com (Curtis) Date: Tue, 5 Mar 2019 08:44:42 -0500 Subject: [Starlingx-discuss] Reviews for the Docs mega-spec In-Reply-To: <3B53AA14-141D-407D-BF5D-7F5032CA34E2@windriver.com> References: <9A85D2917C58154C960D95352B22818BC3ADA773@fmsmsx121.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BC3ADA804@fmsmsx121.amr.corp.intel.com> <3B53AA14-141D-407D-BF5D-7F5032CA34E2@windriver.com> Message-ID: On Tue, Mar 5, 2019 at 7:30 AM Waines, Greg wrote: > See comments in-lined below, > > Greg. > > > > *From: *"Jones, Bruce E" > *Date: *Monday, March 4, 2019 at 5:23 PM > *To: *Curtis > *Cc: *"starlingx-discuss at lists.starlingx.io" < > starlingx-discuss at lists.starlingx.io> > *Subject: *Re: [Starlingx-discuss] Reviews for the Docs mega-spec > > > > * Is multi-region a thing in STX? Will we be doing both distributed cloud > and multi-region? There's a fairly long history of the term "multi-region" > in openstack and I'm wondering if that is the same thing or not? > > > > I’ve heard conflicting views from multiple folks on whether Multi-Region > will be supported in the May release. Given that the work to implement the > Mega-spec spans multiple releases, we could leave it in as a placeholder if > the feature isn’t ready for May but will be in November. > > > > [Greg] yeah ... still TBD whether we continue to support Multi-Region in > STX ... it has not had a lot of uptake. > > It still makes sense as a possible scenario ... i.e. a Primary Region and > multiple Secondary Regions sharing some services of the Primary. > > It addresses some of the Controller Services scalability issues in > OpenStack. > > > > * Can we point to upstream docs for things like provider networks? > > > > Of course. My assumption was that such would be a level of detail for > that document’s author to address. > > [Greg] > > Yeah ... we’ll point upstream where we can ... but provider networks are > not fully modelled in Neutron. We tried to upstream this to Neutron but it > was turned down. So the high level modelling of the configuration of the > provider networks themselves was moved to STX as part of the infrastructure. > > > > * Overall, if we did all this documentation, which is fairly aggressive in > a good way, a lot of it would be valuable upstream. Does it make sense to > try to work with openstack docs? > > > > We are already using the standard OpenStack docs tools and processes. > Speaking just for me and not for the Docs team, I think it would make sense > to collaborate more with them. > > > > [Greg] yeah not sure I understand your comment Curtis, this is upstream > openstack documentation. > > Greg. > Ok, say you document multi-region architecture and do a great job at it, so it describes how multi-region works in openstack whether it's stx or not...where does that document live? In stx docs or openstack docs? Thanks, Curtis > > > brucej > > > > *From:* Curtis [mailto:serverascode at gmail.com] > *Sent:* Monday, March 4, 2019 2:06 PM > *To:* Jones, Bruce E > *Cc:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] Reviews for the Docs mega-spec > > > > > > > > On Mon, Mar 4, 2019 at 4:50 PM Jones, Bruce E > wrote: > > I’d like to close out the Docs mega spec review this week. Thank you to > all of the reviewers. I believe I have addressed all of your comments. If > I have not, please let me know. More reviews are welcome, of course. > > > > I still have a couple outstanding questions that were part of the reviews > but are easy to miss. :) > > > > * Is multi-region a thing in STX? Will we be doing both distributed cloud > and multi-region? There's a fairly long history of the term "multi-region" > in openstack and I'm wondering if that is the same thing or not? > > * Can we point to upstream docs for things like provider networks? > > * Overall, if we did all this documentation, which is fairly aggressive in > a good way, a lot of it would be valuable upstream. Does it make sense to > try to work with openstack docs? I think it would be useful to get other > people introduced to StarlingX and help to show how STX relates to > OpenStack. > > > > The multi-region question is really more me trying to understand what the > project is doing, ie. if we aren't actually doing both then we don't need > to document both. > > > > Otherwise I like the direction and am happy to add my +2. Thanks for all > your effort in this. :) > > > > Thanks, > > Curtis > > > > > > > > https://review.openstack.org/#/c/635641/ > > > > brucej > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > -- > > Blog: serverascode.com > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Tue Mar 5 13:59:37 2019 From: Greg.Waines at windriver.com (Waines, Greg) Date: Tue, 5 Mar 2019 13:59:37 +0000 Subject: [Starlingx-discuss] Reviews for the Docs mega-spec In-Reply-To: References: <9A85D2917C58154C960D95352B22818BC3ADA773@fmsmsx121.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BC3ADA804@fmsmsx121.amr.corp.intel.com> <3B53AA14-141D-407D-BF5D-7F5032CA34E2@windriver.com> Message-ID: <9CDC5FC4-547E-4EAB-97C7-D47410244F3A@windriver.com> * Overall, if we did all this documentation, which is fairly aggressive in a good way, a lot of it would be valuable upstream. Does it make sense to try to work with openstack docs? We are already using the standard OpenStack docs tools and processes. Speaking just for me and not for the Docs team, I think it would make sense to collaborate more with them. [Greg] yeah not sure I understand your comment Curtis, this is upstream openstack documentation. Greg. Ok, say you document multi-region architecture and do a great job at it, so it describes how multi-region works in openstack whether it's stx or not...where does that document live? In stx docs or openstack docs? Thanks, Curtis The STX document would focus on how options/parameters within the STX Installation scripts (e.g. config-controller, config-region, ... and ansible playbook in the future) are used to setup an OpenStack Multi-Region environment with StarlingX ... and would refer to upstream openstack documentation for the description of what OpenStack Multi-Region is in general. Greg. -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Tue Mar 5 14:30:24 2019 From: serverascode at gmail.com (Curtis) Date: Tue, 5 Mar 2019 09:30:24 -0500 Subject: [Starlingx-discuss] Reviews for the Docs mega-spec In-Reply-To: <9CDC5FC4-547E-4EAB-97C7-D47410244F3A@windriver.com> References: <9A85D2917C58154C960D95352B22818BC3ADA773@fmsmsx121.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BC3ADA804@fmsmsx121.amr.corp.intel.com> <3B53AA14-141D-407D-BF5D-7F5032CA34E2@windriver.com> <9CDC5FC4-547E-4EAB-97C7-D47410244F3A@windriver.com> Message-ID: On Tue, Mar 5, 2019 at 9:00 AM Waines, Greg wrote: > > > * Overall, if we did all this documentation, which is fairly aggressive in > a good way, a lot of it would be valuable upstream. Does it make sense to > try to work with openstack docs? > > > > We are already using the standard OpenStack docs tools and processes. > Speaking just for me and not for the Docs team, I think it would make sense > to collaborate more with them. > > > > [Greg] yeah not sure I understand your comment Curtis, this is upstream > openstack documentation. > > Greg. > > > > Ok, say you document multi-region architecture and do a great job at it, > so it describes how multi-region works in openstack whether it's stx or > not...where does that document live? In stx docs or openstack docs? > > > > Thanks, > > Curtis > > > > > > The STX document would focus on how options/parameters within the STX > Installation scripts (e.g. config-controller, config-region, ... and > ansible playbook in the future) are used to setup an OpenStack Multi-Region > environment with StarlingX ... and would refer to upstream openstack > documentation for the description of what OpenStack Multi-Region is in > general. > Ok, now show me the upstream openstack documentation for multi-region. :) I'm having a hard time finding it right now. Doesn't mean it's not there, I just can't find it in a quick search. All I'm saying is that if we actually documented everything in the spec, that would be a lot of useful architecture docs that may very well not exist upstream at this time. There used to be some architecture guides, I think there is still an HA guide, but I'm sure that there are areas that could be improved. And if stx helps to improve those docs, then it would help people outside of the stx project to understand what stx is. Thanks, Curtis > > > Greg. > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Tue Mar 5 15:29:41 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 5 Mar 2019 15:29:41 +0000 Subject: [Starlingx-discuss] Mar 5th 2019 Distro.openstack meeting Message-ID: <9A85D2917C58154C960D95352B22818BD06EECEB@fmsmsx123.amr.corp.intel.com> Overall plan and status tracking document: https://etherpad.openstack.org/p/stx-openstack-patch-refactoring * Details: https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit?usp=sharing Meeting agenda and notes for the 3/5 meeting * NUMA aware live migration work is pushing to Train. See Artom's latest update https://review.openstack.org/#/c/635669/ * Suggest that we plan to backport the patches from Train to stx.2019.05 once they merge. * We reviewed several different options for handling this situation: ? Wait for Train - unsatisfying, least effort ? Carry forks (patches not necessarily accepted upstream) * Implement our own patches - expensive, deterministic, leads to new forks * Pull from upstream patch submissions - less expensive, risky, less perception of forks ? Backport from Train to Stein (once the patches get accepted) - less expensive, some risk, less deterministic ? Nova community doesn't merge things that aren't' deployable or complete ? We postponed decisions as to which options to apply to which patches - hopefully more will go in. * Review LP issues: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack * AR Frank to review the issues with his team and update as needed * Review upstream updates: https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit?ts=5c1933cc#gid=0 * AR Bruce to ping Yong Li re: line item 7 "Clean up orphan instances" * AR Yong Li to ask for an exception for line item 9 "NUMA Topology API" * AR Frank re: line item 30 "RPC timeout handling" please have this re-tested * AR Bruce to ping Yan re: line item 34 "CSRF AngularJS Fixes" -------------- next part -------------- An HTML attachment was scrubbed... URL: From skaplons at redhat.com Tue Mar 5 07:20:08 2019 From: skaplons at redhat.com (Slawomir Kaplonski) Date: Tue, 5 Mar 2019 08:20:08 +0100 Subject: [Starlingx-discuss] [Neutron] Question on uwsgi based web server support for neutron In-Reply-To: <76647BD697F40748B1FA4F56DA02AA0B4D595BCF@SHSMSX104.ccr.corp.intel.com> References: <76647BD697F40748B1FA4F56DA02AA0B4D595BCF@SHSMSX104.ccr.corp.intel.com> Message-ID: <7B5D39C4-7B28-488F-A731-0831D0B44F7C@redhat.com> Hi, > Wiadomość napisana przez Le, Huifeng w dniu 05.03.2019, o godz. 03:26: > > Miguel, > > During STX deployment process, it is found the current neutron eventlet based web server has some unexpected behavior for multiple long live clients and it is also verified that apache WSGI/uwsgi based web server can solve such issues. the detail information of this issue can be found at https://bugs.launchpad.net/neutron/+bug/1800599. > > So is there any plan or roadmap to switch to the new apache WSGI/uswgi based web server for Neutron in Stein release? Thanks much! AFAIK it is already possible since Rocky https://docs.openstack.org/neutron/rocky/admin/config-wsgi.html Is it what You are asking for? > > Best Regards, > Le, Huifeng — Slawek Kaplonski Senior software engineer Red Hat From skaplons at redhat.com Tue Mar 5 07:53:12 2019 From: skaplons at redhat.com (Slawomir Kaplonski) Date: Tue, 5 Mar 2019 08:53:12 +0100 Subject: [Starlingx-discuss] [Neutron] Question on uwsgi based web server support for neutron In-Reply-To: <76647BD697F40748B1FA4F56DA02AA0B4D595D05@SHSMSX104.ccr.corp.intel.com> References: <76647BD697F40748B1FA4F56DA02AA0B4D595BCF@SHSMSX104.ccr.corp.intel.com> <7B5D39C4-7B28-488F-A731-0831D0B44F7C@redhat.com> <76647BD697F40748B1FA4F56DA02AA0B4D595D05@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi, I don’t know about any plans to make it default now in Stein. IMO We can think about it in Train cycle. > Wiadomość napisana przez Le, Huifeng w dniu 05.03.2019, o godz. 08:37: > > Slawek, > > Thanks much for the information. Yes, it is already possible to configure using uswgi for neutron API which is also the way I used to verify the issue. > > So will it be used as default configuration (as other openstack projects) for neutron in any planned release? or it supposed to require the system admin to apply this configuration manually when deployment? thanks much! > > Best Regards, > Le, Huifeng > > -----Original Message----- > From: Slawomir Kaplonski [mailto:skaplons at redhat.com] > Sent: Tuesday, March 5, 2019 3:20 PM > To: Le, Huifeng > Cc: Miguel Lavalle ; Khalil, Ghada ; starlingx-discuss at lists.starlingx.io; openstack-dev at lists.openstack.org > Subject: Re: [Neutron] Question on uwsgi based web server support for neutron > > Hi, > >> Wiadomość napisana przez Le, Huifeng w dniu 05.03.2019, o godz. 03:26: >> >> Miguel, >> >> During STX deployment process, it is found the current neutron eventlet based web server has some unexpected behavior for multiple long live clients and it is also verified that apache WSGI/uwsgi based web server can solve such issues. the detail information of this issue can be found at https://bugs.launchpad.net/neutron/+bug/1800599. >> >> So is there any plan or roadmap to switch to the new apache WSGI/uswgi based web server for Neutron in Stein release? Thanks much! > > AFAIK it is already possible since Rocky https://docs.openstack.org/neutron/rocky/admin/config-wsgi.html > Is it what You are asking for? > >> >> Best Regards, >> Le, Huifeng > > — > Slawek Kaplonski > Senior software engineer > Red Hat > — Slawek Kaplonski Senior software engineer Red Hat From chenjie.xu at intel.com Tue Mar 5 13:53:47 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Tue, 5 Mar 2019 13:53:47 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Joseph, About the configuration of QOS, I don't know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' ; 'Ghada.Khalil at windriver.com' ; 'Peters, Matt' Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng ; Martinez Monroy, Elio ; Zhao, Forrest ; Xie, Cindy ; Cabrales, Ada ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I'm trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I'm responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don't know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing "system host-unlock compute-0", it will report "Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address". But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From smooney at redhat.com Tue Mar 5 14:52:01 2019 From: smooney at redhat.com (Sean Mooney) Date: Tue, 05 Mar 2019 14:52:01 +0000 Subject: [Starlingx-discuss] [Neutron] Question on uwsgi based web server support for neutron In-Reply-To: References: <76647BD697F40748B1FA4F56DA02AA0B4D595BCF@SHSMSX104.ccr.corp.intel.com> <7B5D39C4-7B28-488F-A731-0831D0B44F7C@redhat.com> <76647BD697F40748B1FA4F56DA02AA0B4D595D05@SHSMSX104.ccr.corp.intel.com> Message-ID: On Tue, 2019-03-05 at 08:53 +0100, Slawomir Kaplonski wrote: > Hi, > > I don’t know about any plans to make it default now in Stein. IMO We can think about it in Train cycle. for what its worth i dont think project actully have default in repect to eventlets vs wsgi it really the installer that do have default. keystone i think is the only project that "defults" to wsgi and that is because they delete the eventlet version if i am not miss remembering. that said i do think that more project should consider moving to wsgi only. eventually i would hope we could drop all eventlet depencies in openstack but i know that for several of the agents like the nova agent that is hard to do. for the apis however wsgi provided a convent way to drop that depency and improve performance at the same time. > > > Wiadomość napisana przez Le, Huifeng w dniu 05.03.2019, o godz. 08:37: > > > > Slawek, > > > > Thanks much for the information. Yes, it is already possible to configure using uswgi for neutron API which is also > > the way I used to verify the issue. > > > > So will it be used as default configuration (as other openstack projects) for neutron in any planned release? or it > > supposed to require the system admin to apply this configuration manually when deployment? thanks much! > > > > Best Regards, > > Le, Huifeng > > > > -----Original Message----- > > From: Slawomir Kaplonski [mailto:skaplons at redhat.com] > > Sent: Tuesday, March 5, 2019 3:20 PM > > To: Le, Huifeng > > Cc: Miguel Lavalle ; Khalil, Ghada ; > > starlingx-discuss at lists.starlingx.io; openstack-dev at lists.openstack.org > > Subject: Re: [Neutron] Question on uwsgi based web server support for neutron > > > > Hi, > > > > > Wiadomość napisana przez Le, Huifeng w dniu 05.03.2019, o godz. 03:26: > > > > > > Miguel, > > > > > > During STX deployment process, it is found the current neutron eventlet based web server has some unexpected > > > behavior for multiple long live clients and it is also verified that apache WSGI/uwsgi based web server can solve > > > such issues. the detail information of this issue can be found at https://bugs.launchpad.net/neutron/+bug/1800599. > > > > > > > > > So is there any plan or roadmap to switch to the new apache WSGI/uswgi based web server for Neutron in Stein > > > release? Thanks much! > > > > AFAIK it is already possible since Rocky https://docs.openstack.org/neutron/rocky/admin/config-wsgi.html > > Is it what You are asking for? > > > > > > > > Best Regards, > > > Le, Huifeng > > > > — > > Slawek Kaplonski > > Senior software engineer > > Red Hat > > > > — > Slawek Kaplonski > Senior software engineer > Red Hat > > From Ghada.Khalil at windriver.com Tue Mar 5 16:06:59 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 5 Mar 2019 16:06:59 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> Hi Chenjie, I spoke with Joseph. We don't believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don't know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I'm trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I'm responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don't know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing "system host-unlock compute-0", it will report "Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address". But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From ada.cabrales at intel.com Wed Mar 6 01:12:26 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Wed, 6 Mar 2019 01:12:26 +0000 Subject: [Starlingx-discuss] [ Testing ] Meeting notes - 03/05/2019 Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CD907D4@FMSMSX112.amr.corp.intel.com> Notes from 03/05/2019 Attendees: Elio, Abraham, JC, JP, Numan, Victor, Ada, Jose, Bruce, Bill, Fer 1. Plan progress check - 30 min Regression suite submissions to the repo First upload is the storage test plan - Ada to help with reviewing. The rest of the tests are ready. Will be submitted during this week. Add Maria Y and Numan for reviewers on the intel's submission. Some struggle happening with the format and rst, but that's fixed. Thank you Abraham for your help on submitting the test cases using the template. There's a team that can help with the translation to rst format. There's a meeting tomorrow with the team that is doing this. Abraham to send meeting information to Numan. Contractors helping on checking the networking test cases for accuracy. Heat, Horizon and Security submissions in progress. Gnocchi tests submitted. Simplex in progress. System inventory ready for translation. System test are select, working on content. Distro.OpenStack patch elimination - progress on testing plan definition Taking this plan as a base - https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit#gid=0 Jose - working on Horizon - New test cases must be developed for covering this. Cinder glance - some coverage already there, but new tests must be created too. For the nova side, Numan will double check for coverage, but almost sure all is in the test cases to be submitted. Containerized Openstack services - Sanity running in four configs using containers. Checking different services that are running within containers. Updating the automated suite that checks for the services. Numan to check on duplex direct config coverage Cristopher to install a duplex-direct Successfull installs of 4 configs in virtual, using proxy. Also local mirror working, with one workaroud. OVS-DPDK upgrade Test cases are defined. IPv6 is not tested now, because feature is not ready. Covering bare metal and virtual. Waiting for the upgrade to be included into a containers build. Working also on QoS. Test cases automation - Elio Automation team will begin with networking - progress to be provided weekly. Send the list of test cases to be automated to Numan. Stress and stability Stress run launched yesterday on simplex and 2+2 - creation and launch of instances went ok, but when trying to make operations with instances, they failed. Looks like the rabbitmq is the one with problem: launchpads already opened. JC to upload our findings into the launchpad for the simplex config. Performance No update - struggling with resources. Setup not tried yet. Abraham to sync with Victor to see how can he contribute. 2. Dashboard follow-up - 15 min Cristopher sent the requirements for hosting the dashboard to Ken, Numan and Ada. Numan to ask Ken to request this to CENGN. 3. Opens - 15 min Elio - work with Cristopher to have the duplex direct up and running. Numan - include the tests running in the sanity link included in the email started yesterday. Expand that to see which tests are passing/failing. When the test cases already existing would be adjusted to containers? - Elio to work on estimating a date. Ada to be on vacations next Tuesday - Numan to run the meeting. Cindy asked Numan and Ada to run the ceph upgrade testing in parallel. Let's clarify about commitment in the email. Bill - Ada to update the release verification plan. Fer - SDL progress - security lead reviewing results to work on closure. From juan.carlos.alonso at intel.com Wed Mar 6 02:27:39 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Wed, 6 Mar 2019 02:27:39 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190305 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9F6E5@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Mar-05 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment Simplex Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 02 TCs [PASS] TOTAL: [ 55 TCs PASS ] Duplex Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform In Development TOTAL: [ 53 TCs PASS ] =========================================== Sanity Test is executed in a Containers - Virtual Environment Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 02 TCs [PASS] TOTAL: [ 59 TCs PASS ] ------------------------------------------------------------------ Some configurations faced problems with the provisioning due to an existing issue related to "rabbitmq" service pod: https://bugs.launchpad.net/starlingx/+bug/1815541 The same issue affected the Stress execution. Seems that "rabbitmq" pod had issue to manage signals when there is a big load. ------------------------------------------------------------------ This is the list of test cases executed: https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests ------------------------------------------------------------------ Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Wed Mar 6 06:07:22 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 6 Mar 2019 01:07:22 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_download_mirror - Build # 196 - Failure! Message-ID: <1976513374.49.1551852443232.JavaMail.javamailuser@localhost> Project: STX_download_mirror Build #: 196 Status: Failure Timestamp: 20190306T060043Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190306T060000Z/logs -------------------------------------------------------------------------------- Parameters DOCKER_DL_ID: jenkins-master-20190306T060000Z-downloader PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190306T060000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190306T060000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Wed Mar 6 06:07:26 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 6 Mar 2019 01:07:26 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 7 - Failure! Message-ID: <538940112.52.1551852447078.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 7 Status: Failure Timestamp: 20190306T060000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190306T060000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false BUILD_CONTAINERS_ZZZ: false From shuicheng.lin at intel.com Wed Mar 6 08:56:13 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Wed, 6 Mar 2019 08:56:13 +0000 Subject: [Starlingx-discuss] rate_limit error when execute openstack network command Message-ID: <9700A18779F35F49AF027300A49E7C765FE99AF0@SHSMSX101.ccr.corp.intel.com> Hi all, I try to build latest master code by myself, and do AIO deployment following the Wiki step. All things go well until I try to setup providernet network. Here is the error message: controller-0:/home/wrsroot# openstack network segment range create ${PHYSNET0}-a --network-type vlan --physical-network ${PHYSNET0} --minimum 400 --maximum 499 --private --project ${ADMINID} __init__() got an unexpected keyword argument 'rate_limit' controller-0:/home/wrsroot# openstack network list __init__() got an unexpected keyword argument 'rate_limit' Anyone meet this error before? And how to solve it? Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Wed Mar 6 14:26:23 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 6 Mar 2019 14:26:23 +0000 Subject: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack Distro meeting, 3/6 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35EBAEFC@SHSMSX104.ccr.corp.intel.com> Agenda & Notes for 3/6 meeting: 1. Ceph upgrade status (Ovidiu/Daniel, Changcheng/Tingjie) update: https://etherpad.openstack.org/p/stx-ceph-uprev-mimic Ceph build for ceph sub-module: patch uploaded. 3 PR and 1 patch in manifest pending merge. made the change to achieve download tar.gz, the changes are included in the patch mentioned above. Daniel still WIP to get 2+2+2 work as expected without WR. Expect to get this done by 3/8. will rebase from master to include container support next week. Status: will abandan the current pending reviews against master; engineers from WR/Intel are working on the same manifest today. 2. CentOS 7.6 feature branch merge to master readiness review (Shuicheng) Saul re-based the master changes to f/CentOS7.6 yesterday, build/deployment with one issue with network create. Same issue saw in the master build. May related to local docker server. Will confirm it tomorrow. Plan is to merge back to master on Monday - no change. 3. DevStack update (Dean/Yi) last two weeks, we've submitted 3 patches for flock serves bring-up; 1 for fault and 2 for nfv under review. Dean also submitted 7 patches. 2 patches to fix the compiling warning due to Bionic upgrade. Devstack by design it is runs on OS independent, but Ubuntu is the most tested one. Zuul in Openstack CI/CD is currently hosted on Ubuntu OS. comparing to what we planned, we can enable devstack for flocks services for fault, nfv. Leaving metal and Martin working on this. Due to Devstack switched to new version from Master, thus we may find new issues under new Bionic. Ask core reviewers in flocks to review Devstack patches - patch query: https://review.openstack.org/#/q/status:open+branch:master+topic:devstack. 4. Opens (all) will do bug review next weeks. -----Original Appointment----- From: Xie, Cindy Sent: Monday, November 5, 2018 2:27 PM To: Xie, Cindy; Troyer, Dean; Zhu, Vivian; Hu, Yong; Lin, Shuicheng; Shang, Dehao; Somerville, Jim; Wold, Saul; Sun, Austin; Jones, Bruce E; Liu, ZhipengS; 'Rowsell, Brent'; 'Khalil, Ghada'; starlingx-discuss at lists.starlingx.io; Waheed, Numan Cc: Perez Carranza, Jose; 'Hellmann, Gil'; 'Seiler, Glenn'; 'Young, Ken'; Arce Moreno, Abraham; Cobbley, David A; Fang, Liang A; 'Eslimi, Dariush'; Hu, Wei W; Martinez Monroy, Elio; 'Waines, Greg'; Lara, Cesar; Armstrong, Robert H; 'Chen, Jacky'; Martinez Landa, Hayde; 'Poncea, Ovidiu'; Perez Rodriguez, Humberto I; Gomez, Juan P; Shuquan Huang Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, March 6, 2019 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 Mar 6 03:06:46 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Wed, 6 Mar 2019 03:06:46 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris's guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie ; Richard, Joseph ; Peters, Matt ; Winnicki, Chris Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng ; Martinez Monroy, Elio ; Zhao, Forrest ; Xie, Cindy ; Cabrales, Ada ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don't believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don't know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I'm trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I'm responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don't know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing "system host-unlock compute-0", it will report "Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address". But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Mar 6 16:23:08 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 6 Mar 2019 16:23:08 +0000 Subject: [Starlingx-discuss] Where to find documentation for stx- projects In-Reply-To: <1551257200.2404.15.camel@suse.com> References: <1551257200.2404.15.camel@suse.com> Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC0A14D20@ALA-MBD.corp.ad.wrs.com> Hi Manuel, There is a big documentation thrust that's underway, per https://review.openstack.org/#/c/635641/. Meanwhile... These links have *some* related info... - https://www.starlingx.io/collateral/StarlingX-Onboarding-Deck-for-Web-February-2019.pdf - https://www.starlingx.io/collateral/StarlingX_OnePager_Web-102318.pdf For distributed cloud, there is this presentation from the Rocky OpenStack Summit in Vancouver: - https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21360/edge-computing-operations-day-1-deployment-and-day-2-management Bill... -----Original Message----- From: Manuel Buil Sent: Wednesday, February 27, 2019 3:47 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Where to find documentation for stx- projects Hi, I would like to understand more about stx-distcloud and stx-nfv but unfortunately, I can't find a lot of documentation. The wiki pages don't have much content: https://wiki.openstack.org/wiki/StarlingX/NFV https://wiki.openstack.org/wiki/StarlingX/DistCloud either the docs.io : https://docs.starlingx.io/stx-nfv/index.html https://docs.starlingx.io/stx-distcloud/index.html And the README does not have anything: https://github.com/openstack/stx-nfv https://github.com/openstack/stx-distcloud I wonder if there is another place where the docs are stored or if maybe documentation will be created in the next months. I wanted to get an idea of the general architecture of them and perhaps have a basic guide, so that I could try out those projects. Thanks, Manuel _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From mbuil at suse.com Wed Mar 6 16:47:11 2019 From: mbuil at suse.com (Manuel Buil) Date: Wed, 06 Mar 2019 17:47:11 +0100 Subject: [Starlingx-discuss] Where to find documentation for stx- projects In-Reply-To: <586E8B730EA0DA4A9D6A80A10E486BC0A14D20@ALA-MBD.corp.ad.wrs.com> References: <1551257200.2404.15.camel@suse.com> <586E8B730EA0DA4A9D6A80A10E486BC0A14D20@ALA-MBD.corp.ad.wrs.com> Message-ID: <1551890831.2214.68.camel@suse.com> Thanks Bill! On Wed, 2019-03-06 at 16:23 +0000, Zvonar, Bill wrote: > Hi Manuel, > > There is a big documentation thrust that's underway, per https://revi > ew.openstack.org/#/c/635641/. > > Meanwhile... > > These links have *some* related info... > > - https://www.starlingx.io/collateral/StarlingX-Onboarding-Deck-for-W > eb-February-2019.pdf > - https://www.starlingx.io/collateral/StarlingX_OnePager_Web-102318.p > df > > For distributed cloud, there is this presentation from the Rocky > OpenStack Summit in Vancouver: > > - https://www.openstack.org/summit/vancouver-2018/summit-schedule/eve > nts/21360/edge-computing-operations-day-1-deployment-and-day-2- > management > > Bill... > > -----Original Message----- > From: Manuel Buil > Sent: Wednesday, February 27, 2019 3:47 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Where to find documentation for stx- > projects > > Hi, > > I would like to understand more about stx-distcloud and stx-nfv but > unfortunately, I can't find a lot of documentation. The wiki pages > don't have much content: > > https://wiki.openstack.org/wiki/StarlingX/NFV > https://wiki.openstack.org/wiki/StarlingX/DistCloud > > either the docs.io : > > https://docs.starlingx.io/stx-nfv/index.html > https://docs.starlingx.io/stx-distcloud/index.html > > And the README does not have anything: > > https://github.com/openstack/stx-nfv > https://github.com/openstack/stx-distcloud > > I wonder if there is another place where the docs are stored or if > maybe documentation will be created in the next months. I wanted to > get an idea of the general architecture of them and perhaps have a > basic guide, so that I could try out those projects. > > Thanks, > Manuel > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From build.starlingx at gmail.com Wed Mar 6 18:22:55 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 6 Mar 2019 13:22:55 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_DL_container_setup - Build # 210 - Failure! Message-ID: <2029808380.56.1551896576269.JavaMail.javamailuser@localhost> Project: STX_DL_container_setup Build #: 210 Status: Failure Timestamp: 20190306T182246Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190306T060000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190306T060000Z DOCKER_DL_ID: jenkins-master-20190306T060000Z-downloader PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190306T060000Z/logs DOCKER_DL_TAG: master-20190306T060000Z-downloader-image PUBLISH_LOGS_BASE: /tmp/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From Joseph.Richard at windriver.com Wed Mar 6 18:47:49 2019 From: Joseph.Richard at windriver.com (Richard, Joseph) Date: Wed, 6 Mar 2019 18:47:49 +0000 Subject: [Starlingx-discuss] rate_limit error when execute openstack network command In-Reply-To: <9700A18779F35F49AF027300A49E7C765FE99AF0@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C765FE99AF0@SHSMSX101.ccr.corp.intel.com> Message-ID: <7B6A2AE64F40F245AE81F245059F0C366BE543D7@ALA-MBD.corp.ad.wrs.com> In https://github.com/openstack/openstacksdk/blame/da4ec3e70c20db3ea37cd54dec6dc1e10b309274/lower-constraints.txt, a dependency was added for keystoneauth1==3.13.0, however it looks like we are only at 3.10.0 Because we are building openstacksdk from master, we are hitting this. We will likely need to upversion keystoneauth1 to resolve this. I am not aware of a good workaround. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Wednesday, March 6, 2019 3:56 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] rate_limit error when execute openstack network command Hi all, I try to build latest master code by myself, and do AIO deployment following the Wiki step. All things go well until I try to setup providernet network. Here is the error message: controller-0:/home/wrsroot# openstack network segment range create ${PHYSNET0}-a --network-type vlan --physical-network ${PHYSNET0} --minimum 400 --maximum 499 --private --project ${ADMINID} __init__() got an unexpected keyword argument 'rate_limit' controller-0:/home/wrsroot# openstack network list __init__() got an unexpected keyword argument 'rate_limit' Anyone meet this error before? And how to solve it? Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Wed Mar 6 18:52:18 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 6 Mar 2019 18:52:18 +0000 Subject: [Starlingx-discuss] Community call minutes and notes Mar 6th 2019 Message-ID: <9A85D2917C58154C960D95352B22818BD06F1350@fmsmsx123.amr.corp.intel.com> Agenda and notes for the Mar 6th call * Congratulations to the Container team! * Release plan - line by line review (Ghada). We have 3 items Red for the release: Distributed Keystone, OpenStack patch up streaming and Performance Testing * https://docs.google.com/spreadsheets/d/1HUwbsaSerzFRuvXVB_qvoGdI0Chx1YiiA2WYHwvIoYI/edit?usp=sharing * Defect trend continues to be upward * Docs work - many new documents are marked as Release Gating in the draft spec. Will need help to write them. Looking for volunteers. * Planning for the next release - defer to next meeting * Defects ? added link to help wanted bugs on wiki front page - currently there are 5 bugs ? https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.helpwanted * Awesome! Thanks! * Open ARs ? https://docs.google.com/spreadsheets/d/1F-JKh8_gLlUzbrUJRbsf4u65yBGVBl8HGe-RnUQoyc4/edit?usp=sharing ? AR owners are asked to update their ARs on this sheet * Please submit your topics for Forums! -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Wed Mar 6 19:05:38 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 6 Mar 2019 14:05:38 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_download_mirror - Build # 198 - Failure! Message-ID: <2042379494.62.1551899139694.JavaMail.javamailuser@localhost> Project: STX_download_mirror Build #: 198 Status: Failure Timestamp: 20190306T185820Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190306T060000Z/logs -------------------------------------------------------------------------------- Parameters DOCKER_DL_ID: jenkins-master-20190306T060000Z-downloader PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190306T060000Z/logs PUBLISH_LOGS_BASE: /tmp/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From scott.little at windriver.com Wed Mar 6 19:12:01 2019 From: scott.little at windriver.com (Scott Little) Date: Wed, 6 Mar 2019 14:12:01 -0500 Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 7 - Failure! In-Reply-To: <538940112.52.1551852447078.JavaMail.javamailuser@localhost> References: <538940112.52.1551852447078.JavaMail.javamailuser@localhost> Message-ID: <1988b4df-f0a4-2ea4-58d8-68c9e4af06f9@windriver.com> We had a 404 error across multiple source mirrors trying to access one of the repodata files on one repo. There are a couple of theories. 1)  The fastest mirror plugin appears to open the window for the various files that make up a repodata to come from various sources.  Those sources might be inconsistent as they aren't updating in unison.    Disabling the fast mirror plugin isn't my first choice.   No obvious config option to make all repodata come from a single source.  Am I missing something? 2) stale cached content locally, requireing an explicit yum cleanup comand     Failure to reproduce on the next run suggests this isn't the issue. 3) stale cached content in an upstream server     Solution:  add http_caching=packages to yum.conf     Yum will ask upstream for non-cached repodata.     I will test this and see if we get a recurrence over the next few weeks. Scott On 2019-03-06 1:07 a.m., build.starlingx at gmail.com wrote: > Project: STX_build_master_master > Build #: 7 > Status: Failure > Timestamp: 20190306T060000Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190306T060000Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS: false > BUILD_CONTAINERS_ZZZ: false > > _______________________________________________ > 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 michael.l.tullis at intel.com Wed Mar 6 21:37:07 2019 From: michael.l.tullis at intel.com (Tullis, Michael L) Date: Wed, 6 Mar 2019 21:37:07 +0000 Subject: [Starlingx-discuss] [docs][meetings] docs team meeting minutes 3/6/2019 Message-ID: <3808363B39586544A6839C76CF81445EA1AC1C0C@ORSMSX104.amr.corp.intel.com> For notes and new action items from our docs team meeting today, see our etherpad: https://etherpad.openstack.org/p/stx-documentation Join us if you have interest in StarlingX docs! We meet Wednesdays, and call logistics are here: https://wiki.openstack.org/wiki/Starlingx/Meetings. -- Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: From cesar.lara at intel.com Wed Mar 6 23:39:30 2019 From: cesar.lara at intel.com (Lara, Cesar) Date: Wed, 6 Mar 2019 23:39:30 +0000 Subject: [Starlingx-discuss] [build][meetings] Build team meeting minutes for 2/28/2019 Message-ID: <0B566C62EC792145B40E29EFEBF1AB471060032E@fmsmsx104.amr.corp.intel.com> Build team meeting Agenda for 2/28/2019 - Cengn Update - Build system proposal for Ubuntu - Victor R - Build signing support - opens Meeting notes Cengn Update - team is getting ready for the merge of Centos 7.76 feature, the change of the mirror infrastructure in Cengn is still on hold, We posted Jenkins scripts for the Cengn build, waiting to host those on git repositories, tentative on stx-staging Build signing support Not an easy task, there are a couple pieces of infrastructure that need to be on place before we can start signing our build, multi layered problem, we have several things to look at for signing, we as build team could have some scripts based on the ones Wind River uses but we require the other pieces to make them work. We agreed to follow up with Ken on any requests for signed builds. Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From cesar.lara at intel.com Wed Mar 6 23:50:30 2019 From: cesar.lara at intel.com (Lara, Cesar) Date: Wed, 6 Mar 2019 23:50:30 +0000 Subject: [Starlingx-discuss] [build][meetings] Build team meeting Agenda 3/7/2019 Message-ID: <0B566C62EC792145B40E29EFEBF1AB47106003EA@fmsmsx104.amr.corp.intel.com> Build team meeting Agenda for 3/7/2019 - Cengn build update - Ubuntu Build update - Build separation - Opens Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Thu Mar 7 05:57:00 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 7 Mar 2019 05:57:00 +0000 Subject: [Starlingx-discuss] rate_limit error when execute openstack network command In-Reply-To: <7B6A2AE64F40F245AE81F245059F0C366BE543D7@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C765FE99AF0@SHSMSX101.ccr.corp.intel.com> <7B6A2AE64F40F245AE81F245059F0C366BE543D7@ALA-MBD.corp.ad.wrs.com> Message-ID: <9700A18779F35F49AF027300A49E7C765FE99D16@SHSMSX101.ccr.corp.intel.com> Thanks Joseph. To work around this issue, I try to install keystoneauth1==3.13.1 by pip. After it, I could create network and launch VM successfully. Here is my step: 1. Install pip: a) wget http://mirror.centos.org/centos/7.6.1810/cloud/x86_64/openstack-pike/common/python-pip-8.1.2-1.el7.noarch.rpm b) rpm -ivh python-pip-8.1.2-1.el7.noarch.rpm 2. upgrade keystoneauth1: pip -proxy YOUR_PROXY install keystoneauth1==3.13.1 3. Run "openstack network list" to confirm the issue is gone: controller-0:/home/wrsroot# openstack network list Best Regards Shuicheng From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Thursday, March 7, 2019 2:48 AM To: Lin, Shuicheng ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] rate_limit error when execute openstack network command In https://github.com/openstack/openstacksdk/blame/da4ec3e70c20db3ea37cd54dec6dc1e10b309274/lower-constraints.txt, a dependency was added for keystoneauth1==3.13.0, however it looks like we are only at 3.10.0 Because we are building openstacksdk from master, we are hitting this. We will likely need to upversion keystoneauth1 to resolve this. I am not aware of a good workaround. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Wednesday, March 6, 2019 3:56 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] rate_limit error when execute openstack network command Hi all, I try to build latest master code by myself, and do AIO deployment following the Wiki step. All things go well until I try to setup providernet network. Here is the error message: controller-0:/home/wrsroot# openstack network segment range create ${PHYSNET0}-a --network-type vlan --physical-network ${PHYSNET0} --minimum 400 --maximum 499 --private --project ${ADMINID} __init__() got an unexpected keyword argument 'rate_limit' controller-0:/home/wrsroot# openstack network list __init__() got an unexpected keyword argument 'rate_limit' Anyone meet this error before? And how to solve it? Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Mar 7 14:14:16 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 7 Mar 2019 14:14:16 +0000 Subject: [Starlingx-discuss] rate_limit error when execute openstack network command In-Reply-To: <9700A18779F35F49AF027300A49E7C765FE99D16@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C765FE99AF0@SHSMSX101.ccr.corp.intel.com> <7B6A2AE64F40F245AE81F245059F0C366BE543D7@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE99D16@SHSMSX101.ccr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4C9888@ALA-MBD.corp.ad.wrs.com> Is there a Launchpad for this build issue? Is someone working on a permanent solution? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 07, 2019 12:57 AM To: Richard, Joseph; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] rate_limit error when execute openstack network command Thanks Joseph. To work around this issue, I try to install keystoneauth1==3.13.1 by pip. After it, I could create network and launch VM successfully. Here is my step: 1. Install pip: a) wget http://mirror.centos.org/centos/7.6.1810/cloud/x86_64/openstack-pike/common/python-pip-8.1.2-1.el7.noarch.rpm b) rpm -ivh python-pip-8.1.2-1.el7.noarch.rpm 2. upgrade keystoneauth1: pip -proxy YOUR_PROXY install keystoneauth1==3.13.1 3. Run "openstack network list" to confirm the issue is gone: controller-0:/home/wrsroot# openstack network list Best Regards Shuicheng From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Thursday, March 7, 2019 2:48 AM To: Lin, Shuicheng >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] rate_limit error when execute openstack network command In https://github.com/openstack/openstacksdk/blame/da4ec3e70c20db3ea37cd54dec6dc1e10b309274/lower-constraints.txt, a dependency was added for keystoneauth1==3.13.0, however it looks like we are only at 3.10.0 Because we are building openstacksdk from master, we are hitting this. We will likely need to upversion keystoneauth1 to resolve this. I am not aware of a good workaround. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Wednesday, March 6, 2019 3:56 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] rate_limit error when execute openstack network command Hi all, I try to build latest master code by myself, and do AIO deployment following the Wiki step. All things go well until I try to setup providernet network. Here is the error message: controller-0:/home/wrsroot# openstack network segment range create ${PHYSNET0}-a --network-type vlan --physical-network ${PHYSNET0} --minimum 400 --maximum 499 --private --project ${ADMINID} __init__() got an unexpected keyword argument 'rate_limit' controller-0:/home/wrsroot# openstack network list __init__() got an unexpected keyword argument 'rate_limit' Anyone meet this error before? And how to solve it? Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Mar 7 15:44:16 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 7 Mar 2019 15:44:16 +0000 Subject: [Starlingx-discuss] rate_limit error when execute openstack network command In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA4C9888@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C765FE99AF0@SHSMSX101.ccr.corp.intel.com> <7B6A2AE64F40F245AE81F245059F0C366BE543D7@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE99D16@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4C9888@ALA-MBD.corp.ad.wrs.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4C9C6E@ALA-MBD.corp.ad.wrs.com> I opened: https://bugs.launchpad.net/starlingx/+bug/1819020 From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, March 07, 2019 9:14 AM To: Lin, Shuicheng; Richard, Joseph; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] rate_limit error when execute openstack network command Is there a Launchpad for this issue? Is someone working on a permanent solution? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 07, 2019 12:57 AM To: Richard, Joseph; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] rate_limit error when execute openstack network command Thanks Joseph. To work around this issue, I try to install keystoneauth1==3.13.1 by pip. After it, I could create network and launch VM successfully. Here is my step: 1. Install pip: a) wget http://mirror.centos.org/centos/7.6.1810/cloud/x86_64/openstack-pike/common/python-pip-8.1.2-1.el7.noarch.rpm b) rpm -ivh python-pip-8.1.2-1.el7.noarch.rpm 2. upgrade keystoneauth1: pip -proxy YOUR_PROXY install keystoneauth1==3.13.1 3. Run "openstack network list" to confirm the issue is gone: controller-0:/home/wrsroot# openstack network list Best Regards Shuicheng From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Thursday, March 7, 2019 2:48 AM To: Lin, Shuicheng >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] rate_limit error when execute openstack network command In https://github.com/openstack/openstacksdk/blame/da4ec3e70c20db3ea37cd54dec6dc1e10b309274/lower-constraints.txt, a dependency was added for keystoneauth1==3.13.0, however it looks like we are only at 3.10.0 Because we are building openstacksdk from master, we are hitting this. We will likely need to upversion keystoneauth1 to resolve this. I am not aware of a good workaround. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Wednesday, March 6, 2019 3:56 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] rate_limit error when execute openstack network command Hi all, I try to build latest master code by myself, and do AIO deployment following the Wiki step. All things go well until I try to setup providernet network. Here is the error message: controller-0:/home/wrsroot# openstack network segment range create ${PHYSNET0}-a --network-type vlan --physical-network ${PHYSNET0} --minimum 400 --maximum 499 --private --project ${ADMINID} __init__() got an unexpected keyword argument 'rate_limit' controller-0:/home/wrsroot# openstack network list __init__() got an unexpected keyword argument 'rate_limit' Anyone meet this error before? And how to solve it? Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Wed Mar 6 23:18:19 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 6 Mar 2019 23:18:19 +0000 Subject: [Starlingx-discuss] FW: Mar 5th 2019 Distro.openstack meeting In-Reply-To: <72AD03D27224C74982BE13246D75B397399D5ED0@SHSMSX103.ccr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BD06EECEB@fmsmsx123.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BD06F00EB@fmsmsx123.amr.corp.intel.com> <72AD03D27224C74982BE13246D75B397399D5E95@SHSMSX103.ccr.corp.intel.com> <9A85D2917C58154C960D95352B22818BD06F0EF6@fmsmsx123.amr.corp.intel.com> <72AD03D27224C74982BE13246D75B397399D5EA8@SHSMSX103.ccr.corp.intel.com> <9A85D2917C58154C960D95352B22818BD06F0F08@fmsmsx123.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EB935C@SHSMSX104.ccr.corp.intel.com> <72AD03D27224C74982BE13246D75B397399D5ED0@SHSMSX103.ccr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BD06F17E4@fmsmsx123.amr.corp.intel.com> I have an issue to discuss about Yan's work on the changes for line item 34 "CSRF AngularJS Fixes" in the distro.openstack upstream tracking spreadsheet. The upstream submission has not been approved, due to lack of an automated test case. In looking at Yan's description of the work needed to get this change approved (below), it looks like the test framework changes will be more work than the feature is worth. As such, I'd like to propose dropping this bugfix from the upstream work item list. I'm looking for feedback on that proposal. Thanks! brucej From: Chen, Yan Sent: Tuesday, March 5, 2019 5:22 PM To: Xie, Cindy ; Jones, Bruce E Subject: RE: Mar 5th 2019 Distro.openstack meeting Current test cases are all running on the HTTP environment. This feature will only impact under HTTPS environment, when CSRF_COOKIE_HTTPONLY is enabled in Django (detailed introduction is here: https://docs.djangoproject.com/en/2.1/ref/settings/#csrf-cookie-httponly), according to the official document, this feature is kind of useless... So that's why there's no code in horizon to support this and no test case to test it either. Designating the CSRF cookie as HttpOnly doesn't offer any practical protection because CSRF is only to protect against cross-domain attacks. If an attacker can read the cookie via JavaScript, they're already on the same domain as far as the browser knows, so they can do anything they like anyway. (XSS is a much bigger hole than CSRF.) Although the setting offers little practical benefit, it's sometimes required by security auditors. Yan From: Xie, Cindy Sent: Wednesday, March 6, 2019 09:14 To: Jones, Bruce E >; Chen, Yan > Subject: RE: Mar 5th 2019 Distro.openstack meeting Yan, There are quite few Zuul testing like below, anything we can do to just insert one test case in? horizon-openstack-tox-python3-django111SUCCESS in 11m 04s horizon-selenium-headlessSUCCESS in 6m 02s (non-voting) horizon-integration-testsSUCCESS in 53m 12s (non-voting) horizon-dsvm-tempest-pluginSUCCESS in 34m 10s horizon-dsvm-tempest-plugin-py27SUCCESS in 30m 39s horizon-tox-bandit-baselineSUCCESS in 6m 02s (non-voting) thx. - cindy From: Jones, Bruce E Sent: Wednesday, March 6, 2019 9:11 AM To: Chen, Yan > Cc: Xie, Cindy > Subject: RE: Mar 5th 2019 Distro.openstack meeting How much work is it to modify the test framework? From: Chen, Yan Sent: Tuesday, March 5, 2019 5:10 PM To: Jones, Bruce E > Cc: Xie, Cindy > Subject: RE: Mar 5th 2019 Distro.openstack meeting Yes, exactly. Yan From: Jones, Bruce E Sent: Wednesday, March 6, 2019 09:09 To: Chen, Yan > Cc: Xie, Cindy > Subject: RE: Mar 5th 2019 Distro.openstack meeting But if you don't modify the tests, they won't accept the code, right? From: Chen, Yan Sent: Tuesday, March 5, 2019 5:08 PM To: Jones, Bruce E > Cc: Xie, Cindy > Subject: RE: Mar 5th 2019 Distro.openstack meeting * AR Bruce to ping Yan re: line item 34 "CSRF AngularJS Fixes" I just updated on the spreadsheet and modified the status to Unlikely: There's no existing test case for the CSRF feature. Can not generate test framework for this patch. This patch is only several lines but to test it automatically I need to modify the whole test framework. I don't think it worth doing it. I've sent email to Tyler Smith (WRS) about this, still waiting for his reply. Yan From: Jones, Bruce E Sent: Wednesday, March 6, 2019 02:15 To: He, Yongli >; Chen, Yan > Cc: Ding, Jian-feng >; Xie, Cindy > Subject: FW: Mar 5th 2019 Distro.openstack meeting Hello Yong Li and Yan. Can you please address your ARs as per below and update the tracking spreadsheet with the latest status? Thank you! brucej From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Tuesday, March 5, 2019 7:30 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Mar 5th 2019 Distro.openstack meeting Overall plan and status tracking document: https://etherpad.openstack.org/p/stx-openstack-patch-refactoring * Details: https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit?usp=sharing Meeting agenda and notes for the 3/5 meeting * NUMA aware live migration work is pushing to Train. See Artom's latest update https://review.openstack.org/#/c/635669/ * Suggest that we plan to backport the patches from Train to stx.2019.05 once they merge. * We reviewed several different options for handling this situation: ? Wait for Train - unsatisfying, least effort ? Carry forks (patches not necessarily accepted upstream) * Implement our own patches - expensive, deterministic, leads to new forks * Pull from upstream patch submissions - less expensive, risky, less perception of forks ? Backport from Train to Stein (once the patches get accepted) - less expensive, some risk, less deterministic ? Nova community doesn't merge things that aren't' deployable or complete ? We postponed decisions as to which options to apply to which patches - hopefully more will go in. * Review LP issues: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack * AR Frank to review the issues with his team and update as needed * Review upstream updates: https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit?ts=5c1933cc#gid=0 * AR Bruce to ping Yong Li re: line item 7 "Clean up orphan instances" * AR Yong Li to ask for an exception for line item 9 "NUMA Topology API" * AR Frank re: line item 30 "RPC timeout handling" please have this re-tested * AR Bruce to ping Yan re: line item 34 "CSRF AngularJS Fixes" -------------- next part -------------- An HTML attachment was scrubbed... URL: From corvus at inaugust.com Thu Mar 7 21:47:02 2019 From: corvus at inaugust.com (James E. Blair) Date: Thu, 07 Mar 2019 13:47:02 -0800 Subject: [Starlingx-discuss] Migrating git repos to OpenDev Message-ID: <871s3itl0p.fsf@meyer.lemoncheese.net> Hi, As discussed in November[1], the OpenStack project infrastructure is being rebranded as "OpenDev" to better support a wider community of projects. We are nearly ready to perform the part of this transition with the largest impact: moving the authoritative git repositories for existing projects. In this email, I'd like to introduce the new hosting system we are preparing, discuss the transition, and invite projects to work with us on the logistics of the change. Gerrit ====== Gerrit is the core of our system and it will remain so in OpenDev. As part of this move, we will rename the gerrit server from review.openstack.org to review.opendev.org. As part of the transition, we will automatically merge appropriate changes to all branches of all repositories updating .gitreview and Zuul configuration files. Any further changes (README files, etc.) we expect to be made by individual project contributors. Repository Browsing =================== Currently our canonical *public* repository system is the cgit server at https://git.openstack.org/ (and git.airshipit.org, git.starlingx.io, and git.zuul-ci.org). This is a load balanced cluster of several servers which is designed to handle all the public git repository traffic, as it scales much better than Gerrit (and has a more friendly domain name). >From a technical standpoint, it's excellent, but its usability could be improved. Therefore, as part of this transition, we will replace the cgit servers with a new system based on Gitea. Gitea is a complete development collaboration system, but it's very flexible and will allow us to disable components which we aren't using. We will operate it in a read-only configuration where it will act as the public mirror for Gerrit. The advantages it has over the current system are: * Shorter domain name in project URLs: https://git.openstack.org/openstack/nova vs https://opendev.org/openstack/nova * Clone and browsing URLs are the same (with cgit, the browsing URL has an extra path component) * More visually pleasing code browsing * Integrated code searching * Ability to highlight multiple lines in links When we perform the transition we will install redirects from git.openstack.org (and the other git sites) to opendev.org, and will maintain those redirects for the foreseeable future. We will construct them so that even existing deep links to individual files in individual commits to cgit will redirect to the correct location on opendev.org. This system is up and running now with a live mirror of data from Gerrit, and you can start testing it out today at https://opendev.org/ Please let us know if you encounter any problems. If you would like to read more about the design of this system and the transition, see the infra-spec[2]. GitHub ====== Currently all OpenStack projects are replicated to GitHub. We do not plan on changing that during the transition, however, any projects outside of the openstack*/ namespaces will not automatically be replicated to GitHub, and we do not plan on adding that in the future. We do, however, support projects using Zuul to run post-merge jobs to push updates to GitHub or any other third-party mirrors with their own credentials. We will be happy to work with anyone interested in that to help set up jobs to do so. We are adopting this approach so that individual projects can have more control over how they are represented in social media, and to give us more flexibility in supporting our own organizational namespaces on OpenDev without assuming they map directly to GitHub. Eventually we plan on moving the OpenStack project to that system as well and retiring direct replication from Gerrit to GitHub completely. But we will defer that work until after this transition. Logistics ========= We can prepare much of the system in advance (as we have for the hosting system on opendev.org), but the actual transition and renaming of the Gerrit server will need to happen at once during an outage window. We need to schedule that outage and begin preparing for it. Since all of the project git URLs are going to change (to replace git.openstack.org with opendev.org and review.openstack.org with review.opendev.org), we can additionally take the opportunity to reorganize projects into different organizations. For example, during the transition we will rename Zuul, and it's associated projects, from the "openstack-infra" org to "zuul". So their new names will be "zuul/zuul", "zuul/nodepool", etc. This is an excellent time for the rest of the OpenStack Foundation pilot projects to do the same. If the OpenStack project desires this, it would also be a good time to move unofficial projects out of the openstack/ namespace. Therefore, we need your help: Action Items ============ We need each of the following projects: * OpenStack * Airship * StarlingX * Zuul To nominate a single point of contact to work with us on the transition. It would be helpful for that person to attend the next (and possibly next several) openstack infra team meetings in IRC [3]. We will work with those people on scheduling the transition, as well as finalizing the list of projects which should be renamed as part of the transition. If you manage an unofficial project and would like to take the opportunity to move or rename your project, please add it to this ethercalc[4]. [1] http://lists.openstack.org/pipermail/openstack-dev/2018-November/136403.html [2] http://specs.openstack.org/openstack-infra/infra-specs/specs/opendev-gerrit.html [3] http://eavesdrop.openstack.org/#Project_Infrastructure_Team_Meeting [4] https://ethercalc.openstack.org/opendev-transition From juan.carlos.alonso at intel.com Thu Mar 7 22:25:54 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Thu, 7 Mar 2019 22:25:54 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190307 In-Reply-To: References: Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9FBBC@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Mar-07 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal Environment Simplex Setup Manual [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [FAIL] Sanity Platform 02 TCs [FAIL] TOTAL: [FAIL ] Duplex Setup Manual [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [FAIL] Sanity Platform In Development TOTAL: [FAIL ] Standard Local Storage (2+2) Setup Manual [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [FAIL] Sanity Platform In Development TOTAL: [FAIL ] Standard External Storage (2+2+2) Setup Manual [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [FAIL] Sanity Platform In Development TOTAL: [FAIL ] =========================================== Sanity Test is executed in a Containers - Virtual Environment Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [FAIL] Sanity Platform 02 TCs [FAIL] TOTAL: [FAIL ] Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [FAIL] Sanity Platform In Development TOTAL: [ FAIL ] ------------------------------------------------------------------ rate_limit error when executing openstack network commands: https://bugs.launchpad.net/starlingx/+bug/1819020 $: openstack network list __init__() got an unexpected keyword argument 'rate_limit' ------------------------------------------------------------------ This is the list of test cases executed: https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From tyler.smith at windriver.com Thu Mar 7 18:01:16 2019 From: tyler.smith at windriver.com (Smith, Tyler) Date: Thu, 7 Mar 2019 18:01:16 +0000 Subject: [Starlingx-discuss] Mar 5th 2019 Distro.openstack meeting In-Reply-To: <9A85D2917C58154C960D95352B22818BD06F17E4@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BD06EECEB@fmsmsx123.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BD06F00EB@fmsmsx123.amr.corp.intel.com> <72AD03D27224C74982BE13246D75B397399D5E95@SHSMSX103.ccr.corp.intel.com> <9A85D2917C58154C960D95352B22818BD06F0EF6@fmsmsx123.amr.corp.intel.com> <72AD03D27224C74982BE13246D75B397399D5EA8@SHSMSX103.ccr.corp.intel.com> <9A85D2917C58154C960D95352B22818BD06F0F08@fmsmsx123.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EB935C@SHSMSX104.ccr.corp.intel.com> <72AD03D27224C74982BE13246D75B397399D5ED0@SHSMSX103.ccr.corp.intel.com> <9A85D2917C58154C960D95352B22818BD06F17E4@fmsmsx123.amr.corp.intel.com> Message-ID: I would agree that it's not worth the effort. We've recently dropped this setting from stx-gui, so it will work with vanilla stein horizon anyways, and the recommendation to use the setting was removed from horizon's documentation as well Tyler From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, March 6, 2019 6:18 PM To: starlingx-discuss at lists.starlingx.io Cc: Chen, Yan Subject: [Starlingx-discuss] FW: Mar 5th 2019 Distro.openstack meeting I have an issue to discuss about Yan's work on the changes for line item 34 "CSRF AngularJS Fixes" in the distro.openstack upstream tracking spreadsheet. The upstream submission has not been approved, due to lack of an automated test case. In looking at Yan's description of the work needed to get this change approved (below), it looks like the test framework changes will be more work than the feature is worth. As such, I'd like to propose dropping this bugfix from the upstream work item list. I'm looking for feedback on that proposal. Thanks! brucej From: Chen, Yan Sent: Tuesday, March 5, 2019 5:22 PM To: Xie, Cindy >; Jones, Bruce E > Subject: RE: Mar 5th 2019 Distro.openstack meeting Current test cases are all running on the HTTP environment. This feature will only impact under HTTPS environment, when CSRF_COOKIE_HTTPONLY is enabled in Django (detailed introduction is here: https://docs.djangoproject.com/en/2.1/ref/settings/#csrf-cookie-httponly), according to the official document, this feature is kind of useless... So that's why there's no code in horizon to support this and no test case to test it either. Designating the CSRF cookie as HttpOnly doesn't offer any practical protection because CSRF is only to protect against cross-domain attacks. If an attacker can read the cookie via JavaScript, they're already on the same domain as far as the browser knows, so they can do anything they like anyway. (XSS is a much bigger hole than CSRF.) Although the setting offers little practical benefit, it's sometimes required by security auditors. Yan From: Xie, Cindy Sent: Wednesday, March 6, 2019 09:14 To: Jones, Bruce E >; Chen, Yan > Subject: RE: Mar 5th 2019 Distro.openstack meeting Yan, There are quite few Zuul testing like below, anything we can do to just insert one test case in? horizon-openstack-tox-python3-django111SUCCESS in 11m 04s horizon-selenium-headlessSUCCESS in 6m 02s (non-voting) horizon-integration-testsSUCCESS in 53m 12s (non-voting) horizon-dsvm-tempest-pluginSUCCESS in 34m 10s horizon-dsvm-tempest-plugin-py27SUCCESS in 30m 39s horizon-tox-bandit-baselineSUCCESS in 6m 02s (non-voting) thx. - cindy From: Jones, Bruce E Sent: Wednesday, March 6, 2019 9:11 AM To: Chen, Yan > Cc: Xie, Cindy > Subject: RE: Mar 5th 2019 Distro.openstack meeting How much work is it to modify the test framework? From: Chen, Yan Sent: Tuesday, March 5, 2019 5:10 PM To: Jones, Bruce E > Cc: Xie, Cindy > Subject: RE: Mar 5th 2019 Distro.openstack meeting Yes, exactly. Yan From: Jones, Bruce E Sent: Wednesday, March 6, 2019 09:09 To: Chen, Yan > Cc: Xie, Cindy > Subject: RE: Mar 5th 2019 Distro.openstack meeting But if you don't modify the tests, they won't accept the code, right? From: Chen, Yan Sent: Tuesday, March 5, 2019 5:08 PM To: Jones, Bruce E > Cc: Xie, Cindy > Subject: RE: Mar 5th 2019 Distro.openstack meeting * AR Bruce to ping Yan re: line item 34 "CSRF AngularJS Fixes" I just updated on the spreadsheet and modified the status to Unlikely: There's no existing test case for the CSRF feature. Can not generate test framework for this patch. This patch is only several lines but to test it automatically I need to modify the whole test framework. I don't think it worth doing it. I've sent email to Tyler Smith (WRS) about this, still waiting for his reply. Yan From: Jones, Bruce E Sent: Wednesday, March 6, 2019 02:15 To: He, Yongli >; Chen, Yan > Cc: Ding, Jian-feng >; Xie, Cindy > Subject: FW: Mar 5th 2019 Distro.openstack meeting Hello Yong Li and Yan. Can you please address your ARs as per below and update the tracking spreadsheet with the latest status? Thank you! brucej From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Tuesday, March 5, 2019 7:30 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Mar 5th 2019 Distro.openstack meeting Overall plan and status tracking document: https://etherpad.openstack.org/p/stx-openstack-patch-refactoring * Details: https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit?usp=sharing Meeting agenda and notes for the 3/5 meeting * NUMA aware live migration work is pushing to Train. See Artom's latest update https://review.openstack.org/#/c/635669/ * Suggest that we plan to backport the patches from Train to stx.2019.05 once they merge. * We reviewed several different options for handling this situation: ? Wait for Train - unsatisfying, least effort ? Carry forks (patches not necessarily accepted upstream) * Implement our own patches - expensive, deterministic, leads to new forks * Pull from upstream patch submissions - less expensive, risky, less perception of forks ? Backport from Train to Stein (once the patches get accepted) - less expensive, some risk, less deterministic ? Nova community doesn't merge things that aren't' deployable or complete ? We postponed decisions as to which options to apply to which patches - hopefully more will go in. * Review LP issues: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack * AR Frank to review the issues with his team and update as needed * Review upstream updates: https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit?ts=5c1933cc#gid=0 * AR Bruce to ping Yong Li re: line item 7 "Clean up orphan instances" * AR Yong Li to ask for an exception for line item 9 "NUMA Topology API" * AR Frank re: line item 30 "RPC timeout handling" please have this re-tested * AR Bruce to ping Yan re: line item 34 "CSRF AngularJS Fixes" -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Fri Mar 8 07:50:03 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 8 Mar 2019 02:50:03 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 181 - Failure! Message-ID: <1602167280.67.1552031404243.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 181 Status: Failure Timestamp: 20190308T060738Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190308T060000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190308T060000Z DOCKER_BUILD_ID: jenkins-master-20190308T060000Z-builder MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190308T060000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190308T060000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Fri Mar 8 07:50:07 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 8 Mar 2019 02:50:07 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 9 - Failure! Message-ID: <1839468004.70.1552031407807.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 9 Status: Failure Timestamp: 20190308T060000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190308T060000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false BUILD_CONTAINERS_ZZZ: false From Numan.Waheed at windriver.com Fri Mar 8 14:12:21 2019 From: Numan.Waheed at windriver.com (Waheed, Numan) Date: Fri, 8 Mar 2019 14:12:21 +0000 Subject: [Starlingx-discuss] Test Case Submission in rst format Message-ID: <3CAA827B7A79BA46B15B280EC82088FE4828CE36@ALA-MBD.corp.ad.wrs.com> Hi Abraham, We are currently in process of submitting our test cases in stx-test git repository. There has been a request to upload manual tests is rst format so that they can be visible on a wiki. Conversion of test cases from plain text format to rst format is causing a lot of pain and time lost. At the same time it is also not an absolute requirement as any tester who wants to execute these test cases can easily access them from git in text format. I am not sure about how much time is spent by Ada's team in converting these test cases but I would suggest that we should submit them in plain text format and if documentation team wants to convert them in rst then they can update them. Secondly, if these test cases are to be shown in Wiki, what is your plan for showing them in next release? Would there be a release specific Wiki or a selection available to check test cases for each release? Thanks, Numan. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Fri Mar 8 14:42:00 2019 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Fri, 8 Mar 2019 14:42:00 +0000 Subject: [Starlingx-discuss] python-openstackclient failing to build Message-ID: It looks like a patch was merged into master for python-openstackclient. https://github.com/openstack/python-openstackclient/commit/6868499ad9443960a158143c923da00ea86b7072 And we have been carrying this as a custom patch in stx-upstream https://github.com/openstack/stx-upstream/commit/aceb7fecbaf103f4ed0b269e916f238881b5340f I will remove the custom patch. I will create a Launchpad so I have a value to submit against. Al -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Fri Mar 8 15:32:38 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 8 Mar 2019 15:32:38 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Networking Meeting - 03/07 Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4CA2C8@ALA-MBD.corp.ad.wrs.com> Meeting minutes/agenda are captured at: https://etherpad.openstack.org/p/stx-networking Team Meeting Agenda/Notes - Mar 7/2019 - Network Patch Upstreaming -- Network Segment Range - Expect neutron patches to merge for Stein ms-3. Remaining neutron-lib patches will not make Stein. Analysis confirms that they are not must-have for StarlingX, so should be ok for them to merge for Train - problems with Neutron gates which may block stein-3 release, Neutron team is working on it - Network Patch Upstreaming -- Neutron uwsgi switch: No plan for Stein, may make apache wsgi solution as default web server in Train cycle - Agreed to live with this in StarlingX until the apache solution is available in Train. This is an issue for large scale deployments - Containerized OVS Integration - Code Merge Plan: Mar 15 >> Mar 22 - openstack-helm changes merged; will need to port as a patch until the next StarlingX rebase to the latest openstack-helm code. - https://review.openstack.org/#/c/641542/ - Ghada to ask Bob to review and allow the merge - stx-config code is ready for review. https://review.openstack.org/#/c/633924/ - Ghada asked Chenjie to add a W-1 to avoid merging before all the testing is complete - Next step is to test -- For now, I have tested several cases on VM. I will go ahead with baremetal soon. But before that, I would like the code be reviewed, to make sure no big problem. - Will test multi-node as well as Simplex & Duplex - OVS process monitoring and alarming - Code Merge Plan: Mar 22 - Still on hold. Expect to get back to this after OVS-DPDK Upverison testing on ~Mar 18 - OVS-DPDK Firewall - Code Merge Plan: Mar 22 - Given the move to containers, the code has to be moved from the puppet manifest to the Armada manifest (minor change). Then need a re-test in the container env. - openvswitch package Upversion - Code Merge Plan: Mar 22 >> Apr 5 - Basic functional testing on 3/1 OVS-DPDK Upgrade ISO image and will test again on new image. - TC Feedback - Provider Network Connectivity TCs are no longer valid and should be removed - SDN: SDN does not work with the current version of ovs-dpdk, so this is out of scope of the upversion test-plan. - Need a story to enable SDN - QoS: TCs need to be updated to test enabling rate-limiting thru user helm chart overrides - OpenStack Docs: https://docs.openstack.org/neutron/rocky/admin/config-qos.html - Example StarlingX Command: - system helm-override-update neutron openstack --set conf.plugins.ml2_conf.ml2.extension_drivers=port_security,qos - system application-apply stx-openstack Regards, Ghada From scott.little at windriver.com Fri Mar 8 18:14:55 2019 From: scott.little at windriver.com (Scott Little) Date: Fri, 8 Mar 2019 13:14:55 -0500 Subject: [Starlingx-discuss] python-openstackclient failing to build In-Reply-To: References: Message-ID: <06c7b8ce-549a-4b5d-297b-5a0b0d24dc9b@windriver.com> Al's code review has been posted. https://review.openstack.org/#/c/642043 Please review so we can test the build. Scott On 2019-03-08 9:42 a.m., Bailey, Henry Albert (Al) wrote: > > It looks like a patch was merged into master for python-openstackclient. > > https://github.com/openstack/python-openstackclient/commit/6868499ad9443960a158143c923da00ea86b7072 > > And we have been carrying this as a custom patch in stx-upstream > > https://github.com/openstack/stx-upstream/commit/aceb7fecbaf103f4ed0b269e916f238881b5340f > > I will remove the custom patch.  I will create a Launchpad so I have a > value to submit against. > > Al > > > _______________________________________________ > 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 dtroyer at gmail.com Fri Mar 8 19:09:37 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Fri, 8 Mar 2019 13:09:37 -0600 Subject: [Starlingx-discuss] Migrating git repos to OpenDev In-Reply-To: <871s3itl0p.fsf@meyer.lemoncheese.net> References: <871s3itl0p.fsf@meyer.lemoncheese.net> Message-ID: On Thu, Mar 7, 2019 at 3:47 PM James E. Blair wrote: > When we perform the transition we will install redirects from > git.openstack.org (and the other git sites) to opendev.org, and will > maintain those redirects for the foreseeable future. We will construct > them so that even existing deep links to individual files in individual > commits to cgit will redirect to the correct location on opendev.org. To be clear, this means the 'other domains' (git.starlingx.io, etc) are not meant for continued use, only set up with redirects? So we need to plan to not use those domains going forward. > This is an excellent time for the rest of the OpenStack Foundation > pilot projects to do the same. ++ > We need each of the following projects: > > * OpenStack > * Airship > * StarlingX > * Zuul > > To nominate a single point of contact to work with us on the transition. > It would be helpful for that person to attend the next (and possibly > next several) openstack infra team meetings in IRC [3]. We will work > with those people on scheduling the transition, as well as finalizing > the list of projects which should be renamed as part of the transition. I will be the point of contact for StarlingX. dt -- Dean Troyer dtroyer at gmail.com From bruce.e.jones at intel.com Fri Mar 8 19:25:13 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 8 Mar 2019 19:25:13 +0000 Subject: [Starlingx-discuss] Daylight Savings Time Message-ID: <9A85D2917C58154C960D95352B22818BD06F2DF8@fmsmsx123.amr.corp.intel.com> This weekend many of us switch from standard time to daylight time, as we Spring Forward an hour. As I recall, when we switched from daylight to standard last year, we agreed to keep all meetings in the timezones that are switching at the same clock time while making everyone else move their meetings around. Is that what we want to do for our meetings next week? brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Fri Mar 8 19:30:21 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Fri, 8 Mar 2019 19:30:21 +0000 Subject: [Starlingx-discuss] Daylight Savings Time In-Reply-To: <9A85D2917C58154C960D95352B22818BD06F2DF8@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BD06F2DF8@fmsmsx123.amr.corp.intel.com> Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC0A15AC4@ALA-MBD.corp.ad.wrs.com> +1 from me From: Jones, Bruce E Sent: Friday, March 8, 2019 2:25 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Daylight Savings Time This weekend many of us switch from standard time to daylight time, as we Spring Forward an hour. As I recall, when we switched from daylight to standard last year, we agreed to keep all meetings in the timezones that are switching at the same clock time while making everyone else move their meetings around. Is that what we want to do for our meetings next week? brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Fri Mar 8 19:33:50 2019 From: scott.little at windriver.com (Scott Little) Date: Fri, 8 Mar 2019 14:33:50 -0500 Subject: [Starlingx-discuss] Audit git tag versus rpm version Message-ID: <3e407d40-1d30-fedc-f5e7-f8aad85c80b4@windriver.com> My first crack at an audit comparing most recent tag versus rpm version cd $MY_REPO/.. for d in $(grep ' References: <871s3itl0p.fsf@meyer.lemoncheese.net> Message-ID: <20190308201948.y3o5e34u4jcvka5y@yuggoth.org> On 2019-03-08 13:09:37 -0600 (-0600), Dean Troyer wrote: [...] > To be clear, this means the 'other domains' (git.starlingx.io, etc) > are not meant for continued use, only set up with redirects? So we > need to plan to not use those domains going forward. [...] That's the general idea. At a minimum, we don't anticipate adding any new git.something domain names going forward. I'm actually in the middle of trying to put together the redirect sites now so haven't completely worked out how that is expected to function though it's possible we could keep that name mapped to one or a couple repository namespaces on opendev.org so I'm not *yet* certain whether it will necessarily impact addition of future repositories. I'd say, to be on the safe side, assume for now that any repositories added after the cut-over will need to be referred to as https://opendev.org/starlingx/foo-bar or whatever you decide you want things renamed to. The immediate goal is that any URLs which were valid before the cut-over will remain valid after but we're making no guarantees (for now) about things you add after the cut-over. Does that sound okay? -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From dtroyer at gmail.com Fri Mar 8 20:42:38 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Fri, 8 Mar 2019 14:42:38 -0600 Subject: [Starlingx-discuss] Migrating git repos to OpenDev In-Reply-To: <20190308201948.y3o5e34u4jcvka5y@yuggoth.org> References: <871s3itl0p.fsf@meyer.lemoncheese.net> <20190308201948.y3o5e34u4jcvka5y@yuggoth.org> Message-ID: On Fri, Mar 8, 2019 at 2:20 PM Jeremy Stanley wrote: > I'd say, to be on the safe side, assume for now that any > repositories added after the cut-over will need to be referred to as > https://opendev.org/starlingx/foo-bar or whatever you decide you > want things renamed to. The immediate goal is that any URLs which > were valid before the cut-over will remain valid after but we're > making no guarantees (for now) about things you add after the > cut-over. Does that sound okay? That is exactly what I was expecting you would say :) Thanks dt -- Dean Troyer dtroyer at gmail.com From corvus at inaugust.com Fri Mar 8 21:20:02 2019 From: corvus at inaugust.com (James E. Blair) Date: Fri, 08 Mar 2019 13:20:02 -0800 Subject: [Starlingx-discuss] Migrating git repos to OpenDev In-Reply-To: (Dean Troyer's message of "Fri, 8 Mar 2019 13:09:37 -0600") References: <871s3itl0p.fsf@meyer.lemoncheese.net> Message-ID: <87pnr1m5bx.fsf@meyer.lemoncheese.net> Dean Troyer writes: > On Thu, Mar 7, 2019 at 3:47 PM James E. Blair wrote: >> When we perform the transition we will install redirects from >> git.openstack.org (and the other git sites) to opendev.org, and will >> maintain those redirects for the foreseeable future. We will construct >> them so that even existing deep links to individual files in individual >> commits to cgit will redirect to the correct location on opendev.org. > > To be clear, this means the 'other domains' (git.starlingx.io, etc) > are not meant for continued use, only set up with redirects? So we > need to plan to not use those domains going forward. Yes, exactly right. Sorry about that. >> This is an excellent time for the rest of the OpenStack Foundation >> pilot projects to do the same. > > ++ > >> We need each of the following projects: >> >> * OpenStack >> * Airship >> * StarlingX >> * Zuul >> >> To nominate a single point of contact to work with us on the transition. >> It would be helpful for that person to attend the next (and possibly >> next several) openstack infra team meetings in IRC [3]. We will work >> with those people on scheduling the transition, as well as finalizing >> the list of projects which should be renamed as part of the transition. > > I will be the point of contact for StarlingX. Thanks! See you Tuesday! -Jim From scott.little at windriver.com Fri Mar 8 21:28:25 2019 From: scott.little at windriver.com (Scott Little) Date: Fri, 8 Mar 2019 16:28:25 -0500 Subject: [Starlingx-discuss] [Build] Audit git tag versus rpm version In-Reply-To: <3e407d40-1d30-fedc-f5e7-f8aad85c80b4@windriver.com> References: <3e407d40-1d30-fedc-f5e7-f8aad85c80b4@windriver.com> Message-ID: <2715b74b-e584-1233-b40c-e526eecae43e@windriver.com> I've issued a review, https://review.openstack.org/642158, to correct the rpm packaging versions. However it may be seen as abusing the existing TIS_BASE_SRCREV mechanism, as it result in packages looking like this ... python-cinderclient-4.1.0-1.tis.33.src.rpm This may seem to imply that tis has authored 33 patches upon python-cinderclient.  We are indeed 33 patches beyond tag 4.1.0 (as of this writing), but it is upstream revisions and not stx (tis) revisions that are being counted. We may want further build tool work to implement a second revision counting mechanism to separate upstream revisions from stx revisions. On 2019-03-08 2:33 p.m., Scott Little wrote: > My first crack at an audit comparing most recent tag versus rpm version > > cd $MY_REPO/.. > for d in $(grep '            grep -v 'refs[/]tags[/]' | \ >            grep -v starlingx | \ >            grep -v stx-staging | \ >            sed 's#^.*path="\([^"]*\)".*$#\1#' >           ); do >     b=$(basename $d) >     t=$(cd $d >         git describe | cut -d '-' -f 1 >        ) > >     p=$(grep '\(["/]'"$b"'"$\|[=/]'"$b"'$\)' $(find . -name > build_srpm.data) | \ >         grep ':SRC_DIR=' | \ >         cut -d ':' -f 1 >        ) >     s=$(find $(dirname $p) -name '*spec') >     v=$(grep '^Version:' $s | cut -d ':' -f 2 | sed 's/[ \t]//g') >     if [ "$v" != "$t" ]; then >         echo name=$b >         echo dir=$d >         echo spec=$s >         echo tag=$t >         echo version=$v >         echo >     fi > done > > > name=python-barbicanclient > dir=cgcs-root/stx/git/python-barbicanclient > spec=./cgcs-root/stx/stx-upstream/openstack/python-barbicanclient/centos/python-barbicanclient.spec > > tag=4.8.1 > version=4.7.1 > > name=python-cinderclient > dir=cgcs-root/stx/git/python-cinderclient > spec=./cgcs-root/stx/stx-upstream/openstack/python-cinderclient/centos/python-cinderclient.spec > > tag=4.1.0 > version=4.0.1 > > name=python-glanceclient > dir=cgcs-root/stx/git/python-glanceclient > spec=./cgcs-root/stx/stx-upstream/openstack/python-glanceclient/centos/python-glanceclient.spec > > tag=2.16.0 > version=2.13.1 > > name=python-heatclient > dir=cgcs-root/stx/git/python-heatclient > spec=./cgcs-root/stx/stx-upstream/openstack/python-heatclient/centos/python-heatclient.spec > > tag=1.17.0 > version=1.16.1 > > name=python-ironicclient > dir=cgcs-root/stx/git/python-ironicclient > spec=./cgcs-root/stx/stx-upstream/openstack/python-ironicclient/centos/python-ironicclient.spec > > tag=2.7.0 > version=2.5.0 > > name=python-keystoneclient > dir=cgcs-root/stx/git/python-keystoneclient > spec=./cgcs-root/stx/stx-upstream/openstack/python-keystoneclient/centos/python-keystoneclient.spec > > tag=3.19.0 > version=3.17.0 > > name=python-magnumclient > dir=cgcs-root/stx/git/python-magnumclient > spec=./cgcs-root/stx/stx-upstream/openstack/python-magnumclient/centos/python-magnumclient.spec > > tag=2.12.0 > version=2.10.0 > > name=python-neutronclient > dir=cgcs-root/stx/git/python-neutronclient > spec=./cgcs-root/stx/stx-upstream/openstack/python-neutronclient/centos/python-neutronclient.spec > > tag=6.12.0 > version=6.9.1 > > name=python-novaclient > dir=cgcs-root/stx/git/python-novaclient > spec=./cgcs-root/stx/stx-upstream/openstack/python-novaclient/centos/python-novaclient.spec > > tag=13.0.0 > version=11.0.0 > > name=python-openstackclient > dir=cgcs-root/stx/git/python-openstackclient > spec=./cgcs-root/stx/stx-upstream/openstack/python-openstackclient/centos/python-openstackclient.spec > > tag=3.18.0 > version=3.16.2 > > name=python-openstacksdk > dir=cgcs-root/stx/git/python-openstacksdk > spec=./cgcs-root/stx/stx-upstream/openstack/python-openstacksdk/centos/python-openstacksdk.spec > > tag=0.25.0 > version=0.17.2 > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From hayde.martinez.landa at intel.com Fri Mar 8 21:34:58 2019 From: hayde.martinez.landa at intel.com (Martinez Landa, Hayde) Date: Fri, 8 Mar 2019 21:34:58 +0000 Subject: [Starlingx-discuss] [docs] Build Process FAQ Message-ID: Hi All, As part of the documentation efforts, we are working on a “Build Process FAQ” We are aware that the build process is continually evolving, and might completely change (very) soon. In the mean time we would like to provide a document that might help reducing the frustration while following the process And that can answer questions to the most common issues encountered. Our first-cut draft is here[0], right now we are gathering questions (later on we will work on the answers). We appreciate any feedback from the community, we encourage you to share your questions, comments or thoughts. [0] https://docs.google.com/document/d/1ir5LwhxNcx6P7N9IlNUWfEO16xckzPpH0gQp78QP8Bk From abraham.arce.moreno at intel.com Fri Mar 8 21:44:56 2019 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Fri, 8 Mar 2019 21:44:56 +0000 Subject: [Starlingx-discuss] Test Case Submission in rst format In-Reply-To: <3CAA827B7A79BA46B15B280EC82088FE4828CE36@ALA-MBD.corp.ad.wrs.com> References: <3CAA827B7A79BA46B15B280EC82088FE4828CE36@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Numan, > We are currently in process of submitting our test cases in stx-test git > repository. There has been a request to upload manual tests is rst format so > that they can be visible on a wiki. Thanks to you and all test team for all the support to take advantage of existing documentation infrastructure and give it a try to have it under our official documentation channel at starlingx.io > Conversion of test cases from plain text format to rst format is causing a lot > of pain and time lost. At the same time it is also not an absolute requirement > as any tester who wants to execute these test cases can easily access them > from git in text format. We understand this is a time consuming process considering the number of test cases you have and the ramp up in the learning of the RST format if automated tools are not used. Agree that the format is not relevant to execute a test case. > I am not sure about how much time is spent by Ada's team in converting > these test cases but I would suggest that we should submit them in plain text > format and if documentation team wants to convert them in rst then they > can update them. Let's add this option to the table. At the end, you as a team has the final decision and decide what is the best approach that works for you, here you have the existing options: [ Option A ] Convert all test cases to RST format and merge. [ Option B ] Keep all test cases in X format and merge. [ Option C ] Only merge what has been converted to RST format. There is no right option, again, it all depends on the needs and priorities of the team, your call. > Secondly, if these test cases are to be shown in Wiki, what is your plan for > showing them in next release? The test cases could land (one commit away to make this happen) under our official StarlingX documentation site at: https://docs.starlingx.io/ Our proposal is to add "Test" down to "Tools", under "There are several supporting projects and repositories": - Tools < pointing to https://docs.starlingx.io/stx-tools/index.html - Test < pointing to https://docs.starlingx.io/stx-test/index.html This way we are taking full advantage of the StarlingX documentation infrastructure based in OpenStack guidelines and giving a standard and formal way to present it to the community. > Would there be a release specific Wiki or a selection available to check > test cases for each release? We can discuss what are your needs in terms of versioning in our weekly meeting. As an example, we are currently working to split the installation documentation in 2 versions based in "directories": 1. Version one: old way to deploy StarlingX 2. Version two: new containerized way to deploy StarlingX More information about this "versioning" task under our meeting minutes here: https://etherpad.openstack.org/p/stx-documentation Please let us know any other question you might have. More than happy to support your team objectives. From fungi at yuggoth.org Fri Mar 8 23:04:52 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Fri, 8 Mar 2019 23:04:52 +0000 Subject: [Starlingx-discuss] Test Case Submission in rst format In-Reply-To: <3CAA827B7A79BA46B15B280EC82088FE4828CE36@ALA-MBD.corp.ad.wrs.com> References: <3CAA827B7A79BA46B15B280EC82088FE4828CE36@ALA-MBD.corp.ad.wrs.com> Message-ID: <20190308230451.qocq22wwdfrk2cp5@yuggoth.org> On 2019-03-08 14:12:21 +0000 (+0000), Waheed, Numan wrote: > We are currently in process of submitting our test cases in > stx-test git repository. There has been a request to upload manual > tests is rst format so that they can be visible on a wiki. Which wiki are you using? If this is for wiki.openstack.org it does not support reStructuredText format, but rather a special MediaWiki markup language. > Conversion of test cases from plain text format to rst format is > causing a lot of pain and time lost. At the same time it is also > not an absolute requirement as any tester who wants to execute > these test cases can easily access them from git in text format. [...] If this is in service of being able to build static HTML representations with Sphinx, a useful stepping-stone is to create empty rst documents (perhaps with just a page heading) and then use the include:: directive with the :literal: argument to embed preformatted text from another file elsewhere in the same Git repository. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From bruce.e.jones at intel.com Fri Mar 8 23:26:51 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 8 Mar 2019 23:26:51 +0000 Subject: [Starlingx-discuss] [Docs] Mega spec updated, please approve Message-ID: <9A85D2917C58154C960D95352B22818BD06F32AC@fmsmsx123.amr.corp.intel.com> The Docs mega spec has been updated and should address all current feedback. Including Ian's feedback from the TSC and Greg's feedback from a private email. It also now includes SB numbers for all documents that have been identified as VH priority and release gating. Those stories have all been created. Here is the review: https://review.openstack.org/#/c/635641 You can find the stories pending in the Docs team here: https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.docs The Docs team is looking for volunteers who can help complete all of these stories. brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Sat Mar 9 01:07:38 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Sat, 9 Mar 2019 01:07:38 +0000 Subject: [Starlingx-discuss] Daylight Savings Time In-Reply-To: <586E8B730EA0DA4A9D6A80A10E486BC0A15AC4@ALA-MBD.corp.ad.wrs.com> References: <9A85D2917C58154C960D95352B22818BD06F2DF8@fmsmsx123.amr.corp.intel.com> <586E8B730EA0DA4A9D6A80A10E486BC0A15AC4@ALA-MBD.corp.ad.wrs.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35EBFC49@SHSMSX104.ccr.corp.intel.com> +1 good for China attendees. :) From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] Sent: Saturday, March 9, 2019 3:30 AM To: Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Daylight Savings Time +1 from me From: Jones, Bruce E > Sent: Friday, March 8, 2019 2:25 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Daylight Savings Time This weekend many of us switch from standard time to daylight time, as we Spring Forward an hour. As I recall, when we switched from daylight to standard last year, we agreed to keep all meetings in the timezones that are switching at the same clock time while making everyone else move their meetings around. Is that what we want to do for our meetings next week? brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Sat Mar 9 07:46:21 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 9 Mar 2019 02:46:21 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 183 - Failure! Message-ID: <460780699.75.1552117582718.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 183 Status: Failure Timestamp: 20190309T060701Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190309T060000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190309T060000Z DOCKER_BUILD_ID: jenkins-master-20190309T060000Z-builder MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190309T060000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190309T060000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Sat Mar 9 07:46:25 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 9 Mar 2019 02:46:25 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 11 - Failure! Message-ID: <965754554.78.1552117586548.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 11 Status: Failure Timestamp: 20190309T060000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190309T060000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false BUILD_CONTAINERS_ZZZ: false From liang.a.fang at intel.com Sat Mar 9 12:34:06 2019 From: liang.a.fang at intel.com (Fang, Liang A) Date: Sat, 9 Mar 2019 12:34:06 +0000 Subject: [Starlingx-discuss] Anybody know how to add internal tenant id in cinder.conf? Message-ID: Hi openstack-helm cores In cinder's raw cache guider, internal tenant id (cinder_internal_tenant_project_id and cinder_internal_tenant_user_id) need to be set in cinder.conf: Something like: cinder_internal_tenant_project_id = PROJECT_ID cinder_internal_tenant_user_id = USER_ID refer: https://docs.openstack.org/cinder/latest/admin/blockstorage-image-volume-cache.html I took an investigation, this should be done in cinder's configmap-etc.yaml: ./cinder/templates/configmap-etc.yaml The problem is: the cinder_internal_tenant_project_id and cinder_internal_tenant_user_id are created dynamically, not in values.yaml, in starlingx project we also cannot override in helm/cinder.py because at the time of running helm/cinder.py keystone is not ready. Anybody know how to solve this issue? How to get cinder_internal_tenant_project_id and cinder_internal_tenant_user_id in configmap-etc.yaml and set to cinder.conf? Thanks a lot. I created a story for this: https://storyboard.openstack.org/#!/story/2005189 Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From vm.rod25 at gmail.com Sun Mar 10 15:53:42 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Sun, 10 Mar 2019 09:53:42 -0600 Subject: [Starlingx-discuss] STX performance tests update Message-ID: Hi team After some research on the topic and the great help from Numan's team, I came into this great presentation about how to use OPNFV for performance metrics (video available at [0]): https://www.openstack.org/assets/presentation-media/OpenStack-Summit-Vancouver-OPNFV-Test-tools-2.pdf It was presented on May 2018 OpenStack Summit, Here is described Yardstick Test Case for performance measurement, They do have a very good wiki on how to do : Installation and run: http://artifacts.opnfv.org/yardstick/colorado/2.0/docs/userguide/index.html#document-07-installation Description of every test case : https://docs.opnfv.org/en/stable-fraser/submodules/yardstick/docs/testing/user/userguide/15-list-of-tcs.html After a quick view, Yardstick has the capability to measure performance in 3 sections: * Compute * Storage * Network With multiple tests cases for each one ( slide 13 of presentation ) This is a simple update to keep the community informed about the progress on this topic, if someone has any feedback, please let me know. Numan/ Peng thanks a lot for the document, after reading I realize it is focused on Tempest ( which is used by OPNFV but as part of Functest, which is the test framework provided to answer the question: Does my infrastructure simply work as expected?. Regards BTW, sorry for the long delay of an update for this topic Victor Rodriguez [0] https://www.youtube.com/watch?v=RxMbF8ILl-M From huifeng.le at intel.com Mon Mar 11 02:05:55 2019 From: huifeng.le at intel.com (Le, Huifeng) Date: Mon, 11 Mar 2019 02:05:55 +0000 Subject: [Starlingx-discuss] [Neutron] Question on uwsgi based web server support for neutron In-Reply-To: References: <76647BD697F40748B1FA4F56DA02AA0B4D595BCF@SHSMSX104.ccr.corp.intel.com> <7B5D39C4-7B28-488F-A731-0831D0B44F7C@redhat.com> <76647BD697F40748B1FA4F56DA02AA0B4D595D05@SHSMSX104.ccr.corp.intel.com> Message-ID: <76647BD697F40748B1FA4F56DA02AA0B4D59E0E3@SHSMSX104.ccr.corp.intel.com> Sean and Slawek, Thanks much for the comments! So What the process to propose this default configuration for Train cycle? Thanks much! Best Regards, Le, Huifeng -----Original Message----- From: Sean Mooney [mailto:smooney at redhat.com] Sent: Tuesday, March 5, 2019 10:52 PM To: Slawomir Kaplonski ; Le, Huifeng Cc: Miguel Lavalle ; Khalil, Ghada ; starlingx-discuss at lists.starlingx.io; openstack-dev at lists.openstack.org Subject: Re: [Neutron] Question on uwsgi based web server support for neutron On Tue, 2019-03-05 at 08:53 +0100, Slawomir Kaplonski wrote: > Hi, > > I don’t know about any plans to make it default now in Stein. IMO We can think about it in Train cycle. for what its worth i dont think project actully have default in repect to eventlets vs wsgi it really the installer that do have default. keystone i think is the only project that "defults" to wsgi and that is because they delete the eventlet version if i am not miss remembering. that said i do think that more project should consider moving to wsgi only. eventually i would hope we could drop all eventlet depencies in openstack but i know that for several of the agents like the nova agent that is hard to do. for the apis however wsgi provided a convent way to drop that depency and improve performance at the same time. > > > Wiadomość napisana przez Le, Huifeng w dniu 05.03.2019, o godz. 08:37: > > > > Slawek, > > > > Thanks much for the information. Yes, it is already possible to > > configure using uswgi for neutron API which is also the way I used to verify the issue. > > > > So will it be used as default configuration (as other openstack > > projects) for neutron in any planned release? or it supposed to require the system admin to apply this configuration manually when deployment? thanks much! > > > > Best Regards, > > Le, Huifeng > > > > -----Original Message----- > > From: Slawomir Kaplonski [mailto:skaplons at redhat.com] > > Sent: Tuesday, March 5, 2019 3:20 PM > > To: Le, Huifeng > > Cc: Miguel Lavalle ; Khalil, Ghada > > ; starlingx-discuss at lists.starlingx.io; > > openstack-dev at lists.openstack.org > > Subject: Re: [Neutron] Question on uwsgi based web server support > > for neutron > > > > Hi, > > > > > Wiadomość napisana przez Le, Huifeng w dniu 05.03.2019, o godz. 03:26: > > > > > > Miguel, > > > > > > During STX deployment process, it is found the current neutron > > > eventlet based web server has some unexpected behavior for > > > multiple long live clients and it is also verified that apache WSGI/uwsgi based web server can solve such issues. the detail information of this issue can be found at https://bugs.launchpad.net/neutron/+bug/1800599. > > > > > > > > > So is there any plan or roadmap to switch to the new apache > > > WSGI/uswgi based web server for Neutron in Stein release? Thanks much! > > > > AFAIK it is already possible since Rocky > > https://docs.openstack.org/neutron/rocky/admin/config-wsgi.html > > Is it what You are asking for? > > > > > > > > Best Regards, > > > Le, Huifeng > > > > — > > Slawek Kaplonski > > Senior software engineer > > Red Hat > > > > — > Slawek Kaplonski > Senior software engineer > Red Hat > > From shuicheng.lin at intel.com Mon Mar 11 04:32:42 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Mon, 11 Mar 2019 04:32:42 +0000 Subject: [Starlingx-discuss] QAT driver upugrade Message-ID: <9700A18779F35F49AF027300A49E7C765FE9A652@SHSMSX101.ccr.corp.intel.com> Hi Ghada, Here is the release notes for the latest QAT(1.7.L.4.4.0-00023). https://01.org/sites/default/files/downloads//336211-009qatrelnotes.pdf The release notes just list some issue fixed since 1.0.3-42, which is the version StarlingX using currently. Could you help ask expert from WR to review it, and decide whether we prefer to upgrade it or not? If we choose to upgrade it, could you help share me the test case for QAT driver? Thanks. Best Regards Shuicheng From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Monday, February 4, 2019 11:00 PM To: Lin, Shuicheng ; Waheed, Numan ; Perez, Ricardo O ; Xie, Cindy ; Cabrales, Ada Cc: starlingx-discuss at lists.starlingx.io Subject: RE: CentOS 7.6 rebase feature testing Thanks Shuicheng. Is there a need to actually upversion the qat drivers? Are there new features or bug fixes that are of interest to StarlingX? I suggest you review the release notes and make a decision with the distro.other team leads before proceeding with this item. Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Wednesday, January 30, 2019 7:34 PM To: Khalil, Ghada; Waheed, Numan; Perez, Ricardo O; Xie, Cindy; Cabrales, Ada Cc: starlingx-discuss at lists.starlingx.io Subject: RE: CentOS 7.6 rebase feature testing Hi all, Story is created to track this task: https://storyboard.openstack.org/#!/story/2004901 Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, January 31, 2019 7:56 AM To: Khalil, Ghada >; Waheed, Numan >; Perez, Ricardo O >; Xie, Cindy >; Cabrales, Ada > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] CentOS 7.6 rebase feature testing Hi Ghada, QAT driver is not upgraded yet, since there is no build failure with CentOS 7.6. I will have a check with it after Chinese New Year's holiday, and plan to do the upgrade in master. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Mon Mar 11 07:01:16 2019 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 11 Mar 2019 00:01:16 -0700 Subject: [Starlingx-discuss] CentOS 7.6 feature branch ready to merge to master Message-ID: <090518b8-7b6b-6ec1-566d-50e4c9b0bf50@linux.intel.com> Folks, I pushed 5 reviews [0] to gerrit for merging to master, these have been tested by Shuicheng and are ready for the next level of testing as part of master. Sau! [0] https://review.openstack.org/#/q/topic:merge-f/centos-76+(status:open+OR+status:merged) From shuicheng.lin at intel.com Mon Mar 11 08:10:06 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Mon, 11 Mar 2019 08:10:06 +0000 Subject: [Starlingx-discuss] CentOS 7.6 feature branch ready to merge to master In-Reply-To: <090518b8-7b6b-6ec1-566d-50e4c9b0bf50@linux.intel.com> References: <090518b8-7b6b-6ec1-566d-50e4c9b0bf50@linux.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C765FE9A875@SHSMSX101.ccr.corp.intel.com> Hi Saul, I checked the patches, but the content in gitweb seem like they are from master to centos76 feature branch. Need your double confirm on it. Thanks. Another thing we need take care is, the change in .gitreview file should not be merged to master, since it is branch specific change. Best Regards Shuicheng -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Monday, March 11, 2019 3:01 PM To: starlingx-discuss at lists.starlingx.io Cc: Lin, Shuicheng Subject: CentOS 7.6 feature branch ready to merge to master Folks, I pushed 5 reviews [0] to gerrit for merging to master, these have been tested by Shuicheng and are ready for the next level of testing as part of master. Sau! [0] https://review.openstack.org/#/q/topic:merge-f/centos-76+(status:open+OR+status:merged) From sgw at linux.intel.com Mon Mar 11 08:28:43 2019 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 11 Mar 2019 01:28:43 -0700 Subject: [Starlingx-discuss] CentOS 7.6 feature branch ready to merge to master In-Reply-To: <9700A18779F35F49AF027300A49E7C765FE9A875@SHSMSX101.ccr.corp.intel.com> References: <090518b8-7b6b-6ec1-566d-50e4c9b0bf50@linux.intel.com> <9700A18779F35F49AF027300A49E7C765FE9A875@SHSMSX101.ccr.corp.intel.com> Message-ID: <3aec662e-f8cd-212c-9262-74ebecde2ae0@linux.intel.com> On 3/11/19 1:10 AM, Lin, Shuicheng wrote: > Hi Saul, > I checked the patches, but the content in gitweb seem like they are from master to centos76 feature branch. > Need your double confirm on it. > Thanks. > I guess I goofed this up, I will abandon this patch set and check with Dean on what the correct recipe/command set is for merging back into master. > Another thing we need take care is, the change in .gitreview file should not be merged to master, since it is branch specific change. > I am sure this will get taken care of correctly also once I check with Dean. Sau! > Best Regards > Shuicheng > > > -----Original Message----- > From: Saul Wold [mailto:sgw at linux.intel.com] > Sent: Monday, March 11, 2019 3:01 PM > To: starlingx-discuss at lists.starlingx.io > Cc: Lin, Shuicheng > Subject: CentOS 7.6 feature branch ready to merge to master > > > Folks, > > I pushed 5 reviews [0] to gerrit for merging to master, these have been tested by Shuicheng and are ready for the next level of testing as part of master. > > Sau! > > [0] > https://review.openstack.org/#/q/topic:merge-f/centos-76+(status:open+OR+status:merged) > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From himanshugoyal500 at gmail.com Mon Mar 11 11:44:19 2019 From: himanshugoyal500 at gmail.com (Himanshu Goyal) Date: Mon, 11 Mar 2019 17:14:19 +0530 Subject: [Starlingx-discuss] Changing Controller IP Address Message-ID: Hi Team, I deployed starlingX with 2 physical servers ( 1 controller Node & 1 Compute Node). But i would like to change the ip-address of my controller Machine without reinstalling all services because i don't want to lose all my data and configurations. Please suggest if there is any way to do that. Regards, Himanshu Goyal -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Mon Mar 11 13:25:47 2019 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Mon, 11 Mar 2019 13:25:47 +0000 Subject: [Starlingx-discuss] Warning: /etc/nova/openrc is going away Message-ID: This is a heads up to anyone who is currently using the /etc/nova/openrc file in their own local scripts. In the next day or two the /etc/nova/openrc file will no longer exist on the controller. The /etc/nova/openrc file was deprecated and replaced by /etc/platform/openrc a while back. The wikis are already updated and utilities that reference it are being updated. This is part of removing the unused openstack components from the controller. https://storyboard.openstack.org/#!/story/2004764 This warning is mostly aimed at anyone who has their own private scripts or macros, to be aware that they will need to change. Al -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Mon Mar 11 14:02:54 2019 From: scott.little at windriver.com (Scott Little) Date: Mon, 11 Mar 2019 10:02:54 -0400 Subject: [Starlingx-discuss] [build] Proposed change to the timing of the cengn build Message-ID: <66dcbef7-2f4e-812b-b9e2-decc1212a1ef@windriver.com> Currently the CENGN build is scheduled for a 1 am EST start time.  A build from scratch takes ~ 3 hours, or ~ 5 hours if docker images are included in the build.  Docker images are built for availability Tuesday morning (North America) A request has been put forward by the Wind River test team to have loads ready by midnight EST.  This means push forward the build to 8:30 pm EST most nights, and 6:30 pm EST if a docker image is to be built.  This would allow a same day sanity to be run on hardware labs overnight.  With the current scheduling, hardware sanity has to wait till the evening of the following day. Are there any concerns with the new build times? Scott From Frank.Miller at windriver.com Mon Mar 11 14:26:08 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 11 Mar 2019 14:26:08 +0000 Subject: [Starlingx-discuss] Agenda for Containerization Meeting: Focus on 27 active SBs Message-ID: Today's agenda will focus primarily on the outstanding SBs. If you are prime on one of the active SBs please attend. Etherpad is here: https://etherpad.openstack.org/p/stx-containerization Agenda: 1. StoryBoard status - updates from prime(s) for subset of open SBs: General query: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.containers&project_group_id=86 - Rebase bare metal keystone and horizon to OpenStack master [Tyler] - Local Docker Registry [Jerry] - Replication of mariadb for containerization [Chris Friesen] - Generalized Interface and Network Configuration [Teresa] - Enable https support for containerized openstack endpoints [Teresa] - Kubernetes Cluster Network Configuration [Teresa] - Removal of bare metal Openstack related code [Al] - CEPH persistent storage backend for Kubernetes [Ovidiu] - Container pinning on worker nodes and All-in-one servers [Jim Gauld] - Enable CPU manager static policy for non-openstack worker nodes [Jim Gauld] - Armada Integration [ 2 tasks unassigned] - Infrastructure HELM Chart Override Generation [multiple: Gerry, Kristine, Joseph] - Create HELM chart for Fault project [Mario/Mingyuan] - Neutron Host Management Integration [Kevin] - Add support for k8s labels to inventory panel [Yan] - Huge page management [Austin] - Support for OVS as the default virtual switch [Huifeng] - Containerize the ironic service [Mingyuan] 2. Update on subset of LPs: General query: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.containers a) Higher priority: - #1814595 Containers: Kernel call trace Task jbd2 blocked [Bob/Jim] - Issue is seen on CentOS7.6 as well. Kernel hang in jbd2 as a result of rbd usage - #1818118 Containers: vm unreachable for minutes after live migration or vm reboot [Joseph] b) Other LPs of particular interest: - 3 related to re-apply failures [John] - Controller ungraceful reboots [Bart] c) Other notable LPs 3. Other topics? Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Mon Mar 11 14:41:37 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Mon, 11 Mar 2019 14:41:37 +0000 Subject: [Starlingx-discuss] CentOS 7.6 feature branch ready to merge to master In-Reply-To: <3aec662e-f8cd-212c-9262-74ebecde2ae0@linux.intel.com> References: <090518b8-7b6b-6ec1-566d-50e4c9b0bf50@linux.intel.com> <9700A18779F35F49AF027300A49E7C765FE9A875@SHSMSX101.ccr.corp.intel.com> <3aec662e-f8cd-212c-9262-74ebecde2ae0@linux.intel.com> Message-ID: <20190311144136.qvytqg7ryhl454qw@yuggoth.org> On 2019-03-11 01:28:43 -0700 (-0700), Saul Wold wrote: > On 3/11/19 1:10 AM, Lin, Shuicheng wrote: [...] > > Another thing we need take care is, the change in .gitreview > > file should not be merged to master, since it is branch specific > > change. > > I am sure this will get taken care of correctly also once I check > with Dean. [...] Some guidance for this can be found in a subsection of the Feature Branches recommendations in the Infra Manual: https://docs.openstack.org/infra/manual/drivers.html#how-to-avoid-merging-specific-files -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From dtroyer at gmail.com Mon Mar 11 15:18:42 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Mon, 11 Mar 2019 10:18:42 -0500 Subject: [Starlingx-discuss] CentOS 7.6 feature branch ready to merge to master In-Reply-To: <3aec662e-f8cd-212c-9262-74ebecde2ae0@linux.intel.com> References: <090518b8-7b6b-6ec1-566d-50e4c9b0bf50@linux.intel.com> <9700A18779F35F49AF027300A49E7C765FE9A875@SHSMSX101.ccr.corp.intel.com> <3aec662e-f8cd-212c-9262-74ebecde2ae0@linux.intel.com> Message-ID: On Mon, Mar 11, 2019 at 3:28 AM Saul Wold wrote: > > Another thing we need take care is, the change in .gitreview file should not be merged to master, since it is branch specific change. > > I am sure this will get taken care of correctly also once I check with Dean. I think the .gitreview is the only real problem you had? I do the merge back to master following https://wiki.openstack.org/wiki/StarlingX/Branches#Feature_Branches and swapping the 'master' and '$feature_branch' in the arguments. It results in the same thing, just depends on which branch you are in at the time of the merge. Just below that is the command to fix up .gitreview (whick we skip when going master -> $feature_branch). I've re-done stx-integ[0], stx-root[1], stx-tools[2] and stx-upstream[3]. stx-manifest does not appear to have any changes to master required (the only new bits in the feature branch are the revision="" attributes that master doesn't want). [0] https://review.openstack.org/642481 [1] https://review.openstack.org/642487 [2] https://review.openstack.org/642485 [3] https://review.openstack.org/642486 dt -- Dean Troyer dtroyer at gmail.com From juan.carlos.alonso at intel.com Mon Mar 11 17:50:50 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Mon, 11 Mar 2019 17:50:50 +0000 Subject: [Starlingx-discuss] openstack network segment range create FAILED Message-ID: <8557B550001AFB46A43A0CCC314BF85153CA97B8@FMSMSX108.amr.corp.intel.com> Hi, In "Providernetworking setup: Network Segment Ranges (Stein)" section, in the second command: openstack network segment range create ${PHYSNET0}-b --network-type vlan --physical-network ${PHYSNET0} --minimum 10 --maximum 10 --shared I got the following error: BadRequestException: 400: Client Error for url: http://neutron.openstack.svc.cluster.local:80/v2.0/network_segment_ranges, Invalid input for tenant_id. Reason: 'None' is not a valid string. I tried to add --project ${ADMINID} but --project is only allowed with --private. Has this command been updated? Because the wiki does not show an update. Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From Numan.Waheed at windriver.com Mon Mar 11 19:56:20 2019 From: Numan.Waheed at windriver.com (Waheed, Numan) Date: Mon, 11 Mar 2019 19:56:20 +0000 Subject: [Starlingx-discuss] [ Testing ] Meeting agenda - 03/12/2019 Message-ID: <3CAA827B7A79BA46B15B280EC82088FE4828DD97@ALA-MBD.corp.ad.wrs.com> Agenda for 03/12/2019 1. Plan Progress check - 30 Min Update Release Plan with planned dates Regression Suite Submission to the repo Distro.OpenStack patch elimination - Progress on test plan definition CentOS 7.6 testing after merge OVS-DPDK upgrade Test Case Automation Stress and Stability Testing 2. Format for Manual Test Cases - txt vs. rst - 10 Min 3. Dashboard Follow-up - 05 Min 4. Opens - 15 Min Please let me know if you would like to add anything in this agenda. Regards, Numan. -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Mon Mar 11 23:19:00 2019 From: serverascode at gmail.com (Curtis) Date: Mon, 11 Mar 2019 19:19:00 -0400 Subject: [Starlingx-discuss] STX performance tests update In-Reply-To: References: Message-ID: On Sun, Mar 10, 2019 at 11:54 AM Victor Rodriguez wrote: > Hi team > > After some research on the topic and the great help from Numan's team, > I came into this great presentation about how to use OPNFV for > performance metrics (video available at [0]): > > > https://www.openstack.org/assets/presentation-media/OpenStack-Summit-Vancouver-OPNFV-Test-tools-2.pdf > > It was presented on May 2018 OpenStack Summit, Here is described > Yardstick Test Case for performance measurement, They do have a very > good wiki on how to do : > > Installation and run: > > http://artifacts.opnfv.org/yardstick/colorado/2.0/docs/userguide/index.html#document-07-installation > > Description of every test case : > > https://docs.opnfv.org/en/stable-fraser/submodules/yardstick/docs/testing/user/userguide/15-list-of-tcs.html > > After a quick view, Yardstick has the capability to measure > performance in 3 sections: > > * Compute > * Storage > * Network > > With multiple tests cases for each one ( slide 13 of presentation ) > > This is a simple update to keep the community informed about the > progress on this topic, if someone has any feedback, please let me > know. > I haven't used Yardstick, but it sounds like a step in the right direction. Perhaps we can find things to push back upstream to OPNFV. What I'm hoping is that we can use the Packet.com resources that should be available soon to run automated performance tests and then publish the results on a continual basis. I'm definitely interested in helping out. :) Thanks, Curtis > > Numan/ Peng thanks a lot for the document, after reading I realize it > is focused on Tempest ( which is used by OPNFV but as part of > Functest, which is the test framework provided to answer the question: > Does my infrastructure simply work as expected?. > > Regards > > BTW, sorry for the long delay of an update for this topic > > Victor Rodriguez > > [0] https://www.youtube.com/watch?v=RxMbF8ILl-M > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Tue Mar 12 01:16:09 2019 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 11 Mar 2019 18:16:09 -0700 Subject: [Starlingx-discuss] CentOS 7.6 feature branch ready to merge to master In-Reply-To: References: <090518b8-7b6b-6ec1-566d-50e4c9b0bf50@linux.intel.com> <9700A18779F35F49AF027300A49E7C765FE9A875@SHSMSX101.ccr.corp.intel.com> <3aec662e-f8cd-212c-9262-74ebecde2ae0@linux.intel.com> Message-ID: Dean, Thanks for handling this, I will review these docs today. Can someone from the stx-upstream core team provide a +W to this review [0], it has 2 +2s but needs the +W Thanks Sau! [0] https://review.openstack.org/#/c/642486/ On 3/11/19 8:18 AM, Dean Troyer wrote: > On Mon, Mar 11, 2019 at 3:28 AM Saul Wold wrote: >>> Another thing we need take care is, the change in .gitreview file should not be merged to master, since it is branch specific change. >> >> I am sure this will get taken care of correctly also once I check with Dean. > > I think the .gitreview is the only real problem you had? I do the > merge back to master following > https://wiki.openstack.org/wiki/StarlingX/Branches#Feature_Branches > and swapping the 'master' and '$feature_branch' in the arguments. It > results in the same thing, just depends on which branch you are in at > the time of the merge. > > Just below that is the command to fix up .gitreview (whick we skip > when going master -> $feature_branch). > > I've re-done stx-integ[0], stx-root[1], stx-tools[2] and > stx-upstream[3]. stx-manifest does not appear to have any changes to > master required (the only new bits in the feature branch are the > revision="" attributes that master doesn't want). > > [0] https://review.openstack.org/642481 > [1] https://review.openstack.org/642487 > [2] https://review.openstack.org/642485 > [3] https://review.openstack.org/642486 > > dt > From vm.rod25 at gmail.com Tue Mar 12 02:20:56 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Mon, 11 Mar 2019 20:20:56 -0600 Subject: [Starlingx-discuss] STX performance tests update In-Reply-To: References: Message-ID: On Mon, Mar 11, 2019 at 5:19 PM Curtis wrote: > > > > On Sun, Mar 10, 2019 at 11:54 AM Victor Rodriguez wrote: >> >> Hi team >> >> After some research on the topic and the great help from Numan's team, >> I came into this great presentation about how to use OPNFV for >> performance metrics (video available at [0]): >> >> https://www.openstack.org/assets/presentation-media/OpenStack-Summit-Vancouver-OPNFV-Test-tools-2.pdf >> >> It was presented on May 2018 OpenStack Summit, Here is described >> Yardstick Test Case for performance measurement, They do have a very >> good wiki on how to do : >> >> Installation and run: >> http://artifacts.opnfv.org/yardstick/colorado/2.0/docs/userguide/index.html#document-07-installation >> >> Description of every test case : >> https://docs.opnfv.org/en/stable-fraser/submodules/yardstick/docs/testing/user/userguide/15-list-of-tcs.html >> >> After a quick view, Yardstick has the capability to measure >> performance in 3 sections: >> >> * Compute >> * Storage >> * Network >> >> With multiple tests cases for each one ( slide 13 of presentation ) >> >> This is a simple update to keep the community informed about the >> progress on this topic, if someone has any feedback, please let me >> know. > > > I haven't used Yardstick, but it sounds like a step in the right direction. Perhaps we can find things to push back upstream to OPNFV. > > What I'm hoping is that we can use the Packet.com resources that should be available soon to run automated performance tests and then publish the results on a continual basis. I'm definitely interested in helping out. :) > > Thanks, > Curtis > Thanks a lot Curtis, CI/CD definitely is the next step ones I could enable this from the developer perspective. My goal is to provide a simple tutorial/script to run a test on a pre-configured and working STX cloud system that developers could use to measure their changes. Once I have this and make a demo I will ping you to try in your dev machine and then TSC can decide to deploy this on Packet. The good thing about Yardstick is that it has a connection to grafana so we don't have to worry about a dashboard : ) . The concern that I have (that I would like input from the TSC) is how to define what configuration we want to use on Packet as baseline configuration, this is important because a change in the configuration might represent a huge change in performance results. Also, are we ok to compare the STX results against regular OpenStack Performanceomrance numbers is always hard to handle since they are very senitive. I would like to bring this topic to the TSC or comunity meeting so we can tak e a decision as comunity. My work might finish when we could have a way to get the numbers, publication, and track of them might be a decision out of my scope. I will keep you posted Regards > >> >> >> Numan/ Peng thanks a lot for the document, after reading I realize it >> is focused on Tempest ( which is used by OPNFV but as part of >> Functest, which is the test framework provided to answer the question: >> Does my infrastructure simply work as expected?. >> >> Regards >> >> BTW, sorry for the long delay of an update for this topic >> >> Victor Rodriguez >> >> [0] https://www.youtube.com/watch?v=RxMbF8ILl-M >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > -- > Blog: serverascode.com From juan.carlos.alonso at intel.com Tue Mar 12 02:31:14 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Tue, 12 Mar 2019 02:31:14 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190311 Message-ID: <8557B550001AFB46A43A0CCC314BF85153CA9958@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Mar-11 (link) Status: YELLOW =========================================== Sanity Test is executed in a Containers - Bare Metal Environment Simplex Setup Manual [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [PASS] Sanity Platform 05 TCs [PASS] TOTAL: [58 TCs PASS | 01 TCs FAIL ] Duplex Setup Manual [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [PASS] Sanity Platform 03 TCs [FAIL] TOTAL: [53 TCs PASS | 04 TCs FAIL ] Standard Local Storage (2+2) Setup Manual [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 16 TCs [PASS] | 33 TCS [FAIL] Sanity Platform 03 TCs [PASS] TOTAL: [ 20 TCs PASS | 34 TCs FAIL ] Standard External Storage (2+2+2) Setup Manual [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [PASS] Sanity Platform 03 TCs [PASS] TOTAL: [ 56 TCs PASS | 01 TCs FAIL ] =========================================== Sanity Test is executed in a Containers - Virtual Environment Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [PASS] Sanity Platform 05 TCs [PASS] TOTAL: [ 61 TCs PASS | 01 TCs FAIL ] Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 29 TCs [PASS] | 23 TCS [FAIL] Sanity Platform 03 TCs [FAIL] TOTAL: [ 37 TCs PASS | 23 TCs FAIL ] ------------------------------------------------------------------ openstack network segment range create FAILED Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1819541 Duplex virtual, Duplex Bare Metal, Standard Local Storage Bare Metal and Standard External Storage configurations suddenly swacted during Sanity Test and cause a lot of test cases fail, debugging in progress to know if it is a real issue or not. Also will check in next release if behavior is still present. ------------------------------------------------------------------ This is the list of test cases executed: https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Mar 12 08:03:38 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 12 Mar 2019 04:03:38 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 186 - Failure! Message-ID: <988363005.83.1552377820142.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 186 Status: Failure Timestamp: 20190312T061216Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190312T050000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190312T050000Z DOCKER_BUILD_ID: jenkins-master-20190312T050000Z-builder MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190312T050000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190312T050000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Tue Mar 12 08:03:42 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 12 Mar 2019 04:03:42 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 14 - Failure! Message-ID: <939516032.86.1552377823636.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 14 Status: Failure Timestamp: 20190312T050000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190312T050000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false BUILD_CONTAINERS_ZZZ: false From kailun.qin at intel.com Tue Mar 12 09:59:25 2019 From: kailun.qin at intel.com (Qin, Kailun) Date: Tue, 12 Mar 2019 09:59:25 +0000 Subject: [Starlingx-discuss] openstack network segment range create FAILED In-Reply-To: <8557B550001AFB46A43A0CCC314BF85153CA97B8@FMSMSX108.amr.corp.intel.com> References: <8557B550001AFB46A43A0CCC314BF85153CA97B8@FMSMSX108.amr.corp.intel.com> Message-ID: Hi Juan Carlos, I can reproduce this issue locally. This is a regression issue due to the requirement change of the network-segment-range OSC CLI during the feature patch review. I've filed bugs [1][2] and submitted patches [3][4] for them. Currently you can work around this by not specifying --shared and it'll default to a shared range. Let me know if any further question. Thanks a lot. BR, Kailun [1] https://storyboard.openstack.org/#!/story/2005205 [2] https://storyboard.openstack.org/#!/story/2005206 [3] https://review.openstack.org/#/c/642707/ [4] https://review.openstack.org/#/c/642708/ From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Tuesday, March 12, 2019 1:51 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] openstack network segment range create FAILED Hi, In "Providernetworking setup: Network Segment Ranges (Stein)" section, in the second command: openstack network segment range create ${PHYSNET0}-b --network-type vlan --physical-network ${PHYSNET0} --minimum 10 --maximum 10 --shared I got the following error: BadRequestException: 400: Client Error for url: http://neutron.openstack.svc.cluster.local:80/v2.0/network_segment_ranges, Invalid input for tenant_id. Reason: 'None' is not a valid string. I tried to add --project ${ADMINID} but --project is only allowed with --private. Has this command been updated? Because the wiki does not show an update. Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Tue Mar 12 12:31:10 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 12 Mar 2019 12:31:10 +0000 Subject: [Starlingx-discuss] CentOS 7.6 feature branch ready to merge to master In-Reply-To: References: <090518b8-7b6b-6ec1-566d-50e4c9b0bf50@linux.intel.com> <9700A18779F35F49AF027300A49E7C765FE9A875@SHSMSX101.ccr.corp.intel.com> <3aec662e-f8cd-212c-9262-74ebecde2ae0@linux.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35EC5FF9@SHSMSX104.ccr.corp.intel.com> Dean/Shuicheng, I noticed that all 4 patches below are now fully merged to Master - that's all for CentOS7.6, correct? Can we declare that we now have full CentOS7.6 support in StarlingX Master now? we may want to monitor the build and test results for today and see if there is any unexpected issues identified. Thx. - cindy -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Monday, March 11, 2019 11:19 PM To: Saul Wold Cc: starlingx Subject: Re: [Starlingx-discuss] CentOS 7.6 feature branch ready to merge to master On Mon, Mar 11, 2019 at 3:28 AM Saul Wold wrote: > > Another thing we need take care is, the change in .gitreview file should not be merged to master, since it is branch specific change. > > I am sure this will get taken care of correctly also once I check with Dean. I think the .gitreview is the only real problem you had? I do the merge back to master following https://wiki.openstack.org/wiki/StarlingX/Branches#Feature_Branches and swapping the 'master' and '$feature_branch' in the arguments. It results in the same thing, just depends on which branch you are in at the time of the merge. Just below that is the command to fix up .gitreview (whick we skip when going master -> $feature_branch). I've re-done stx-integ[0], stx-root[1], stx-tools[2] and stx-upstream[3]. stx-manifest does not appear to have any changes to master required (the only new bits in the feature branch are the revision="" attributes that master doesn't want). [0] https://review.openstack.org/642481 [1] https://review.openstack.org/642487 [2] https://review.openstack.org/642485 [3] https://review.openstack.org/642486 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 shuicheng.lin at intel.com Tue Mar 12 12:40:10 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Tue, 12 Mar 2019 12:40:10 +0000 Subject: [Starlingx-discuss] CentOS 7.6 feature branch ready to merge to master In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F35EC5FF9@SHSMSX104.ccr.corp.intel.com> References: <090518b8-7b6b-6ec1-566d-50e4c9b0bf50@linux.intel.com> <9700A18779F35F49AF027300A49E7C765FE9A875@SHSMSX101.ccr.corp.intel.com> <3aec662e-f8cd-212c-9262-74ebecde2ae0@linux.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC5FF9@SHSMSX104.ccr.corp.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C765FE9AC35@SHSMSX101.ccr.corp.intel.com> Hi Cindy, Yes, we already have all change in centos76 feature branch merged back to Master. Best Regards Shuicheng -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Tuesday, March 12, 2019 8:31 PM To: Dean Troyer ; Saul Wold Cc: starlingx Subject: Re: [Starlingx-discuss] CentOS 7.6 feature branch ready to merge to master Dean/Shuicheng, I noticed that all 4 patches below are now fully merged to Master - that's all for CentOS7.6, correct? Can we declare that we now have full CentOS7.6 support in StarlingX Master now? we may want to monitor the build and test results for today and see if there is any unexpected issues identified. Thx. - cindy -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Monday, March 11, 2019 11:19 PM To: Saul Wold Cc: starlingx Subject: Re: [Starlingx-discuss] CentOS 7.6 feature branch ready to merge to master On Mon, Mar 11, 2019 at 3:28 AM Saul Wold wrote: > > Another thing we need take care is, the change in .gitreview file should not be merged to master, since it is branch specific change. > > I am sure this will get taken care of correctly also once I check with Dean. I think the .gitreview is the only real problem you had? I do the merge back to master following https://wiki.openstack.org/wiki/StarlingX/Branches#Feature_Branches and swapping the 'master' and '$feature_branch' in the arguments. It results in the same thing, just depends on which branch you are in at the time of the merge. Just below that is the command to fix up .gitreview (whick we skip when going master -> $feature_branch). I've re-done stx-integ[0], stx-root[1], stx-tools[2] and stx-upstream[3]. stx-manifest does not appear to have any changes to master required (the only new bits in the feature branch are the revision="" attributes that master doesn't want). [0] https://review.openstack.org/642481 [1] https://review.openstack.org/642487 [2] https://review.openstack.org/642485 [3] https://review.openstack.org/642486 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 yong.hu at intel.com Tue Mar 12 12:50:32 2019 From: yong.hu at intel.com (Hu, Yong) Date: Tue, 12 Mar 2019 12:50:32 +0000 Subject: [Starlingx-discuss] about NVME disk as the boot disk Message-ID: <1778C939-9D03-4AE2-8B6D-D6C54E55AAD4@intel.com> Hi folks, I was installing StarlingX in a NUC with 2 NVME disks (without other HD or SATA disks), and the installation was ended up with an issue as follows: “ERROR: Specified installation (sda) or boot (sda) device is a USB drive.” It seemed NVME disk was not recognized as valid boot disk. With the help from @Saul, we found in “bsp-files/grub.cfg”, “boot_device” and “rootfs_device” were by default set as “sda” in ks cmdline: linuxefi /vmlinuz inst.ks=hd:LABEL=oe_iso_boot:/smallsystem_ks.cfg boot_device=sda rootfs_device=sda biosdevname=0 usbcore.autosuspend=-1 console=tty0 inst.text inst.stage2=hd:LABEL=oe_iso_boot inst.gpt security_profile=standard user_namespace.enable=1 So, there are 2 ways to make NVME disks work as boot disk: 1. to change the grub cmdline, with “nvme0n1” for “rootfs_device” and “boot_device” accordingly, during the installation. 2. Not to set “rootfs_device” and “boot_device” in ks cmdline, and let “bsp-files/kickstarts/pre_disk_setup_common.cfg” detect “nvme0n1” dynamically. Though, I wonder if there are other better ways in such a case. Regards, Yong -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Tue Mar 12 13:15:25 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 12 Mar 2019 13:15:25 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack Distro meeting Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35EC629E@SHSMSX104.ccr.corp.intel.com> Please be noted that for attendees from China, the meeting is now 9pm! Agenda for 3/13 meeting: - CentOS 7.6 merged to Master, review 1st daily test report (Ada) - Ceph upgrade status (Ovidiu/Daniel, Changcheng/Tingjie) - DevStack update (Dean/Yi) - Opens (all) Thx. - cindy -----Original Appointment----- From: Xie, Cindy Sent: Monday, November 5, 2018 2:27 PM To: Xie, Cindy; Troyer, Dean; Zhu, Vivian; Hu, Yong; Lin, Shuicheng; Shang, Dehao; Somerville, Jim; Wold, Saul; Sun, Austin; Jones, Bruce E; Liu, ZhipengS; 'Rowsell, Brent'; 'Khalil, Ghada'; starlingx-discuss at lists.starlingx.io; Waheed, Numan Cc: Perez Carranza, Jose; 'Hellmann, Gil'; 'Seiler, Glenn'; 'Young, Ken'; Arce Moreno, Abraham; Cobbley, David A; Fang, Liang A; 'Eslimi, Dariush'; Hu, Wei W; Martinez Monroy, Elio; 'Waines, Greg'; Lara, Cesar; Armstrong, Robert H; 'Chen, Jacky'; Martinez Landa, Hayde; 'Poncea, Ovidiu'; Perez Rodriguez, Humberto I; Gomez, Juan P; Shuquan Huang Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, March 13, 2019 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Tue Mar 12 13:15:20 2019 From: serverascode at gmail.com (Curtis) Date: Tue, 12 Mar 2019 09:15:20 -0400 Subject: [Starlingx-discuss] STX performance tests update In-Reply-To: References: Message-ID: On Mon, Mar 11, 2019 at 10:21 PM Victor Rodriguez wrote: > On Mon, Mar 11, 2019 at 5:19 PM Curtis wrote: > > > > > > > > On Sun, Mar 10, 2019 at 11:54 AM Victor Rodriguez > wrote: > >> > >> Hi team > >> > >> After some research on the topic and the great help from Numan's team, > >> I came into this great presentation about how to use OPNFV for > >> performance metrics (video available at [0]): > >> > >> > https://www.openstack.org/assets/presentation-media/OpenStack-Summit-Vancouver-OPNFV-Test-tools-2.pdf > >> > >> It was presented on May 2018 OpenStack Summit, Here is described > >> Yardstick Test Case for performance measurement, They do have a very > >> good wiki on how to do : > >> > >> Installation and run: > >> > http://artifacts.opnfv.org/yardstick/colorado/2.0/docs/userguide/index.html#document-07-installation > >> > >> Description of every test case : > >> > https://docs.opnfv.org/en/stable-fraser/submodules/yardstick/docs/testing/user/userguide/15-list-of-tcs.html > >> > >> After a quick view, Yardstick has the capability to measure > >> performance in 3 sections: > >> > >> * Compute > >> * Storage > >> * Network > >> > >> With multiple tests cases for each one ( slide 13 of presentation ) > >> > >> This is a simple update to keep the community informed about the > >> progress on this topic, if someone has any feedback, please let me > >> know. > > > > > > I haven't used Yardstick, but it sounds like a step in the right > direction. Perhaps we can find things to push back upstream to OPNFV. > > > > What I'm hoping is that we can use the Packet.com resources that should > be available soon to run automated performance tests and then publish the > results on a continual basis. I'm definitely interested in helping out. :) > > > > Thanks, > > Curtis > > > > Thanks a lot Curtis, CI/CD definitely is the next step ones I could > enable this from the developer perspective. My goal is to provide a > simple tutorial/script to run a test on a pre-configured and working > STX cloud system that developers could use to measure their changes. > Once I have this and make a demo I will ping you to try in your dev > machine and then TSC can decide to deploy this on Packet. The good > thing about Yardstick is that it has a connection to grafana so we > don't have to worry about a dashboard : ) . > > The concern that I have (that I would like input from the TSC) is how > to define what configuration we want to use on Packet as baseline > configuration, this is important because a change in the configuration > might represent a huge change in performance results. Yes it would be pretty easy to create a configuration that doesn't perform well. :) There are many, many variables, many of which would be out of our control or are a black box. For sure part of this would be to determine what configuration, or configurations, would be best to test, and those decisions described. I would expect we would create a baseline configuration and then expand from there. Also, are we ok > to compare the STX results against regular OpenStack > Performanceomrance numbers is always hard to handle since they are > very senitive. I would like to bring this topic to the TSC or comunity > meeting so we can tak e a decision as comunity. My work might finish > when we could have a way to get the numbers, publication, and track of > them might be a decision out of my scope. > > I think the focus would be on simply having data to compare for STX, not to compare STX against other distros or projects. I'm not sure what "regular openstack" is to be honest. :) My example is Kata Containers who do performance testing to ensure that they are not losing 1% a month. I'd just like to see some trending data. Thanks, Curtis > I will keep you posted > > Regards > > > > > >> > >> > >> Numan/ Peng thanks a lot for the document, after reading I realize it > >> is focused on Tempest ( which is used by OPNFV but as part of > >> Functest, which is the test framework provided to answer the question: > >> Does my infrastructure simply work as expected?. > >> > >> Regards > >> > >> BTW, sorry for the long delay of an update for this topic > >> > >> Victor Rodriguez > >> > >> [0] https://www.youtube.com/watch?v=RxMbF8ILl-M > >> > >> _______________________________________________ > >> Starlingx-discuss mailing list > >> Starlingx-discuss at lists.starlingx.io > >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > > > > -- > > Blog: serverascode.com > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Tue Mar 12 13:39:18 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 12 Mar 2019 13:39:18 +0000 Subject: [Starlingx-discuss] openstack network segment range create FAILED In-Reply-To: References: <8557B550001AFB46A43A0CCC314BF85153CA97B8@FMSMSX108.amr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4CBE39@ALA-MBD.corp.ad.wrs.com> Hi Kailun, All bugs need to be reported in Launchpad. Moving forward, please do not open stories for bugs. JC already opened a Launchpad bug for the issue he reported: https://bugs.launchpad.net/starlingx/+bug/1819541 I've assigned it to you. Please update your commit message to add "Closes-Bug: 1819541" Thanks, Ghada From: Qin, Kailun [mailto:kailun.qin at intel.com] Sent: Tuesday, March 12, 2019 5:59 AM To: Alonso, Juan Carlos; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] openstack network segment range create FAILED Hi Juan Carlos, I can reproduce this issue locally. This is a regression issue due to the requirement change of the network-segment-range OSC CLI during the feature patch review. I've filed bugs [1][2] and submitted patches [3][4] for them. Currently you can work around this by not specifying --shared and it'll default to a shared range. Let me know if any further question. Thanks a lot. BR, Kailun [1] https://storyboard.openstack.org/#!/story/2005205 [2] https://storyboard.openstack.org/#!/story/2005206 [3] https://review.openstack.org/#/c/642707/ [4] https://review.openstack.org/#/c/642708/ From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Tuesday, March 12, 2019 1:51 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] openstack network segment range create FAILED Hi, In "Providernetworking setup: Network Segment Ranges (Stein)" section, in the second command: openstack network segment range create ${PHYSNET0}-b --network-type vlan --physical-network ${PHYSNET0} --minimum 10 --maximum 10 --shared I got the following error: BadRequestException: 400: Client Error for url: http://neutron.openstack.svc.cluster.local:80/v2.0/network_segment_ranges, Invalid input for tenant_id. Reason: 'None' is not a valid string. I tried to add --project ${ADMINID} but --project is only allowed with --private. Has this command been updated? Because the wiki does not show an update. Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Tue Mar 12 13:41:33 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 12 Mar 2019 13:41:33 +0000 Subject: [Starlingx-discuss] openstack network segment range create FAILED References: <8557B550001AFB46A43A0CCC314BF85153CA97B8@FMSMSX108.amr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4CBE4A@ALA-MBD.corp.ad.wrs.com> My apologies. I didn't realize that the code needs to go in openstack-client ...not in starlingx. From: Khalil, Ghada Sent: Tuesday, March 12, 2019 9:39 AM To: 'Qin, Kailun'; Alonso, Juan Carlos; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] openstack network segment range create FAILED Hi Kailun, All bugs need to be reported in Launchpad. Moving forward, please do not open stories for bugs. JC already opened a Launchpad bug for the issue he reported: https://bugs.launchpad.net/starlingx/+bug/1819541 I've assigned it to you. Please update your commit message to add "Closes-Bug: 1819541" Thanks, Ghada From: Qin, Kailun [mailto:kailun.qin at intel.com] Sent: Tuesday, March 12, 2019 5:59 AM To: Alonso, Juan Carlos; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] openstack network segment range create FAILED Hi Juan Carlos, I can reproduce this issue locally. This is a regression issue due to the requirement change of the network-segment-range OSC CLI during the feature patch review. I've filed bugs [1][2] and submitted patches [3][4] for them. Currently you can work around this by not specifying --shared and it'll default to a shared range. Let me know if any further question. Thanks a lot. BR, Kailun [1] https://storyboard.openstack.org/#!/story/2005205 [2] https://storyboard.openstack.org/#!/story/2005206 [3] https://review.openstack.org/#/c/642707/ [4] https://review.openstack.org/#/c/642708/ From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Tuesday, March 12, 2019 1:51 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] openstack network segment range create FAILED Hi, In "Providernetworking setup: Network Segment Ranges (Stein)" section, in the second command: openstack network segment range create ${PHYSNET0}-b --network-type vlan --physical-network ${PHYSNET0} --minimum 10 --maximum 10 --shared I got the following error: BadRequestException: 400: Client Error for url: http://neutron.openstack.svc.cluster.local:80/v2.0/network_segment_ranges, Invalid input for tenant_id. Reason: 'None' is not a valid string. I tried to add --project ${ADMINID} but --project is only allowed with --private. Has this command been updated? Because the wiki does not show an update. Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Tue Mar 12 13:54:57 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 12 Mar 2019 13:54:57 +0000 Subject: [Starlingx-discuss] Distro.openstack meeting notes Mar 12th 2019 Message-ID: <9A85D2917C58154C960D95352B22818BD06FCBCA@fmsmsx123.amr.corp.intel.com> Meeting agenda and notes for the 3/12 meeting * Good news - Neutron network segment range patches in (except lib) * Bad news - NUMA topology pushed out. * We believe we will have to carry forks of at least some of the Nova changes * We also believe anything committed to Nova is deployable (and will remain so as per Matt R). * We should implement the "upstream first" and "stable branch" concept and backport critical features and features from Train to our release branch ? Changes that are absolutely critical should be backported before they are accepted (and updated over time until acceptance). ? We should help fix things upstream as we find issues with Train "work in progress" patches * Meanwhile we will continuously update our master from OpenStack master * AR Bruce and Frank - need a plan for upstream contributions for Nova * We need to define our branching strategy. Create an f/stx-stein branch? Create a f/nova feature branch for StarlingX? * We will need to build our Nova container out of the github staging trees - once Nova cuts there first RC (Mar 22nd). Backports will be checked into github directly. * Plan to raise these issues with Nova community at PTG and support the efforts * Review updates: https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit?ts=5c1933cc#gid=0 * Review LP issues: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Mar 12 13:54:14 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 12 Mar 2019 13:54:14 +0000 Subject: [Starlingx-discuss] about NVME disk as the boot disk In-Reply-To: <1778C939-9D03-4AE2-8B6D-D6C54E55AAD4@intel.com> References: <1778C939-9D03-4AE2-8B6D-D6C54E55AAD4@intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA462970@ALA-MBD.corp.ad.wrs.com> Hi Yong, Please see the following reference: https://docs.starlingx.io/installation_guide/index.html#nvme-drive-as-boot-drive Edit the kernel boot parameter. After you are presented with the StarlingX ISO boot options and after you have selected the preferred installation option (e.g. Standard Configuration / All-in-One Controller Configuration), press the TAB key to edit the Kernel boot parameters. Modify the boot_device and rootfs_device from the default sda so that it is the correct device name for the NVMe drive (e.g. “nvme0n1”). Cheers, Don. From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Tuesday, March 12, 2019 8:51 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] about NVME disk as the boot disk Hi folks, I was installing StarlingX in a NUC with 2 NVME disks (without other HD or SATA disks), and the installation was ended up with an issue as follows: “ERROR: Specified installation (sda) or boot (sda) device is a USB drive.” It seemed NVME disk was not recognized as valid boot disk. With the help from @Saul, we found in “bsp-files/grub.cfg”, “boot_device” and “rootfs_device” were by default set as “sda” in ks cmdline: linuxefi /vmlinuz inst.ks=hd:LABEL=oe_iso_boot:/smallsystem_ks.cfg boot_device=sda rootfs_device=sda biosdevname=0 usbcore.autosuspend=-1 console=tty0 inst.text inst.stage2=hd:LABEL=oe_iso_boot inst.gpt security_profile=standard user_namespace.enable=1 So, there are 2 ways to make NVME disks work as boot disk: 1. to change the grub cmdline, with “nvme0n1” for “rootfs_device” and “boot_device” accordingly, during the installation. 2. Not to set “rootfs_device” and “boot_device” in ks cmdline, and let “bsp-files/kickstarts/pre_disk_setup_common.cfg” detect “nvme0n1” dynamically. Though, I wonder if there are other better ways in such a case. Regards, Yong -------------- next part -------------- An HTML attachment was scrubbed... URL: From huang.shuquan at 99cloud.net Tue Mar 12 14:27:23 2019 From: huang.shuquan at 99cloud.net (Shuquan Huang) Date: Tue, 12 Mar 2019 22:27:23 +0800 Subject: [Starlingx-discuss] Daylight Savings Time In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F35EBFC49@SHSMSX104.ccr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BD06F2DF8@fmsmsx123.amr.corp.intel.com> <586E8B730EA0DA4A9D6A80A10E486BC0A15AC4@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35EBFC49@SHSMSX104.ccr.corp.intel.com> Message-ID: <763714DA-2149-4CE8-B247-42BCD591D6C4@99cloud.net> +1 And I suggest we update the meeting time in the wiki[1] at the same time. [1]https://wiki.openstack.org/wiki/Starlingx/Meetings On Mar 9, 2019, at 9:07 AM, Xie, Cindy wrote: +1 good for China attendees. J   <> <>From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] Sent: Saturday, March 9, 2019 3:30 AM To: Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Daylight Savings Time +1 from me From: Jones, Bruce E > Sent: Friday, March 8, 2019 2:25 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Daylight Savings Time This weekend many of us switch from standard time to daylight time, as we Spring Forward an hour. As I recall, when we switched from daylight to standard last year, we agreed to keep all meetings in the timezones that are switching at the same clock time while making everyone else move their meetings around. Is that what we want to do for our meetings next week? brucej _______________________________________________ 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 serverascode at gmail.com Tue Mar 12 14:58:52 2019 From: serverascode at gmail.com (Curtis) Date: Tue, 12 Mar 2019 10:58:52 -0400 Subject: [Starlingx-discuss] Daylight Savings Time In-Reply-To: <9A85D2917C58154C960D95352B22818BD06F2DF8@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BD06F2DF8@fmsmsx123.amr.corp.intel.com> Message-ID: On Fri, Mar 8, 2019 at 2:26 PM Jones, Bruce E wrote: > This weekend many of us switch from standard time to daylight time, as we > Spring Forward an hour. As I recall, when we switched from daylight to > standard last year, we agreed to keep all meetings in the timezones that > are switching at the same clock time while making everyone else move their > meetings around. > > > > Is that what we want to do for our meetings next week? > I'm assuming the meetings are in UTC? At any rate +1. That does cause me a problem as I won't be able to attend the TSC or community meeting until about 15,30 minutes after they start. But that's just me. :) Thanks, Curtis > > > brucej > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtroyer at gmail.com Tue Mar 12 15:14:47 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Tue, 12 Mar 2019 10:14:47 -0500 Subject: [Starlingx-discuss] Distro.openstack meeting notes Mar 12th 2019 In-Reply-To: <9A85D2917C58154C960D95352B22818BD06FCBCA@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BD06FCBCA@fmsmsx123.amr.corp.intel.com> Message-ID: On Tue, Mar 12, 2019 at 8:55 AM Jones, Bruce E wrote: [...] > · We need to define our branching strategy. Create an f/stx-stein branch? Create a f/nova feature branch for StarlingX? > We will need to build our Nova container out of the github staging trees - once Nova cuts there first RC (Mar 22nd). Backports will be checked into github directly. This is the process I imagined and outlined in the meeting: * When Nova creates their stable/stein branch at RC1 time we will create a mirror of that in starlingx-staging/nova as stx/stein. * This branch will be periodically updated from stable/stein as backports appear there from the Nova team. * As items on our list of upstream changes land in master (Train) we will backport them to stx/stein for StarlingX to pick up. * There may be times that work upstream has not yet merged but is sufficiently complete that we would backport early to meet a StarlingX time requirement, with the expectation that it be brought current with what finally does merge after that happens. * Upstream work that is not yet complete that we want to backport to meet a StarlingX time requirement should be worked upstream to get it to the state mentioned above to enable us to backport it to stx/stein. Still to be decided/confirmed: * We need to have some measure of testing in stx/stein, I will look in to what we can run from OpenStack Zuul directly. * I like the idea of continuing to have only a small number of people with the ability to commit to the staging repo * We may want to consider the tactic of keeping our additional commits in stx/stein rebased on top of the upstream stable/stein rather than merging in upstream backports. This would be inconvenient for those with local copies of the branch after each rebase but it would keep the SHAs in the upstream commits the same. (I am not convinced yet that we should do this, still sorting it out) dt -- Dean Troyer dtroyer at gmail.com From marcel at schaible-consulting.de Tue Mar 12 16:29:48 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Tue, 12 Mar 2019 17:29:48 +0100 (CET) Subject: [Starlingx-discuss] Configuration of internet access of a VM Message-ID: <1893840216.749048.1552408188934@communicator.strato.com> Hi, I want to setup an internet access of one of my VM (simplex config). I am a little bit puzzled what kind of networks and routes do I need to configure. Can someone point me to some documentation how this is intended to work? Thanks Marcel From scott.little at windriver.com Tue Mar 12 16:31:48 2019 From: scott.little at windriver.com (Scott Little) Date: Tue, 12 Mar 2019 12:31:48 -0400 Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 14 - Failure! In-Reply-To: <939516032.86.1552377823636.JavaMail.javamailuser@localhost> References: <939516032.86.1552377823636.JavaMail.javamailuser@localhost> Message-ID: Builds are failing after the merge of f/centos76. https://bugs.launchpad.net/starlingx/+bug/1819717 proposed fix.... https://review.openstack.org/642801 Scott On 2019-03-12 4:03 a.m., build.starlingx at gmail.com wrote: > Project: STX_build_master_master > Build #: 14 > Status: Failure > Timestamp: 20190312T050000Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190312T050000Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS: false > BUILD_CONTAINERS_ZZZ: false > > _______________________________________________ > 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 bruce.e.jones at intel.com Tue Mar 12 16:45:42 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 12 Mar 2019 16:45:42 +0000 Subject: [Starlingx-discuss] Release sub-team meeting - new time and date Message-ID: <9A85D2917C58154C960D95352B22818BD06FD2BF@fmsmsx123.amr.corp.intel.com> We are starting up a Release sub-team meeting, to discuss release related issues. The time is 11AM PST 1900 UTC on Thursdays, using the usual Zoom link. All are welcome to attend. brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Tue Mar 12 17:32:47 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 12 Mar 2019 17:32:47 +0000 Subject: [Starlingx-discuss] Release sub-team meeting - new time and date In-Reply-To: <9A85D2917C58154C960D95352B22818BD06FD2BF@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BD06FD2BF@fmsmsx123.amr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4CC062@ALA-MBD.corp.ad.wrs.com> The etherpad for this meeting is: https://etherpad.openstack.org/p/stx-releases From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Tuesday, March 12, 2019 12:46 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Release sub-team meeting - new time and date We are starting up a Release sub-team meeting, to discuss release related issues.  The time is 11AM PST 1900 UTC on Thursdays, using the usual Zoom link.  All are welcome to attend.       brucej From Barton.Wensley at windriver.com Tue Mar 12 17:35:03 2019 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Tue, 12 Mar 2019 17:35:03 +0000 Subject: [Starlingx-discuss] Potential failure in stx-openstack application Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA7B660@ALA-MBD.corp.ad.wrs.com> Public service announcement... If you are using a load built after Friday, you may see the stx-openstack apply failing - the symptom will be that the ceph-pools-audit pod will be scheduled to run on controller-1 and will be stuck in the ImagePullBackOff state. The following bug is tracking the issue: https://bugs.launchpad.net/starlingx/+bug/1819720 To work around this, you can do the following on controller-1 (as root): export KUBECONFIG=/etc/kubernetes/admin.conf export REGISTRY_HOST=192.168.204.2 export REGISTRY_PORT=9001 export REGISTRY=${REGISTRY_HOST}:${REGISTRY_PORT} docker login $REGISTRY docker pull $REGISTRY/docker.io/port/ceph-config-helper:v1.10.3 You can then redo your "system application-apply stx-openstack" and all should be good. Bart -------------- next part -------------- An HTML attachment was scrubbed... URL: From vm.rod25 at gmail.com Tue Mar 12 17:48:50 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Tue, 12 Mar 2019 11:48:50 -0600 Subject: [Starlingx-discuss] STX performance tests update In-Reply-To: References: Message-ID: On Tue, Mar 12, 2019 at 7:15 AM Curtis wrote: > > > > On Mon, Mar 11, 2019 at 10:21 PM Victor Rodriguez wrote: >> >> On Mon, Mar 11, 2019 at 5:19 PM Curtis wrote: >> > >> > >> > >> > On Sun, Mar 10, 2019 at 11:54 AM Victor Rodriguez wrote: >> >> >> >> Hi team >> >> >> >> After some research on the topic and the great help from Numan's team, >> >> I came into this great presentation about how to use OPNFV for >> >> performance metrics (video available at [0]): >> >> >> >> https://www.openstack.org/assets/presentation-media/OpenStack-Summit-Vancouver-OPNFV-Test-tools-2.pdf >> >> >> >> It was presented on May 2018 OpenStack Summit, Here is described >> >> Yardstick Test Case for performance measurement, They do have a very >> >> good wiki on how to do : >> >> >> >> Installation and run: >> >> http://artifacts.opnfv.org/yardstick/colorado/2.0/docs/userguide/index.html#document-07-installation >> >> >> >> Description of every test case : >> >> https://docs.opnfv.org/en/stable-fraser/submodules/yardstick/docs/testing/user/userguide/15-list-of-tcs.html >> >> >> >> After a quick view, Yardstick has the capability to measure >> >> performance in 3 sections: >> >> >> >> * Compute >> >> * Storage >> >> * Network >> >> >> >> With multiple tests cases for each one ( slide 13 of presentation ) >> >> >> >> This is a simple update to keep the community informed about the >> >> progress on this topic, if someone has any feedback, please let me >> >> know. >> > >> > >> > I haven't used Yardstick, but it sounds like a step in the right direction. Perhaps we can find things to push back upstream to OPNFV. >> > >> > What I'm hoping is that we can use the Packet.com resources that should be available soon to run automated performance tests and then publish the results on a continual basis. I'm definitely interested in helping out. :) >> > >> > Thanks, >> > Curtis >> > >> >> Thanks a lot Curtis, CI/CD definitely is the next step ones I could >> enable this from the developer perspective. My goal is to provide a >> simple tutorial/script to run a test on a pre-configured and working >> STX cloud system that developers could use to measure their changes. >> Once I have this and make a demo I will ping you to try in your dev >> machine and then TSC can decide to deploy this on Packet. The good >> thing about Yardstick is that it has a connection to grafana so we >> don't have to worry about a dashboard : ) . >> >> The concern that I have (that I would like input from the TSC) is how >> to define what configuration we want to use on Packet as baseline >> configuration, this is important because a change in the configuration >> might represent a huge change in performance results. > > > Yes it would be pretty easy to create a configuration that doesn't perform well. :) There are many, many variables, many of which would be out of our control or are a black box. > > For sure part of this would be to determine what configuration, or configurations, would be best to test, and those decisions described. I would expect we would create a baseline configuration and then expand from there. > Having a baseline configuration will be a great milestone >> Also, are we ok >> to compare the STX results against regular OpenStack >> Performanceomrance numbers is always hard to handle since they are >> very senitive. I would like to bring this topic to the TSC or comunity >> meeting so we can tak e a decision as comunity. My work might finish >> when we could have a way to get the numbers, publication, and track of >> them might be a decision out of my scope. >> > > I think the focus would be on simply having data to compare for STX, not to compare STX against other distros or projects. I'm not sure what "regular openstack" is to be honest. :) > > My example is Kata Containers who do performance testing to ensure that they are not losing 1% a month. I'd just like to see some trending data. > I see your point now , thanks . Yes , the goal of having a dashboard that track performance of STX daily will be very usefull for the project . Without comparing to other projects we will be able to detect regresions on perfomrance ( something we currentlyd ont have ) Regards > Thanks, > Curtis > > >> >> I will keep you posted >> >> Regards >> >> >> > >> >> >> >> >> >> Numan/ Peng thanks a lot for the document, after reading I realize it >> >> is focused on Tempest ( which is used by OPNFV but as part of >> >> Functest, which is the test framework provided to answer the question: >> >> Does my infrastructure simply work as expected?. >> >> >> >> Regards >> >> >> >> BTW, sorry for the long delay of an update for this topic >> >> >> >> Victor Rodriguez >> >> >> >> [0] https://www.youtube.com/watch?v=RxMbF8ILl-M >> >> >> >> _______________________________________________ >> >> Starlingx-discuss mailing list >> >> Starlingx-discuss at lists.starlingx.io >> >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > >> > >> > >> > -- >> > Blog: serverascode.com > > > > -- > Blog: serverascode.com From Ghada.Khalil at windriver.com Tue Mar 12 17:50:43 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 12 Mar 2019 17:50:43 +0000 Subject: [Starlingx-discuss] Weekly StarlingX Release meeting Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4CD0EA@ALA-MBD.corp.ad.wrs.com> Weekly meeting on Thursday 11AM PT / 1900 UTC Zoom Link: https://zoom.us/j/342730236 Meeting agenda/minutes: https://etherpad.openstack.org/p/stx-releases -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1733 bytes Desc: not available URL: From Ghada.Khalil at windriver.com Tue Mar 12 19:50:58 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 12 Mar 2019 19:50:58 +0000 Subject: [Starlingx-discuss] QAT driver upgrade Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4CD1A3@ALA-MBD.corp.ad.wrs.com> Hi Shuicheng, The version used in StarlingX is from July 2017 which is pretty old, so my inclination is to suggest we upgrade to the latest. We need input/approval from the TLs (Brent & Saul). Let's discuss with them in the distro.other meeting tomorrow. I put this item on the agenda. I've asked Numan to send out the test-cases. Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Monday, March 11, 2019 12:33 AM To: Khalil, Ghada Cc: starlingx-discuss at lists.starlingx.io; Xie, Cindy Subject: QAT driver upugrade Hi Ghada, Here is the release notes for the latest QAT(1.7.L.4.4.0-00023). https://01.org/sites/default/files/downloads//336211-009qatrelnotes.pdf The release notes just list some issue fixed since 1.0.3-42, which is the version StarlingX using currently. Could you help ask expert from WR to review it, and decide whether we prefer to upgrade it or not? If we choose to upgrade it, could you help share me the test case for QAT driver? Thanks. Best Regards Shuicheng From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Monday, February 4, 2019 11:00 PM To: Lin, Shuicheng >; Waheed, Numan >; Perez, Ricardo O >; Xie, Cindy >; Cabrales, Ada > Cc: starlingx-discuss at lists.starlingx.io Subject: RE: CentOS 7.6 rebase feature testing Thanks Shuicheng. Is there a need to actually upversion the qat drivers? Are there new features or bug fixes that are of interest to StarlingX? I suggest you review the release notes and make a decision with the distro.other team leads before proceeding with this item. Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Wednesday, January 30, 2019 7:34 PM To: Khalil, Ghada; Waheed, Numan; Perez, Ricardo O; Xie, Cindy; Cabrales, Ada Cc: starlingx-discuss at lists.starlingx.io Subject: RE: CentOS 7.6 rebase feature testing Hi all, Story is created to track this task: https://storyboard.openstack.org/#!/story/2004901 Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, January 31, 2019 7:56 AM To: Khalil, Ghada >; Waheed, Numan >; Perez, Ricardo O >; Xie, Cindy >; Cabrales, Ada > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] CentOS 7.6 rebase feature testing Hi Ghada, QAT driver is not upgraded yet, since there is no build failure with CentOS 7.6. I will have a check with it after Chinese New Year's holiday, and plan to do the upgrade in master. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Tue Mar 12 20:18:04 2019 From: scott.little at windriver.com (Scott Little) Date: Tue, 12 Mar 2019 16:18:04 -0400 Subject: [Starlingx-discuss] [build] publishing CENGN jenkins scripts via git In-Reply-To: <81cf14b7-7762-44df-77b6-e59a6a31ff50@linux.intel.com> References: <93fbd3d2-b121-eb49-4741-d4018f5c2bf4@windriver.com> <4ad0c17e983a034b1351ed0136070a13973fdacc.camel@intel.com> <9A85D2917C58154C960D95352B22818BC3AD4C45@fmsmsx121.amr.corp.intel.com> <81cf14b7-7762-44df-77b6-e59a6a31ff50@linux.intel.com> Message-ID: I've uploaded the current set of build scripts to https://github.com/starlingx-staging/jenkins.git Scott On 2019-02-28 2:51 p.m., Saul Wold wrote: > > > On 2/28/19 8:16 AM, Victor Rodriguez wrote: >> As discussed in build meeting, the new repo might live in: >> >> https://github.com/starlingx-staging >> >> Saul can help with the creation of the repo >> > Repo created: https://github.com/starlingx-staging/jenkins.git > > Sau! > >> regards >> >> On Thu, Feb 28, 2019 at 8:36 AM Scott Little >> wrote: >>> >>> Jenkins under git is basically a snapshot of the jenkins home >>> directory, >>> or a subset thereof.   I think it really needs to be a git unto itself. >>> >>> Scott >>> >>> >>> On 2019-02-25 12:52 p.m., Jones, Bruce E wrote: >>>> Great idea!  Maybe stx-tools? >>>> >>>>          brucej >>>> >>>> -----Original Message----- >>>> From: Cordoba Malibran, Erich >>>> [mailto:erich.cordoba.malibran at intel.com] >>>> Sent: Monday, February 25, 2019 9:50 AM >>>> To: scott.little at windriver.com; starlingx-discuss at lists.starlingx.io >>>> Subject: Re: [Starlingx-discuss] [build] publishing CENGN jenkins >>>> scripts via git >>>> >>>> Hi Scott, >>>> >>>> I think that is a great idea! >>>> >>>> I would suggest a new stx-automation or stx-ci repository, also not >>>> sure where is the best place, I would suggest github, but for sure >>>> Dean  will have better insights on this :) >>>> >>>> -Erich >>>> >>>> On Fri, 2019-02-22 at 16:50 -0500, Scott Little wrote: >>>>> The idea was floated several weeks ago that we should place the >>>>> jenkins scripts used by starlingx.cengn.ca builds under git revision >>>>> control, and publish them somewhere. >>>>> >>>>> If we are all agreed this would be a good thing, I would like to move >>>>> forward with that proposal. >>>>> >>>>> Where should we publish it,  github or openstack? >>>>> >>>>> If openstack, I'll need some pointers on how to set up the new git. >>>>> >>>>> >>>>> Thanks >>>>> >>>>> Scott >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 cesar.lara at intel.com Tue Mar 12 20:21:19 2019 From: cesar.lara at intel.com (Lara, Cesar) Date: Tue, 12 Mar 2019 20:21:19 +0000 Subject: [Starlingx-discuss] [build] publishing CENGN jenkins scripts via git In-Reply-To: References: <93fbd3d2-b121-eb49-4741-d4018f5c2bf4@windriver.com> <4ad0c17e983a034b1351ed0136070a13973fdacc.camel@intel.com> <9A85D2917C58154C960D95352B22818BC3AD4C45@fmsmsx121.amr.corp.intel.com> <81cf14b7-7762-44df-77b6-e59a6a31ff50@linux.intel.com>, Message-ID: <5e54bcd8-9d08-4630-ba20-a53b6b5d5a26@intel.com> Awesome, thanks Scott Regards Cesar Lara ________________________________ From: Scott Little Sent: Tuesday, March 12, 2019 2:19 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build] publishing CENGN jenkins scripts via git I've uploaded the current set of build scripts to https://github.com/starlingx-staging/jenkins.git Scott On 2019-02-28 2:51 p.m., Saul Wold wrote: > > > On 2/28/19 8:16 AM, Victor Rodriguez wrote: >> As discussed in build meeting, the new repo might live in: >> >> https://github.com/starlingx-staging >> >> Saul can help with the creation of the repo >> > Repo created: https://github.com/starlingx-staging/jenkins.git > > Sau! > >> regards >> >> On Thu, Feb 28, 2019 at 8:36 AM Scott Little >> wrote: >>> >>> Jenkins under git is basically a snapshot of the jenkins home >>> directory, >>> or a subset thereof. I think it really needs to be a git unto itself. >>> >>> Scott >>> >>> >>> On 2019-02-25 12:52 p.m., Jones, Bruce E wrote: >>>> Great idea! Maybe stx-tools? >>>> >>>> brucej >>>> >>>> -----Original Message----- >>>> From: Cordoba Malibran, Erich >>>> [mailto:erich.cordoba.malibran at intel.com] >>>> Sent: Monday, February 25, 2019 9:50 AM >>>> To: scott.little at windriver.com; starlingx-discuss at lists.starlingx.io >>>> Subject: Re: [Starlingx-discuss] [build] publishing CENGN jenkins >>>> scripts via git >>>> >>>> Hi Scott, >>>> >>>> I think that is a great idea! >>>> >>>> I would suggest a new stx-automation or stx-ci repository, also not >>>> sure where is the best place, I would suggest github, but for sure >>>> Dean will have better insights on this :) >>>> >>>> -Erich >>>> >>>> On Fri, 2019-02-22 at 16:50 -0500, Scott Little wrote: >>>>> The idea was floated several weeks ago that we should place the >>>>> jenkins scripts used by starlingx.cengn.ca builds under git revision >>>>> control, and publish them somewhere. >>>>> >>>>> If we are all agreed this would be a good thing, I would like to move >>>>> forward with that proposal. >>>>> >>>>> Where should we publish it, github or openstack? >>>>> >>>>> If openstack, I'll need some pointers on how to set up the new git. >>>>> >>>>> >>>>> Thanks >>>>> >>>>> Scott >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Tue Mar 12 21:45:33 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 12 Mar 2019 21:45:33 +0000 Subject: [Starlingx-discuss] Reminder: No mlx support on data interfaces w/ CentOS 7.6 Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4CD221@ALA-MBD.corp.ad.wrs.com> I just wanted to send a reminder that there will be no mellanox NIC support on data interfaces in loads starting today due to the merge of the CentOS 7.6 feature branch. The support will be re-introduced by: https://storyboard.openstack.org/#!/story/2004743 Until this story merges, please do not use systems w/ mellanox data interfaces. Thanks, Ghada -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Mar 12 22:45:14 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 12 Mar 2019 18:45:14 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 16 - Failure! Message-ID: <1573627026.94.1552430719091.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 16 Status: Failure Timestamp: 20190312T223000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190312T223000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false BUILD_CONTAINERS_ZZZ: false From sgw at linux.intel.com Wed Mar 13 00:24:25 2019 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 12 Mar 2019 17:24:25 -0700 Subject: [Starlingx-discuss] about NVME disk as the boot disk In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA462970@ALA-MBD.corp.ad.wrs.com> References: <1778C939-9D03-4AE2-8B6D-D6C54E55AAD4@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA462970@ALA-MBD.corp.ad.wrs.com> Message-ID: <024ffcb7-b4b7-210f-17dc-893e2cd4ba09@linux.intel.com> On 3/12/19 6:54 AM, Penney, Don wrote: > Hi Yong, > > Please see the following reference: > > https://docs.starlingx.io/installation_guide/index.html#nvme-drive-as-boot-drive > > Edit the kernel boot parameter. After you are presented with the > StarlingX ISO boot options and after you have selected the preferred > installation option (e.g. Standard Configuration / All-in-One Controller > Configuration), press the TAB key to edit the Kernel boot parameters. > Modify the *boot_device* and *rootfs_device* from the default *sda* so > that it is the correct device name for the NVMe drive (e.g. “nvme0n1”). > While editing the kernel cmdline is a workaround for this issue, does it also make sense to have a launchpad issue and work to fix the logic in selecting an appropriate boot/rootfs device target. There already is some logic to check for a USB device and fail out, so why not move that into the loop and have it auto detect nvme devices. Another option would be to change the ordering in pre_disk_setup_common code. Sau! > Cheers, > > Don. > > *From:*Hu, Yong [mailto:yong.hu at intel.com] > *Sent:* Tuesday, March 12, 2019 8:51 AM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] about NVME disk as the boot disk > > Hi folks, > > I was installing StarlingX in a NUC with 2 NVME disks (without other HD > or SATA disks), and the installation was ended up with an issue as follows: > > “ERROR: Specified installation (sda) or boot (sda) device is a USB drive.” > > It seemed NVME disk was not recognized as valid boot disk. > > With the help from @Saul, we found in “bsp-files/grub.cfg”, > “boot_device” and “rootfs_device” were by default set as “sda” in ks > cmdline: > > /linuxefi /vmlinuz inst.ks=hd:LABEL=oe_iso_boot:/smallsystem_ks.cfg > boot_device=sda rootfs_device=sda biosdevname=0 usbcore.autosuspend=-1 > console=tty0 inst.text inst.stage2=hd:LABEL=oe_iso_boot inst.gpt > security_profile=standard user_namespace.enable=1/ > > So, there are 2 ways to make NVME disks work as boot disk: > > 1. to change the grub cmdline, with “nvme0n1” for “rootfs_device” and > “boot_device” accordingly, during the installation. > 2. Not to set “rootfs_device” and “boot_device” in ks cmdline, and let > “bsp-files/kickstarts/pre_disk_setup_common.cfg” detect “nvme0n1” > dynamically. > > Though, I wonder if there are other better ways in such a case. > > Regards, > > Yong > > > _______________________________________________ > 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 Mar 13 01:08:40 2019 From: kailun.qin at intel.com (Qin, Kailun) Date: Wed, 13 Mar 2019 01:08:40 +0000 Subject: [Starlingx-discuss] openstack network segment range create FAILED In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA4CBE4A@ALA-MBD.corp.ad.wrs.com> References: <8557B550001AFB46A43A0CCC314BF85153CA97B8@FMSMSX108.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CBE4A@ALA-MBD.corp.ad.wrs.com> Message-ID: Just FYI, the issue was not discovered due to a functional test bug [1][2] in openstackclient. The functional test for network segment range in OSC was skipped unexpectedly because of this. Now we've added tests at unit level [3] to have it covered. [1] https://review.openstack.org/#/c/642074/ [2] https://storyboard.openstack.org/#!/story/2005169 [3] https://review.openstack.org/#/c/642707/ From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Tuesday, March 12, 2019 9:42 PM To: Qin, Kailun ; Alonso, Juan Carlos ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] openstack network segment range create FAILED My apologies. I didn't realize that the code needs to go in openstack-client ...not in starlingx. From: Khalil, Ghada Sent: Tuesday, March 12, 2019 9:39 AM To: 'Qin, Kailun'; Alonso, Juan Carlos; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] openstack network segment range create FAILED Hi Kailun, All bugs need to be reported in Launchpad. Moving forward, please do not open stories for bugs. JC already opened a Launchpad bug for the issue he reported: https://bugs.launchpad.net/starlingx/+bug/1819541 I've assigned it to you. Please update your commit message to add "Closes-Bug: 1819541" Thanks, Ghada From: Qin, Kailun [mailto:kailun.qin at intel.com] Sent: Tuesday, March 12, 2019 5:59 AM To: Alonso, Juan Carlos; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] openstack network segment range create FAILED Hi Juan Carlos, I can reproduce this issue locally. This is a regression issue due to the requirement change of the network-segment-range OSC CLI during the feature patch review. I've filed bugs [1][2] and submitted patches [3][4] for them. Currently you can work around this by not specifying --shared and it'll default to a shared range. Let me know if any further question. Thanks a lot. BR, Kailun [1] https://storyboard.openstack.org/#!/story/2005205 [2] https://storyboard.openstack.org/#!/story/2005206 [3] https://review.openstack.org/#/c/642707/ [4] https://review.openstack.org/#/c/642708/ From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Tuesday, March 12, 2019 1:51 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] openstack network segment range create FAILED Hi, In "Providernetworking setup: Network Segment Ranges (Stein)" section, in the second command: openstack network segment range create ${PHYSNET0}-b --network-type vlan --physical-network ${PHYSNET0} --minimum 10 --maximum 10 --shared I got the following error: BadRequestException: 400: Client Error for url: http://neutron.openstack.svc.cluster.local:80/v2.0/network_segment_ranges, Invalid input for tenant_id. Reason: 'None' is not a valid string. I tried to add --project ${ADMINID} but --project is only allowed with --private. Has this command been updated? Because the wiki does not show an update. Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Wed Mar 13 01:56:59 2019 From: yong.hu at intel.com (Hu, Yong) Date: Wed, 13 Mar 2019 01:56:59 +0000 Subject: [Starlingx-discuss] about NVME disk as the boot disk In-Reply-To: <024ffcb7-b4b7-210f-17dc-893e2cd4ba09@linux.intel.com> References: <1778C939-9D03-4AE2-8B6D-D6C54E55AAD4@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA462970@ALA-MBD.corp.ad.wrs.com> <024ffcb7-b4b7-210f-17dc-893e2cd4ba09@linux.intel.com> Message-ID: <95AF2728-C5A8-45CA-877E-070898935B13@intel.com> Thanks Don and Saul. I tried of removing "boot_device=sda rootfs_device=sda" from ks cmd, It turned out that loop of detection in "pre_disk_setup_common.cfg "worked as expected. So, I think we are all set. On 13/03/2019, 8:26 AM, "Saul Wold" wrote: On 3/12/19 6:54 AM, Penney, Don wrote: > Hi Yong, > > Please see the following reference: > > https://docs.starlingx.io/installation_guide/index.html#nvme-drive-as-boot-drive > > Edit the kernel boot parameter. After you are presented with the > StarlingX ISO boot options and after you have selected the preferred > installation option (e.g. Standard Configuration / All-in-One Controller > Configuration), press the TAB key to edit the Kernel boot parameters. > Modify the *boot_device* and *rootfs_device* from the default *sda* so > that it is the correct device name for the NVMe drive (e.g. “nvme0n1”). > While editing the kernel cmdline is a workaround for this issue, does it also make sense to have a launchpad issue and work to fix the logic in selecting an appropriate boot/rootfs device target. There already is some logic to check for a USB device and fail out, so why not move that into the loop and have it auto detect nvme devices. Another option would be to change the ordering in pre_disk_setup_common code. Sau! > Cheers, > > Don. > > *From:*Hu, Yong [mailto:yong.hu at intel.com] > *Sent:* Tuesday, March 12, 2019 8:51 AM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] about NVME disk as the boot disk > > Hi folks, > > I was installing StarlingX in a NUC with 2 NVME disks (without other HD > or SATA disks), and the installation was ended up with an issue as follows: > > “ERROR: Specified installation (sda) or boot (sda) device is a USB drive.” > > It seemed NVME disk was not recognized as valid boot disk. > > With the help from @Saul, we found in “bsp-files/grub.cfg”, > “boot_device” and “rootfs_device” were by default set as “sda” in ks > cmdline: > > /linuxefi /vmlinuz inst.ks=hd:LABEL=oe_iso_boot:/smallsystem_ks.cfg > boot_device=sda rootfs_device=sda biosdevname=0 usbcore.autosuspend=-1 > console=tty0 inst.text inst.stage2=hd:LABEL=oe_iso_boot inst.gpt > security_profile=standard user_namespace.enable=1/ > > So, there are 2 ways to make NVME disks work as boot disk: > > 1. to change the grub cmdline, with “nvme0n1” for “rootfs_device” and > “boot_device” accordingly, during the installation. > 2. Not to set “rootfs_device” and “boot_device” in ks cmdline, and let > “bsp-files/kickstarts/pre_disk_setup_common.cfg” detect “nvme0n1” > dynamically. > > Though, I wonder if there are other better ways in such a case. > > Regards, > > Yong > > > _______________________________________________ > 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 Wed Mar 13 03:57:13 2019 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 13 Mar 2019 03:57:13 +0000 Subject: [Starlingx-discuss] Potential failure in stx-openstack application In-Reply-To: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA7B660@ALA-MBD.corp.ad.wrs.com> References: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA7B660@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Bart: Thanks your announcement in advance . When I run docker login $REGISTRY, it prompt to input user and password , where can get user/password ? Thanks. BR Austin Sun. From: Wensley, Barton [mailto:Barton.Wensley at windriver.com] Sent: Wednesday, March 13, 2019 1:35 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Potential failure in stx-openstack application Public service announcement... If you are using a load built after Friday, you may see the stx-openstack apply failing - the symptom will be that the ceph-pools-audit pod will be scheduled to run on controller-1 and will be stuck in the ImagePullBackOff state. The following bug is tracking the issue: https://bugs.launchpad.net/starlingx/+bug/1819720 To work around this, you can do the following on controller-1 (as root): export KUBECONFIG=/etc/kubernetes/admin.conf export REGISTRY_HOST=192.168.204.2 export REGISTRY_PORT=9001 export REGISTRY=${REGISTRY_HOST}:${REGISTRY_PORT} docker login $REGISTRY docker pull $REGISTRY/docker.io/port/ceph-config-helper:v1.10.3 You can then redo your "system application-apply stx-openstack" and all should be good. Bart -------------- next part -------------- An HTML attachment was scrubbed... URL: From yatindrax.shashi at intel.com Wed Mar 13 11:14:36 2019 From: yatindrax.shashi at intel.com (Shashi, YatindraX) Date: Wed, 13 Mar 2019 11:14:36 +0000 Subject: [Starlingx-discuss] Configuration of internet access of a VM In-Reply-To: <1893840216.749048.1552408188934@communicator.strato.com> References: <1893840216.749048.1552408188934@communicator.strato.com> Message-ID: Hi Marcel, I tried once using same method of the Openstack where we create on public network (external NW- Flat type) and attach a VM to it. (https://docs.openstack.org/liberty/install-guide-rdo/launch-instance-networks-public.html) And I was able to access public network. I have also used a router when I have VM attached to the private network. In the router I have added the external gateway of the external Network. Mit freundlichen Grüßen, with best regards, Yatindra Shashi -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Tuesday, March 12, 2019 5:30 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Configuration of internet access of a VM Hi, I want to setup an internet access of one of my VM (simplex config). I am a little bit puzzled what kind of networks and routes do I need to configure. Can someone point me to some documentation how this is intended to work? Thanks Marcel _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Bill.Zvonar at windriver.com Wed Mar 13 11:25:11 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 13 Mar 2019 11:25:11 +0000 Subject: [Starlingx-discuss] Community Call (March 13, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC0A16CD4@ALA-MBD.corp.ad.wrs.com> Hi folks - for tomorrow's Community call, please note that we've switched to DST here in Ottawa, so the start time may change for you. The meeting will start at 10am EDT, or 2pm UTC - please check [3] for the start time in your time-zone if you're unsure. Thanks, Bill... [0] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1500_UTC_-_Community_Call [1] etherpad: https://etherpad.openstack.org/p/stx-status [3] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190313T1400 From: Zvonar, Bill Sent: Tuesday, February 19, 2019 1:44 PM To: starlingx-discuss at lists.starlingx.io Subject: Call for Agenda Items for Community Call (Feb 20, 2019) Hi folks - for tomorrow's Community call, please add any items you'd like to see on the agenda to the etherpad [1]. Thanks, Bill... [0] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1500_UTC_-_Community_Call [1] etherpad: https://etherpad.openstack.org/p/stx-status -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Mar 13 11:28:07 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 13 Mar 2019 11:28:07 +0000 Subject: [Starlingx-discuss] Community Call (March 13, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC0A16CEF@ALA-MBD.corp.ad.wrs.com> And of course that should've said *today's* Community call... From: Zvonar, Bill Sent: Wednesday, March 13, 2019 7:25 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: Community Call (March 13, 2019) Hi folks - for today's Community call, please note that we've switched to DST here in Ottawa, so the start time may change for you. The meeting will start at 10am EDT, or 2pm UTC - please check [3] for the start time in your time-zone if you're unsure. Thanks, Bill... [0] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1500_UTC_-_Community_Call [1] etherpad: https://etherpad.openstack.org/p/stx-status [3] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190313T1400 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Barton.Wensley at windriver.com Wed Mar 13 12:00:08 2019 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Wed, 13 Mar 2019 12:00:08 +0000 Subject: [Starlingx-discuss] Potential failure in stx-openstack application In-Reply-To: References: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA7B660@ALA-MBD.corp.ad.wrs.com> Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA7B99D@ALA-MBD.corp.ad.wrs.com> If you issue the commands below when logged in as the root user, the username will default to "admin". You would then use the "admin" password that was configured when you ran config_controller. Bart From: Sun, Austin [mailto:austin.sun at intel.com] Sent: March 12, 2019 11:57 PM To: Wensley, Barton; starlingx-discuss at lists.starlingx.io Subject: RE: Potential failure in stx-openstack application Hi Bart: Thanks your announcement in advance . When I run docker login $REGISTRY, it prompt to input user and password , where can get user/password ? Thanks. BR Austin Sun. From: Wensley, Barton [mailto:Barton.Wensley at windriver.com] Sent: Wednesday, March 13, 2019 1:35 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Potential failure in stx-openstack application Public service announcement... If you are using a load built after Friday, you may see the stx-openstack apply failing - the symptom will be that the ceph-pools-audit pod will be scheduled to run on controller-1 and will be stuck in the ImagePullBackOff state. The following bug is tracking the issue: https://bugs.launchpad.net/starlingx/+bug/1819720 To work around this, you can do the following on controller-1 (as root): export KUBECONFIG=/etc/kubernetes/admin.conf export REGISTRY_HOST=192.168.204.2 export REGISTRY_PORT=9001 export REGISTRY=${REGISTRY_HOST}:${REGISTRY_PORT} docker login $REGISTRY docker pull $REGISTRY/docker.io/port/ceph-config-helper:v1.10.3 You can then redo your "system application-apply stx-openstack" and all should be good. Bart -------------- next part -------------- An HTML attachment was scrubbed... URL: From liang.a.fang at intel.com Wed Mar 13 13:21:03 2019 From: liang.a.fang at intel.com (Fang, Liang A) Date: Wed, 13 Mar 2019 13:21:03 +0000 Subject: [Starlingx-discuss] Code review of cinder raw cache in stx-config Message-ID: Hi Brent Regarding the raw cache review: https://review.openstack.org/#/c/633400/ Currently the code is implemented according the discussion before between Ovidiu and Lisa: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-January/002548.html The raw cache is configured via "system storage-backend-modify". e.g. system storage-backend-modify ceph-store cinder_raw_cache_gib=10 Your opinion is to decouple openstack from the storage backend. Thanks for your comment. I take a look of system subcommand, there's no subcommand for openstack currently, at this point "system storage-backend-modify" seems is the best choice. Should we add subcommand "openstack"? Something like: system openstack cinder_raw_cache_gib=10 Or should we config openstack in other way? Could you please give suggestion on this? Thank you very much Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Wed Mar 13 13:47:30 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 13 Mar 2019 13:47:30 +0000 Subject: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack Distro meeting, 3/13 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35EC8C9F@SHSMSX104.ccr.corp.intel.com> Agenda & Notes for 3/13 meeting: - CentOS 7.6 merged to Master, review 1st daily test report (Ada) LP 1819717 broke the build after CentOS 7.6 branch merged, due to python-betamax is higher. Issue has been fixed in python-keystoneauth1.spec file. one successful build from Cengen: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190312T163454Z/outputs/iso/bootimage.iso, it may have Ceph deployment issue, and it was fixed by patch https://review.openstack.org/642886, which broke the current tip buld, and now fixed by patch: https://review.openstack.org/#/c/642943/ one Intel internal build: http://starlingx-hub.zpn.intel.com/ISO/stx-2019-03-12-172-master.iso Recommendation: generate a new build with tip and we should have a good build including 7.6! Watching the next daily sanity to see the Master healthy status after 7.6 merge. - Ceph upgrade status (Ovidiu/Daniel, Changcheng/Tingjie) Milestone#1 finished with feature enabled. Ceph mimic enabled in feature branch working w/ 2+2+2 config. Daniel is now starting on rebasing from master. A list of known issues: - mon_max_pg_per_osd needs to be increased - cinder-volumes pool is not created - "repo status" lists ceph submodule contents - missing mgr-restful-plugin pid file - pools need activation - need to review release notes jewel -> mimic Yong is still work in progress to repro success from Daniel from Intel's side.Yong has 2 controller + 2 compute + 2 storage, but Rados-gw was disabled, with Daniel's workaround, it might be possible to enable rados-gw manually. we are not yet in instiate OpenStack VM - let's just repro what Daniel has. Tngjie deployed 2+2+2 with virtual machine not finished yet. Pending task - to improve the build efficiency with Ceph. Release notes review: Vivian/Tingjie to setup meeting for overal release notes from ceph and understand what's going to impact StarlingX. - DevStack update (Dean/Yi) The pending patches from Dean have been merge. There will be more changes coming. Yi/Martin have several patches pending review, and have dependencies among each other. Dean is reviewing those patches. 2 patches for compilation issues have been merged (metal and nfv). 9 patches under review. Most of the services should be able to brought up: nfv, metal, fault and config. Will work on stx-ha after the others merged. it is on top of the dependency chain. two issues: sysInv API broken on Ubuntu Bionic. task created and Martin is on it. mtce-agent service also broken on bionic, Yi is working on it. - Opens (all) - QAT Driver Upversion: https://storyboard.openstack.org/#!/story/2004901 - The current version used by StarlingX is from July 2017 ( 1.0.3-42) - Release notes: https://01.org/sites/default/files/downloads//336211-009qatrelnotes.pdf, latest release is Dec 2018 (1.7.L.4.4.0-00023) - Need input from the TLs (Brent & Saul) on whether to proceed Agreed to upversion. Testing is needed for qat-dh895xcc (pci version) & qat-c62x (more modern on-board) - Remove libvirt/qemu unneded patches: https://storyboard.openstack.org/#!/story/2005212 - With the move to nova master, some of the libvirt patches that we have are not required. - This story tracks the removal of those patches and also suggests looking at the remaining patches to see if any others can be removed. - Any concerns from the TLs (Brent & Saul) with doing this? Jim Somerville is ready to take this on. Agreed to go ahead with this. This is low risk and will reduce our patch maintenance cost moving forward. -----Original Appointment----- From: Xie, Cindy Sent: Monday, November 5, 2018 2:27 PM To: Xie, Cindy; Troyer, Dean; Zhu, Vivian; Hu, Yong; Lin, Shuicheng; Shang, Dehao; Somerville, Jim; Wold, Saul; Sun, Austin; Jones, Bruce E; Liu, ZhipengS; 'Rowsell, Brent'; 'Khalil, Ghada'; starlingx-discuss at lists.starlingx.io; Waheed, Numan Cc: Perez Carranza, Jose; 'Hellmann, Gil'; 'Seiler, Glenn'; 'Young, Ken'; Arce Moreno, Abraham; Cobbley, David A; Fang, Liang A; 'Eslimi, Dariush'; Hu, Wei W; Martinez Monroy, Elio; 'Waines, Greg'; Lara, Cesar; Armstrong, Robert H; 'Chen, Jacky'; Martinez Landa, Hayde; 'Poncea, Ovidiu'; Perez Rodriguez, Humberto I; Gomez, Juan P; Shuquan Huang Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, March 13, 2019 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 Mon Mar 11 13:17:09 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Mon, 11 Mar 2019 13:17:09 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> Message-ID: Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can't get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can't ping each other. The DHCP exists and VMs can't ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie ; Khalil, Ghada ; Richard, Joseph ; Peters, Matt ; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio ; Zhao, Forrest ; Xie, Cindy ; Cabrales, Ada ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris's guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don't believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don't know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I'm trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I'm responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don't know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing "system host-unlock compute-0", it will report "Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address". But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: dhcp-ping-vm.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: vm-ping-dhcp.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: openstack-endpoint-list.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ovs-ofctl-dump-flows.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ovs-vsctl-show.txt URL: From forrest.zhao at intel.com Mon Mar 11 13:54:13 2019 From: forrest.zhao at intel.com (Zhao, Forrest) Date: Mon, 11 Mar 2019 13:54:13 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> Message-ID: <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt ; Richard, Joseph ; Khalil, Ghada ; Chris.Winnicki at windriver.com; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio ; Zhao, Forrest ; Xie, Cindy ; Cabrales, Ada ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can't get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can't ping each other. The DHCP exists and VMs can't ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris's guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don't believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don't know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I'm trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I'm responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don't know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing "system host-unlock compute-0", it will report "Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address". But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Mon Mar 11 14:05:04 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Mon, 11 Mar 2019 14:05:04 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie ; Peters, Matt ; Richard, Joseph ; Khalil, Ghada ; Chris.Winnicki at windriver.com; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio ; Xie, Cindy ; Cabrales, Ada ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can't get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can't ping each other. The DHCP exists and VMs can't ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris's guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don't believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don't know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I'm trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I'm responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don't know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing "system host-unlock compute-0", it will report "Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address". But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From chenjie.xu at intel.com Mon Mar 11 14:40:04 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Mon, 11 Mar 2019 14:40:04 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi Cindy, Thank you for your information! The following issue is not exactly the same as mine: https://bugs.launchpad.net/starlingx/+bug/1819031 In this issue, the DHCP works and external network can reach the VMs. However in my case, VMs can't get IP from DHCP and external network can't reach VMs even with an IP allocated by myself. Best Regards, Xu, Chenjie From: Xie, Cindy Sent: Monday, March 11, 2019 10:05 PM To: Zhao, Forrest ; Xu, Chenjie ; Peters, Matt ; Richard, Joseph ; Khalil, Ghada ; Chris.Winnicki at windriver.com; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio ; Cabrales, Ada ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can't get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can't ping each other. The DHCP exists and VMs can't ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris's guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don't believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don't know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I'm trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I'm responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don't know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing "system host-unlock compute-0", it will report "Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address". But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Mon Mar 11 14:51:54 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 11 Mar 2019 14:51:54 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> To answer Forrest's question: Do you know if OVS/DPDK has been tested after cut-over to container? I have seen Green sanity reports from Ada's team since the cut-over. I expect this covers basic ovs-dpdk functional testing. Ada, please correct me if I am wrong. Regarding https://bugs.launchpad.net/starlingx/+bug/1819031, we've requested information from the reporter on how reproducible this issue is. As far as I know, it was reported on one system only. We're waiting for more information from Peng. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Monday, March 11, 2019 10:40 AM To: Xie, Cindy; Zhao, Forrest; Peters, Matt; Richard, Joseph; Khalil, Ghada; Winnicki, Chris; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, Thank you for your information! The following issue is not exactly the same as mine: https://bugs.launchpad.net/starlingx/+bug/1819031 In this issue, the DHCP works and external network can reach the VMs. However in my case, VMs can't get IP from DHCP and external network can't reach VMs even with an IP allocated by myself. Best Regards, Xu, Chenjie From: Xie, Cindy Sent: Monday, March 11, 2019 10:05 PM To: Zhao, Forrest >; Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can't get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can't ping each other. The DHCP exists and VMs can't ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris's guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don't believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don't know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I'm trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I'm responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don't know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing "system host-unlock compute-0", it will report "Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address". But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Mon Mar 11 15:48:24 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 11 Mar 2019 15:48:24 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4CA92C@ALA-MBD.corp.ad.wrs.com> To answer Forrest's question: Do you know if OVS/DPDK has been tested after cut-over to container? I have seen Green sanity reports from Ada's team since the cut-over. I expect this covers basic ovs-dpdk functional testing. Ada, please correct me if I am wrong. Regarding https://bugs.launchpad.net/starlingx/+bug/1819031, we've requested information from the reporter on how reproducible this issue is. As far as I know, it was reported on one system only. We're waiting for more information from Peng. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Monday, March 11, 2019 10:40 AM To: Xie, Cindy; Zhao, Forrest; Peters, Matt; Richard, Joseph; Khalil, Ghada; Winnicki, Chris; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, Thank you for your information! The following issue is not exactly the same as mine: https://bugs.launchpad.net/starlingx/+bug/1819031 In this issue, the DHCP works and external network can reach the VMs. However in my case, VMs can't get IP from DHCP and external network can't reach VMs even with an IP allocated by myself. Best Regards, Xu, Chenjie From: Xie, Cindy Sent: Monday, March 11, 2019 10:05 PM To: Zhao, Forrest >; Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can't get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can't ping each other. The DHCP exists and VMs can't ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris's guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don't believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don't know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I'm trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I'm responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don't know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing "system host-unlock compute-0", it will report "Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address". But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From elio.martinez.monroy at intel.com Mon Mar 11 16:28:34 2019 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Mon, 11 Mar 2019 16:28:34 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> Message-ID: <1466AF2176E6F040BD63860D0A241BBD46C99EC0@FMSMSX109.amr.corp.intel.com> Hi guys, Those sanity results doesn't contain any OVS-DPDK feature testing. We are just starting with our tests this week. Please refer to the following document https://docs.google.com/spreadsheets/d/1zf3U1QSxxfsokWQpvNuO7sVvA5zTP0-OARoRu_I6Pyg/edit#gid=1269184376. Beside that. What I'm thinking is that for our feature testing (manual execution), we can run the sanity set as well. And if you decide we can add some test for ovs in a short future. Please let me know what do you think. Adding Juan Carlos (Sanity testing) and Richo (ovs/dpdk testing) BR Elio From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Monday, March 11, 2019 8:52 AM To: Xu, Chenjie ; Xie, Cindy ; Zhao, Forrest ; Peters, Matt ; Richard, Joseph ; Winnicki, Chris ; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio ; Cabrales, Ada ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing To answer Forrest's question: Do you know if OVS/DPDK has been tested after cut-over to container? I have seen Green sanity reports from Ada's team since the cut-over. I expect this covers basic ovs-dpdk functional testing. Ada, please correct me if I am wrong. Regarding https://bugs.launchpad.net/starlingx/+bug/1819031, we've requested information from the reporter on how reproducible this issue is. As far as I know, it was reported on one system only. We're waiting for more information from Peng. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Monday, March 11, 2019 10:40 AM To: Xie, Cindy; Zhao, Forrest; Peters, Matt; Richard, Joseph; Khalil, Ghada; Winnicki, Chris; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, Thank you for your information! The following issue is not exactly the same as mine: https://bugs.launchpad.net/starlingx/+bug/1819031 In this issue, the DHCP works and external network can reach the VMs. However in my case, VMs can't get IP from DHCP and external network can't reach VMs even with an IP allocated by myself. Best Regards, Xu, Chenjie From: Xie, Cindy Sent: Monday, March 11, 2019 10:05 PM To: Zhao, Forrest >; Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can't get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can't ping each other. The DHCP exists and VMs can't ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris's guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don't believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don't know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I'm trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I'm responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don't know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing "system host-unlock compute-0", it will report "Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address". But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Peters at windriver.com Mon Mar 11 16:28:05 2019 From: Matt.Peters at windriver.com (Peters, Matt) Date: Mon, 11 Mar 2019 16:28:05 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> Message-ID: <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> If you co-locate the VMs on the same compute host (lock the other computes) do things work as expected? I.e. is it only when you are traversing the physical network that things are not pingable? -Matt From: Ghada Khalil Date: Monday, March 11, 2019 at 10:51 AM To: "Xu, Chenjie" , "Xie, Cindy" , "Zhao, Forrest" , "Peters, Matt" , "Richard, Joseph" , "Winnicki, Chris" , "Lin, Shuicheng" Cc: "starlingx-discuss at lists.starlingx.io" , "Martinez Monroy, Elio" , "Cabrales, Ada" , "Jones, Bruce E" , "Qin, Kailun" , "Guo, Ruijing" , "Le, Huifeng" Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing To answer Forrest’s question: Do you know if OVS/DPDK has been tested after cut-over to container? I have seen Green sanity reports from Ada’s team since the cut-over. I expect this covers basic ovs-dpdk functional testing. Ada, please correct me if I am wrong. Regarding https://bugs.launchpad.net/starlingx/+bug/1819031, we’ve requested information from the reporter on how reproducible this issue is. As far as I know, it was reported on one system only. We’re waiting for more information from Peng. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Monday, March 11, 2019 10:40 AM To: Xie, Cindy; Zhao, Forrest; Peters, Matt; Richard, Joseph; Khalil, Ghada; Winnicki, Chris; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, Thank you for your information! The following issue is not exactly the same as mine: https://bugs.launchpad.net/starlingx/+bug/1819031 In this issue, the DHCP works and external network can reach the VMs. However in my case, VMs can’t get IP from DHCP and external network can’t reach VMs even with an IP allocated by myself. Best Regards, Xu, Chenjie From: Xie, Cindy Sent: Monday, March 11, 2019 10:05 PM To: Zhao, Forrest >; Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can’t get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can’t ping each other. The DHCP exists and VMs can’t ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris’s guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don’t believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don’t know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I’m trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I’m responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don’t know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing “system host-unlock compute-0”, it will report “Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address”. But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From yatindrax.shashi at intel.com Tue Mar 12 11:31:01 2019 From: yatindrax.shashi at intel.com (Shashi, YatindraX) Date: Tue, 12 Mar 2019 11:31:01 +0000 Subject: [Starlingx-discuss] StarlingX Magnum cluster-template giving error as "errors" Message-ID: Hi All,, While running the command to create magnum cluster template or any magnum command I receive error like ERROR: "errors" I am using simplex mode installation of the StarlingX. I checked the log files of magnum api and it shows some authentication problem as below " 2019-03-11 17:53:41.394 241971 WARNING oslo_reports.guru_meditation_report [-] Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so please use SIGUSR2 to generate reports. 2019-03-11 17:53:41.395 241971 INFO magnum.api.app [-] Full WSGI config used: /etc/magnum/api-paste.ini 2019-03-11 17:53:41.493 241971 WARNING keystonemiddleware.auth_token [-] AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True. 2019-03-11 17:53:41.505 241971 INFO magnum.cmd.api [-] Starting server in PID 241971 2019-03-11 17:53:41.510 241971 INFO magnum.cmd.api [-] Serving on http://127.168.204.2:9511 2019-03-11 17:53:41.511 241971 INFO magnum.cmd.api [-] Server will handle each request in a new process up to 112 concurrent processes 2019-03-11 17:53:41.511 241971 INFO werkzeug [-] * Running on http://127.168.204.2:9511/ 2019-03-11 17:53:56.090 244289 WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Unauthorized"}}: Unauthorized: The request you have made requires authentication. (HTTP 401) (Request-ID: req-361ef3fe-3749-4959-b33f-69c1a10fd84b) 2019-03-11 17:53:56.403 244289 WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Unauthorized"}}: Unauthorized: The request you have made requires authentication. (HTTP 401) (Request-ID: req-06c1c183-3d8d-48fa-95f5-311c77990435) 2019-03-11 17:53:56.403 244289 CRITICAL keystonemiddleware.auth_token [-] Unable to validate token: Identity server rejected authorization necessary to fetch token data: ServiceError: Identity server rejected authorization necessary to fetch token data 2019-03-11 17:53:56.404 244289 INFO werkzeug [-] 127.168.204.3 - - [11/Mar/2019 17:53:56] "POST /v1/clustertemplates HTTP/1.1" 503 - 2019-03-12 10:02:27.172 202974 WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Unauthorized"}}: Unauthorized: The request you have made requires authentication. (HTTP 401) (Request-ID: req-6be81e7b-ac2e-4943-8967-b5a1adab1139) 2019-03-12 10:02:27.481 202974 WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Unauthorized"}}: Unauthorized: The request you have made requires authentication. (HTTP 401) (Request-ID: req-4c848660-982f-491f-a3a8-186a5f3f124e) 2019-03-12 10:02:27.482 202974 CRITICAL keystonemiddleware.auth_token [-] Unable to validate token: Identity server rejected authorization necessary to fetch token data: ServiceError: Identity server rejected authorization necessary to fetch token data 2019-03-12 10:02:27.482 202974 INFO werkzeug [-] 127.168.204.3 - - [12/Mar/2019 10:02:27] "GET /v1/mservices HTTP/1.1" 503 - " Where as my magnum KEYSTONE_AUTHTOKEN configuration in magnum.conf is as below. " # Authentication type to load (string value) # Deprecated group/name - [keystone_authtoken]/auth_plugin #auth_type = auth_type = password # Config Section from which to load plugin specific options (string value) #auth_section = project_name=services username=magnum password=f7e60b57917fTi0* auth_url=http://127.168.204.2:5000" I checked the user magnum, and its domain. It looks configured to me. Will you tell me if I am missing something. If you need any further information then please let me know. Mit freundlichen Grüßen, with best regards, Yatindra Shashi Intel Corporation Munich, Germany -------------- next part -------------- An HTML attachment was scrubbed... URL: From yatindrax.shashi at intel.com Tue Mar 12 11:34:45 2019 From: yatindrax.shashi at intel.com (Shashi, YatindraX) Date: Tue, 12 Mar 2019 11:34:45 +0000 Subject: [Starlingx-discuss] StarlingX Magnum cluster-template giving error as "errors" In-Reply-To: References: Message-ID: Hi All, Please also find attached screenshot of magnum -debug service-list. Mit freundlichen Grüßen, with best regards, Yatindra Shashi From: Shashi, YatindraX Sent: Tuesday, March 12, 2019 12:31 PM To: 'starlingx-discuss at lists.starlingx.io' Cc: Marcel Wagner (marcel.wagner at intel.com) Subject: StarlingX Magnum cluster-template giving error as "errors" Hi All,, While running the command to create magnum cluster template or any magnum command I receive error like ERROR: "errors" I am using simplex mode installation of the StarlingX. I checked the log files of magnum api and it shows some authentication problem as below " 2019-03-11 17:53:41.394 241971 WARNING oslo_reports.guru_meditation_report [-] Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so please use SIGUSR2 to generate reports. 2019-03-11 17:53:41.395 241971 INFO magnum.api.app [-] Full WSGI config used: /etc/magnum/api-paste.ini 2019-03-11 17:53:41.493 241971 WARNING keystonemiddleware.auth_token [-] AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True. 2019-03-11 17:53:41.505 241971 INFO magnum.cmd.api [-] Starting server in PID 241971 2019-03-11 17:53:41.510 241971 INFO magnum.cmd.api [-] Serving on http://127.168.204.2:9511 2019-03-11 17:53:41.511 241971 INFO magnum.cmd.api [-] Server will handle each request in a new process up to 112 concurrent processes 2019-03-11 17:53:41.511 241971 INFO werkzeug [-] * Running on http://127.168.204.2:9511/ 2019-03-11 17:53:56.090 244289 WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Unauthorized"}}: Unauthorized: The request you have made requires authentication. (HTTP 401) (Request-ID: req-361ef3fe-3749-4959-b33f-69c1a10fd84b) 2019-03-11 17:53:56.403 244289 WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Unauthorized"}}: Unauthorized: The request you have made requires authentication. (HTTP 401) (Request-ID: req-06c1c183-3d8d-48fa-95f5-311c77990435) 2019-03-11 17:53:56.403 244289 CRITICAL keystonemiddleware.auth_token [-] Unable to validate token: Identity server rejected authorization necessary to fetch token data: ServiceError: Identity server rejected authorization necessary to fetch token data 2019-03-11 17:53:56.404 244289 INFO werkzeug [-] 127.168.204.3 - - [11/Mar/2019 17:53:56] "POST /v1/clustertemplates HTTP/1.1" 503 - 2019-03-12 10:02:27.172 202974 WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Unauthorized"}}: Unauthorized: The request you have made requires authentication. (HTTP 401) (Request-ID: req-6be81e7b-ac2e-4943-8967-b5a1adab1139) 2019-03-12 10:02:27.481 202974 WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Unauthorized"}}: Unauthorized: The request you have made requires authentication. (HTTP 401) (Request-ID: req-4c848660-982f-491f-a3a8-186a5f3f124e) 2019-03-12 10:02:27.482 202974 CRITICAL keystonemiddleware.auth_token [-] Unable to validate token: Identity server rejected authorization necessary to fetch token data: ServiceError: Identity server rejected authorization necessary to fetch token data 2019-03-12 10:02:27.482 202974 INFO werkzeug [-] 127.168.204.3 - - [12/Mar/2019 10:02:27] "GET /v1/mservices HTTP/1.1" 503 - " Where as my magnum KEYSTONE_AUTHTOKEN configuration in magnum.conf is as below. " # Authentication type to load (string value) # Deprecated group/name - [keystone_authtoken]/auth_plugin #auth_type = auth_type = password # Config Section from which to load plugin specific options (string value) #auth_section = project_name=services username=magnum password=f7e60b57917fTi0* auth_url=http://127.168.204.2:5000" I checked the user magnum, and its domain. It looks configured to me. Will you tell me if I am missing something. If you need any further information then please let me know. Mit freundlichen Grüßen, with best regards, Yatindra Shashi Intel Corporation Munich, Germany -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Magnum_debug_command.png Type: image/png Size: 124688 bytes Desc: Magnum_debug_command.png URL: From Ghada.Khalil at windriver.com Tue Mar 12 14:43:37 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 12 Mar 2019 14:43:37 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <1466AF2176E6F040BD63860D0A241BBD46C99EC0@FMSMSX109.amr.corp.intel.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <1466AF2176E6F040BD63860D0A241BBD46C99EC0@FMSMSX109.amr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4CBEC5@ALA-MBD.corp.ad.wrs.com> Hi Elio / JC / Ada, Sanity should include a basic VM connectivity test. Please update the sanity suite to cover this. Thanks, Ghada From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Monday, March 11, 2019 12:29 PM To: Khalil, Ghada; Xu, Chenjie; Xie, Cindy; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng; Perez, Ricardo O; Alonso, Juan Carlos Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi guys, Those sanity results doesn't contain any OVS-DPDK feature testing. We are just starting with our tests this week. Please refer to the following document https://docs.google.com/spreadsheets/d/1zf3U1QSxxfsokWQpvNuO7sVvA5zTP0-OARoRu_I6Pyg/edit#gid=1269184376. Beside that. What I'm thinking is that for our feature testing (manual execution), we can run the sanity set as well. And if you decide we can add some test for ovs in a short future. Please let me know what do you think. Adding Juan Carlos (Sanity testing) and Richo (ovs/dpdk testing) BR Elio From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Monday, March 11, 2019 8:52 AM To: Xu, Chenjie >; Xie, Cindy >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing To answer Forrest's question: Do you know if OVS/DPDK has been tested after cut-over to container? I have seen Green sanity reports from Ada's team since the cut-over. I expect this covers basic ovs-dpdk functional testing. Ada, please correct me if I am wrong. Regarding https://bugs.launchpad.net/starlingx/+bug/1819031, we've requested information from the reporter on how reproducible this issue is. As far as I know, it was reported on one system only. We're waiting for more information from Peng. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Monday, March 11, 2019 10:40 AM To: Xie, Cindy; Zhao, Forrest; Peters, Matt; Richard, Joseph; Khalil, Ghada; Winnicki, Chris; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, Thank you for your information! The following issue is not exactly the same as mine: https://bugs.launchpad.net/starlingx/+bug/1819031 In this issue, the DHCP works and external network can reach the VMs. However in my case, VMs can't get IP from DHCP and external network can't reach VMs even with an IP allocated by myself. Best Regards, Xu, Chenjie From: Xie, Cindy Sent: Monday, March 11, 2019 10:05 PM To: Zhao, Forrest >; Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can't get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can't ping each other. The DHCP exists and VMs can't ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris's guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don't believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don't know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I'm trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I'm responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don't know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing "system host-unlock compute-0", it will report "Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address". But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From chenjie.xu at intel.com Mon Mar 11 16:38:47 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Mon, 11 Mar 2019 16:38:47 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> Message-ID: Hi team, For Matt, I just tried to lock compute-1 to ensure the VMs is on the same compute host. But it still doesn’t work. The DHCP, router and VMs all located on compute-0. For Ghada, I checked the test cases listed in sanity test. I see that there is no test case to test the connectivity between VMs. Need confirmation from Ada’s team. https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 12, 2019 12:28 AM To: Khalil, Ghada ; Xu, Chenjie ; Xie, Cindy ; Zhao, Forrest ; Richard, Joseph ; Winnicki, Chris ; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio ; Cabrales, Ada ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing If you co-locate the VMs on the same compute host (lock the other computes) do things work as expected? I.e. is it only when you are traversing the physical network that things are not pingable? -Matt From: Ghada Khalil > Date: Monday, March 11, 2019 at 10:51 AM To: "Xu, Chenjie" >, "Xie, Cindy" >, "Zhao, Forrest" >, "Peters, Matt" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" > Cc: "starlingx-discuss at lists.starlingx.io" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing To answer Forrest’s question: Do you know if OVS/DPDK has been tested after cut-over to container? I have seen Green sanity reports from Ada’s team since the cut-over. I expect this covers basic ovs-dpdk functional testing. Ada, please correct me if I am wrong. Regarding https://bugs.launchpad.net/starlingx/+bug/1819031, we’ve requested information from the reporter on how reproducible this issue is. As far as I know, it was reported on one system only. We’re waiting for more information from Peng. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Monday, March 11, 2019 10:40 AM To: Xie, Cindy; Zhao, Forrest; Peters, Matt; Richard, Joseph; Khalil, Ghada; Winnicki, Chris; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, Thank you for your information! The following issue is not exactly the same as mine: https://bugs.launchpad.net/starlingx/+bug/1819031 In this issue, the DHCP works and external network can reach the VMs. However in my case, VMs can’t get IP from DHCP and external network can’t reach VMs even with an IP allocated by myself. Best Regards, Xu, Chenjie From: Xie, Cindy Sent: Monday, March 11, 2019 10:05 PM To: Zhao, Forrest >; Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can’t get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can’t ping each other. The DHCP exists and VMs can’t ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris’s guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don’t believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don’t know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I’m trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I’m responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don’t know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing “system host-unlock compute-0”, it will report “Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address”. But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Numan.Waheed at windriver.com Tue Mar 12 17:46:36 2019 From: Numan.Waheed at windriver.com (Waheed, Numan) Date: Tue, 12 Mar 2019 17:46:36 +0000 Subject: [Starlingx-discuss] [ Testing ] Meeting agenda - 03/12/2019 In-Reply-To: <3CAA827B7A79BA46B15B280EC82088FE4828DD97@ALA-MBD.corp.ad.wrs.com> References: <3CAA827B7A79BA46B15B280EC82088FE4828DD97@ALA-MBD.corp.ad.wrs.com> Message-ID: <3CAA827B7A79BA46B15B280EC82088FE4828E669@ALA-MBD.corp.ad.wrs.com> Following are the minutes of meeting of stx-test call. Attendees: Elio, Fer, JP, Abraham, Numan, JC, Jose,Richo, Victor, Bill, Christopher 1. Plan Progress check - 30 Min Update Release Plan with planned dates - Ada to add dates on the release plan - Ada is away today. Numan will talk to her once she comes back tomorrow Regression Suite Submission to the repo Regression - AIO-SX - (JP) Will be done by Friday Regression - Backup & Restore - (Marvin) First draft is in Regression - Distributed Cloud - (Peng) Has not started yet. There will be a number of changes in the coming days. Regression - Gnoochi - Done - Making some changes. Should be done shortly Regression - FM - (Jeyan) Has not started yet but the changes are ready and will be uploaded soon Regression - HA - (Jeyan) Has not started yet but the changes are ready and will be uploaded soon Regression - Heat - (Fer) Uploaded 3 out of 12 test cases Regression - Horizon - Updates are complete but not uploaded to the repo. Probably need some more test cases as there are changes in Horizon Regression - Install and Config - (Peng) First draft is uploaded Regression - Maintenance - (Jeyan) Has not started yet but the changes are ready and will be uploaded soon Regression - Networking - (Elio) Updating the test cases. Larger number of test cases. Tentatively finishing by 03/29 Regression - Nova - (Wendy) Started uploading the testcases. Will be completing next week. She only needs to update the comments Regression - Security - (Fer) 36 out of 42 test cases uploaded. Most likely finish this week Regression - SNMP - (Jeyan) Has not started yet but the changes are ready and will be uploaded soon Regression - Storage - (Maria) Already merged. Regression - Inventory - Needs update System Test - (Ada) Needs update Distro.OpenStack patch elimination - Progress on test plan definition Jose: Finished analysis of Neutron, Horizon, Cinder and Glance. Wil be reviewed once Ada is back and then Test Plan creation will begin CentOS 7.6 testing after merge Q for Ada: Do we need to test it after the merge? OVS-DPDK upgrade Elio: Test cases are reviewed. Got feedback from Ghada. Waiting for Bare metal environment setup. Have received the ISO with OVS-DPDK and containers. Will start testing today. Plan to finish in two weeks. Number of test cases are only 17 but would be tested in diiferent ways on 2+2 config. Will be using different NICs Test Case Automation Elio: 21 out of 200 existing test cases are being worked at. 7 are fixed. 8 new test cases added. A bit behind the schedule. Estimating to have 50 test cases by EOW. Overall stability of the system is hindering progress. Stress and Stability Testing JC: Did not execute stress and stability last week due to Neutron commands issue. Will schedule an execution this week. 2. Format for Manual Test Cases - txt vs. rst - 10 Min Although it is worth showing the test cases on a wiki but it is not a mandatory requirement. If it is taking a lot of time uploading the test cases in rst format, then we should upload the test cases in txt format. Should we include results of each command in the test cases? (Ada, Numan to decide) 3. Dashboard Follow-up - 05 Min Bruce was not on the call. Bruce is supposed to reach out to CENGN for negociation about more space. 4. Opens - 15 Min Fer: Need Peng to make changes in the commit he has created about security test plan Elio: Storage test cases are merged by Maria. They will be given to Automation team. Numan: Elio will talk to Ada about uploading automation test cases developed by Intel automation team. From: Waheed, Numan Sent: March-11-19 3:56 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [ Testing ] Meeting agenda - 03/12/2019 Agenda for 03/12/2019 1. Plan Progress check - 30 Min Update Release Plan with planned dates Regression Suite Submission to the repo Distro.OpenStack patch elimination - Progress on test plan definition CentOS 7.6 testing after merge OVS-DPDK upgrade Test Case Automation Stress and Stability Testing 2. Format for Manual Test Cases - txt vs. rst - 10 Min 3. Dashboard Follow-up - 05 Min 4. Opens - 15 Min Please let me know if you would like to add anything in this agenda. Regards, Numan. -------------- next part -------------- An HTML attachment was scrubbed... URL: From chenjie.xu at intel.com Wed Mar 13 12:54:59 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Wed, 13 Mar 2019 12:54:59 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> Message-ID: Hi team, I installed StarlingX using following the March 5th ISO image and the issue still exists:http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190305T060000Z/outputs/iso/ Are there any steps not been written on the guide? I just followed the following guide: https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnStandard I checked the ovs-vswitchd.log and the following line maybe the cause: 23127 hugepages of size 2097152 reserved, but no mounted hugetlbfs found for that size It seems that something went wrong with hugepage. Some logs have been attached. If you have any idea about hugepage, please let me know. Peng has been added and hope Peng can provide some information about his environment. https://bugs.launchpad.net/starlingx/+bug/1819031 Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Tuesday, March 12, 2019 12:39 AM To: Peters, Matt ; Khalil, Ghada ; Xie, Cindy ; Zhao, Forrest ; Richard, Joseph ; Winnicki, Chris ; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio ; Cabrales, Ada ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, For Matt, I just tried to lock compute-1 to ensure the VMs is on the same compute host. But it still doesn’t work. The DHCP, router and VMs all located on compute-0. For Ghada, I checked the test cases listed in sanity test. I see that there is no test case to test the connectivity between VMs. Need confirmation from Ada’s team. https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 12, 2019 12:28 AM To: Khalil, Ghada >; Xu, Chenjie >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing If you co-locate the VMs on the same compute host (lock the other computes) do things work as expected? I.e. is it only when you are traversing the physical network that things are not pingable? -Matt From: Ghada Khalil > Date: Monday, March 11, 2019 at 10:51 AM To: "Xu, Chenjie" >, "Xie, Cindy" >, "Zhao, Forrest" >, "Peters, Matt" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" > Cc: "starlingx-discuss at lists.starlingx.io" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing To answer Forrest’s question: Do you know if OVS/DPDK has been tested after cut-over to container? I have seen Green sanity reports from Ada’s team since the cut-over. I expect this covers basic ovs-dpdk functional testing. Ada, please correct me if I am wrong. Regarding https://bugs.launchpad.net/starlingx/+bug/1819031, we’ve requested information from the reporter on how reproducible this issue is. As far as I know, it was reported on one system only. We’re waiting for more information from Peng. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Monday, March 11, 2019 10:40 AM To: Xie, Cindy; Zhao, Forrest; Peters, Matt; Richard, Joseph; Khalil, Ghada; Winnicki, Chris; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, Thank you for your information! The following issue is not exactly the same as mine: https://bugs.launchpad.net/starlingx/+bug/1819031 In this issue, the DHCP works and external network can reach the VMs. However in my case, VMs can’t get IP from DHCP and external network can’t reach VMs even with an IP allocated by myself. Best Regards, Xu, Chenjie From: Xie, Cindy Sent: Monday, March 11, 2019 10:05 PM To: Zhao, Forrest >; Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can’t get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can’t ping each other. The DHCP exists and VMs can’t ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris’s guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don’t believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don’t know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I’m trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I’m responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don’t know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing “system host-unlock compute-0”, it will report “Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address”. But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 192.168.204.52.yaml Type: application/octet-stream Size: 9491 bytes Desc: 192.168.204.52.yaml URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ovs-vswitchd.log Type: application/octet-stream Size: 207094 bytes Desc: ovs-vswitchd.log URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: meminfo.txt URL: From Matt.Peters at windriver.com Wed Mar 13 13:13:20 2019 From: Matt.Peters at windriver.com (Peters, Matt) Date: Wed, 13 Mar 2019 13:13:20 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> Message-ID: Hello, That message is a normal message from DPDK if you have multiple huge page sizes configured in your system. Openvswitch is configured to use 1G huge pages and will ignore the 2M huge pages. You can confirm this by looking at the Puppet logs to see what was configured and to ensure the 1G huge pages were mounted prior to openvswitch starting. -Matt From: "Xu, Chenjie" Date: Wednesday, March 13, 2019 at 8:55 AM To: "Peters, Matt" , Ghada Khalil , "Xie, Cindy" , "Zhao, Forrest" , "Richard, Joseph" , "Winnicki, Chris" , "Lin, Shuicheng" , "Peng, Peng" Cc: "'starlingx-discuss at lists.starlingx.io'" , "Martinez Monroy, Elio" , "Cabrales, Ada" , "Jones, Bruce E" , "Qin, Kailun" , "Guo, Ruijing" , "Le, Huifeng" Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I installed StarlingX using following the March 5th ISO image and the issue still exists:http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190305T060000Z/outputs/iso/ Are there any steps not been written on the guide? I just followed the following guide: https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnStandard I checked the ovs-vswitchd.log and the following line maybe the cause: 23127 hugepages of size 2097152 reserved, but no mounted hugetlbfs found for that size It seems that something went wrong with hugepage. Some logs have been attached. If you have any idea about hugepage, please let me know. Peng has been added and hope Peng can provide some information about his environment. https://bugs.launchpad.net/starlingx/+bug/1819031 Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Tuesday, March 12, 2019 12:39 AM To: Peters, Matt ; Khalil, Ghada ; Xie, Cindy ; Zhao, Forrest ; Richard, Joseph ; Winnicki, Chris ; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio ; Cabrales, Ada ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, For Matt, I just tried to lock compute-1 to ensure the VMs is on the same compute host. But it still doesn’t work. The DHCP, router and VMs all located on compute-0. For Ghada, I checked the test cases listed in sanity test. I see that there is no test case to test the connectivity between VMs. Need confirmation from Ada’s team. https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 12, 2019 12:28 AM To: Khalil, Ghada >; Xu, Chenjie >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing If you co-locate the VMs on the same compute host (lock the other computes) do things work as expected? I.e. is it only when you are traversing the physical network that things are not pingable? -Matt From: Ghada Khalil > Date: Monday, March 11, 2019 at 10:51 AM To: "Xu, Chenjie" >, "Xie, Cindy" >, "Zhao, Forrest" >, "Peters, Matt" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" > Cc: "starlingx-discuss at lists.starlingx.io" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing To answer Forrest’s question: Do you know if OVS/DPDK has been tested after cut-over to container? I have seen Green sanity reports from Ada’s team since the cut-over. I expect this covers basic ovs-dpdk functional testing. Ada, please correct me if I am wrong. Regarding https://bugs.launchpad.net/starlingx/+bug/1819031, we’ve requested information from the reporter on how reproducible this issue is. As far as I know, it was reported on one system only. We’re waiting for more information from Peng. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Monday, March 11, 2019 10:40 AM To: Xie, Cindy; Zhao, Forrest; Peters, Matt; Richard, Joseph; Khalil, Ghada; Winnicki, Chris; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, Thank you for your information! The following issue is not exactly the same as mine: https://bugs.launchpad.net/starlingx/+bug/1819031 In this issue, the DHCP works and external network can reach the VMs. However in my case, VMs can’t get IP from DHCP and external network can’t reach VMs even with an IP allocated by myself. Best Regards, Xu, Chenjie From: Xie, Cindy Sent: Monday, March 11, 2019 10:05 PM To: Zhao, Forrest >; Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can’t get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can’t ping each other. The DHCP exists and VMs can’t ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris’s guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don’t believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don’t know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I’m trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I’m responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don’t know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing “system host-unlock compute-0”, it will report “Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address”. But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Robert.Church at windriver.com Wed Mar 13 14:44:27 2019 From: Robert.Church at windriver.com (Church, Robert) Date: Wed, 13 Mar 2019 14:44:27 +0000 Subject: [Starlingx-discuss] Code review of cinder raw cache in stx-config Message-ID: <0BB14CDD-5E16-45BC-9117-E1787519E895@windriver.com> Hi Liang, I took a look at this yesterday to understand what you are up against here. Ideally we would want some combination of a system helm override/armada manifest change to automatically provision the Cinder image-volume cache when the stx-openstack application is installed. We do not want to use any platform specific interface changes (i.e. system backend-modify or a new API) since we want to decouple openstack k8s application dependencies from the general k8s platform provisioning. Using the current content on master, here are the following steps required by an end user to enable this feature: # Initial application install system application-apply stx-openstack # After install, the feature requires a project/user to manage the cache openstack project create --enable --description "Block Storage Internal Tenant" cinder-internal openstack user create --project cinder-internal cinder-internal TENANTID=$(openstack project list | awk /cinder-internal/'{print $2}') USERID=$(openstack user list | awk /cinder-internal/'{print $2}') # The created project/user are needed in cinder.conf along with enabling the cache for the specific backend (we define ceph-store as part of the original application apply). Reapply the application to trigger the armada upgrade to cinder system helm-override-update cinder openstack --reuse-values --set conf.cinder.DEFAULT.cinder_internal_tenant_project_id=$TENANTID system helm-override-update cinder openstack --reuse-values --set conf.cinder.DEFAULT.cinder_internal_tenant_user_id=$USERID system helm-override-update cinder openstack --reuse-values --set conf.backends.ceph-store.image_volume_cache_enabled=true system helm-override-update cinder openstack --reuse-values --set conf.backends.ceph-store.image_volume_cache_max_size_gb=10 system helm-override-update cinder openstack --reuse-values --set conf.backends.ceph-store.image_volume_cache_max_count=5 system application-apply stx-openstack Now, back to the desired approach. The challenge here is we need a way to create a project/user as part of the initial application install and look up the UUIDs to embed in an override in a declarative manner. I’m not sure this is possible in a single application apply. 1. We could enable creating the project/user as part of the Cinder bootstrap script, but these would not be created/available at the time overrides are declared for cinder’s configuration 2. We could use an existing project/user (i.e. admin) and avoid creating a dedicated cinder project/user, but again on the initial application install they are not available at the time overrides are declared for cinder’s configuration Looking across the charts and the helm-toolkit in the OSH projects, I have yet to see an easy way to accomplish this. I think you should check with the OSH project cores to see if they have any suggestions on the best way to tackle this as part of the first install of the Cinder chart OR if a two pass approach is required (install then upgrade) Bob From: "Fang, Liang A" Date: Wednesday, March 13, 2019 at 8:22 AM To: "Rowsell, Brent" Cc: Ovidiu Poncea , "Zhu, Vivian" , "Jones, Bruce E" , "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Code review of cinder raw cache in stx-config Hi Brent Regarding the raw cache review: https://review.openstack.org/#/c/633400/ Currently the code is implemented according the discussion before between Ovidiu and Lisa: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-January/002548.html The raw cache is configured via “system storage-backend-modify”. e.g. system storage-backend-modify ceph-store cinder_raw_cache_gib=10 Your opinion is to decouple openstack from the storage backend. Thanks for your comment. I take a look of system subcommand, there’s no subcommand for openstack currently, at this point “system storage-backend-modify” seems is the best choice. Should we add subcommand “openstack”? Something like: system openstack cinder_raw_cache_gib=10 Or should we config openstack in other way? Could you please give suggestion on this? Thank you very much Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Wed Mar 13 15:51:05 2019 From: scott.little at windriver.com (Scott Little) Date: Wed, 13 Mar 2019 11:51:05 -0400 Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 16 - Failure! In-Reply-To: <1573627026.94.1552430719091.JavaMail.javamailuser@localhost> References: <1573627026.94.1552430719091.JavaMail.javamailuser@localhost> Message-ID: <7d674b12-5e98-e5e0-8427-90da2ea9350f@windriver.com> 404 errors during download_mirror.sh strikes again. Let's get eyes on https://review.openstack.org/#/c/641495/   please Scott On 2019-03-12 6:45 p.m., build.starlingx at gmail.com wrote: > Project: STX_build_master_master > Build #: 16 > Status: Failure > Timestamp: 20190312T223000Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190312T223000Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS: false > BUILD_CONTAINERS_ZZZ: false > > _______________________________________________ > 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 bruce.e.jones at intel.com Wed Mar 13 16:39:00 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 13 Mar 2019 16:39:00 +0000 Subject: [Starlingx-discuss] about NVME disk as the boot disk In-Reply-To: <024ffcb7-b4b7-210f-17dc-893e2cd4ba09@linux.intel.com> References: <1778C939-9D03-4AE2-8B6D-D6C54E55AAD4@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA462970@ALA-MBD.corp.ad.wrs.com> <024ffcb7-b4b7-210f-17dc-893e2cd4ba09@linux.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BD06FE1D0@fmsmsx123.amr.corp.intel.com> Saul wrote: > While editing the kernel cmdline is a workaround for this issue, does it > also make sense to have a launchpad issue and work to fix the logic in > selecting an appropriate boot/rootfs device target. +1 this sounds like a great idea! -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Tuesday, March 12, 2019 5:24 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] about NVME disk as the boot disk On 3/12/19 6:54 AM, Penney, Don wrote: > Hi Yong, > > Please see the following reference: > > https://docs.starlingx.io/installation_guide/index.html#nvme-drive-as- > boot-drive > > Edit the kernel boot parameter. After you are presented with the > StarlingX ISO boot options and after you have selected the preferred > installation option (e.g. Standard Configuration / All-in-One > Controller Configuration), press the TAB key to edit the Kernel boot parameters. > Modify the *boot_device* and *rootfs_device* from the default *sda* so > that it is the correct device name for the NVMe drive (e.g. “nvme0n1”). > While editing the kernel cmdline is a workaround for this issue, does it also make sense to have a launchpad issue and work to fix the logic in selecting an appropriate boot/rootfs device target. There already is some logic to check for a USB device and fail out, so why not move that into the loop and have it auto detect nvme devices. Another option would be to change the ordering in pre_disk_setup_common code. Sau! > Cheers, > > Don. > > *From:*Hu, Yong [mailto:yong.hu at intel.com] > *Sent:* Tuesday, March 12, 2019 8:51 AM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] about NVME disk as the boot disk > > Hi folks, > > I was installing StarlingX in a NUC with 2 NVME disks (without other HD > or SATA disks), and the installation was ended up with an issue as follows: > > “ERROR: Specified installation (sda) or boot (sda) device is a USB drive.” > > It seemed NVME disk was not recognized as valid boot disk. > > With the help from @Saul, we found in “bsp-files/grub.cfg”, > “boot_device” and “rootfs_device” were by default set as “sda” in ks > cmdline: > > /linuxefi /vmlinuz inst.ks=hd:LABEL=oe_iso_boot:/smallsystem_ks.cfg > boot_device=sda rootfs_device=sda biosdevname=0 usbcore.autosuspend=-1 > console=tty0 inst.text inst.stage2=hd:LABEL=oe_iso_boot inst.gpt > security_profile=standard user_namespace.enable=1/ > > So, there are 2 ways to make NVME disks work as boot disk: > > 1. to change the grub cmdline, with “nvme0n1” for “rootfs_device” and > “boot_device” accordingly, during the installation. > 2. Not to set “rootfs_device” and “boot_device” in ks cmdline, and let > “bsp-files/kickstarts/pre_disk_setup_common.cfg” detect “nvme0n1” > dynamically. > > Though, I wonder if there are other better ways in such a case. > > Regards, > > Yong > > > _______________________________________________ > 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 maria.g.perez.ibarra at intel.com Wed Mar 13 17:22:49 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Wed, 13 Mar 2019 17:22:49 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190312 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Mar-12 (link) Status : RED =================== Virtual environment =================== Simplex: Setup 04 TCs [FAIL] Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 49 TCs [FAIL] Sanity-Platform 07 TCs [FAIL] TOTAL: [61 TCs FAIL] ------------------------------ Duplex: Setup 04 TCs [FAIL] Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [62 TCs FAIL] ------------------------------ Standard Local Storage (2+2): Setup 04 TCs [FAIL] Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [62 TCs FAIL] ------------------------------ Standard External Storage (2+2+2): Setup 04 TCs [FAIL] Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [62 TCs FAIL] ------------------------------ ====================== Bare Metal environment ====================== Simplex: Setup Manual Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 49 TCs [FAIL] Sanity-Platform 07 TCs [FAIL] TOTAL: [57 TCs FAIL] ------------------------------ Duplex: Setup Manual Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [58 TCs FAIL] ------------------------------ Standard Local Storage (2+2): Setup Manual Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [58 TCs FAIL] ------------------------------ Standard External Storage (2+2+2): Setup Manual Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [58 TCs FAIL] STX ISO installation FAILED Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1819941 Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Wed Mar 13 18:41:41 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 13 Mar 2019 18:41:41 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190312 In-Reply-To: References: Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4CD6EA@ALA-MBD.corp.ad.wrs.com> Hi Cindy / Shuicheng, Please have someone from your team investigate. It seems there is an issue with the installer after the merge of CentOS 7.6. Thanks, Ghada From: Perez Ibarra, Maria G [mailto:maria.g.perez.ibarra at intel.com] Sent: Wednesday, March 13, 2019 1:23 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190312 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Mar-12 (link) Status : RED =================== Virtual environment =================== Simplex: Setup 04 TCs [FAIL] Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 49 TCs [FAIL] Sanity-Platform 07 TCs [FAIL] TOTAL: [61 TCs FAIL] ------------------------------ Duplex: Setup 04 TCs [FAIL] Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [62 TCs FAIL] ------------------------------ Standard Local Storage (2+2): Setup 04 TCs [FAIL] Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [62 TCs FAIL] ------------------------------ Standard External Storage (2+2+2): Setup 04 TCs [FAIL] Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [62 TCs FAIL] ------------------------------ ====================== Bare Metal environment ====================== Simplex: Setup Manual Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 49 TCs [FAIL] Sanity-Platform 07 TCs [FAIL] TOTAL: [57 TCs FAIL] ------------------------------ Duplex: Setup Manual Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [58 TCs FAIL] ------------------------------ Standard Local Storage (2+2): Setup Manual Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [58 TCs FAIL] ------------------------------ Standard External Storage (2+2+2): Setup Manual Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [58 TCs FAIL] STX ISO installation FAILED Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1819941 Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcel at schaible-consulting.de Wed Mar 13 18:44:05 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Wed, 13 Mar 2019 19:44:05 +0100 (CET) Subject: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. Message-ID: <2130766305.1081052.1552502645093@communicator.strato.com> Hi *, when I try to create or edit a network in WebUI under "Admin->Network->Networks->Edit Network" I am getting the error: Danger: An error occurred. Please try again later. Any idea of the root cause of this issue? Thanks Marcel From elio.martinez.monroy at intel.com Wed Mar 13 18:55:14 2019 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Wed, 13 Mar 2019 18:55:14 +0000 Subject: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. In-Reply-To: <2130766305.1081052.1552502645093@communicator.strato.com> References: <2130766305.1081052.1552502645093@communicator.strato.com> Message-ID: <1466AF2176E6F040BD63860D0A241BBD46CA0171@FMSMSX109.amr.corp.intel.com> Do you have the same problem using CLI? Could you specify which image are you using? BR Elio -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Wednesday, March 13, 2019 12:44 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. Hi *, when I try to create or edit a network in WebUI under "Admin->Network->Networks->Edit Network" I am getting the error: Danger: An error occurred. Please try again later. Any idea of the root cause of this issue? Thanks Marcel _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From marcel at schaible-consulting.de Wed Mar 13 19:14:11 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Wed, 13 Mar 2019 20:14:11 +0100 Subject: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. In-Reply-To: <1466AF2176E6F040BD63860D0A241BBD46CA0171@FMSMSX109.amr.corp.intel.com> References: <2130766305.1081052.1552502645093@communicator.strato.com> <1466AF2176E6F040BD63860D0A241BBD46CA0171@FMSMSX109.amr.corp.intel.com> Message-ID: Nope, cli is working. The image is from 20190229. Von meinem iPhone gesendet > Am 13.03.2019 um 19:55 schrieb Martinez Monroy, Elio : > > Do you have the same problem using CLI? > Could you specify which image are you using? > > BR > > Elio > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Wednesday, March 13, 2019 12:44 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. > > Hi *, > > when I try to create or edit a network in WebUI under "Admin->Network->Networks->Edit Network" I am getting the error: > > Danger: An error occurred. Please try again later. > > Any idea of the root cause of this issue? > > > Thanks > > Marcel > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From elio.martinez.monroy at intel.com Wed Mar 13 19:28:11 2019 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Wed, 13 Mar 2019 19:28:11 +0000 Subject: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. In-Reply-To: References: <2130766305.1081052.1552502645093@communicator.strato.com> <1466AF2176E6F040BD63860D0A241BBD46CA0171@FMSMSX109.amr.corp.intel.com> Message-ID: <1466AF2176E6F040BD63860D0A241BBD46CA0358@FMSMSX109.amr.corp.intel.com> So, I think this is a Horizon GUI issue that we need to investigate further, could you help us submitting the defect? In that way we can start debugging and posting comments and findings. Every log can help us. Thanks -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Wednesday, March 13, 2019 1:14 PM To: Martinez Monroy, Elio Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. Nope, cli is working. The image is from 20190229. Von meinem iPhone gesendet > Am 13.03.2019 um 19:55 schrieb Martinez Monroy, Elio : > > Do you have the same problem using CLI? > Could you specify which image are you using? > > BR > > Elio > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Wednesday, March 13, 2019 12:44 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. > > Hi *, > > when I try to create or edit a network in WebUI under "Admin->Network->Networks->Edit Network" I am getting the error: > > Danger: An error occurred. Please try again later. > > Any idea of the root cause of this issue? > > > Thanks > > Marcel > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From marcel at schaible-consulting.de Wed Mar 13 19:29:58 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Wed, 13 Mar 2019 20:29:58 +0100 Subject: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. In-Reply-To: <1466AF2176E6F040BD63860D0A241BBD46CA0358@FMSMSX109.amr.corp.intel.com> References: <2130766305.1081052.1552502645093@communicator.strato.com> <1466AF2176E6F040BD63860D0A241BBD46CA0171@FMSMSX109.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD46CA0358@FMSMSX109.amr.corp.intel.com> Message-ID: <96468830-F551-4802-82A8-FA131089987D@schaible-consulting.de> Sure. Which logs do you need? Since it quite late here I can send them tomorrow. Kind regards Marcel > Am 13.03.2019 um 20:28 schrieb Martinez Monroy, Elio : > > So, I think this is a Horizon GUI issue that we need to investigate further, could you help us submitting the defect? In that way we can start debugging and posting comments and findings. Every log can help us. > > Thanks > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Wednesday, March 13, 2019 1:14 PM > To: Martinez Monroy, Elio > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. > > Nope, cli is working. The image is from 20190229. > > Von meinem iPhone gesendet > >> Am 13.03.2019 um 19:55 schrieb Martinez Monroy, Elio : >> >> Do you have the same problem using CLI? >> Could you specify which image are you using? >> >> BR >> >> Elio >> >> -----Original Message----- >> From: Marcel Schaible [mailto:marcel at schaible-consulting.de] >> Sent: Wednesday, March 13, 2019 12:44 PM >> To: starlingx-discuss at lists.starlingx.io >> Subject: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. >> >> Hi *, >> >> when I try to create or edit a network in WebUI under "Admin->Network->Networks->Edit Network" I am getting the error: >> >> Danger: An error occurred. Please try again later. >> >> Any idea of the root cause of this issue? >> >> >> Thanks >> >> Marcel >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From elio.martinez.monroy at intel.com Wed Mar 13 19:32:42 2019 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Wed, 13 Mar 2019 19:32:42 +0000 Subject: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. In-Reply-To: <96468830-F551-4802-82A8-FA131089987D@schaible-consulting.de> References: <2130766305.1081052.1552502645093@communicator.strato.com> <1466AF2176E6F040BD63860D0A241BBD46CA0171@FMSMSX109.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD46CA0358@FMSMSX109.amr.corp.intel.com> <96468830-F551-4802-82A8-FA131089987D@schaible-consulting.de> Message-ID: <1466AF2176E6F040BD63860D0A241BBD46CA0374@FMSMSX109.amr.corp.intel.com> I think we should start from the beginning. What about /var/log/horizon/gunicorn.log? BR Elio -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Wednesday, March 13, 2019 1:30 PM To: Martinez Monroy, Elio Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. Sure. Which logs do you need? Since it quite late here I can send them tomorrow. Kind regards Marcel > Am 13.03.2019 um 20:28 schrieb Martinez Monroy, Elio : > > So, I think this is a Horizon GUI issue that we need to investigate further, could you help us submitting the defect? In that way we can start debugging and posting comments and findings. Every log can help us. > > Thanks > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Wednesday, March 13, 2019 1:14 PM > To: Martinez Monroy, Elio > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. > > Nope, cli is working. The image is from 20190229. > > Von meinem iPhone gesendet > >> Am 13.03.2019 um 19:55 schrieb Martinez Monroy, Elio : >> >> Do you have the same problem using CLI? >> Could you specify which image are you using? >> >> BR >> >> Elio >> >> -----Original Message----- >> From: Marcel Schaible [mailto:marcel at schaible-consulting.de] >> Sent: Wednesday, March 13, 2019 12:44 PM >> To: starlingx-discuss at lists.starlingx.io >> Subject: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. >> >> Hi *, >> >> when I try to create or edit a network in WebUI under "Admin->Network->Networks->Edit Network" I am getting the error: >> >> Danger: An error occurred. Please try again later. >> >> Any idea of the root cause of this issue? >> >> >> Thanks >> >> Marcel >> >> _______________________________________________ >> 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 juan.carlos.alonso at intel.com Wed Mar 13 19:46:33 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Wed, 13 Mar 2019 19:46:33 +0000 Subject: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. In-Reply-To: <1466AF2176E6F040BD63860D0A241BBD46CA0374@FMSMSX109.amr.corp.intel.com> References: <2130766305.1081052.1552502645093@communicator.strato.com> <1466AF2176E6F040BD63860D0A241BBD46CA0171@FMSMSX109.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD46CA0358@FMSMSX109.amr.corp.intel.com> <96468830-F551-4802-82A8-FA131089987D@schaible-consulting.de> <1466AF2176E6F040BD63860D0A241BBD46CA0374@FMSMSX109.amr.corp.intel.com> Message-ID: <8557B550001AFB46A43A0CCC314BF85153CAB14A@FMSMSX108.amr.corp.intel.com> Hi, Or you can try with a recent image. I suggest to try with 20190305, it was the latest with Green status. Regards. Juan Carlos Alonso -----Original Message----- From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Wednesday, March 13, 2019 1:33 PM To: Marcel Schaible Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. I think we should start from the beginning. What about /var/log/horizon/gunicorn.log? BR Elio -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Wednesday, March 13, 2019 1:30 PM To: Martinez Monroy, Elio Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. Sure. Which logs do you need? Since it quite late here I can send them tomorrow. Kind regards Marcel > Am 13.03.2019 um 20:28 schrieb Martinez Monroy, Elio : > > So, I think this is a Horizon GUI issue that we need to investigate further, could you help us submitting the defect? In that way we can start debugging and posting comments and findings. Every log can help us. > > Thanks > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Wednesday, March 13, 2019 1:14 PM > To: Martinez Monroy, Elio > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. > > Nope, cli is working. The image is from 20190229. > > Von meinem iPhone gesendet > >> Am 13.03.2019 um 19:55 schrieb Martinez Monroy, Elio : >> >> Do you have the same problem using CLI? >> Could you specify which image are you using? >> >> BR >> >> Elio >> >> -----Original Message----- >> From: Marcel Schaible [mailto:marcel at schaible-consulting.de] >> Sent: Wednesday, March 13, 2019 12:44 PM >> To: starlingx-discuss at lists.starlingx.io >> Subject: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. >> >> Hi *, >> >> when I try to create or edit a network in WebUI under "Admin->Network->Networks->Edit Network" I am getting the error: >> >> Danger: An error occurred. Please try again later. >> >> Any idea of the root cause of this issue? >> >> >> Thanks >> >> Marcel >> >> _______________________________________________ >> 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 Ghada.Khalil at windriver.com Wed Mar 13 19:51:25 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 13 Mar 2019 19:51:25 +0000 Subject: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. In-Reply-To: <8557B550001AFB46A43A0CCC314BF85153CAB14A@FMSMSX108.amr.corp.intel.com> References: <2130766305.1081052.1552502645093@communicator.strato.com> <1466AF2176E6F040BD63860D0A241BBD46CA0171@FMSMSX109.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD46CA0358@FMSMSX109.amr.corp.intel.com> <96468830-F551-4802-82A8-FA131089987D@schaible-consulting.de> <1466AF2176E6F040BD63860D0A241BBD46CA0374@FMSMSX109.amr.corp.intel.com> <8557B550001AFB46A43A0CCC314BF85153CAB14A@FMSMSX108.amr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4CD75A@ALA-MBD.corp.ad.wrs.com> There is an issue with creating networks from horizon on older loads: https://bugs.launchpad.net/starlingx/+bug/1804863 This is addressed in newer loads (March 1st and later) as part of the containerized env cutover. -----Original Message----- From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Wednesday, March 13, 2019 3:47 PM To: Martinez Monroy, Elio; Marcel Schaible Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. Hi, Or you can try with a recent image. I suggest to try with 20190305, it was the latest with Green status. Regards. Juan Carlos Alonso -----Original Message----- From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Wednesday, March 13, 2019 1:33 PM To: Marcel Schaible Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. I think we should start from the beginning. What about /var/log/horizon/gunicorn.log? BR Elio -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Wednesday, March 13, 2019 1:30 PM To: Martinez Monroy, Elio Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. Sure. Which logs do you need? Since it quite late here I can send them tomorrow. Kind regards Marcel > Am 13.03.2019 um 20:28 schrieb Martinez Monroy, Elio : > > So, I think this is a Horizon GUI issue that we need to investigate further, could you help us submitting the defect? In that way we can start debugging and posting comments and findings. Every log can help us. > > Thanks > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Wednesday, March 13, 2019 1:14 PM > To: Martinez Monroy, Elio > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. > > Nope, cli is working. The image is from 20190229. > > Von meinem iPhone gesendet > >> Am 13.03.2019 um 19:55 schrieb Martinez Monroy, Elio : >> >> Do you have the same problem using CLI? >> Could you specify which image are you using? >> >> BR >> >> Elio >> >> -----Original Message----- >> From: Marcel Schaible [mailto:marcel at schaible-consulting.de] >> Sent: Wednesday, March 13, 2019 12:44 PM >> To: starlingx-discuss at lists.starlingx.io >> Subject: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. >> >> Hi *, >> >> when I try to create or edit a network in WebUI under "Admin->Network->Networks->Edit Network" I am getting the error: >> >> Danger: An error occurred. Please try again later. >> >> Any idea of the root cause of this issue? >> >> >> Thanks >> >> Marcel >> >> _______________________________________________ >> 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 michael.l.tullis at intel.com Wed Mar 13 20:28:03 2019 From: michael.l.tullis at intel.com (Tullis, Michael L) Date: Wed, 13 Mar 2019 20:28:03 +0000 Subject: [Starlingx-discuss] [docs][meetings] docs team meeting minutes 3/13/2019 Message-ID: <3808363B39586544A6839C76CF81445EA1AD417F@ORSMSX104.amr.corp.intel.com> For notes and new action items from our docs team meeting today, see our etherpad: https://etherpad.openstack.org/p/stx-documentation Join us if you have interest in StarlingX docs! We meet Wednesdays, and call logistics are here: https://wiki.openstack.org/wiki/Starlingx/Meetings. -- Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ken.Young at windriver.com Wed Mar 13 20:40:58 2019 From: Ken.Young at windriver.com (Young, Ken) Date: Wed, 13 Mar 2019 20:40:58 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190312 In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA4CD6EA@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA4CD6EA@ALA-MBD.corp.ad.wrs.com> Message-ID: Team, This is an issue with the installer build on CENGN. I am assigning to Scott for triage and fix. /KenY From: "Khalil, Ghada" Date: Wednesday, March 13, 2019 at 2:44 PM To: "Perez Ibarra, Maria G" , "starlingx-discuss at lists.starlingx.io" , XIAO XIE , Shuicheng Lin Subject: Re: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190312 Hi Cindy / Shuicheng, Please have someone from your team investigate. It seems there is an issue with the installer after the merge of CentOS 7.6. Thanks, Ghada From: Perez Ibarra, Maria G [mailto:maria.g.perez.ibarra at intel.com] Sent: Wednesday, March 13, 2019 1:23 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190312 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Mar-12 (link) Status : RED =================== Virtual environment =================== Simplex: Setup 04 TCs [FAIL] Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 49 TCs [FAIL] Sanity-Platform 07 TCs [FAIL] TOTAL: [61 TCs FAIL] ------------------------------ Duplex: Setup 04 TCs [FAIL] Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [62 TCs FAIL] ------------------------------ Standard Local Storage (2+2): Setup 04 TCs [FAIL] Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [62 TCs FAIL] ------------------------------ Standard External Storage (2+2+2): Setup 04 TCs [FAIL] Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [62 TCs FAIL] ------------------------------ ====================== Bare Metal environment ====================== Simplex: Setup Manual Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 49 TCs [FAIL] Sanity-Platform 07 TCs [FAIL] TOTAL: [57 TCs FAIL] ------------------------------ Duplex: Setup Manual Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [58 TCs FAIL] ------------------------------ Standard Local Storage (2+2): Setup Manual Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [58 TCs FAIL] ------------------------------ Standard External Storage (2+2+2): Setup Manual Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [58 TCs FAIL] STX ISO installation FAILED Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1819941 Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ada.cabrales at intel.com Wed Mar 13 21:01:07 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Wed, 13 Mar 2019 21:01:07 +0000 Subject: [Starlingx-discuss] Test Case Submission in rst format In-Reply-To: References: <3CAA827B7A79BA46B15B280EC82088FE4828CE36@ALA-MBD.corp.ad.wrs.com> Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CDAADC1@FMSMSX114.amr.corp.intel.com> Well, based on the amount of work that rst formatting is requiring, and being as close as we are to the release testing, I support the submission of manual test cases (to our repo) using txt format. We can continue the effort of translating those into rst in the following months, so we can align to the project documentation standards. Please raise the concerns you might have regarding this topic Ada > -----Original Message----- > From: Arce Moreno, Abraham > Sent: Friday, March 8, 2019 3:45 PM > To: Waheed, Numan ; Cabrales, Ada > ; starlingx-discuss at lists.starlingx.io > Subject: RE: Test Case Submission in rst format > > Hi Numan, > > > We are currently in process of submitting our test cases in stx-test > > git repository. There has been a request to upload manual tests is rst > > format so that they can be visible on a wiki. > > Thanks to you and all test team for all the support to take advantage of existing > documentation infrastructure and give it a try to have it under our official > documentation channel at starlingx.io > > > Conversion of test cases from plain text format to rst format is > > causing a lot of pain and time lost. At the same time it is also not > > an absolute requirement as any tester who wants to execute these test > > cases can easily access them from git in text format. > > We understand this is a time consuming process considering the number of test > cases you have and the ramp up in the learning of the RST format if automated > tools are not used. Agree that the format is not relevant to execute a test case. > > > I am not sure about how much time is spent by Ada's team in converting > > these test cases but I would suggest that we should submit them in > > plain text format and if documentation team wants to convert them in > > rst then they can update them. > > Let's add this option to the table. At the end, you as a team has the final decision > and decide what is the best approach that works for you, here you have the > existing > options: > > [ Option A ] Convert all test cases to RST format and merge. > [ Option B ] Keep all test cases in X format and merge. > [ Option C ] Only merge what has been converted to RST format. > > There is no right option, again, it all depends on the needs and priorities of the > team, your call. > > > Secondly, if these test cases are to be shown in Wiki, what is your > > plan for showing them in next release? > > The test cases could land (one commit away to make this happen) under our > official StarlingX documentation site at: https://docs.starlingx.io/ > > Our proposal is to add "Test" down to "Tools", under "There are several > supporting projects and repositories": > > - Tools < pointing to https://docs.starlingx.io/stx-tools/index.html > - Test < pointing to https://docs.starlingx.io/stx-test/index.html > > This way we are taking full advantage of the StarlingX documentation > infrastructure based in OpenStack guidelines and giving a standard and formal > way to present it to the community. > > > Would there be a release specific Wiki or a selection available to > > check test cases for each release? > > We can discuss what are your needs in terms of versioning in our weekly > meeting. > As an example, we are currently working to split the installation documentation > in 2 versions based in "directories": > > 1. Version one: old way to deploy StarlingX 2. Version two: new containerized > way to deploy StarlingX > > More information about this "versioning" task under our meeting minutes here: > https://etherpad.openstack.org/p/stx-documentation > > Please let us know any other question you might have. More than happy to > support your team objectives. From scott.little at windriver.com Wed Mar 13 21:11:14 2019 From: scott.little at windriver.com (Scott Little) Date: Wed, 13 Mar 2019 17:11:14 -0400 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190312 In-Reply-To: References: <151EE31B9FCCA54397A757BC674650F0BA4CD6EA@ALA-MBD.corp.ad.wrs.com> Message-ID: <66534bce-f927-4d9d-869e-f6b8e6845224@windriver.com> Launchpad: https://bugs.launchpad.net/starlingx/+bug/1819941 I've started a new CENGN build after deleting the contents of ... .../stx-tools/centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/EFI .../stx-tools/centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/images .../stx-tools/centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/isolinux .../stx-tools/centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/LiveOS This should trigger a redownload of the squashfs.img, and should yield a 7.6 compatible installer. ETA ~ 8pm EST Scott On 2019-03-13 4:40 p.m., Young, Ken wrote: > > Team, > > This is an issue with the installer build on CENGN.  I am assigning to > Scott for triage and fix. > > /KenY > > *From: *"Khalil, Ghada" > *Date: *Wednesday, March 13, 2019 at 2:44 PM > *To: *"Perez Ibarra, Maria G" , > "starlingx-discuss at lists.starlingx.io" > , XIAO XIE > , Shuicheng Lin > *Subject: *Re: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190312 > > Hi Cindy / Shuicheng, > > Please have someone from your team investigate. It seems there is an > issue with the installer after the merge of CentOS 7.6. > > Thanks, > > Ghada > > *From:* Perez Ibarra, Maria G [mailto:maria.g.perez.ibarra at intel.com] > *Sent:* Wednesday, March 13, 2019 1:23 PM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] [Containers] Sanity Test - ISO 20190312 > > *Status of the Sanity Test for last CENGN ISO: */bootimage.iso from > 2019-Mar-12 /(link > ) > > > Status : RED > > =================== > > Virtual environment > > =================== > > Simplex: > > Setup                 04 TCs [FAIL] > > Provision-Containers  01 TCs [FAIL] > > Sanity-OpenStack      49 TCs [FAIL] > > Sanity-Platform       07 TCs [FAIL] > > TOTAL:                [61 TCs FAIL] > > ------------------------------ > > Duplex: > > Setup                 04 TCs [FAIL] > > Provision-Containers  01 TCs [FAIL] > > Sanity-OpenStack      52 TCs [FAIL] > > Sanity-Platform       05 TCs [FAIL] > > TOTAL:                [62 TCs FAIL] > > ------------------------------ > > Standard Local Storage (2+2): > > Setup                 04 TCs [FAIL] > > Provision-Containers  01 TCs [FAIL] > > Sanity-OpenStack      52 TCs [FAIL] > > Sanity-Platform       05 TCs [FAIL] > > TOTAL:                [62 TCs FAIL] > > ------------------------------ > > Standard External Storage (2+2+2): > > Setup                 04 TCs [FAIL] > > Provision-Containers  01 TCs [FAIL] > > Sanity-OpenStack      52 TCs [FAIL] > > Sanity-Platform       05 TCs [FAIL] > > TOTAL:                [62 TCs FAIL] > > ------------------------------ > > ====================== > > Bare Metal environment > > ====================== > > Simplex: > > Setup                 Manual > > Provision-Containers  01 TCs [FAIL] > > Sanity-OpenStack      49 TCs [FAIL] > > Sanity-Platform       07 TCs [FAIL] > > TOTAL:                [57 TCs FAIL] > > ------------------------------ > > Duplex: > > Setup                 Manual > > Provision-Containers  01 TCs [FAIL] > > Sanity-OpenStack      52 TCs [FAIL] > > Sanity-Platform       05 TCs [FAIL] > > TOTAL:                [58 TCs FAIL] > > ------------------------------ > > Standard Local Storage (2+2): > > Setup                 Manual > > Provision-Containers  01 TCs [FAIL] > > Sanity-OpenStack      52 TCs [FAIL] > > Sanity-Platform       05 TCs [FAIL] > > TOTAL:                [58 TCs FAIL] > > ------------------------------ > > Standard External Storage (2+2+2): > > Setup                 Manual > > Provision-Containers  01 TCs [FAIL] > > Sanity-OpenStack      52 TCs [FAIL] > > Sanity-Platform       05 TCs [FAIL] > > TOTAL:                [58 TCs FAIL] > > STX ISO installation FAILED > > Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1819941 > > Regards > > Maria G. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Numan.Waheed at windriver.com Wed Mar 13 21:18:15 2019 From: Numan.Waheed at windriver.com (Waheed, Numan) Date: Wed, 13 Mar 2019 21:18:15 +0000 Subject: [Starlingx-discuss] Test Case Submission in rst format In-Reply-To: <4F6AACE4B0F173488D033B02A8BB5B7E7CDAADC1@FMSMSX114.amr.corp.intel.com> References: <3CAA827B7A79BA46B15B280EC82088FE4828CE36@ALA-MBD.corp.ad.wrs.com> <4F6AACE4B0F173488D033B02A8BB5B7E7CDAADC1@FMSMSX114.amr.corp.intel.com> Message-ID: <3CAA827B7A79BA46B15B280EC82088FE4828F0E3@ALA-MBD.corp.ad.wrs.com> Hi Ada, We discussed this topic in stx-test call and Abraham was fine with us submitting our test plans in txt format. Thanks, Numan. -----Original Message----- From: Cabrales, Ada Sent: March-13-19 5:01 PM To: Arce Moreno, Abraham ; Waheed, Numan ; starlingx-discuss at lists.starlingx.io Subject: RE: Test Case Submission in rst format Well, based on the amount of work that rst formatting is requiring, and being as close as we are to the release testing, I support the submission of manual test cases (to our repo) using txt format. We can continue the effort of translating those into rst in the following months, so we can align to the project documentation standards. Please raise the concerns you might have regarding this topic Ada > -----Original Message----- > From: Arce Moreno, Abraham > Sent: Friday, March 8, 2019 3:45 PM > To: Waheed, Numan ; Cabrales, Ada > ; starlingx-discuss at lists.starlingx.io > Subject: RE: Test Case Submission in rst format > > Hi Numan, > > > We are currently in process of submitting our test cases in stx-test > > git repository. There has been a request to upload manual tests is > > rst format so that they can be visible on a wiki. > > Thanks to you and all test team for all the support to take advantage > of existing documentation infrastructure and give it a try to have it > under our official documentation channel at starlingx.io > > > Conversion of test cases from plain text format to rst format is > > causing a lot of pain and time lost. At the same time it is also not > > an absolute requirement as any tester who wants to execute these > > test cases can easily access them from git in text format. > > We understand this is a time consuming process considering the number > of test cases you have and the ramp up in the learning of the RST > format if automated tools are not used. Agree that the format is not relevant to execute a test case. > > > I am not sure about how much time is spent by Ada's team in > > converting these test cases but I would suggest that we should > > submit them in plain text format and if documentation team wants to > > convert them in rst then they can update them. > > Let's add this option to the table. At the end, you as a team has the > final decision and decide what is the best approach that works for > you, here you have the existing > options: > > [ Option A ] Convert all test cases to RST format and merge. > [ Option B ] Keep all test cases in X format and merge. > [ Option C ] Only merge what has been converted to RST format. > > There is no right option, again, it all depends on the needs and > priorities of the team, your call. > > > Secondly, if these test cases are to be shown in Wiki, what is your > > plan for showing them in next release? > > The test cases could land (one commit away to make this happen) under > our official StarlingX documentation site at: > https://docs.starlingx.io/ > > Our proposal is to add "Test" down to "Tools", under "There are > several supporting projects and repositories": > > - Tools < pointing to https://docs.starlingx.io/stx-tools/index.html > - Test < pointing to https://docs.starlingx.io/stx-test/index.html > > This way we are taking full advantage of the StarlingX documentation > infrastructure based in OpenStack guidelines and giving a standard and > formal way to present it to the community. > > > Would there be a release specific Wiki or a selection available to > > check test cases for each release? > > We can discuss what are your needs in terms of versioning in our > weekly meeting. > As an example, we are currently working to split the installation > documentation in 2 versions based in "directories": > > 1. Version one: old way to deploy StarlingX 2. Version two: new > containerized way to deploy StarlingX > > More information about this "versioning" task under our meeting minutes here: > https://etherpad.openstack.org/p/stx-documentation > > Please let us know any other question you might have. More than happy > to support your team objectives. From mario.alfredo.c.arevalo at intel.com Wed Mar 13 21:52:12 2019 From: mario.alfredo.c.arevalo at intel.com (Arevalo, Mario Alfredo C) Date: Wed, 13 Mar 2019 21:52:12 +0000 Subject: [Starlingx-discuss] Questions related to FM containerization Message-ID: <6594B51DBE477C48AAE23675314E6C46645994B3@fmsmsx107.amr.corp.intel.com> Hi Brent and team, This mail plans to interchange information in order to get more granularity about the "Fault Manager" Containerization process where the final objective is to deploy a pod or pods which make completely match with the design of containerization architecture. According from the feedback received yesterday in our meeting and taking a look to the source code and the processes which are running in a deployed environment I can understand the possible missing parts. This is my understanding about the full picture and some questions about it, please let me know if something is wrong or deviates from the original objective/result. The storyboard [1] related to FM chart will be finished when the FM restful API and the FM manager main services are containerized and work correctly with the rest of the StarlingX components: - I think the best approach is to run a container per service and both containers should live in the same pod. - Both services should consume the same Docker image in order to reduce the memory foot print. - According the previous shared information and my code exploring I understand the FM manager (fmManager binary) is a service which listens in the port 8001 and executes requests. It is launched by an script called "fminit". At this point I have a pair of questions, is this the service which the storyboard [1] makes reference of, intended to have an instance in bare metal and another one exposed by a container? If the last questions is yes, we will have 2 instances of the same service then they should be exposed in a different port, and how about fm rest api service, it will just exist in a container? FM manager service has interaction with a PostgreSQL data base, then I wonder how this will be handled. Does this containerized service point to the bare metal database? Should we add a new chart which exposes a PostgreSQL due to the current chart tarball or just include one for MariaDB. Then the task 28876 makes reference to modify nfv_vim[2] in order to get the alarms information from the container? - Surfing in a deployed image I saw that is possible to remove alarms from the web interface provided by horizon, then the task 28878 makes reference to points to the FM manager containerized service from horizon, however it is not clear for me the task 28877 described in the chart storyboard[1]. These are some points and questions which will give a better understanding for the rest of tasks, however, possibly, I will get more questions during this process I will be in contact with all of you. Thank you for your help. Best Regards. Mario. References: [1] https://storyboard.openstack.org/#!/story/2004008 [2] https://git.starlingx.io/cgit/stx-nfv/tree/nfv/nfv-vim/nfv_vim From cesar.lara at intel.com Wed Mar 13 23:14:10 2019 From: cesar.lara at intel.com (Lara, Cesar) Date: Wed, 13 Mar 2019 23:14:10 +0000 Subject: [Starlingx-discuss] [build][meetings] Build team meeting minutes 3/7/2019 Message-ID: <0B566C62EC792145B40E29EFEBF1AB47106177FF@fmsmsx104.amr.corp.intel.com> Build team meeting Agenda for 3/7/2019 - Cengn build update - Ubuntu Build update - Build separation - Opens Notes Cengn build update Build experiencing a few errors due to 404 for certain files when try to download on mirror, Scott has a proposed patch, please advise. Cengn build scripts have been uploaded to git repository on stx-staging/Jenkins. Still working on the mirror infrastructure for be moved to K8 backend. Ubuntu Build update Build for Ubuntu POC was successful, the goal is to try to integrate to Ubuntu, a modified kernel with StarlingX patches, a few bare metal components and the bits necessary to bring stx-faul online, so far, we have built an Ubuntu image with the kernel and the stx-fault plus their dependencies packaged in a .deb file. Build separation we are evaluating proposals on the implementation for a separated build based on layers having on one side the OS/distro build, which we are targeting that we build once and hardly ever touch it (so we don't have to build it all the time) just when a change is introduced to the OS and host that separated from the other layers for consumption , and, the Containers and Flock services layers, containing separate bits that are built regularly and also stored separate for consumption. This proposal is being evaluated as well as another proposal from Scott which we are waiting to hear about. Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From cesar.lara at intel.com Wed Mar 13 23:16:47 2019 From: cesar.lara at intel.com (Lara, Cesar) Date: Wed, 13 Mar 2019 23:16:47 +0000 Subject: [Starlingx-discuss] [build][meeting] Build team meeting Agenda for 3/14/2019 Message-ID: <0B566C62EC792145B40E29EFEBF1AB4710617839@fmsmsx104.amr.corp.intel.com> Build team meeting Agenda for 3/14/2019 - Cengn build update - Help needed - Opens Abraham to cover for Cesar chairing this meeting Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Thu Mar 14 00:23:05 2019 From: scott.little at windriver.com (Scott Little) Date: Wed, 13 Mar 2019 20:23:05 -0400 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190312 In-Reply-To: <66534bce-f927-4d9d-869e-f6b8e6845224@windriver.com> References: <151EE31B9FCCA54397A757BC674650F0BA4CD6EA@ALA-MBD.corp.ad.wrs.com> <66534bce-f927-4d9d-869e-f6b8e6845224@windriver.com> Message-ID: <7f49bcb7-1483-dff1-7601-c04f60f8bbf4@windriver.com> Build complete.  Mounted the iso and it does look like a 7.6 installer this time. This one is ready for test. The regular 8:30 EST will start shortly. Scott On 2019-03-13 5:11 p.m., Scott Little wrote: > Launchpad: https://bugs.launchpad.net/starlingx/+bug/1819941 > > I've started a new CENGN build after deleting the contents of ... > .../stx-tools/centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/EFI > .../stx-tools/centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/images > .../stx-tools/centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/isolinux > .../stx-tools/centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/LiveOS > > This should trigger a redownload of the squashfs.img, and should yield > a 7.6 compatible installer. > > ETA ~ 8pm EST > > Scott > > > On 2019-03-13 4:40 p.m., Young, Ken wrote: >> >> Team, >> >> This is an issue with the installer build on CENGN.  I am assigning >> to Scott for triage and fix. >> >> /KenY >> >> *From: *"Khalil, Ghada" >> *Date: *Wednesday, March 13, 2019 at 2:44 PM >> *To: *"Perez Ibarra, Maria G" , >> "starlingx-discuss at lists.starlingx.io" >> , XIAO XIE >> , Shuicheng Lin >> *Subject: *Re: [Starlingx-discuss] [Containers] Sanity Test - ISO >> 20190312 >> >> Hi Cindy / Shuicheng, >> >> Please have someone from your team investigate. It seems there is an >> issue with the installer after the merge of CentOS 7.6. >> >> Thanks, >> >> Ghada >> >> *From:* Perez Ibarra, Maria G [mailto:maria.g.perez.ibarra at intel.com] >> *Sent:* Wednesday, March 13, 2019 1:23 PM >> *To:* starlingx-discuss at lists.starlingx.io >> *Subject:* [Starlingx-discuss] [Containers] Sanity Test - ISO 20190312 >> >> *Status of the Sanity Test for last CENGN ISO: */bootimage.iso from >> 2019-Mar-12 /(link >> ) >> >> >> Status : RED >> >> =================== >> >> Virtual environment >> >> =================== >> >> Simplex: >> >> Setup                 04 TCs [FAIL] >> >> Provision-Containers  01 TCs [FAIL] >> >> Sanity-OpenStack      49 TCs [FAIL] >> >> Sanity-Platform       07 TCs [FAIL] >> >> TOTAL:                [61 TCs FAIL] >> >> ------------------------------ >> >> Duplex: >> >> Setup                 04 TCs [FAIL] >> >> Provision-Containers  01 TCs [FAIL] >> >> Sanity-OpenStack      52 TCs [FAIL] >> >> Sanity-Platform       05 TCs [FAIL] >> >> TOTAL:                [62 TCs FAIL] >> >> ------------------------------ >> >> Standard Local Storage (2+2): >> >> Setup                 04 TCs [FAIL] >> >> Provision-Containers  01 TCs [FAIL] >> >> Sanity-OpenStack      52 TCs [FAIL] >> >> Sanity-Platform       05 TCs [FAIL] >> >> TOTAL:                [62 TCs FAIL] >> >> ------------------------------ >> >> Standard External Storage (2+2+2): >> >> Setup                 04 TCs [FAIL] >> >> Provision-Containers  01 TCs [FAIL] >> >> Sanity-OpenStack      52 TCs [FAIL] >> >> Sanity-Platform       05 TCs [FAIL] >> >> TOTAL:                [62 TCs FAIL] >> >> ------------------------------ >> >> ====================== >> >> Bare Metal environment >> >> ====================== >> >> Simplex: >> >> Setup                 Manual >> >> Provision-Containers  01 TCs [FAIL] >> >> Sanity-OpenStack      49 TCs [FAIL] >> >> Sanity-Platform       07 TCs [FAIL] >> >> TOTAL:                [57 TCs FAIL] >> >> ------------------------------ >> >> Duplex: >> >> Setup                 Manual >> >> Provision-Containers  01 TCs [FAIL] >> >> Sanity-OpenStack      52 TCs [FAIL] >> >> Sanity-Platform       05 TCs [FAIL] >> >> TOTAL:                [58 TCs FAIL] >> >> ------------------------------ >> >> Standard Local Storage (2+2): >> >> Setup                 Manual >> >> Provision-Containers  01 TCs [FAIL] >> >> Sanity-OpenStack      52 TCs [FAIL] >> >> Sanity-Platform       05 TCs [FAIL] >> >> TOTAL:                [58 TCs FAIL] >> >> ------------------------------ >> >> Standard External Storage (2+2+2): >> >> Setup                 Manual >> >> Provision-Containers  01 TCs [FAIL] >> >> Sanity-OpenStack      52 TCs [FAIL] >> >> Sanity-Platform       05 TCs [FAIL] >> >> TOTAL:                [58 TCs FAIL] >> >> STX ISO installation FAILED >> >> Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1819941 >> >> Regards >> >> Maria G. >> > > > _______________________________________________ > 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 cindy.xie at intel.com Thu Mar 14 00:38:29 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Thu, 14 Mar 2019 00:38:29 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190312 In-Reply-To: <7f49bcb7-1483-dff1-7601-c04f60f8bbf4@windriver.com> References: <151EE31B9FCCA54397A757BC674650F0BA4CD6EA@ALA-MBD.corp.ad.wrs.com> <66534bce-f927-4d9d-869e-f6b8e6845224@windriver.com> <7f49bcb7-1483-dff1-7601-c04f60f8bbf4@windriver.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35EC971A@SHSMSX104.ccr.corp.intel.com> Thanks Scott for the quick fix! Just wondering if we need an intelligent kernel change discovery mechanism so that the installer will be automatically re-built… Thx. - cindy From: Scott Little [mailto:scott.little at windriver.com] Sent: Thursday, March 14, 2019 8:23 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190312 Build complete. Mounted the iso and it does look like a 7.6 installer this time. This one is ready for test. The regular 8:30 EST will start shortly. Scott On 2019-03-13 5:11 p.m., Scott Little wrote: Launchpad: https://bugs.launchpad.net/starlingx/+bug/1819941 I've started a new CENGN build after deleting the contents of ... .../stx-tools/centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/EFI .../stx-tools/centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/images .../stx-tools/centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/isolinux .../stx-tools/centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/LiveOS This should trigger a redownload of the squashfs.img, and should yield a 7.6 compatible installer. ETA ~ 8pm EST Scott On 2019-03-13 4:40 p.m., Young, Ken wrote: Team, This is an issue with the installer build on CENGN. I am assigning to Scott for triage and fix. /KenY From: "Khalil, Ghada" Date: Wednesday, March 13, 2019 at 2:44 PM To: "Perez Ibarra, Maria G" , "starlingx-discuss at lists.starlingx.io" , XIAO XIE , Shuicheng Lin Subject: Re: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190312 Hi Cindy / Shuicheng, Please have someone from your team investigate. It seems there is an issue with the installer after the merge of CentOS 7.6. Thanks, Ghada From: Perez Ibarra, Maria G [mailto:maria.g.perez.ibarra at intel.com] Sent: Wednesday, March 13, 2019 1:23 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190312 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Mar-12 (link) Status : RED =================== Virtual environment =================== Simplex: Setup 04 TCs [FAIL] Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 49 TCs [FAIL] Sanity-Platform 07 TCs [FAIL] TOTAL: [61 TCs FAIL] ------------------------------ Duplex: Setup 04 TCs [FAIL] Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [62 TCs FAIL] ------------------------------ Standard Local Storage (2+2): Setup 04 TCs [FAIL] Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [62 TCs FAIL] ------------------------------ Standard External Storage (2+2+2): Setup 04 TCs [FAIL] Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [62 TCs FAIL] ------------------------------ ====================== Bare Metal environment ====================== Simplex: Setup Manual Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 49 TCs [FAIL] Sanity-Platform 07 TCs [FAIL] TOTAL: [57 TCs FAIL] ------------------------------ Duplex: Setup Manual Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [58 TCs FAIL] ------------------------------ Standard Local Storage (2+2): Setup Manual Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [58 TCs FAIL] ------------------------------ Standard External Storage (2+2+2): Setup Manual Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 52 TCs [FAIL] Sanity-Platform 05 TCs [FAIL] TOTAL: [58 TCs FAIL] STX ISO installation FAILED Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1819941 Regards Maria G. _______________________________________________ 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 sgw at linux.intel.com Thu Mar 14 02:59:07 2019 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 13 Mar 2019 19:59:07 -0700 Subject: [Starlingx-discuss] Contrib or Experimental tools location ?? Message-ID: <48a4e21c-25ad-04ad-dba6-1abeba14cd07@linux.intel.com> Folks, I know this was brought up as part of the Virtualbox Python deployment tool, which in that case we decided to keep it as was proposed in stx-tools/depolyment/virtualbox (logical location). We are likely going have more contributions that fall into experimental that the community may want to try. Should we have a contrib or experimental repo or subdirectory in stx-tools for these contributions? For example the "StarlingX in a box" work, or another different deployment tool for qemu? Thoughts? Sau! From Don.Penney at windriver.com Thu Mar 14 03:11:16 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 14 Mar 2019 03:11:16 +0000 Subject: [Starlingx-discuss] about NVME disk as the boot disk In-Reply-To: <9A85D2917C58154C960D95352B22818BD06FE1D0@fmsmsx123.amr.corp.intel.com> References: <1778C939-9D03-4AE2-8B6D-D6C54E55AAD4@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA462970@ALA-MBD.corp.ad.wrs.com> <024ffcb7-b4b7-210f-17dc-893e2cd4ba09@linux.intel.com> <9A85D2917C58154C960D95352B22818BD06FE1D0@fmsmsx123.amr.corp.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA465319@ALA-MBD.corp.ad.wrs.com> Originally, the kickstarts would automatically select the first disk for installation, which is where the code in "pre_disk_setup_common.cfg" originated. We introduced the configurable installation parameters to allow the user to configure which device should be used - at the time, this was specifically to allow for disk selection in a host with a mix of disks and SDDs. A default of sda was chosen for initial ISO installation of controller-0 as the most common choice (at the time, at least). There are some considerations for removing this default selection: a. Just for initial install of controller-0, or for all nodes? As you've seen, it would be easy enough for the ISO boot config. During initial configuration, we check to see which disk was used for the install and record it in sysinv for reinstalls/upgrades, so there'd be no further code changes required. b. For all nodes: This is set as the default value for configurable installation parameters for each node. We'd need work to support having this value unset by default, changing the utility that generates the pelinux.cfg files for each node. Likewise, we'd need to ensure sysinv-agent records the boot/rootfs device on initial boot and updates the host data in sysinv on the active controller. Not voting against making such changes, mind you... just noting some of the work items/considerations that would be required. Cheers, Don. -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, March 13, 2019 12:39 PM To: Saul Wold Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] about NVME disk as the boot disk Saul wrote: > While editing the kernel cmdline is a workaround for this issue, does it > also make sense to have a launchpad issue and work to fix the logic in > selecting an appropriate boot/rootfs device target. +1 this sounds like a great idea! -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Tuesday, March 12, 2019 5:24 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] about NVME disk as the boot disk On 3/12/19 6:54 AM, Penney, Don wrote: > Hi Yong, > > Please see the following reference: > > https://docs.starlingx.io/installation_guide/index.html#nvme-drive-as- > boot-drive > > Edit the kernel boot parameter. After you are presented with the > StarlingX ISO boot options and after you have selected the preferred > installation option (e.g. Standard Configuration / All-in-One > Controller Configuration), press the TAB key to edit the Kernel boot parameters. > Modify the *boot_device* and *rootfs_device* from the default *sda* so > that it is the correct device name for the NVMe drive (e.g. “nvme0n1”). > While editing the kernel cmdline is a workaround for this issue, does it also make sense to have a launchpad issue and work to fix the logic in selecting an appropriate boot/rootfs device target. There already is some logic to check for a USB device and fail out, so why not move that into the loop and have it auto detect nvme devices. Another option would be to change the ordering in pre_disk_setup_common code. Sau! > Cheers, > > Don. > > *From:*Hu, Yong [mailto:yong.hu at intel.com] > *Sent:* Tuesday, March 12, 2019 8:51 AM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] about NVME disk as the boot disk > > Hi folks, > > I was installing StarlingX in a NUC with 2 NVME disks (without other HD > or SATA disks), and the installation was ended up with an issue as follows: > > “ERROR: Specified installation (sda) or boot (sda) device is a USB drive.” > > It seemed NVME disk was not recognized as valid boot disk. > > With the help from @Saul, we found in “bsp-files/grub.cfg”, > “boot_device” and “rootfs_device” were by default set as “sda” in ks > cmdline: > > /linuxefi /vmlinuz inst.ks=hd:LABEL=oe_iso_boot:/smallsystem_ks.cfg > boot_device=sda rootfs_device=sda biosdevname=0 usbcore.autosuspend=-1 > console=tty0 inst.text inst.stage2=hd:LABEL=oe_iso_boot inst.gpt > security_profile=standard user_namespace.enable=1/ > > So, there are 2 ways to make NVME disks work as boot disk: > > 1. to change the grub cmdline, with “nvme0n1” for “rootfs_device” and > “boot_device” accordingly, during the installation. > 2. Not to set “rootfs_device” and “boot_device” in ks cmdline, and let > “bsp-files/kickstarts/pre_disk_setup_common.cfg” detect “nvme0n1” > dynamically. > > Though, I wonder if there are other better ways in such a case. > > Regards, > > Yong > > > _______________________________________________ > 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 mingyuan.qi at intel.com Thu Mar 14 08:44:53 2019 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Thu, 14 Mar 2019 08:44:53 +0000 Subject: [Starlingx-discuss] [Container] Ironic service containerization Message-ID: Hi folks, I'm starting the story of containerize ironic service, I'd like to add below tasks to story https://storyboard.openstack.org/#!/story/2004760 in order to enable ironic service. * Add ironic chart to stx-openstack armada manifest. Add ironic chart values to armada manifest as well as static configuration. * Generate ironic overrides Generate dynamic configuration in sysinv for ironic. * Enable ironic service Adding ironic chart to armada chart group to switch on ironic service for stx-openstack application. Should this be default in stx-openstack armada manifest? * Cleanup ironic in sysinv and puppet I'm not sure whether to add this task here or to a specific openstack component cleanup story. And speaking of the test, the first choice is to deploy starlingx standard config on bare metal because of the connection to ipmi, but it will take long time for testing. Did anyone get the chance to have ipmi/BMC enabled in vm (or it's not possible)? Best Regards, Mingyuan -------------- next part -------------- An HTML attachment was scrubbed... URL: From liang.a.fang at intel.com Thu Mar 14 11:35:19 2019 From: liang.a.fang at intel.com (Fang, Liang A) Date: Thu, 14 Mar 2019 11:35:19 +0000 Subject: [Starlingx-discuss] Code review of cinder raw cache in stx-config In-Reply-To: <0BB14CDD-5E16-45BC-9117-E1787519E895@windriver.com> References: <0BB14CDD-5E16-45BC-9117-E1787519E895@windriver.com> Message-ID: Hi Bob Thanks for your reply. So cinder raw cache feature in fact already can be enabled in current containerized Starlingx, user just need to follow the instructions you gave below. The code review https://review.openstack.org/#/c/633400/ is not needed anymore. Regarding adding project_id and user_id in cinder.conf in initial application install, it seems like an small enhancement now because this can be done easily via “system helm-override-update”. I checked with cores in openstack-helm irc, Some cores feel project_id and user_id should be populated by whatevers orchestrating the deployment of the charts. An approach(may don’t needed anymore) I’m thinking is: 1. Submit a patch to cinder, let cinder accept internal_project_name and internal_user_name in cinder.conf, not the id. 2. Hardcode the internal_project_name and internal_user_name in value.yaml 3. Let job-ks-user.yaml or create a new job to create the hardcoded project and user Regards Liang From: Church, Robert [mailto:Robert.Church at windriver.com] Sent: Wednesday, March 13, 2019 10:44 PM To: Fang, Liang A ; Rowsell, Brent Cc: Poncea, Ovidiu ; Zhu, Vivian ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Code review of cinder raw cache in stx-config Hi Liang, I took a look at this yesterday to understand what you are up against here. Ideally we would want some combination of a system helm override/armada manifest change to automatically provision the Cinder image-volume cache when the stx-openstack application is installed. We do not want to use any platform specific interface changes (i.e. system backend-modify or a new API) since we want to decouple openstack k8s application dependencies from the general k8s platform provisioning. Using the current content on master, here are the following steps required by an end user to enable this feature: # Initial application install system application-apply stx-openstack # After install, the feature requires a project/user to manage the cache openstack project create --enable --description "Block Storage Internal Tenant" cinder-internal openstack user create --project cinder-internal cinder-internal TENANTID=$(openstack project list | awk /cinder-internal/'{print $2}') USERID=$(openstack user list | awk /cinder-internal/'{print $2}') # The created project/user are needed in cinder.conf along with enabling the cache for the specific backend (we define ceph-store as part of the original application apply). Reapply the application to trigger the armada upgrade to cinder system helm-override-update cinder openstack --reuse-values --set conf.cinder.DEFAULT.cinder_internal_tenant_project_id=$TENANTID system helm-override-update cinder openstack --reuse-values --set conf.cinder.DEFAULT.cinder_internal_tenant_user_id=$USERID system helm-override-update cinder openstack --reuse-values --set conf.backends.ceph-store.image_volume_cache_enabled=true system helm-override-update cinder openstack --reuse-values --set conf.backends.ceph-store.image_volume_cache_max_size_gb=10 system helm-override-update cinder openstack --reuse-values --set conf.backends.ceph-store.image_volume_cache_max_count=5 system application-apply stx-openstack Now, back to the desired approach. The challenge here is we need a way to create a project/user as part of the initial application install and look up the UUIDs to embed in an override in a declarative manner. I’m not sure this is possible in a single application apply. 1) We could enable creating the project/user as part of the Cinder bootstrap script, but these would not be created/available at the time overrides are declared for cinder’s configuration 2) We could use an existing project/user (i.e. admin) and avoid creating a dedicated cinder project/user, but again on the initial application install they are not available at the time overrides are declared for cinder’s configuration Looking across the charts and the helm-toolkit in the OSH projects, I have yet to see an easy way to accomplish this. I think you should check with the OSH project cores to see if they have any suggestions on the best way to tackle this as part of the first install of the Cinder chart OR if a two pass approach is required (install then upgrade) Bob From: "Fang, Liang A" > Date: Wednesday, March 13, 2019 at 8:22 AM To: "Rowsell, Brent" > Cc: Ovidiu Poncea >, "Zhu, Vivian" >, "Jones, Bruce E" >, "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] Code review of cinder raw cache in stx-config Hi Brent Regarding the raw cache review: https://review.openstack.org/#/c/633400/ Currently the code is implemented according the discussion before between Ovidiu and Lisa: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-January/002548.html The raw cache is configured via “system storage-backend-modify”. e.g. system storage-backend-modify ceph-store cinder_raw_cache_gib=10 Your opinion is to decouple openstack from the storage backend. Thanks for your comment. I take a look of system subcommand, there’s no subcommand for openstack currently, at this point “system storage-backend-modify” seems is the best choice. Should we add subcommand “openstack”? Something like: system openstack cinder_raw_cache_gib=10 Or should we config openstack in other way? Could you please give suggestion on this? Thank you very much Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcel at schaible-consulting.de Thu Mar 14 11:55:33 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Thu, 14 Mar 2019 12:55:33 +0100 (CET) Subject: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA4CD75A@ALA-MBD.corp.ad.wrs.com> References: <2130766305.1081052.1552502645093@communicator.strato.com> <1466AF2176E6F040BD63860D0A241BBD46CA0171@FMSMSX109.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD46CA0358@FMSMSX109.amr.corp.intel.com> <96468830-F551-4802-82A8-FA131089987D@schaible-consulting.de> <1466AF2176E6F040BD63860D0A241BBD46CA0374@FMSMSX109.amr.corp.intel.com> <8557B550001AFB46A43A0CCC314BF85153CAB14A@FMSMSX108.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CD75A@ALA-MBD.corp.ad.wrs.com> Message-ID: <791934774.1115807.1552564533761@communicator.strato.com> Hi, so then I would suggest that we first try the image from 20190305. I'll keep you updated of the progress. Thanks, Marcel > "Khalil, Ghada" hat am 13. März 2019 um 20:51 geschrieben: > > > There is an issue with creating networks from horizon on older loads: > https://bugs.launchpad.net/starlingx/+bug/1804863 > > This is addressed in newer loads (March 1st and later) as part of the containerized env cutover. > > -----Original Message----- > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] > Sent: Wednesday, March 13, 2019 3:47 PM > To: Martinez Monroy, Elio; Marcel Schaible > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. > > Hi, > > Or you can try with a recent image. I suggest to try with 20190305, it was the latest with Green status. > > Regards. > Juan Carlos Alonso > > -----Original Message----- > From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] > Sent: Wednesday, March 13, 2019 1:33 PM > To: Marcel Schaible > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. > > I think we should start from the beginning. What about /var/log/horizon/gunicorn.log? > > BR > > Elio > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Wednesday, March 13, 2019 1:30 PM > To: Martinez Monroy, Elio > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. > > Sure. Which logs do you need? > Since it quite late here I can send them tomorrow. > > Kind regards > > Marcel > > > Am 13.03.2019 um 20:28 schrieb Martinez Monroy, Elio : > > > > So, I think this is a Horizon GUI issue that we need to investigate further, could you help us submitting the defect? In that way we can start debugging and posting comments and findings. Every log can help us. > > > > Thanks > > > > -----Original Message----- > > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > > Sent: Wednesday, March 13, 2019 1:14 PM > > To: Martinez Monroy, Elio > > Cc: starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. > > > > Nope, cli is working. The image is from 20190229. > > > > Von meinem iPhone gesendet > > > >> Am 13.03.2019 um 19:55 schrieb Martinez Monroy, Elio : > >> > >> Do you have the same problem using CLI? > >> Could you specify which image are you using? > >> > >> BR > >> > >> Elio > >> > >> -----Original Message----- > >> From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > >> Sent: Wednesday, March 13, 2019 12:44 PM > >> To: starlingx-discuss at lists.starlingx.io > >> Subject: [Starlingx-discuss] StarlingX WebUI: Cannot create or edit network: Danger: An error occurred. > >> > >> Hi *, > >> > >> when I try to create or edit a network in WebUI under "Admin->Network->Networks->Edit Network" I am getting the error: > >> > >> Danger: An error occurred. Please try again later. > >> > >> Any idea of the root cause of this issue? > >> > >> > >> Thanks > >> > >> Marcel > >> > >> _______________________________________________ > >> 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 Brent.Rowsell at windriver.com Thu Mar 14 12:26:13 2019 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Thu, 14 Mar 2019 12:26:13 +0000 Subject: [Starlingx-discuss] Code review of cinder raw cache in stx-config In-Reply-To: References: <0BB14CDD-5E16-45BC-9117-E1787519E895@windriver.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB41BC4D@ALA-MBD.corp.ad.wrs.com> This needs to be done as part of the initial deployment of the openstack application. Up to you if you want to continue the work under the existing review or start a new one. Thanks, Brent From: Fang, Liang A [mailto:liang.a.fang at intel.com] Sent: Thursday, March 14, 2019 7:35 AM To: Church, Robert ; Rowsell, Brent Cc: Poncea, Ovidiu ; Zhu, Vivian ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Code review of cinder raw cache in stx-config Hi Bob Thanks for your reply. So cinder raw cache feature in fact already can be enabled in current containerized Starlingx, user just need to follow the instructions you gave below. The code review https://review.openstack.org/#/c/633400/ is not needed anymore. Regarding adding project_id and user_id in cinder.conf in initial application install, it seems like an small enhancement now because this can be done easily via “system helm-override-update”. I checked with cores in openstack-helm irc, Some cores feel project_id and user_id should be populated by whatevers orchestrating the deployment of the charts. An approach(may don’t needed anymore) I’m thinking is: 1. Submit a patch to cinder, let cinder accept internal_project_name and internal_user_name in cinder.conf, not the id. 2. Hardcode the internal_project_name and internal_user_name in value.yaml 3. Let job-ks-user.yaml or create a new job to create the hardcoded project and user Regards Liang From: Church, Robert [mailto:Robert.Church at windriver.com] Sent: Wednesday, March 13, 2019 10:44 PM To: Fang, Liang A >; Rowsell, Brent > Cc: Poncea, Ovidiu >; Zhu, Vivian >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Code review of cinder raw cache in stx-config Hi Liang, I took a look at this yesterday to understand what you are up against here. Ideally we would want some combination of a system helm override/armada manifest change to automatically provision the Cinder image-volume cache when the stx-openstack application is installed. We do not want to use any platform specific interface changes (i.e. system backend-modify or a new API) since we want to decouple openstack k8s application dependencies from the general k8s platform provisioning. Using the current content on master, here are the following steps required by an end user to enable this feature: # Initial application install system application-apply stx-openstack # After install, the feature requires a project/user to manage the cache openstack project create --enable --description "Block Storage Internal Tenant" cinder-internal openstack user create --project cinder-internal cinder-internal TENANTID=$(openstack project list | awk /cinder-internal/'{print $2}') USERID=$(openstack user list | awk /cinder-internal/'{print $2}') # The created project/user are needed in cinder.conf along with enabling the cache for the specific backend (we define ceph-store as part of the original application apply). Reapply the application to trigger the armada upgrade to cinder system helm-override-update cinder openstack --reuse-values --set conf.cinder.DEFAULT.cinder_internal_tenant_project_id=$TENANTID system helm-override-update cinder openstack --reuse-values --set conf.cinder.DEFAULT.cinder_internal_tenant_user_id=$USERID system helm-override-update cinder openstack --reuse-values --set conf.backends.ceph-store.image_volume_cache_enabled=true system helm-override-update cinder openstack --reuse-values --set conf.backends.ceph-store.image_volume_cache_max_size_gb=10 system helm-override-update cinder openstack --reuse-values --set conf.backends.ceph-store.image_volume_cache_max_count=5 system application-apply stx-openstack Now, back to the desired approach. The challenge here is we need a way to create a project/user as part of the initial application install and look up the UUIDs to embed in an override in a declarative manner. I’m not sure this is possible in a single application apply. 1) We could enable creating the project/user as part of the Cinder bootstrap script, but these would not be created/available at the time overrides are declared for cinder’s configuration 2) We could use an existing project/user (i.e. admin) and avoid creating a dedicated cinder project/user, but again on the initial application install they are not available at the time overrides are declared for cinder’s configuration Looking across the charts and the helm-toolkit in the OSH projects, I have yet to see an easy way to accomplish this. I think you should check with the OSH project cores to see if they have any suggestions on the best way to tackle this as part of the first install of the Cinder chart OR if a two pass approach is required (install then upgrade) Bob From: "Fang, Liang A" > Date: Wednesday, March 13, 2019 at 8:22 AM To: "Rowsell, Brent" > Cc: Ovidiu Poncea >, "Zhu, Vivian" >, "Jones, Bruce E" >, "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] Code review of cinder raw cache in stx-config Hi Brent Regarding the raw cache review: https://review.openstack.org/#/c/633400/ Currently the code is implemented according the discussion before between Ovidiu and Lisa: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-January/002548.html The raw cache is configured via “system storage-backend-modify”. e.g. system storage-backend-modify ceph-store cinder_raw_cache_gib=10 Your opinion is to decouple openstack from the storage backend. Thanks for your comment. I take a look of system subcommand, there’s no subcommand for openstack currently, at this point “system storage-backend-modify” seems is the best choice. Should we add subcommand “openstack”? Something like: system openstack cinder_raw_cache_gib=10 Or should we config openstack in other way? Could you please give suggestion on this? Thank you very much Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From Robert.Church at windriver.com Thu Mar 14 12:48:17 2019 From: Robert.Church at windriver.com (Church, Robert) Date: Thu, 14 Mar 2019 12:48:17 +0000 Subject: [Starlingx-discuss] Code review of cinder raw cache in stx-config In-Reply-To: References: <0BB14CDD-5E16-45BC-9117-E1787519E895@windriver.com> Message-ID: <18E9F5EA-650C-4304-BEE2-440A9B92D8C0@windriver.com> Hi Liang, See Inline… Regards, Bob From: "Fang, Liang A" Date: Thursday, March 14, 2019 at 6:35 AM To: Robert Church , "Rowsell, Brent" Cc: Ovidiu Poncea , "Zhu, Vivian" , "Jones, Bruce E" , "starlingx-discuss at lists.starlingx.io" Subject: RE: [Starlingx-discuss] Code review of cinder raw cache in stx-config Hi Bob Thanks for your reply. So cinder raw cache feature in fact already can be enabled in current containerized Starlingx, user just need to follow the instructions you gave below. The code review https://review.openstack.org/#/c/633400/ is not needed anymore. [RTC] Yes. I’ve tested the basic functionality and it works as advertised. As Brent mentioned in his response keep this review or abandon it.. Up to you… Regarding adding project_id and user_id in cinder.conf in initial application install, it seems like an small enhancement now because this can be done easily via “system helm-override-update”. I checked with cores in openstack-helm irc, Some cores feel project_id and user_id should be populated by whatevers orchestrating the deployment of the charts. An approach(may don’t needed anymore) I’m thinking is: 1. Submit a patch to cinder, let cinder accept internal_project_name and internal_user_name in cinder.conf, not the id. [RTC] Agreed. We’d need an upstream patch to Cinder so that it would look up the UUID based on the project/user name provided in the conf file <-- this is the key element, I think 1. Hardcode the internal_project_name and internal_user_name in value.yaml [RTC] Agreed. This would provide the ability to keep the default or override the project/user to suit a deployment 1. Let job-ks-user.yaml or create a new job to create the hardcoded project and user [RTC] You could enable the bootstrap script (see how keystone does it) and then add the project/user creation step in values .yaml Regards Liang From: Church, Robert [mailto:Robert.Church at windriver.com] Sent: Wednesday, March 13, 2019 10:44 PM To: Fang, Liang A ; Rowsell, Brent Cc: Poncea, Ovidiu ; Zhu, Vivian ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Code review of cinder raw cache in stx-config Hi Liang, I took a look at this yesterday to understand what you are up against here. Ideally we would want some combination of a system helm override/armada manifest change to automatically provision the Cinder image-volume cache when the stx-openstack application is installed. We do not want to use any platform specific interface changes (i.e. system backend-modify or a new API) since we want to decouple openstack k8s application dependencies from the general k8s platform provisioning. Using the current content on master, here are the following steps required by an end user to enable this feature: # Initial application install system application-apply stx-openstack # After install, the feature requires a project/user to manage the cache openstack project create --enable --description "Block Storage Internal Tenant" cinder-internal openstack user create --project cinder-internal cinder-internal TENANTID=$(openstack project list | awk /cinder-internal/'{print $2}') USERID=$(openstack user list | awk /cinder-internal/'{print $2}') # The created project/user are needed in cinder.conf along with enabling the cache for the specific backend (we define ceph-store as part of the original application apply). Reapply the application to trigger the armada upgrade to cinder system helm-override-update cinder openstack --reuse-values --set conf.cinder.DEFAULT.cinder_internal_tenant_project_id=$TENANTID system helm-override-update cinder openstack --reuse-values --set conf.cinder.DEFAULT.cinder_internal_tenant_user_id=$USERID system helm-override-update cinder openstack --reuse-values --set conf.backends.ceph-store.image_volume_cache_enabled=true system helm-override-update cinder openstack --reuse-values --set conf.backends.ceph-store.image_volume_cache_max_size_gb=10 system helm-override-update cinder openstack --reuse-values --set conf.backends.ceph-store.image_volume_cache_max_count=5 system application-apply stx-openstack Now, back to the desired approach. The challenge here is we need a way to create a project/user as part of the initial application install and look up the UUIDs to embed in an override in a declarative manner. I’m not sure this is possible in a single application apply. 1. We could enable creating the project/user as part of the Cinder bootstrap script, but these would not be created/available at the time overrides are declared for cinder’s configuration 2. We could use an existing project/user (i.e. admin) and avoid creating a dedicated cinder project/user, but again on the initial application install they are not available at the time overrides are declared for cinder’s configuration Looking across the charts and the helm-toolkit in the OSH projects, I have yet to see an easy way to accomplish this. I think you should check with the OSH project cores to see if they have any suggestions on the best way to tackle this as part of the first install of the Cinder chart OR if a two pass approach is required (install then upgrade) Bob From: "Fang, Liang A" > Date: Wednesday, March 13, 2019 at 8:22 AM To: "Rowsell, Brent" > Cc: Ovidiu Poncea >, "Zhu, Vivian" >, "Jones, Bruce E" >, "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] Code review of cinder raw cache in stx-config Hi Brent Regarding the raw cache review: https://review.openstack.org/#/c/633400/ Currently the code is implemented according the discussion before between Ovidiu and Lisa: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-January/002548.html The raw cache is configured via “system storage-backend-modify”. e.g. system storage-backend-modify ceph-store cinder_raw_cache_gib=10 Your opinion is to decouple openstack from the storage backend. Thanks for your comment. I take a look of system subcommand, there’s no subcommand for openstack currently, at this point “system storage-backend-modify” seems is the best choice. Should we add subcommand “openstack”? Something like: system openstack cinder_raw_cache_gib=10 Or should we config openstack in other way? Could you please give suggestion on this? Thank you very much Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From liang.a.fang at intel.com Thu Mar 14 12:53:43 2019 From: liang.a.fang at intel.com (Fang, Liang A) Date: Thu, 14 Mar 2019 12:53:43 +0000 Subject: [Starlingx-discuss] Code review of cinder raw cache in stx-config In-Reply-To: <18E9F5EA-650C-4304-BEE2-440A9B92D8C0@windriver.com> References: <0BB14CDD-5E16-45BC-9117-E1787519E895@windriver.com> <18E9F5EA-650C-4304-BEE2-440A9B92D8C0@windriver.com> Message-ID: OK, thanks Bob and Brent! Regards Liang From: Church, Robert [mailto:Robert.Church at windriver.com] Sent: Thursday, March 14, 2019 8:48 PM To: Fang, Liang A ; Rowsell, Brent Cc: Poncea, Ovidiu ; Zhu, Vivian ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Code review of cinder raw cache in stx-config Hi Liang, See Inline… Regards, Bob From: "Fang, Liang A" > Date: Thursday, March 14, 2019 at 6:35 AM To: Robert Church >, "Rowsell, Brent" > Cc: Ovidiu Poncea >, "Zhu, Vivian" >, "Jones, Bruce E" >, "starlingx-discuss at lists.starlingx.io" > Subject: RE: [Starlingx-discuss] Code review of cinder raw cache in stx-config Hi Bob Thanks for your reply. So cinder raw cache feature in fact already can be enabled in current containerized Starlingx, user just need to follow the instructions you gave below. The code review https://review.openstack.org/#/c/633400/ is not needed anymore. [RTC] Yes. I’ve tested the basic functionality and it works as advertised. As Brent mentioned in his response keep this review or abandon it.. Up to you… Regarding adding project_id and user_id in cinder.conf in initial application install, it seems like an small enhancement now because this can be done easily via “system helm-override-update”. I checked with cores in openstack-helm irc, Some cores feel project_id and user_id should be populated by whatevers orchestrating the deployment of the charts. An approach(may don’t needed anymore) I’m thinking is: 1. Submit a patch to cinder, let cinder accept internal_project_name and internal_user_name in cinder.conf, not the id. [RTC] Agreed. We’d need an upstream patch to Cinder so that it would look up the UUID based on the project/user name provided in the conf file <-- this is the key element, I think 1. Hardcode the internal_project_name and internal_user_name in value.yaml [RTC] Agreed. This would provide the ability to keep the default or override the project/user to suit a deployment 1. Let job-ks-user.yaml or create a new job to create the hardcoded project and user [RTC] You could enable the bootstrap script (see how keystone does it) and then add the project/user creation step in values .yaml Regards Liang From: Church, Robert [mailto:Robert.Church at windriver.com] Sent: Wednesday, March 13, 2019 10:44 PM To: Fang, Liang A >; Rowsell, Brent > Cc: Poncea, Ovidiu >; Zhu, Vivian >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Code review of cinder raw cache in stx-config Hi Liang, I took a look at this yesterday to understand what you are up against here. Ideally we would want some combination of a system helm override/armada manifest change to automatically provision the Cinder image-volume cache when the stx-openstack application is installed. We do not want to use any platform specific interface changes (i.e. system backend-modify or a new API) since we want to decouple openstack k8s application dependencies from the general k8s platform provisioning. Using the current content on master, here are the following steps required by an end user to enable this feature: # Initial application install system application-apply stx-openstack # After install, the feature requires a project/user to manage the cache openstack project create --enable --description "Block Storage Internal Tenant" cinder-internal openstack user create --project cinder-internal cinder-internal TENANTID=$(openstack project list | awk /cinder-internal/'{print $2}') USERID=$(openstack user list | awk /cinder-internal/'{print $2}') # The created project/user are needed in cinder.conf along with enabling the cache for the specific backend (we define ceph-store as part of the original application apply). Reapply the application to trigger the armada upgrade to cinder system helm-override-update cinder openstack --reuse-values --set conf.cinder.DEFAULT.cinder_internal_tenant_project_id=$TENANTID system helm-override-update cinder openstack --reuse-values --set conf.cinder.DEFAULT.cinder_internal_tenant_user_id=$USERID system helm-override-update cinder openstack --reuse-values --set conf.backends.ceph-store.image_volume_cache_enabled=true system helm-override-update cinder openstack --reuse-values --set conf.backends.ceph-store.image_volume_cache_max_size_gb=10 system helm-override-update cinder openstack --reuse-values --set conf.backends.ceph-store.image_volume_cache_max_count=5 system application-apply stx-openstack Now, back to the desired approach. The challenge here is we need a way to create a project/user as part of the initial application install and look up the UUIDs to embed in an override in a declarative manner. I’m not sure this is possible in a single application apply. 1) We could enable creating the project/user as part of the Cinder bootstrap script, but these would not be created/available at the time overrides are declared for cinder’s configuration 2) We could use an existing project/user (i.e. admin) and avoid creating a dedicated cinder project/user, but again on the initial application install they are not available at the time overrides are declared for cinder’s configuration Looking across the charts and the helm-toolkit in the OSH projects, I have yet to see an easy way to accomplish this. I think you should check with the OSH project cores to see if they have any suggestions on the best way to tackle this as part of the first install of the Cinder chart OR if a two pass approach is required (install then upgrade) Bob From: "Fang, Liang A" > Date: Wednesday, March 13, 2019 at 8:22 AM To: "Rowsell, Brent" > Cc: Ovidiu Poncea >, "Zhu, Vivian" >, "Jones, Bruce E" >, "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] Code review of cinder raw cache in stx-config Hi Brent Regarding the raw cache review: https://review.openstack.org/#/c/633400/ Currently the code is implemented according the discussion before between Ovidiu and Lisa: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-January/002548.html The raw cache is configured via “system storage-backend-modify”. e.g. system storage-backend-modify ceph-store cinder_raw_cache_gib=10 Your opinion is to decouple openstack from the storage backend. Thanks for your comment. I take a look of system subcommand, there’s no subcommand for openstack currently, at this point “system storage-backend-modify” seems is the best choice. Should we add subcommand “openstack”? Something like: system openstack cinder_raw_cache_gib=10 Or should we config openstack in other way? Could you please give suggestion on this? Thank you very much Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Thu Mar 14 12:56:17 2019 From: Greg.Waines at windriver.com (Waines, Greg) Date: Thu, 14 Mar 2019 12:56:17 +0000 Subject: [Starlingx-discuss] [Container] Ironic service containerization In-Reply-To: References: Message-ID: <7A22CC1A-C578-4A4A-AD08-0F62C682FD9B@windriver.com> In-lined comments, Greg. From: "Qi, Mingyuan" Date: Thursday, March 14, 2019 at 4:45 AM To: "starlingx-discuss at lists.starlingx.io" Cc: "Rowsell, Brent" , "Miller, Frank" , Greg Waines , "Xie, Cindy" , "An, Ran1" Subject: [Container] Ironic service containerization Hi folks, I’m starting the story of containerize ironic service, I’d like to add below tasks to story https://storyboard.openstack.org/#!/story/2004760 in order to enable ironic service. * Add ironic chart to stx-openstack armada manifest. [Greg] Do we want Ironic to be an OPTIONAL service in StarlingX ? My initial thoughts are yes ... thinking most StarlingX deployments will not use it, so for utilization reasons it would be better not to even run it. So if we are making Ironic OPTIONAL and disabled by default, how is this achieved ? e.g. - does it have a separate stx-ironic-openstack armada manifest ? OR - Is it included in the stx-openstack armada manifest and somehow(?) disabled by default, and can be enabled thru helm-overrides ? Add ironic chart values to armada manifest as well as static configuration. * Generate ironic overrides Generate dynamic configuration in sysinv for ironic. [Greg] As part of this work I think it would be good to understand (and review with starlingx cores): - Where do we want Ironic Conductor running ? Controller or Compute ? Do we have a choice in vanilla upstream ironic ? - Is it possible to have an HA deployment of Ironic Conductor in vanilla upstream ironic ? - How do we set it up such that system can manage both VM Instances and Bare Metal Instances ? i.e. I believe this is done thru host aggregates ? will/can these be setup as part of starlingx system overrides ? Greg. * Enable ironic service Adding ironic chart to armada chart group to switch on ironic service for stx-openstack application. Should this be default in stx-openstack armada manifest? * Cleanup ironic in sysinv and puppet I’m not sure whether to add this task here or to a specific openstack component cleanup story. And speaking of the test, the first choice is to deploy starlingx standard config on bare metal because of the connection to ipmi, but it will take long time for testing. Did anyone get the chance to have ipmi/BMC enabled in vm (or it’s not possible)? Best Regards, Mingyuan -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Thu Mar 14 12:57:21 2019 From: Greg.Waines at windriver.com (Waines, Greg) Date: Thu, 14 Mar 2019 12:57:21 +0000 Subject: [Starlingx-discuss] [Container] Ironic service containerization In-Reply-To: References: Message-ID: Mingyuan, I don’t understand why doing testing of ironic on hardware will take a long time. What is the issue ? Greg. From: "Qi, Mingyuan" Date: Thursday, March 14, 2019 at 4:45 AM To: "starlingx-discuss at lists.starlingx.io" Cc: "Rowsell, Brent" , "Miller, Frank" , Greg Waines , "Xie, Cindy" , "An, Ran1" Subject: [Container] Ironic service containerization Hi folks, I’m starting the story of containerize ironic service, I’d like to add below tasks to story https://storyboard.openstack.org/#!/story/2004760 in order to enable ironic service. * Add ironic chart to stx-openstack armada manifest. Add ironic chart values to armada manifest as well as static configuration. * Generate ironic overrides Generate dynamic configuration in sysinv for ironic. * Enable ironic service Adding ironic chart to armada chart group to switch on ironic service for stx-openstack application. Should this be default in stx-openstack armada manifest? * Cleanup ironic in sysinv and puppet I’m not sure whether to add this task here or to a specific openstack component cleanup story. And speaking of the test, the first choice is to deploy starlingx standard config on bare metal because of the connection to ipmi, but it will take long time for testing. Did anyone get the chance to have ipmi/BMC enabled in vm (or it’s not possible)? Best Regards, Mingyuan -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ian.Jolliffe at windriver.com Thu Mar 14 13:24:51 2019 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Thu, 14 Mar 2019 13:24:51 +0000 Subject: [Starlingx-discuss] [TSC] Minutes 3/7 Message-ID: <0DC74F09-3DA2-478F-B8BE-F99325156799@windriver.com> TSC election for Q2 (ildikov) Needs to be held in Q2 Timing recommendation - watch out for summit conflict Need a date - not week leading up to release or summit. Before or after summit? Need a date - not week leading up to release or summit. Before or after summit? Leverage OpenStack Tools and Processes Upload a patch to election repo https://governance.openstack.org/election/ Bruce volunteered to be election official + Ildiko from Foundation Could have another - not likely a popular job :) Positions for election: 1 - Open, 1 from Wind River, 1 from Intel, Ana and Miguel position also up for election Denver summit workshop Is up on the schedule now: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23630/starlingx-hands-on-workshop. Thanks to Ildiko and foundation team for putting it up. Need to confirm VM's and size available - need to watch out for machine load Feedback from Packet team - give each user a smaller machine to minimize problems if a participant hangs a machine. Blog post to advertise (ildikov) Curtis - I can work on this unless someone else wants to, could have something next week Multi-os direction Looking for input on which kernel to use - Abraham doing analysis Spec to be abandoned - LTS to be taken for STX Team to look at a "How to/recipe" for changing Kernel Packet.com PoC Curtis - Still awaiting MOU; emailed Brian K. @packet earlier this week for an update Draft is available - will send over. 3 Edge sites launched and up and running Working to connect edge with Wireless infrastructure Brian from Packet.com feels STX is a great fit for Packet Each site will have CBRS access Forum Sessions https://etherpad.openstack.org/p/stx-forum-preparation-denver-2019 Curtis - I submitted "StarlingX for OpenStack Operators". They only allow one moderator per session it seems so I couldn't add Shuquan. Public service announcements: Welcome to join the 9th Open Source Hackathon in Shenzhen China from Apr.18 - Apr.20 Some sessions on STX planned - also bug hacking sessions -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ken.Young at windriver.com Thu Mar 14 14:27:55 2019 From: Ken.Young at windriver.com (Young, Ken) Date: Thu, 14 Mar 2019 14:27:55 +0000 Subject: [Starlingx-discuss] [build][meeting] Build team meeting Agenda for 3/14/2019 In-Reply-To: <0B566C62EC792145B40E29EFEBF1AB4710617839@fmsmsx104.amr.corp.intel.com> References: <0B566C62EC792145B40E29EFEBF1AB4710617839@fmsmsx104.amr.corp.intel.com> Message-ID: <5959AA8E-FDBA-4A0E-BF65-11353F7CBD55@windriver.com> Cesar, I have a conflict at 11 which I cannot miss. I will join the meeting late if I can. On the CENGN side, an issue has been exposed on the recipe for building the installer and file versions. Please see here: https://bugs.launchpad.net/starlingx/+bug/1819941 We should discuss how to handle this before implementing a fix. Scott has some ideas. Also, can we get an update from Memo / Victor on the security scanning? Thanks! Regards, Ken Y From: "Lara, Cesar" Date: Wednesday, March 13, 2019 at 7:17 PM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] [build][meeting] Build team meeting Agenda for 3/14/2019 Build team meeting Agenda for 3/14/2019 - Cengn build update - Help needed - Opens Abraham to cover for Cesar chairing this meeting Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Thu Mar 14 15:08:15 2019 From: serverascode at gmail.com (Curtis) Date: Thu, 14 Mar 2019 11:08:15 -0400 Subject: [Starlingx-discuss] Contrib or Experimental tools location ?? In-Reply-To: <48a4e21c-25ad-04ad-dba6-1abeba14cd07@linux.intel.com> References: <48a4e21c-25ad-04ad-dba6-1abeba14cd07@linux.intel.com> Message-ID: On Wed, Mar 13, 2019 at 11:00 PM Saul Wold wrote: > > Folks, > > I know this was brought up as part of the Virtualbox Python deployment > tool, which in that case we decided to keep it as was proposed in > stx-tools/depolyment/virtualbox (logical location). > > We are likely going have more contributions that fall into experimental > that the community may want to try. > > Should we have a contrib or experimental repo or subdirectory in > stx-tools for these contributions? > > For example the "StarlingX in a box" work, or another different > deployment tool for qemu? > > Thoughts? > I am in favour of having an experimental repository where useful code that is not as heavily scrutinized is stored. That code, if used over time, can be moved out of the repository into a more permanent location with full project workflows and processes applied. My canonical example is the osops-tools-contrib [0] repo. I am just always a fan of large open source projects having something like this where new perhaps inexperienced contributors can submit code, or organizations can submit code that is not "fully baked" for overall review for potential usefulness. Now, how many contributions we might see, and what it might look like are certainly up for debate, but I still think it's a useful repository to have, and if it is not used over time then we can remove it. But without it we'll never know. :) I am also thinking of myself here as the stx community is putting on a workshop at the summit and there will likely be code and docs that go with that, and perhaps this would be a good place for that kind of thing to live. Thanks, Curtis [0]: https://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/README.rst > > Sau! > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Thu Mar 14 16:14:06 2019 From: scott.little at windriver.com (Scott Little) Date: Thu, 14 Mar 2019 12:14:06 -0400 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190312 In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F35EC971A@SHSMSX104.ccr.corp.intel.com> References: <151EE31B9FCCA54397A757BC674650F0BA4CD6EA@ALA-MBD.corp.ad.wrs.com> <66534bce-f927-4d9d-869e-f6b8e6845224@windriver.com> <7f49bcb7-1483-dff1-7601-c04f60f8bbf4@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F35EC971A@SHSMSX104.ccr.corp.intel.com> Message-ID: The last two builds worked.  The workaround we implemented within CENGN will see us through until the next centos rebase.  I believe we can no close the two P1's raised. - https://bugs.launchpad.net/starlingx/+bug/1819964 - https://bugs.launchpad.net/starlingx/+bug/1819941 In there place I have created a story to track the tooling changes in stx-tools to prevent a repeat. Scott On 2019-03-13 8:38 p.m., Xie, Cindy wrote: > > Thanks Scott for the quick fix! > > Just wondering if we need an intelligent kernel change discovery > mechanism so that the installer will be automatically re-built… > > Thx. - cindy > > *From:*Scott Little [mailto:scott.little at windriver.com] > *Sent:* Thursday, March 14, 2019 8:23 AM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190312 > > Build complete.  Mounted the iso and it does look like a 7.6 installer > this time. > > This one is ready for test. > > The regular 8:30 EST will start shortly. > > Scott > > On 2019-03-13 5:11 p.m., Scott Little wrote: > > Launchpad: https://bugs.launchpad.net/starlingx/+bug/1819941 > > > I've started a new CENGN build after deleting the contents of ... > > .../stx-tools/centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/EFI > .../stx-tools/centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/images > .../stx-tools/centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/isolinux > .../stx-tools/centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/LiveOS > > This should trigger a redownload of the squashfs.img, and should > yield a 7.6 compatible installer. > > ETA ~ 8pm EST > > Scott > > On 2019-03-13 4:40 p.m., Young, Ken wrote: > > Team, > > This is an issue with the installer build on CENGN.  I am > assigning to Scott for triage and fix. > > /KenY > > *From: *"Khalil, Ghada" > > *Date: *Wednesday, March 13, 2019 at 2:44 PM > *To: *"Perez Ibarra, Maria G" > , > "starlingx-discuss at lists.starlingx.io" > > > , XIAO XIE > , Shuicheng > Lin > *Subject: *Re: [Starlingx-discuss] [Containers] Sanity Test - > ISO 20190312 > > Hi Cindy / Shuicheng, > > Please have someone from your team investigate. It seems there > is an issue with the installer after the merge of CentOS 7.6. > > Thanks, > > Ghada > > *From:* Perez Ibarra, Maria G > [mailto:maria.g.perez.ibarra at intel.com] > *Sent:* Wednesday, March 13, 2019 1:23 PM > *To:* starlingx-discuss at lists.starlingx.io > > *Subject:* [Starlingx-discuss] [Containers] Sanity Test - ISO > 20190312 > > *Status of the Sanity Test for last CENGN ISO: */bootimage.iso > from 2019-Mar-12 /(link > ) > > > Status : RED > > =================== > > Virtual environment > > =================== > > Simplex: > > Setup                 04 TCs [FAIL] > > Provision-Containers  01 TCs [FAIL] > > Sanity-OpenStack      49 TCs [FAIL] > > Sanity-Platform       07 TCs [FAIL] > > TOTAL:                [61 TCs FAIL] > > ------------------------------ > > Duplex: > > Setup                 04 TCs [FAIL] > > Provision-Containers  01 TCs [FAIL] > > Sanity-OpenStack      52 TCs [FAIL] > > Sanity-Platform       05 TCs [FAIL] > > TOTAL:                [62 TCs FAIL] > > ------------------------------ > > Standard Local Storage (2+2): > > Setup                 04 TCs [FAIL] > > Provision-Containers  01 TCs [FAIL] > > Sanity-OpenStack      52 TCs [FAIL] > > Sanity-Platform       05 TCs [FAIL] > > TOTAL:                [62 TCs FAIL] > > ------------------------------ > > Standard External Storage (2+2+2): > > Setup                 04 TCs [FAIL] > > Provision-Containers  01 TCs [FAIL] > > Sanity-OpenStack      52 TCs [FAIL] > > Sanity-Platform       05 TCs [FAIL] > > TOTAL:                [62 TCs FAIL] > > ------------------------------ > > ====================== > > Bare Metal environment > > ====================== > > Simplex: > > Setup                 Manual > > Provision-Containers  01 TCs [FAIL] > > Sanity-OpenStack      49 TCs [FAIL] > > Sanity-Platform       07 TCs [FAIL] > > TOTAL:                [57 TCs FAIL] > > ------------------------------ > > Duplex: > > Setup                 Manual > > Provision-Containers  01 TCs [FAIL] > > Sanity-OpenStack      52 TCs [FAIL] > > Sanity-Platform       05 TCs [FAIL] > > TOTAL:                [58 TCs FAIL] > > ------------------------------ > > Standard Local Storage (2+2): > > Setup                 Manual > > Provision-Containers  01 TCs [FAIL] > > Sanity-OpenStack      52 TCs [FAIL] > > Sanity-Platform       05 TCs [FAIL] > > TOTAL:                [58 TCs FAIL] > > ------------------------------ > > Standard External Storage (2+2+2): > > Setup                 Manual > > Provision-Containers  01 TCs [FAIL] > > Sanity-OpenStack      52 TCs [FAIL] > > Sanity-Platform       05 TCs [FAIL] > > TOTAL: [58 TCs FAIL] > > STX ISO installation FAILED > > Launchpad opened: > https://bugs.launchpad.net/starlingx/+bug/1819941 > > Regards > > Maria G. > > > > _______________________________________________ > > 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 andy.ning at windriver.com Thu Mar 14 19:39:23 2019 From: andy.ning at windriver.com (Andy Ning) Date: Thu, 14 Mar 2019 15:39:23 -0400 Subject: [Starlingx-discuss] [Zuul] failure on review in stx-config project Message-ID: Hi, I have a review https://review.openstack.org/#/c/642488/2 with small changes to sysinv. sysinv-tox-py27 and sysinv-tox-py35 failed for this review. However the failure doesn't seem to be related to my changes. The test output has traceback like: 2019-03-14 15:56:10.816504 | ubuntu-bionic | tests.db.sqlalchemy.test_migrations.TestMigrations.test_postgresql_connect_fail 2019-03-14 15:56:10.816685 | ubuntu-bionic | ------------------------------------------------------------------------------- 2019-03-14 15:56:10.816716 | ubuntu-bionic | 2019-03-14 15:56:10.816781 | ubuntu-bionic | Captured traceback: 2019-03-14 15:56:10.816845 | ubuntu-bionic | ~~~~~~~~~~~~~~~~~~~ 2019-03-14 15:56:10.816945 | ubuntu-bionic | Traceback (most recent call last): 2019-03-14 15:56:10.817260 | ubuntu-bionic | File "/home/zuul/src/git.openstack.org/openstack/stx-config/sysinv/sysinv/sysinv/sysinv/tests/db/sqlalchemy/test_migrations.py", line 523, in setUp 2019-03-14 15:56:10.817370 | ubuntu-bionic | super(TestMigrations, self).setUp() 2019-03-14 15:56:10.817679 | ubuntu-bionic | File "/home/zuul/src/git.openstack.org/openstack/stx-config/sysinv/sysinv/sysinv/sysinv/tests/db/sqlalchemy/test_migrations.py", line 188, in setUp 2019-03-14 15:56:10.817817 | ubuntu-bionic | self.engines[key] = sqlalchemy.create_engine(value) 2019-03-14 15:56:10.818086 | ubuntu-bionic | File "/tmp/zuul_sysinvtox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/__init__.py", line 387, in create_engine 2019-03-14 15:56:10.818203 | ubuntu-bionic | return strategy.create(*args, **kwargs) 2019-03-14 15:56:10.818457 | ubuntu-bionic | File "/tmp/zuul_sysinvtox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/strategies.py", line 80, in create 2019-03-14 15:56:10.818574 | ubuntu-bionic | dbapi = dialect_cls.dbapi(**dbapi_args) 2019-03-14 15:56:10.818848 | ubuntu-bionic | File "/tmp/zuul_sysinvtox/py27/local/lib/python2.7/site-packages/sqlalchemy/dialects/postgresql/psycopg2.py", line 554, in dbapi 2019-03-14 15:56:10.818920 | ubuntu-bionic | import psycopg2 2019-03-14 15:56:10.819158 | ubuntu-bionic | File "/tmp/zuul_sysinvtox/py27/local/lib/python2.7/site-packages/psycopg2/__init__.py", line 50, in 2019-03-14 15:56:10.819308 | ubuntu-bionic | from psycopg2._psycopg import ( # noqa 2019-03-14 15:56:10.819740 | ubuntu-bionic | ImportError: /tmp/zuul_sysinvtox/py27/local/lib/python2.7/site-packages/psycopg2/.libs/libresolv-2-c4c53def.5.so: symbol __res_maybe_init version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference 2019-03-14 15:56:10.819785 | ubuntu-bionic | Also, local run of tox py27 and py35 both passed. Anybody knows what's going wrong? Any fix is in progress? Thanks, Andy -- Andy Ning Cube: 3071 Tel: 613-9631408 (int: 4408) Skype: andy.ning.wr From fungi at yuggoth.org Thu Mar 14 20:02:36 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 14 Mar 2019 20:02:36 +0000 Subject: [Starlingx-discuss] [Zuul] failure on review in stx-config project In-Reply-To: References: Message-ID: <20190314200235.oksm642vn33nq5hi@yuggoth.org> On 2019-03-14 15:39:23 -0400 (-0400), Andy Ning wrote: > I have a review https://review.openstack.org/#/c/642488/2 with small changes > to sysinv. sysinv-tox-py27 and sysinv-tox-py35 failed for this review. > However the failure doesn't seem to be related to my changes. The test > output has traceback like: [...] > 2019-03-14 15:56:10.819308 | ubuntu-bionic | from psycopg2._psycopg > import ( # noqa > 2019-03-14 15:56:10.819740 | ubuntu-bionic | ImportError: /tmp/zuul_sysinvtox/py27/local/lib/python2.7/site-packages/psycopg2/.libs/libresolv-2-c4c53def.5.so: > symbol __res_maybe_init version GLIBC_PRIVATE not defined in file libc.so.6 > with link time reference > 2019-03-14 15:56:10.819785 | ubuntu-bionic | > > Also, local run of tox py27 and py35 both passed. > > Anybody knows what's going wrong? Any fix is in progress? As of roughly 22:00 UTC (on Wednesday, March 13), the default nodeset in the opendev/base-jobs repository was updated from ubuntu-xenial (16.04 LTS) to ubuntu-bionic (18.04 LTS). In the case of the sysinv-tox-py35 job you almost certainly need to set an explicit "nodeset: ubuntu-xenial" so that it runs on a platform with actually provides a Python 3.5 interpreter (ubuntu-bionic only provides 3.6 and 3.7). For the sysinv-tox-py27 psycopg2 error above, it looks like it's attempting to use a libresolv build which references symbols from a different libc. Are you maybe installing bundled libraries previously built on an ubuntu-xenial node? -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From Tao.Liu at windriver.com Thu Mar 14 20:53:37 2019 From: Tao.Liu at windriver.com (Liu, Tao) Date: Thu, 14 Mar 2019 20:53:37 +0000 Subject: [Starlingx-discuss] Questions related to FM containerization Message-ID: <7242A3DC72E453498E3D783BBB134C3E9DDD2C1F@ALA-MBD.corp.ad.wrs.com> Hi Mario, I think it would simplify the implementation significantly if we only containerize the FM rest API service. You will need to add POST and PUT support in the API server and VIM will use the rest APIs to raise the instance alarms/logs. The alarm POST / PUT request handler will need to add alarm history entries to the event log database table. The rest API service interfaces with the configured database backend directly. Currently postgres is configured as the backend. You will need to configure mysql as the database backend for the containerized FM rest API service. Openstack Horizon will also interface with containerized FM rest API service and retrieve the instances alarm and event logs. I think the alarm suppression should still be managed through the platform fm cli and horizon. For the current release, we will not suppress the instance alarms nor would raise SNMP traps inside the containerized services. Regards, Tao Liu ------------------------------ Message: 2 Date: Wed, 13 Mar 2019 21:52:12 +0000 From: "Arevalo, Mario Alfredo C" To: "starlingx-discuss at lists.starlingx.io" Cc: "brent.rowsell at windriver.com" Subject: [Starlingx-discuss] Questions related to FM containerization Message-ID: <6594B51DBE477C48AAE23675314E6C46645994B3 at fmsmsx107.amr.corp.intel.com> Content-Type: text/plain; charset="us-ascii" Hi Brent and team, This mail plans to interchange information in order to get more granularity about the "Fault Manager" Containerization process where the final objective is to deploy a pod or pods which make completely match with the design of containerization architecture. According from the feedback received yesterday in our meeting and taking a look to the source code and the processes which are running in a deployed environment I can understand the possible missing parts. This is my understanding about the full picture and some questions about it, please let me know if something is wrong or deviates from the original objective/result. The storyboard [1] related to FM chart will be finished when the FM restful API and the FM manager main services are containerized and work correctly with the rest of the StarlingX components: - I think the best approach is to run a container per service and both containers should live in the same pod. - Both services should consume the same Docker image in order to reduce the memory foot print. - According the previous shared information and my code exploring I understand the FM manager (fmManager binary) is a service which listens in the port 8001 and executes requests. It is launched by an script called "fminit". At this point I have a pair of questions, is this the service which the storyboard [1] makes reference of, intended to have an instance in bare metal and another one exposed by a container? If the last questions is yes, we will have 2 instances of the same service then they should be exposed in a different port, and how about fm rest api service, it will just exist in a container? FM manager service has interaction with a PostgreSQL data base, then I wonder how this will be handled. Does this containerized service point to the bare metal database? Should we add a new chart which exposes a PostgreSQL due to the current chart tarball or just include one for MariaDB. Then the task 28876 makes reference to modify nfv_vim[2] in order to get the alarms information from the container? - Surfing in a deployed image I saw that is possible to remove alarms from the web interface provided by horizon, then the task 28878 makes reference to points to the FM manager containerized service from horizon, however it is not clear for me the task 28877 described in the chart storyboard[1]. These are some points and questions which will give a better understanding for the rest of tasks, however, possibly, I will get more questions during this process I will be in contact with all of you. Thank you for your help. Best Regards. Mario. References: [1] https://storyboard.openstack.org/#!/story/2004008 [2] https://git.starlingx.io/cgit/stx-nfv/tree/nfv/nfv-vim/nfv_vim -------------- 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 10, Issue 64 ************************************************* From andy.ning at windriver.com Thu Mar 14 20:57:09 2019 From: andy.ning at windriver.com (Andy Ning) Date: Thu, 14 Mar 2019 16:57:09 -0400 Subject: [Starlingx-discuss] [Zuul] failure on review in stx-config project In-Reply-To: <20190314200235.oksm642vn33nq5hi@yuggoth.org> References: <20190314200235.oksm642vn33nq5hi@yuggoth.org> Message-ID: <5057dc09-fbaa-dd31-56eb-5309408cf619@windriver.com> Thanks Jeremy, see my comments inline ... Andy On 2019-03-14 04:02 PM, Jeremy Stanley wrote: > On 2019-03-14 15:39:23 -0400 (-0400), Andy Ning wrote: >> I have a review https://review.openstack.org/#/c/642488/2 with small changes >> to sysinv. sysinv-tox-py27 and sysinv-tox-py35 failed for this review. >> However the failure doesn't seem to be related to my changes. The test >> output has traceback like: > [...] >> 2019-03-14 15:56:10.819308 | ubuntu-bionic | from psycopg2._psycopg >> import ( # noqa >> 2019-03-14 15:56:10.819740 | ubuntu-bionic | ImportError: /tmp/zuul_sysinvtox/py27/local/lib/python2.7/site-packages/psycopg2/.libs/libresolv-2-c4c53def.5.so: >> symbol __res_maybe_init version GLIBC_PRIVATE not defined in file libc.so.6 >> with link time reference >> 2019-03-14 15:56:10.819785 | ubuntu-bionic | >> >> Also, local run of tox py27 and py35 both passed. >> >> Anybody knows what's going wrong? Any fix is in progress? > As of roughly 22:00 UTC (on Wednesday, March 13), the default > nodeset in the opendev/base-jobs repository was updated from > ubuntu-xenial (16.04 LTS) to ubuntu-bionic (18.04 LTS). > > In the case of the sysinv-tox-py35 job you almost certainly need to > set an explicit "nodeset: ubuntu-xenial" so that it runs on a > platform with actually provides a Python 3.5 interpreter > (ubuntu-bionic only provides 3.6 and 3.7). > > For the sysinv-tox-py27 psycopg2 error above, it looks like it's > attempting to use a libresolv build which references symbols from a > different libc. Are you maybe installing bundled libraries > previously built on an ubuntu-xenial node? > [AN]: As developer I don't install anything, I submit my source code changes to gerrit as review, and Zuul is triggered to run to verify if my change break tox. Where tox runs the tests and what its environment like is transparent to (as least for me until now :)). So I'm not sure how I could do what you suggest. > > _______________________________________________ > 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 dtroyer at gmail.com Thu Mar 14 21:16:25 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Thu, 14 Mar 2019 16:16:25 -0500 Subject: [Starlingx-discuss] Contrib or Experimental tools location ?? In-Reply-To: <48a4e21c-25ad-04ad-dba6-1abeba14cd07@linux.intel.com> References: <48a4e21c-25ad-04ad-dba6-1abeba14cd07@linux.intel.com> Message-ID: On Wed, Mar 13, 2019 at 9:59 PM Saul Wold wrote: > We are likely going have more contributions that fall into experimental > that the community may want to try. > > Should we have a contrib or experimental repo or subdirectory in > stx-tools for these contributions? My experience with this sort of thing is over time they bit-rot and are slowly, if at all, updated, much like many wikis. There is also a perception of blessing by the project when hosted in project-controlled places, be it a git repo or a subdirectory within another project.[0] The bar for anyone to host their own workspaces publicly is fantastically low these days, with Github, Gitlab, BitBucket and friends all available for free. I see that discovery is one of the issues here, we could host a directory of these repos centrally (wiki page?). What is the benefit of placing arbitrary code into a StarlingX repo over a personal Github account + having a directory listing these personal repos? I see a benefit in the legitimization that putting it under an stx repo gives (this one of my concerns), what are the other benefits? I would feel much better about doing this in an stx repo if the core group (there will be a limited group of people with merge permissions here, yes?) has the responsibility to curate the content of a contrib repo. dt [0] We have already seen this ourselves around some of the scripts in stx-tools/deployment that were put there for a specific purpose and users discovered them and expected them to be supported. -- Dean Troyer dtroyer at gmail.com From fungi at yuggoth.org Thu Mar 14 21:16:37 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 14 Mar 2019 21:16:37 +0000 Subject: [Starlingx-discuss] [Zuul] failure on review in stx-config project In-Reply-To: <20190314200235.oksm642vn33nq5hi@yuggoth.org> References: <20190314200235.oksm642vn33nq5hi@yuggoth.org> Message-ID: <20190314211636.dzeoebeyq52zevwm@yuggoth.org> On 2019-03-14 20:02:36 +0000 (+0000), Jeremy Stanley wrote: [...] > For the sysinv-tox-py27 psycopg2 error above, it looks like it's > attempting to use a libresolv build which references symbols from a > different libc. Are you maybe installing bundled libraries > previously built on an ubuntu-xenial node? After a bit more digging this seems to be https://github.com/psycopg/psycopg2-wheels/issues/2 which can be remedied by upgrading the version of psycopg2 you're using or by setting that job to also use an ubuntu-xenial nodeset for now. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From dtroyer at gmail.com Thu Mar 14 21:21:16 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Thu, 14 Mar 2019 16:21:16 -0500 Subject: [Starlingx-discuss] [Zuul] failure on review in stx-config project In-Reply-To: <5057dc09-fbaa-dd31-56eb-5309408cf619@windriver.com> References: <20190314200235.oksm642vn33nq5hi@yuggoth.org> <5057dc09-fbaa-dd31-56eb-5309408cf619@windriver.com> Message-ID: On Thu, Mar 14, 2019 at 3:58 PM Andy Ning wrote: > [AN]: As developer I don't install anything, I submit my source code changes to gerrit as review, and Zuul is triggered to run to verify if my change break tox. Where tox runs the tests and what its environment like is transparent to (as least for me until now :)). So I'm not sure how I could do what you suggest. Andy, I am working through the STX repos to clean up some of these py35 things following the bionic update upstream. As Jeremy points out, there are two issues at play here, running on xenial will work around both, and I will start pushing that out. dt -- Dean Troyer dtroyer at gmail.com From fungi at yuggoth.org Thu Mar 14 21:23:02 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 14 Mar 2019 21:23:02 +0000 Subject: [Starlingx-discuss] [Zuul] failure on review in stx-config project In-Reply-To: <5057dc09-fbaa-dd31-56eb-5309408cf619@windriver.com> References: <20190314200235.oksm642vn33nq5hi@yuggoth.org> <5057dc09-fbaa-dd31-56eb-5309408cf619@windriver.com> Message-ID: <20190314212302.gpyplg7kuqqo5jax@yuggoth.org> On 2019-03-14 16:57:09 -0400 (-0400), Andy Ning wrote: [...] > [AN]: As developer I don't install anything, I submit my source code changes > to gerrit as review, and Zuul is triggered to run to verify if my change > break tox. Where tox runs the tests and what its environment like is > transparent to (as least for me until now :)). So I'm not sure how I could > do what you suggest. By "you" in this case I meant developers on StarlingX. Your CI jobs should absolutely not be a black box to you, especially since the job in question is defined in your repository: http://git.starlingx.io/cgit/stx-config/tree/.zuul.yaml#n66 Just a matter of adding "nodeset: ubuntu-xenial" to that job definition. The change which adds it should be self-testing so you'll be able to see in the CI results whether it worked or not. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From Ghada.Khalil at windriver.com Thu Mar 14 22:24:28 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 14 Mar 2019 22:24:28 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - March 14/2019 Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4CDDCB@ALA-MBD.corp.ad.wrs.com> Thank you to all who attended the release sub-project meeting today. Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Meeting Agenda/Notes - March 14/2019 Goals for the meeting: - Ghada: Review the overall status of the release -- item-by-item as well as overall - Acknowledge whether the current dates are achievable - If not, work on a plan to revise the release dates - Bruce: There are people waiting for this release. There is interest by one party to deploy StarlingX as an edge device. - We need to set a high bar for ourselves - We need to have a stable release with the required content - Bill: What is the critical path? Which items need more attention and how can we bring focus to these items? Current Dates - MS-3: Apr 8-12 2019 / RC1: Apr 29-May 3 2019 / Release: May 20-24 2019 - Countdown to MS-3 is 4wks Green -- On Track / Non-Blocking Items - CVE Upgrades - CentOS upgrade to 7.6 - Kernel and user-space packages have merged as of March 11 - ovs-dpdk upversion is in progress: some issues to work through, but we feel this can make it - Python3 Readiness - Prep. Not gating the StarlingX release schedule. - Integrate Containerized OVS - On track; this should be ready before the current MS-3 - Non-Openstack Patch Backlog Reduction - Best effort; does not gate the StarlingX release schedule - Openstack Rebase - Most components have been rebased. - Final item is to complete the rebase of horizon, keystone, Barbican on the host. Fcst: March 30 - Green for milestone-3 - DevStack Enablement - Not gating the StarlingX release schedule - OVS-DPDK Enhancements - Small enhancements; this should be ready before the current MS-3 Yellow -- Watch List - Documentation - 35 stories in play. Not fully staffed currently. Need more community help to land this. - Still working more detailed plans. - On watch to determine what is the minimal set required for the release (need to focus on resourcing those items) and what can come after - Anisble bootstrap Deployment - Preliminary code is available, but facing issues in testing. - Status is yellow relative to the current MS-3 - Anchor feature - Ceph Upgrade - Need an update from Cindy, but it feels like this is about 1wk past the current forecast (Apr 5), so pushes against the current MS-3 date. Red -- Won't Make the current dates - Containers - Anchor Feature -- holds up the release - 28 stories still open - Frank currently working story-by-story on a new forecast - Action: Frank - Plan to have a new plan/forecast by March 22 - Distributed Cloud - Anchor Feature -- holds up the release - Direct dependency on containers. Got impacted by a late start due to the containers cut-over. - With the containers cut-over done, we now are able to make progress. Dependency is finish-to-finish now. - Action: Dariush - Plan to have a new plan/forecast by March 22 - Distro Openstack Patch Elimination - Anchor Feature -- holds up the release - Policy is to upstream to train first, then backport to StarlingX - Still need to work out timing/plan in terms of reviews being posted and stable - Need to decide the key items the StarlingX release should be gated on - Action: Bruce to figure out plan proposal - Not confident we can have a full plan by next week, but will work towards a clearer view - especially around the gating items Test Readiness - Test Case Definition is on track - Feature Testing (Execution) - Action: Ada/Numan to update each feature on the release plan with the "Feature Tested" date. - For Features where are the dates are being re-worked, wait until next week when a new date is available - Regression Testing (Execution) - Original plan has release regression starting next week - However, with the shift in a number of key features, this plan needs to be re-examined - Options: (1) Delay regression start. (2) Start reduced regression now, but plan another regression cycle when anchor features are ready. Bug Resolution - Review in next meeting - Need to make sure the new dates provide adequate time for bug resolution. Conclusion: - Current MS-3 is highly unlikely >> knock-on effect to the subsequent release milestones as well - Next week we will work on proposal for the new date based on revised plans for the above items Regards, Ghada From vm.rod25 at gmail.com Thu Mar 14 23:13:24 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Thu, 14 Mar 2019 17:13:24 -0600 Subject: [Starlingx-discuss] [Multi-OS] Update of POC: Building basic STX components in Ubuntu Message-ID: Hello everybody out there using/building Starling X - This is our first update of the progress we have done on the Multi-OS project. During the last couple of weeks, we have been working on this POC of a build system for STX on top of Ubuntu images. This is the git repository ( branch poc_ubuntu ) where you can try it: https://github.com/VictorRodriguez/stx-packaging/tree/poc_ubuntu The provided instructions ( also example videos ) will guide you through the build of Debian base packages for components such as fm-common, fm mgr, kernel, horizon and others ones that you might want to add to your image ( like bc for a basic example). Please let us know your feedback, we will do a live demo on next build meeting. Hope you like it. Victor R and Multi-OS STX team From ada.cabrales at intel.com Thu Mar 14 23:50:19 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Thu, 14 Mar 2019 23:50:19 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - March 14/2019 Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CDAB6FD@FMSMSX114.amr.corp.intel.com> Please take a look at my comments below, regarding testing. A. > -----Original Message----- > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Thursday, March 14, 2019 4:24 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - March 14/2019 > > > Thank you to all who attended the release sub-project meeting today. > > Agenda/Minutes are posted at: > https://etherpad.openstack.org/p/stx-releases > > Release Meeting Agenda/Notes - March 14/2019 Goals for the meeting: > - Ghada: Review the overall status of the release -- item-by-item as well as > overall > - Acknowledge whether the current dates are achievable > - If not, work on a plan to revise the release dates > - Bruce: There are people waiting for this release. There is interest by one party > to deploy StarlingX as an edge device. > - We need to set a high bar for ourselves > - We need to have a stable release with the required content > - Bill: What is the critical path? Which items need more attention and how can > we bring focus to these items? > > Current Dates > - MS-3: Apr 8-12 2019 / RC1: Apr 29-May 3 2019 / Release: May 20-24 2019 > - Countdown to MS-3 is 4wks > > Green -- On Track / Non-Blocking Items > - CVE Upgrades > - CentOS upgrade to 7.6 > - Kernel and user-space packages have merged as of March 11 > - ovs-dpdk upversion is in progress: some issues to work through, but we feel > this can make it > - Python3 Readiness > - Prep. Not gating the StarlingX release schedule. > - Integrate Containerized OVS > - On track; this should be ready before the current MS-3 > - Non-Openstack Patch Backlog Reduction > - Best effort; does not gate the StarlingX release schedule > - Openstack Rebase > - Most components have been rebased. > - Final item is to complete the rebase of horizon, keystone, Barbican on the > host. Fcst: March 30 > - Green for milestone-3 > - DevStack Enablement > - Not gating the StarlingX release schedule > - OVS-DPDK Enhancements > - Small enhancements; this should be ready before the current MS-3 > > Yellow -- Watch List > - Documentation > - 35 stories in play. Not fully staffed currently. Need more community help to > land this. > - Still working more detailed plans. > - On watch to determine what is the minimal set required for the release > (need to focus on resourcing those items) and what can come after > - Anisble bootstrap Deployment > - Preliminary code is available, but facing issues in testing. > - Status is yellow relative to the current MS-3 > - Anchor feature > - Ceph Upgrade > - Need an update from Cindy, but it feels like this is about 1wk past the current > forecast (Apr 5), so pushes against the current MS-3 date. > > Red -- Won't Make the current dates > - Containers > - Anchor Feature -- holds up the release > - 28 stories still open > - Frank currently working story-by-story on a new forecast > - Action: Frank - Plan to have a new plan/forecast by March 22 > - Distributed Cloud > - Anchor Feature -- holds up the release > - Direct dependency on containers. Got impacted by a late start due to the > containers cut-over. > - With the containers cut-over done, we now are able to make progress. > Dependency is finish-to-finish now. > - Action: Dariush - Plan to have a new plan/forecast by March 22 > - Distro Openstack Patch Elimination > - Anchor Feature -- holds up the release > - Policy is to upstream to train first, then backport to StarlingX > - Still need to work out timing/plan in terms of reviews being posted and > stable > - Need to decide the key items the StarlingX release should be gated on > - Action: Bruce to figure out plan proposal > - Not confident we can have a full plan by next week, but will work > towards a clearer view - especially around the gating items > > Test Readiness > - Test Case Definition is on track > - Feature Testing (Execution) > - Action: Ada/Numan to update each feature on the release plan with the > "Feature Tested" date. > - For Features where are the dates are being re-worked, wait until next week > when a new date is available > - Regression Testing (Execution) > - Original plan has release regression starting next week > - However, with the shift in a number of key features, this plan needs to be re- > examined > - Options: (1) Delay regression start. (2) Start reduced regression now, but > plan another regression cycle when anchor features are ready. > Based on the stability of the release, I suggest to delay the beginning of regression testing. We haven't had a green sanity since 03/05. We can re-define a date when we have clarity on the delivery of the key features, and continue running Sanity meanwhile. > Bug Resolution > - Review in next meeting > - Need to make sure the new dates provide adequate time for bug resolution. > > Conclusion: > - Current MS-3 is highly unlikely >> knock-on effect to the subsequent release > milestones as well > - Next week we will work on proposal for the new date based on revised plans > for the above items > > > Regards, > Ghada > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From maria.g.perez.ibarra at intel.com Fri Mar 15 02:32:03 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Fri, 15 Mar 2019 02:32:03 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190314 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Mar-14 (link) Status : YELLOW =================== Virtual environment =================== Simplex: Setup 04 TCs [PASS] Provision-Containers 01 TCs [PASS] Sanity-OpenStack 49 TCs [PASS] Sanity-Platform 07 TCs [PASS] TOTAL: [61 TCs PASS] ------------------------------ Duplex: Setup 04 TCs [PASS] Provision-Containers 01 TCs [PASS] Sanity-OpenStack 52 TCs [PASS] | 8 TCs [FAIL] Sanity-Platform 05 TCs [PASS] TOTAL: 62 TCs [54 PASS | 8-FAIL] ====================== Bare Metal environment ====================== Simplex: Setup Manual Provision-Containers 01 TCs [PASS] Sanity-OpenStack 49 TCs [PASS] Sanity-Platform 07 TCs [PASS] TOTAL: [57 TCs PASS] ------------------------------ Duplex: Setup Manual Provision-Containers 01 TCs [PASS] Sanity-OpenStack 52 TCs [PASS] Sanity-Platform 05 TCs [PASS] | 2 TCs [FAIL] TOTAL: 58 TCs [56-PASS | 2-FAIL] Several issue were found during application-apply process. Most likely to be related with external networking. Will confirm in next build. ------------------------------------------------------------------ This is the list of test cases executed: https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mingyuan.qi at intel.com Fri Mar 15 06:34:00 2019 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Fri, 15 Mar 2019 06:34:00 +0000 Subject: [Starlingx-discuss] [Container] Ironic service containerization In-Reply-To: <7A22CC1A-C578-4A4A-AD08-0F62C682FD9B@windriver.com> References: <7A22CC1A-C578-4A4A-AD08-0F62C682FD9B@windriver.com> Message-ID: Hi Greg, My understanding for your questions. - [Greg] Do we want Ironic to be an OPTIONAL service in StarlingX ? [Mingyuan] I’m going to add ironic to stx-openstack and enable it by node label, as Brent said. - [Greg] Where do we want Ironic Conductor running ? [Mingyuan] I suppose ironic is running on controllers since ipmi connects to oam network. - [Greg] Is it possible to have an HA deployment of Ironic Conductor in vanilla upstream ironic ? [Mingyuan] ironic conductor HA is supported in vanilla upstream ironic, ironic conductor pod will run on both controllers. I need further investigation of this. Ø “There can be multiple instances of the conductor service to support various class of drivers and also to manage fail over. Instances of the conductor service should be on separate nodes.” Ø https://docs.openstack.org/ironic/latest/install/get_started.html#deployment-architecture - [Greg] How do we set it up such that system can manage both VM Instances and Bare Metal Instances ? will/can these be setup as part of starlingx system overrides ? [Mingyuan] Sounds good with host aggregate. For overrides, let me figure this out. - [Greg] I don’t understand why doing testing of ironic on hardware will take a long time. [Mingyuan] Bare metal deployment manually of starlingx usually takes more time than that in vm. In addition, to test functionality of ironic, more ironic nodes are needed for installing tenant instances, which obviously takes more time than installing the vm instances. Mingyuan From: Waines, Greg [mailto:Greg.Waines at windriver.com] Sent: Thursday, March 14, 2019 20:56 To: Qi, Mingyuan ; starlingx-discuss at lists.starlingx.io Cc: Rowsell, Brent ; Miller, Frank ; Xie, Cindy ; An, Ran1 Subject: Re: [Container] Ironic service containerization In-lined comments, Greg. From: "Qi, Mingyuan" > Date: Thursday, March 14, 2019 at 4:45 AM To: "starlingx-discuss at lists.starlingx.io" > Cc: "Rowsell, Brent" >, "Miller, Frank" >, Greg Waines >, "Xie, Cindy" >, "An, Ran1" > Subject: [Container] Ironic service containerization Hi folks, I’m starting the story of containerize ironic service, I’d like to add below tasks to story https://storyboard.openstack.org/#!/story/2004760 in order to enable ironic service. * Add ironic chart to stx-openstack armada manifest. [Greg] Do we want Ironic to be an OPTIONAL service in StarlingX ? My initial thoughts are yes ... thinking most StarlingX deployments will not use it, so for utilization reasons it would be better not to even run it. So if we are making Ironic OPTIONAL and disabled by default, how is this achieved ? e.g. - does it have a separate stx-ironic-openstack armada manifest ? OR - Is it included in the stx-openstack armada manifest and somehow(?) disabled by default, and can be enabled thru helm-overrides ? Add ironic chart values to armada manifest as well as static configuration. * Generate ironic overrides Generate dynamic configuration in sysinv for ironic. [Greg] As part of this work I think it would be good to understand (and review with starlingx cores): - Where do we want Ironic Conductor running ? Controller or Compute ? Do we have a choice in vanilla upstream ironic ? - Is it possible to have an HA deployment of Ironic Conductor in vanilla upstream ironic ? - How do we set it up such that system can manage both VM Instances and Bare Metal Instances ? i.e. I believe this is done thru host aggregates ? will/can these be setup as part of starlingx system overrides ? Greg. * Enable ironic service Adding ironic chart to armada chart group to switch on ironic service for stx-openstack application. Should this be default in stx-openstack armada manifest? * Cleanup ironic in sysinv and puppet I’m not sure whether to add this task here or to a specific openstack component cleanup story. And speaking of the test, the first choice is to deploy starlingx standard config on bare metal because of the connection to ipmi, but it will take long time for testing. Did anyone get the chance to have ipmi/BMC enabled in vm (or it’s not possible)? Best Regards, Mingyuan -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.ning at windriver.com Fri Mar 15 13:26:55 2019 From: andy.ning at windriver.com (Andy Ning) Date: Fri, 15 Mar 2019 09:26:55 -0400 Subject: [Starlingx-discuss] [Zuul] failure on review in stx-config project In-Reply-To: <20190314212302.gpyplg7kuqqo5jax@yuggoth.org> References: <20190314200235.oksm642vn33nq5hi@yuggoth.org> <5057dc09-fbaa-dd31-56eb-5309408cf619@windriver.com> <20190314212302.gpyplg7kuqqo5jax@yuggoth.org> Message-ID: On 2019-03-14 05:23 PM, Jeremy Stanley wrote: > On 2019-03-14 16:57:09 -0400 (-0400), Andy Ning wrote: > [...] >> [AN]: As developer I don't install anything, I submit my source code changes >> to gerrit as review, and Zuul is triggered to run to verify if my change >> break tox. Where tox runs the tests and what its environment like is >> transparent to (as least for me until now :)). So I'm not sure how I could >> do what you suggest. > By "you" in this case I meant developers on StarlingX. Your CI jobs > should absolutely not be a black box to you, especially since the > job in question is defined in your repository: > > http://git.starlingx.io/cgit/stx-config/tree/.zuul.yaml#n66 > > Just a matter of adding "nodeset: ubuntu-xenial" to that job > definition. The change which adds it should be self-testing so > you'll be able to see in the CI results whether it worked or not. > Good to know that we can somehow control the job by the .zuul.yaml file. I would think adding a nodeset to the job should be a temporary workaround. Overall I'm not sure we want to specify where a particular job is running (will that be a load balancing issue for Zuul for example?). Plus most of us want to focus on the production code, so hiding Zuul job details may not be a bad idea for developers (maybe that's the reason why .zuul.yaml is hidden file?) In terms of self-testing, I usually run tox locally on our build machine and that works fairly well. Is there a way we can trigger Zuul jobs on our change before we sumit the review? The idea is developers run tox in the same environment as Zuul runs it. Thanks, Andy > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Andy Ning Cube: 3071 Tel: 613-9631408 (int: 4408) Skype: andy.ning.wr -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Fri Mar 15 13:39:38 2019 From: serverascode at gmail.com (Curtis) Date: Fri, 15 Mar 2019 09:39:38 -0400 Subject: [Starlingx-discuss] Contrib or Experimental tools location ?? In-Reply-To: References: <48a4e21c-25ad-04ad-dba6-1abeba14cd07@linux.intel.com> Message-ID: On Thu, Mar 14, 2019 at 5:17 PM Dean Troyer wrote: > On Wed, Mar 13, 2019 at 9:59 PM Saul Wold wrote: > > We are likely going have more contributions that fall into experimental > > that the community may want to try. > > > > Should we have a contrib or experimental repo or subdirectory in > > stx-tools for these contributions? > > My experience with this sort of thing is over time they bit-rot and > are slowly, if at all, updated, much like many wikis. There is also a > perception of blessing by the project when hosted in > project-controlled places, be it a git repo or a subdirectory within > another project.[0] > > The bar for anyone to host their own workspaces publicly is > fantastically low these days, with Github, Gitlab, BitBucket and > friends all available for free. I see that discovery is one of the > issues here, we could host a directory of these repos centrally (wiki > page?). What is the benefit of placing arbitrary code into a > StarlingX repo over a personal Github account + having a directory > listing these personal repos? I see a benefit in the legitimization > that putting it under an stx repo gives (this one of my concerns), > what are the other benefits? > Ultimately I believe we are arguing different goals with the same points. I'm ok with bit rot, it's inevitable, and can actually be a good thing. I'm ok with code with lower standards being contributed to a place where it can be legitimized. These things are pros to me. :) > > I would feel much better about doing this in an stx repo if the core > group (there will be a limited group of people with merge permissions > here, yes?) has the responsibility to curate the content of a contrib > repo. > There would have to be some standards, eg. no pyc files, no -2s to new contributors, etc. Arbitrary no, curated yes. Thanks, Curtis > > dt > > [0] We have already seen this ourselves around some of the scripts > in stx-tools/deployment that were put there for a specific purpose and > users discovered them and expected them to be supported. > > -- > > 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 > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtroyer at gmail.com Fri Mar 15 13:55:54 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Fri, 15 Mar 2019 08:55:54 -0500 Subject: [Starlingx-discuss] Contrib or Experimental tools location ?? In-Reply-To: References: <48a4e21c-25ad-04ad-dba6-1abeba14cd07@linux.intel.com> Message-ID: On Fri, Mar 15, 2019 at 8:39 AM Curtis wrote: > Ultimately I believe we are arguing different goals with the same points. > > I'm ok with bit rot, it's inevitable, and can actually be a good thing. I'm ok with code with lower standards being contributed to a place where it can be legitimized. > > These things are pros to me. :) I am not against having a place for unofficial code to go and rot, I am against it being associated with the StarlingX name in a way that drags down the perception of the code we produce. And that is all we produce in the end, code in repositories. > There would have to be some standards, eg. no pyc files, no -2s to new contributors, etc. Arbitrary no, curated yes. To me 'curated' includes vetting suitability for purpose. Untested code is broken code. I would support a repo in github.com/starlingx-staging or an index anywhere but not a repo in Gerrit without meeting a certain minimum of quality and accountability. dt -- Dean Troyer dtroyer at gmail.com From Numan.Waheed at windriver.com Wed Mar 13 15:45:07 2019 From: Numan.Waheed at windriver.com (Waheed, Numan) Date: Wed, 13 Mar 2019 15:45:07 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> Message-ID: <3CAA827B7A79BA46B15B280EC82088FE4828EF32@ALA-MBD.corp.ad.wrs.com> We have not seen https://bugs.launchpad.net/starlingx/+bug/1819031 issue in other labs (AIO-SX, AIO-DX and Multi-node with storage). We have successful VM connectivity in 20190305T060000Z build. Thanks, Numan. From: Khalil, Ghada Sent: March-11-19 10:52 AM To: Xu, Chenjie ; Xie, Cindy ; Zhao, Forrest ; Peters, Matt ; Richard, Joseph ; Winnicki, Chris ; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio ; Cabrales, Ada ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing To answer Forrest's question: Do you know if OVS/DPDK has been tested after cut-over to container? I have seen Green sanity reports from Ada's team since the cut-over. I expect this covers basic ovs-dpdk functional testing. Ada, please correct me if I am wrong. Regarding https://bugs.launchpad.net/starlingx/+bug/1819031, we've requested information from the reporter on how reproducible this issue is. As far as I know, it was reported on one system only. We're waiting for more information from Peng. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Monday, March 11, 2019 10:40 AM To: Xie, Cindy; Zhao, Forrest; Peters, Matt; Richard, Joseph; Khalil, Ghada; Winnicki, Chris; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, Thank you for your information! The following issue is not exactly the same as mine: https://bugs.launchpad.net/starlingx/+bug/1819031 In this issue, the DHCP works and external network can reach the VMs. However in my case, VMs can't get IP from DHCP and external network can't reach VMs even with an IP allocated by myself. Best Regards, Xu, Chenjie From: Xie, Cindy Sent: Monday, March 11, 2019 10:05 PM To: Zhao, Forrest >; Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can't get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can't ping each other. The DHCP exists and VMs can't ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris's guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don't believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don't know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I'm trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I'm responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don't know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing "system host-unlock compute-0", it will report "Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address". But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Wed Mar 13 22:36:29 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 13 Mar 2019 22:36:29 +0000 Subject: [Starlingx-discuss] FW: Distro.openstack meeting notes Mar 12th 2019 In-Reply-To: <15E77730-1BCD-47FA-A598-9DDA186DD094@99cloud.net> References: <9A85D2917C58154C960D95352B22818BD06FCD2B@fmsmsx123.amr.corp.intel.com> <8EA56FFE-EC7B-442A-A95E-B5D0156DD236@99cloud.net> <15E77730-1BCD-47FA-A598-9DDA186DD094@99cloud.net> Message-ID: <9A85D2917C58154C960D95352B22818BD06FE61C@fmsmsx123.amr.corp.intel.com> Here is an update on 99Cloud’s work on OpenStack patch upstreaming. The master spreadsheet has been updated to reflect this update. They are requesting help on a couple of the line items: Line 27 primary: server-groups best-effort and group size: Server group soft-affinity is achieved in pike version, why not to use it but to develop the best-effort? And what is the server group size used for, I can't think about a necessary scene to finish the spec. Line 37 Configurable auto page refresh: Can someone (@Dean, @Frank) send the un-squashed patches to Shuquan please? brucej From: Shuquan Huang [mailto:huang.shuquan at 99cloud.net] Sent: Wednesday, March 13, 2019 1:59 AM To: Jones, Bruce E Cc: 王亚 ; 朱博祥 ; 张鲲鹏 Subject: Re: [Starlingx-discuss] Distro.openstack meeting notes Mar 12th 2019 Hi Bruce, This is the updated from 99Cloud. 6 vCPU model Ya Wang Because the feature is frozen, this spec has to be deferred to the train release. Last week I submit two patches into review system, the main work was refactor part of libvirt driver’s code and add a public method in scheduler utils to get flavor traits. Now the review is pause because we have to wait for re-proposed spec merged. The spec has one +2. Code: https://review.openstack.org/#/c/637834/ Spec: https://review.openstack.org/#/c/642030/ 20 rbd disks: convert from source format to raw Intel to fix upstram Boxiang Zhu Last week, Matthew suggested to remove the LVM related changes out of the patch. He thought that it might be easier to split it into a separate follow-up patch, as this is the change that will require a release note. Therefore, I have split it into two patches. And I also added some unit tests and improved the release notes. Just ready for review. I will ping Matthew and some other nova core reviewers to review the patch. Code1: https://review.openstack.org/#/c/640271/ Code2: https://review.openstack.org/#/c/642667/ 23 Do not bypass scheduler when using forced hosts Boxiang Zhu I have pushed a patch to the review system. But it still need more time to discuss with nova community to find whether it is suitable. Code: https://review.openstack.org/#/c/641908/ 25 Live block migration fails following auth token expiration Ya Wang The bug has been solved and I’ve verified it. On the other hand, I’ve submit a patch to update the nova’s document. The reason for the previous failure is because the service user's role does not match the config item: service_token_roles which is not clear in the document. Code: https://review.openstack.org/#/c/542008/ 26 Drop support for forced hosts for live migrate Boxiang Zhu The bug has been solved and I’ve verified it. The nova community has the same bp like 'remove-force-flag-from-live-migrate-and-evacuate'. The bp adds a micro version(named as 2.68) of api to remove the force flag. I have test the function by myself. And it will not accept the force flag if I specify the os-compute-api-version is 2.68. So I think the bp completely meets our requirements. Code: https://review.openstack.org/#/c/634600/ 27 Unsquash: primary: server-groups best-effort and group size Kupeng Zhang This patch contains two features, best-effort server group and group size. The best-effort feature is similar to soft-affinity/soft-anti-affinity of server group in nova community, and the group size is a new feature which need to submit a spec. We are discussing how to work for them. There are two questions to ask. Server group soft-affinity is achieved in pike version, why not to use it but to develop the best-effort? And what is the server group size used for, I can't think about a necessary scene to finish the spec. 37 Configurable Auto Page Refresh Kupeng Zhang I can’t get the patch from the link in the excel. It’s inside the intel github. Could you send this to us? Intel github: https://github.intel.com/Madawaska/patch-review/blob/master/horizon/0001-ENG-Openstack-rebase-to-Pike-Part-2.patch On Mar 12, 2019, at 10:24 PM, Shuquan Huang > wrote: Sorry, I didn’t notice it shifts to PDT. I’ll summary the progress from my side and send it out tomorrow. On Mar 12, 2019, at 10:21 PM, Jones, Bruce E > wrote: It’s over. All meetings shifted one hour earlier due to the US/Canada time change. From: Shuquan Huang [mailto:huang.shuquan at 99cloud.net] Sent: Tuesday, March 12, 2019 7:08 AM To: Jones, Bruce E > Subject: Re: [Starlingx-discuss] Distro.openstack meeting notes Mar 12th 2019 Hi Bruce, It seems I can’t join the meeting. It shows “The host has another meeting in progress” Is the meeting rescheduled? From: > on behalf of "Jones, Bruce E" > Date: Tuesday, March 12, 2019 at 9:55 PM To: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] Distro.openstack meeting notes Mar 12th 2019 Meeting agenda and notes for the 3/12 meeting • Good news - Neutron network segment range patches in (except lib) • Bad news - NUMA topology pushed out. • We believe we will have to carry forks of at least some of the Nova changes * We also believe anything committed to Nova is deployable (and will remain so as per Matt R). * We should implement the "upstream first" and "stable branch" concept and backport critical features and features from Train to our release branch • Changes that are absolutely critical should be backported before they are accepted (and updated over time until acceptance). • We should help fix things upstream as we find issues with Train "work in progress" patches * Meanwhile we will continuously update our master from OpenStack master • AR Bruce and Frank - need a plan for upstream contributions for Nova • We need to define our branching strategy. Create an f/stx-stein branch? Create a f/nova feature branch for StarlingX? * We will need to build our Nova container out of the github staging trees - once Nova cuts there first RC (Mar 22nd). Backports will be checked into github directly. • Plan to raise these issues with Nova community at PTG and support the efforts • Review updates: https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit?ts=5c1933cc#gid=0 • Review LP issues: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss 黄舒泉 Shuquan Huang 技术总监 Technical Director 九州云信息科技有限公司 99Cloud Co. Ltd. 邮箱(Email): huang.shuquan at 99cloud.net 手机(Mobile): +86-18616211612 电话(Tel): 021-61207665 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From chenjie.xu at intel.com Thu Mar 14 16:23:19 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Thu, 14 Mar 2019 16:23:19 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <3CAA827B7A79BA46B15B280EC82088FE4828EF32@ALA-MBD.corp.ad.wrs.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <3CAA827B7A79BA46B15B280EC82088FE4828EF32@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Bruce/Ghada, We suspect that the some steps are missing in the following guide: https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnStandard According to Numan, they have verified the VM connectivity in 20190305T060000Z build. Thus the ISO image should be fine. Cindy team provided 2 versions of ISO images and I have tested the first version last week. The first version works correctly and thus hardware of my environment should be fine. Based on above analysis, we suspect that the some steps are missing in the guide. We have been blocked by this issue for several days. If somebody can review the guide and provide some comments, it will be pretty good. Best Regards, Xu, Chenjie From: Waheed, Numan [mailto:Numan.Waheed at windriver.com] Sent: Wednesday, March 13, 2019 11:45 PM To: Khalil, Ghada ; Xu, Chenjie ; Xie, Cindy ; Zhao, Forrest ; Peters, Matt ; Richard, Joseph ; Winnicki, Chris ; Lin, Shuicheng ; Peng, Peng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio ; Cabrales, Ada ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing We have not seen https://bugs.launchpad.net/starlingx/+bug/1819031 issue in other labs (AIO-SX, AIO-DX and Multi-node with storage). We have successful VM connectivity in 20190305T060000Z build. Thanks, Numan. From: Khalil, Ghada > Sent: March-11-19 10:52 AM To: Xu, Chenjie >; Xie, Cindy >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing To answer Forrest's question: Do you know if OVS/DPDK has been tested after cut-over to container? I have seen Green sanity reports from Ada's team since the cut-over. I expect this covers basic ovs-dpdk functional testing. Ada, please correct me if I am wrong. Regarding https://bugs.launchpad.net/starlingx/+bug/1819031, we've requested information from the reporter on how reproducible this issue is. As far as I know, it was reported on one system only. We're waiting for more information from Peng. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Monday, March 11, 2019 10:40 AM To: Xie, Cindy; Zhao, Forrest; Peters, Matt; Richard, Joseph; Khalil, Ghada; Winnicki, Chris; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, Thank you for your information! The following issue is not exactly the same as mine: https://bugs.launchpad.net/starlingx/+bug/1819031 In this issue, the DHCP works and external network can reach the VMs. However in my case, VMs can't get IP from DHCP and external network can't reach VMs even with an IP allocated by myself. Best Regards, Xu, Chenjie From: Xie, Cindy Sent: Monday, March 11, 2019 10:05 PM To: Zhao, Forrest >; Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can't get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can't ping each other. The DHCP exists and VMs can't ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris's guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don't believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don't know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I'm trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I'm responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don't know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing "system host-unlock compute-0", it will report "Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address". But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From elio.martinez.monroy at intel.com Thu Mar 14 17:51:11 2019 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Thu, 14 Mar 2019 17:51:11 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <3CAA827B7A79BA46B15B280EC82088FE4828EF32@ALA-MBD.corp.ad.wrs.com> Message-ID: <1466AF2176E6F040BD63860D0A241BBD46CA1793@FMSMSX109.amr.corp.intel.com> Adding Richo, We will try to investigate a little bit deeper inside this problem, he is going to be deploying in Bare metal , while I will try on virtual. In which part is failing for you? BR Elio From: Xu, Chenjie Sent: Thursday, March 14, 2019 10:23 AM To: Jones, Bruce E ; Waheed, Numan ; Khalil, Ghada ; Xie, Cindy ; Zhao, Forrest ; Peters, Matt ; Richard, Joseph ; Winnicki, Chris ; Lin, Shuicheng ; Peng, Peng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio ; Cabrales, Ada ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Bruce/Ghada, We suspect that the some steps are missing in the following guide: https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnStandard According to Numan, they have verified the VM connectivity in 20190305T060000Z build. Thus the ISO image should be fine. Cindy team provided 2 versions of ISO images and I have tested the first version last week. The first version works correctly and thus hardware of my environment should be fine. Based on above analysis, we suspect that the some steps are missing in the guide. We have been blocked by this issue for several days. If somebody can review the guide and provide some comments, it will be pretty good. Best Regards, Xu, Chenjie From: Waheed, Numan [mailto:Numan.Waheed at windriver.com] Sent: Wednesday, March 13, 2019 11:45 PM To: Khalil, Ghada >; Xu, Chenjie >; Xie, Cindy >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing We have not seen https://bugs.launchpad.net/starlingx/+bug/1819031 issue in other labs (AIO-SX, AIO-DX and Multi-node with storage). We have successful VM connectivity in 20190305T060000Z build. Thanks, Numan. From: Khalil, Ghada > Sent: March-11-19 10:52 AM To: Xu, Chenjie >; Xie, Cindy >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing To answer Forrest's question: Do you know if OVS/DPDK has been tested after cut-over to container? I have seen Green sanity reports from Ada's team since the cut-over. I expect this covers basic ovs-dpdk functional testing. Ada, please correct me if I am wrong. Regarding https://bugs.launchpad.net/starlingx/+bug/1819031, we've requested information from the reporter on how reproducible this issue is. As far as I know, it was reported on one system only. We're waiting for more information from Peng. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Monday, March 11, 2019 10:40 AM To: Xie, Cindy; Zhao, Forrest; Peters, Matt; Richard, Joseph; Khalil, Ghada; Winnicki, Chris; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, Thank you for your information! The following issue is not exactly the same as mine: https://bugs.launchpad.net/starlingx/+bug/1819031 In this issue, the DHCP works and external network can reach the VMs. However in my case, VMs can't get IP from DHCP and external network can't reach VMs even with an IP allocated by myself. Best Regards, Xu, Chenjie From: Xie, Cindy Sent: Monday, March 11, 2019 10:05 PM To: Zhao, Forrest >; Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can't get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can't ping each other. The DHCP exists and VMs can't ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris's guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don't believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don't know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I'm trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I'm responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don't know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing "system host-unlock compute-0", it will report "Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address". But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Fri Mar 15 15:06:24 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Fri, 15 Mar 2019 15:06:24 +0000 Subject: [Starlingx-discuss] [Zuul] failure on review in stx-config project In-Reply-To: References: <20190314200235.oksm642vn33nq5hi@yuggoth.org> <5057dc09-fbaa-dd31-56eb-5309408cf619@windriver.com> <20190314212302.gpyplg7kuqqo5jax@yuggoth.org> Message-ID: <20190315150623.6exsnc2nawnpy4kw@yuggoth.org> On 2019-03-15 09:26:55 -0400 (-0400), Andy Ning wrote: [...] > Good to know that we can somehow control the job by the .zuul.yaml > file. I would think adding a nodeset to the job should be a > temporary workaround. Yes, I think this is what Dean was going to propose for both the jobs you noted. > Overall I'm not sure we want to specify where a particular job is > running (will that be a load balancing issue for Zuul for > example?). The nodeset doesn't specify a location, just what sort of environment should be booted for the system in which the job will be run. Aside from some highly-specialized nodesets we have which are provider-specific or specific to non x86-64 processors, our generic $distro-$release nodesets can be booted in any of our Nodepool providers. > Plus most of us want to focus on the production code, so hiding > Zuul job details may not be a bad idea for developers (maybe > that's the reason why .zuul.yaml is hidden file?) Zuul will load[0] zuul.yaml or zuul.d/*.yaml with or without a leading '.' so it's not an architectural choice to make those files hidden, and they can be renamed to remove the leading '.' in the file or directory name with no change in behavior. The goal with Zuul is that your job definitions are part of your repository so they can be available to anyone to inspect and alter (and with a few security-related exceptions, will even run speculatively on proposed alterations to those configuration files so they can be proven to work before they're merged). > In terms of self-testing, I usually run tox locally on our build > machine and that works fairly well. Is there a way we can trigger > Zuul jobs on our change before we sumit the review? The idea is > developers run tox in the same environment as Zuul runs it. As the errors you raised demonstrate, the details/dependencies of some tests rely strongly on the characteristics of the system on which they're being run. You can of course download[1] the images we build for our test systems and boot one in a virtual machine context or run a script[2] we provide to build one yourself with or without modifications. However, it's not just the images themselves which can affect job characteristics but also the underlying machine, so we provide a breakdown[3] of the most relevant known (and unknown) properties for the providers/flavors we use. At present, exactly replicating every detail of a Zuul job without running Zuul itself is nontrivial, since job definitions are often distributed and components inherited from multiple git repositories. There is some work underway to provide tooling to make this task much easier, but most times it's sufficient for tox-based jobs to just emulate them in an appropriate system (with images described above) by checking out the repository in question, installing any system packages bindep says are missing for its "test" profile, running any additional tools/test-setup.sh script that project provides, and then invoking tox with the desired parameters. That said, if you're looking to have the Zuul service we're operating test your changes before you push them to Gerrit for review, I don't see the point. We standardize on making a "work in progress" option available to all change owners (currently implemented as a -1 vote for the Workflow label) so they can communicate to reviewers that a change is not yet ready to be reviewed. Zuul will still run all configured jobs on such changes and report results back in a review comment just like for any other proposed change. [0] https://zuul-ci.org/docs/zuul/user/config.html#configuration-loading [1] https://nb01.openstack.org/images/ [2] https://opendev.org/openstack-infra/project-config/src/branch/master/tools/build-image.sh [3] https://docs.openstack.org/infra/manual/testing.html -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From cesar.lara at intel.com Fri Mar 15 18:40:42 2019 From: cesar.lara at intel.com (Lara, Cesar) Date: Fri, 15 Mar 2019 18:40:42 +0000 Subject: [Starlingx-discuss] [build] [meetings] MutliOS team meeting 3/18/2019 CANCELLED Message-ID: <2204a126-da40-44e1-ac24-3ba61c5e64a6@intel.com> Team Next Monday is a México holiday, and since most of stakeholders are going to be out of the office I will cancel this occurrence. I will send an update on the activities around this topic Regards Cesar Lara Software Engineering Manager Sent from my mobile phone -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Fri Mar 15 19:22:36 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Fri, 15 Mar 2019 19:22:36 +0000 Subject: [Starlingx-discuss] FW: Distro.openstack meeting notes Mar 12th 2019 In-Reply-To: <9A85D2917C58154C960D95352B22818BD06FE61C@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BD06FCD2B@fmsmsx123.amr.corp.intel.com> <8EA56FFE-EC7B-442A-A95E-B5D0156DD236@99cloud.net> <15E77730-1BCD-47FA-A598-9DDA186DD094@99cloud.net> <9A85D2917C58154C960D95352B22818BD06FE61C@fmsmsx123.amr.corp.intel.com> Message-ID: Shuquan: It is great to see the progress being made by your team. Gerry Kopec has already provided guidance to you for line 27 (only a subset of the patch is intended to be upstreamed). Also Dean provided the unsquashed patches for line 37 yesterday. One suggestion I have for all the nova changes in your list would be for your primes to have a meeting with Gerry since he is familiar with all of the nova high priority bugs in your list. Gerry can answer questions you may have about any of the patches and provide suggestions on what to put in the launchpads that you create. I’ll leave it to you to work out a day and time that works best for both your primes and Gerry. Frank From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, March 13, 2019 6:36 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] FW: Distro.openstack meeting notes Mar 12th 2019 Here is an update on 99Cloud’s work on OpenStack patch upstreaming. The master spreadsheet has been updated to reflect this update. They are requesting help on a couple of the line items: Line 27 primary: server-groups best-effort and group size: Server group soft-affinity is achieved in pike version, why not to use it but to develop the best-effort? And what is the server group size used for, I can't think about a necessary scene to finish the spec. Line 37 Configurable auto page refresh: Can someone (@Dean, @Frank) send the un-squashed patches to Shuquan please? brucej From: Shuquan Huang [mailto:huang.shuquan at 99cloud.net] Sent: Wednesday, March 13, 2019 1:59 AM To: Jones, Bruce E > Cc: 王亚 >; 朱博祥 >; 张鲲鹏 > Subject: Re: [Starlingx-discuss] Distro.openstack meeting notes Mar 12th 2019 Hi Bruce, This is the updated from 99Cloud. -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Fri Mar 15 23:51:26 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Fri, 15 Mar 2019 23:51:26 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190315 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Mar-15 (link) Status : GREEN =================== Virtual environment =================== Simplex: Setup 04 TCs [PASS] Provision-Containers 01 TCs [PASS] Sanity-OpenStack 49 TCs [PASS] Sanity-Platform 07 TCs [PASS] TOTAL: [61 TCs PASS] ------------------------------ Duplex: Setup 04 TCs [PASS] Provision-Containers 01 TCs [PASS] Sanity-OpenStack 52 TCs [PASS] Sanity-Platform 05 TCs [PASS] TOTAL: [62 TCs PASS] ------------------------------ ====================== Bare Metal environment ====================== Simplex: Setup Manual Provision-Containers 01 TCs [PASS] Sanity-OpenStack 49 TCs [PASS] Sanity-Platform 07 TCs [PASS] TOTAL: [57 TCs PASS] ------------------------------ Duplex: Setup Manual Provision-Containers 01 TCs [PASS] Sanity-OpenStack 52 TCs [PASS] Sanity-Platform 05 TCs [PASS] TOTAL: [58 TCs PASS] ------------------------------ Standard Local Storage (2+2): Setup Manual Provision-Containers 01 TCs [PASS] Sanity-OpenStack 52 TCs [PASS] Sanity-Platform 05 TCs [PASS] TOTAL: [58 TCs PASS] ------------------------------ Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From yatindrax.shashi at intel.com Fri Mar 15 17:28:53 2019 From: yatindrax.shashi at intel.com (Shashi, YatindraX) Date: Fri, 15 Mar 2019 17:28:53 +0000 Subject: [Starlingx-discuss] Is Magnum Fully supported for kubernetes cluster in StarlingX 2018.10? Message-ID: Dear Team, Lots of ISVs are interested in deploying StarlingX edge platform and to support them I am trying to see feasibility of kubernetes cluster in starlingX. I am trying to setup kubernetes clusters using Magnum 5.0.1 available in the StarlingX 2018.10. I have downloaded latest 2018.10 ISO image from the StarlingX Mirror repositories. But I am facing multiple issues while enabling the Magnum service and running the commands. Is it supported and tested fully? If it is supported fully then would you please look in the logs and tell me what I am missing. I have attached my Magnum.conf file and current logs of service running: ######################### [wrsroot at controller-0 ~(keystone_admin)]$ magnum service-list ERROR: Invalid input for field 'identity/password/user/password': None is not of type 'string' Failed validating 'type' in schema['properties']['identity']['properties']['password']['properties']['user']['properties']['password']: {'type': 'string'} On instance['identity']['password']['user']['password']: None (HTTP 400) (Request-ID: req-e1fd9612-a616-421f-92a3-2b5ee1f4e5ec) (HTTP 500) (Request-ID: req-38d34547-9fb0-423b-bd33-1dcfa26ada68) [wrsroot at controller-0 ~(keystone_admin)]$ ####### Would you please look on it and let me know. I tried to add details as per the bug reported in the openstack seen in the link https://bugs.launchpad.net/magnum/+bug/1717798 [keystone_authtoken] section of magnum.conf admin_user: magnum admin_password: abcd at 123 admin_tenant_name= services But still no Luck. Would you please tell what could be problem. Mit freundlichen Grüßen, with best regards, Yatindra Shashi Intel Corporation Munich, Germany -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: magnum.conf Type: application/octet-stream Size: 51685 bytes Desc: magnum.conf URL: From chenjie.xu at intel.com Fri Mar 15 18:48:02 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Fri, 15 Mar 2019 18:48:02 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> Message-ID: Hi Matt, We create vhostuser port and VM manually. And the connectivity between manually created VM and br-int works correctly. But the vhostuser port created by StarlingX doesn’t work. Could you please help review our following debugging steps and leave a comment? 1. We manually assigned correct IP to the StarlingX VM’s interface eth0 and ping DHCP server in VM. No packet can be captured by tcpdump and thus we think vhostuser port doesn’t work. Bring up br-int to verify the connectivity: sudo ifconfig br-int 192.168.101.1/24 up Check the IP assigned to the VM: openstack server list Manually assign IP to VM: sudo ifconfig 192.168.101.216/24 up Tcpdump in dhcp namespace: sudo ip netns exec $dhcp_namespace tcpdump –i $tap_device Ping DHCP server in VM: ping 192.168.101.1 No packets can be captured. 2. We added our own vhost user port to br-int and use virsh command and cirros-dpdk-vhostuserclient.xml (you can find in attached files) to create VM: Create vhostuser port: ovs-vsctl add-port br-int vhost-user-1 -- set Interface vhost-user-1 type=dpdkvhostuserclient options:vhost-server-path=/var/run/openvswitch/vhost-user-1 Create VM: virsh create cirros-dpdk-vhostuserclient.xml Bring up br-int to verify the connectivity: sudo ifconfig br-int 192.168.101.1/24 up Manually assign an IP to VM: sudo ifconfig eth0 192.168.101.18/24 up In created VM, ping br-int: ping 192.168.101.1 And the ping succeeds. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 13, 2019 9:13 PM To: Xu, Chenjie ; Khalil, Ghada ; Xie, Cindy ; Zhao, Forrest ; Richard, Joseph ; Winnicki, Chris ; Lin, Shuicheng ; Peng, Peng Cc: 'starlingx-discuss at lists.starlingx.io' ; Martinez Monroy, Elio ; Cabrales, Ada ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello, That message is a normal message from DPDK if you have multiple huge page sizes configured in your system. Openvswitch is configured to use 1G huge pages and will ignore the 2M huge pages. You can confirm this by looking at the Puppet logs to see what was configured and to ensure the 1G huge pages were mounted prior to openvswitch starting. -Matt From: "Xu, Chenjie" > Date: Wednesday, March 13, 2019 at 8:55 AM To: "Peters, Matt" >, Ghada Khalil >, "Xie, Cindy" >, "Zhao, Forrest" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" >, "Peng, Peng" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I installed StarlingX using following the March 5th ISO image and the issue still exists:http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190305T060000Z/outputs/iso/ Are there any steps not been written on the guide? I just followed the following guide: https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnStandard I checked the ovs-vswitchd.log and the following line maybe the cause: 23127 hugepages of size 2097152 reserved, but no mounted hugetlbfs found for that size It seems that something went wrong with hugepage. Some logs have been attached. If you have any idea about hugepage, please let me know. Peng has been added and hope Peng can provide some information about his environment. https://bugs.launchpad.net/starlingx/+bug/1819031 Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Tuesday, March 12, 2019 12:39 AM To: Peters, Matt >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, For Matt, I just tried to lock compute-1 to ensure the VMs is on the same compute host. But it still doesn’t work. The DHCP, router and VMs all located on compute-0. For Ghada, I checked the test cases listed in sanity test. I see that there is no test case to test the connectivity between VMs. Need confirmation from Ada’s team. https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 12, 2019 12:28 AM To: Khalil, Ghada >; Xu, Chenjie >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing If you co-locate the VMs on the same compute host (lock the other computes) do things work as expected? I.e. is it only when you are traversing the physical network that things are not pingable? -Matt From: Ghada Khalil > Date: Monday, March 11, 2019 at 10:51 AM To: "Xu, Chenjie" >, "Xie, Cindy" >, "Zhao, Forrest" >, "Peters, Matt" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" > Cc: "starlingx-discuss at lists.starlingx.io" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing To answer Forrest’s question: Do you know if OVS/DPDK has been tested after cut-over to container? I have seen Green sanity reports from Ada’s team since the cut-over. I expect this covers basic ovs-dpdk functional testing. Ada, please correct me if I am wrong. Regarding https://bugs.launchpad.net/starlingx/+bug/1819031, we’ve requested information from the reporter on how reproducible this issue is. As far as I know, it was reported on one system only. We’re waiting for more information from Peng. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Monday, March 11, 2019 10:40 AM To: Xie, Cindy; Zhao, Forrest; Peters, Matt; Richard, Joseph; Khalil, Ghada; Winnicki, Chris; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, Thank you for your information! The following issue is not exactly the same as mine: https://bugs.launchpad.net/starlingx/+bug/1819031 In this issue, the DHCP works and external network can reach the VMs. However in my case, VMs can’t get IP from DHCP and external network can’t reach VMs even with an IP allocated by myself. Best Regards, Xu, Chenjie From: Xie, Cindy Sent: Monday, March 11, 2019 10:05 PM To: Zhao, Forrest >; Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can’t get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can’t ping each other. The DHCP exists and VMs can’t ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris’s guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don’t believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don’t know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I’m trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I’m responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don’t know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing “system host-unlock compute-0”, it will report “Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address”. But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cirros-dpdk-vhostuserclient.xml Type: text/xml Size: 3890 bytes Desc: cirros-dpdk-vhostuserclient.xml URL: From Frank.Miller at windriver.com Fri Mar 15 19:13:39 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Fri, 15 Mar 2019 19:13:39 +0000 Subject: [Starlingx-discuss] FW: Distro.openstack meeting notes Mar 12th 2019 In-Reply-To: <9A85D2917C58154C960D95352B22818BD06FE61C@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BD06FCD2B@fmsmsx123.amr.corp.intel.com> <8EA56FFE-EC7B-442A-A95E-B5D0156DD236@99cloud.net> <15E77730-1BCD-47FA-A598-9DDA186DD094@99cloud.net> <9A85D2917C58154C960D95352B22818BD06FE61C@fmsmsx123.amr.corp.intel.com> Message-ID: Shuquan: It is great to see the progress being made by your team. Gerry Kopec has already provided guidance to you for line 27 (only a subset of the patch is intended to be upstreamed). Also Dean provided the unsquashed patches for line 37 yesterday. One suggestion I have for all the nova changes in your list would be for your primes to have a meeting with Gerry since he is familiar with all of the nova high priority bugs in your list. Gerry can answer questions you may have about any of the patches and possibly provide suggestions on what to put in the launchpads that you create. I’ll leave it to you to work out a day and time that works best for both your primes and Gerry. Frank From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, March 13, 2019 6:36 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] FW: Distro.openstack meeting notes Mar 12th 2019 Here is an update on 99Cloud’s work on OpenStack patch upstreaming. The master spreadsheet has been updated to reflect this update. They are requesting help on a couple of the line items: Line 27 primary: server-groups best-effort and group size: Server group soft-affinity is achieved in pike version, why not to use it but to develop the best-effort? And what is the server group size used for, I can't think about a necessary scene to finish the spec. Line 37 Configurable auto page refresh: Can someone (@Dean, @Frank) send the un-squashed patches to Shuquan please? brucej From: Shuquan Huang [mailto:huang.shuquan at 99cloud.net] Sent: Wednesday, March 13, 2019 1:59 AM To: Jones, Bruce E > Cc: 王亚 >; 朱博祥 >; 张鲲鹏 > Subject: Re: [Starlingx-discuss] Distro.openstack meeting notes Mar 12th 2019 Hi Bruce, This is the updated from 99Cloud. 6 vCPU model Ya Wang Because the feature is frozen, this spec has to be deferred to the train release. Last week I submit two patches into review system, the main work was refactor part of libvirt driver’s code and add a public method in scheduler utils to get flavor traits. Now the review is pause because we have to wait for re-proposed spec merged. The spec has one +2. Code: https://review.openstack.org/#/c/637834/ Spec: https://review.openstack.org/#/c/642030/ 20 rbd disks: convert from source format to raw Intel to fix upstram Boxiang Zhu Last week, Matthew suggested to remove the LVM related changes out of the patch. He thought that it might be easier to split it into a separate follow-up patch, as this is the change that will require a release note. Therefore, I have split it into two patches. And I also added some unit tests and improved the release notes. Just ready for review. I will ping Matthew and some other nova core reviewers to review the patch. Code1: https://review.openstack.org/#/c/640271/ Code2: https://review.openstack.org/#/c/642667/ 23 Do not bypass scheduler when using forced hosts Boxiang Zhu I have pushed a patch to the review system. But it still need more time to discuss with nova community to find whether it is suitable. Code: https://review.openstack.org/#/c/641908/ 25 Live block migration fails following auth token expiration Ya Wang The bug has been solved and I’ve verified it. On the other hand, I’ve submit a patch to update the nova’s document. The reason for the previous failure is because the service user's role does not match the config item: service_token_roles which is not clear in the document. Code: https://review.openstack.org/#/c/542008/ 26 Drop support for forced hosts for live migrate Boxiang Zhu The bug has been solved and I’ve verified it. The nova community has the same bp like 'remove-force-flag-from-live-migrate-and-evacuate'. The bp adds a micro version(named as 2.68) of api to remove the force flag. I have test the function by myself. And it will not accept the force flag if I specify the os-compute-api-version is 2.68. So I think the bp completely meets our requirements. Code: https://review.openstack.org/#/c/634600/ 27 Unsquash: primary: server-groups best-effort and group size Kupeng Zhang This patch contains two features, best-effort server group and group size. The best-effort feature is similar to soft-affinity/soft-anti-affinity of server group in nova community, and the group size is a new feature which need to submit a spec. We are discussing how to work for them. There are two questions to ask. Server group soft-affinity is achieved in pike version, why not to use it but to develop the best-effort? And what is the server group size used for, I can't think about a necessary scene to finish the spec. 37 Configurable Auto Page Refresh Kupeng Zhang I can’t get the patch from the link in the excel. It’s inside the intel github. Could you send this to us? Intel github: https://github.intel.com/Madawaska/patch-review/blob/master/horizon/0001-ENG-Openstack-rebase-to-Pike-Part-2.patch On Mar 12, 2019, at 10:24 PM, Shuquan Huang > wrote: Sorry, I didn’t notice it shifts to PDT. I’ll summary the progress from my side and send it out tomorrow. On Mar 12, 2019, at 10:21 PM, Jones, Bruce E > wrote: It’s over. All meetings shifted one hour earlier due to the US/Canada time change. From: Shuquan Huang [mailto:huang.shuquan at 99cloud.net] Sent: Tuesday, March 12, 2019 7:08 AM To: Jones, Bruce E > Subject: Re: [Starlingx-discuss] Distro.openstack meeting notes Mar 12th 2019 Hi Bruce, It seems I can’t join the meeting. It shows “The host has another meeting in progress” Is the meeting rescheduled? From: > on behalf of "Jones, Bruce E" > Date: Tuesday, March 12, 2019 at 9:55 PM To: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] Distro.openstack meeting notes Mar 12th 2019 Meeting agenda and notes for the 3/12 meeting • Good news - Neutron network segment range patches in (except lib) • Bad news - NUMA topology pushed out. • We believe we will have to carry forks of at least some of the Nova changes * We also believe anything committed to Nova is deployable (and will remain so as per Matt R). * We should implement the "upstream first" and "stable branch" concept and backport critical features and features from Train to our release branch • Changes that are absolutely critical should be backported before they are accepted (and updated over time until acceptance). • We should help fix things upstream as we find issues with Train "work in progress" patches * Meanwhile we will continuously update our master from OpenStack master • AR Bruce and Frank - need a plan for upstream contributions for Nova • We need to define our branching strategy. Create an f/stx-stein branch? Create a f/nova feature branch for StarlingX? * We will need to build our Nova container out of the github staging trees - once Nova cuts there first RC (Mar 22nd). Backports will be checked into github directly. • Plan to raise these issues with Nova community at PTG and support the efforts • Review updates: https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit?ts=5c1933cc#gid=0 • Review LP issues: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss 黄舒泉 Shuquan Huang 技术总监 Technical Director 九州云信息科技有限公司 99Cloud Co. Ltd. 邮箱(Email): huang.shuquan at 99cloud.net 手机(Mobile): +86-18616211612 电话(Tel): 021-61207665 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From yi.c.wang at intel.com Mon Mar 18 02:18:48 2019 From: yi.c.wang at intel.com (Wang, Yi C) Date: Mon, 18 Mar 2019 02:18:48 +0000 Subject: [Starlingx-discuss] Could any core reviewer help review our devstack patches? Message-ID: Hi core reviewers, Could you help review our devstack patches? We got CR+1 from Dean already. Thanks! https://review.openstack.org/#/c/641965/ https://review.openstack.org/#/c/639501/ https://review.openstack.org/#/c/641894/ https://review.openstack.org/#/c/642617/ https://review.openstack.org/#/c/639253/ https://review.openstack.org/#/c/642303/ https://review.openstack.org/#/c/639480/ https://review.openstack.org/#/c/642305/ BR Yi -------------- next part -------------- An HTML attachment was scrubbed... URL: From mario.alfredo.c.arevalo at intel.com Mon Mar 18 05:11:38 2019 From: mario.alfredo.c.arevalo at intel.com (Arevalo, Mario Alfredo C) Date: Mon, 18 Mar 2019 05:11:38 +0000 Subject: [Starlingx-discuss] Questions related to FM containerization In-Reply-To: <7242A3DC72E453498E3D783BBB134C3E9DDD2C1F@ALA-MBD.corp.ad.wrs.com> References: <7242A3DC72E453498E3D783BBB134C3E9DDD2C1F@ALA-MBD.corp.ad.wrs.com> Message-ID: <6594B51DBE477C48AAE23675314E6C466459B811@fmsmsx107.amr.corp.intel.com> Hi Tao, thanks for your answer, I think, it sounds as a good plan, however I would also like to complement this with the input from Brent. This is in order to define in a granularity way, the rest of the missing parts to update the storyboard with the needed requirements to accomplish this task (e.g. fm-fault 1 pod, connected through mysql in the same pod? consuming mariadb from x port?, add POST/PUT methods etc). Thanks. Best regards. Mario. [0] https://storyboard.openstack.org/#!/story/2004008 > -----Original Message----- > From: Liu, Tao [mailto:Tao.Liu at windriver.com] > Sent: Thursday, March 14, 2019 2:54 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Questions related to FM containerization > > Hi Mario, > > I think it would simplify the implementation significantly if we only containerize > the FM rest API service. > > You will need to add POST and PUT support in the API server and VIM will use > the rest APIs to raise the instance alarms/logs. > The alarm POST / PUT request handler will need to add alarm history entries to > the event log database table. > > The rest API service interfaces with the configured database backend directly. > Currently postgres is configured as the backend. > You will need to configure mysql as the database backend for the containerized > FM rest API service. > Openstack Horizon will also interface with containerized FM rest API service and > retrieve the instances alarm and event logs. > > I think the alarm suppression should still be managed through the platform fm > cli and horizon. > For the current release, we will not suppress the instance alarms nor would raise > SNMP traps inside the containerized services. > > Regards, > Tao Liu > > ------------------------------ > > Message: 2 > Date: Wed, 13 Mar 2019 21:52:12 +0000 > From: "Arevalo, Mario Alfredo C" > To: "starlingx-discuss at lists.starlingx.io" > > Cc: "brent.rowsell at windriver.com" > Subject: [Starlingx-discuss] Questions related to FM containerization > Message-ID: > <6594B51DBE477C48AAE23675314E6C46645994B3 at fmsmsx107.am > r.corp.intel.com> > > Content-Type: text/plain; charset="us-ascii" > > Hi Brent and team, > > This mail plans to interchange information in order to get more granularity > about the "Fault Manager" > Containerization process where the final objective is to deploy a pod or pods > which make completely match with the design of containerization architecture. > > According from the feedback received yesterday in our meeting and taking a > look to the source code and the processes which are running in a deployed > environment I can understand the possible missing parts. > > This is my understanding about the full picture and some questions about it, > please let me know if something is wrong or deviates from the original > objective/result. The storyboard [1] related to FM chart will be finished when > the FM restful API and the FM manager main services are containerized and > work correctly with the rest of the StarlingX components: > > - I think the best approach is to run a container per service and both containers > should live in the same pod. > - Both services should consume the same Docker image in order to reduce the > memory foot print. > - According the previous shared information and my code exploring I > understand the FM manager (fmManager > binary) is a service which listens in the port 8001 and executes requests. It is > launched by an script called "fminit". > At this point I have a pair of questions, is this the service which the storyboard > [1] makes reference of, > intended to have an instance in bare metal and another one exposed by a > container? > If the last questions is yes, we will have 2 instances of the same service then > they should be exposed in a > different port, and how about fm rest api service, it will just exist in a > container? > FM manager service has interaction with a PostgreSQL data base, then I > wonder how this will be handled. > Does this containerized service point to the bare metal database? Should we > add a new chart which exposes > a PostgreSQL due to the current chart tarball or just include one for MariaDB. > Then the task 28876 makes reference to modify nfv_vim[2] in order to get > the alarms information from > the container? > - Surfing in a deployed image I saw that is possible to remove alarms from the > web interface provided by > horizon, then the task 28878 makes reference to points to the FM manager > containerized service from > horizon, however it is not clear for me the task 28877 described in the chart > storyboard[1]. > > These are some points and questions which will give a better understanding for > the rest of tasks, however, possibly, I will get more questions during this process > I will be in contact with all of you. > > Thank you for your help. > > Best Regards. > Mario. > > References: > > [1] https://storyboard.openstack.org/#!/story/2004008 > [2] https://git.starlingx.io/cgit/stx-nfv/tree/nfv/nfv-vim/nfv_vim > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: discuss/attachments/20190313/a63da701/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 10, Issue 64 > ************************************************* > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From donny at fortnebula.com Mon Mar 18 12:56:05 2019 From: donny at fortnebula.com (Donny Davis) Date: Mon, 18 Mar 2019 08:56:05 -0400 Subject: [Starlingx-discuss] Is Magnum Fully supported for kubernetes cluster in StarlingX 2018.10? In-Reply-To: References: Message-ID: Can you share your whole magnum.conf? On Sat, Mar 16, 2019 at 4:57 PM Shashi, YatindraX < yatindrax.shashi at intel.com> wrote: > Dear Team, > > > > Lots of ISVs are interested in deploying StarlingX edge platform and to > support them I am trying to see feasibility of kubernetes cluster in > starlingX. > > > > I am trying to setup kubernetes clusters using Magnum 5.0.1 available in > the StarlingX 2018.10. I have downloaded latest 2018.10 ISO image from the > StarlingX Mirror repositories. > > But I am facing multiple issues while enabling the Magnum service and > running the commands. Is it supported and tested fully? > > > > If it is supported fully then would you please look in the logs and tell > me what I am missing. > > I have attached my Magnum.conf file and current logs of service running: > > > > > > ######################### > > > > *[wrsroot at controller-0 ~(keystone_admin)]$ magnum service-list* > > *ERROR: Invalid input for field 'identity/password/user/password': None is > not of type 'string'* > > > > *Failed validating 'type' in > schema['properties']['identity']['properties']['password']['properties']['user']['properties']['password']:* > > * {'type': 'string'}* > > > > *On instance['identity']['password']['user']['password']:* > > * None (HTTP 400) (Request-ID: > req-e1fd9612-a616-421f-92a3-2b5ee1f4e5ec) (HTTP 500) (Request-ID: > req-38d34547-9fb0-423b-bd33-1dcfa26ada68)* > > *[wrsroot at controller-0 ~(keystone_admin)]$* > > > > ####### > > > > Would you please look on it and let me know. > > > > I tried to add details as per the bug reported in the openstack seen in > the link https://bugs.launchpad.net/magnum/+bug/1717798 > > [keystone_authtoken] section of magnum.conf > > > > *admin_user: magnum* > > *admin_password: abcd at 123* > > *admin_tenant_name= services* > > > > But still no Luck. Would you please tell what could be problem. > > > > > > Mit freundlichen Grüßen, with best regards, > > Yatindra Shashi > > Intel Corporation > > Munich, Germany > > > > > _______________________________________________ > 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 Frank.Miller at windriver.com Mon Mar 18 18:54:28 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 18 Mar 2019 18:54:28 +0000 Subject: [Starlingx-discuss] Questions related to FM containerization In-Reply-To: <6594B51DBE477C48AAE23675314E6C466459B811@fmsmsx107.amr.corp.intel.com> References: <7242A3DC72E453498E3D783BBB134C3E9DDD2C1F@ALA-MBD.corp.ad.wrs.com> <6594B51DBE477C48AAE23675314E6C466459B811@fmsmsx107.amr.corp.intel.com> Message-ID: Mario: I took the action last week to set up a review this week to discuss a proposal and/or answer further questions in order to get to a proposal. Are you ready for me to set up the meeting? If you need more time please suggest a day for us to meet. Frank -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Monday, March 18, 2019 1:12 AM To: Liu, Tao; starlingx-discuss at lists.starlingx.io Cc: Rowsell, Brent Subject: Re: [Starlingx-discuss] Questions related to FM containerization Hi Tao, thanks for your answer, I think, it sounds as a good plan, however I would also like to complement this with the input from Brent. This is in order to define in a granularity way, the rest of the missing parts to update the storyboard with the needed requirements to accomplish this task (e.g. fm-fault 1 pod, connected through mysql in the same pod? consuming mariadb from x port?, add POST/PUT methods etc). Thanks. Best regards. Mario. [0] https://storyboard.openstack.org/#!/story/2004008 > -----Original Message----- > From: Liu, Tao [mailto:Tao.Liu at windriver.com] > Sent: Thursday, March 14, 2019 2:54 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Questions related to FM > containerization > > Hi Mario, > > I think it would simplify the implementation significantly if we only > containerize the FM rest API service. > > You will need to add POST and PUT support in the API server and VIM > will use the rest APIs to raise the instance alarms/logs. > The alarm POST / PUT request handler will need to add alarm history > entries to the event log database table. > > The rest API service interfaces with the configured database backend directly. > Currently postgres is configured as the backend. > You will need to configure mysql as the database backend for the > containerized FM rest API service. > Openstack Horizon will also interface with containerized FM rest API > service and retrieve the instances alarm and event logs. > > I think the alarm suppression should still be managed through the > platform fm cli and horizon. > For the current release, we will not suppress the instance alarms nor > would raise SNMP traps inside the containerized services. > > Regards, > Tao Liu > > ------------------------------ > > Message: 2 > Date: Wed, 13 Mar 2019 21:52:12 +0000 > From: "Arevalo, Mario Alfredo C" > To: "starlingx-discuss at lists.starlingx.io" > > Cc: "brent.rowsell at windriver.com" > Subject: [Starlingx-discuss] Questions related to FM containerization > Message-ID: > <6594B51DBE477C48AAE23675314E6C46645994B3 at fmsmsx107.am > r.corp.intel.com> > > Content-Type: text/plain; charset="us-ascii" > > Hi Brent and team, > > This mail plans to interchange information in order to get more > granularity about the "Fault Manager" > Containerization process where the final objective is to deploy a pod > or pods which make completely match with the design of containerization architecture. > > According from the feedback received yesterday in our meeting and > taking a look to the source code and the processes which are running > in a deployed environment I can understand the possible missing parts. > > This is my understanding about the full picture and some questions > about it, please let me know if something is wrong or deviates from > the original objective/result. The storyboard [1] related to FM chart > will be finished when the FM restful API and the FM manager main > services are containerized and work correctly with the rest of the StarlingX components: > > - I think the best approach is to run a container per service and both containers > should live in the same pod. > - Both services should consume the same Docker image in order to reduce the > memory foot print. > - According the previous shared information and my code exploring I > understand the FM manager (fmManager > binary) is a service which listens in the port 8001 and executes > requests. It is launched by an script called "fminit". > At this point I have a pair of questions, is this the service > which the storyboard [1] makes reference of, > intended to have an instance in bare metal and another one > exposed by a container? > If the last questions is yes, we will have 2 instances of the > same service then they should be exposed in a > different port, and how about fm rest api service, it will just > exist in a container? > FM manager service has interaction with a PostgreSQL data base, > then I wonder how this will be handled. > Does this containerized service point to the bare metal database? > Should we add a new chart which exposes > a PostgreSQL due to the current chart tarball or just include one for MariaDB. > Then the task 28876 makes reference to modify nfv_vim[2] in order > to get the alarms information from > the container? > - Surfing in a deployed image I saw that is possible to remove alarms from the > web interface provided by > horizon, then the task 28878 makes reference to points to the FM > manager containerized service from > horizon, however it is not clear for me the task 28877 described > in the chart storyboard[1]. > > These are some points and questions which will give a better > understanding for the rest of tasks, however, possibly, I will get > more questions during this process I will be in contact with all of you. > > Thank you for your help. > > Best Regards. > Mario. > > References: > > [1] https://storyboard.openstack.org/#!/story/2004008 > [2] https://git.starlingx.io/cgit/stx-nfv/tree/nfv/nfv-vim/nfv_vim > > > > > -------------- next part -------------- An HTML attachment was > scrubbed... > URL: discuss/attachments/20190313/a63da701/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 10, Issue 64 > ************************************************* > _______________________________________________ > 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 serverascode at gmail.com Mon Mar 18 22:16:42 2019 From: serverascode at gmail.com (Curtis) Date: Mon, 18 Mar 2019 18:16:42 -0400 Subject: [Starlingx-discuss] Offline docker images install? Message-ID: Hi All, I apologise if this has been covered somewhere, did a bit of searching...what if I want to install all the docker images for stx from an offline file. Was there some mention of these being included in the ISO (thought maybe I'd heard that), or can I import them prior to installation of openstack? Mostly I am coming from the perspective of the upcoming stx workshop at the openinfra summit. Would like to avoid students having to all download at the same time, or all hitting a local proxy, if possible. Sorry if I missed it. Thanks, Curtis PS. Thanks for the docs at https://wiki.openstack.org/wiki/StarlingX/Containers/Installation ran through it today, all good. :) -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.cm.lists at yandex.com Mon Mar 18 22:21:46 2019 From: erich.cm.lists at yandex.com (Erich Cordoba) Date: Mon, 18 Mar 2019 15:21:46 -0700 Subject: [Starlingx-discuss] Offline docker images install? In-Reply-To: References: Message-ID: <11547091552947706@myt3-964eae3a5b05.qloud-c.yandex.net> An HTML attachment was scrubbed... URL: From zhang.kunpeng at 99cloud.net Mon Mar 18 03:47:52 2019 From: zhang.kunpeng at 99cloud.net (=?utf-8?B?5byg6bKy6bmP?=) Date: Mon, 18 Mar 2019 11:47:52 +0800 Subject: [Starlingx-discuss] Fwd: FW: Distro.openstack meeting notes Mar 12th 2019 References: Message-ID: <8C822D42-D36D-4F30-98C9-5E1D69B33CEA@99cloud.net> Hi Dean, Can you provide the patches of line 37 “Configurable Auto Page Refresh”? I cannot open the link[1] [1] https://github.intel.com/Madawaska/patch-review/blob/master/horizon/0001-ENG-Openstack-rebase-to-Pike-Part-2.patch Regards Kunpeng > Begin forwarded message: > > From: "Miller, Frank" > Subject: Re: [Starlingx-discuss] FW: Distro.openstack meeting notes Mar 12th 2019 > Date: March 16, 2019 at 03:13:39 GMT+8 > To: "Jones, Bruce E" , "starlingx-discuss at lists.starlingx.io" > Cc: "Kopec, Gerald (Gerry)" > > Shuquan: > > It is great to see the progress being made by your team. Gerry Kopec has already provided guidance to you for line 27 (only a subset of the patch is intended to be upstreamed). Also Dean provided the unsquashed patches for line 37 yesterday. > > One suggestion I have for all the nova changes in your list would be for your primes to have a meeting with Gerry since he is familiar with all of the nova high priority bugs in your list. Gerry can answer questions you may have about any of the patches and possibly provide suggestions on what to put in the launchpads that you create. I’ll leave it to you to work out a day and time that works best for both your primes and Gerry. > > Frank >   <> > From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] > Sent: Wednesday, March 13, 2019 6:36 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] FW: Distro.openstack meeting notes Mar 12th 2019 > > Here is an update on 99Cloud’s work on OpenStack patch upstreaming. The master spreadsheet has been updated to reflect this update. > > They are requesting help on a couple of the line items: > > Line 27 primary: server-groups best-effort and group size: Server group soft-affinity is achieved in pike version, why not to use it but to develop the best-effort? And what is the server group size used for, I can't think about a necessary scene to finish the spec. > > Line 37 Configurable auto page refresh: Can someone (@Dean, @Frank) send the un-squashed patches to Shuquan please? > > brucej > > <>From: Shuquan Huang [mailto:huang.shuquan at 99cloud.net ] > Sent: Wednesday, March 13, 2019 1:59 AM > To: Jones, Bruce E > > Cc: 王亚 >; 朱博祥 >; 张鲲鹏 > > Subject: Re: [Starlingx-discuss] Distro.openstack meeting notes Mar 12th 2019 > > Hi Bruce, > > This is the updated from 99Cloud. > > 6 > vCPU model > Ya Wang > Because the feature is frozen, this spec has to be deferred to the train release. Last week I submit two patches into review system, the main work was refactor part of libvirt driver’s code and add a public method in scheduler utils to get flavor traits. Now the review is pause because we have to wait for re-proposed spec merged. The spec has one +2. > > Code: https://review.openstack.org/#/c/637834/ > Spec: https://review.openstack.org/#/c/642030/ > 20 > rbd disks: convert from source format to raw Intel to fix upstram > Boxiang Zhu > Last week, Matthew suggested to remove the LVM related changes out of the patch. He thought that it might be easier to split it into a separate follow-up patch, as this is the change that will require a release note. Therefore, I have split it into two patches. And I also added some unit tests and improved the release notes. Just ready for review. I will ping Matthew and some other nova core reviewers to review the patch. > > Code1: https://review.openstack.org/#/c/640271/ > Code2: https://review.openstack.org/#/c/642667/ > 23 > Do not bypass scheduler when using forced hosts > Boxiang Zhu > I have pushed a patch to the review system. But it still need more time to discuss with nova community to find whether it is suitable. > > Code: https://review.openstack.org/#/c/641908/ > 25 > Live block migration fails following auth token expiration > Ya Wang > The bug has been solved and I’ve verified it. On the other hand, I’ve submit a patch to update the nova’s document. The reason for the previous failure is because the service user's role does not match the config item: service_token_roles which is not clear in the document. > > Code: https://review.openstack.org/#/c/542008/ > 26 > Drop support for forced hosts for live migrate > Boxiang Zhu > The bug has been solved and I’ve verified it. The nova community has the same bp like 'remove-force-flag-from-live-migrate-and-evacuate'. The bp adds a micro version(named as 2.68) of api to remove the force flag. I have test the function by myself. And it will not accept the force flag if I specify the os-compute-api-version is 2.68. So I think the bp completely meets our requirements. > > Code: https://review.openstack.org/#/c/634600/ > 27 > Unsquash: primary: server-groups best-effort and group size > Kupeng Zhang > This patch contains two features, best-effort server group and group size. The best-effort feature is similar to soft-affinity/soft-anti-affinity of server group in nova community, and the group size is a new feature which need to submit a spec. We are discussing how to work for them. There are two questions to ask. Server group soft-affinity is achieved in pike version, why not to use it but to develop the best-effort? And what is the server group size used for, I can't think about a necessary scene to finish the spec. > 37 > Configurable Auto Page Refresh > Kupeng Zhang > I can’t get the patch from the link in the excel. It’s inside the intel github. Could you send this to us? > > Intel github: https://github.intel.com/Madawaska/patch-review/blob/master/horizon/0001-ENG-Openstack-rebase-to-Pike-Part-2.patch > > > On Mar 12, 2019, at 10:24 PM, Shuquan Huang > wrote: > > Sorry, I didn’t notice it shifts to PDT. I’ll summary the progress from my side and send it out tomorrow. > > On Mar 12, 2019, at 10:21 PM, Jones, Bruce E > wrote: > > It’s over. All meetings shifted one hour earlier due to the US/Canada time change. > > From: Shuquan Huang [mailto:huang.shuquan at 99cloud.net ] > Sent: Tuesday, March 12, 2019 7:08 AM > To: Jones, Bruce E > > Subject: Re: [Starlingx-discuss] Distro.openstack meeting notes Mar 12th 2019 > > Hi Bruce, > > It seems I can’t join the meeting. It shows “The host has another meeting in progress” > > Is the meeting rescheduled? > > From: > on behalf of "Jones, Bruce E" > > Date: Tuesday, March 12, 2019 at 9:55 PM > To: "starlingx-discuss at lists.starlingx.io " > > Subject: [Starlingx-discuss] Distro.openstack meeting notes Mar 12th 2019 > > Meeting agenda and notes for the 3/12 meeting > · Good news - Neutron network segment range patches in (except lib) > · Bad news - NUMA topology pushed out. > · We believe we will have to carry forks of at least some of the Nova changes > We also believe anything committed to Nova is deployable (and will remain so as per Matt R). > We should implement the "upstream first" and "stable branch" concept and backport critical features and features from Train to our release branch > § Changes that are absolutely critical should be backported before they are accepted (and updated over time until acceptance). > § We should help fix things upstream as we find issues with Train "work in progress" patches > Meanwhile we will continuously update our master from OpenStack master > · AR Bruce and Frank - need a plan for upstream contributions for Nova > · We need to define our branching strategy. Create an f/stx-stein branch? Create a f/nova feature branch for StarlingX? > We will need to build our Nova container out of the github staging trees - once Nova cuts there first RC (Mar 22nd). Backports will be checked into github directly. > · Plan to raise these issues with Nova community at PTG and support the efforts > · Review updates: https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit?ts=5c1933cc#gid=0 > · Review LP issues: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack > > > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > > > > 黄舒泉 Shuquan Huang > 技术总监 Technical Director > > 九州云信息科技有限公司 99Cloud Co. Ltd. > > 邮箱(Email): huang.shuquan at 99cloud.net > 手机(Mobile): +86-18616211612 > 电话(Tel): 021-61207665 > 地址(Addr): 上海市局门路427号1号楼206 > Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China > 网址(Site): http://www.99cloud.net > > > _______________________________________________ > 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 Matt.Peters at windriver.com Mon Mar 18 12:40:07 2019 From: Matt.Peters at windriver.com (Peters, Matt) Date: Mon, 18 Mar 2019 12:40:07 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> Message-ID: <7027C5CE-7CC6-44FF-9649-2287F2B233D1@windriver.com> Hi Chenjie, Sorry for the delayed reply. For the port that is created / plugged by OpenStack, can you confirm the flows that are visible to the OVS datapath? Are the packets seen by OVS br-int and then not switched properly or are the packets not being processed by the vhost port at all? If you are seeing packets reach the bridge, can you confirm if all packet types are not getting through, i.e. is ARP working, but not ICMP. You can dump the datapath ports and flows with the following command: ovs-appctl dpif/show ovs-appctl dpif/dump-flows br-int Also, when you did your manual test, did you have the other VM present as well, or was it a fully manual setup with no OpenStack agents present? Regards, Matt From: "Xu, Chenjie" Date: Friday, March 15, 2019 at 2:48 PM To: "Peters, Matt" , Ghada Khalil , "Xie, Cindy" , "Zhao, Forrest" , "Richard, Joseph" , "Winnicki, Chris" , "Lin, Shuicheng" , "Peng, Peng" Cc: "'starlingx-discuss at lists.starlingx.io'" , "Martinez Monroy, Elio" , "Cabrales, Ada" , "Jones, Bruce E" , "Qin, Kailun" , "Guo, Ruijing" , "Le, Huifeng" Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, We create vhostuser port and VM manually. And the connectivity between manually created VM and br-int works correctly. But the vhostuser port created by StarlingX doesn’t work. Could you please help review our following debugging steps and leave a comment? 1. We manually assigned correct IP to the StarlingX VM’s interface eth0 and ping DHCP server in VM. No packet can be captured by tcpdump and thus we think vhostuser port doesn’t work. Bring up br-int to verify the connectivity: sudo ifconfig br-int 192.168.101.1/24 up Check the IP assigned to the VM: openstack server list Manually assign IP to VM: sudo ifconfig 192.168.101.216/24 up Tcpdump in dhcp namespace: sudo ip netns exec $dhcp_namespace tcpdump –i $tap_device Ping DHCP server in VM: ping 192.168.101.1 No packets can be captured. 2. We added our own vhost user port to br-int and use virsh command and cirros-dpdk-vhostuserclient.xml (you can find in attached files) to create VM: Create vhostuser port: ovs-vsctl add-port br-int vhost-user-1 -- set Interface vhost-user-1 type=dpdkvhostuserclient options:vhost-server-path=/var/run/openvswitch/vhost-user-1 Create VM: virsh create cirros-dpdk-vhostuserclient.xml Bring up br-int to verify the connectivity: sudo ifconfig br-int 192.168.101.1/24 up Manually assign an IP to VM: sudo ifconfig eth0 192.168.101.18/24 up In created VM, ping br-int: ping 192.168.101.1 And the ping succeeds. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 13, 2019 9:13 PM To: Xu, Chenjie ; Khalil, Ghada ; Xie, Cindy ; Zhao, Forrest ; Richard, Joseph ; Winnicki, Chris ; Lin, Shuicheng ; Peng, Peng Cc: 'starlingx-discuss at lists.starlingx.io' ; Martinez Monroy, Elio ; Cabrales, Ada ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello, That message is a normal message from DPDK if you have multiple huge page sizes configured in your system. Openvswitch is configured to use 1G huge pages and will ignore the 2M huge pages. You can confirm this by looking at the Puppet logs to see what was configured and to ensure the 1G huge pages were mounted prior to openvswitch starting. -Matt From: "Xu, Chenjie" > Date: Wednesday, March 13, 2019 at 8:55 AM To: "Peters, Matt" >, Ghada Khalil >, "Xie, Cindy" >, "Zhao, Forrest" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" >, "Peng, Peng" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I installed StarlingX using following the March 5th ISO image and the issue still exists:http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190305T060000Z/outputs/iso/ Are there any steps not been written on the guide? I just followed the following guide: https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnStandard I checked the ovs-vswitchd.log and the following line maybe the cause: 23127 hugepages of size 2097152 reserved, but no mounted hugetlbfs found for that size It seems that something went wrong with hugepage. Some logs have been attached. If you have any idea about hugepage, please let me know. Peng has been added and hope Peng can provide some information about his environment. https://bugs.launchpad.net/starlingx/+bug/1819031 Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Tuesday, March 12, 2019 12:39 AM To: Peters, Matt >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, For Matt, I just tried to lock compute-1 to ensure the VMs is on the same compute host. But it still doesn’t work. The DHCP, router and VMs all located on compute-0. For Ghada, I checked the test cases listed in sanity test. I see that there is no test case to test the connectivity between VMs. Need confirmation from Ada’s team. https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 12, 2019 12:28 AM To: Khalil, Ghada >; Xu, Chenjie >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing If you co-locate the VMs on the same compute host (lock the other computes) do things work as expected? I.e. is it only when you are traversing the physical network that things are not pingable? -Matt From: Ghada Khalil > Date: Monday, March 11, 2019 at 10:51 AM To: "Xu, Chenjie" >, "Xie, Cindy" >, "Zhao, Forrest" >, "Peters, Matt" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" > Cc: "starlingx-discuss at lists.starlingx.io" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing To answer Forrest’s question: Do you know if OVS/DPDK has been tested after cut-over to container? I have seen Green sanity reports from Ada’s team since the cut-over. I expect this covers basic ovs-dpdk functional testing. Ada, please correct me if I am wrong. Regarding https://bugs.launchpad.net/starlingx/+bug/1819031, we’ve requested information from the reporter on how reproducible this issue is. As far as I know, it was reported on one system only. We’re waiting for more information from Peng. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Monday, March 11, 2019 10:40 AM To: Xie, Cindy; Zhao, Forrest; Peters, Matt; Richard, Joseph; Khalil, Ghada; Winnicki, Chris; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, Thank you for your information! The following issue is not exactly the same as mine: https://bugs.launchpad.net/starlingx/+bug/1819031 In this issue, the DHCP works and external network can reach the VMs. However in my case, VMs can’t get IP from DHCP and external network can’t reach VMs even with an IP allocated by myself. Best Regards, Xu, Chenjie From: Xie, Cindy Sent: Monday, March 11, 2019 10:05 PM To: Zhao, Forrest >; Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can’t get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can’t ping each other. The DHCP exists and VMs can’t ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris’s guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don’t believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don’t know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I’m trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I’m responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don’t know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing “system host-unlock compute-0”, it will report “Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address”. But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From chenjie.xu at intel.com Mon Mar 18 14:05:15 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Mon, 18 Mar 2019 14:05:15 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <7027C5CE-7CC6-44FF-9649-2287F2B233D1@windriver.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> <7027C5CE-7CC6-44FF-9649-2287F2B233D1@windriver.com> Message-ID: Hi Bruce/Ghada/Matt, I have located the cause of this bug: the domain XML file created by StarlingX lacks numa related sections. Need nova expert to fix this bug because it’s stx-nova to create domain XML file. By manually adding numa related sections, I can continue the OVSDPDK Upgrade Testing. But some unexpected behavior may exist. And I have tested the E/W traffic for VLAN network ( within the same host and across hosts). I have reported the bug in launchpad and you can find my debugging steps in the following bug report: https://bugs.launchpad.net/starlingx/+bug/1820378 Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Monday, March 18, 2019 8:40 PM To: Xu, Chenjie ; Khalil, Ghada ; Xie, Cindy ; Zhao, Forrest ; Richard, Joseph ; Winnicki, Chris ; Lin, Shuicheng ; Peng, Peng Cc: 'starlingx-discuss at lists.starlingx.io' ; Martinez Monroy, Elio ; Cabrales, Ada ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, Sorry for the delayed reply. For the port that is created / plugged by OpenStack, can you confirm the flows that are visible to the OVS datapath? Are the packets seen by OVS br-int and then not switched properly or are the packets not being processed by the vhost port at all? If you are seeing packets reach the bridge, can you confirm if all packet types are not getting through, i.e. is ARP working, but not ICMP. You can dump the datapath ports and flows with the following command: ovs-appctl dpif/show ovs-appctl dpif/dump-flows br-int Also, when you did your manual test, did you have the other VM present as well, or was it a fully manual setup with no OpenStack agents present? Regards, Matt From: "Xu, Chenjie" > Date: Friday, March 15, 2019 at 2:48 PM To: "Peters, Matt" >, Ghada Khalil >, "Xie, Cindy" >, "Zhao, Forrest" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" >, "Peng, Peng" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, We create vhostuser port and VM manually. And the connectivity between manually created VM and br-int works correctly. But the vhostuser port created by StarlingX doesn’t work. Could you please help review our following debugging steps and leave a comment? 1. We manually assigned correct IP to the StarlingX VM’s interface eth0 and ping DHCP server in VM. No packet can be captured by tcpdump and thus we think vhostuser port doesn’t work. Bring up br-int to verify the connectivity: sudo ifconfig br-int 192.168.101.1/24 up Check the IP assigned to the VM: openstack server list Manually assign IP to VM: sudo ifconfig 192.168.101.216/24 up Tcpdump in dhcp namespace: sudo ip netns exec $dhcp_namespace tcpdump –i $tap_device Ping DHCP server in VM: ping 192.168.101.1 No packets can be captured. 2. We added our own vhost user port to br-int and use virsh command and cirros-dpdk-vhostuserclient.xml (you can find in attached files) to create VM: Create vhostuser port: ovs-vsctl add-port br-int vhost-user-1 -- set Interface vhost-user-1 type=dpdkvhostuserclient options:vhost-server-path=/var/run/openvswitch/vhost-user-1 Create VM: virsh create cirros-dpdk-vhostuserclient.xml Bring up br-int to verify the connectivity: sudo ifconfig br-int 192.168.101.1/24 up Manually assign an IP to VM: sudo ifconfig eth0 192.168.101.18/24 up In created VM, ping br-int: ping 192.168.101.1 And the ping succeeds. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 13, 2019 9:13 PM To: Xu, Chenjie >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello, That message is a normal message from DPDK if you have multiple huge page sizes configured in your system. Openvswitch is configured to use 1G huge pages and will ignore the 2M huge pages. You can confirm this by looking at the Puppet logs to see what was configured and to ensure the 1G huge pages were mounted prior to openvswitch starting. -Matt From: "Xu, Chenjie" > Date: Wednesday, March 13, 2019 at 8:55 AM To: "Peters, Matt" >, Ghada Khalil >, "Xie, Cindy" >, "Zhao, Forrest" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" >, "Peng, Peng" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I installed StarlingX using following the March 5th ISO image and the issue still exists:http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190305T060000Z/outputs/iso/ Are there any steps not been written on the guide? I just followed the following guide: https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnStandard I checked the ovs-vswitchd.log and the following line maybe the cause: 23127 hugepages of size 2097152 reserved, but no mounted hugetlbfs found for that size It seems that something went wrong with hugepage. Some logs have been attached. If you have any idea about hugepage, please let me know. Peng has been added and hope Peng can provide some information about his environment. https://bugs.launchpad.net/starlingx/+bug/1819031 Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Tuesday, March 12, 2019 12:39 AM To: Peters, Matt >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, For Matt, I just tried to lock compute-1 to ensure the VMs is on the same compute host. But it still doesn’t work. The DHCP, router and VMs all located on compute-0. For Ghada, I checked the test cases listed in sanity test. I see that there is no test case to test the connectivity between VMs. Need confirmation from Ada’s team. https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 12, 2019 12:28 AM To: Khalil, Ghada >; Xu, Chenjie >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing If you co-locate the VMs on the same compute host (lock the other computes) do things work as expected? I.e. is it only when you are traversing the physical network that things are not pingable? -Matt From: Ghada Khalil > Date: Monday, March 11, 2019 at 10:51 AM To: "Xu, Chenjie" >, "Xie, Cindy" >, "Zhao, Forrest" >, "Peters, Matt" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" > Cc: "starlingx-discuss at lists.starlingx.io" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing To answer Forrest’s question: Do you know if OVS/DPDK has been tested after cut-over to container? I have seen Green sanity reports from Ada’s team since the cut-over. I expect this covers basic ovs-dpdk functional testing. Ada, please correct me if I am wrong. Regarding https://bugs.launchpad.net/starlingx/+bug/1819031, we’ve requested information from the reporter on how reproducible this issue is. As far as I know, it was reported on one system only. We’re waiting for more information from Peng. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Monday, March 11, 2019 10:40 AM To: Xie, Cindy; Zhao, Forrest; Peters, Matt; Richard, Joseph; Khalil, Ghada; Winnicki, Chris; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, Thank you for your information! The following issue is not exactly the same as mine: https://bugs.launchpad.net/starlingx/+bug/1819031 In this issue, the DHCP works and external network can reach the VMs. However in my case, VMs can’t get IP from DHCP and external network can’t reach VMs even with an IP allocated by myself. Best Regards, Xu, Chenjie From: Xie, Cindy Sent: Monday, March 11, 2019 10:05 PM To: Zhao, Forrest >; Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can’t get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can’t ping each other. The DHCP exists and VMs can’t ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris’s guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don’t believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don’t know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I’m trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I’m responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don’t know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing “system host-unlock compute-0”, it will report “Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address”. But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Mon Mar 18 15:01:12 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Mon, 18 Mar 2019 15:01:12 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> <7027C5CE-7CC6-44FF-9649-2287F2B233D1@windriver.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35ECF687@SHSMSX104.ccr.corp.intel.com> Thanks Chenjie to root-cause the issue. I am adding Zhipeng who is working on Nova-NUMA related patches and see if the feature has been included in the patch-set he is working on. Th.x - cindy From: Xu, Chenjie Sent: Monday, March 18, 2019 10:05 PM To: Peters, Matt ; Khalil, Ghada ; Xie, Cindy ; Zhao, Forrest ; Richard, Joseph ; Winnicki, Chris ; Lin, Shuicheng ; Peng, Peng Cc: 'starlingx-discuss at lists.starlingx.io' ; Martinez Monroy, Elio ; Cabrales, Ada ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Bruce/Ghada/Matt, I have located the cause of this bug: the domain XML file created by StarlingX lacks numa related sections. Need nova expert to fix this bug because it’s stx-nova to create domain XML file. By manually adding numa related sections, I can continue the OVSDPDK Upgrade Testing. But some unexpected behavior may exist. And I have tested the E/W traffic for VLAN network ( within the same host and across hosts). I have reported the bug in launchpad and you can find my debugging steps in the following bug report: https://bugs.launchpad.net/starlingx/+bug/1820378 Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Monday, March 18, 2019 8:40 PM To: Xu, Chenjie >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, Sorry for the delayed reply. For the port that is created / plugged by OpenStack, can you confirm the flows that are visible to the OVS datapath? Are the packets seen by OVS br-int and then not switched properly or are the packets not being processed by the vhost port at all? If you are seeing packets reach the bridge, can you confirm if all packet types are not getting through, i.e. is ARP working, but not ICMP. You can dump the datapath ports and flows with the following command: ovs-appctl dpif/show ovs-appctl dpif/dump-flows br-int Also, when you did your manual test, did you have the other VM present as well, or was it a fully manual setup with no OpenStack agents present? Regards, Matt From: "Xu, Chenjie" > Date: Friday, March 15, 2019 at 2:48 PM To: "Peters, Matt" >, Ghada Khalil >, "Xie, Cindy" >, "Zhao, Forrest" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" >, "Peng, Peng" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, We create vhostuser port and VM manually. And the connectivity between manually created VM and br-int works correctly. But the vhostuser port created by StarlingX doesn’t work. Could you please help review our following debugging steps and leave a comment? 1. We manually assigned correct IP to the StarlingX VM’s interface eth0 and ping DHCP server in VM. No packet can be captured by tcpdump and thus we think vhostuser port doesn’t work. Bring up br-int to verify the connectivity: sudo ifconfig br-int 192.168.101.1/24 up Check the IP assigned to the VM: openstack server list Manually assign IP to VM: sudo ifconfig 192.168.101.216/24 up Tcpdump in dhcp namespace: sudo ip netns exec $dhcp_namespace tcpdump –i $tap_device Ping DHCP server in VM: ping 192.168.101.1 No packets can be captured. 2. We added our own vhost user port to br-int and use virsh command and cirros-dpdk-vhostuserclient.xml (you can find in attached files) to create VM: Create vhostuser port: ovs-vsctl add-port br-int vhost-user-1 -- set Interface vhost-user-1 type=dpdkvhostuserclient options:vhost-server-path=/var/run/openvswitch/vhost-user-1 Create VM: virsh create cirros-dpdk-vhostuserclient.xml Bring up br-int to verify the connectivity: sudo ifconfig br-int 192.168.101.1/24 up Manually assign an IP to VM: sudo ifconfig eth0 192.168.101.18/24 up In created VM, ping br-int: ping 192.168.101.1 And the ping succeeds. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 13, 2019 9:13 PM To: Xu, Chenjie >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello, That message is a normal message from DPDK if you have multiple huge page sizes configured in your system. Openvswitch is configured to use 1G huge pages and will ignore the 2M huge pages. You can confirm this by looking at the Puppet logs to see what was configured and to ensure the 1G huge pages were mounted prior to openvswitch starting. -Matt From: "Xu, Chenjie" > Date: Wednesday, March 13, 2019 at 8:55 AM To: "Peters, Matt" >, Ghada Khalil >, "Xie, Cindy" >, "Zhao, Forrest" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" >, "Peng, Peng" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I installed StarlingX using following the March 5th ISO image and the issue still exists:http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190305T060000Z/outputs/iso/ Are there any steps not been written on the guide? I just followed the following guide: https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnStandard I checked the ovs-vswitchd.log and the following line maybe the cause: 23127 hugepages of size 2097152 reserved, but no mounted hugetlbfs found for that size It seems that something went wrong with hugepage. Some logs have been attached. If you have any idea about hugepage, please let me know. Peng has been added and hope Peng can provide some information about his environment. https://bugs.launchpad.net/starlingx/+bug/1819031 Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Tuesday, March 12, 2019 12:39 AM To: Peters, Matt >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, For Matt, I just tried to lock compute-1 to ensure the VMs is on the same compute host. But it still doesn’t work. The DHCP, router and VMs all located on compute-0. For Ghada, I checked the test cases listed in sanity test. I see that there is no test case to test the connectivity between VMs. Need confirmation from Ada’s team. https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 12, 2019 12:28 AM To: Khalil, Ghada >; Xu, Chenjie >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing If you co-locate the VMs on the same compute host (lock the other computes) do things work as expected? I.e. is it only when you are traversing the physical network that things are not pingable? -Matt From: Ghada Khalil > Date: Monday, March 11, 2019 at 10:51 AM To: "Xu, Chenjie" >, "Xie, Cindy" >, "Zhao, Forrest" >, "Peters, Matt" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" > Cc: "starlingx-discuss at lists.starlingx.io" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing To answer Forrest’s question: Do you know if OVS/DPDK has been tested after cut-over to container? I have seen Green sanity reports from Ada’s team since the cut-over. I expect this covers basic ovs-dpdk functional testing. Ada, please correct me if I am wrong. Regarding https://bugs.launchpad.net/starlingx/+bug/1819031, we’ve requested information from the reporter on how reproducible this issue is. As far as I know, it was reported on one system only. We’re waiting for more information from Peng. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Monday, March 11, 2019 10:40 AM To: Xie, Cindy; Zhao, Forrest; Peters, Matt; Richard, Joseph; Khalil, Ghada; Winnicki, Chris; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, Thank you for your information! The following issue is not exactly the same as mine: https://bugs.launchpad.net/starlingx/+bug/1819031 In this issue, the DHCP works and external network can reach the VMs. However in my case, VMs can’t get IP from DHCP and external network can’t reach VMs even with an IP allocated by myself. Best Regards, Xu, Chenjie From: Xie, Cindy Sent: Monday, March 11, 2019 10:05 PM To: Zhao, Forrest >; Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can’t get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can’t ping each other. The DHCP exists and VMs can’t ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris’s guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don’t believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don’t know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I’m trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I’m responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don’t know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing “system host-unlock compute-0”, it will report “Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address”. But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Peters at windriver.com Mon Mar 18 15:44:54 2019 From: Matt.Peters at windriver.com (Peters, Matt) Date: Mon, 18 Mar 2019 15:44:54 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F35ECF687@SHSMSX104.ccr.corp.intel.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> <7027C5CE-7CC6-44FF-9649-2287F2B233D1@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F35ECF687@SHSMSX104.ccr.corp.intel.com> Message-ID: <2EA87E40-D5F5-4100-A805-E46CE4D2B771@windriver.com> Hi Chenjie, I added some comments to the bug report and attached a domain XML from one of the Wind River labs. The numa sections you identity are present, so I included some software load information as well in case you are running a different software lineup (other than the openvswitch upgrade) that may be contributing to what you have observed. Regards, Matt From: "Xie, Cindy" Date: Monday, March 18, 2019 at 11:01 AM To: "Xu, Chenjie" , "Peters, Matt" , Ghada Khalil , "Zhao, Forrest" , "Richard, Joseph" , "Winnicki, Chris" , "Lin, Shuicheng" , "Peng, Peng" , "Liu, ZhipengS" Cc: "'starlingx-discuss at lists.starlingx.io'" , "Martinez Monroy, Elio" , "Cabrales, Ada" , "Jones, Bruce E" , "Qin, Kailun" , "Guo, Ruijing" , "Le, Huifeng" Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie to root-cause the issue. I am adding Zhipeng who is working on Nova-NUMA related patches and see if the feature has been included in the patch-set he is working on. Th.x - cindy From: Xu, Chenjie Sent: Monday, March 18, 2019 10:05 PM To: Peters, Matt ; Khalil, Ghada ; Xie, Cindy ; Zhao, Forrest ; Richard, Joseph ; Winnicki, Chris ; Lin, Shuicheng ; Peng, Peng Cc: 'starlingx-discuss at lists.starlingx.io' ; Martinez Monroy, Elio ; Cabrales, Ada ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Bruce/Ghada/Matt, I have located the cause of this bug: the domain XML file created by StarlingX lacks numa related sections. Need nova expert to fix this bug because it’s stx-nova to create domain XML file. By manually adding numa related sections, I can continue the OVSDPDK Upgrade Testing. But some unexpected behavior may exist. And I have tested the E/W traffic for VLAN network ( within the same host and across hosts). I have reported the bug in launchpad and you can find my debugging steps in the following bug report: https://bugs.launchpad.net/starlingx/+bug/1820378 Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Monday, March 18, 2019 8:40 PM To: Xu, Chenjie >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, Sorry for the delayed reply. For the port that is created / plugged by OpenStack, can you confirm the flows that are visible to the OVS datapath? Are the packets seen by OVS br-int and then not switched properly or are the packets not being processed by the vhost port at all? If you are seeing packets reach the bridge, can you confirm if all packet types are not getting through, i.e. is ARP working, but not ICMP. You can dump the datapath ports and flows with the following command: ovs-appctl dpif/show ovs-appctl dpif/dump-flows br-int Also, when you did your manual test, did you have the other VM present as well, or was it a fully manual setup with no OpenStack agents present? Regards, Matt From: "Xu, Chenjie" > Date: Friday, March 15, 2019 at 2:48 PM To: "Peters, Matt" >, Ghada Khalil >, "Xie, Cindy" >, "Zhao, Forrest" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" >, "Peng, Peng" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, We create vhostuser port and VM manually. And the connectivity between manually created VM and br-int works correctly. But the vhostuser port created by StarlingX doesn’t work. Could you please help review our following debugging steps and leave a comment? 1. We manually assigned correct IP to the StarlingX VM’s interface eth0 and ping DHCP server in VM. No packet can be captured by tcpdump and thus we think vhostuser port doesn’t work. Bring up br-int to verify the connectivity: sudo ifconfig br-int 192.168.101.1/24 up Check the IP assigned to the VM: openstack server list Manually assign IP to VM: sudo ifconfig 192.168.101.216/24 up Tcpdump in dhcp namespace: sudo ip netns exec $dhcp_namespace tcpdump –i $tap_device Ping DHCP server in VM: ping 192.168.101.1 No packets can be captured. 2. We added our own vhost user port to br-int and use virsh command and cirros-dpdk-vhostuserclient.xml (you can find in attached files) to create VM: Create vhostuser port: ovs-vsctl add-port br-int vhost-user-1 -- set Interface vhost-user-1 type=dpdkvhostuserclient options:vhost-server-path=/var/run/openvswitch/vhost-user-1 Create VM: virsh create cirros-dpdk-vhostuserclient.xml Bring up br-int to verify the connectivity: sudo ifconfig br-int 192.168.101.1/24 up Manually assign an IP to VM: sudo ifconfig eth0 192.168.101.18/24 up In created VM, ping br-int: ping 192.168.101.1 And the ping succeeds. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 13, 2019 9:13 PM To: Xu, Chenjie >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello, That message is a normal message from DPDK if you have multiple huge page sizes configured in your system. Openvswitch is configured to use 1G huge pages and will ignore the 2M huge pages. You can confirm this by looking at the Puppet logs to see what was configured and to ensure the 1G huge pages were mounted prior to openvswitch starting. -Matt From: "Xu, Chenjie" > Date: Wednesday, March 13, 2019 at 8:55 AM To: "Peters, Matt" >, Ghada Khalil >, "Xie, Cindy" >, "Zhao, Forrest" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" >, "Peng, Peng" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I installed StarlingX using following the March 5th ISO image and the issue still exists:http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190305T060000Z/outputs/iso/ Are there any steps not been written on the guide? I just followed the following guide: https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnStandard I checked the ovs-vswitchd.log and the following line maybe the cause: 23127 hugepages of size 2097152 reserved, but no mounted hugetlbfs found for that size It seems that something went wrong with hugepage. Some logs have been attached. If you have any idea about hugepage, please let me know. Peng has been added and hope Peng can provide some information about his environment. https://bugs.launchpad.net/starlingx/+bug/1819031 Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Tuesday, March 12, 2019 12:39 AM To: Peters, Matt >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, For Matt, I just tried to lock compute-1 to ensure the VMs is on the same compute host. But it still doesn’t work. The DHCP, router and VMs all located on compute-0. For Ghada, I checked the test cases listed in sanity test. I see that there is no test case to test the connectivity between VMs. Need confirmation from Ada’s team. https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 12, 2019 12:28 AM To: Khalil, Ghada >; Xu, Chenjie >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing If you co-locate the VMs on the same compute host (lock the other computes) do things work as expected? I.e. is it only when you are traversing the physical network that things are not pingable? -Matt From: Ghada Khalil > Date: Monday, March 11, 2019 at 10:51 AM To: "Xu, Chenjie" >, "Xie, Cindy" >, "Zhao, Forrest" >, "Peters, Matt" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" > Cc: "starlingx-discuss at lists.starlingx.io" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing To answer Forrest’s question: Do you know if OVS/DPDK has been tested after cut-over to container? I have seen Green sanity reports from Ada’s team since the cut-over. I expect this covers basic ovs-dpdk functional testing. Ada, please correct me if I am wrong. Regarding https://bugs.launchpad.net/starlingx/+bug/1819031, we’ve requested information from the reporter on how reproducible this issue is. As far as I know, it was reported on one system only. We’re waiting for more information from Peng. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Monday, March 11, 2019 10:40 AM To: Xie, Cindy; Zhao, Forrest; Peters, Matt; Richard, Joseph; Khalil, Ghada; Winnicki, Chris; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, Thank you for your information! The following issue is not exactly the same as mine: https://bugs.launchpad.net/starlingx/+bug/1819031 In this issue, the DHCP works and external network can reach the VMs. However in my case, VMs can’t get IP from DHCP and external network can’t reach VMs even with an IP allocated by myself. Best Regards, Xu, Chenjie From: Xie, Cindy Sent: Monday, March 11, 2019 10:05 PM To: Zhao, Forrest >; Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can’t get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can’t ping each other. The DHCP exists and VMs can’t ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris’s guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don’t believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don’t know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I’m trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I’m responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don’t know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing “system host-unlock compute-0”, it will report “Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address”. But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Mon Mar 18 17:25:11 2019 From: kennelson11 at gmail.com (Kendall Nelson) Date: Mon, 18 Mar 2019 10:25:11 -0700 Subject: [Starlingx-discuss] [all][PTG] Strawman Schedule In-Reply-To: References: Message-ID: Hello Everyone, In the attached picture or link [0] you will find the proposed schedule for the various tracks at the Denver PTG in April/May. We did our best to avoid the key conflicts that the track leads (PTLs, SIG leads...) mentioned in their PTG survey responses, although there was no perfect solution that would avoid all conflicts especially when the event is three days long and we have over 40 teams meeting. If there is a critical conflict that was missed, please let us know, but otherwise we are not planning to change this proposal. You'll notice that: - Like in Dublin and the last time we were in Denver, a number of tracks do not get pre-allocated time, and will be scheduled on the spot in available rooms at the time that makes the most sense for the participants. - Every track will be able to book extra time and space in available extra rooms at the event via the PTGBot once its configured for the event. More details to come on that. - Airship & OpenStack Helm will each have a day and a half (with the opportunity to book more time as they need) but we hadn't decided which will go first And here are links to more information about the event[1], on registration[2] or booking a room at the event hotel[3] in case you haven't booked or registered yet :) See you there! -Kendall Nelson (diablo_rojo) [0] https://screenshotscdn.firefoxusercontent.com/images/8c880d0a-b41e-4cea-8ff7-8f34073852ca.png?embedded=og [1]https://www.openstack.org/ptg [2]https://www.eventbrite.com/e/open-infrastructure-summit-project-teams-gathering-tickets-52606153421?_ga=2.190991274.1609728385.1552928145-572792429.1538091877 [3]https://www.hyatt.com/en-US/group-booking/DENCC/G-FNTE -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: train_ptg_strawman.png Type: image/png Size: 48457 bytes Desc: not available URL: From himanshugoyal500 at gmail.com Tue Mar 19 05:59:18 2019 From: himanshugoyal500 at gmail.com (Himanshu Goyal) Date: Tue, 19 Mar 2019 11:29:18 +0530 Subject: [Starlingx-discuss] Not able to create tenant network in case of a flat provider network Message-ID: Hi, I installed a controller + compute starlingX setup & configured provider data network as flat.when i'm trying to create tenant network it showing me below error: *Error: *Failed to create network "private": Unable to create the network. No tenant network is available for allocation. Neutron server returns request_ids: ['req-aa3bde1c-a1c0-404f-8d44-9bdc70abbed7'] I have one more setup with provider network as VLAN in that tenant network it is working fine. Please suggest, what are the needful changes need to follow to create tenant network in setup 1. Regards, Himanshu Goyal -------------- next part -------------- An HTML attachment was scrubbed... URL: From kailun.qin at intel.com Tue Mar 19 06:38:26 2019 From: kailun.qin at intel.com (Qin, Kailun) Date: Tue, 19 Mar 2019 06:38:26 +0000 Subject: [Starlingx-discuss] Not able to create tenant network in case of a flat provider network In-Reply-To: References: Message-ID: Hi Himanshu, Would you please kindly help provide the following information: 1. which version of StarlingX are you working on? w/ or w/o Container configuration? 2. which installation guide are you following? Thanks a lot. BR, Kailun From: Himanshu Goyal [mailto:himanshugoyal500 at gmail.com] Sent: Tuesday, March 19, 2019 1:59 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Not able to create tenant network in case of a flat provider network Hi, I installed a controller + compute starlingX setup & configured provider data network as flat.when i'm trying to create tenant network it showing me below error: Error: Failed to create network "private": Unable to create the network. No tenant network is available for allocation. Neutron server returns request_ids: ['req-aa3bde1c-a1c0-404f-8d44-9bdc70abbed7'] I have one more setup with provider network as VLAN in that tenant network it is working fine. Please suggest, what are the needful changes need to follow to create tenant network in setup 1. Regards, Himanshu Goyal -------------- next part -------------- An HTML attachment was scrubbed... URL: From himanshugoyal500 at gmail.com Tue Mar 19 07:28:36 2019 From: himanshugoyal500 at gmail.com (Himanshu Goyal) Date: Tue, 19 Mar 2019 12:58:36 +0530 Subject: [Starlingx-discuss] Not able to create tenant network in case of a flat provider network In-Reply-To: References: Message-ID: Hi kailun, Please find response inline [Himanshu]: Regards, Himanshu Goyal On Tue, Mar 19, 2019 at 12:08 PM Qin, Kailun wrote: > Hi Himanshu, > > > > Would you please kindly help provide the following information: > > 1. which version of StarlingX are you working on? w/ or w/o > Container configuration? > [Himanshu]: we are using OCT 2018 release without container, download starling ISO image from below path: http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/outputs/iso/ > 2. which installation guide are you following? > [Himanshu]:we followed the steps mentioned in below link: https://docs.starlingx.io/installation_guide/2018_10/controller_storage.html As we installed our setup with only 2 physical machines skip steps related to controller 1 configuration. Thanks a lot. > > > BR, > > Kailun > > > > *From:* Himanshu Goyal [mailto:himanshugoyal500 at gmail.com] > *Sent:* Tuesday, March 19, 2019 1:59 PM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] Not able to create tenant network in case > of a flat provider network > > > > Hi, > > > > I installed a controller + compute starlingX setup & configured provider > data network as flat.when i'm trying to create tenant network it showing me > below error: > > *Error: *Failed to create network "private": Unable to create the > network. No tenant network is available for allocation. Neutron server > returns request_ids: ['req-aa3bde1c-a1c0-404f-8d44-9bdc70abbed7'] > > > > I have one more setup with provider network as VLAN in that tenant network > it is working fine. > > > > Please suggest, what are the needful changes need to follow to create > tenant network in setup 1. > > > > Regards, > > Himanshu Goyal > -------------- next part -------------- An HTML attachment was scrubbed... URL: From abraham.arce.moreno at intel.com Tue Mar 19 14:58:04 2019 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Tue, 19 Mar 2019 14:58:04 +0000 Subject: [Starlingx-discuss] Offline docker images install? In-Reply-To: References: Message-ID: Curtis, > I apologise if this has been covered somewhere, did a bit of searching...what > if I want to install all the docker images for stx from an offline file. Was there > some mention of these being included in the ISO (thought maybe I'd heard > that), or can I import them prior to installation of openstack? > > Mostly I am coming from the perspective of the upcoming stx workshop at > the openinfra summit. Would like to avoid students having to all download at > the same time, or all hitting a local proxy, if possible. > https://wiki.openstack.org/wiki/StarlingX/Containers/Installation ran > through it today, all good. :) I do not know about workshop outline and resources the attendees would need to take but here you have one idea that have worked out for me in workshops: - It is always good to try the pre-work option, share with a attendees a list of steps / resources to complete before day 1. Not all attendees will complete but your network will handle fewer connections. - If those instructions are shared in advance, attendees can be early involved in our community by asking them to follow our Installation instructions and ask them to make changes and fix things for a reward to be delivered in day 1 :) P.D. You will be one of our reviewers for the transition from the wiki to the StarlingX documentation site. From serverascode at gmail.com Tue Mar 19 15:07:53 2019 From: serverascode at gmail.com (Curtis) Date: Tue, 19 Mar 2019 11:07:53 -0400 Subject: [Starlingx-discuss] Offline docker images install? In-Reply-To: References: Message-ID: On Tue, Mar 19, 2019 at 10:58 AM Arce Moreno, Abraham < abraham.arce.moreno at intel.com> wrote: > Curtis, > > > I apologise if this has been covered somewhere, did a bit of > searching...what > > if I want to install all the docker images for stx from an offline file. > Was there > > some mention of these being included in the ISO (thought maybe I'd heard > > that), or can I import them prior to installation of openstack? > > > > Mostly I am coming from the perspective of the upcoming stx workshop at > > the openinfra summit. Would like to avoid students having to all > download at > > the same time, or all hitting a local proxy, if possible. > > > https://wiki.openstack.org/wiki/StarlingX/Containers/Installation ran > > through it today, all good. :) > > I do not know about workshop outline and resources the attendees would > need to take but here you have one idea > that have worked out for me in workshops: > Thanks Abraham. :) > > - It is always good to try the pre-work option, share with a attendees a > list of steps / resources to complete before day 1. > Not all attendees will complete but your network will handle fewer > connections. > There won't be any pre-work for the attendees, they'll just show up and have access to everything they need to complete the workshop. The pre-work will be automated and using packet.com's infrastructure and likely ansible. > - If those instructions are shared in advance, attendees can be early > involved in our community by asking them to follow our Installation > instructions and ask them to make changes and fix things for a reward to > be delivered in day 1 :) > > Yeah we can make everything available beforehand for sure. But the style of workshop is that anyone can show up and as long as they have an ssh terminal, some command line experience, and the ability to cut and paste commands they should be good. :) > P.D. You will be one of our reviewers for the transition from the wiki to > the StarlingX documentation site. > Sounds good. Thanks, Curtis -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Tue Mar 19 15:49:11 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 19 Mar 2019 16:49:11 +0100 Subject: [Starlingx-discuss] Community Marketing Planning call at 9am PST on Wednesday this week? Message-ID: <79DAF250-2045-4F41-925F-DBF450CC53D1@gmail.com> Hi, I have a conflict this week and can’t make it to the 8am PST call. Would it work for people who are interested in attending the call to stick to 1600 UTC and have it from 9am PST? Thanks, Ildikó From cindy.xie at intel.com Tue Mar 19 18:24:41 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 19 Mar 2019 18:24:41 +0000 Subject: [Starlingx-discuss] Weekly StarlingX non-OpenStack Distro meeting In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F35DB65F5@SHSMSX104.ccr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F35DB65F5@SHSMSX104.ccr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35ED13C4@SHSMSX104.ccr.corp.intel.com> Agenda for 3/20 meeting: - CentOS 7.6 has been merged to master and testing was green in 3/15 Cengen image (thanks everybody who contributed to this activities). - Ceph upgrade update (Ovidiu/Daniel, Tingjie/Yong) - QAT upgrade plan (Cindy) - Opens (All) -----Original Appointment----- From: Xie, Cindy Sent: Sunday, November 4, 2018 10:27 PM To: Xie, Cindy; Troyer, Dean; Zhu, Vivian; Hu, Yong; Lin, Shuicheng; Shang, Dehao; Somerville, Jim; Wold, Saul; Sun, Austin; Jones, Bruce E; Liu, ZhipengS; 'Rowsell, Brent'; 'Khalil, Ghada'; starlingx-discuss at lists.starlingx.io; Waheed, Numan Cc: Perez Carranza, Jose; 'Hellmann, Gil'; 'Seiler, Glenn'; 'Young, Ken'; Arce Moreno, Abraham; Cobbley, David A; Fang, Liang A; 'Eslimi, Dariush'; Hu, Wei W; Martinez Monroy, Elio; 'Waines, Greg'; Lara, Cesar; Armstrong, Robert H; 'Chen, Jacky'; Martinez Landa, Hayde; 'Poncea, Ovidiu'; Perez Rodriguez, Humberto I; Gomez, Juan P; Shuquan Huang Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, March 20, 2019 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 zhipengs.liu at intel.com Tue Mar 19 03:06:32 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Tue, 19 Mar 2019 03:06:32 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F35ECF687@SHSMSX104.ccr.corp.intel.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> <7027C5CE-7CC6-44FF-9649-2287F2B233D1@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F35ECF687@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C7530564B4@SHSMSX104.ccr.corp.intel.com> Hi Cindy, The feature mentioned below is not included in the patch-set that I’m working on. That is just for migration related Numa data. BTW, using below command openstack server show I could not see numa topology related info that I can see in non-container build Thanks! Zhipeng From: Xie, Cindy Sent: 2019年3月18日 23:01 To: Xu, Chenjie ; Peters, Matt ; Khalil, Ghada ; Zhao, Forrest ; Richard, Joseph ; Winnicki, Chris ; Lin, Shuicheng ; Peng, Peng ; Liu, ZhipengS Cc: 'starlingx-discuss at lists.starlingx.io' ; Martinez Monroy, Elio ; Cabrales, Ada ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie to root-cause the issue. I am adding Zhipeng who is working on Nova-NUMA related patches and see if the feature has been included in the patch-set he is working on. Th.x - cindy From: Xu, Chenjie Sent: Monday, March 18, 2019 10:05 PM To: Peters, Matt >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Bruce/Ghada/Matt, I have located the cause of this bug: the domain XML file created by StarlingX lacks numa related sections. Need nova expert to fix this bug because it’s stx-nova to create domain XML file. By manually adding numa related sections, I can continue the OVSDPDK Upgrade Testing. But some unexpected behavior may exist. And I have tested the E/W traffic for VLAN network ( within the same host and across hosts). I have reported the bug in launchpad and you can find my debugging steps in the following bug report: https://bugs.launchpad.net/starlingx/+bug/1820378 Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Monday, March 18, 2019 8:40 PM To: Xu, Chenjie >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, Sorry for the delayed reply. For the port that is created / plugged by OpenStack, can you confirm the flows that are visible to the OVS datapath? Are the packets seen by OVS br-int and then not switched properly or are the packets not being processed by the vhost port at all? If you are seeing packets reach the bridge, can you confirm if all packet types are not getting through, i.e. is ARP working, but not ICMP. You can dump the datapath ports and flows with the following command: ovs-appctl dpif/show ovs-appctl dpif/dump-flows br-int Also, when you did your manual test, did you have the other VM present as well, or was it a fully manual setup with no OpenStack agents present? Regards, Matt From: "Xu, Chenjie" > Date: Friday, March 15, 2019 at 2:48 PM To: "Peters, Matt" >, Ghada Khalil >, "Xie, Cindy" >, "Zhao, Forrest" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" >, "Peng, Peng" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, We create vhostuser port and VM manually. And the connectivity between manually created VM and br-int works correctly. But the vhostuser port created by StarlingX doesn’t work. Could you please help review our following debugging steps and leave a comment? 1. We manually assigned correct IP to the StarlingX VM’s interface eth0 and ping DHCP server in VM. No packet can be captured by tcpdump and thus we think vhostuser port doesn’t work. Bring up br-int to verify the connectivity: sudo ifconfig br-int 192.168.101.1/24 up Check the IP assigned to the VM: openstack server list Manually assign IP to VM: sudo ifconfig 192.168.101.216/24 up Tcpdump in dhcp namespace: sudo ip netns exec $dhcp_namespace tcpdump –i $tap_device Ping DHCP server in VM: ping 192.168.101.1 No packets can be captured. 2. We added our own vhost user port to br-int and use virsh command and cirros-dpdk-vhostuserclient.xml (you can find in attached files) to create VM: Create vhostuser port: ovs-vsctl add-port br-int vhost-user-1 -- set Interface vhost-user-1 type=dpdkvhostuserclient options:vhost-server-path=/var/run/openvswitch/vhost-user-1 Create VM: virsh create cirros-dpdk-vhostuserclient.xml Bring up br-int to verify the connectivity: sudo ifconfig br-int 192.168.101.1/24 up Manually assign an IP to VM: sudo ifconfig eth0 192.168.101.18/24 up In created VM, ping br-int: ping 192.168.101.1 And the ping succeeds. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 13, 2019 9:13 PM To: Xu, Chenjie >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello, That message is a normal message from DPDK if you have multiple huge page sizes configured in your system. Openvswitch is configured to use 1G huge pages and will ignore the 2M huge pages. You can confirm this by looking at the Puppet logs to see what was configured and to ensure the 1G huge pages were mounted prior to openvswitch starting. -Matt From: "Xu, Chenjie" > Date: Wednesday, March 13, 2019 at 8:55 AM To: "Peters, Matt" >, Ghada Khalil >, "Xie, Cindy" >, "Zhao, Forrest" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" >, "Peng, Peng" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I installed StarlingX using following the March 5th ISO image and the issue still exists:http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190305T060000Z/outputs/iso/ Are there any steps not been written on the guide? I just followed the following guide: https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnStandard I checked the ovs-vswitchd.log and the following line maybe the cause: 23127 hugepages of size 2097152 reserved, but no mounted hugetlbfs found for that size It seems that something went wrong with hugepage. Some logs have been attached. If you have any idea about hugepage, please let me know. Peng has been added and hope Peng can provide some information about his environment. https://bugs.launchpad.net/starlingx/+bug/1819031 Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Tuesday, March 12, 2019 12:39 AM To: Peters, Matt >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, For Matt, I just tried to lock compute-1 to ensure the VMs is on the same compute host. But it still doesn’t work. The DHCP, router and VMs all located on compute-0. For Ghada, I checked the test cases listed in sanity test. I see that there is no test case to test the connectivity between VMs. Need confirmation from Ada’s team. https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 12, 2019 12:28 AM To: Khalil, Ghada >; Xu, Chenjie >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing If you co-locate the VMs on the same compute host (lock the other computes) do things work as expected? I.e. is it only when you are traversing the physical network that things are not pingable? -Matt From: Ghada Khalil > Date: Monday, March 11, 2019 at 10:51 AM To: "Xu, Chenjie" >, "Xie, Cindy" >, "Zhao, Forrest" >, "Peters, Matt" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" > Cc: "starlingx-discuss at lists.starlingx.io" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing To answer Forrest’s question: Do you know if OVS/DPDK has been tested after cut-over to container? I have seen Green sanity reports from Ada’s team since the cut-over. I expect this covers basic ovs-dpdk functional testing. Ada, please correct me if I am wrong. Regarding https://bugs.launchpad.net/starlingx/+bug/1819031, we’ve requested information from the reporter on how reproducible this issue is. As far as I know, it was reported on one system only. We’re waiting for more information from Peng. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Monday, March 11, 2019 10:40 AM To: Xie, Cindy; Zhao, Forrest; Peters, Matt; Richard, Joseph; Khalil, Ghada; Winnicki, Chris; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, Thank you for your information! The following issue is not exactly the same as mine: https://bugs.launchpad.net/starlingx/+bug/1819031 In this issue, the DHCP works and external network can reach the VMs. However in my case, VMs can’t get IP from DHCP and external network can’t reach VMs even with an IP allocated by myself. Best Regards, Xu, Chenjie From: Xie, Cindy Sent: Monday, March 11, 2019 10:05 PM To: Zhao, Forrest >; Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can’t get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can’t ping each other. The DHCP exists and VMs can’t ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris’s guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don’t believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don’t know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I’m trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I’m responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don’t know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing “system host-unlock compute-0”, it will report “Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address”. But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Tue Mar 19 19:16:30 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 19 Mar 2019 19:16:30 +0000 Subject: [Starlingx-discuss] Distro.openstack meeting minutes Mar 19th Message-ID: <9A85D2917C58154C960D95352B22818BD0701D6D@fmsmsx123.amr.corp.intel.com> Overall plan and status tracking document: https://etherpad.openstack.org/p/stx-openstack-patch-refactoring * Details: https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit?usp=sharing Story boards: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.distro.openstack&project_group_id=86 Meeting agenda and notes for the 3/19 meeting * 3/12 email from Dean: * This is the process I imagined and outlined in the meeting: ? When Nova creates their stable/stein branch at RC1 time (week of Mar 19th) we will create a mirror of that in starlingx-staging/nova as stx/stein. ? AR Dean to pull our branch next week, to be populated from backports * This branch will be periodically updated from stable/stein as backports appear there from the Nova team. * As items on our list of upstream changes land in master (Train) we will backport them to stx/stein for StarlingX to pick up. * There may be times that work upstream has not yet merged but is sufficiently complete that we would backport early to meet a StarlingX time requirement, with the expectation that it be brought current with what finally does merge after that happens. ? Upstream work that is not yet complete that we want to backport to meet a StarlingX time requirement should be worked upstream to get it to the state mentioned above to enable us to backport it to stx/stein. * Still to be decided/confirmed: ? We need to have some measure of testing in stx/stein, I will look in to what we can run from OpenStack Zuul directly. * We can switch Sanity testing to the new branch. * We would have to update / add Zuul jobs to allow the already defined Nova Zuul jobs to run out of github staging * We would have to add a trigger to the github to watch PRs and start Zuul ? I like the idea of continuing to have only a small number of people with the ability to commit to the staging repo ? We may want to consider the tactic of keeping our additional commits in stx/stein rebased on top of the upstream stable/stein rather than merging in upstream backports. This would be inconvenient for those with local copies of the branch after each rebase but it would keep the SHAs in the upstream commits the same. (I am not convinced yet that we should do this, still sorting it out) * Do we rebase backports? * We think that the right approach will be to take these as they come in. Make it easy on the developers. Concern is about how to manage conflicts with upstream Nova changes. * How frequently do we rebase? Weekly? When we need to? At the very least we want to do one rebase just before code freeze (and after stable Stein is released). * We marked up the spreadsheet with a new "Candidate for backport" column and identified 11 changes that are candidates * NUMA live migration WIP code - can/should we jumpstart integration of it with STX? * Code upstream is in reasonable shape and needs two small fixes. Gerry @ WR has been testing it against pinning / not pinned, hugepages vs none. Gerry has posted review comments with suggested fixes. * Bruce to stop the work in SH on this and let Gerry drive. * Dean to post a message to Nova calling out our need for a fork and would like to minimize it, by asking that the changes we want hit Train early. * Re: https://review.openstack.org/#/c/641908/ - this didn't get a launchpad filed, so the Nova community (Matt R) put a -2 on the review since it looks like a new feature. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Tue Mar 19 21:50:14 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 19 Mar 2019 22:50:14 +0100 Subject: [Starlingx-discuss] Community Marketing Planning call at 9am PST on Wednesday this week? In-Reply-To: <79DAF250-2045-4F41-925F-DBF450CC53D1@gmail.com> References: <79DAF250-2045-4F41-925F-DBF450CC53D1@gmail.com> Message-ID: <653ADD3C-7B34-4C09-A74D-D4B849232376@gmail.com> Hi, A quick update that based on the responses we will do the 9am PST / 1600 UTC slot tomorrow. Please see this etherpad for agenda and dial-in info in case you are interested in joining: https://etherpad.openstack.org/p/2019_StarlingX_Marketing_Plans Thanks, Ildikó > On 2019. Mar 19., at 16:49, Ildiko Vancsa wrote: > > Hi, > > I have a conflict this week and can’t make it to the 8am PST call. Would it work for people who are interested in attending the call to stick to 1600 UTC and have it from 9am PST? > > Thanks, > Ildikó > > From mario.alfredo.c.arevalo at intel.com Tue Mar 19 21:56:02 2019 From: mario.alfredo.c.arevalo at intel.com (Arevalo, Mario Alfredo C) Date: Tue, 19 Mar 2019 21:56:02 +0000 Subject: [Starlingx-discuss] Questions related to FM containerization In-Reply-To: References: <7242A3DC72E453498E3D783BBB134C3E9DDD2C1F@ALA-MBD.corp.ad.wrs.com> <6594B51DBE477C48AAE23675314E6C466459B811@fmsmsx107.amr.corp.intel.com>, Message-ID: <6594B51DBE477C48AAE23675314E6C466459C4C3@fmsmsx107.amr.corp.intel.com> Hi Frank, Yes, I am ready, this Thursday, any time during the morning. Thanks. Best regards. Mario. ________________________________________ From: Miller, Frank [Frank.Miller at windriver.com] Sent: Monday, March 18, 2019 11:54 AM To: Arevalo, Mario Alfredo C; Liu, Tao; starlingx-discuss at lists.starlingx.io Cc: Rowsell, Brent Subject: RE: Questions related to FM containerization Mario: I took the action last week to set up a review this week to discuss a proposal and/or answer further questions in order to get to a proposal. Are you ready for me to set up the meeting? If you need more time please suggest a day for us to meet. Frank -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Monday, March 18, 2019 1:12 AM To: Liu, Tao; starlingx-discuss at lists.starlingx.io Cc: Rowsell, Brent Subject: Re: [Starlingx-discuss] Questions related to FM containerization Hi Tao, thanks for your answer, I think, it sounds as a good plan, however I would also like to complement this with the input from Brent. This is in order to define in a granularity way, the rest of the missing parts to update the storyboard with the needed requirements to accomplish this task (e.g. fm-fault 1 pod, connected through mysql in the same pod? consuming mariadb from x port?, add POST/PUT methods etc). Thanks. Best regards. Mario. [0] https://storyboard.openstack.org/#!/story/2004008 > -----Original Message----- > From: Liu, Tao [mailto:Tao.Liu at windriver.com] > Sent: Thursday, March 14, 2019 2:54 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Questions related to FM > containerization > > Hi Mario, > > I think it would simplify the implementation significantly if we only > containerize the FM rest API service. > > You will need to add POST and PUT support in the API server and VIM > will use the rest APIs to raise the instance alarms/logs. > The alarm POST / PUT request handler will need to add alarm history > entries to the event log database table. > > The rest API service interfaces with the configured database backend directly. > Currently postgres is configured as the backend. > You will need to configure mysql as the database backend for the > containerized FM rest API service. > Openstack Horizon will also interface with containerized FM rest API > service and retrieve the instances alarm and event logs. > > I think the alarm suppression should still be managed through the > platform fm cli and horizon. > For the current release, we will not suppress the instance alarms nor > would raise SNMP traps inside the containerized services. > > Regards, > Tao Liu > > ------------------------------ > > Message: 2 > Date: Wed, 13 Mar 2019 21:52:12 +0000 > From: "Arevalo, Mario Alfredo C" > To: "starlingx-discuss at lists.starlingx.io" > > Cc: "brent.rowsell at windriver.com" > Subject: [Starlingx-discuss] Questions related to FM containerization > Message-ID: > <6594B51DBE477C48AAE23675314E6C46645994B3 at fmsmsx107.am > r.corp.intel.com> > > Content-Type: text/plain; charset="us-ascii" > > Hi Brent and team, > > This mail plans to interchange information in order to get more > granularity about the "Fault Manager" > Containerization process where the final objective is to deploy a pod > or pods which make completely match with the design of containerization architecture. > > According from the feedback received yesterday in our meeting and > taking a look to the source code and the processes which are running > in a deployed environment I can understand the possible missing parts. > > This is my understanding about the full picture and some questions > about it, please let me know if something is wrong or deviates from > the original objective/result. The storyboard [1] related to FM chart > will be finished when the FM restful API and the FM manager main > services are containerized and work correctly with the rest of the StarlingX components: > > - I think the best approach is to run a container per service and both containers > should live in the same pod. > - Both services should consume the same Docker image in order to reduce the > memory foot print. > - According the previous shared information and my code exploring I > understand the FM manager (fmManager > binary) is a service which listens in the port 8001 and executes > requests. It is launched by an script called "fminit". > At this point I have a pair of questions, is this the service > which the storyboard [1] makes reference of, > intended to have an instance in bare metal and another one > exposed by a container? > If the last questions is yes, we will have 2 instances of the > same service then they should be exposed in a > different port, and how about fm rest api service, it will just > exist in a container? > FM manager service has interaction with a PostgreSQL data base, > then I wonder how this will be handled. > Does this containerized service point to the bare metal database? > Should we add a new chart which exposes > a PostgreSQL due to the current chart tarball or just include one for MariaDB. > Then the task 28876 makes reference to modify nfv_vim[2] in order > to get the alarms information from > the container? > - Surfing in a deployed image I saw that is possible to remove alarms from the > web interface provided by > horizon, then the task 28878 makes reference to points to the FM > manager containerized service from > horizon, however it is not clear for me the task 28877 described > in the chart storyboard[1]. > > These are some points and questions which will give a better > understanding for the rest of tasks, however, possibly, I will get > more questions during this process I will be in contact with all of you. > > Thank you for your help. > > Best Regards. > Mario. > > References: > > [1] https://storyboard.openstack.org/#!/story/2004008 > [2] https://git.starlingx.io/cgit/stx-nfv/tree/nfv/nfv-vim/nfv_vim > > > > > -------------- next part -------------- An HTML attachment was > scrubbed... > URL: discuss/attachments/20190313/a63da701/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 10, Issue 64 > ************************************************* > _______________________________________________ > 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 serverascode at gmail.com Tue Mar 19 21:57:21 2019 From: serverascode at gmail.com (Curtis) Date: Tue, 19 Mar 2019 17:57:21 -0400 Subject: [Starlingx-discuss] apply-failed check logs for details Message-ID: Hi All, Running the containers install again today, ran into this. Any pointers to which logs or other troubleshooting pointers would be welcome. :) It's quite possible/likely this is of my own doing, but AFAIK was following the docs [0]. [wrsroot at controller-0 ~(keystone_admin)]$ system application-list +---------------+-----------------+-----------+--------------+-------------+ | application | manifest name | manifest | status | progress | | | | file | | | +---------------+-----------------+-----------+--------------+-------------+ | stx-openstack | armada-manifest | manifest. | apply-failed | operation | | | | yaml | | aborted, | | | | | | check logs | | | | | | for detail | | | | | | | +---------------+-----------------+-----------+--------------+-------------+ Thanks, Curtis [0]: https://wiki.openstack.org/wiki/StarlingX/Containers/Installation -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tee.Ngo at windriver.com Tue Mar 19 22:03:35 2019 From: Tee.Ngo at windriver.com (Ngo, Tee) Date: Tue, 19 Mar 2019 22:03:35 +0000 Subject: [Starlingx-discuss] apply-failed check logs for details In-Reply-To: References: Message-ID: <80ED4CE81E3D8F4099306648E95DAFE44CA0879D@ALA-MBD.corp.ad.wrs.com> Hi Curtis, Please check /var/log/sysinv.log. Search for the string “aborted!”. Tee From: Curtis [mailto:serverascode at gmail.com] Sent: March-19-19 5:57 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] apply-failed check logs for details Hi All, Running the containers install again today, ran into this. Any pointers to which logs or other troubleshooting pointers would be welcome. :) It's quite possible/likely this is of my own doing, but AFAIK was following the docs [0]. [wrsroot at controller-0 ~(keystone_admin)]$ system application-list +---------------+-----------------+-----------+--------------+-------------+ | application | manifest name | manifest | status | progress | | | | file | | | +---------------+-----------------+-----------+--------------+-------------+ | stx-openstack | armada-manifest | manifest. | apply-failed | operation | | | | yaml | | aborted, | | | | | | check logs | | | | | | for detail | | | | | | | +---------------+-----------------+-----------+--------------+-------------+ Thanks, Curtis [0]: https://wiki.openstack.org/wiki/StarlingX/Containers/Installation -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Tue Mar 19 22:05:03 2019 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Tue, 19 Mar 2019 22:05:03 +0000 Subject: [Starlingx-discuss] apply-failed check logs for details In-Reply-To: References: Message-ID: There might be some indication in /var/log/sysinv.log You can also refer to the Service Debugging section of the FAQ if you need to look at individual service logs https://wiki.openstack.org/wiki/StarlingX/Containers/FAQ Al From: Curtis [mailto:serverascode at gmail.com] Sent: Tuesday, March 19, 2019 5:57 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] apply-failed check logs for details Hi All, Running the containers install again today, ran into this. Any pointers to which logs or other troubleshooting pointers would be welcome. :) It's quite possible/likely this is of my own doing, but AFAIK was following the docs [0]. [wrsroot at controller-0 ~(keystone_admin)]$ system application-list +---------------+-----------------+-----------+--------------+-------------+ | application | manifest name | manifest | status | progress | | | | file | | | +---------------+-----------------+-----------+--------------+-------------+ | stx-openstack | armada-manifest | manifest. | apply-failed | operation | | | | yaml | | aborted, | | | | | | check logs | | | | | | for detail | | | | | | | +---------------+-----------------+-----------+--------------+-------------+ Thanks, Curtis [0]: https://wiki.openstack.org/wiki/StarlingX/Containers/Installation -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Tue Mar 19 22:12:09 2019 From: serverascode at gmail.com (Curtis) Date: Tue, 19 Mar 2019 18:12:09 -0400 Subject: [Starlingx-discuss] apply-failed check logs for details In-Reply-To: <80ED4CE81E3D8F4099306648E95DAFE44CA0879D@ALA-MBD.corp.ad.wrs.com> References: <80ED4CE81E3D8F4099306648E95DAFE44CA0879D@ALA-MBD.corp.ad.wrs.com> Message-ID: On Tue, Mar 19, 2019 at 6:04 PM Ngo, Tee wrote: > Hi Curtis, > > > > Please check /var/log/sysinv.log. Search for the string “aborted!”. > OK thanks kindly that is helpful. I see: 2019-03-19 21:45:39.540 31849 ERROR sysinv.conductor.kube_app [-] Deployment of application stx-openstack failed: failed to download one or more image(s). Interesting in that this is what I'm working on avoiding... :) Thanks, Curtis > > > Tee > > > > *From:* Curtis [mailto:serverascode at gmail.com] > *Sent:* March-19-19 5:57 PM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] apply-failed check logs for details > > > > Hi All, > > > > Running the containers install again today, ran into this. Any pointers to > which logs or other troubleshooting pointers would be welcome. :) It's > quite possible/likely this is of my own doing, but AFAIK was following the > docs [0]. > > > > [wrsroot at controller-0 ~(keystone_admin)]$ system application-list > > +---------------+-----------------+-----------+--------------+-------------+ > | application | manifest name | manifest | status | progress > | > | | | file | | > | > > +---------------+-----------------+-----------+--------------+-------------+ > | stx-openstack | armada-manifest | manifest. | apply-failed | operation > | > | | | yaml | | aborted, > | > | | | | | check logs > | > | | | | | for detail > | > | | | | | > | > > +---------------+-----------------+-----------+--------------+-------------+ > > Thanks, > > Curtis > > > > [0]: https://wiki.openstack.org/wiki/StarlingX/Containers/Installation > > > -- > > Blog: serverascode.com > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From elio.martinez.monroy at intel.com Tue Mar 19 22:19:52 2019 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Tue, 19 Mar 2019 22:19:52 +0000 Subject: [Starlingx-discuss] Duplex Direct CPE connection Message-ID: <1466AF2176E6F040BD63860D0A241BBD46CA2958@FMSMSX109.amr.corp.intel.com> Hello guys, Have everyone tried with CPE duplex direct connection? After the config_controller im not able to get the system working. Every "system" command line is showing: "aN unexpected error prevented the server from fulfilling your request" Is the configuration broken? Because not even system host-list works. I will check more details collecting all logs BR [cid:image001.png at 01CF8BAC.3B4C5DD0] Martinez Monroy, Elio. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 4914 bytes Desc: image001.png URL: From juan.p.gomez at intel.com Wed Mar 20 03:31:09 2019 From: juan.p.gomez at intel.com (Gomez, Juan P) Date: Wed, 20 Mar 2019 03:31:09 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190318 Message-ID: <0483622846A57742B81A944248DD69042FC20D4C@fmsmsx101.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Mar-18 (link) Status : Yellow =================== Virtual environment =================== Simplex: Setup 04 TCs [PASS] Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 49 TCs [FAIL] Sanity-Platform 07 TCs [FAIL] TOTAL: [4 TCs PASS] System Application apply didn't finish, 95% of progress was just completed ------------------------------ Duplex: Setup 04 TCs [PASS] Provision-Containers 01 TCs [PASS] Sanity-OpenStack 52 TCs [PASS] Sanity-Platform 05 TCs [PASS] TOTAL: [62 TCs PASS] ------------------------------ ====================== Bare Metal environment ====================== Simplex: Setup Manual Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 49 TCs [FAIL] Sanity-Platform 07 TCs [FAIL] TOTAL: [57 TCs FAIL] System Application apply didn't finish, 95% of progress was just completed ------------------------------ Duplex: Setup Manual Provision-Containers 01 TCs [PASS] Sanity-OpenStack 52 TCs [PASS] Sanity-Platform 05 TCs [PASS] TOTAL: [58 TCs PASS] ------------------------------ Standard Local Storage (2+2): Setup Manual Provision-Containers 01 TCs [PASS] Sanity-OpenStack 52 TCs [PASS] Sanity-Platform 05 TCs [PASS] TOTAL: [58 TCs PASS] ------------------------------ Standard External Storage (2+2+2): Setup Manual Provision-Containers 01 TCs Sanity-OpenStack 52 TCs Sanity-Platform 05 TCs ------------------------------ TOTAL: 58 TCs The issue was reproduced on simplex virtual and baremetal, system application-apply aborts at 95% of progress, during "processing chart: osh-openstack-ceilometer, overall completion: 95.0%" Launchpad for Simplex Bare Metal and Virtual Environment was already opened: https://bugs.launchpad.net/starlingx/+bug/1820928 Best Regards, Juan Pablo Gomez -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhu.boxiang at 99cloud.net Wed Mar 20 08:44:04 2019 From: zhu.boxiang at 99cloud.net (=?utf-8?B?5pyx5Y2a56Wl?=) Date: Wed, 20 Mar 2019 16:44:04 +0800 Subject: [Starlingx-discuss] Distro.openstack meeting minutes Mar 19th Message-ID: An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Mar 20 12:59:58 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 20 Mar 2019 12:59:58 +0000 Subject: [Starlingx-discuss] Community Call (March 20, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC0A1B907@ALA-MBD.corp.ad.wrs.com> Reminder of today's Community call - please feel free to add to the agenda at [0]. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1500_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190313T1400 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Wed Mar 20 13:32:46 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 20 Mar 2019 13:32:46 +0000 Subject: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack Distro meeting, 3/20 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35ED2B04@SHSMSX104.ccr.corp.intel.com> Agenda & Notes for 3/20 meeting: - CentOS 7.6 has been merged to master and testing was green in 3/15 Cengen image (thanks everybody who contributed to this activities). Ada will do more more testing (other than Sanity) for the master which now is 7.6. More OS related testing, like security, etc. - Ceph upgrade update (Ovidiu/Daniel, Tingjie/Yong) ceph_uprev feature branch has been rebased to master code base, with container support and based on CentOS 7.6 right now. Daniel and Tingjie both reproduced successful build and deployed 2+2+2 in VE. update: working on the new test cases on new Ceph to Ada. For StarlingX part, kick off the discussion btw Daniel, Ovidiu, Engineers from Ada's team to define the whole test plan. rado-gw: already have a workaround and a proposed fix. Daniel: rebased to master (container base), build is good, ISO is up on AIO-SX and multinode (2+2+2). Manual work around for AIO-SX. Trending to have an ISO for testing by beginning of next week. Squashing the commits after that and merge to master (planning start @ next week). dev testing is now started in the same time, Ada is starting her dry-run of testing. Saul: where is the feature branch? Ceph_uprev is based on manifest on Git. Those old reviews on Gerrit needs to be abandoned. Action here: for the next time similar activities, bring the co-dev work into feature branch and it could be more open to the rest of the community. - QAT upgrade plan (Cindy) StoryBoard: https://storyboard.openstack.org/#!/story/2004901 The work will be done on master - test will be conducted on bare-metal system with qat-dh895xcc (pci version) & qat-c62x (more modern on-board). Shanghai developers will validate on "Wolf Pass 2U 8x2.5in QAT Skylake SP Server" for simple deployment tests before provide ISO to GDC. · 3/20 ~ 3/30: technical ramping up (Haitao) · 4/1 ~ 4/12: patch development and post for review (Haitao & new CW) · 3/20 ~ 4/12: test plan review, dry-run using master build (Ada) · 4/15: test ISO provided to Ada (Haitao) · 4/15 ~ 5/3: testing and bug fixing (Ada/Haitao) · 5/6: test pass, patch review done & merge to master (Haitao & CW) - Opens (All) - None -----Original Appointment----- From: Xie, Cindy Sent: Sunday, November 4, 2018 10:27 PM To: Xie, Cindy; Sun, Austin; starlingx-discuss at lists.starlingx.io; Troyer, Dean; Shang, Dehao; Waheed, Numan; Zhu, Vivian; Hu, Yong; Jones, Bruce E; 'Khalil, Ghada'; Lin, Shuicheng; Liu, ZhipengS; 'Rowsell, Brent'; Somerville, Jim; Wold, Saul Cc: Lara, Cesar; Armstrong, Robert H; 'Hellmann, Gil'; Martinez Landa, Hayde; Gomez, Juan P; Martinez Monroy, Elio; Cobbley, David A; Shuquan Huang; 'Waines, Greg'; 'Poncea, Ovidiu'; 'Seiler, Glenn'; Fang, Liang A; 'Eslimi, Dariush'; Hu, Wei W; Perez Rodriguez, Humberto I; Arce Moreno, Abraham; 'Chen, Jacky'; 'Young, Ken'; Perez Carranza, Jose Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, March 20, 2019 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 Bill.Zvonar at windriver.com Wed Mar 20 14:25:25 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 20 Mar 2019 14:25:25 +0000 Subject: [Starlingx-discuss] Community Call (March 20, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC0A1B9DB@ALA-MBD.corp.ad.wrs.com> Notes from the Mar 20th call... - Voting Process - Ildiko's Email http://lists.starlingx.io/pipermail/starlingx-discuss/2019-January/002581.html - Election Process Etherpad: https://etherpad.openstack.org/p/StarlingX_Election_Process - the election is for the TSC members, targeted for May/June, after Denver - Community members are encouraged to comment on the process, and of course, to consider standing for election - Issues with Zuul on stx-config [Ken] - 2 issues were identified on the mailing list; are they corrected? - some, not all, reviews in stx-config are blocked - need to get this sorted out soon or it will start impacting reviews getting merged - Dean's looking into this - he knows what the issue is, not sure why it's happening yet, will work with Ken to sort it out - Release Sub-Team - readout from last week's call - Release Plan: https://docs.google.com/spreadsheets/d/1HUwbsaSerzFRuvXVB_qvoGdI0Chx1YiiA2WYHwvIoYI/edit?usp=sharing - Release Meeting Minutes: https://etherpad.openstack.org/p/stx-releases - Summary: Current release dates are not achievable. The community is currently in a re-planning phase. - Details are being worked in the Release Planning meeting. - Next meeting: Thursday March 21 2pm ET / 11am PT - Bitergia - who's tried it out? - Ildiko's Email: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-March/003421.html - Dean encouraged folks to use Bitergia over Stackalytics, we would like to not have to use Stackalytics any more - Stackalytics isn't maintained (we think) and it's not hosted by OSF -------------------------------- From: Zvonar, Bill Sent: Wednesday, March 20, 2019 9:00 AM To: starlingx-discuss at lists.starlingx.io Subject: Community Call (March 20, 2019) Reminder of today's Community call - please feel free to add to the agenda at [0]. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1500_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190313T1400 From Chris.Winnicki at windriver.com Wed Mar 20 14:55:56 2019 From: Chris.Winnicki at windriver.com (Winnicki, Chris) Date: Wed, 20 Mar 2019 14:55:56 +0000 Subject: [Starlingx-discuss] Duplex Direct CPE connection In-Reply-To: <1466AF2176E6F040BD63860D0A241BBD46CA2958@FMSMSX109.amr.corp.intel.com> References: <1466AF2176E6F040BD63860D0A241BBD46CA2958@FMSMSX109.amr.corp.intel.com> Message-ID: <7E4792BA14B1DE4BAB354DF77FE0233ABC8AB3AF@ALA-MBD.corp.ad.wrs.com> Hi Elio In Ottawa we currently have duplex-direct system installed with load: BUILD_ID="20190318T013000Z" (load details below, including parameters supplied to config_controller) - There is no issue in executing any system commands. For everyone's benefit it would be great if questions posted to the group included more system details; such as: 1) Load/build details 2) Hardware used (and or Virtual environment) 3) Config details # Buid/Load info: [wrsroot at controller-0 ~(keystone_admin)]$ cat /etc/platform/platform.conf ### ### StarlingX ### Built from master ### OS="centos" SW_VERSION="19.01" BUILD_TARGET="Host Installer" BUILD_TYPE="Formal" BUILD_ID="20190318T013000Z" JOB="STX_build_master_master" BUILD_BY="starlingx.build at cengn.ca" BUILD_NUMBER="23" BUILD_HOST="starlingx_mirror" BUILD_DATE="2019-03-18 01:30:00 +0000" # The following parameters were supplied to config_controller [VERSION] RELEASE = 19.01 [SYSTEM] SYSTEM_MODE=duplex-direct [PXEBOOT_NETWORK] PXEBOOT_CIDR = 192.168.222.0/24 [LOGICAL_INTERFACE_1] LAG_INTERFACE = N INTERFACE_MTU = 9216 INTERFACE_LINK_CAPACITY=10000 INTERFACE_PORTS = enp136s0f0 [MGMT_NETWORK] VLAN = 192 CIDR = 192.168.204.0/24 MULTICAST_CIDR = 239.0.74.16/28 DYNAMIC_ALLOCATION = Y LOGICAL_INTERFACE = LOGICAL_INTERFACE_1 [CLUSTER_NETWORK] VLAN = 193 CIDR = 192.168.205.0/24 LOGICAL_INTERFACE = LOGICAL_INTERFACE_1 [OAM_NETWORK] CIDR = 128.224.150.0/23 MULTICAST_CIDR = 239.0.74.128/28 GATEWAY = 128.224.150.1 IP_FLOATING_ADDRESS = 128.224.150.248 IP_UNIT_0_ADDRESS = 128.224.150.247 IP_UNIT_1_ADDRESS = 128.224.150.251 LOGICAL_INTERFACE = LOGICAL_INTERFACE_2 [LOGICAL_INTERFACE_2] LAG_INTERFACE = N INTERFACE_MTU = 1500 INTERFACE_PORTS = enp136s0f1 [AUTHENTICATION] ADMIN_PASSWORD = Li69nux* Regards, Chris Winnicki chris.winnicki at windriver.com 613-963-1329 ________________________________ From: Martinez Monroy, Elio [elio.martinez.monroy at intel.com] Sent: Tuesday, March 19, 2019 6:19 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Duplex Direct CPE connection Hello guys, Have everyone tried with CPE duplex direct connection? After the config_controller im not able to get the system working. Every “system” command line is showing: “aN unexpected error prevented the server from fulfilling your request” Is the configuration broken? Because not even system host-list works. I will check more details collecting all logs BR [cid:image001.png at 01CF8BAC.3B4C5DD0] Martinez Monroy, Elio. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 4914 bytes Desc: image001.png URL: From marcel at schaible-consulting.de Wed Mar 20 15:01:39 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Wed, 20 Mar 2019 16:01:39 +0100 (CET) Subject: [Starlingx-discuss] Any recommendations which image version for duplex installation? Message-ID: <1764012181.1392924.1553094099916@communicator.strato.com> Hi, which version do you recommend at the moment for a duplex installation? With the one from 20190318 I have some problems, because probably the kubernetes part of config_controller tries to connect to a google cloud instance. Since I have no access to this server it fails. Thanks Marcel From elio.martinez.monroy at intel.com Wed Mar 20 15:11:00 2019 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Wed, 20 Mar 2019 15:11:00 +0000 Subject: [Starlingx-discuss] Duplex Direct CPE connection In-Reply-To: <7E4792BA14B1DE4BAB354DF77FE0233ABC8AB3AF@ALA-MBD.corp.ad.wrs.com> References: <1466AF2176E6F040BD63860D0A241BBD46CA2958@FMSMSX109.amr.corp.intel.com> <7E4792BA14B1DE4BAB354DF77FE0233ABC8AB3AF@ALA-MBD.corp.ad.wrs.com> Message-ID: <1466AF2176E6F040BD63860D0A241BBD46CA2C52@FMSMSX109.amr.corp.intel.com> Thanks Chris, will double check that during the day. BR Elio From: Winnicki, Chris [mailto:Chris.Winnicki at windriver.com] Sent: Wednesday, March 20, 2019 8:56 AM To: Martinez Monroy, Elio ; starlingx-discuss at lists.starlingx.io Subject: RE: Duplex Direct CPE connection Hi Elio In Ottawa we currently have duplex-direct system installed with load: BUILD_ID="20190318T013000Z" (load details below, including parameters supplied to config_controller) - There is no issue in executing any system commands. For everyone's benefit it would be great if questions posted to the group included more system details; such as: 1) Load/build details 2) Hardware used (and or Virtual environment) 3) Config details # Buid/Load info: [wrsroot at controller-0 ~(keystone_admin)]$ cat /etc/platform/platform.conf ### ### StarlingX ### Built from master ### OS="centos" SW_VERSION="19.01" BUILD_TARGET="Host Installer" BUILD_TYPE="Formal" BUILD_ID="20190318T013000Z" JOB="STX_build_master_master" BUILD_BY="starlingx.build at cengn.ca" BUILD_NUMBER="23" BUILD_HOST="starlingx_mirror" BUILD_DATE="2019-03-18 01:30:00 +0000" # The following parameters were supplied to config_controller [VERSION] RELEASE = 19.01 [SYSTEM] SYSTEM_MODE=duplex-direct [PXEBOOT_NETWORK] PXEBOOT_CIDR = 192.168.222.0/24 [LOGICAL_INTERFACE_1] LAG_INTERFACE = N INTERFACE_MTU = 9216 INTERFACE_LINK_CAPACITY=10000 INTERFACE_PORTS = enp136s0f0 [MGMT_NETWORK] VLAN = 192 CIDR = 192.168.204.0/24 MULTICAST_CIDR = 239.0.74.16/28 DYNAMIC_ALLOCATION = Y LOGICAL_INTERFACE = LOGICAL_INTERFACE_1 [CLUSTER_NETWORK] VLAN = 193 CIDR = 192.168.205.0/24 LOGICAL_INTERFACE = LOGICAL_INTERFACE_1 [OAM_NETWORK] CIDR = 128.224.150.0/23 MULTICAST_CIDR = 239.0.74.128/28 GATEWAY = 128.224.150.1 IP_FLOATING_ADDRESS = 128.224.150.248 IP_UNIT_0_ADDRESS = 128.224.150.247 IP_UNIT_1_ADDRESS = 128.224.150.251 LOGICAL_INTERFACE = LOGICAL_INTERFACE_2 [LOGICAL_INTERFACE_2] LAG_INTERFACE = N INTERFACE_MTU = 1500 INTERFACE_PORTS = enp136s0f1 [AUTHENTICATION] ADMIN_PASSWORD = Li69nux* Regards, Chris Winnicki chris.winnicki at windriver.com 613-963-1329 ________________________________ From: Martinez Monroy, Elio [elio.martinez.monroy at intel.com] Sent: Tuesday, March 19, 2019 6:19 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Duplex Direct CPE connection Hello guys, Have everyone tried with CPE duplex direct connection? After the config_controller im not able to get the system working. Every "system" command line is showing: "aN unexpected error prevented the server from fulfilling your request" Is the configuration broken? Because not even system host-list works. I will check more details collecting all logs BR [cid:image001.png at 01CF8BAC.3B4C5DD0] Martinez Monroy, Elio. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 4914 bytes Desc: image001.png URL: From bruce.e.jones at intel.com Wed Mar 20 16:08:01 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 20 Mar 2019 16:08:01 +0000 Subject: [Starlingx-discuss] Distro.openstack meeting minutes Mar 19th In-Reply-To: References: Message-ID: <9A85D2917C58154C960D95352B22818BD0704C00@fmsmsx123.amr.corp.intel.com> Thank you, Zhu. It looks like the Nova folks think this code might be working as designed. Nova experts – do we agree? brucej From: 朱博祥 [mailto:zhu.boxiang at 99cloud.net] Sent: Wednesday, March 20, 2019 1:44 AM To: Jones, Bruce E ; Gerry.Kopec at windriver.com; starlingx-discuss Subject: Re: [Starlingx-discuss] Distro.openstack meeting minutes Mar 19th Hi Bruce and Gerry, For this review[1], in fact, I also have submitted a bug to the launchpad[2] to discuss. Matt R set this to 'Option' status. I take the affinity/anti-affinity as an example for booting instances with force_hosts/force_nodes. When we use the force_hosts/force_nodes, it will break the affinity/anti-affinity server_group. The openstack discuss mailing list is here[3]. After that, Nova community(Matt R) gave -2 on the review. And he thought this would need a bp and some design discussion for alternatives. So he added this to the PTG agenda for Train[4] : ) [1] https://review.openstack.org/#/c/641908/ [2] https://bugs.launchpad.net/nova/+bug/1820018 [3] http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003813.html [4] https://etherpad.openstack.org/p/nova-ptg-train Best Regards Boxiang On 3/20/2019 03:16,Jones, Bruce E wrote: Overall plan and status tracking document: https://etherpad.openstack.org/p/stx-openstack-patch-refactoring • Details: https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit?usp=sharing Story boards: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.distro.openstack&project_group_id=86 Meeting agenda and notes for the 3/19 meeting • 3/12 email from Dean: * This is the process I imagined and outlined in the meeting: • When Nova creates their stable/stein branch at RC1 time (week of Mar 19th) we will create a mirror of that in starlingx-staging/nova as stx/stein. • AR Dean to pull our branch next week, to be populated from backports • This branch will be periodically updated from stable/stein as backports appear there from the Nova team. • As items on our list of upstream changes land in master (Train) we will backport them to stx/stein for StarlingX to pick up. • There may be times that work upstream has not yet merged but is sufficiently complete that we would backport early to meet a StarlingX time requirement, with the expectation that it be brought current with what finally does merge after that happens. • Upstream work that is not yet complete that we want to backport to meet a StarlingX time requirement should be worked upstream to get it to the state mentioned above to enable us to backport it to stx/stein. * Still to be decided/confirmed: • We need to have some measure of testing in stx/stein, I will look in to what we can run from OpenStack Zuul directly. • We can switch Sanity testing to the new branch. • We would have to update / add Zuul jobs to allow the already defined Nova Zuul jobs to run out of github staging • We would have to add a trigger to the github to watch PRs and start Zuul • I like the idea of continuing to have only a small number of people with the ability to commit to the staging repo • We may want to consider the tactic of keeping our additional commits in stx/stein rebased on top of the upstream stable/stein rather than merging in upstream backports. This would be inconvenient for those with local copies of the branch after each rebase but it would keep the SHAs in the upstream commits the same. (I am not convinced yet that we should do this, still sorting it out) • Do we rebase backports? • We think that the right approach will be to take these as they come in. Make it easy on the developers. Concern is about how to manage conflicts with upstream Nova changes. • How frequently do we rebase? Weekly? When we need to? At the very least we want to do one rebase just before code freeze (and after stable Stein is released). • We marked up the spreadsheet with a new "Candidate for backport" column and identified 11 changes that are candidates • NUMA live migration WIP code - can/should we jumpstart integration of it with STX? * Code upstream is in reasonable shape and needs two small fixes. Gerry @ WR has been testing it against pinning / not pinned, hugepages vs none. Gerry has posted review comments with suggested fixes. * Bruce to stop the work in SH on this and let Gerry drive. * Dean to post a message to Nova calling out our need for a fork and would like to minimize it, by asking that the changes we want hit Train early. • Re: https://review.openstack.org/#/c/641908/ - this didn't get a launchpad filed, so the Nova community (Matt R) put a -2 on the review since it looks like a new feature. -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Wed Mar 20 16:54:03 2019 From: serverascode at gmail.com (Curtis) Date: Wed, 20 Mar 2019 12:54:03 -0400 Subject: [Starlingx-discuss] Any recommendations which image version for duplex installation? In-Reply-To: <1764012181.1392924.1553094099916@communicator.strato.com> References: <1764012181.1392924.1553094099916@communicator.strato.com> Message-ID: On Wed, Mar 20, 2019 at 11:03 AM Marcel Schaible < marcel at schaible-consulting.de> wrote: > Hi, > > which version do you recommend at the moment for a duplex installation? > > With the one from 20190318 I have some problems, because probably the > kubernetes part of config_controller tries to connect to a google cloud > instance. Since I have no access to this server it fails. > Someone on this list will correct me if I'm wrong, but I'd be using the latest image available. There is a tremendous amount of working being done as the project moves towards a release, but I would expect that the latest image available is usually the best for testing with. Thanks, Curtis > > Thanks > > Marcel > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcel at schaible-consulting.de Wed Mar 20 17:09:06 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Wed, 20 Mar 2019 18:09:06 +0100 (CET) Subject: [Starlingx-discuss] Any recommendations which image version for duplex installation? In-Reply-To: References: <1764012181.1392924.1553094099916@communicator.strato.com> Message-ID: <609025849.1401614.1553101746793@communicator.strato.com> The problem with the greatest latest version is the external dependency of kubernetes. I am not getting a connection out to google drive from my lab. Since I don't want to use kubernetes/docker at the moment is it ok to throw them out of the worker and controller manifest? > Curtis hat am 20. März 2019 um 17:54 geschrieben: > > > On Wed, Mar 20, 2019 at 11:03 AM Marcel Schaible < > marcel at schaible-consulting.de> wrote: > > > Hi, > > > > which version do you recommend at the moment for a duplex installation? > > > > With the one from 20190318 I have some problems, because probably the > > kubernetes part of config_controller tries to connect to a google cloud > > instance. Since I have no access to this server it fails. > > > > Someone on this list will correct me if I'm wrong, but I'd be using the > latest image available. There is a tremendous amount of working being done > as the project moves towards a release, but I would expect that the latest > image available is usually the best for testing with. > > Thanks, > Curtis > > > > > > > Thanks > > > > Marcel > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > -- > Blog: serverascode.com From serverascode at gmail.com Wed Mar 20 17:59:39 2019 From: serverascode at gmail.com (Curtis) Date: Wed, 20 Mar 2019 13:59:39 -0400 Subject: [Starlingx-discuss] Any recommendations which image version for duplex installation? In-Reply-To: <609025849.1401614.1553101746793@communicator.strato.com> References: <1764012181.1392924.1553094099916@communicator.strato.com> <609025849.1401614.1553101746793@communicator.strato.com> Message-ID: On Wed, Mar 20, 2019 at 1:09 PM Marcel Schaible < marcel at schaible-consulting.de> wrote: > The problem with the greatest latest version is the external dependency of > kubernetes. I am not getting a connection out to google drive from my lab. > > When you say google drive, do you mean downloading docker images from remote repositories? Or is it trying to connect to some other service from google? Does your lab have some security restrictions to accessing external resources? Thanks, Curtis > Since I don't want to use kubernetes/docker at the moment is it ok to > throw them out of the worker and controller manifest? > > > Curtis hat am 20. März 2019 um 17:54 > geschrieben: > > > > > > On Wed, Mar 20, 2019 at 11:03 AM Marcel Schaible < > > marcel at schaible-consulting.de> wrote: > > > > > Hi, > > > > > > which version do you recommend at the moment for a duplex installation? > > > > > > With the one from 20190318 I have some problems, because probably the > > > kubernetes part of config_controller tries to connect to a google > cloud > > > instance. Since I have no access to this server it fails. > > > > > > > Someone on this list will correct me if I'm wrong, but I'd be using the > > latest image available. There is a tremendous amount of working being > done > > as the project moves towards a release, but I would expect that the > latest > > image available is usually the best for testing with. > > > > Thanks, > > Curtis > > > > > > > > > > > > Thanks > > > > > > Marcel > > > > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > > > > > -- > > Blog: serverascode.com > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Wed Mar 20 19:26:06 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Wed, 20 Mar 2019 19:26:06 +0000 Subject: [Starlingx-discuss] Questions related to FM containerization In-Reply-To: <6594B51DBE477C48AAE23675314E6C466459C4C3@fmsmsx107.amr.corp.intel.com> References: <7242A3DC72E453498E3D783BBB134C3E9DDD2C1F@ALA-MBD.corp.ad.wrs.com> <6594B51DBE477C48AAE23675314E6C466459B811@fmsmsx107.amr.corp.intel.com>, <6594B51DBE477C48AAE23675314E6C466459C4C3@fmsmsx107.amr.corp.intel.com> Message-ID: Mario: I can't meet Thursday but can meet Friday. I'll set it up for 1600 UTC (8am PDT / 11am EDT). We'll use the StarlingX zoom link. Frank -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Tuesday, March 19, 2019 5:56 PM To: Miller, Frank; Liu, Tao; starlingx-discuss at lists.starlingx.io Cc: Rowsell, Brent Subject: RE: Questions related to FM containerization Hi Frank, Yes, I am ready, this Thursday, any time during the morning. Thanks. Best regards. Mario. ________________________________________ From: Miller, Frank [Frank.Miller at windriver.com] Sent: Monday, March 18, 2019 11:54 AM To: Arevalo, Mario Alfredo C; Liu, Tao; starlingx-discuss at lists.starlingx.io Cc: Rowsell, Brent Subject: RE: Questions related to FM containerization Mario: I took the action last week to set up a review this week to discuss a proposal and/or answer further questions in order to get to a proposal. Are you ready for me to set up the meeting? If you need more time please suggest a day for us to meet. Frank -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Monday, March 18, 2019 1:12 AM To: Liu, Tao; starlingx-discuss at lists.starlingx.io Cc: Rowsell, Brent Subject: Re: [Starlingx-discuss] Questions related to FM containerization Hi Tao, thanks for your answer, I think, it sounds as a good plan, however I would also like to complement this with the input from Brent. This is in order to define in a granularity way, the rest of the missing parts to update the storyboard with the needed requirements to accomplish this task (e.g. fm-fault 1 pod, connected through mysql in the same pod? consuming mariadb from x port?, add POST/PUT methods etc). Thanks. Best regards. Mario. [0] https://storyboard.openstack.org/#!/story/2004008 > -----Original Message----- > From: Liu, Tao [mailto:Tao.Liu at windriver.com] > Sent: Thursday, March 14, 2019 2:54 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Questions related to FM > containerization > > Hi Mario, > > I think it would simplify the implementation significantly if we only > containerize the FM rest API service. > > You will need to add POST and PUT support in the API server and VIM > will use the rest APIs to raise the instance alarms/logs. > The alarm POST / PUT request handler will need to add alarm history > entries to the event log database table. > > The rest API service interfaces with the configured database backend directly. > Currently postgres is configured as the backend. > You will need to configure mysql as the database backend for the > containerized FM rest API service. > Openstack Horizon will also interface with containerized FM rest API > service and retrieve the instances alarm and event logs. > > I think the alarm suppression should still be managed through the > platform fm cli and horizon. > For the current release, we will not suppress the instance alarms nor > would raise SNMP traps inside the containerized services. > > Regards, > Tao Liu > > ------------------------------ > > Message: 2 > Date: Wed, 13 Mar 2019 21:52:12 +0000 > From: "Arevalo, Mario Alfredo C" > To: "starlingx-discuss at lists.starlingx.io" > > Cc: "brent.rowsell at windriver.com" > Subject: [Starlingx-discuss] Questions related to FM containerization > Message-ID: > <6594B51DBE477C48AAE23675314E6C46645994B3 at fmsmsx107.am > r.corp.intel.com> > > Content-Type: text/plain; charset="us-ascii" > > Hi Brent and team, > > This mail plans to interchange information in order to get more > granularity about the "Fault Manager" > Containerization process where the final objective is to deploy a pod > or pods which make completely match with the design of containerization architecture. > > According from the feedback received yesterday in our meeting and > taking a look to the source code and the processes which are running > in a deployed environment I can understand the possible missing parts. > > This is my understanding about the full picture and some questions > about it, please let me know if something is wrong or deviates from > the original objective/result. The storyboard [1] related to FM chart > will be finished when the FM restful API and the FM manager main > services are containerized and work correctly with the rest of the StarlingX components: > > - I think the best approach is to run a container per service and both containers > should live in the same pod. > - Both services should consume the same Docker image in order to reduce the > memory foot print. > - According the previous shared information and my code exploring I > understand the FM manager (fmManager > binary) is a service which listens in the port 8001 and executes > requests. It is launched by an script called "fminit". > At this point I have a pair of questions, is this the service > which the storyboard [1] makes reference of, > intended to have an instance in bare metal and another one > exposed by a container? > If the last questions is yes, we will have 2 instances of the > same service then they should be exposed in a > different port, and how about fm rest api service, it will just > exist in a container? > FM manager service has interaction with a PostgreSQL data base, > then I wonder how this will be handled. > Does this containerized service point to the bare metal database? > Should we add a new chart which exposes > a PostgreSQL due to the current chart tarball or just include one for MariaDB. > Then the task 28876 makes reference to modify nfv_vim[2] in order > to get the alarms information from > the container? > - Surfing in a deployed image I saw that is possible to remove alarms from the > web interface provided by > horizon, then the task 28878 makes reference to points to the FM > manager containerized service from > horizon, however it is not clear for me the task 28877 described > in the chart storyboard[1]. > > These are some points and questions which will give a better > understanding for the rest of tasks, however, possibly, I will get > more questions during this process I will be in contact with all of you. > > Thank you for your help. > > Best Regards. > Mario. > > References: > > [1] https://storyboard.openstack.org/#!/story/2004008 > [2] https://git.starlingx.io/cgit/stx-nfv/tree/nfv/nfv-vim/nfv_vim > > > > > -------------- next part -------------- An HTML attachment was > scrubbed... > URL: discuss/attachments/20190313/a63da701/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 10, Issue 64 > ************************************************* > _______________________________________________ > 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 mario.alfredo.c.arevalo at intel.com Wed Mar 20 19:28:48 2019 From: mario.alfredo.c.arevalo at intel.com (Arevalo, Mario Alfredo C) Date: Wed, 20 Mar 2019 19:28:48 +0000 Subject: [Starlingx-discuss] Questions related to FM containerization In-Reply-To: References: <7242A3DC72E453498E3D783BBB134C3E9DDD2C1F@ALA-MBD.corp.ad.wrs.com> <6594B51DBE477C48AAE23675314E6C466459B811@fmsmsx107.amr.corp.intel.com>, <6594B51DBE477C48AAE23675314E6C466459C4C3@fmsmsx107.amr.corp.intel.com>, Message-ID: <6594B51DBE477C48AAE23675314E6C466459CE18@fmsmsx107.amr.corp.intel.com> This Friday is a good day for me. thanks! Best regards. Mario. ________________________________________ From: Miller, Frank [Frank.Miller at windriver.com] Sent: Wednesday, March 20, 2019 12:26 PM To: Arevalo, Mario Alfredo C; Liu, Tao; starlingx-discuss at lists.starlingx.io Cc: Rowsell, Brent Subject: RE: Questions related to FM containerization Mario: I can't meet Thursday but can meet Friday. I'll set it up for 1600 UTC (8am PDT / 11am EDT). We'll use the StarlingX zoom link. Frank -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Tuesday, March 19, 2019 5:56 PM To: Miller, Frank; Liu, Tao; starlingx-discuss at lists.starlingx.io Cc: Rowsell, Brent Subject: RE: Questions related to FM containerization Hi Frank, Yes, I am ready, this Thursday, any time during the morning. Thanks. Best regards. Mario. ________________________________________ From: Miller, Frank [Frank.Miller at windriver.com] Sent: Monday, March 18, 2019 11:54 AM To: Arevalo, Mario Alfredo C; Liu, Tao; starlingx-discuss at lists.starlingx.io Cc: Rowsell, Brent Subject: RE: Questions related to FM containerization Mario: I took the action last week to set up a review this week to discuss a proposal and/or answer further questions in order to get to a proposal. Are you ready for me to set up the meeting? If you need more time please suggest a day for us to meet. Frank -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Monday, March 18, 2019 1:12 AM To: Liu, Tao; starlingx-discuss at lists.starlingx.io Cc: Rowsell, Brent Subject: Re: [Starlingx-discuss] Questions related to FM containerization Hi Tao, thanks for your answer, I think, it sounds as a good plan, however I would also like to complement this with the input from Brent. This is in order to define in a granularity way, the rest of the missing parts to update the storyboard with the needed requirements to accomplish this task (e.g. fm-fault 1 pod, connected through mysql in the same pod? consuming mariadb from x port?, add POST/PUT methods etc). Thanks. Best regards. Mario. [0] https://storyboard.openstack.org/#!/story/2004008 > -----Original Message----- > From: Liu, Tao [mailto:Tao.Liu at windriver.com] > Sent: Thursday, March 14, 2019 2:54 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Questions related to FM > containerization > > Hi Mario, > > I think it would simplify the implementation significantly if we only > containerize the FM rest API service. > > You will need to add POST and PUT support in the API server and VIM > will use the rest APIs to raise the instance alarms/logs. > The alarm POST / PUT request handler will need to add alarm history > entries to the event log database table. > > The rest API service interfaces with the configured database backend directly. > Currently postgres is configured as the backend. > You will need to configure mysql as the database backend for the > containerized FM rest API service. > Openstack Horizon will also interface with containerized FM rest API > service and retrieve the instances alarm and event logs. > > I think the alarm suppression should still be managed through the > platform fm cli and horizon. > For the current release, we will not suppress the instance alarms nor > would raise SNMP traps inside the containerized services. > > Regards, > Tao Liu > > ------------------------------ > > Message: 2 > Date: Wed, 13 Mar 2019 21:52:12 +0000 > From: "Arevalo, Mario Alfredo C" > To: "starlingx-discuss at lists.starlingx.io" > > Cc: "brent.rowsell at windriver.com" > Subject: [Starlingx-discuss] Questions related to FM containerization > Message-ID: > <6594B51DBE477C48AAE23675314E6C46645994B3 at fmsmsx107.am > r.corp.intel.com> > > Content-Type: text/plain; charset="us-ascii" > > Hi Brent and team, > > This mail plans to interchange information in order to get more > granularity about the "Fault Manager" > Containerization process where the final objective is to deploy a pod > or pods which make completely match with the design of containerization architecture. > > According from the feedback received yesterday in our meeting and > taking a look to the source code and the processes which are running > in a deployed environment I can understand the possible missing parts. > > This is my understanding about the full picture and some questions > about it, please let me know if something is wrong or deviates from > the original objective/result. The storyboard [1] related to FM chart > will be finished when the FM restful API and the FM manager main > services are containerized and work correctly with the rest of the StarlingX components: > > - I think the best approach is to run a container per service and both containers > should live in the same pod. > - Both services should consume the same Docker image in order to reduce the > memory foot print. > - According the previous shared information and my code exploring I > understand the FM manager (fmManager > binary) is a service which listens in the port 8001 and executes > requests. It is launched by an script called "fminit". > At this point I have a pair of questions, is this the service > which the storyboard [1] makes reference of, > intended to have an instance in bare metal and another one > exposed by a container? > If the last questions is yes, we will have 2 instances of the > same service then they should be exposed in a > different port, and how about fm rest api service, it will just > exist in a container? > FM manager service has interaction with a PostgreSQL data base, > then I wonder how this will be handled. > Does this containerized service point to the bare metal database? > Should we add a new chart which exposes > a PostgreSQL due to the current chart tarball or just include one for MariaDB. > Then the task 28876 makes reference to modify nfv_vim[2] in order > to get the alarms information from > the container? > - Surfing in a deployed image I saw that is possible to remove alarms from the > web interface provided by > horizon, then the task 28878 makes reference to points to the FM > manager containerized service from > horizon, however it is not clear for me the task 28877 described > in the chart storyboard[1]. > > These are some points and questions which will give a better > understanding for the rest of tasks, however, possibly, I will get > more questions during this process I will be in contact with all of you. > > Thank you for your help. > > Best Regards. > Mario. > > References: > > [1] https://storyboard.openstack.org/#!/story/2004008 > [2] https://git.starlingx.io/cgit/stx-nfv/tree/nfv/nfv-vim/nfv_vim > > > > > -------------- next part -------------- An HTML attachment was > scrubbed... > URL: discuss/attachments/20190313/a63da701/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 10, Issue 64 > ************************************************* > _______________________________________________ > 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 corvus at inaugust.com Wed Mar 20 19:57:17 2019 From: corvus at inaugust.com (James E. Blair) Date: Wed, 20 Mar 2019 12:57:17 -0700 Subject: [Starlingx-discuss] Migrating git repos to OpenDev Message-ID: <87woktnwte.fsf@meyer.lemoncheese.net> corvus at inaugust.com (James E. Blair) writes: > Hi, > > As discussed in November[1], the OpenStack project infrastructure is > being rebranded as "OpenDev" to better support a wider community of > projects. > > We are nearly ready to perform the part of this transition with the > largest impact: moving the authoritative git repositories for existing > projects. Working with the folks representing each of the affected OSF projects, we've scheduled the migration for Friday, April 19, 2019. This is shortly after the next OpenStack release. Please see [2] for further details about what this will involve. [1] http://lists.openstack.org/pipermail/openstack-dev/2018-November/136403.html [2] http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html -Jim From serverascode at gmail.com Wed Mar 20 20:31:27 2019 From: serverascode at gmail.com (Curtis) Date: Wed, 20 Mar 2019 16:31:27 -0400 Subject: [Starlingx-discuss] Offline docker images install? In-Reply-To: <11547091552947706@myt3-964eae3a5b05.qloud-c.yandex.net> References: <11547091552947706@myt3-964eae3a5b05.qloud-c.yandex.net> Message-ID: On Mon, Mar 18, 2019 at 6:21 PM Erich Cordoba wrote: > Cristopher has setup an internal/local docker registry with all needed > images. I think he can (tomorrow, today is Mexican holiday) give more > insights on this. > > If anyone has any hints on this, I'm running into a problem where kubeadm init seems to be failing during config_controller when using an alternative registry for all the public ones. Not finding meaningful error messages yet. Thanks, Curtis > -Erich > > -- > Sent from Yandex.Mail for mobile > > 18.03.2019, 16:17, "Curtis" : > > Hi All, > > I apologise if this has been covered somewhere, did a bit of > searching...what if I want to install all the docker images for stx from an > offline file. Was there some mention of these being included in the ISO > (thought maybe I'd heard that), or can I import them prior to installation > of openstack? > > Mostly I am coming from the perspective of the upcoming stx workshop at > the openinfra summit. Would like to avoid students having to all download > at the same time, or all hitting a local proxy, if possible. > > Sorry if I missed it. > > Thanks, > Curtis > > PS. Thanks for the docs at > https://wiki.openstack.org/wiki/StarlingX/Containers/Installation ran > through it today, all good. :) > > -- > Blog: serverascode.com > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.l.tullis at intel.com Wed Mar 20 20:54:42 2019 From: michael.l.tullis at intel.com (Tullis, Michael L) Date: Wed, 20 Mar 2019 20:54:42 +0000 Subject: [Starlingx-discuss] [docs][meetings] docs team meeting minutes 3/20/2019 Message-ID: <3808363B39586544A6839C76CF81445EA1AD8B16@ORSMSX104.amr.corp.intel.com> For notes and new action items from our docs team meeting today, see our etherpad: https://etherpad.openstack.org/p/stx-documentation Join us if you have interest in StarlingX docs! We meet Wednesdays, and call logistics are here: https://wiki.openstack.org/wiki/Starlingx/Meetings. -- Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: From cesar.lara at intel.com Wed Mar 20 23:20:28 2019 From: cesar.lara at intel.com (Lara, Cesar) Date: Wed, 20 Mar 2019 23:20:28 +0000 Subject: [Starlingx-discuss] [build][meetings] Build team meeting agenda for 03/21/2019 Message-ID: <0B566C62EC792145B40E29EFEBF1AB471061D484@fmsmsx104.amr.corp.intel.com> Build team meeting Agenda for 03/21/2019 - Update on build, bugs and stories for next release - Multi Layer build proposal - Mirror tool - Opens Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Thu Mar 21 00:40:38 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 21 Mar 2019 00:40:38 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190320 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Mar-20 (link) Status: YELLOW =================== Virtual environment =================== Simplex: Setup 04 TCs [FAIL] Provision-Containers 01 TCs [FAIL] Sanity-OpenStack 49 TCs [FAIL] Sanity-Platform 07 TCs [FAIL] TOTAL: [61 TCs FAIL] ------------------------------ Duplex: Setup 04 TCs [PASS] Provision-Containers 01 TCs [PASS] Sanity-OpenStack 52 TCs [PASS] Sanity-Platform 05 TCs [PASS] TOTAL: [62 TCs PASS] ------------------------------ ====================== Bare Metal environment ====================== Simplex: Setup Manual Provision-Containers 01 TCs [PASS] Sanity-OpenStack 49 TCs [PASS] Sanity-Platform 07 TCs [PASS] TOTAL: [57 TCs PASS] ------------------------------ Duplex: Setup Manual Provision-Containers 01 TCs [PASS] Sanity-OpenStack 52 TCs [PASS] Sanity-Platform 05 TCs [PASS] TOTAL: [58 TCs PASS] ------------------------------ Standard Local Storage (2+2+2): Setup Manual Provision-Containers 01 TCs [PASS] Sanity-OpenStack 52 TCs [PASS] Sanity-Platform 05 TCs [PASS] TOTAL: [58 TCs PASS] Simplex - application-apply fails at 95% - ceilometer pod https://bugs.launchpad.net/starlingx/+bug/1820928 Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Thu Mar 21 03:46:37 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 20 Mar 2019 23:46:37 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 197 - Failure! Message-ID: <1655782213.119.1553139998674.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 197 Status: Failure Timestamp: 20190321T021448Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190321T013000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190321T013000Z DOCKER_BUILD_ID: jenkins-master-20190321T013000Z-builder MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190321T013000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190321T013000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Thu Mar 21 03:46:41 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 20 Mar 2019 23:46:41 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 26 - Failure! Message-ID: <1635116869.122.1553140002412.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 26 Status: Failure Timestamp: 20190321T013000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190321T013000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false BUILD_CONTAINERS_ZZZ: false From serverascode at gmail.com Thu Mar 21 12:47:15 2019 From: serverascode at gmail.com (Curtis) Date: Thu, 21 Mar 2019 08:47:15 -0400 Subject: [Starlingx-discuss] Offline docker images install? In-Reply-To: References: <11547091552947706@myt3-964eae3a5b05.qloud-c.yandex.net> Message-ID: On Wed, Mar 20, 2019 at 4:31 PM Curtis wrote: > > > On Mon, Mar 18, 2019 at 6:21 PM Erich Cordoba > wrote: > >> Cristopher has setup an internal/local docker registry with all needed >> images. I think he can (tomorrow, today is Mexican holiday) give more >> insights on this. >> >> > If anyone has any hints on this, I'm running into a problem where kubeadm > init seems to be failing during config_controller when using an alternative > registry for all the public ones. Not finding meaningful error messages yet. > > FYI I entered a bug report: https://bugs.launchpad.net/starlingx/+bug/1821090 Thanks, Curtis > Thanks, > Curtis > > > >> -Erich >> >> -- >> Sent from Yandex.Mail for mobile >> >> 18.03.2019, 16:17, "Curtis" : >> >> Hi All, >> >> I apologise if this has been covered somewhere, did a bit of >> searching...what if I want to install all the docker images for stx from an >> offline file. Was there some mention of these being included in the ISO >> (thought maybe I'd heard that), or can I import them prior to installation >> of openstack? >> >> Mostly I am coming from the perspective of the upcoming stx workshop at >> the openinfra summit. Would like to avoid students having to all download >> at the same time, or all hitting a local proxy, if possible. >> >> Sorry if I missed it. >> >> Thanks, >> Curtis >> >> PS. Thanks for the docs at >> https://wiki.openstack.org/wiki/StarlingX/Containers/Installation ran >> through it today, all good. :) >> >> -- >> Blog: serverascode.com >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> > > -- > Blog: serverascode.com > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ian.Jolliffe at windriver.com Thu Mar 21 12:49:43 2019 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Thu, 21 Mar 2019 12:49:43 +0000 Subject: [Starlingx-discuss] [TSC] Minutes 3/14 Message-ID: Hi all; Below are the minutes and notes from the March 14th StarlingX TSC meeting. TSC election plan: Ian, Dean, Ana and Miguel will be up for election - + the open position. Consensus is better post PTG/Summit is the recommendation - check if there is an issue with the release? Current proposal week of June 10th - will confirm next week. Curtis - Packet.com PoC/Project Just recieved initial MOU from Packet.com Under review by Curtis Ildiko will have someone from Foundation, once TSC has reviewed Opportunities/ideas to move forward with Packet 1)CI/CD use 1 as a learning opportunity Deployment and HW learnings will happen 2)Performance testing Need to baseline which hw is being leveraged and then test consistently. Need to document choices. 3) short term edge project for CBRS shows a great use case Brian - from packet - initial sites are coming on line. Curtis/Shuquan - Summit Workshop John @packet.com provided us access to an initial project in packet, have created a couple of test nodes, discussing how to proceed with developing workshop. Initial deployment on baremetal underway testing out initial virtual machines Need to determine which release to use for this Workshop Dean - Openstack infra team - transitioning to OpenDev group Means to us that our host names for the Git Repos - an opportunity to rename git repos Plan is to put us in an StarlingX top level projects Https://etherpad.openstack.org/p/stx-opendev Like to have final disucssion and TSC review at 3/21 TSC meeting Tech leads - please review and provide input Consistent approach to naming across repos. (choose meaningless or functional not a mix) Saul - asks do we want an experimental repo ? risk is people will assume they are real or supported? could put experimental items in git hub. see email – from Saul PTG - when to do planning for next release plans Getting close Spreadsheet - ethercalc - from Face to Face is an initial starting point, https://ethercalc.openstack.org/pj7rsux1c461 Standing approach the summit StarlingX - day is secured - day TBD -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Thu Mar 21 14:23:30 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Thu, 21 Mar 2019 14:23:30 +0000 Subject: [Starlingx-discuss] Offline docker images install? In-Reply-To: References: <11547091552947706@myt3-964eae3a5b05.qloud-c.yandex.net> Message-ID: I’ve assigned the LP to Mingyuan as he was prime on implementing this feature. Mingyuan can you please provide some assistance to Curtis with his setup? Thanks. Frank From: Curtis [mailto:serverascode at gmail.com] Sent: Thursday, March 21, 2019 8:47 AM To: Erich Cordoba Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Offline docker images install? On Wed, Mar 20, 2019 at 4:31 PM Curtis > wrote: On Mon, Mar 18, 2019 at 6:21 PM Erich Cordoba > wrote: Cristopher has setup an internal/local docker registry with all needed images. I think he can (tomorrow, today is Mexican holiday) give more insights on this. If anyone has any hints on this, I'm running into a problem where kubeadm init seems to be failing during config_controller when using an alternative registry for all the public ones. Not finding meaningful error messages yet. FYI I entered a bug report: https://bugs.launchpad.net/starlingx/+bug/1821090 Thanks, Curtis Thanks, Curtis -Erich -- Sent from Yandex.Mail for mobile 18.03.2019, 16:17, "Curtis" >: Hi All, I apologise if this has been covered somewhere, did a bit of searching...what if I want to install all the docker images for stx from an offline file. Was there some mention of these being included in the ISO (thought maybe I'd heard that), or can I import them prior to installation of openstack? Mostly I am coming from the perspective of the upcoming stx workshop at the openinfra summit. Would like to avoid students having to all download at the same time, or all hitting a local proxy, if possible. Sorry if I missed it. Thanks, Curtis PS. Thanks for the docs at https://wiki.openstack.org/wiki/StarlingX/Containers/Installation ran through it today, all good. :) -- Blog: serverascode.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Blog: serverascode.com -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Thu Mar 21 15:02:50 2019 From: scott.little at windriver.com (Scott Little) Date: Thu, 21 Mar 2019 11:02:50 -0400 Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 26 - Failure! In-Reply-To: <1635116869.122.1553140002412.JavaMail.javamailuser@localhost> References: <1635116869.122.1553140002412.JavaMail.javamailuser@localhost> Message-ID: <2c56b8d9-5549-5f6b-1338-9c5935814f3f@windriver.com> Build failed on package openstack-helm... ...Successfully got an update from the "local" chart repository Update Complete. ⎈Happy Helming!⎈ Saving 1 charts Downloading helm-toolkit from repo http://localhost:8879/charts Deleting outdated charts if [ -d neutron ]; then helm lint neutron; fi ==> Linting neutron [ERROR] templates/daemonset-lb-agent.yaml.orig: file extension '.orig' not valid. Valid extensions are .yaml, .yml, .tpl, or .txt [ERROR] templates/daemonset-ovs-agent.yaml.orig: file extension '.orig' not valid. Valid extensions are .yaml, .yml, .tpl, or .txt BUILDSTDERR: Error: 1 chart(s) linted, 1 chart(s) failed BUILDSTDERR: make[1]: *** [lint-neutron] Error 1 make[1]: Leaving directory `/builddir/build/BUILD/openstack-helm' BUILDSTDERR: make: *** [neutron] Error 2 BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sd6TYe (%build) BUILDSTDERR:     Bad exit status from /var/tmp/rpm-tmp.Sd6TYe (%build) RPM build errors: This failure was not reproduced in my private build this morning. I don't see any changes to this package since the prior build. We do have a patch against the file (0011-Support-per-host-overrides-of-auto_bridge_add.patch)  that applies with fuzz, which might explain the creation of a .orig file.  This doesn't explain the linters inconsistent behavior. Patch #12 (0011-Support-per-host-overrides-of-auto_bridge_add.patch): + echo 'Patch #12 (0011-Support-per-host-overrides-of-auto_bridge_add.patch):' + /usr/bin/cat /builddir/build/SOURCES/0011-Support-per-host-overrides-of-auto_bridge_add.patch + /usr/bin/patch -p1 --fuzz=0 patching file doc/source/devref/networking.rst patching file neutron/templates/bin/_neutron-linuxbridge-agent-init.sh.tpl patching file neutron/templates/bin/_neutron-openvswitch-agent-init.sh.tpl patching file neutron/templates/configmap-etc.yaml patching file neutron/templates/daemonset-lb-agent.yaml Hunk #1 succeeded at 110 (offset -2 lines). patching file neutron/templates/daemonset-ovs-agent.yaml Hunk #1 succeeded at 120 (offset -2 lines). patching file neutron/values.yaml Hunk #2 succeeded at 1637 (offset 17 lines). On 2019-03-20 11:46 p.m., build.starlingx at gmail.com wrote: > Project: STX_build_master_master > Build #: 26 > Status: Failure > Timestamp: 20190321T013000Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190321T013000Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS: false > BUILD_CONTAINERS_ZZZ: false > > _______________________________________________ > 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 Thu Mar 21 15:14:32 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 21 Mar 2019 15:14:32 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> <7027C5CE-7CC6-44FF-9649-2287F2B233D1@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F35ECF687@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530564B4@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CF4CB@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9F898@SHSMSX101.ccr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4CFA11@ALA-MBD.corp.ad.wrs.com> Hi Shuicheng, We discussed this in the networking bi-weekly team meeting today. Please re-enable the mlx pmd – re-apply the following patch: https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch Then please rebase to the latest master and build a new load for Ada’s team to start testing Hi Elio, One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 Thanks, Ghada From: Khalil, Ghada Sent: Thursday, March 21, 2019 9:12 AM To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. Can you confirm that the load being used has the mellanox pmd enabled in it? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 21, 2019 9:03 AM To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie for the testing. Hi all, Does it mean greenlight for code merge, or any other test is needed? Here is the patch list: https://review.openstack.org/642672 https://review.openstack.org/642673 Best Regards Shuicheng From: Xu, Chenjie Sent: Thursday, March 21, 2019 5:46 PM To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From elio.martinez.monroy at intel.com Thu Mar 21 15:19:46 2019 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Thu, 21 Mar 2019 15:19:46 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA4CFA11@ALA-MBD.corp.ad.wrs.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> <7027C5CE-7CC6-44FF-9649-2287F2B233D1@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F35ECF687@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530564B4@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CF4CB@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9F898@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CFA11@ALA-MBD.corp.ad.wrs.com> Message-ID: <1466AF2176E6F040BD63860D0A241BBD46CA30D1@FMSMSX109.amr.corp.intel.com> Perfect, I will be cheking my mail for that new ISO. Adding Richo , he is the one that is going to execute the tests. Thanks BR Elio From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, March 21, 2019 9:15 AM To: Lin, Shuicheng ; Cabrales, Ada ; Martinez Monroy, Elio Cc: 'starlingx-discuss at lists.starlingx.io' ; Zhao, Forrest Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, We discussed this in the networking bi-weekly team meeting today. Please re-enable the mlx pmd – re-apply the following patch: https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch Then please rebase to the latest master and build a new load for Ada’s team to start testing Hi Elio, One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 Thanks, Ghada From: Khalil, Ghada Sent: Thursday, March 21, 2019 9:12 AM To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. Can you confirm that the load being used has the mellanox pmd enabled in it? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 21, 2019 9:03 AM To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie for the testing. Hi all, Does it mean greenlight for code merge, or any other test is needed? Here is the patch list: https://review.openstack.org/642672 https://review.openstack.org/642673 Best Regards Shuicheng From: Xu, Chenjie Sent: Thursday, March 21, 2019 5:46 PM To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Thu Mar 21 15:31:53 2019 From: serverascode at gmail.com (Curtis) Date: Thu, 21 Mar 2019 11:31:53 -0400 Subject: [Starlingx-discuss] Offline docker images install? In-Reply-To: References: <11547091552947706@myt3-964eae3a5b05.qloud-c.yandex.net> Message-ID: On Thu, Mar 21, 2019 at 10:23 AM Miller, Frank wrote: > I’ve assigned the LP to Mingyuan as he was prime on implementing this > feature. Mingyuan can you please provide some assistance to Curtis with > his setup? Thanks. > > > Thanks for looking at the bug and assigning someone. Will be great to get this figured out. :) Thanks, Curtis > Frank > > > > *From:* Curtis [mailto:serverascode at gmail.com] > *Sent:* Thursday, March 21, 2019 8:47 AM > *To:* Erich Cordoba > *Cc:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] Offline docker images install? > > > > On Wed, Mar 20, 2019 at 4:31 PM Curtis wrote: > > > > > > On Mon, Mar 18, 2019 at 6:21 PM Erich Cordoba > wrote: > > Cristopher has setup an internal/local docker registry with all needed > images. I think he can (tomorrow, today is Mexican holiday) give more > insights on this. > > > > > > If anyone has any hints on this, I'm running into a problem where kubeadm > init seems to be failing during config_controller when using an alternative > registry for all the public ones. Not finding meaningful error messages yet. > > > > > > FYI I entered a bug report: > https://bugs.launchpad.net/starlingx/+bug/1821090 > > Thanks, > > Curtis > > > > > > Thanks, > > Curtis > > > > > > -Erich > > -- > Sent from Yandex.Mail for mobile > > 18.03.2019, 16:17, "Curtis" : > > Hi All, > > > > I apologise if this has been covered somewhere, did a bit of > searching...what if I want to install all the docker images for stx from an > offline file. Was there some mention of these being included in the ISO > (thought maybe I'd heard that), or can I import them prior to installation > of openstack? > > > > Mostly I am coming from the perspective of the upcoming stx workshop at > the openinfra summit. Would like to avoid students having to all download > at the same time, or all hitting a local proxy, if possible. > > > > Sorry if I missed it. > > > > Thanks, > > Curtis > > > > PS. Thanks for the docs at > https://wiki.openstack.org/wiki/StarlingX/Containers/Installation ran > through it today, all good. :) > > > -- > > Blog: serverascode.com > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > -- > > Blog: serverascode.com > > > > -- > > Blog: serverascode.com > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcel at schaible-consulting.de Thu Mar 21 15:41:17 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Thu, 21 Mar 2019 16:41:17 +0100 (CET) Subject: [Starlingx-discuss] Any recommendations which image version for duplex installation? In-Reply-To: References: <1764012181.1392924.1553094099916@communicator.strato.com> <609025849.1401614.1553101746793@communicator.strato.com> Message-ID: <216735795.1457146.1553182877799@communicator.strato.com> Image: centos of 2019-03-05 In the puppet log I see the following error: [ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-apiserver:v1.12.3: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Since I don't have internet access at this point in time, how can I fix this? Thanks Marcel > Curtis hat am 20. März 2019 um 18:59 geschrieben: > > > On Wed, Mar 20, 2019 at 1:09 PM Marcel Schaible < > marcel at schaible-consulting.de> wrote: > > > The problem with the greatest latest version is the external dependency of > > kubernetes. I am not getting a connection out to google drive from my lab. > > > > > When you say google drive, do you mean downloading docker images from > remote repositories? Or is it trying to connect to some other service from > google? Does your lab have some security restrictions to accessing external > resources? > > Thanks, > Curtis > > > > > Since I don't want to use kubernetes/docker at the moment is it ok to > > throw them out of the worker and controller manifest? > > > > > > Curtis hat am 20. März 2019 um 17:54 > > geschrieben: > > > > > > > > > On Wed, Mar 20, 2019 at 11:03 AM Marcel Schaible < > > > marcel at schaible-consulting.de> wrote: > > > > > > > Hi, > > > > > > > > which version do you recommend at the moment for a duplex installation? > > > > > > > > With the one from 20190318 I have some problems, because probably the > > > > kubernetes part of config_controller tries to connect to a google > > cloud > > > > instance. Since I have no access to this server it fails. > > > > > > > > > > Someone on this list will correct me if I'm wrong, but I'd be using the > > > latest image available. There is a tremendous amount of working being > > done > > > as the project moves towards a release, but I would expect that the > > latest > > > image available is usually the best for testing with. > > > > > > Thanks, > > > Curtis > > > > > > > > > > > > > > > > > Thanks > > > > > > > > Marcel > > > > > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > > > > > > > > > -- > > > Blog: serverascode.com > > > > > -- > Blog: serverascode.com From marcel at schaible-consulting.de Thu Mar 21 15:52:30 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Thu, 21 Mar 2019 16:52:30 +0100 (CET) Subject: [Starlingx-discuss] config_controller fails because of kubernetes Message-ID: <1759467452.1457865.1553183550615@communicator.strato.com> Hi, I have tried the image from yesterday 20190320 and the config_controller bails out with the following error in the puppet.log: [ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-apiserver:v1.12.3: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) When I try to access the url with another computer ith proper internet access I'll et the response: {"errors":[{"code":"UNAUTHORIZED","message":"Unauthorized access."}]} Is this expected? So does that mean, that I have a working internet connection for installation? Since I don't want to use kubernetes/docker at the moment, how can I disable this behavior? Thanks Marcel From serverascode at gmail.com Thu Mar 21 16:14:49 2019 From: serverascode at gmail.com (Curtis) Date: Thu, 21 Mar 2019 12:14:49 -0400 Subject: [Starlingx-discuss] config_controller fails because of kubernetes In-Reply-To: <1759467452.1457865.1553183550615@communicator.strato.com> References: <1759467452.1457865.1553183550615@communicator.strato.com> Message-ID: On Thu, Mar 21, 2019 at 11:53 AM Marcel Schaible < marcel at schaible-consulting.de> wrote: > Hi, > > I have tried the image from yesterday 20190320 and the config_controller > bails out with the > following error in the puppet.log: > > [ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-apiserver:v1.12.3: > output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: > request canceled while waiting for connection (Client.Timeout exceeded > while awaiting headers) > > When I try to access the url with another computer ith proper internet > access I'll et the response: > > {"errors":[{"code":"UNAUTHORIZED","message":"Unauthorized access."}]} > > Is this expected? > > So does that mean, that I have a working internet connection for > installation? > This is how I understand it, and hopefully someone else will correct me or better explain if needed, but basically the ISO does not contain any Docker images. But when running config_controller, it needs to have Docker images to deploy Kubernetes. So those Docker images have to come from somewhere. So to answer your question, yes, you do need an internet connection at some point to get the Docker images. There is the option to 1) use a Docker proxy or 2) use a local Docker registry as an "alternative registry", ie. offline or "air gapped." Though I'm there may be a bug in option #2, and option #1 still requires that the proxy has access to the images somehow (generally the proxy is used as a cache, and the proxy itself still has access to the internet). > > Since I don't want to use kubernetes/docker at the moment, how can I > disable this behavior? > > Basically, I don't think it's possible to have StarlingX without Kubernetes...it's not an option any more. That's a major design decision the project has made and in many ways is a key feature of StarlingX. I don't think you would want to avoid it even if it were possible. :) Thanks, Curtis > Thanks > > Marcel > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From hayde.martinez.landa at intel.com Thu Mar 21 16:20:19 2019 From: hayde.martinez.landa at intel.com (Martinez Landa, Hayde) Date: Thu, 21 Mar 2019 16:20:19 +0000 Subject: [Starlingx-discuss] [stxinabox] Today's meeting Message-ID: Hi All, We are cancelling today's stx in a box meeting. See you next Thursday at 9:30 am PDT. Thanks, Hayde -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcel at schaible-consulting.de Thu Mar 21 16:24:20 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Thu, 21 Mar 2019 17:24:20 +0100 (CET) Subject: [Starlingx-discuss] config_controller fails because of kubernetes In-Reply-To: References: <1759467452.1457865.1553183550615@communicator.strato.com> Message-ID: <1529945301.1459698.1553185460183@communicator.strato.com> Thanks Curtis! Since there was no configuration option for setting up the internet access I suspect I have to do this manually before running the config_controller? Is this somewhere in the installation docs mentioned? > Curtis hat am 21. März 2019 um 17:14 geschrieben: > > > On Thu, Mar 21, 2019 at 11:53 AM Marcel Schaible < > marcel at schaible-consulting.de> wrote: > > > Hi, > > > > I have tried the image from yesterday 20190320 and the config_controller > > bails out with the > > following error in the puppet.log: > > > > [ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-apiserver:v1.12.3: > > output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: > > request canceled while waiting for connection (Client.Timeout exceeded > > while awaiting headers) > > > > When I try to access the url with another computer ith proper internet > > access I'll et the response: > > > > {"errors":[{"code":"UNAUTHORIZED","message":"Unauthorized access."}]} > > > > Is this expected? > > > > So does that mean, that I have a working internet connection for > > installation? > > > > This is how I understand it, and hopefully someone else will correct me or > better explain if needed, but basically the ISO does not contain any Docker > images. But when running config_controller, it needs to have Docker images > to deploy Kubernetes. So those Docker images have to come from somewhere. > So to answer your question, yes, you do need an internet connection at some > point to get the Docker images. > > There is the option to 1) use a Docker proxy or 2) use a local Docker > registry as an "alternative registry", ie. offline or "air gapped." Though > I'm there may be a bug in option #2, and option #1 still requires that the > proxy has access to the images somehow (generally the proxy is used as a > cache, and the proxy itself still has access to the internet). > > > > > > Since I don't want to use kubernetes/docker at the moment, how can I > > disable this behavior? > > > > > Basically, I don't think it's possible to have StarlingX without > Kubernetes...it's not an option any more. That's a major design decision > the project has made and in many ways is a key feature of StarlingX. I > don't think you would want to avoid it even if it were possible. :) > > Thanks, > Curtis > > > > > Thanks > > > > Marcel > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > -- > Blog: serverascode.com From serverascode at gmail.com Thu Mar 21 16:32:01 2019 From: serverascode at gmail.com (Curtis) Date: Thu, 21 Mar 2019 12:32:01 -0400 Subject: [Starlingx-discuss] config_controller fails because of kubernetes In-Reply-To: <1529945301.1459698.1553185460183@communicator.strato.com> References: <1759467452.1457865.1553183550615@communicator.strato.com> <1529945301.1459698.1553185460183@communicator.strato.com> Message-ID: On Thu, Mar 21, 2019 at 12:24 PM Marcel Schaible < marcel at schaible-consulting.de> wrote: > Thanks Curtis! > > Since there was no configuration option for setting up the internet access > I suspect I have to do this manually before running the config_controller? > > Is this somewhere in the installation docs mentioned? > I believe when answering the config_controller prompts/questions you need to configure the "External OAM Network" so that it can access either a docker proxy, a local registry, or the internet. In general, basically that External OAM Network needs access to the internet. So what ever IP information you input there should allow the node to access the internet. This is what config_controller says when providing prompts: 'The external OAM network is used for management of the cloud. It also provides access to the platform APIs. IP addresses on this network are reachable outside the data center." Again hopefully someone will correct me if I'm wrong. :) Thanks, Curtis > > > > > > > > Curtis hat am 21. März 2019 um 17:14 > geschrieben: > > > > > > On Thu, Mar 21, 2019 at 11:53 AM Marcel Schaible < > > marcel at schaible-consulting.de> wrote: > > > > > Hi, > > > > > > I have tried the image from yesterday 20190320 and the > config_controller > > > bails out with the > > > following error in the puppet.log: > > > > > > [ERROR ImagePull]: failed to pull image > k8s.gcr.io/kube-apiserver:v1.12.3: > > > output: Error response from daemon: Get https://k8s.gcr.io/v2/: > net/http: > > > request canceled while waiting for connection (Client.Timeout exceeded > > > while awaiting headers) > > > > > > When I try to access the url with another computer ith proper internet > > > access I'll et the response: > > > > > > {"errors":[{"code":"UNAUTHORIZED","message":"Unauthorized access."}]} > > > > > > Is this expected? > > > > > > So does that mean, that I have a working internet connection for > > > installation? > > > > > > > This is how I understand it, and hopefully someone else will correct me > or > > better explain if needed, but basically the ISO does not contain any > Docker > > images. But when running config_controller, it needs to have Docker > images > > to deploy Kubernetes. So those Docker images have to come from somewhere. > > So to answer your question, yes, you do need an internet connection at > some > > point to get the Docker images. > > > > There is the option to 1) use a Docker proxy or 2) use a local Docker > > registry as an "alternative registry", ie. offline or "air gapped." > Though > > I'm there may be a bug in option #2, and option #1 still requires that > the > > proxy has access to the images somehow (generally the proxy is used as a > > cache, and the proxy itself still has access to the internet). > > > > > > > > > > Since I don't want to use kubernetes/docker at the moment, how can I > > > disable this behavior? > > > > > > > > Basically, I don't think it's possible to have StarlingX without > > Kubernetes...it's not an option any more. That's a major design decision > > the project has made and in many ways is a key feature of StarlingX. I > > don't think you would want to avoid it even if it were possible. :) > > > > Thanks, > > Curtis > > > > > > > > > Thanks > > > > > > Marcel > > > > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > > > > > -- > > Blog: serverascode.com > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Thu Mar 21 16:37:05 2019 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Thu, 21 Mar 2019 16:37:05 +0000 Subject: [Starlingx-discuss] config_controller fails because of kubernetes In-Reply-To: References: <1759467452.1457865.1553183550615@communicator.strato.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB429C86@ALA-MBD.corp.ad.wrs.com> Hi, Some further clarification. StarlingX is now a kubernetes platform. Openstack is a containerized application that runs on top of this platform. There is no bare metal installation option for openstack anymore. As Curtis points out below if you do not have internet access you will need to use a proxy or an alternative registry(s) that is accessible from your deployment. This is configured through config_controller. The alterative registry would need to be populated with the required images. Brent From: Curtis [mailto:serverascode at gmail.com] Sent: Thursday, March 21, 2019 12:15 PM To: Marcel Schaible Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] config_controller fails because of kubernetes On Thu, Mar 21, 2019 at 11:53 AM Marcel Schaible > wrote: Hi, I have tried the image from yesterday 20190320 and the config_controller bails out with the following error in the puppet.log: [ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-apiserver:v1.12.3: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) When I try to access the url with another computer ith proper internet access I'll et the response: {"errors":[{"code":"UNAUTHORIZED","message":"Unauthorized access."}]} Is this expected? So does that mean, that I have a working internet connection for installation? This is how I understand it, and hopefully someone else will correct me or better explain if needed, but basically the ISO does not contain any Docker images. But when running config_controller, it needs to have Docker images to deploy Kubernetes. So those Docker images have to come from somewhere. So to answer your question, yes, you do need an internet connection at some point to get the Docker images. There is the option to 1) use a Docker proxy or 2) use a local Docker registry as an "alternative registry", ie. offline or "air gapped." Though I'm there may be a bug in option #2, and option #1 still requires that the proxy has access to the images somehow (generally the proxy is used as a cache, and the proxy itself still has access to the internet). Since I don't want to use kubernetes/docker at the moment, how can I disable this behavior? Basically, I don't think it's possible to have StarlingX without Kubernetes...it's not an option any more. That's a major design decision the project has made and in many ways is a key feature of StarlingX. I don't think you would want to avoid it even if it were possible. :) Thanks, Curtis Thanks Marcel _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Thu Mar 21 17:19:04 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 21 Mar 2019 13:19:04 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 198 - Still Failing! In-Reply-To: <1116414625.117.1553139994412.JavaMail.javamailuser@localhost> References: <1116414625.117.1553139994412.JavaMail.javamailuser@localhost> Message-ID: <289646793.125.1553188745561.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 198 Status: Still Failing Timestamp: 20190321T171858Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190321T013000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190321T013000Z DOCKER_BUILD_ID: jenkins-master-20190321T013000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190321T013000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190321T013000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From Ghada.Khalil at windriver.com Thu Mar 21 17:22:57 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 21 Mar 2019 17:22:57 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Networking Meeting - 03/21 Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4CFB33@ALA-MBD.corp.ad.wrs.com> Meeting minutes/agenda are captured at: https://etherpad.openstack.org/p/stx-networking Team Meeting Agenda/Notes - Mar 21/2019 - Kickoff joint planning with Neutron upstream for the Train cycle PTG (mlavalle): - http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003895.html and - https://etherpad.openstack.org/p/openstack-networking-train-ptg - L2/L3 rescheduling/rebalancing - to continue the effort discussed in Stein PTG? - https://review.openstack.org/#/c/595978/ - proposals: 1) scripts in Neutron or 2) plugin running rescheduling/rebalancing services out of Neutron (e.g. in STX repo) - StarlingX is implementing agent rescheduling/rebalancing in the VIM: https://storyboard.openstack.org/#!/story/2003857 - No additional functionality required in neutron - Other Gaps in StarlingX after rebase to Stein? - Port Forwarding for Floating IP is not in openstack client - StoryBoard already exists for openstack client: https://storyboard.openstack.org/#!/story/2004924 - If community is not implementing this, we should take over the implementation. Action: Forrest to resource once train implementation cycle is started. - Other items TBD - StarlingX just recently rebased to master/stein. Need to monitor and bring up any items - There may be small items / bug reports found during testing - We don't believe there are any major gaps in neutron that StarlingX needs for train - OVS VLAN transparent - It would be good to discuss with the neutron community the rationale behind not implementing this feature, but not a priority for StarlingX in train - L2POP (and more generally BGP EVPN) - The majority of the l2pop patches were related to BGP EVPN. This is still a low priority for StarlingX. - BGP EVPN should be discussed for StarlingX in the PTG, but it's not likely this will be required for the next release - https://blueprints.launchpad.net/neutron/+spec/native-l2pop - l2pop is being obsoleted, so we would need to re-work our proposal to the community if we want to pursue this - Neutron Patches -- Discuss next steps for patches not making Stein - Spreadsheet: https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit#gid=0 - Prevent DHCP from processing stale RPC messages (fd6cfc) - Kailun - RFE - This is a robustness item, so we want to continue pursuing this in train - 0039-dhcp-handle-concurrent-port-creation-error.patch (a38f89) - Kailun - Help needed on reproduction under concurrency - Put on hold for now. Wait to see if any issues come out of testing with Stein. - 0147-CGTS-8844-ml2-use-new-bindings-when-failing-concurre.patch (da31d0) - Kailun - Need community triage firstly: https://bugs.launchpad.net/neutron/+bug/1755810 - Continue to pursue in train - 0047-wsgi-prevent-accepting-socket-without-a-gr.patch (8e72491) - Huifeng - Discuss in the PTG whether the neutron community is planning to move to the wsgi - 0062-dvr-force-admin-state-update-before-distri.patch (edf9731) - Matt W - Refreshing this patch. Continue to pursue in train. - This is not serious enough to push for a backport to Stein - 0065-dvr-do-not-create-agent-gateway-ports-unle.patch (2857911) - Enyinna - Continue to pursue in train - Containerized OVS Integration - Code Merge Plan: Mar 22 (may have a few days delay to go thru code inspection/merge) - stx-config code review: https://review.openstack.org/#/c/633924/ - Testing: - simplex and dumplex tests are finished, result is updated on story https://storyboard.openstack.org/#!/story/2004649#comment-118416 - multi node standard deployment vswitch_type=ovs-dpdk is finished, result is updated on story https://storyboard.openstack.org/#!/story/2004649#comment-119007 - multi node standard deployment vswitch_type=none test is finished, result is updated here https://storyboard.openstack.org/#!/story/2004649#comment-119007 - Ready to merge once the code review is done: Matt & Joseph to review. Then Ghada to follow up with core reviewers as needed. - Once the code merges, Cheng needs to update the Install wiki to indicate that OVS is the default config, that OVS must be used for a vitual env, ...etc. - Also an email should be sent to StarlingX discuss list - openvswitch package Upversion - Code Merge Plan: Apr 5 - Issues w/ VM connectivity even seen on cengn load; issues not seen in WR labs - What are the next steps to investigate/address? - https://bugs.launchpad.net/starlingx/+bug/1820378 (reproduced on the cengn 03-05-2019 in Intel env) - Basic Functional Testing done and following bugs have been reported: - https://bugs.launchpad.net/starlingx/+bug/1821150 - https://bugs.launchpad.net/starlingx/+bug/1821135 - workaround doesn't work if different bridge name on different compute nodes - None of the 3 issues above are seen in WR labs using cengn load - Need to check that the latest docker images and armada manifests are being used - Suggest Chenjie shares the checksums from his env so that Matt can compare them to our env - Ada's team still needs to do regression testing as well as Mellanox testing before the code would merge - OVS-DPDK Firewall - Code Merge Plan: Mar 22 >> ?? - Given the move to containers, the code has to be moved from the puppet manifest to the Armada manifest (minor change). Then need a re-test in the container env. - stx-config change: https://review.openstack.org/#/c/645054/ - Only 1 multi-node HW env currently used for tests of containerized OVS integration - Since OVS-DPDK is not containerized and we've already done full OVS-DPDK firewall functional testing w/o containers, the functional testing done in openvswitch pkg upversion should be enough. - Will finish performance testing once the env is available. - Need new forecast. Action: Forrest to update - OVS process monitoring and alarming - Code Merge Plan: Mar 22 >> ?? - Still on hold due to OVS-DPDK Upverison testing - Need new forecast given the issues w/ openvswitch package upversion. - Kubenetes cluster network issues update: - https://bugs.launchpad.net/starlingx/+bug/1819738 : need to check whether it is by design - No this is a bug - https://bugs.launchpad.net/starlingx/+bug/1819492 : need to check whether the test case configuration is valid - Yes the config is valid; It's valid configuration to have the cluster-host interface tagged on the management interface with LAG mode - https://bugs.launchpad.net/starlingx/+bug/1820115 : some questions require help for clarification From build.starlingx at gmail.com Thu Mar 21 19:31:45 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 21 Mar 2019 15:31:45 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 27 - Still Failing! In-Reply-To: <1272259227.120.1553139999647.JavaMail.javamailuser@localhost> References: <1272259227.120.1553139999647.JavaMail.javamailuser@localhost> Message-ID: <1360611617.130.1553196707629.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 27 Status: Still Failing Timestamp: 20190321T193129Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190321T193129Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false BUILD_CONTAINERS_ZZZ: false From build.starlingx at gmail.com Thu Mar 21 19:43:27 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 21 Mar 2019 15:43:27 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 28 - Still Failing! In-Reply-To: <603795086.128.1553196704434.JavaMail.javamailuser@localhost> References: <603795086.128.1553196704434.JavaMail.javamailuser@localhost> Message-ID: <1863971643.134.1553197408449.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 28 Status: Still Failing Timestamp: 20190321T194243Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190321T194243Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false BUILD_CONTAINERS_ZZZ: false From Ghada.Khalil at windriver.com Wed Mar 20 14:54:59 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 20 Mar 2019 14:54:59 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <93814834B4855241994F290E959305C7530564B4@SHSMSX104.ccr.corp.intel.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> <7027C5CE-7CC6-44FF-9649-2287F2B233D1@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F35ECF687@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530564B4@SHSMSX104.ccr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4CF4CB@ALA-MBD.corp.ad.wrs.com> Just to clarify, StarlingX is currently using master nova. As far as I know, there should be no dependency on starlingx specific nova numa patches to have VM connectivity. As noted by Matt Peters and confirmed by Numan and Peng, we do not see this VM connectivity issue in the WR labs using cengn builds. Ada, Can you please clarify if your team is running VM connectivity tests as part of their regular sanity as requested previously? Are you seeing the same issue reported by Chenjie? Thanks, Ghada From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Monday, March 18, 2019 11:07 PM To: Xie, Cindy; Xu, Chenjie; Peters, Matt; Khalil, Ghada; Zhao, Forrest; Richard, Joseph; Winnicki, Chris; Lin, Shuicheng; Peng, Peng Cc: 'starlingx-discuss at lists.starlingx.io'; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, The feature mentioned below is not included in the patch-set that I’m working on. That is just for migration related Numa data. BTW, using below command openstack server show I could not see numa topology related info that I can see in non-container build Thanks! Zhipeng From: Xie, Cindy Sent: 2019年3月18日 23:01 To: Xu, Chenjie >; Peters, Matt >; Khalil, Ghada >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Liu, ZhipengS > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie to root-cause the issue. I am adding Zhipeng who is working on Nova-NUMA related patches and see if the feature has been included in the patch-set he is working on. Th.x - cindy From: Xu, Chenjie Sent: Monday, March 18, 2019 10:05 PM To: Peters, Matt >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Bruce/Ghada/Matt, I have located the cause of this bug: the domain XML file created by StarlingX lacks numa related sections. Need nova expert to fix this bug because it’s stx-nova to create domain XML file. By manually adding numa related sections, I can continue the OVSDPDK Upgrade Testing. But some unexpected behavior may exist. And I have tested the E/W traffic for VLAN network ( within the same host and across hosts). I have reported the bug in launchpad and you can find my debugging steps in the following bug report: https://bugs.launchpad.net/starlingx/+bug/1820378 Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Monday, March 18, 2019 8:40 PM To: Xu, Chenjie >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, Sorry for the delayed reply. For the port that is created / plugged by OpenStack, can you confirm the flows that are visible to the OVS datapath? Are the packets seen by OVS br-int and then not switched properly or are the packets not being processed by the vhost port at all? If you are seeing packets reach the bridge, can you confirm if all packet types are not getting through, i.e. is ARP working, but not ICMP. You can dump the datapath ports and flows with the following command: ovs-appctl dpif/show ovs-appctl dpif/dump-flows br-int Also, when you did your manual test, did you have the other VM present as well, or was it a fully manual setup with no OpenStack agents present? Regards, Matt From: "Xu, Chenjie" > Date: Friday, March 15, 2019 at 2:48 PM To: "Peters, Matt" >, Ghada Khalil >, "Xie, Cindy" >, "Zhao, Forrest" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" >, "Peng, Peng" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, We create vhostuser port and VM manually. And the connectivity between manually created VM and br-int works correctly. But the vhostuser port created by StarlingX doesn’t work. Could you please help review our following debugging steps and leave a comment? 1. We manually assigned correct IP to the StarlingX VM’s interface eth0 and ping DHCP server in VM. No packet can be captured by tcpdump and thus we think vhostuser port doesn’t work. Bring up br-int to verify the connectivity: sudo ifconfig br-int 192.168.101.1/24 up Check the IP assigned to the VM: openstack server list Manually assign IP to VM: sudo ifconfig 192.168.101.216/24 up Tcpdump in dhcp namespace: sudo ip netns exec $dhcp_namespace tcpdump –i $tap_device Ping DHCP server in VM: ping 192.168.101.1 No packets can be captured. 2. We added our own vhost user port to br-int and use virsh command and cirros-dpdk-vhostuserclient.xml (you can find in attached files) to create VM: Create vhostuser port: ovs-vsctl add-port br-int vhost-user-1 -- set Interface vhost-user-1 type=dpdkvhostuserclient options:vhost-server-path=/var/run/openvswitch/vhost-user-1 Create VM: virsh create cirros-dpdk-vhostuserclient.xml Bring up br-int to verify the connectivity: sudo ifconfig br-int 192.168.101.1/24 up Manually assign an IP to VM: sudo ifconfig eth0 192.168.101.18/24 up In created VM, ping br-int: ping 192.168.101.1 And the ping succeeds. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 13, 2019 9:13 PM To: Xu, Chenjie >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello, That message is a normal message from DPDK if you have multiple huge page sizes configured in your system. Openvswitch is configured to use 1G huge pages and will ignore the 2M huge pages. You can confirm this by looking at the Puppet logs to see what was configured and to ensure the 1G huge pages were mounted prior to openvswitch starting. -Matt From: "Xu, Chenjie" > Date: Wednesday, March 13, 2019 at 8:55 AM To: "Peters, Matt" >, Ghada Khalil >, "Xie, Cindy" >, "Zhao, Forrest" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" >, "Peng, Peng" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I installed StarlingX using following the March 5th ISO image and the issue still exists:http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190305T060000Z/outputs/iso/ Are there any steps not been written on the guide? I just followed the following guide: https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnStandard I checked the ovs-vswitchd.log and the following line maybe the cause: 23127 hugepages of size 2097152 reserved, but no mounted hugetlbfs found for that size It seems that something went wrong with hugepage. Some logs have been attached. If you have any idea about hugepage, please let me know. Peng has been added and hope Peng can provide some information about his environment. https://bugs.launchpad.net/starlingx/+bug/1819031 Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Tuesday, March 12, 2019 12:39 AM To: Peters, Matt >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, For Matt, I just tried to lock compute-1 to ensure the VMs is on the same compute host. But it still doesn’t work. The DHCP, router and VMs all located on compute-0. For Ghada, I checked the test cases listed in sanity test. I see that there is no test case to test the connectivity between VMs. Need confirmation from Ada’s team. https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 12, 2019 12:28 AM To: Khalil, Ghada >; Xu, Chenjie >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing If you co-locate the VMs on the same compute host (lock the other computes) do things work as expected? I.e. is it only when you are traversing the physical network that things are not pingable? -Matt From: Ghada Khalil > Date: Monday, March 11, 2019 at 10:51 AM To: "Xu, Chenjie" >, "Xie, Cindy" >, "Zhao, Forrest" >, "Peters, Matt" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" > Cc: "starlingx-discuss at lists.starlingx.io" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing To answer Forrest’s question: Do you know if OVS/DPDK has been tested after cut-over to container? I have seen Green sanity reports from Ada’s team since the cut-over. I expect this covers basic ovs-dpdk functional testing. Ada, please correct me if I am wrong. Regarding https://bugs.launchpad.net/starlingx/+bug/1819031, we’ve requested information from the reporter on how reproducible this issue is. As far as I know, it was reported on one system only. We’re waiting for more information from Peng. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Monday, March 11, 2019 10:40 AM To: Xie, Cindy; Zhao, Forrest; Peters, Matt; Richard, Joseph; Khalil, Ghada; Winnicki, Chris; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, Thank you for your information! The following issue is not exactly the same as mine: https://bugs.launchpad.net/starlingx/+bug/1819031 In this issue, the DHCP works and external network can reach the VMs. However in my case, VMs can’t get IP from DHCP and external network can’t reach VMs even with an IP allocated by myself. Best Regards, Xu, Chenjie From: Xie, Cindy Sent: Monday, March 11, 2019 10:05 PM To: Zhao, Forrest >; Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can’t get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can’t ping each other. The DHCP exists and VMs can’t ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris’s guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don’t believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don’t know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I’m trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I’m responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don’t know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing “system host-unlock compute-0”, it will report “Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address”. But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eric.MacDonald at windriver.com Wed Mar 20 18:10:17 2019 From: Eric.MacDonald at windriver.com (MacDonald, Eric) Date: Wed, 20 Mar 2019 18:10:17 +0000 Subject: [Starlingx-discuss] Improve FM's Python API return data In-Reply-To: <9700A18779F35F49AF027300A49E7C765FE87D29@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C765FE850FA@SHSMSX101.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9FA630E@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE854D3@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765FE87381@SHSMSX101.ccr.corp.intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA67C8C@ALA-MBD.corp.ad.wrs.com> <210898B96CA058408C55992CCAD98676B9FA7348@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE876D1@SHSMSX101.ccr.corp.intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA682EB@ALA-MBD.corp.ad.wrs.com> <7242A3DC72E453498E3D783BBB134C3E9DDC0111@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE87D29@SHSMSX101.ccr.corp.intel.com> Message-ID: <210898B96CA058408C55992CCAD98676B9FBC0C3@ALA-MBD.corp.ad.wrs.com> Hi Shuicheng, I've been using your new API FaultAPIsV2 and found that it is not behaving the way we discussed or I expected. I looked back on the code update and this behavior seems to have gotten by all of us. My example is for the clear_fault case. I call clear_fault against an alarmID/entity path that there is no alarm raised for but instead of just returning False or None ; it generates an exception. From below , from Bart who I agree with ... "My view is that you should be updating all six APIs to be consistent and raise an exception if the operation fails (e.g. because the API can't connect to fmmanager)." ... I expected to get an exception pretty much only if there was a 'software error' in the API call or it was 'unable to connect to the fm manager'. Not simply if the referenced alarm does not exist. >From your SS my case is the highlighted [cid:image003.jpg at 01D4DF26.A5398AB0] Eric. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Tuesday, February 26, 2019 7:47 PM To: Liu, Tao; Wensley, Barton; MacDonald, Eric; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Importance: High Hi all, Thanks for the quick confirmation. I will implement the code as Bart's suggestion. Best Regards Shuicheng From: Liu, Tao [mailto:Tao.Liu at windriver.com] Sent: Tuesday, February 26, 2019 10:31 PM To: Wensley, Barton ; Lin, Shuicheng ; MacDonald, Eric ; Bailey, Henry Albert (Al) Cc: Xie, Cindy ; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi Shuicheng, I agree with Bart's recommendation. The failure condition occurs when the FM manager has not been started by SM during the booting or swact, and raise an exception for this condition is a right approach. Having a new class for the new behavior is a good way to migrate the API changes. Regards, Tao From: Wensley, Barton Sent: Tuesday, February 26, 2019 9:11 AM To: Lin, Shuicheng; MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Shuicheng, As per your spreadsheet, there are actually three APIs that currently return ambiguous results (get_fault, get_faults and get_faults_by_id). My view is that you should be updating all six APIs to be consistent and raise an exception if the operation fails (e.g. because the API can't connect to fmmanager). You can avoid impacting the existing APIs by having both a FaultAPIs class and a FaultAPIsV2 class. To avoid code duplication, you would create a FaultAPIsBase class to hold all the common code and subclass from it. Bart From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February 25, 2019 8:59 PM To: MacDonald, Eric; Wensley, Barton; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi Eric/Tao/Al, Please confirm you agree a new set fault API (FaultAPIs_V2) or not. The attached excel is a simple comparison between original class FaultAPIs and FaultAPIs_V2. For myself, I still prefer to add 2 new API in original class, so other API call could be kept without change. We could have more discuss about the FaultAPIs_V2 design if you all agree to choose it. Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Monday, February 25, 2019 10:23 PM To: Wensley, Barton >; Lin, Shuicheng >; Liu, Tao >; Bailey, Henry Albert (Al) > Cc: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data I see your point Bart. This Jira is an Enhancement Request and fulfilling that should not be done so half way. All the APIs in V2 should be changed to defer exception handling to the caller as apparently that is the pythonic way. From: Wensley, Barton Sent: Monday, February 25, 2019 8:10 AM To: Lin, Shuicheng; MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Importance: High I disagree with this approach. Instead of just updating two of the methods, you should be updating all the methods in the FaultAPIs class that could fail in the same way and have them raise an exception. You should create a new FaultAPIs_v2 class for the updated methods to avoid impacting existing users. When a user of this API wants to use the new exceptions, they will start using the new class. Bart From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February 25, 2019 2:58 AM To: MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al); Wensley, Barton Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi all, Based on the comments in patch [0], I will add two new API, get_fault_ex and get_faults_by_id_ex. I will not add a new class, since all other APIs are kept without change. For get_fault_ex and get_faults_by_id_ex: the return value will be alarm list (maybe None). Exception will be thrown if there is error during API execution. [0]: https://review.openstack.org/637655 Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Wednesday, February 20, 2019 10:41 AM To: MacDonald, Eric >; Liu, Tao >; Al.Bailey at windriver.com Cc: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Improve FM's Python API return data Hi Eric, Thanks for the detail comments. In my plan, the return value for get_fault API will be like below: (False, None): there is error in the API execution. (True, None): API execution correctly, and there is no alarm message. (True, Alarm): API execution correctly, and there is alarm message. I think it should fix the issue you have. Is it right? If you agree on this new API return value change, I will implement it. Thanks. Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Tuesday, February 19, 2019 10:35 PM To: Lin, Shuicheng >; Liu, Tao > Cc: Xie, Cindy > Subject: RE: Improve FM's Python API return data I took a look and added comments. I don't think this update fixes the issue I have. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Monday, February 18, 2019 10:09 PM To: MacDonald, Eric; Liu, Tao Cc: Xie, Cindy Subject: RE: Improve FM's Python API return data Importance: High Resend the mail. Best Regards Shuicheng From: Lin, Shuicheng Sent: Tuesday, February 19, 2019 9:56 AM To: Liu, Tao (Wind River) >; 'eric.macdonald at windriver.com' > Cc: Xie, Cindy > Subject: Improve FM's Python API return data Hi Tao/Eric, For story 2004859, I plan to modify the get_fault api return value as a tuple. (True/False, Alarm) Alarm is valid only when the 1st item is True. Sample code is uploaded for you early review: Stx-fault: https://review.openstack.org/637655 Stx-integ: https://review.openstack.org/637656 Could you help review it and share your thought? If you agree on it, I will implement the code and test it. For test, I will try to kill fmManager/modify its listening port to simulate the failure case. For the api call outside of stx-fault, I may try to call it manually to verify. Please share me if there is better verify method. Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 22912 bytes Desc: image003.jpg URL: From shuicheng.lin at intel.com Thu Mar 21 01:32:32 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 21 Mar 2019 01:32:32 +0000 Subject: [Starlingx-discuss] Improve FM's Python API return data In-Reply-To: <210898B96CA058408C55992CCAD98676B9FBC0C3@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C765FE850FA@SHSMSX101.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9FA630E@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE854D3@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765FE87381@SHSMSX101.ccr.corp.intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA67C8C@ALA-MBD.corp.ad.wrs.com> <210898B96CA058408C55992CCAD98676B9FA7348@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE876D1@SHSMSX101.ccr.corp.intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA682EB@ALA-MBD.corp.ad.wrs.com> <7242A3DC72E453498E3D783BBB134C3E9DDC0111@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE87D29@SHSMSX101.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9FBC0C3@ALA-MBD.corp.ad.wrs.com> Message-ID: <9700A18779F35F49AF027300A49E7C765FE9F6D9@SHSMSX101.ccr.corp.intel.com> Hi Eric, Thanks for using the new API. :) I will update code to take "clear non exist alarm" as normal case (no exception) as your suggestion. Another thing is, I don't think we need return value for clear_fault/clear_all API. If we want return value for clear_fault/clear_all, then we could define return value as below: True: alarm is cleared False: alarm is not found. Exception: there is operation failure. Which version do you prefer? Thanks. I created below LP issue to track it: https://bugs.launchpad.net/starlingx/+bug/1821112 Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Thursday, March 21, 2019 2:10 AM To: Lin, Shuicheng ; Liu, Tao ; Wensley, Barton ; Bailey, Henry Albert (Al) Cc: Xie, Cindy ; starlingx-discuss at lists.starlingx.io; Khalil, Ghada Subject: RE: Improve FM's Python API return data Hi Shuicheng, I've been using your new API FaultAPIsV2 and found that it is not behaving the way we discussed or I expected. I looked back on the code update and this behavior seems to have gotten by all of us. My example is for the clear_fault case. I call clear_fault against an alarmID/entity path that there is no alarm raised for but instead of just returning False or None ; it generates an exception. From below , from Bart who I agree with ... "My view is that you should be updating all six APIs to be consistent and raise an exception if the operation fails (e.g. because the API can't connect to fmmanager)." ... I expected to get an exception pretty much only if there was a 'software error' in the API call or it was 'unable to connect to the fm manager'. Not simply if the referenced alarm does not exist. >From your SS my case is the highlighted [cid:image001.jpg at 01D4DFC0.AC313D50] Eric. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Tuesday, February 26, 2019 7:47 PM To: Liu, Tao; Wensley, Barton; MacDonald, Eric; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Importance: High Hi all, Thanks for the quick confirmation. I will implement the code as Bart's suggestion. Best Regards Shuicheng From: Liu, Tao [mailto:Tao.Liu at windriver.com] Sent: Tuesday, February 26, 2019 10:31 PM To: Wensley, Barton >; Lin, Shuicheng >; MacDonald, Eric >; Bailey, Henry Albert (Al) > Cc: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi Shuicheng, I agree with Bart's recommendation. The failure condition occurs when the FM manager has not been started by SM during the booting or swact, and raise an exception for this condition is a right approach. Having a new class for the new behavior is a good way to migrate the API changes. Regards, Tao From: Wensley, Barton Sent: Tuesday, February 26, 2019 9:11 AM To: Lin, Shuicheng; MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Shuicheng, As per your spreadsheet, there are actually three APIs that currently return ambiguous results (get_fault, get_faults and get_faults_by_id). My view is that you should be updating all six APIs to be consistent and raise an exception if the operation fails (e.g. because the API can't connect to fmmanager). You can avoid impacting the existing APIs by having both a FaultAPIs class and a FaultAPIsV2 class. To avoid code duplication, you would create a FaultAPIsBase class to hold all the common code and subclass from it. Bart From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February 25, 2019 8:59 PM To: MacDonald, Eric; Wensley, Barton; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi Eric/Tao/Al, Please confirm you agree a new set fault API (FaultAPIs_V2) or not. The attached excel is a simple comparison between original class FaultAPIs and FaultAPIs_V2. For myself, I still prefer to add 2 new API in original class, so other API call could be kept without change. We could have more discuss about the FaultAPIs_V2 design if you all agree to choose it. Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Monday, February 25, 2019 10:23 PM To: Wensley, Barton >; Lin, Shuicheng >; Liu, Tao >; Bailey, Henry Albert (Al) > Cc: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data I see your point Bart. This Jira is an Enhancement Request and fulfilling that should not be done so half way. All the APIs in V2 should be changed to defer exception handling to the caller as apparently that is the pythonic way. From: Wensley, Barton Sent: Monday, February 25, 2019 8:10 AM To: Lin, Shuicheng; MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Importance: High I disagree with this approach. Instead of just updating two of the methods, you should be updating all the methods in the FaultAPIs class that could fail in the same way and have them raise an exception. You should create a new FaultAPIs_v2 class for the updated methods to avoid impacting existing users. When a user of this API wants to use the new exceptions, they will start using the new class. Bart From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February 25, 2019 2:58 AM To: MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al); Wensley, Barton Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi all, Based on the comments in patch [0], I will add two new API, get_fault_ex and get_faults_by_id_ex. I will not add a new class, since all other APIs are kept without change. For get_fault_ex and get_faults_by_id_ex: the return value will be alarm list (maybe None). Exception will be thrown if there is error during API execution. [0]: https://review.openstack.org/637655 Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Wednesday, February 20, 2019 10:41 AM To: MacDonald, Eric >; Liu, Tao >; Al.Bailey at windriver.com Cc: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Improve FM's Python API return data Hi Eric, Thanks for the detail comments. In my plan, the return value for get_fault API will be like below: (False, None): there is error in the API execution. (True, None): API execution correctly, and there is no alarm message. (True, Alarm): API execution correctly, and there is alarm message. I think it should fix the issue you have. Is it right? If you agree on this new API return value change, I will implement it. Thanks. Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Tuesday, February 19, 2019 10:35 PM To: Lin, Shuicheng >; Liu, Tao > Cc: Xie, Cindy > Subject: RE: Improve FM's Python API return data I took a look and added comments. I don't think this update fixes the issue I have. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Monday, February 18, 2019 10:09 PM To: MacDonald, Eric; Liu, Tao Cc: Xie, Cindy Subject: RE: Improve FM's Python API return data Importance: High Resend the mail. Best Regards Shuicheng From: Lin, Shuicheng Sent: Tuesday, February 19, 2019 9:56 AM To: Liu, Tao (Wind River) >; 'eric.macdonald at windriver.com' > Cc: Xie, Cindy > Subject: Improve FM's Python API return data Hi Tao/Eric, For story 2004859, I plan to modify the get_fault api return value as a tuple. (True/False, Alarm) Alarm is valid only when the 1st item is True. Sample code is uploaded for you early review: Stx-fault: https://review.openstack.org/637655 Stx-integ: https://review.openstack.org/637656 Could you help review it and share your thought? If you agree on it, I will implement the code and test it. For test, I will try to kill fmManager/modify its listening port to simulate the failure case. For the api call outside of stx-fault, I may try to call it manually to verify. Please share me if there is better verify method. Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 22912 bytes Desc: image001.jpg URL: From chenjie.xu at intel.com Thu Mar 21 09:45:49 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Thu, 21 Mar 2019 09:45:49 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA4CF4CB@ALA-MBD.corp.ad.wrs.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> <7027C5CE-7CC6-44FF-9649-2287F2B233D1@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F35ECF687@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530564B4@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CF4CB@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 20, 2019 10:55 PM To: Liu, ZhipengS ; Xie, Cindy ; Xu, Chenjie ; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Just to clarify, StarlingX is currently using master nova. As far as I know, there should be no dependency on starlingx specific nova numa patches to have VM connectivity. As noted by Matt Peters and confirmed by Numan and Peng, we do not see this VM connectivity issue in the WR labs using cengn builds. Ada, Can you please clarify if your team is running VM connectivity tests as part of their regular sanity as requested previously? Are you seeing the same issue reported by Chenjie? Thanks, Ghada From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Monday, March 18, 2019 11:07 PM To: Xie, Cindy; Xu, Chenjie; Peters, Matt; Khalil, Ghada; Zhao, Forrest; Richard, Joseph; Winnicki, Chris; Lin, Shuicheng; Peng, Peng Cc: 'starlingx-discuss at lists.starlingx.io'; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, The feature mentioned below is not included in the patch-set that I’m working on. That is just for migration related Numa data. BTW, using below command openstack server show I could not see numa topology related info that I can see in non-container build Thanks! Zhipeng From: Xie, Cindy Sent: 2019年3月18日 23:01 To: Xu, Chenjie >; Peters, Matt >; Khalil, Ghada >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Liu, ZhipengS > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie to root-cause the issue. I am adding Zhipeng who is working on Nova-NUMA related patches and see if the feature has been included in the patch-set he is working on. Th.x - cindy From: Xu, Chenjie Sent: Monday, March 18, 2019 10:05 PM To: Peters, Matt >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Bruce/Ghada/Matt, I have located the cause of this bug: the domain XML file created by StarlingX lacks numa related sections. Need nova expert to fix this bug because it’s stx-nova to create domain XML file. By manually adding numa related sections, I can continue the OVSDPDK Upgrade Testing. But some unexpected behavior may exist. And I have tested the E/W traffic for VLAN network ( within the same host and across hosts). I have reported the bug in launchpad and you can find my debugging steps in the following bug report: https://bugs.launchpad.net/starlingx/+bug/1820378 Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Monday, March 18, 2019 8:40 PM To: Xu, Chenjie >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, Sorry for the delayed reply. For the port that is created / plugged by OpenStack, can you confirm the flows that are visible to the OVS datapath? Are the packets seen by OVS br-int and then not switched properly or are the packets not being processed by the vhost port at all? If you are seeing packets reach the bridge, can you confirm if all packet types are not getting through, i.e. is ARP working, but not ICMP. You can dump the datapath ports and flows with the following command: ovs-appctl dpif/show ovs-appctl dpif/dump-flows br-int Also, when you did your manual test, did you have the other VM present as well, or was it a fully manual setup with no OpenStack agents present? Regards, Matt From: "Xu, Chenjie" > Date: Friday, March 15, 2019 at 2:48 PM To: "Peters, Matt" >, Ghada Khalil >, "Xie, Cindy" >, "Zhao, Forrest" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" >, "Peng, Peng" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, We create vhostuser port and VM manually. And the connectivity between manually created VM and br-int works correctly. But the vhostuser port created by StarlingX doesn’t work. Could you please help review our following debugging steps and leave a comment? 1. We manually assigned correct IP to the StarlingX VM’s interface eth0 and ping DHCP server in VM. No packet can be captured by tcpdump and thus we think vhostuser port doesn’t work. Bring up br-int to verify the connectivity: sudo ifconfig br-int 192.168.101.1/24 up Check the IP assigned to the VM: openstack server list Manually assign IP to VM: sudo ifconfig 192.168.101.216/24 up Tcpdump in dhcp namespace: sudo ip netns exec $dhcp_namespace tcpdump –i $tap_device Ping DHCP server in VM: ping 192.168.101.1 No packets can be captured. 2. We added our own vhost user port to br-int and use virsh command and cirros-dpdk-vhostuserclient.xml (you can find in attached files) to create VM: Create vhostuser port: ovs-vsctl add-port br-int vhost-user-1 -- set Interface vhost-user-1 type=dpdkvhostuserclient options:vhost-server-path=/var/run/openvswitch/vhost-user-1 Create VM: virsh create cirros-dpdk-vhostuserclient.xml Bring up br-int to verify the connectivity: sudo ifconfig br-int 192.168.101.1/24 up Manually assign an IP to VM: sudo ifconfig eth0 192.168.101.18/24 up In created VM, ping br-int: ping 192.168.101.1 And the ping succeeds. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 13, 2019 9:13 PM To: Xu, Chenjie >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello, That message is a normal message from DPDK if you have multiple huge page sizes configured in your system. Openvswitch is configured to use 1G huge pages and will ignore the 2M huge pages. You can confirm this by looking at the Puppet logs to see what was configured and to ensure the 1G huge pages were mounted prior to openvswitch starting. -Matt From: "Xu, Chenjie" > Date: Wednesday, March 13, 2019 at 8:55 AM To: "Peters, Matt" >, Ghada Khalil >, "Xie, Cindy" >, "Zhao, Forrest" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" >, "Peng, Peng" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I installed StarlingX using following the March 5th ISO image and the issue still exists:http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190305T060000Z/outputs/iso/ Are there any steps not been written on the guide? I just followed the following guide: https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnStandard I checked the ovs-vswitchd.log and the following line maybe the cause: 23127 hugepages of size 2097152 reserved, but no mounted hugetlbfs found for that size It seems that something went wrong with hugepage. Some logs have been attached. If you have any idea about hugepage, please let me know. Peng has been added and hope Peng can provide some information about his environment. https://bugs.launchpad.net/starlingx/+bug/1819031 Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Tuesday, March 12, 2019 12:39 AM To: Peters, Matt >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, For Matt, I just tried to lock compute-1 to ensure the VMs is on the same compute host. But it still doesn’t work. The DHCP, router and VMs all located on compute-0. For Ghada, I checked the test cases listed in sanity test. I see that there is no test case to test the connectivity between VMs. Need confirmation from Ada’s team. https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 12, 2019 12:28 AM To: Khalil, Ghada >; Xu, Chenjie >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing If you co-locate the VMs on the same compute host (lock the other computes) do things work as expected? I.e. is it only when you are traversing the physical network that things are not pingable? -Matt From: Ghada Khalil > Date: Monday, March 11, 2019 at 10:51 AM To: "Xu, Chenjie" >, "Xie, Cindy" >, "Zhao, Forrest" >, "Peters, Matt" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" > Cc: "starlingx-discuss at lists.starlingx.io" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing To answer Forrest’s question: Do you know if OVS/DPDK has been tested after cut-over to container? I have seen Green sanity reports from Ada’s team since the cut-over. I expect this covers basic ovs-dpdk functional testing. Ada, please correct me if I am wrong. Regarding https://bugs.launchpad.net/starlingx/+bug/1819031, we’ve requested information from the reporter on how reproducible this issue is. As far as I know, it was reported on one system only. We’re waiting for more information from Peng. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Monday, March 11, 2019 10:40 AM To: Xie, Cindy; Zhao, Forrest; Peters, Matt; Richard, Joseph; Khalil, Ghada; Winnicki, Chris; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, Thank you for your information! The following issue is not exactly the same as mine: https://bugs.launchpad.net/starlingx/+bug/1819031 In this issue, the DHCP works and external network can reach the VMs. However in my case, VMs can’t get IP from DHCP and external network can’t reach VMs even with an IP allocated by myself. Best Regards, Xu, Chenjie From: Xie, Cindy Sent: Monday, March 11, 2019 10:05 PM To: Zhao, Forrest >; Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can’t get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can’t ping each other. The DHCP exists and VMs can’t ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris’s guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don’t believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don’t know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I’m trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I’m responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don’t know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing “system host-unlock compute-0”, it will report “Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address”. But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Thu Mar 21 13:02:38 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 21 Mar 2019 13:02:38 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> <7027C5CE-7CC6-44FF-9649-2287F2B233D1@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F35ECF687@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530564B4@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CF4CB@ALA-MBD.corp.ad.wrs.com> Message-ID: <9700A18779F35F49AF027300A49E7C765FE9F898@SHSMSX101.ccr.corp.intel.com> Thanks Chenjie for the testing. Hi all, Does it mean greenlight for code merge, or any other test is needed? Here is the patch list: https://review.openstack.org/642672 https://review.openstack.org/642673 Best Regards Shuicheng From: Xu, Chenjie Sent: Thursday, March 21, 2019 5:46 PM To: Khalil, Ghada ; Liu, ZhipengS ; Xie, Cindy ; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io' ; Zhao, Forrest ; Peters, Matt ; Richard, Joseph ; Winnicki, Chris ; Lin, Shuicheng ; Peng, Peng ; Martinez Monroy, Elio ; Jones, Bruce E ; Qin, Kailun ; Guo, Ruijing ; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 20, 2019 10:55 PM To: Liu, ZhipengS >; Xie, Cindy >; Xu, Chenjie >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Just to clarify, StarlingX is currently using master nova. As far as I know, there should be no dependency on starlingx specific nova numa patches to have VM connectivity. As noted by Matt Peters and confirmed by Numan and Peng, we do not see this VM connectivity issue in the WR labs using cengn builds. Ada, Can you please clarify if your team is running VM connectivity tests as part of their regular sanity as requested previously? Are you seeing the same issue reported by Chenjie? Thanks, Ghada From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Monday, March 18, 2019 11:07 PM To: Xie, Cindy; Xu, Chenjie; Peters, Matt; Khalil, Ghada; Zhao, Forrest; Richard, Joseph; Winnicki, Chris; Lin, Shuicheng; Peng, Peng Cc: 'starlingx-discuss at lists.starlingx.io'; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, The feature mentioned below is not included in the patch-set that I’m working on. That is just for migration related Numa data. BTW, using below command openstack server show I could not see numa topology related info that I can see in non-container build Thanks! Zhipeng From: Xie, Cindy Sent: 2019年3月18日 23:01 To: Xu, Chenjie >; Peters, Matt >; Khalil, Ghada >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Liu, ZhipengS > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie to root-cause the issue. I am adding Zhipeng who is working on Nova-NUMA related patches and see if the feature has been included in the patch-set he is working on. Th.x - cindy From: Xu, Chenjie Sent: Monday, March 18, 2019 10:05 PM To: Peters, Matt >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Bruce/Ghada/Matt, I have located the cause of this bug: the domain XML file created by StarlingX lacks numa related sections. Need nova expert to fix this bug because it’s stx-nova to create domain XML file. By manually adding numa related sections, I can continue the OVSDPDK Upgrade Testing. But some unexpected behavior may exist. And I have tested the E/W traffic for VLAN network ( within the same host and across hosts). I have reported the bug in launchpad and you can find my debugging steps in the following bug report: https://bugs.launchpad.net/starlingx/+bug/1820378 Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Monday, March 18, 2019 8:40 PM To: Xu, Chenjie >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, Sorry for the delayed reply. For the port that is created / plugged by OpenStack, can you confirm the flows that are visible to the OVS datapath? Are the packets seen by OVS br-int and then not switched properly or are the packets not being processed by the vhost port at all? If you are seeing packets reach the bridge, can you confirm if all packet types are not getting through, i.e. is ARP working, but not ICMP. You can dump the datapath ports and flows with the following command: ovs-appctl dpif/show ovs-appctl dpif/dump-flows br-int Also, when you did your manual test, did you have the other VM present as well, or was it a fully manual setup with no OpenStack agents present? Regards, Matt From: "Xu, Chenjie" > Date: Friday, March 15, 2019 at 2:48 PM To: "Peters, Matt" >, Ghada Khalil >, "Xie, Cindy" >, "Zhao, Forrest" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" >, "Peng, Peng" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, We create vhostuser port and VM manually. And the connectivity between manually created VM and br-int works correctly. But the vhostuser port created by StarlingX doesn’t work. Could you please help review our following debugging steps and leave a comment? 1. We manually assigned correct IP to the StarlingX VM’s interface eth0 and ping DHCP server in VM. No packet can be captured by tcpdump and thus we think vhostuser port doesn’t work. Bring up br-int to verify the connectivity: sudo ifconfig br-int 192.168.101.1/24 up Check the IP assigned to the VM: openstack server list Manually assign IP to VM: sudo ifconfig 192.168.101.216/24 up Tcpdump in dhcp namespace: sudo ip netns exec $dhcp_namespace tcpdump –i $tap_device Ping DHCP server in VM: ping 192.168.101.1 No packets can be captured. 2. We added our own vhost user port to br-int and use virsh command and cirros-dpdk-vhostuserclient.xml (you can find in attached files) to create VM: Create vhostuser port: ovs-vsctl add-port br-int vhost-user-1 -- set Interface vhost-user-1 type=dpdkvhostuserclient options:vhost-server-path=/var/run/openvswitch/vhost-user-1 Create VM: virsh create cirros-dpdk-vhostuserclient.xml Bring up br-int to verify the connectivity: sudo ifconfig br-int 192.168.101.1/24 up Manually assign an IP to VM: sudo ifconfig eth0 192.168.101.18/24 up In created VM, ping br-int: ping 192.168.101.1 And the ping succeeds. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 13, 2019 9:13 PM To: Xu, Chenjie >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello, That message is a normal message from DPDK if you have multiple huge page sizes configured in your system. Openvswitch is configured to use 1G huge pages and will ignore the 2M huge pages. You can confirm this by looking at the Puppet logs to see what was configured and to ensure the 1G huge pages were mounted prior to openvswitch starting. -Matt From: "Xu, Chenjie" > Date: Wednesday, March 13, 2019 at 8:55 AM To: "Peters, Matt" >, Ghada Khalil >, "Xie, Cindy" >, "Zhao, Forrest" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" >, "Peng, Peng" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I installed StarlingX using following the March 5th ISO image and the issue still exists:http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190305T060000Z/outputs/iso/ Are there any steps not been written on the guide? I just followed the following guide: https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnStandard I checked the ovs-vswitchd.log and the following line maybe the cause: 23127 hugepages of size 2097152 reserved, but no mounted hugetlbfs found for that size It seems that something went wrong with hugepage. Some logs have been attached. If you have any idea about hugepage, please let me know. Peng has been added and hope Peng can provide some information about his environment. https://bugs.launchpad.net/starlingx/+bug/1819031 Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Tuesday, March 12, 2019 12:39 AM To: Peters, Matt >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, For Matt, I just tried to lock compute-1 to ensure the VMs is on the same compute host. But it still doesn’t work. The DHCP, router and VMs all located on compute-0. For Ghada, I checked the test cases listed in sanity test. I see that there is no test case to test the connectivity between VMs. Need confirmation from Ada’s team. https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 12, 2019 12:28 AM To: Khalil, Ghada >; Xu, Chenjie >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing If you co-locate the VMs on the same compute host (lock the other computes) do things work as expected? I.e. is it only when you are traversing the physical network that things are not pingable? -Matt From: Ghada Khalil > Date: Monday, March 11, 2019 at 10:51 AM To: "Xu, Chenjie" >, "Xie, Cindy" >, "Zhao, Forrest" >, "Peters, Matt" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" > Cc: "starlingx-discuss at lists.starlingx.io" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing To answer Forrest’s question: Do you know if OVS/DPDK has been tested after cut-over to container? I have seen Green sanity reports from Ada’s team since the cut-over. I expect this covers basic ovs-dpdk functional testing. Ada, please correct me if I am wrong. Regarding https://bugs.launchpad.net/starlingx/+bug/1819031, we’ve requested information from the reporter on how reproducible this issue is. As far as I know, it was reported on one system only. We’re waiting for more information from Peng. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Monday, March 11, 2019 10:40 AM To: Xie, Cindy; Zhao, Forrest; Peters, Matt; Richard, Joseph; Khalil, Ghada; Winnicki, Chris; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, Thank you for your information! The following issue is not exactly the same as mine: https://bugs.launchpad.net/starlingx/+bug/1819031 In this issue, the DHCP works and external network can reach the VMs. However in my case, VMs can’t get IP from DHCP and external network can’t reach VMs even with an IP allocated by myself. Best Regards, Xu, Chenjie From: Xie, Cindy Sent: Monday, March 11, 2019 10:05 PM To: Zhao, Forrest >; Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can’t get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can’t ping each other. The DHCP exists and VMs can’t ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris’s guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don’t believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don’t know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I’m trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I’m responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don’t know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing “system host-unlock compute-0”, it will report “Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address”. But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Mar 21 13:11:59 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 21 Mar 2019 13:11:59 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <9700A18779F35F49AF027300A49E7C765FE9F898@SHSMSX101.ccr.corp.intel.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> <7027C5CE-7CC6-44FF-9649-2287F2B233D1@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F35ECF687@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530564B4@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CF4CB@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9F898@SHSMSX101.ccr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4CF947@ALA-MBD.corp.ad.wrs.com> Hi Shuicheng, There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. Can you confirm that the load being used has the mellanox pmd enabled in it? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 21, 2019 9:03 AM To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie for the testing. Hi all, Does it mean greenlight for code merge, or any other test is needed? Here is the patch list: https://review.openstack.org/642672 https://review.openstack.org/642673 Best Regards Shuicheng From: Xu, Chenjie Sent: Thursday, March 21, 2019 5:46 PM To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 20, 2019 10:55 PM To: Liu, ZhipengS >; Xie, Cindy >; Xu, Chenjie >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Just to clarify, StarlingX is currently using master nova. As far as I know, there should be no dependency on starlingx specific nova numa patches to have VM connectivity. As noted by Matt Peters and confirmed by Numan and Peng, we do not see this VM connectivity issue in the WR labs using cengn builds. Ada, Can you please clarify if your team is running VM connectivity tests as part of their regular sanity as requested previously? Are you seeing the same issue reported by Chenjie? Thanks, Ghada From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Monday, March 18, 2019 11:07 PM To: Xie, Cindy; Xu, Chenjie; Peters, Matt; Khalil, Ghada; Zhao, Forrest; Richard, Joseph; Winnicki, Chris; Lin, Shuicheng; Peng, Peng Cc: 'starlingx-discuss at lists.starlingx.io'; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, The feature mentioned below is not included in the patch-set that I’m working on. That is just for migration related Numa data. BTW, using below command openstack server show I could not see numa topology related info that I can see in non-container build Thanks! Zhipeng From: Xie, Cindy Sent: 2019年3月18日 23:01 To: Xu, Chenjie >; Peters, Matt >; Khalil, Ghada >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Liu, ZhipengS > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie to root-cause the issue. I am adding Zhipeng who is working on Nova-NUMA related patches and see if the feature has been included in the patch-set he is working on. Th.x - cindy From: Xu, Chenjie Sent: Monday, March 18, 2019 10:05 PM To: Peters, Matt >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Bruce/Ghada/Matt, I have located the cause of this bug: the domain XML file created by StarlingX lacks numa related sections. Need nova expert to fix this bug because it’s stx-nova to create domain XML file. By manually adding numa related sections, I can continue the OVSDPDK Upgrade Testing. But some unexpected behavior may exist. And I have tested the E/W traffic for VLAN network ( within the same host and across hosts). I have reported the bug in launchpad and you can find my debugging steps in the following bug report: https://bugs.launchpad.net/starlingx/+bug/1820378 Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Monday, March 18, 2019 8:40 PM To: Xu, Chenjie >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, Sorry for the delayed reply. For the port that is created / plugged by OpenStack, can you confirm the flows that are visible to the OVS datapath? Are the packets seen by OVS br-int and then not switched properly or are the packets not being processed by the vhost port at all? If you are seeing packets reach the bridge, can you confirm if all packet types are not getting through, i.e. is ARP working, but not ICMP. You can dump the datapath ports and flows with the following command: ovs-appctl dpif/show ovs-appctl dpif/dump-flows br-int Also, when you did your manual test, did you have the other VM present as well, or was it a fully manual setup with no OpenStack agents present? Regards, Matt From: "Xu, Chenjie" > Date: Friday, March 15, 2019 at 2:48 PM To: "Peters, Matt" >, Ghada Khalil >, "Xie, Cindy" >, "Zhao, Forrest" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" >, "Peng, Peng" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, We create vhostuser port and VM manually. And the connectivity between manually created VM and br-int works correctly. But the vhostuser port created by StarlingX doesn’t work. Could you please help review our following debugging steps and leave a comment? 1. We manually assigned correct IP to the StarlingX VM’s interface eth0 and ping DHCP server in VM. No packet can be captured by tcpdump and thus we think vhostuser port doesn’t work. Bring up br-int to verify the connectivity: sudo ifconfig br-int 192.168.101.1/24 up Check the IP assigned to the VM: openstack server list Manually assign IP to VM: sudo ifconfig 192.168.101.216/24 up Tcpdump in dhcp namespace: sudo ip netns exec $dhcp_namespace tcpdump –i $tap_device Ping DHCP server in VM: ping 192.168.101.1 No packets can be captured. 2. We added our own vhost user port to br-int and use virsh command and cirros-dpdk-vhostuserclient.xml (you can find in attached files) to create VM: Create vhostuser port: ovs-vsctl add-port br-int vhost-user-1 -- set Interface vhost-user-1 type=dpdkvhostuserclient options:vhost-server-path=/var/run/openvswitch/vhost-user-1 Create VM: virsh create cirros-dpdk-vhostuserclient.xml Bring up br-int to verify the connectivity: sudo ifconfig br-int 192.168.101.1/24 up Manually assign an IP to VM: sudo ifconfig eth0 192.168.101.18/24 up In created VM, ping br-int: ping 192.168.101.1 And the ping succeeds. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 13, 2019 9:13 PM To: Xu, Chenjie >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng > Cc: 'starlingx-discuss at lists.starlingx.io' >; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello, That message is a normal message from DPDK if you have multiple huge page sizes configured in your system. Openvswitch is configured to use 1G huge pages and will ignore the 2M huge pages. You can confirm this by looking at the Puppet logs to see what was configured and to ensure the 1G huge pages were mounted prior to openvswitch starting. -Matt From: "Xu, Chenjie" > Date: Wednesday, March 13, 2019 at 8:55 AM To: "Peters, Matt" >, Ghada Khalil >, "Xie, Cindy" >, "Zhao, Forrest" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" >, "Peng, Peng" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I installed StarlingX using following the March 5th ISO image and the issue still exists:http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190305T060000Z/outputs/iso/ Are there any steps not been written on the guide? I just followed the following guide: https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnStandard I checked the ovs-vswitchd.log and the following line maybe the cause: 23127 hugepages of size 2097152 reserved, but no mounted hugetlbfs found for that size It seems that something went wrong with hugepage. Some logs have been attached. If you have any idea about hugepage, please let me know. Peng has been added and hope Peng can provide some information about his environment. https://bugs.launchpad.net/starlingx/+bug/1819031 Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Tuesday, March 12, 2019 12:39 AM To: Peters, Matt >; Khalil, Ghada >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, For Matt, I just tried to lock compute-1 to ensure the VMs is on the same compute host. But it still doesn’t work. The DHCP, router and VMs all located on compute-0. For Ghada, I checked the test cases listed in sanity test. I see that there is no test case to test the connectivity between VMs. Need confirmation from Ada’s team. https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 12, 2019 12:28 AM To: Khalil, Ghada >; Xu, Chenjie >; Xie, Cindy >; Zhao, Forrest >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing If you co-locate the VMs on the same compute host (lock the other computes) do things work as expected? I.e. is it only when you are traversing the physical network that things are not pingable? -Matt From: Ghada Khalil > Date: Monday, March 11, 2019 at 10:51 AM To: "Xu, Chenjie" >, "Xie, Cindy" >, "Zhao, Forrest" >, "Peters, Matt" >, "Richard, Joseph" >, "Winnicki, Chris" >, "Lin, Shuicheng" > Cc: "starlingx-discuss at lists.starlingx.io" >, "Martinez Monroy, Elio" >, "Cabrales, Ada" >, "Jones, Bruce E" >, "Qin, Kailun" >, "Guo, Ruijing" >, "Le, Huifeng" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing To answer Forrest’s question: Do you know if OVS/DPDK has been tested after cut-over to container? I have seen Green sanity reports from Ada’s team since the cut-over. I expect this covers basic ovs-dpdk functional testing. Ada, please correct me if I am wrong. Regarding https://bugs.launchpad.net/starlingx/+bug/1819031, we’ve requested information from the reporter on how reproducible this issue is. As far as I know, it was reported on one system only. We’re waiting for more information from Peng. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Monday, March 11, 2019 10:40 AM To: Xie, Cindy; Zhao, Forrest; Peters, Matt; Richard, Joseph; Khalil, Ghada; Winnicki, Chris; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Cindy, Thank you for your information! The following issue is not exactly the same as mine: https://bugs.launchpad.net/starlingx/+bug/1819031 In this issue, the DHCP works and external network can reach the VMs. However in my case, VMs can’t get IP from DHCP and external network can’t reach VMs even with an IP allocated by myself. Best Regards, Xu, Chenjie From: Xie, Cindy Sent: Monday, March 11, 2019 10:05 PM To: Zhao, Forrest >; Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Is the below issue similar? https://bugs.launchpad.net/starlingx/+bug/1819031 From: Zhao, Forrest Sent: Monday, March 11, 2019 9:54 PM To: Xu, Chenjie >; Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Ghada, Matt, Joseph and validation team, Do you know if OVS/DPDK has been tested after cut-over to container? I think the below issue reported by Chenjie might already exist after cut-over to container. Thanks, Forrest From: Xu, Chenjie Sent: Monday, March 11, 2019 9:17 PM To: Peters, Matt >; Richard, Joseph >; Khalil, Ghada >; Chris.Winnicki at windriver.com; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have installed StarlingX multimode with new ISO image on 4 bare metals (2 controllers and 2 computes). However the VMs can’t get an IP address. I allocate the IP address which is same as neutron allocated to the VM, but the VMs still can’t ping each other. The DHCP exists and VMs can’t ping DHCP or router. Some logs have been attached. This issue blocks basic functional testing for OVS-DPDK Upgrade and please let me know if you have any ideas. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 8, 2019 9:49 AM To: Xu, Chenjie >; Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi all, I just shared the new test ISO with Chenjie/Elio in another mail thread. It is built from centos76 feature branch with latest master code rebased. Best Regards Shuicheng From: Xu, Chenjie Sent: Wednesday, March 6, 2019 11:07 AM To: Khalil, Ghada >; Richard, Joseph >; Peters, Matt >; Chris.Winnicki at windriver.com Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, That will be very helpful and many thanks to you and Joseph! Looking forward to Chris’s guide. Best Regards, Xu, Chenjie From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, March 6, 2019 12:07 AM To: Xu, Chenjie >; Richard, Joseph >; Peters, Matt >; Winnicki, Chris > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Chenjie, I spoke with Joseph. We don’t believe you need to make any puppet changes to test qos. Storyboard https://storyboard.openstack.org/#!/story/2003948 (which you already noted below) removed the STX/WR custom QoS extensions, so StarlingX is now aligned with the upstream neutron behavior. I have added Chris Winnicki to this email thread. He recently verified QoS functionality in StarlingX after the above Story was merged. He can provide you with the steps. Chris is away today, but should be able to respond tomorrow. Regards, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 05, 2019 8:54 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, About the configuration of QOS, I don’t know which puppet file should be modified to add the following configuration into the file /etc/neutron/plugins/ml2/openvswitch.ini: extensions = qos Could you please tell which puppet file I should modify? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 11:39 PM To: 'Richard, Joseph' >; 'Ghada.Khalil at windriver.com' >; 'Peters, Matt' > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: FW: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, For the following bug sent on last Friday: system host-port-list compute-1 'pdevice' I attached the /var/log/sysinv.log of controller-0 and compute-1. According to the logs, the compute-1 is not correctly installed. Could you please take a look at the logs and provide some comments? Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Monday, March 4, 2019 10:08 PM To: Richard, Joseph >; Ghada.Khalil at windriver.com; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, Thank you for your reply! For now I’m trying to configure QOS in StarlingX by changing puppet to change neutron configuration files. But I think this is not a good way to configure QOS in StarlingX. Could you please provide some guide on how to configure QOS in StarlingX? I noticed that the StarlingX custom QOS extension has been removed. (https://storyboard.openstack.org/#!/story/2003948) Best Regards, Xu, Chenjie From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Saturday, March 2, 2019 12:41 AM To: Xu, Chenjie >; Khalil, Ghada >; Peters, Matt > Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng >; Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing 1: You need to use sysinv to add the address, not add it using ip commands. usage: system host-addr-add 2: Check in /var/log/sysinv.log for the traceback at that time. From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Friday, March 1, 2019 9:55 AM To: Richard, Joseph; Khalil, Ghada; Peters, Matt Cc: starlingx-discuss at lists.starlingx.io; Lin, Shuicheng; Martinez Monroy, Elio; Zhao, Forrest; Xie, Cindy; Cabrales, Ada; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Joseph, I’m responsible for the Basic Functional Testing for OVS-DPDK Upgrade. I have set up a StarlingX multimode environment (1 controller and 2 computes) using the ISO image for OVS/DPDK upgrade test. I have 2 questions for you: 1. I don’t know how associate a vxlan providernet with compute node. Could you please provide the steps how to associate a vxlan providernet with compute node? The commands I use are following: neutron providernet-create tenant_vxlan --type=vxlan --mtu=1400 neutron providernet-range-create --name tenant_vxlan-a-range1 --range 100-400 --group 224.0.0.1 --ttl 255 tenant_vxlan system datanetwork-add tenant_vxlan vxlan --multicast_group 224.0.0.1 --ttl 255 --port_num 4789 system host-if-modify -p tenant_vxlan -c data compute-0 enp4s0f1 system host-unlock compute-0 After executing “system host-unlock compute-0”, it will report “Interface enp4s0f1 is associated to VXLAN data network tenant_vxlan which requires an IPv4 address”. But I do allocate a IP address for enp4s0f1. You can check the attached images. 2. I have found one bug and will investigate it. If you have any ideas please let me know. After installing the compute-1, I try to list the interface on compute-1 by following command: system host-port-list compute-1 'pdevice' The normal output should be: system host-port-list compute-0 +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | e072d576-90a6-4040-87df-66a913076df0 | eno1 | ethernet | 0000:07:00.0 | 0 | 0 | True | I350 Gigabit Network Connection | | 485b6e35-5b75-4b73-93dc-7deae0fb5c5c | eno2 | ethernet | 0000:07:00.1 | 0 | 0 | True | I350 Gigabit Network Connection | | 8b448ab6-e9df-4ce7-84a4-256d97f6fd5b | enp4s0f0 | ethernet | 0000:04:00.0 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | | 6d5b1ce7-ae76-4781-9e51-93bfe8417dc0 | enp4s0f1 | ethernet | 0000:04:00.1 | 0 | 0 | True | 82599ES 10-Gigabit SFI/SFP+ Network Connection | +--------------------------------------+----------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Friday, March 1, 2019 2:32 PM To: Lin, Shuicheng > Cc: Martinez Monroy, Elio >; Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: ISO image for OVS/DPDK upgrade Hi Shuicheng, Thank you for your information! I will start to do the Basic Functional Test. Best Regards, Xu, Chenjie From: Lin, Shuicheng Sent: Friday, March 1, 2019 2:03 PM To: Xu, Chenjie >; Martinez Monroy, Elio > Cc: Zhao, Forrest >; Xie, Cindy >; Cabrales, Ada >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing > Subject: ISO image for OVS/DPDK upgrade Hi Chenjie/Elio, Here is the ISO image for OVS/DPDK upgrade test. I have done basic deploy test, and could ping VM from each other successfully. Please help have a try with it, and notify me if there is any issue. It is built with recent code of centos76 feature branch. ec at 10.239.154.150:/home/ec/bootimage_ovs.iso scp passwd: 1 Here is the patch list for the upgrade in case you want to have a check: https://review.openstack.org/640244 https://review.openstack.org/640245 Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eric.MacDonald at windriver.com Thu Mar 21 13:16:14 2019 From: Eric.MacDonald at windriver.com (MacDonald, Eric) Date: Thu, 21 Mar 2019 13:16:14 +0000 Subject: [Starlingx-discuss] Improve FM's Python API return data In-Reply-To: <9700A18779F35F49AF027300A49E7C765FE9F6D9@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C765FE850FA@SHSMSX101.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9FA630E@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE854D3@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765FE87381@SHSMSX101.ccr.corp.intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA67C8C@ALA-MBD.corp.ad.wrs.com> <210898B96CA058408C55992CCAD98676B9FA7348@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE876D1@SHSMSX101.ccr.corp.intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA682EB@ALA-MBD.corp.ad.wrs.com> <7242A3DC72E453498E3D783BBB134C3E9DDC0111@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE87D29@SHSMSX101.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9FBC0C3@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9F6D9@SHSMSX101.ccr.corp.intel.com> Message-ID: <210898B96CA058408C55992CCAD98676B9FBC322@ALA-MBD.corp.ad.wrs.com> Hi Shuicheng, First of all, thank you for supporting this change for us. It's much appreciated. Yes, please go with (what was in your spreadsheet) True: alarm is cleared False: alarm is not found. Exception: there is operation failure. Please apply that change to the other new APIs as well. Looking at the code now more closely we need to ensure that the 'clear_fault', 'get_fault','clear_all' , 'get_faults' and 'get_faults_by_id' all follow this approach. Interestingly I don't see the get_faults_by_id returning an exception in my code in the case where there are none found. It is behaving properly but looking at the code I can only assume that fm_core.get_by_aid is returning None rather than False which would explain it. Please test 'each' the APIs with the following conditions ... * With applicable alarm present or success path * With applicable alarm not present. * With FM main process not running (you can do this by runnin the operations on a compute while there is no controller up.) * With an (software) error API call (like using an invalid alarmID) Eric. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Wednesday, March 20, 2019 9:33 PM To: MacDonald, Eric; Liu, Tao; Wensley, Barton; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io; Khalil, Ghada Subject: RE: Improve FM's Python API return data Importance: High Hi Eric, Thanks for using the new API. :) I will update code to take "clear non exist alarm" as normal case (no exception) as your suggestion. Another thing is, I don't think we need return value for clear_fault/clear_all API. If we want return value for clear_fault/clear_all, then we could define return value as below: True: alarm is cleared False: alarm is not found. Exception: there is operation failure. Which version do you prefer? Thanks. I created below LP issue to track it: https://bugs.launchpad.net/starlingx/+bug/1821112 Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Thursday, March 21, 2019 2:10 AM To: Lin, Shuicheng ; Liu, Tao ; Wensley, Barton ; Bailey, Henry Albert (Al) Cc: Xie, Cindy ; starlingx-discuss at lists.starlingx.io; Khalil, Ghada Subject: RE: Improve FM's Python API return data Hi Shuicheng, I've been using your new API FaultAPIsV2 and found that it is not behaving the way we discussed or I expected. I looked back on the code update and this behavior seems to have gotten by all of us. My example is for the clear_fault case. I call clear_fault against an alarmID/entity path that there is no alarm raised for but instead of just returning False or None ; it generates an exception. From below , from Bart who I agree with ... "My view is that you should be updating all six APIs to be consistent and raise an exception if the operation fails (e.g. because the API can't connect to fmmanager)." ... I expected to get an exception pretty much only if there was a 'software error' in the API call or it was 'unable to connect to the fm manager'. Not simply if the referenced alarm does not exist. >From your SS my case is the highlighted [cid:image001.jpg at 01D4DFC0.AC313D50] Eric. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Tuesday, February 26, 2019 7:47 PM To: Liu, Tao; Wensley, Barton; MacDonald, Eric; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Importance: High Hi all, Thanks for the quick confirmation. I will implement the code as Bart's suggestion. Best Regards Shuicheng From: Liu, Tao [mailto:Tao.Liu at windriver.com] Sent: Tuesday, February 26, 2019 10:31 PM To: Wensley, Barton >; Lin, Shuicheng >; MacDonald, Eric >; Bailey, Henry Albert (Al) > Cc: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi Shuicheng, I agree with Bart's recommendation. The failure condition occurs when the FM manager has not been started by SM during the booting or swact, and raise an exception for this condition is a right approach. Having a new class for the new behavior is a good way to migrate the API changes. Regards, Tao From: Wensley, Barton Sent: Tuesday, February 26, 2019 9:11 AM To: Lin, Shuicheng; MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Shuicheng, As per your spreadsheet, there are actually three APIs that currently return ambiguous results (get_fault, get_faults and get_faults_by_id). My view is that you should be updating all six APIs to be consistent and raise an exception if the operation fails (e.g. because the API can't connect to fmmanager). You can avoid impacting the existing APIs by having both a FaultAPIs class and a FaultAPIsV2 class. To avoid code duplication, you would create a FaultAPIsBase class to hold all the common code and subclass from it. Bart From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February 25, 2019 8:59 PM To: MacDonald, Eric; Wensley, Barton; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi Eric/Tao/Al, Please confirm you agree a new set fault API (FaultAPIs_V2) or not. The attached excel is a simple comparison between original class FaultAPIs and FaultAPIs_V2. For myself, I still prefer to add 2 new API in original class, so other API call could be kept without change. We could have more discuss about the FaultAPIs_V2 design if you all agree to choose it. Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Monday, February 25, 2019 10:23 PM To: Wensley, Barton >; Lin, Shuicheng >; Liu, Tao >; Bailey, Henry Albert (Al) > Cc: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data I see your point Bart. This Jira is an Enhancement Request and fulfilling that should not be done so half way. All the APIs in V2 should be changed to defer exception handling to the caller as apparently that is the pythonic way. From: Wensley, Barton Sent: Monday, February 25, 2019 8:10 AM To: Lin, Shuicheng; MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Importance: High I disagree with this approach. Instead of just updating two of the methods, you should be updating all the methods in the FaultAPIs class that could fail in the same way and have them raise an exception. You should create a new FaultAPIs_v2 class for the updated methods to avoid impacting existing users. When a user of this API wants to use the new exceptions, they will start using the new class. Bart From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February 25, 2019 2:58 AM To: MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al); Wensley, Barton Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi all, Based on the comments in patch [0], I will add two new API, get_fault_ex and get_faults_by_id_ex. I will not add a new class, since all other APIs are kept without change. For get_fault_ex and get_faults_by_id_ex: the return value will be alarm list (maybe None). Exception will be thrown if there is error during API execution. [0]: https://review.openstack.org/637655 Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Wednesday, February 20, 2019 10:41 AM To: MacDonald, Eric >; Liu, Tao >; Al.Bailey at windriver.com Cc: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Improve FM's Python API return data Hi Eric, Thanks for the detail comments. In my plan, the return value for get_fault API will be like below: (False, None): there is error in the API execution. (True, None): API execution correctly, and there is no alarm message. (True, Alarm): API execution correctly, and there is alarm message. I think it should fix the issue you have. Is it right? If you agree on this new API return value change, I will implement it. Thanks. Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Tuesday, February 19, 2019 10:35 PM To: Lin, Shuicheng >; Liu, Tao > Cc: Xie, Cindy > Subject: RE: Improve FM's Python API return data I took a look and added comments. I don't think this update fixes the issue I have. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Monday, February 18, 2019 10:09 PM To: MacDonald, Eric; Liu, Tao Cc: Xie, Cindy Subject: RE: Improve FM's Python API return data Importance: High Resend the mail. Best Regards Shuicheng From: Lin, Shuicheng Sent: Tuesday, February 19, 2019 9:56 AM To: Liu, Tao (Wind River) >; 'eric.macdonald at windriver.com' > Cc: Xie, Cindy > Subject: Improve FM's Python API return data Hi Tao/Eric, For story 2004859, I plan to modify the get_fault api return value as a tuple. (True/False, Alarm) Alarm is valid only when the 1st item is True. Sample code is uploaded for you early review: Stx-fault: https://review.openstack.org/637655 Stx-integ: https://review.openstack.org/637656 Could you help review it and share your thought? If you agree on it, I will implement the code and test it. For test, I will try to kill fmManager/modify its listening port to simulate the failure case. For the api call outside of stx-fault, I may try to call it manually to verify. Please share me if there is better verify method. Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 22912 bytes Desc: image001.jpg URL: From bruce.e.jones at intel.com Thu Mar 21 20:56:00 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 21 Mar 2019 20:56:00 +0000 Subject: [Starlingx-discuss] Draft - release policy Message-ID: <9A85D2917C58154C960D95352B22818BD0705CE4@fmsmsx123.amr.corp.intel.com> After our release team call today, I've been thinking about how we decide about when/if to release. Here is a very rough draft [0] of a policy. Comments and feedback welcomed! Brucej [0] https://etherpad.openstack.org/p/stx-release-policy-draft -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Mar 21 22:24:12 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 21 Mar 2019 22:24:12 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - March 21/2019 Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4CFD04@ALA-MBD.corp.ad.wrs.com> Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Meeting Agenda/Notes - March 21/2019 - Yellow Items - Documentation - Release gating documents have been identified. Execution plan is as follows: - Step 1: Implement the landing page structure. Bruce is meeting tomorrow with Abraham to get this going. - Step 2: Map the current content into the new structure - Step 3: Assign the work items to people to generate the content - This is when to determine how much help is needed. - Step 4: Implementation; assignees add the content - Expect Step 1 & 2 to be done in the next week. In the next release meeting, Bruce will share the plan for Step 3. - Anisble bootstrap Deployment - Developed a wk-by-wk plan with multiple milestones. - Plan to enable configurations over time: simplex, duplex, multi-node, storage - Need help from the test teams to verify the different configurations - Test setting up their individual systems - Expect full cut-over to Ansible (obsoleting config_controller) by mid-May. - Detailed milestones/plan to be published by next week. - Ceph Upgrade - Feature trending from yellow to green - Expect ISO to be ready for test team by next week - Expect two weeks for pre-submission feature testing - Code Merge Date: sometime in April (Cindy to provide final date) - Post-submission feature testing of 1wk - Red Items - Containers - Most items have plans in place now. There are still some unknown/unplanned items being worked. - Containers Plan: https://docs.google.com/spreadsheets/d/1lMMclUmLMPTuk_a5URMMoWrJR4MbeA_UINnBliumg2Y/edit#gid=991138079 - Merged Stories: https://storyboard.openstack.org/#!/story/list?tags=stx.containers&project_group_id=86&status=merged - Active Stories: https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.containers - 80% of feature content should be in the load by end of April. Full feature functionality by June 6. - Action: Frank to identify key milestones to enable verification activity. - Next step is to work with the test teams to define test-cases and the detailed plan for execution. - Distributed Cloud - Developing a wk-by-wk plan with multiple milestones - DC enabled with containers only - DC w/ openstack services - DC add-on features like update system and anisble provisioning - Expect feature completion by end of June. - Next step is to work with the test teams (Numan is the prime) to define test-cases and the detailed plan for execution. - Distro Openstack Patch Elimination - 10 nova items are considered StarlingX release gating + 1 internal StarlingX item - Next step is to determine forecasts for code review available on nova master. Steps are as follows: - Reproduce issue on master / open nova bug - Rebase the code as needed - Test the fix - Propose fix to the community (gerrit review) - Merge the fix in the starlingx branch (possibly in parallel with the upstream reviews) - Action: Bruce to work with 99cloud Test Readiness - Ada/Numan to work the updated verification plan ...dates are needed to determine RC1. - Plan is to provide an update in the next release meeting Bug Resolution - Bugs are actively being assigned to members of the community. Trends are going in the right direction. - Action: Document the policy around the # of bugs that can be open at the time of the release. From build.starlingx at gmail.com Thu Mar 21 22:46:07 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 21 Mar 2019 18:46:07 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_helm_charts - Build # 133 - Failure! Message-ID: <713128663.3.1553208371980.JavaMail.javamailuser@localhost> Project: STX_build_helm_charts Build #: 133 Status: Failure Timestamp: 20190321T224602Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190321T200039Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190321T200039Z OS: 7.6.1810 DOCKER_BUILD_ID: jenkins-master-20190321T200039Z-builder MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190321T200039Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190321T200039Z/logs From build.starlingx at gmail.com Thu Mar 21 22:46:14 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 21 Mar 2019 18:46:14 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 29 - Still Failing! In-Reply-To: <187823230.132.1553197405443.JavaMail.javamailuser@localhost> References: <187823230.132.1553197405443.JavaMail.javamailuser@localhost> Message-ID: <1951306901.6.1553208376292.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 29 Status: Still Failing Timestamp: 20190321T200039Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190321T200039Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false BUILD_CONTAINERS_ZZZ: false From mingyuan.qi at intel.com Fri Mar 22 01:55:31 2019 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Fri, 22 Mar 2019 01:55:31 +0000 Subject: [Starlingx-discuss] Offline docker images install? In-Reply-To: References: <11547091552947706@myt3-964eae3a5b05.qloud-c.yandex.net> Message-ID: Curtis, I’ve updated a comment in LP, please check the images listed in your private registry. Mingyuan From: Curtis [mailto:serverascode at gmail.com] Sent: Thursday, March 21, 2019 23:32 To: Miller, Frank Cc: Erich Cordoba ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Offline docker images install? On Thu, Mar 21, 2019 at 10:23 AM Miller, Frank > wrote: I’ve assigned the LP to Mingyuan as he was prime on implementing this feature. Mingyuan can you please provide some assistance to Curtis with his setup? Thanks. Thanks for looking at the bug and assigning someone. Will be great to get this figured out. :) Thanks, Curtis Frank From: Curtis [mailto:serverascode at gmail.com] Sent: Thursday, March 21, 2019 8:47 AM To: Erich Cordoba Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Offline docker images install? On Wed, Mar 20, 2019 at 4:31 PM Curtis > wrote: On Mon, Mar 18, 2019 at 6:21 PM Erich Cordoba > wrote: Cristopher has setup an internal/local docker registry with all needed images. I think he can (tomorrow, today is Mexican holiday) give more insights on this. If anyone has any hints on this, I'm running into a problem where kubeadm init seems to be failing during config_controller when using an alternative registry for all the public ones. Not finding meaningful error messages yet. FYI I entered a bug report: https://bugs.launchpad.net/starlingx/+bug/1821090 Thanks, Curtis Thanks, Curtis -Erich -- Sent from Yandex.Mail for mobile 18.03.2019, 16:17, "Curtis" >: Hi All, I apologise if this has been covered somewhere, did a bit of searching...what if I want to install all the docker images for stx from an offline file. Was there some mention of these being included in the ISO (thought maybe I'd heard that), or can I import them prior to installation of openstack? Mostly I am coming from the perspective of the upcoming stx workshop at the openinfra summit. Would like to avoid students having to all download at the same time, or all hitting a local proxy, if possible. Sorry if I missed it. Thanks, Curtis PS. Thanks for the docs at https://wiki.openstack.org/wiki/StarlingX/Containers/Installation ran through it today, all good. :) -- Blog: serverascode.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Blog: serverascode.com -- Blog: serverascode.com -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mingyuan.qi at intel.com Fri Mar 22 02:11:44 2019 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Fri, 22 Mar 2019 02:11:44 +0000 Subject: [Starlingx-discuss] Offline docker images install? In-Reply-To: References: <11547091552947706@myt3-964eae3a5b05.qloud-c.yandex.net> Message-ID: Erich & Cristopher, We’ll have to add a wiki page for setting up a private registry, would you please add the recipes for that? Including all the images need by starlingx. I planned to do that after I finish my current story, but in case more people are asking about the private registry these days, at least an image list is needed asap. Mingyuan From: Qi, Mingyuan [mailto:mingyuan.qi at intel.com] Sent: Friday, March 22, 2019 9:56 To: Curtis ; Miller, Frank Cc: Erich Cordoba ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Offline docker images install? Curtis, I’ve updated a comment in LP, please check the images listed in your private registry. Mingyuan From: Curtis [mailto:serverascode at gmail.com] Sent: Thursday, March 21, 2019 23:32 To: Miller, Frank > Cc: Erich Cordoba >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Offline docker images install? On Thu, Mar 21, 2019 at 10:23 AM Miller, Frank > wrote: I’ve assigned the LP to Mingyuan as he was prime on implementing this feature. Mingyuan can you please provide some assistance to Curtis with his setup? Thanks. Thanks for looking at the bug and assigning someone. Will be great to get this figured out. :) Thanks, Curtis Frank From: Curtis [mailto:serverascode at gmail.com] Sent: Thursday, March 21, 2019 8:47 AM To: Erich Cordoba Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Offline docker images install? On Wed, Mar 20, 2019 at 4:31 PM Curtis > wrote: On Mon, Mar 18, 2019 at 6:21 PM Erich Cordoba > wrote: Cristopher has setup an internal/local docker registry with all needed images. I think he can (tomorrow, today is Mexican holiday) give more insights on this. If anyone has any hints on this, I'm running into a problem where kubeadm init seems to be failing during config_controller when using an alternative registry for all the public ones. Not finding meaningful error messages yet. FYI I entered a bug report: https://bugs.launchpad.net/starlingx/+bug/1821090 Thanks, Curtis Thanks, Curtis -Erich -- Sent from Yandex.Mail for mobile 18.03.2019, 16:17, "Curtis" >: Hi All, I apologise if this has been covered somewhere, did a bit of searching...what if I want to install all the docker images for stx from an offline file. Was there some mention of these being included in the ISO (thought maybe I'd heard that), or can I import them prior to installation of openstack? Mostly I am coming from the perspective of the upcoming stx workshop at the openinfra summit. Would like to avoid students having to all download at the same time, or all hitting a local proxy, if possible. Sorry if I missed it. Thanks, Curtis PS. Thanks for the docs at https://wiki.openstack.org/wiki/StarlingX/Containers/Installation ran through it today, all good. :) -- Blog: serverascode.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Blog: serverascode.com -- Blog: serverascode.com -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Fri Mar 22 03:26:07 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 21 Mar 2019 23:26:07 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 201 - Failure! Message-ID: <1577816583.9.1553225169180.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 201 Status: Failure Timestamp: 20190322T015606Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T013000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190322T013000Z DOCKER_BUILD_ID: jenkins-master-20190322T013000Z-builder OS: 7.6.1810 MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T013000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190322T013000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Fri Mar 22 03:26:11 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 21 Mar 2019 23:26:11 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 30 - Still Failing! In-Reply-To: <554037733.4.1553208372856.JavaMail.javamailuser@localhost> References: <554037733.4.1553208372856.JavaMail.javamailuser@localhost> Message-ID: <1177776814.12.1553225173096.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 30 Status: Still Failing Timestamp: 20190322T013000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T013000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false BUILD_CONTAINERS_ZZZ: false From shuicheng.lin at intel.com Fri Mar 22 04:48:49 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Fri, 22 Mar 2019 04:48:49 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA4CFA11@ALA-MBD.corp.ad.wrs.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> <7027C5CE-7CC6-44FF-9649-2287F2B233D1@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F35ECF687@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530564B4@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CF4CB@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9F898@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CFA11@ALA-MBD.corp.ad.wrs.com> Message-ID: <9700A18779F35F49AF027300A49E7C765FE9FAE1@SHSMSX101.ccr.corp.intel.com> Hi Ghada, The mlx pmd patch is already included in below file: https://review.openstack.org/#/c/642672/2/networking/openvswitch/files/x86_64-native-linuxapp-gcc-config # Compile burst-oriented Mellanox ConnectX-3 (MLX4) PMD CONFIG_RTE_LIBRTE_MLX4_PMD=y … # Compile burst-oriented Mellanox ConnectX-4 & ConnectX-5 (MLX5) PMD CONFIG_RTE_LIBRTE_MLX5_PMD=y I will share the test ISO with latest master code with Elio in another mail thread today. Thanks. Best Regards Shuicheng From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, March 21, 2019 11:15 PM To: Lin, Shuicheng ; Cabrales, Ada ; Martinez Monroy, Elio Cc: 'starlingx-discuss at lists.starlingx.io' ; Zhao, Forrest Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, We discussed this in the networking bi-weekly team meeting today. Please re-enable the mlx pmd – re-apply the following patch: https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch Then please rebase to the latest master and build a new load for Ada’s team to start testing Hi Elio, One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 Thanks, Ghada From: Khalil, Ghada Sent: Thursday, March 21, 2019 9:12 AM To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. Can you confirm that the load being used has the mellanox pmd enabled in it? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 21, 2019 9:03 AM To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie for the testing. Hi all, Does it mean greenlight for code merge, or any other test is needed? Here is the patch list: https://review.openstack.org/642672 https://review.openstack.org/642673 Best Regards Shuicheng From: Xu, Chenjie Sent: Thursday, March 21, 2019 5:46 PM To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From himanshugoyal500 at gmail.com Fri Mar 22 10:27:14 2019 From: himanshugoyal500 at gmail.com (Himanshu Goyal) Date: Fri, 22 Mar 2019 15:57:14 +0530 Subject: [Starlingx-discuss] cpu model Passthrough with Intel/Skylake-Server-IBRS Message-ID: Hi, I'm using starlingX release "stx.2018.10", and "Intel/Skylake-Server-IBRS" as my compute server, trying to create a VM with cpu_model as passthrough but it is giving a error. Error: No valid host was found. There are not enough hosts available. compute-0: (ComputeFilter) host is disabled, reason: disabled by VIM*, compute-1: (VCpuModelFilter) Host VCPU model Skylake-Server-IBRS required Passthrough* I checked the starling-Discuss page & found it is fixed with qemu-kvm version:qemu-kvm-ev-3.0.0-0.tis.97 *starling-discuss link:* http://lists.starlingx.io/pipermail/starlingx-discuss/2018-December/002110.html Current qemu-kvm version in my setup: q*emu-img version 2.10.0(qemu-kvm-ev-2.10.0-0.tis.0)* Please let me know how can i upgrade qemu-kvm package in my compute without disturbing much running setup. Many Thanks, Himanshu Goyal -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Fri Mar 22 12:17:50 2019 From: serverascode at gmail.com (Curtis) Date: Fri, 22 Mar 2019 08:17:50 -0400 Subject: [Starlingx-discuss] Offline docker images install? In-Reply-To: References: <11547091552947706@myt3-964eae3a5b05.qloud-c.yandex.net> Message-ID: On Thu, Mar 21, 2019 at 9:55 PM Qi, Mingyuan wrote: > Curtis, > > > > I’ve updated a comment in LP, please check the images listed in your > private registry. > > > Thanks, updated. The images are definitely in the registry with the tags you are looking for. Some images are pulled from the registry, but around when config_controller fails there are no connections to the registry...I've been tcpdumping registry traffic. Anyways, I'll just post comments and such in the bug. Thanks for your help!, Curtis > Mingyuan > > > > *From:* Curtis [mailto:serverascode at gmail.com] > *Sent:* Thursday, March 21, 2019 23:32 > *To:* Miller, Frank > *Cc:* Erich Cordoba ; > starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] Offline docker images install? > > > > On Thu, Mar 21, 2019 at 10:23 AM Miller, Frank > wrote: > > I’ve assigned the LP to Mingyuan as he was prime on implementing this > feature. Mingyuan can you please provide some assistance to Curtis with > his setup? Thanks. > > > > > > Thanks for looking at the bug and assigning someone. Will be great to get > this figured out. :) > > > > Thanks, > > Curtis > > > > > > Frank > > > > *From:* Curtis [mailto:serverascode at gmail.com] > *Sent:* Thursday, March 21, 2019 8:47 AM > *To:* Erich Cordoba > *Cc:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] Offline docker images install? > > > > On Wed, Mar 20, 2019 at 4:31 PM Curtis wrote: > > > > > > On Mon, Mar 18, 2019 at 6:21 PM Erich Cordoba > wrote: > > Cristopher has setup an internal/local docker registry with all needed > images. I think he can (tomorrow, today is Mexican holiday) give more > insights on this. > > > > > > If anyone has any hints on this, I'm running into a problem where kubeadm > init seems to be failing during config_controller when using an alternative > registry for all the public ones. Not finding meaningful error messages yet. > > > > > > FYI I entered a bug report: > https://bugs.launchpad.net/starlingx/+bug/1821090 > > Thanks, > > Curtis > > > > > > Thanks, > > Curtis > > > > > > -Erich > > -- > Sent from Yandex.Mail for mobile > > 18.03.2019, 16:17, "Curtis" : > > Hi All, > > > > I apologise if this has been covered somewhere, did a bit of > searching...what if I want to install all the docker images for stx from an > offline file. Was there some mention of these being included in the ISO > (thought maybe I'd heard that), or can I import them prior to installation > of openstack? > > > > Mostly I am coming from the perspective of the upcoming stx workshop at > the openinfra summit. Would like to avoid students having to all download > at the same time, or all hitting a local proxy, if possible. > > > > Sorry if I missed it. > > > > Thanks, > > Curtis > > > > PS. Thanks for the docs at > https://wiki.openstack.org/wiki/StarlingX/Containers/Installation ran > through it today, all good. :) > > > -- > > Blog: serverascode.com > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > -- > > Blog: serverascode.com > > > > -- > > Blog: serverascode.com > > > > -- > > Blog: serverascode.com > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Fri Mar 22 12:22:15 2019 From: serverascode at gmail.com (Curtis) Date: Fri, 22 Mar 2019 08:22:15 -0400 Subject: [Starlingx-discuss] Offline docker images install? In-Reply-To: References: <11547091552947706@myt3-964eae3a5b05.qloud-c.yandex.net> Message-ID: On Thu, Mar 21, 2019 at 10:11 PM Qi, Mingyuan wrote: > Erich & Cristopher, > > > > We’ll have to add a wiki page for setting up a private registry, would you > please add the recipes for that? Including all the images need by starlingx. > > I planned to do that after I finish my current story, but in case more > people are asking about the private registry these days, at least an image > list is needed asap. > > > This would be very helpful. I've based my private registry on a stx install from the public regsitries. But it was a fairly convoluted process to determine image names and tags, strip public repo names from the names, and get them saved, imported, and pushed to the registry, but I've only done this once and I'm assuming there must be an easier way to save and upload images to a private registry. :) Thanks, Curtis > Mingyuan > > > > *From:* Qi, Mingyuan [mailto:mingyuan.qi at intel.com] > *Sent:* Friday, March 22, 2019 9:56 > *To:* Curtis ; Miller, Frank < > Frank.Miller at windriver.com> > *Cc:* Erich Cordoba ; > starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] Offline docker images install? > > > > Curtis, > > > > I’ve updated a comment in LP, please check the images listed in your > private registry. > > > > Mingyuan > > > > *From:* Curtis [mailto:serverascode at gmail.com ] > *Sent:* Thursday, March 21, 2019 23:32 > *To:* Miller, Frank > *Cc:* Erich Cordoba ; > starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] Offline docker images install? > > > > On Thu, Mar 21, 2019 at 10:23 AM Miller, Frank > wrote: > > I’ve assigned the LP to Mingyuan as he was prime on implementing this > feature. Mingyuan can you please provide some assistance to Curtis with > his setup? Thanks. > > > > > > Thanks for looking at the bug and assigning someone. Will be great to get > this figured out. :) > > > > Thanks, > > Curtis > > > > > > Frank > > > > *From:* Curtis [mailto:serverascode at gmail.com] > *Sent:* Thursday, March 21, 2019 8:47 AM > *To:* Erich Cordoba > *Cc:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] Offline docker images install? > > > > On Wed, Mar 20, 2019 at 4:31 PM Curtis wrote: > > > > > > On Mon, Mar 18, 2019 at 6:21 PM Erich Cordoba > wrote: > > Cristopher has setup an internal/local docker registry with all needed > images. I think he can (tomorrow, today is Mexican holiday) give more > insights on this. > > > > > > If anyone has any hints on this, I'm running into a problem where kubeadm > init seems to be failing during config_controller when using an alternative > registry for all the public ones. Not finding meaningful error messages yet. > > > > > > FYI I entered a bug report: > https://bugs.launchpad.net/starlingx/+bug/1821090 > > Thanks, > > Curtis > > > > > > Thanks, > > Curtis > > > > > > -Erich > > -- > Sent from Yandex.Mail for mobile > > 18.03.2019, 16:17, "Curtis" : > > Hi All, > > > > I apologise if this has been covered somewhere, did a bit of > searching...what if I want to install all the docker images for stx from an > offline file. Was there some mention of these being included in the ISO > (thought maybe I'd heard that), or can I import them prior to installation > of openstack? > > > > Mostly I am coming from the perspective of the upcoming stx workshop at > the openinfra summit. Would like to avoid students having to all download > at the same time, or all hitting a local proxy, if possible. > > > > Sorry if I missed it. > > > > Thanks, > > Curtis > > > > PS. Thanks for the docs at > https://wiki.openstack.org/wiki/StarlingX/Containers/Installation ran > through it today, all good. :) > > > -- > > Blog: serverascode.com > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > -- > > Blog: serverascode.com > > > > -- > > Blog: serverascode.com > > > > -- > > Blog: serverascode.com > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Peters at windriver.com Fri Mar 22 12:31:07 2019 From: Matt.Peters at windriver.com (Peters, Matt) Date: Fri, 22 Mar 2019 12:31:07 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> <7027C5CE-7CC6-44FF-9649-2287F2B233D1@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F35ECF687@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530564B4@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CF4CB@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9F898@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CFA11@ALA-MBD.corp.ad.wrs.com> <1466AF2176E6F040BD63860D0A241BBD46CA30D1@FMSMSX109.amr.corp.intel.com> Message-ID: Hello Chenjie, Comparing the image list to our labs shows a difference in the image IDs (sha), but I’m not sure if that is just a difference in build baselines or an actual difference in the images. Since some of them align, I think you might be running a different set of images. Can you confirm what the build baseline is that you pulled the images from? I have attached a sample list from our labs for comparison. -Matt From: "Xu, Chenjie" Date: Friday, March 22, 2019 at 7:25 AM To: "Peters, Matt" , "Martinez Monroy, Elio" , Ghada Khalil , "Lin, Shuicheng" , "Cabrales, Ada" , "Perez, Ricardo O" Cc: "'starlingx-discuss at lists.starlingx.io'" , "Zhao, Forrest" Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, The docker image versions in my environment and helm-charts-manifest-no-tests.tgz has been attached. The helm-charts-manifest-no-tests.tgz is built by Shuicheng for the OVSDPDK Upgrade Testing ISO image. Best Regards, Xu, Chenjie From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Thursday, March 21, 2019 11:20 PM To: Khalil, Ghada ; Lin, Shuicheng ; Cabrales, Ada ; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io' ; Zhao, Forrest Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Perfect, I will be cheking my mail for that new ISO. Adding Richo , he is the one that is going to execute the tests. Thanks BR Elio From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, March 21, 2019 9:15 AM To: Lin, Shuicheng >; Cabrales, Ada >; Martinez Monroy, Elio > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, We discussed this in the networking bi-weekly team meeting today. Please re-enable the mlx pmd – re-apply the following patch: https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch Then please rebase to the latest master and build a new load for Ada’s team to start testing Hi Elio, One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 Thanks, Ghada From: Khalil, Ghada Sent: Thursday, March 21, 2019 9:12 AM To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. Can you confirm that the load being used has the mellanox pmd enabled in it? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 21, 2019 9:03 AM To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie for the testing. Hi all, Does it mean greenlight for code merge, or any other test is needed? Here is the patch list: https://review.openstack.org/642672 https://review.openstack.org/642673 Best Regards Shuicheng From: Xu, Chenjie Sent: Thursday, March 21, 2019 5:46 PM To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: wrs-compute-1-images.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: wrs-controller-0-images.txt URL: From marcel at schaible-consulting.de Fri Mar 22 13:55:29 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Fri, 22 Mar 2019 14:55:29 +0100 (CET) Subject: [Starlingx-discuss] DUPLEX Installation: Image 20190320 fails to apply bootstrap manifest Message-ID: <373089711.1533160.1553262929290@communicator.strato.com> Hi, we are trying to install the centos image from 20190320 and getting the error below. Any help is greatly appreciated! Thanks Marcel 2019-03-22T13:00:54.085 Debug: 2019-03-22 13:00:53 +0000 Performing a hiera indirector lookup of postgresql::client::validcon_script_path with options {:variables=>Scope(Class[Postgresql::Client]), :merge=>#>, @value_type=#]>>>]>, @options={}>} 2019-03-22T13:00:54.087 Debug: 2019-03-22 13:00:53 +0000 hiera(): Looking up postgresql::client::validcon_script_path in YAML backend 2019-03-22T13:00:54.090 Debug: 2019-03-22 13:00:53 +0000 hiera(): Looking for data source runtime 2019-03-22T13:00:54.092 Debug: 2019-03-22 13:00:53 +0000 hiera(): Cannot find datafile /tmp/puppet/hieradata/runtime.yaml, skipping 2019-03-22T13:00:54.094 Debug: 2019-03-22 13:00:53 +0000 hiera(): Looking for data source host 2019-03-22T13:00:54.096 Debug: 2019-03-22 13:00:53 +0000 hiera(): Cannot find datafile /tmp/puppet/hieradata/host.yaml, skipping 2019-03-22T13:00:54.098 Debug: 2019-03-22 13:00:53 +0000 hiera(): Looking for data source secure_system 2019-03-22T13:00:54.100 Debug: 2019-03-22 13:00:53 +0000 hiera(): Cannot find datafile /tmp/puppet/hieradata/secure_system.yaml, skipping 2019-03-22T13:00:54.103 Debug: 2019-03-22 13:00:53 +0000 hiera(): Looking for data source system 2019-03-22T13:00:54.105 Debug: 2019-03-22 13:00:53 +0000 hiera(): Cannot find datafile /tmp/puppet/hieradata/system.yaml, skipping 2019-03-22T13:00:54.107 Debug: 2019-03-22 13:00:53 +0000 hiera(): Looking for data source secure_static 2019-03-22T13:00:54.109 Debug: 2019-03-22 13:00:53 +0000 hiera(): Looking for data source static 2019-03-22T13:00:54.111 Debug: 2019-03-22 13:00:53 +0000 hiera(): Looking for data source personality 2019-03-22T13:00:54.113 Debug: 2019-03-22 13:00:53 +0000 hiera(): Looking for data source global ... 2019-03-22T13:04:22.423 Error: 2019-03-22 13:04:22 +0000 Failed to apply catalog: Execution of '/usr/bin/openstack --os-interface internal role list --quiet --format csv' returned 1: The service catalog is empty. (tried 35, for a total of 170 seconds) 2019-03-22T13:04:22.425 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:126:in `rescue in block (2 levels) in request' 2019-03-22T13:04:22.427 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:88:in `block (2 levels) in request' 2019-03-22T13:04:22.429 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:87:in `loop' 2019-03-22T13:04:22.432 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:87:in `block in request' 2019-03-22T13:04:22.434 /usr/share/ruby/vendor_ruby/puppet/util.rb:128:in `withenv' 2019-03-22T13:04:22.436 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:82:in `request' 2019-03-22T13:04:22.438 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack/auth.rb:57:in `request' 2019-03-22T13:04:22.440 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone.rb:254:in `request' 2019-03-22T13:04:22.442 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone_role/openstack.rb:51:in `instances' 2019-03-22T13:04:22.444 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone_role/openstack.rb:64:in `prefetch' 2019-03-22T13:04:22.446 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:323:in `prefetch' 2019-03-22T13:04:22.448 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:223:in `prefetch_if_necessary' 2019-03-22T13:04:22.451 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:107:in `block in evaluate' 2019-03-22T13:04:22.453 /usr/share/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:116:in `call' 2019-03-22T13:04:22.455 /usr/share/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:116:in `traverse' 2019-03-22T13:04:22.457 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:154:in `evaluate' 2019-03-22T13:04:22.459 /usr/share/ruby/vendor_ruby/puppet/resource/catalog.rb:222:in `block in apply' 2019-03-22T13:04:22.461 /usr/share/ruby/vendor_ruby/puppet/util/log.rb:155:in `with_destination' 2019-03-22T13:04:22.463 /usr/share/ruby/vendor_ruby/puppet/transaction/report.rb:142:in `as_logging_destination' 2019-03-22T13:04:22.465 /usr/share/ruby/vendor_ruby/puppet/resource/catalog.rb:221:in `apply' 2019-03-22T13:04:22.467 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:171:in `block in apply_catalog' 2019-03-22T13:04:22.469 /usr/share/ruby/vendor_ruby/puppet/util.rb:223:in `block in benchmark' 2019-03-22T13:04:22.472 /usr/share/ruby/benchmark.rb:296:in `realtime' 2019-03-22T13:04:22.474 /usr/share/ruby/vendor_ruby/puppet/util.rb:222:in `benchmark' 2019-03-22T13:04:22.476 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:170:in `apply_catalog' 2019-03-22T13:04:22.478 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:343:in `run_internal' 2019-03-22T13:04:22.480 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:221:in `block in run' 2019-03-22T13:04:22.482 /usr/share/ruby/vendor_ruby/puppet/context.rb:65:in `override' 2019-03-22T13:04:22.484 /usr/share/ruby/vendor_ruby/puppet.rb:241:in `override' 2019-03-22T13:04:22.486 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:195:in `run' 2019-03-22T13:04:22.488 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:350:in `apply_catalog' 2019-03-22T13:04:22.490 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:274:in `block in main' 2019-03-22T13:04:22.493 /usr/share/ruby/vendor_ruby/puppet/context.rb:65:in `override' 2019-03-22T13:04:22.495 /usr/share/ruby/vendor_ruby/puppet.rb:241:in `override' 2019-03-22T13:04:22.497 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:225:in `main' 2019-03-22T13:04:22.499 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:170:in `run_command' 2019-03-22T13:04:22.501 /usr/share/ruby/vendor_ruby/puppet/application.rb:344:in `block in run' 2019-03-22T13:04:22.503 /usr/share/ruby/vendor_ruby/puppet/util.rb:540:in `exit_on_fail' 2019-03-22T13:04:22.505 /usr/share/ruby/vendor_ruby/puppet/application.rb:344:in `run' 2019-03-22T13:04:22.507 /usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run' 2019-03-22T13:04:22.509 /usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' 2019-03-22T13:04:22.512 /usr/bin/puppet:5:in `
' 2019-03-22T13:04:22.514 Debug: 2019-03-22 13:04:22 +0000 Applying settings catalog for sections reporting, metrics 2019-03-22T13:04:22.516 Debug: 2019-03-22 13:04:22 +0000 Finishing transaction 84378320 2019-03-22T13:04:22.518 Debug: 2019-03-22 13:04:22 +0000 Received report to process from controller-0 2019-03-22T13:04:22.520 Debug: 2019-03-22 13:04:22 +0000 Evicting cache entry for environment 'production' 2019-03-22T13:04:22.522 Debug: 2019-03-22 13:04:22 +0000 Caching environment 'production' (ttl = 0 sec) 2019-03-22T13:04:22.524 Debug: 2019-03-22 13:04:22 +0000 Processing report from controller-0 with processor Puppet::Reports::Store From scott.little at windriver.com Fri Mar 22 13:58:21 2019 From: scott.little at windriver.com (Scott Little) Date: Fri, 22 Mar 2019 09:58:21 -0400 Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 30 - Still Failing! In-Reply-To: <1177776814.12.1553225173096.JavaMail.javamailuser@localhost> References: <554037733.4.1553208372856.JavaMail.javamailuser@localhost> <1177776814.12.1553225173096.JavaMail.javamailuser@localhost> Message-ID: Build failed on package openstack-helm... again ... I'm testing a fix with the next build.... Scott On 2019-03-21 11:26 p.m., build.starlingx at gmail.com wrote: > Project: STX_build_master_master > Build #: 30 > Status: Still Failing > Timestamp: 20190322T013000Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T013000Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS: false > BUILD_CONTAINERS_ZZZ: false > > _______________________________________________ > 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 chenjie.xu at intel.com Fri Mar 22 11:22:13 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Fri, 22 Mar 2019 11:22:13 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <1466AF2176E6F040BD63860D0A241BBD46CA30D1@FMSMSX109.amr.corp.intel.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> <7027C5CE-7CC6-44FF-9649-2287F2B233D1@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F35ECF687@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530564B4@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CF4CB@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9F898@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CFA11@ALA-MBD.corp.ad.wrs.com> <1466AF2176E6F040BD63860D0A241BBD46CA30D1@FMSMSX109.amr.corp.intel.com> Message-ID: Hi Matt, The docker image versions in my environment and helm-charts-manifest-no-tests.tgz has been attached. The helm-charts-manifest-no-tests.tgz is built by Shuicheng for the OVSDPDK Upgrade Testing ISO image. Best Regards, Xu, Chenjie From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Thursday, March 21, 2019 11:20 PM To: Khalil, Ghada ; Lin, Shuicheng ; Cabrales, Ada ; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io' ; Zhao, Forrest Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Perfect, I will be cheking my mail for that new ISO. Adding Richo , he is the one that is going to execute the tests. Thanks BR Elio From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, March 21, 2019 9:15 AM To: Lin, Shuicheng >; Cabrales, Ada >; Martinez Monroy, Elio > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, We discussed this in the networking bi-weekly team meeting today. Please re-enable the mlx pmd – re-apply the following patch: https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch Then please rebase to the latest master and build a new load for Ada’s team to start testing Hi Elio, One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 Thanks, Ghada From: Khalil, Ghada Sent: Thursday, March 21, 2019 9:12 AM To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. Can you confirm that the load being used has the mellanox pmd enabled in it? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 21, 2019 9:03 AM To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie for the testing. Hi all, Does it mean greenlight for code merge, or any other test is needed? Here is the patch list: https://review.openstack.org/642672 https://review.openstack.org/642673 Best Regards Shuicheng From: Xu, Chenjie Sent: Thursday, March 21, 2019 5:46 PM To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: compute-0-images.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: compute-1-images.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: controller-0-images.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: controller-1-images.txt URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: helm-charts-manifest-no-tests.tgz Type: application/x-compressed Size: 956658 bytes Desc: helm-charts-manifest-no-tests.tgz URL: From erich.cordoba.malibran at intel.com Fri Mar 22 16:12:03 2019 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Fri, 22 Mar 2019 16:12:03 +0000 Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 30 - Still Failing! In-Reply-To: References: <554037733.4.1553208372856.JavaMail.javamailuser@localhost> <1177776814.12.1553225173096.JavaMail.javamailuser@localhost> Message-ID: <4C69153E-305C-4857-A7CA-F178994D4F56@intel.com> We are not seeing this failure in our internal builds, is there a way to reproduce? I want to be sure I’m not hiding something. -Erich From: Scott Little Date: Friday, March 22, 2019 at 7:59 AM To: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 30 - Still Failing! Build failed on package openstack-helm... again ... I'm testing a fix with the next build.... Scott On 2019-03-21 11:26 p.m., build.starlingx at gmail.com wrote: Project: STX_build_master_master Build #: 30 Status: Still Failing Timestamp: 20190322T013000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T013000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false BUILD_CONTAINERS_ZZZ: false _______________________________________________ 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 build.starlingx at gmail.com Fri Mar 22 16:11:43 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 22 Mar 2019 12:11:43 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 202 - Still Failing! In-Reply-To: <17412313.7.1553225165198.JavaMail.javamailuser@localhost> References: <17412313.7.1553225165198.JavaMail.javamailuser@localhost> Message-ID: <406927497.15.1553271104465.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 202 Status: Still Failing Timestamp: 20190322T142317Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T135629Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190322T135629Z DOCKER_BUILD_ID: jenkins-master-20190322T135629Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T135629Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190322T135629Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Fri Mar 22 16:11:48 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 22 Mar 2019 12:11:48 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 31 - Still Failing! In-Reply-To: <1947205763.10.1553225170001.JavaMail.javamailuser@localhost> References: <1947205763.10.1553225170001.JavaMail.javamailuser@localhost> Message-ID: <227163806.18.1553271109983.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 31 Status: Still Failing Timestamp: 20190322T135629Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T135629Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false BUILD_CONTAINERS_ZZZ: false From dtroyer at gmail.com Fri Mar 22 16:15:57 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Fri, 22 Mar 2019 11:15:57 -0500 Subject: [Starlingx-discuss] Finalizing DevStack plugin structure Message-ID: I think we are finally at the point that the structure of the DevStack plugins in seven flock repos is set and mostly consistent. Solving the dependency issues between services has been fun... The last bit I think we need to do here, at a test infrastructure level, is to clean up the job definitions and make them all voting. It turns out my choice of putting the base Zuul job definition in stx-fault was unfortunate, I want to move it to stx-integ as the better-but-still-not-ideal home as not every plugin needs to have fault loaded anyway.[0] Story 2005285 [1] has more details on moving and renaming the base job, plus making all devstack jobs run on the whole repo and voting. I will start preparing these reviews soon, comments or objections should be registered here or in the story. dt [0] An (unfortunately not-logged) IRC discussion a couple of weeks ago with dpenney and slittle1 landed on stx-integ as least-worst option. [1] https://storyboard.openstack.org/#!/story/2005285 -- Dean Troyer dtroyer at gmail.com From sgw at linux.intel.com Fri Mar 22 17:29:03 2019 From: sgw at linux.intel.com (Saul Wold) Date: Fri, 22 Mar 2019 10:29:03 -0700 Subject: [Starlingx-discuss] README for new github.com/starlingx-staging/tools-contrib repo Message-ID: Folks, Please take a quick review of the README for the new Contribution area in the https://github.com/starlingx-staging/tools-contrib repo. Please provide feedback, I have initialized the repo and will add the README over the weekend. Thanks Sau! -------------- next part -------------- ================================================================ tools-contrib - this is a repo for experimental or contrib tools ================================================================ Contributing Code ================= StarlingX is licensed under the Apache-2.0 license, so it's required that any code contributed here also use the Apache-2.0 license. Code contributions must include a valid "Signed-off-by" acknowledging the license for the modified or contributed file. We do not require assignment of copyright to contribute code; code is contributed under the terms of the applicable license. Directory Structure =================== The initial directory structure should be grouped by functionality, similar to the stx-tools repo. archive build configuration deployment mirror From abraham.arce.moreno at intel.com Fri Mar 22 17:37:50 2019 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Fri, 22 Mar 2019 17:37:50 +0000 Subject: [Starlingx-discuss] Fault Management Containerization (SB 2004008) Follow Up Message-ID: Thanks Frank for setting this up. Thanks everyone for your attendance to this meeting, here you have high level notes and ToDos based in the topics covered. In Summary - The presentation Stx-Fault/Containers is located at [0]. - Tao will kindly update the Fault Management architecture diagram, slide 8. - Mario will send an email no later than Monday afternoon with the latest findings / questions based in his 5 ToDos. - We will meet again on Tuesday to finalize on tasks and implementation details. If we are forgetting about any key point in this email, please do not hesitate to reply. StarlingX Architecture - 2 instances for each of the following projects: - Keystone - Horizon - Barbican - Fault Management will have 2 instances as well. Fault Management Architecture - [ToDo] [Tao] to modify the Fault Management architecture (Slide 8) Thanks Tao! - fm-api runs in compute node, snmp provide interfaces - [ToDo] [Mario] to check these statements Fault Management REST API - [ToDo] [Mario] to write the next level of details for REST API mapping / implementation, consider to include PUT to Event Log. Fault Management Architecture - python-fmclient is a wrapper to fm_cli / fm_api - [ToDo] [Mario] to understand more about fm_cli as a wrapper and how does it interact and affects fault management containerized strategy. FM Proposal - Remove mysql, fm-api, fm-common - [ToDo] [Mario] to understand about the removal of fm-api and fm-common from the containerized instance. - Dependency to cgts-client - [ToDo] [Mario] to understand what is cgtc-client and how does it interacts with fault management and the new containerized instance. OpenStack Applications The following 2 projects will make use of the Fault Management containerized: - starlingx-dashboard - stx-nfv [0] https://docs.google.com/presentation/d/1_vG83aHTToXlIdJxaJpVL-MHWfRGnxLuyEdFDt-nfwo/edit?usp=sharing From dtroyer at gmail.com Fri Mar 22 17:55:25 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Fri, 22 Mar 2019 12:55:25 -0500 Subject: [Starlingx-discuss] README for new github.com/starlingx-staging/tools-contrib repo In-Reply-To: References: Message-ID: On Fri, Mar 22, 2019 at 12:29 PM Saul Wold wrote: > Please take a quick review of the README for the new Contribution area > in the https://github.com/starlingx-staging/tools-contrib repo. > > Please provide feedback, I have initialized the repo and will add the > README over the weekend. Or.... (wait for it) add it as a PR and have the conversation there, you know, all code-review-y like :) In the mean time, I think it would be useful to have a minimal doc requirement, a) a README that at least says what it is, and b) a line in the top-level README to make an index of contents. You hit what I think are the foundation requirements (license, required DCO, no required CLA). Do we have the volunteers with the commit bit on this repo identified yet? I'd be happy letting them further refine the guidelines, which could be the second commit. Thanks for getting this set up Saul. dt -- Dean Troyer dtroyer at gmail.com From jose.perez.carranza at intel.com Fri Mar 22 18:22:26 2019 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Fri, 22 Mar 2019 18:22:26 +0000 Subject: [Starlingx-discuss] latest_green_build on CENG Message-ID: <0A5D9A624DF90343892F8F3FE7DE525A2A957B78@fmsmsx101.amr.corp.intel.com> Hi Currently the "latest_green_build" is pointing to a kind of old ISO (Feb 22), is this actually accurate? Or this should be updated to a newest ISO? Regards, José From scott.little at windriver.com Fri Mar 22 20:55:33 2019 From: scott.little at windriver.com (Scott Little) Date: Fri, 22 Mar 2019 16:55:33 -0400 Subject: [Starlingx-discuss] latest_green_build on CENG In-Reply-To: <0A5D9A624DF90343892F8F3FE7DE525A2A957B78@fmsmsx101.amr.corp.intel.com> References: <0A5D9A624DF90343892F8F3FE7DE525A2A957B78@fmsmsx101.amr.corp.intel.com> Message-ID: <2a25a104-8338-07f3-708b-8acac5804f8b@windriver.com> Hmmm, your right. The sanity e-mails have shifted format again.  The script didn't understand the new format. Scott On 2019-03-22 2:22 p.m., Perez Carranza, Jose wrote: > Hi > > Currently the "latest_green_build" is pointing to a kind of old ISO (Feb 22), is this actually accurate? Or this should be updated to a newest ISO? > > Regards, > José > > > _______________________________________________ > 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 Fri Mar 22 21:20:40 2019 From: sgw at linux.intel.com (Saul Wold) Date: Fri, 22 Mar 2019 14:20:40 -0700 Subject: [Starlingx-discuss] Building from master is failing Message-ID: <9a5f2200-d6f1-bb51-84ba-e86fd0ddfe08@linux.intel.com> I am trying to do a container build from master and seem to be having a failure, when building "build-stx-images.sh" stx-ceilometer. I believe that I have most latest build, but it's possibly I am a day or two off. I don't remember seeing any gerrit reviews for Panko, but maybe I missed it. Thoughts? Sau! Error from build-stx-images.sh script: Collecting pylint Downloading https://files.pythonhosted.org/packages/59/65/adcffa71fe942313c4d9e9284565d9a9e67798f4771f464e1d5dd58fea88/pylint-1.9.4-py2.py3-none-any.whl (689kB) Collecting panko==5.0.0 ^[[91m Could not find a version that satisfies the requirement panko==5.0.0 (from versions: 1.0.0.0b1, 1.0.0.0b3, 1.0.0.0rc1, 1.0.0, 2.0.0, 2.0.1, 2.0.2, 2.0.3, 3.0.0, 3.1.0, 4.0.0, 4.0.1, 4.0.2, 6.0.0.0rc1) ^[[0m^[[91mNo matching distribution found for panko==5.0.0 ^[[0mThe command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Failed to build stx-ceilometer... Aborting Skipping stx-cinder Skipping stx-glance Skipping stx-gnocchi Skipping stx-heat Skipping stx-horizon Skipping stx-keystone Skipping stx-neutron Skipping stx-nova ####################################### There were 1 failures: stx-ceilometer From cesar.lara at intel.com Fri Mar 22 23:10:04 2019 From: cesar.lara at intel.com (Lara, Cesar) Date: Fri, 22 Mar 2019 23:10:04 +0000 Subject: [Starlingx-discuss] [meetings][multios] Multi-OS team meeting Agenda for 03/25/2019 Message-ID: <0B566C62EC792145B40E29EFEBF1AB471061F165@fmsmsx104.amr.corp.intel.com> Multi-OS team meeting Agenda for 3/25/2019 - Update on Ubuntu build - Git repo with code access and readme documentation for this PoC - Update on Stx in a box - Opens Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From sxmatch1986 at gmail.com Sat Mar 23 02:42:07 2019 From: sxmatch1986 at gmail.com (hao wang) Date: Sat, 23 Mar 2019 10:42:07 +0800 Subject: [Starlingx-discuss] newbie want some help to contribute to starlingX Message-ID: Hi, starlingx My name is Wang Hao (Irc nickname: wanghao), a senior software engineer in FiberHome Telecommunication Technologies Co., Ltd. I'm an old soldier to contribute to OpenStack projects like Cinder, Nova, Zaqar, etc. since 2013. Also is the PTL of Zaqar project from 2017. I kept eye on starlingx project for a while and knew this is an important project in NFV and edge computing areas. I (and my team) want to contribute this project but as a newbie here, really appreciate who can give me some help how to do this. Thanks From serverascode at gmail.com Sat Mar 23 12:16:23 2019 From: serverascode at gmail.com (Curtis) Date: Sat, 23 Mar 2019 08:16:23 -0400 Subject: [Starlingx-discuss] DUPLEX Installation: Image 20190320 fails to apply bootstrap manifest In-Reply-To: <373089711.1533160.1553262929290@communicator.strato.com> References: <373089711.1533160.1553262929290@communicator.strato.com> Message-ID: On Fri, Mar 22, 2019 at 9:56 AM Marcel Schaible < marcel at schaible-consulting.de> wrote: > Hi, > > we are trying to install the centos image from 20190320 and getting the > error below. > > Any help is greatly appreciated! > Hmm, I don't see any related bugs [0] in a quick look. Does this happen every time? If so you could add a bug. Thanks, Curtis [0]: https://bugs.launchpad.net/starlingx > > Thanks > > Marcel > > > 2019-03-22T13:00:54.085 [0;36mDebug: 2019-03-22 13:00:53 +0000 Performing > a hiera indirector lookup of postgresql::client::validcon_script_path with > options {:variables=>Scope(Class[Postgresql::Client]), > :merge=># @options_t=# @elements=[# @key_type=# @type=# @values=["strategy"]>>, > @value_type=# @type=# @patterns=[# @pattern="first", @regexp=/first/>]>>>]>, @options={}>} [0m > 2019-03-22T13:00:54.087 [0;36mDebug: 2019-03-22 13:00:53 +0000 hiera(): > Looking up postgresql::client::validcon_script_path in YAML backend [0m > 2019-03-22T13:00:54.090 [0;36mDebug: 2019-03-22 13:00:53 +0000 hiera(): > Looking for data source runtime [0m > 2019-03-22T13:00:54.092 [0;36mDebug: 2019-03-22 13:00:53 +0000 hiera(): > Cannot find datafile /tmp/puppet/hieradata/runtime.yaml, skipping [0m > 2019-03-22T13:00:54.094 [0;36mDebug: 2019-03-22 13:00:53 +0000 hiera(): > Looking for data source host [0m > 2019-03-22T13:00:54.096 [0;36mDebug: 2019-03-22 13:00:53 +0000 hiera(): > Cannot find datafile /tmp/puppet/hieradata/host.yaml, skipping [0m > 2019-03-22T13:00:54.098 [0;36mDebug: 2019-03-22 13:00:53 +0000 hiera(): > Looking for data source secure_system [0m > 2019-03-22T13:00:54.100 [0;36mDebug: 2019-03-22 13:00:53 +0000 hiera(): > Cannot find datafile /tmp/puppet/hieradata/secure_system.yaml, skipping [0m > 2019-03-22T13:00:54.103 [0;36mDebug: 2019-03-22 13:00:53 +0000 hiera(): > Looking for data source system [0m > 2019-03-22T13:00:54.105 [0;36mDebug: 2019-03-22 13:00:53 +0000 hiera(): > Cannot find datafile /tmp/puppet/hieradata/system.yaml, skipping [0m > 2019-03-22T13:00:54.107 [0;36mDebug: 2019-03-22 13:00:53 +0000 hiera(): > Looking for data source secure_static [0m > 2019-03-22T13:00:54.109 [0;36mDebug: 2019-03-22 13:00:53 +0000 hiera(): > Looking for data source static [0m > 2019-03-22T13:00:54.111 [0;36mDebug: 2019-03-22 13:00:53 +0000 hiera(): > Looking for data source personality [0m > 2019-03-22T13:00:54.113 [0;36mDebug: 2019-03-22 13:00:53 +0000 hiera(): > Looking for data source global [0m > ... > 2019-03-22T13:04:22.423 [1;31mError: 2019-03-22 13:04:22 +0000 Failed to > apply catalog: Execution of '/usr/bin/openstack --os-interface internal > role list --quiet --format csv' returned 1: The service catalog is empty. > (tried 35, for a total of 170 seconds) > 2019-03-22T13:04:22.425 > /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:126:in > `rescue in block (2 levels) in request' > 2019-03-22T13:04:22.427 > /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:88:in > `block (2 levels) in request' > 2019-03-22T13:04:22.429 > /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:87:in > `loop' > 2019-03-22T13:04:22.432 > /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:87:in > `block in request' > 2019-03-22T13:04:22.434 /usr/share/ruby/vendor_ruby/puppet/util.rb:128:in > `withenv' > 2019-03-22T13:04:22.436 > /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:82:in > `request' > 2019-03-22T13:04:22.438 > /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack/auth.rb:57:in > `request' > 2019-03-22T13:04:22.440 > /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone.rb:254:in > `request' > 2019-03-22T13:04:22.442 > /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone_role/openstack.rb:51:in > `instances' > 2019-03-22T13:04:22.444 > /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone_role/openstack.rb:64:in > `prefetch' > 2019-03-22T13:04:22.446 > /usr/share/ruby/vendor_ruby/puppet/transaction.rb:323:in `prefetch' > 2019-03-22T13:04:22.448 > /usr/share/ruby/vendor_ruby/puppet/transaction.rb:223:in > `prefetch_if_necessary' > 2019-03-22T13:04:22.451 > /usr/share/ruby/vendor_ruby/puppet/transaction.rb:107:in `block in evaluate' > 2019-03-22T13:04:22.453 > /usr/share/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:116:in `call' > 2019-03-22T13:04:22.455 > /usr/share/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:116:in > `traverse' > 2019-03-22T13:04:22.457 > /usr/share/ruby/vendor_ruby/puppet/transaction.rb:154:in `evaluate' > 2019-03-22T13:04:22.459 > /usr/share/ruby/vendor_ruby/puppet/resource/catalog.rb:222:in `block in > apply' > 2019-03-22T13:04:22.461 > /usr/share/ruby/vendor_ruby/puppet/util/log.rb:155:in `with_destination' > 2019-03-22T13:04:22.463 > /usr/share/ruby/vendor_ruby/puppet/transaction/report.rb:142:in > `as_logging_destination' > 2019-03-22T13:04:22.465 > /usr/share/ruby/vendor_ruby/puppet/resource/catalog.rb:221:in `apply' > 2019-03-22T13:04:22.467 > /usr/share/ruby/vendor_ruby/puppet/configurer.rb:171:in `block in > apply_catalog' > 2019-03-22T13:04:22.469 /usr/share/ruby/vendor_ruby/puppet/util.rb:223:in > `block in benchmark' > 2019-03-22T13:04:22.472 /usr/share/ruby/benchmark.rb:296:in `realtime' > 2019-03-22T13:04:22.474 /usr/share/ruby/vendor_ruby/puppet/util.rb:222:in > `benchmark' > 2019-03-22T13:04:22.476 > /usr/share/ruby/vendor_ruby/puppet/configurer.rb:170:in `apply_catalog' > 2019-03-22T13:04:22.478 > /usr/share/ruby/vendor_ruby/puppet/configurer.rb:343:in `run_internal' > 2019-03-22T13:04:22.480 > /usr/share/ruby/vendor_ruby/puppet/configurer.rb:221:in `block in run' > 2019-03-22T13:04:22.482 > /usr/share/ruby/vendor_ruby/puppet/context.rb:65:in `override' > 2019-03-22T13:04:22.484 /usr/share/ruby/vendor_ruby/puppet.rb:241:in > `override' > 2019-03-22T13:04:22.486 > /usr/share/ruby/vendor_ruby/puppet/configurer.rb:195:in `run' > 2019-03-22T13:04:22.488 > /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:350:in > `apply_catalog' > 2019-03-22T13:04:22.490 > /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:274:in `block in > main' > 2019-03-22T13:04:22.493 > /usr/share/ruby/vendor_ruby/puppet/context.rb:65:in `override' > 2019-03-22T13:04:22.495 /usr/share/ruby/vendor_ruby/puppet.rb:241:in > `override' > 2019-03-22T13:04:22.497 > /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:225:in `main' > 2019-03-22T13:04:22.499 > /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:170:in `run_command' > 2019-03-22T13:04:22.501 > /usr/share/ruby/vendor_ruby/puppet/application.rb:344:in `block in run' > 2019-03-22T13:04:22.503 /usr/share/ruby/vendor_ruby/puppet/util.rb:540:in > `exit_on_fail' > 2019-03-22T13:04:22.505 > /usr/share/ruby/vendor_ruby/puppet/application.rb:344:in `run' > 2019-03-22T13:04:22.507 > /usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run' > 2019-03-22T13:04:22.509 > /usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' > 2019-03-22T13:04:22.512 /usr/bin/puppet:5:in `
' [0m > 2019-03-22T13:04:22.514 [0;36mDebug: 2019-03-22 13:04:22 +0000 Applying > settings catalog for sections reporting, metrics [0m > 2019-03-22T13:04:22.516 [0;36mDebug: 2019-03-22 13:04:22 +0000 Finishing > transaction 84378320 [0m > 2019-03-22T13:04:22.518 [0;36mDebug: 2019-03-22 13:04:22 +0000 Received > report to process from controller-0 [0m > 2019-03-22T13:04:22.520 [0;36mDebug: 2019-03-22 13:04:22 +0000 Evicting > cache entry for environment 'production' [0m > 2019-03-22T13:04:22.522 [0;36mDebug: 2019-03-22 13:04:22 +0000 Caching > environment 'production' (ttl = 0 sec) [0m > 2019-03-22T13:04:22.524 [0;36mDebug: 2019-03-22 13:04:22 +0000 Processing > report from controller-0 with processor Puppet::Reports::Store [0m > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Sat Mar 23 16:06:32 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Sat, 23 Mar 2019 16:06:32 +0000 Subject: [Starlingx-discuss] newbie want some help to contribute to starlingX In-Reply-To: References: Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35ED7102@SHSMSX104.ccr.corp.intel.com> Hi Wang Hao, Welcome to the StarlingX community! We definitely want somebody like you who has the OpenStack experience to join us. I guess you already read StarlingX wiki page: https://wiki.openstack.org/wiki/StarlingX. Joining Wed's weekly community call will be very helpful to catch up the progress on weekly basis. There are couple of LP bugs we marked as "help needed", maybe this can be good start point: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.helpwanted Please feel free to ask questions in the mailing list. Thx. -cindy -----Original Message----- From: hao wang [mailto:sxmatch1986 at gmail.com] Sent: Friday, March 22, 2019 7:42 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] newbie want some help to contribute to starlingX Hi, starlingx My name is Wang Hao (Irc nickname: wanghao), a senior software engineer in FiberHome Telecommunication Technologies Co., Ltd. I'm an old soldier to contribute to OpenStack projects like Cinder, Nova, Zaqar, etc. since 2013. Also is the PTL of Zaqar project from 2017. I kept eye on starlingx project for a while and knew this is an important project in NFV and edge computing areas. I (and my team) want to contribute this project but as a newbie here, really appreciate who can give me some help how to do this. Thanks _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Don.Penney at windriver.com Sun Mar 24 23:06:27 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Sun, 24 Mar 2019 23:06:27 +0000 Subject: [Starlingx-discuss] Building from master is failing In-Reply-To: <9a5f2200-d6f1-bb51-84ba-e86fd0ddfe08@linux.intel.com> References: <9a5f2200-d6f1-bb51-84ba-e86fd0ddfe08@linux.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA46AB84@ALA-MBD.corp.ad.wrs.com> I built a few days ago with no problems, but I'll give it another shot shortly and see if I'm having the same issue -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Friday, March 22, 2019 5:21 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Building from master is failing I am trying to do a container build from master and seem to be having a failure, when building "build-stx-images.sh" stx-ceilometer. I believe that I have most latest build, but it's possibly I am a day or two off. I don't remember seeing any gerrit reviews for Panko, but maybe I missed it. Thoughts? Sau! Error from build-stx-images.sh script: Collecting pylint Downloading https://files.pythonhosted.org/packages/59/65/adcffa71fe942313c4d9e9284565d9a9e67798f4771f464e1d5dd58fea88/pylint-1.9.4-py2.py3-none-any.whl (689kB) Collecting panko==5.0.0 ^[[91m Could not find a version that satisfies the requirement panko==5.0.0 (from versions: 1.0.0.0b1, 1.0.0.0b3, 1.0.0.0rc1, 1.0.0, 2.0.0, 2.0.1, 2.0.2, 2.0.3, 3.0.0, 3.1.0, 4.0.0, 4.0.1, 4.0.2, 6.0.0.0rc1) ^[[0m^[[91mNo matching distribution found for panko==5.0.0 ^[[0mThe command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Failed to build stx-ceilometer... Aborting Skipping stx-cinder Skipping stx-glance Skipping stx-gnocchi Skipping stx-heat Skipping stx-horizon Skipping stx-keystone Skipping stx-neutron Skipping stx-nova ####################################### There were 1 failures: stx-ceilometer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Don.Penney at windriver.com Sun Mar 24 23:12:46 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Sun, 24 Mar 2019 23:12:46 +0000 Subject: [Starlingx-discuss] Building from master is failing References: <9a5f2200-d6f1-bb51-84ba-e86fd0ddfe08@linux.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA46AB93@ALA-MBD.corp.ad.wrs.com> Can you provide your build commands? The master-wheels.cfg explicitly includes panko 5.0.0, so if you're building your own wheels tarball or using the CENGN tarball, you should have panko-5.0.0-py2-none-any.whl present. -----Original Message----- From: Penney, Don Sent: Sunday, March 24, 2019 7:06 PM To: 'Saul Wold'; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Building from master is failing I built a few days ago with no problems, but I'll give it another shot shortly and see if I'm having the same issue -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Friday, March 22, 2019 5:21 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Building from master is failing I am trying to do a container build from master and seem to be having a failure, when building "build-stx-images.sh" stx-ceilometer. I believe that I have most latest build, but it's possibly I am a day or two off. I don't remember seeing any gerrit reviews for Panko, but maybe I missed it. Thoughts? Sau! Error from build-stx-images.sh script: Collecting pylint Downloading https://files.pythonhosted.org/packages/59/65/adcffa71fe942313c4d9e9284565d9a9e67798f4771f464e1d5dd58fea88/pylint-1.9.4-py2.py3-none-any.whl (689kB) Collecting panko==5.0.0 ^[[91m Could not find a version that satisfies the requirement panko==5.0.0 (from versions: 1.0.0.0b1, 1.0.0.0b3, 1.0.0.0rc1, 1.0.0, 2.0.0, 2.0.1, 2.0.2, 2.0.3, 3.0.0, 3.1.0, 4.0.0, 4.0.1, 4.0.2, 6.0.0.0rc1) ^[[0m^[[91mNo matching distribution found for panko==5.0.0 ^[[0mThe command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Failed to build stx-ceilometer... Aborting Skipping stx-cinder Skipping stx-glance Skipping stx-gnocchi Skipping stx-heat Skipping stx-horizon Skipping stx-keystone Skipping stx-neutron Skipping stx-nova ####################################### There were 1 failures: stx-ceilometer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Frank.Miller at windriver.com Mon Mar 25 01:11:34 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 25 Mar 2019 01:11:34 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX Infrastructure Containerization Message-ID: Re-sending as the original outlook meeting cancelation is held up due to "awaits moderator approval". FYI: For people who accept a meeting invite to starlingx-discuss, Outlook adds them to the cc list which then causes the "Too many recipients to the message" error when updating the original meeting invite. Frank -----Original Appointment----- From: Miller, Frank Sent: Sunday, March 24, 2019 9:04 PM To: starlingx-discuss at lists.starlingx.io; Liu, Tao; Kung, John Cc: 'Armstrong, Robert H'; 'Jones, Bruce E'; Mihai, Irina; Church, Robert; Rowsell, Brent; Seiler, Glenn; Chen, Jacky; Smith, Tyler; 'An, Ran1'; 'Lara, Cesar'; 'Martinez Monroy, Elio'; 'Hu, Wei W'; 'Xie, Cindy'; Wensley, Barton; Eslimi, Dariush; 'Carlos Cebrian'; Young, Ken; Friesen, Chris; 'Botello Ortega, Luis'; Hellmann, Gil; Waines, Greg; 'Arce Moreno, Abraham'; Komiyama, Takeo; Nasir, Shoaib; 'Ponce Castaneda, Guillermo A'; 'Alonso, Juan Carlos'; 'Lemus Contreras, Cristopher J'; Rasa, Nimalini; 'Shuquan Huang'; Poncea, Ovidiu Subject: Canceled: StarlingX Infrastructure Containerization When: Monday, March 25, 2019 11:00 AM-11:30 AM (UTC-05:00) Eastern Time (US & Canada). Where: https://zoom.us/j/342730236 Importance: High Folks - apologies but I need to cancel the Containerization meeting planned for March 25th. If you have any concerns or topics you wanted to raise at the Containerization meeting please email and I'll look for an opportunity to respond on Tuesday or later in the week, Thank-you. Frank ----------------------------> 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: From skaplons at redhat.com Sun Mar 24 08:43:26 2019 From: skaplons at redhat.com (Slawomir Kaplonski) Date: Sun, 24 Mar 2019 09:43:26 +0100 Subject: [Starlingx-discuss] [Neutron] Question on uwsgi based web server support for neutron In-Reply-To: <76647BD697F40748B1FA4F56DA02AA0B4D59E0E3@SHSMSX104.ccr.corp.intel.com> References: <76647BD697F40748B1FA4F56DA02AA0B4D595BCF@SHSMSX104.ccr.corp.intel.com> <7B5D39C4-7B28-488F-A731-0831D0B44F7C@redhat.com> <76647BD697F40748B1FA4F56DA02AA0B4D595D05@SHSMSX104.ccr.corp.intel.com> <76647BD697F40748B1FA4F56DA02AA0B4D59E0E3@SHSMSX104.ccr.corp.intel.com> Message-ID: <2D763631-189D-4334-8343-247BA39CDC48@redhat.com> Hi, I’m not sure but probably, if this would require any changes in neutron code, then it should be proposed as RFE and discussed by drivers team. > Wiadomość napisana przez Le, Huifeng w dniu 11.03.2019, o godz. 03:05: > > Sean and Slawek, > > Thanks much for the comments! So What the process to propose this default configuration for Train cycle? Thanks much! > > Best Regards, > Le, Huifeng > > -----Original Message----- > From: Sean Mooney [mailto:smooney at redhat.com] > Sent: Tuesday, March 5, 2019 10:52 PM > To: Slawomir Kaplonski ; Le, Huifeng > Cc: Miguel Lavalle ; Khalil, Ghada ; starlingx-discuss at lists.starlingx.io; openstack-dev at lists.openstack.org > Subject: Re: [Neutron] Question on uwsgi based web server support for neutron > > On Tue, 2019-03-05 at 08:53 +0100, Slawomir Kaplonski wrote: >> Hi, >> >> I don’t know about any plans to make it default now in Stein. IMO We can think about it in Train cycle. > for what its worth i dont think project actully have default in repect to eventlets vs wsgi it really the installer that do have default. keystone i think is the only project that "defults" to wsgi and that is because they delete the eventlet version if i am not miss remembering. > > that said i do think that more project should consider moving to wsgi only. > eventually i would hope we could drop all eventlet depencies in openstack but i know that for several of the agents like the nova agent that is hard to do. for the apis however wsgi provided a convent way to drop that depency and improve performance at the same time. >> >>> Wiadomość napisana przez Le, Huifeng w dniu 05.03.2019, o godz. 08:37: >>> >>> Slawek, >>> >>> Thanks much for the information. Yes, it is already possible to >>> configure using uswgi for neutron API which is also the way I used to verify the issue. >>> >>> So will it be used as default configuration (as other openstack >>> projects) for neutron in any planned release? or it supposed to require the system admin to apply this configuration manually when deployment? thanks much! >>> >>> Best Regards, >>> Le, Huifeng >>> >>> -----Original Message----- >>> From: Slawomir Kaplonski [mailto:skaplons at redhat.com] >>> Sent: Tuesday, March 5, 2019 3:20 PM >>> To: Le, Huifeng >>> Cc: Miguel Lavalle ; Khalil, Ghada >>> ; starlingx-discuss at lists.starlingx.io; >>> openstack-dev at lists.openstack.org >>> Subject: Re: [Neutron] Question on uwsgi based web server support >>> for neutron >>> >>> Hi, >>> >>>> Wiadomość napisana przez Le, Huifeng w dniu 05.03.2019, o godz. 03:26: >>>> >>>> Miguel, >>>> >>>> During STX deployment process, it is found the current neutron >>>> eventlet based web server has some unexpected behavior for >>>> multiple long live clients and it is also verified that apache WSGI/uwsgi based web server can solve such issues. the detail information of this issue can be found at https://bugs.launchpad.net/neutron/+bug/1800599. >>>> >>>> >>>> So is there any plan or roadmap to switch to the new apache >>>> WSGI/uswgi based web server for Neutron in Stein release? Thanks much! >>> >>> AFAIK it is already possible since Rocky >>> https://docs.openstack.org/neutron/rocky/admin/config-wsgi.html >>> Is it what You are asking for? >>> >>>> >>>> Best Regards, >>>> Le, Huifeng >>> >>> — >>> Slawek Kaplonski >>> Senior software engineer >>> Red Hat >>> >> >> — >> Slawek Kaplonski >> Senior software engineer >> Red Hat >> >> > — Slawek Kaplonski Senior software engineer Red Hat From Frank.Miller at windriver.com Mon Mar 25 01:03:30 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 25 Mar 2019 01:03:30 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX Infrastructure Containerization Message-ID: Folks - apologies but I need to cancel the Containerization meeting planned for March 25th. If you have any concerns or topics you wanted to raise at the Containerization meeting please email and I'll look for an opportunity to respond on Tuesday or later in the week, Thank-you. Frank ----------------------------> 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: 6426 bytes Desc: not available URL: From chenjie.xu at intel.com Mon Mar 25 05:54:07 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Mon, 25 Mar 2019 05:54:07 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> <7027C5CE-7CC6-44FF-9649-2287F2B233D1@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F35ECF687@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530564B4@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CF4CB@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9F898@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CFA11@ALA-MBD.corp.ad.wrs.com> <1466AF2176E6F040BD63860D0A241BBD46CA30D1@FMSMSX109.amr.corp.intel.com> Message-ID: Hi Matt, The ISO image for OVSDPDK Upgrade Testing is built by Shuicheng. According to him, the image is built based on latest master code on March 6. The build.info is below: (cat /etc/build.info) SW_VERSION="19.01" BUILD_TARGET="Unknown" BUILD_TYPE="Informal" BUILD_ID="n/a" JOB="n/a" BUILD_BY="slin14" BUILD_NUMBER="n/a" BUILD_HOST="" BUILD_DATE="2019-03-06 16:34:21 +0000" BUILD_DIR="/" WRS_SRC_DIR="/localdisk/designer/slin14/starlingx/cgcs-root" WRS_GIT_BRANCH="centos76" CGCS_SRC_DIR="/localdisk/designer/slin14/starlingx/cgcs-root/stx" CGCS_GIT_BRANCH="centos76" Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Friday, March 22, 2019 8:31 PM To: Xu, Chenjie ; Martinez Monroy, Elio ; Khalil, Ghada ; Lin, Shuicheng ; Cabrales, Ada ; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io' ; Zhao, Forrest Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Comparing the image list to our labs shows a difference in the image IDs (sha), but I’m not sure if that is just a difference in build baselines or an actual difference in the images. Since some of them align, I think you might be running a different set of images. Can you confirm what the build baseline is that you pulled the images from? I have attached a sample list from our labs for comparison. -Matt From: "Xu, Chenjie" > Date: Friday, March 22, 2019 at 7:25 AM To: "Peters, Matt" >, "Martinez Monroy, Elio" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, The docker image versions in my environment and helm-charts-manifest-no-tests.tgz has been attached. The helm-charts-manifest-no-tests.tgz is built by Shuicheng for the OVSDPDK Upgrade Testing ISO image. Best Regards, Xu, Chenjie From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Thursday, March 21, 2019 11:20 PM To: Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Perfect, I will be cheking my mail for that new ISO. Adding Richo , he is the one that is going to execute the tests. Thanks BR Elio From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, March 21, 2019 9:15 AM To: Lin, Shuicheng >; Cabrales, Ada >; Martinez Monroy, Elio > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, We discussed this in the networking bi-weekly team meeting today. Please re-enable the mlx pmd – re-apply the following patch: https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch Then please rebase to the latest master and build a new load for Ada’s team to start testing Hi Elio, One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 Thanks, Ghada From: Khalil, Ghada Sent: Thursday, March 21, 2019 9:12 AM To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. Can you confirm that the load being used has the mellanox pmd enabled in it? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 21, 2019 9:03 AM To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie for the testing. Hi all, Does it mean greenlight for code merge, or any other test is needed? Here is the patch list: https://review.openstack.org/642672 https://review.openstack.org/642673 Best Regards Shuicheng From: Xu, Chenjie Sent: Thursday, March 21, 2019 5:46 PM To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Mon Mar 25 06:09:44 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 25 Mar 2019 02:09:44 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_docker_flock_images - Build # 59 - Failure! Message-ID: <803398080.24.1553494185647.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 59 Status: Failure Timestamp: 20190325T041842Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190325T013001Z/logs -------------------------------------------------------------------------------- Parameters HOST_PORT: 80 MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190325T013001Z OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root BASE_VERSION: dev-20190325T013001Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190325T013001Z/logs REGISTRY_USERID: slittlewrs HOST: build.starlingx.cengn.ca LATEST_PREFIX: dev PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190325T013001Z/logs PUBLISH_TIMESTAMP: 20190325T013001Z FLOCK_VERSION: dev-centos-master-20190325T013001Z PREFIX: dev OPENSTACK_RELEASE: master TIMESTAMP: 20190325T013001Z REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20190325T013001Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Mon Mar 25 06:09:48 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 25 Mar 2019 02:09:48 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_docker_images - Build # 57 - Failure! Message-ID: <110522562.27.1553494189506.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 57 Status: Failure Timestamp: 20190325T041111Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190325T013001Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190325T013001Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190325T013001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190325T013001Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos PUBLISH_TIMESTAMP: 20190325T013001Z DOCKER_BUILD_ID: jenkins-master-20190325T013001Z-builder OPENSTACK_RELEASE: master TIMESTAMP: 20190325T013001Z OS_VERSION: 7.6.1810 PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/20190325T013001Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20190325T013001Z/outputs From build.starlingx at gmail.com Mon Mar 25 06:09:51 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 25 Mar 2019 02:09:51 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 35 - Failure! Message-ID: <919477488.30.1553494193013.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 35 Status: Failure Timestamp: 20190325T013001Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190325T013001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false BUILD_CONTAINERS_ZZZ: false From himanshugoyal500 at gmail.com Mon Mar 25 08:03:46 2019 From: himanshugoyal500 at gmail.com (Himanshu Goyal) Date: Mon, 25 Mar 2019 13:33:46 +0530 Subject: [Starlingx-discuss] cpu model Passthrough with Intel/Skylake-Server-IBRS In-Reply-To: References: Message-ID: Hi, I tried manual installation of rpm packages "qemu-kvm-ev-3.0.0-0.tis.97.x86_64.rpm" but it is not working, Please help how can i upgrade the required packages. Many thanks, Himanshu Goyal On Fri, Mar 22, 2019 at 3:57 PM Himanshu Goyal wrote: > Hi, > > I'm using starlingX release "stx.2018.10", and "Intel/Skylake-Server-IBRS" > as my compute server, trying to create a VM with cpu_model as passthrough > but it is giving a error. > > Error: > No valid host was found. There are not enough hosts available. compute-0: > (ComputeFilter) host is disabled, reason: disabled by VIM*, compute-1: > (VCpuModelFilter) Host VCPU model Skylake-Server-IBRS required Passthrough* > > > I checked the starling-Discuss page & found it is fixed with qemu-kvm > version:qemu-kvm-ev-3.0.0-0.tis.97 > > *starling-discuss link:* > > http://lists.starlingx.io/pipermail/starlingx-discuss/2018-December/002110.html > > Current qemu-kvm version in my setup: > q*emu-img version 2.10.0(qemu-kvm-ev-2.10.0-0.tis.0)* > > Please let me know how can i upgrade qemu-kvm package in my compute > without disturbing much running setup. > > Many Thanks, > Himanshu Goyal > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Mon Mar 25 11:06:41 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Mon, 25 Mar 2019 11:06:41 +0000 Subject: [Starlingx-discuss] newbie want some help to contribute to starlingX In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F35ED7102@SHSMSX104.ccr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F35ED7102@SHSMSX104.ccr.corp.intel.com> Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC0A1CBE9@ALA-MBD.corp.ad.wrs.com> Hi Wang Hao - welcome! You can find the full list of meetings from the main wiki at [1] - including the weekly meeting for OpenStack distro work [2] on Tuesdays, and, as Cindy mentioned, our Community call [3] on Wednesdays. Bill... [1] https://wiki.openstack.org/wiki/Starlingx/Meetings [2] https://wiki.openstack.org/wiki/Starlingx/Meetings#6am_PDT_.2F_1400_UTC_-_Distro_OpenStack_Team_Call [3] https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call -----Original Message----- From: Xie, Cindy Sent: Saturday, March 23, 2019 12:07 PM To: hao wang ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] newbie want some help to contribute to starlingX Hi Wang Hao, Welcome to the StarlingX community! We definitely want somebody like you who has the OpenStack experience to join us. I guess you already read StarlingX wiki page: https://wiki.openstack.org/wiki/StarlingX. Joining Wed's weekly community call will be very helpful to catch up the progress on weekly basis. There are couple of LP bugs we marked as "help needed", maybe this can be good start point: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.helpwanted Please feel free to ask questions in the mailing list. Thx. -cindy -----Original Message----- From: hao wang [mailto:sxmatch1986 at gmail.com] Sent: Friday, March 22, 2019 7:42 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] newbie want some help to contribute to starlingX Hi, starlingx My name is Wang Hao (Irc nickname: wanghao), a senior software engineer in FiberHome Telecommunication Technologies Co., Ltd. I'm an old soldier to contribute to OpenStack projects like Cinder, Nova, Zaqar, etc. since 2013. Also is the PTL of Zaqar project from 2017. I kept eye on starlingx project for a while and knew this is an important project in NFV and edge computing areas. I (and my team) want to contribute this project but as a newbie here, really appreciate who can give me some help how to do this. Thanks _______________________________________________ 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 Mar 25 12:27:15 2019 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Mon, 25 Mar 2019 12:27:15 +0000 Subject: [Starlingx-discuss] StarlingX activity metrics In-Reply-To: References: Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA81FC6@ALA-MBD.corp.ad.wrs.com> Ildiko, I played around with the new metrics a bit and it looks to me like they are almost all based on commits. The stackalytics metrics considered a mix of commits, reviews and approvals, which I think is much more useful. Can you update the dashboard to include review/approval metrics as well? Bart -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: March 4, 2019 7:51 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX activity metrics Hi StarlingX Community, As some of you already heard, the OSF staff has been working with Bitergia to provide a proof-of-concept dashboard of community activity metrics for StarlingX. This dashboard is now available at: https://starlingx.biterg.io/ It currently contains the default set of Bitergia dashboards, so you might find some panels more interesting than others. It tracks Git data, Gerrit activity, and mailing-list activity. We have the possibility to customize or add panels, so if you see some analysis or panel that would be specifically useful for StarlingX, let us know! Some identities are duplicated (especially across data sources as people don't use the same email address in for example git and the ML) -- although we did a pass at correcting those, there may be a few persisting. In the same vein, some affiliations may still be "unknown" -- we are trying to see if there would be a way for people to fix that data directly, rather than relying on a community manager to do so. Please also note that the database changes need some time to take effect on the dashboard. We'll run this proof-of-concept for a year, to confirm that the data is useful and accurate before we pursue this further. During this period, don't hesitate to report issues or start a discussion about features. The mailing-list is a good venue for that, until we set up a more formal issue reporting channel (Bitergia is using Gitlab). Thanks, Ildikó _______________________________________________ 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 Mon Mar 25 11:56:58 2019 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Mon, 25 Mar 2019 11:56:58 +0000 Subject: [Starlingx-discuss] Strange Network behavior Message-ID: Hi, i have a network behavior which i can't explain, attached is the network schema. Basically everything works as it should and is to be expected, only my VM2 is not reachable via "Floating IP 2" ?! VM1 can easily be reached via "Floating IP1" and VM1 can also reach VM2 via Network1. The VM2 can also be reached via the "Floating IP 3" from the console PC. so, I don't understand why this doesn't work over the "Floating IP 2" ? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: network.pdf Type: application/pdf Size: 143665 bytes Desc: network.pdf URL: From liang.a.fang at intel.com Mon Mar 25 15:13:38 2019 From: liang.a.fang at intel.com (Fang, Liang A) Date: Mon, 25 Mar 2019 15:13:38 +0000 Subject: [Starlingx-discuss] Code review of cinder raw cache in stx-config In-Reply-To: <18E9F5EA-650C-4304-BEE2-440A9B92D8C0@windriver.com> References: <0BB14CDD-5E16-45BC-9117-E1787519E895@windriver.com> <18E9F5EA-650C-4304-BEE2-440A9B92D8C0@windriver.com> Message-ID: Hi Bob and Brent The approach I mentioned in last email is not workable because: - It is cinder-vol who are using this internal project/user id - Need to call keystone with admin privilege to get the project list, then find id from name in the list. But cinder-vol don’t have admin privilege. So, finally I implemented in openstack-helm. See review: https://review.openstack.org/#/c/647493/ - Given a default name(internal_cinder) in values.yaml - Prepare cinder.conf in initContainers phase It works now, see: [cid:image001.png at 01D4E360.5F9A4BA0] The review is in openstack-helm repo now, welcome to comment there, thanks. Regards Liang From: Church, Robert [mailto:Robert.Church at windriver.com] Sent: Thursday, March 14, 2019 8:48 PM To: Fang, Liang A ; Rowsell, Brent Cc: Poncea, Ovidiu ; Zhu, Vivian ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Code review of cinder raw cache in stx-config Hi Liang, See Inline… Regards, Bob From: "Fang, Liang A" > Date: Thursday, March 14, 2019 at 6:35 AM To: Robert Church >, "Rowsell, Brent" > Cc: Ovidiu Poncea >, "Zhu, Vivian" >, "Jones, Bruce E" >, "starlingx-discuss at lists.starlingx.io" > Subject: RE: [Starlingx-discuss] Code review of cinder raw cache in stx-config Hi Bob Thanks for your reply. So cinder raw cache feature in fact already can be enabled in current containerized Starlingx, user just need to follow the instructions you gave below. The code review https://review.openstack.org/#/c/633400/ is not needed anymore. [RTC] Yes. I’ve tested the basic functionality and it works as advertised. As Brent mentioned in his response keep this review or abandon it.. Up to you… Regarding adding project_id and user_id in cinder.conf in initial application install, it seems like an small enhancement now because this can be done easily via “system helm-override-update”. I checked with cores in openstack-helm irc, Some cores feel project_id and user_id should be populated by whatevers orchestrating the deployment of the charts. An approach(may don’t needed anymore) I’m thinking is: 1. Submit a patch to cinder, let cinder accept internal_project_name and internal_user_name in cinder.conf, not the id. [RTC] Agreed. We’d need an upstream patch to Cinder so that it would look up the UUID based on the project/user name provided in the conf file <-- this is the key element, I think 1. Hardcode the internal_project_name and internal_user_name in value.yaml [RTC] Agreed. This would provide the ability to keep the default or override the project/user to suit a deployment 1. Let job-ks-user.yaml or create a new job to create the hardcoded project and user [RTC] You could enable the bootstrap script (see how keystone does it) and then add the project/user creation step in values .yaml Regards Liang From: Church, Robert [mailto:Robert.Church at windriver.com] Sent: Wednesday, March 13, 2019 10:44 PM To: Fang, Liang A >; Rowsell, Brent > Cc: Poncea, Ovidiu >; Zhu, Vivian >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Code review of cinder raw cache in stx-config Hi Liang, I took a look at this yesterday to understand what you are up against here. Ideally we would want some combination of a system helm override/armada manifest change to automatically provision the Cinder image-volume cache when the stx-openstack application is installed. We do not want to use any platform specific interface changes (i.e. system backend-modify or a new API) since we want to decouple openstack k8s application dependencies from the general k8s platform provisioning. Using the current content on master, here are the following steps required by an end user to enable this feature: # Initial application install system application-apply stx-openstack # After install, the feature requires a project/user to manage the cache openstack project create --enable --description "Block Storage Internal Tenant" cinder-internal openstack user create --project cinder-internal cinder-internal TENANTID=$(openstack project list | awk /cinder-internal/'{print $2}') USERID=$(openstack user list | awk /cinder-internal/'{print $2}') # The created project/user are needed in cinder.conf along with enabling the cache for the specific backend (we define ceph-store as part of the original application apply). Reapply the application to trigger the armada upgrade to cinder system helm-override-update cinder openstack --reuse-values --set conf.cinder.DEFAULT.cinder_internal_tenant_project_id=$TENANTID system helm-override-update cinder openstack --reuse-values --set conf.cinder.DEFAULT.cinder_internal_tenant_user_id=$USERID system helm-override-update cinder openstack --reuse-values --set conf.backends.ceph-store.image_volume_cache_enabled=true system helm-override-update cinder openstack --reuse-values --set conf.backends.ceph-store.image_volume_cache_max_size_gb=10 system helm-override-update cinder openstack --reuse-values --set conf.backends.ceph-store.image_volume_cache_max_count=5 system application-apply stx-openstack Now, back to the desired approach. The challenge here is we need a way to create a project/user as part of the initial application install and look up the UUIDs to embed in an override in a declarative manner. I’m not sure this is possible in a single application apply. 1) We could enable creating the project/user as part of the Cinder bootstrap script, but these would not be created/available at the time overrides are declared for cinder’s configuration 2) We could use an existing project/user (i.e. admin) and avoid creating a dedicated cinder project/user, but again on the initial application install they are not available at the time overrides are declared for cinder’s configuration Looking across the charts and the helm-toolkit in the OSH projects, I have yet to see an easy way to accomplish this. I think you should check with the OSH project cores to see if they have any suggestions on the best way to tackle this as part of the first install of the Cinder chart OR if a two pass approach is required (install then upgrade) Bob From: "Fang, Liang A" > Date: Wednesday, March 13, 2019 at 8:22 AM To: "Rowsell, Brent" > Cc: Ovidiu Poncea >, "Zhu, Vivian" >, "Jones, Bruce E" >, "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] Code review of cinder raw cache in stx-config Hi Brent Regarding the raw cache review: https://review.openstack.org/#/c/633400/ Currently the code is implemented according the discussion before between Ovidiu and Lisa: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-January/002548.html The raw cache is configured via “system storage-backend-modify”. e.g. system storage-backend-modify ceph-store cinder_raw_cache_gib=10 Your opinion is to decouple openstack from the storage backend. Thanks for your comment. I take a look of system subcommand, there’s no subcommand for openstack currently, at this point “system storage-backend-modify” seems is the best choice. Should we add subcommand “openstack”? Something like: system openstack cinder_raw_cache_gib=10 Or should we config openstack in other way? Could you please give suggestion on this? Thank you very much Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8671 bytes Desc: image001.png URL: From glenn.seiler at windriver.com Mon Mar 25 15:29:10 2019 From: glenn.seiler at windriver.com (Seiler, Glenn) Date: Mon, 25 Mar 2019 15:29:10 +0000 Subject: [Starlingx-discuss] newbie want some help to contribute to starlingX In-Reply-To: References: Message-ID: Hello Wang Hao Thank you for your interest in StarlingX. I think Cindy gave some very good advice as to where your team could make an immediate impact by looking at the some of the bugs marked as Help Needed. Also, if you or any of your team members are planning to be in Denver for the Open Infrastructure Summit, there will be a hands-on workshop earlier in the summit, and also a StarlingX PTG meeting at the end of the week on Thur and Friday. That would be a very good opportunity to learn more and meet some of the StarlingX team. We're happy to help provide any information. Regards -glenn seiler -----Original Message----- From: hao wang [mailto:sxmatch1986 at gmail.com] Sent: Friday, March 22, 2019 7:42 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] newbie want some help to contribute to starlingX Hi, starlingx My name is Wang Hao (Irc nickname: wanghao), a senior software engineer in FiberHome Telecommunication Technologies Co., Ltd. I'm an old soldier to contribute to OpenStack projects like Cinder, Nova, Zaqar, etc. since 2013. Also is the PTL of Zaqar project from 2017. I kept eye on starlingx project for a while and knew this is an important project in NFV and edge computing areas. I (and my team) want to contribute this project but as a newbie here, really appreciate who can give me some help how to do this. Thanks _______________________________________________ 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 Mon Mar 25 19:12:15 2019 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 25 Mar 2019 12:12:15 -0700 Subject: [Starlingx-discuss] README for new github.com/starlingx-staging/tools-contrib repo In-Reply-To: References: Message-ID: <92a9da88-b75b-88a5-b661-6682a84beff4@linux.intel.com> On 3/22/19 10:55 AM, Dean Troyer wrote: > On Fri, Mar 22, 2019 at 12:29 PM Saul Wold wrote: >> Please take a quick review of the README for the new Contribution area >> in the https://github.com/starlingx-staging/tools-contrib repo. >> >> Please provide feedback, I have initialized the repo and will add the >> README over the weekend. > > Or.... (wait for it) > > add it as a PR and have the conversation there, you know, all > code-review-y like :) > Done: https://github.com/starlingx-staging/tools-contrib/pull/1 > In the mean time, I think it would be useful to have a minimal doc > requirement, a) a README that at least says what it is, and b) a line > in the top-level README to make an index of contents. > > You hit what I think are the foundation requirements (license, > required DCO, no required CLA). > > Do we have the volunteers with the commit bit on this repo identified > yet? I'd be happy letting them further refine the guidelines, which > could be the second commit. > I guess I will start out and can add anyone one else that's interested. Sau! > Thanks for getting this set up Saul. > > dt > From serverascode at gmail.com Mon Mar 25 19:15:13 2019 From: serverascode at gmail.com (Curtis) Date: Mon, 25 Mar 2019 15:15:13 -0400 Subject: [Starlingx-discuss] README for new github.com/starlingx-staging/tools-contrib repo In-Reply-To: <92a9da88-b75b-88a5-b661-6682a84beff4@linux.intel.com> References: <92a9da88-b75b-88a5-b661-6682a84beff4@linux.intel.com> Message-ID: On Mon, Mar 25, 2019 at 3:13 PM Saul Wold wrote: > > > On 3/22/19 10:55 AM, Dean Troyer wrote: > > On Fri, Mar 22, 2019 at 12:29 PM Saul Wold wrote: > >> Please take a quick review of the README for the new Contribution area > >> in the https://github.com/starlingx-staging/tools-contrib repo. > >> > >> Please provide feedback, I have initialized the repo and will add the > >> README over the weekend. > > > > Or.... (wait for it) > > > > add it as a PR and have the conversation there, you know, all > > code-review-y like :) > > > Done: https://github.com/starlingx-staging/tools-contrib/pull/1 > > > > In the mean time, I think it would be useful to have a minimal doc > > requirement, a) a README that at least says what it is, and b) a line > > in the top-level README to make an index of contents. > > > > You hit what I think are the foundation requirements (license, > > required DCO, no required CLA). > > > > Do we have the volunteers with the commit bit on this repo identified > > yet? I'd be happy letting them further refine the guidelines, which > > could be the second commit. > > > I guess I will start out and can add anyone one else that's interested. > > Sau! > > > Thanks for getting this set up Saul. > > > > dt > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Mon Mar 25 19:17:57 2019 From: serverascode at gmail.com (Curtis) Date: Mon, 25 Mar 2019 15:17:57 -0400 Subject: [Starlingx-discuss] README for new github.com/starlingx-staging/tools-contrib repo In-Reply-To: References: <92a9da88-b75b-88a5-b661-6682a84beff4@linux.intel.com> Message-ID: On Mon, Mar 25, 2019 at 3:15 PM Curtis wrote: > > > On Mon, Mar 25, 2019 at 3:13 PM Saul Wold wrote: > >> >> >> On 3/22/19 10:55 AM, Dean Troyer wrote: >> > On Fri, Mar 22, 2019 at 12:29 PM Saul Wold wrote: >> >> Please take a quick review of the README for the new Contribution area >> >> in the https://github.com/starlingx-staging/tools-contrib repo. >> >> >> >> Please provide feedback, I have initialized the repo and will add the >> >> README over the weekend. >> > >> > Or.... (wait for it) >> > >> > add it as a PR and have the conversation there, you know, all >> > code-review-y like :) >> > >> Done: https://github.com/starlingx-staging/tools-contrib/pull/1 >> >> >> > In the mean time, I think it would be useful to have a minimal doc >> > requirement, a) a README that at least says what it is, and b) a line >> > in the top-level README to make an index of contents. >> > >> > You hit what I think are the foundation requirements (license, >> > required DCO, no required CLA). >> > >> > Do we have the volunteers with the commit bit on this repo identified >> > yet? I'd be happy letting them further refine the guidelines, which >> > could be the second commit. >> > >> I guess I will start out and can add anyone one else that's interested. >> >> First, I think a blank message from me just went out. Thanks gmail! Second, thanks for this repository. I think it's a good idea and we'll see if anyone uses it. :) I think once the summit workshop gets a bit farther along we can bring some of that work into this repository. There will likely be some ansible that automates the deployment of the workshop. Thanks, Curtis > Sau! >> >> > Thanks for getting this set up Saul. >> > >> > dt >> > >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > > -- > Blog: serverascode.com > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Mon Mar 25 19:58:36 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 25 Mar 2019 19:58:36 +0000 Subject: [Starlingx-discuss] Minor change to the StarlingX Bug Template Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4D1966@ALA-MBD.corp.ad.wrs.com> Hello all, In an effort to make it easy to determine if an issue is recently introduced, the following section has been added to the bug template. Last Pass -------------- Did this test scenario pass previously? If so, please indicate the load/pull time info of the last pass. Use this section to also indicate if this is a new test scenario. The wiki and the Launchpad template have been updated: https://wiki.openstack.org/wiki/StarlingX/BugTemplate Thanks, Ghada -------------- next part -------------- An HTML attachment was scrubbed... URL: From ada.cabrales at intel.com Mon Mar 25 22:51:39 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Mon, 25 Mar 2019 22:51:39 +0000 Subject: [Starlingx-discuss] [ Testing ] Meeting - Cancelling 03/26/2019 Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CDAF1FA@FMSMSX114.amr.corp.intel.com> Hello, I'm cancelling this week meeting due to a conflict and revisiting of the meeting dates for the May release. Any question, please contact me by email. Thanks Ada From mario.alfredo.c.arevalo at intel.com Tue Mar 26 00:38:07 2019 From: mario.alfredo.c.arevalo at intel.com (Arevalo, Mario Alfredo C) Date: Tue, 26 Mar 2019 00:38:07 +0000 Subject: [Starlingx-discuss] Fault Management Containerization (SB 2004008) Follow Up In-Reply-To: References: Message-ID: <6594B51DBE477C48AAE23675314E6C466459EDD6@fmsmsx107.amr.corp.intel.com> Hi team, Thank you for your feedback from our last meeting, and this is my update. I am checking all points described in this thread. Actually I have got progress in the topic related to snmp and the relation with oamcontroller, sysinv and cgts-client. I plan to send a PR with information about findings/architecture to the stx-fault/doc in a future. I think, it is not necessary another meeting as it was mentioned, I think I have enough information to continue and I am going to update the current reviews and send news according to the points discussed until today, and contact Tao for specific questions. Thanks Tao, Abraham and Frank. Best regards. Mario. ________________________________________ From: Arce Moreno, Abraham Sent: Friday, March 22, 2019 10:37 AM To: starlingx-discuss at lists.starlingx.io Cc: Arevalo, Mario Alfredo C; Tao Liu Subject: Fault Management Containerization (SB 2004008) Follow Up Thanks Frank for setting this up. Thanks everyone for your attendance to this meeting, here you have high level notes and ToDos based in the topics covered. In Summary - The presentation Stx-Fault/Containers is located at [0]. - Tao will kindly update the Fault Management architecture diagram, slide 8. - Mario will send an email no later than Monday afternoon with the latest findings / questions based in his 5 ToDos. - We will meet again on Tuesday to finalize on tasks and implementation details. If we are forgetting about any key point in this email, please do not hesitate to reply. StarlingX Architecture - 2 instances for each of the following projects: - Keystone - Horizon - Barbican - Fault Management will have 2 instances as well. Fault Management Architecture - [ToDo] [Tao] to modify the Fault Management architecture (Slide 8) Thanks Tao! - fm-api runs in compute node, snmp provide interfaces - [ToDo] [Mario] to check these statements Fault Management REST API - [ToDo] [Mario] to write the next level of details for REST API mapping / implementation, consider to include PUT to Event Log. Fault Management Architecture - python-fmclient is a wrapper to fm_cli / fm_api - [ToDo] [Mario] to understand more about fm_cli as a wrapper and how does it interact and affects fault management containerized strategy. FM Proposal - Remove mysql, fm-api, fm-common - [ToDo] [Mario] to understand about the removal of fm-api and fm-common from the containerized instance. - Dependency to cgts-client - [ToDo] [Mario] to understand what is cgtc-client and how does it interacts with fault management and the new containerized instance. OpenStack Applications The following 2 projects will make use of the Fault Management containerized: - starlingx-dashboard - stx-nfv [0] https://docs.google.com/presentation/d/1_vG83aHTToXlIdJxaJpVL-MHWfRGnxLuyEdFDt-nfwo/edit?usp=sharing From cindy.xie at intel.com Tue Mar 26 00:44:27 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 26 Mar 2019 00:44:27 +0000 Subject: [Starlingx-discuss] Fault Management Containerization (SB 2004008) Follow Up In-Reply-To: <6594B51DBE477C48AAE23675314E6C466459EDD6@fmsmsx107.amr.corp.intel.com> References: <6594B51DBE477C48AAE23675314E6C466459EDD6@fmsmsx107.amr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35ED90C1@SHSMSX104.ccr.corp.intel.com> Mario, Nice to know that you're getting all information and having better understanding for the tasks. We probably needs to get a little bit more detail granularity of your plan, for each task in the storyboard: - when the patches will be uploaded for review; - what tests you're planning to do? Any support required from Ada's team? and when... - when you expect the patch review comments can be addressed and patch merged to master. Thanks. - cindy -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Tuesday, March 26, 2019 8:38 AM To: Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Cc: Tao Liu ; Frank.Miller at windriver.com Subject: Re: [Starlingx-discuss] Fault Management Containerization (SB 2004008) Follow Up Hi team, Thank you for your feedback from our last meeting, and this is my update. I am checking all points described in this thread. Actually I have got progress in the topic related to snmp and the relation with oamcontroller, sysinv and cgts-client. I plan to send a PR with information about findings/architecture to the stx-fault/doc in a future. I think, it is not necessary another meeting as it was mentioned, I think I have enough information to continue and I am going to update the current reviews and send news according to the points discussed until today, and contact Tao for specific questions. Thanks Tao, Abraham and Frank. Best regards. Mario. ________________________________________ From: Arce Moreno, Abraham Sent: Friday, March 22, 2019 10:37 AM To: starlingx-discuss at lists.starlingx.io Cc: Arevalo, Mario Alfredo C; Tao Liu Subject: Fault Management Containerization (SB 2004008) Follow Up Thanks Frank for setting this up. Thanks everyone for your attendance to this meeting, here you have high level notes and ToDos based in the topics covered. In Summary - The presentation Stx-Fault/Containers is located at [0]. - Tao will kindly update the Fault Management architecture diagram, slide 8. - Mario will send an email no later than Monday afternoon with the latest findings / questions based in his 5 ToDos. - We will meet again on Tuesday to finalize on tasks and implementation details. If we are forgetting about any key point in this email, please do not hesitate to reply. StarlingX Architecture - 2 instances for each of the following projects: - Keystone - Horizon - Barbican - Fault Management will have 2 instances as well. Fault Management Architecture - [ToDo] [Tao] to modify the Fault Management architecture (Slide 8) Thanks Tao! - fm-api runs in compute node, snmp provide interfaces - [ToDo] [Mario] to check these statements Fault Management REST API - [ToDo] [Mario] to write the next level of details for REST API mapping / implementation, consider to include PUT to Event Log. Fault Management Architecture - python-fmclient is a wrapper to fm_cli / fm_api - [ToDo] [Mario] to understand more about fm_cli as a wrapper and how does it interact and affects fault management containerized strategy. FM Proposal - Remove mysql, fm-api, fm-common - [ToDo] [Mario] to understand about the removal of fm-api and fm-common from the containerized instance. - Dependency to cgts-client - [ToDo] [Mario] to understand what is cgtc-client and how does it interacts with fault management and the new containerized instance. OpenStack Applications The following 2 projects will make use of the Fault Management containerized: - starlingx-dashboard - stx-nfv [0] https://docs.google.com/presentation/d/1_vG83aHTToXlIdJxaJpVL-MHWfRGnxLuyEdFDt-nfwo/edit?usp=sharing _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From kyle.oh95 at gmail.com Tue Mar 26 02:43:35 2019 From: kyle.oh95 at gmail.com (=?UTF-8?B?7Jik7J6s7Jqx?=) Date: Tue, 26 Mar 2019 11:43:35 +0900 Subject: [Starlingx-discuss] [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" Message-ID: Hello StarlingX Teams, I finally deployed duplex starlingx model on two physical servers. However, it was not truly deployed. The "all-in-one controller-1" has deploy failed, The fault management alarm shows, 200.005 Failure: is experiencing a persistent critical 'Management Network' communication failure." And I think above fault is the main reason of deploy failed I followed BIOS Setup for all nodes, and used Feb 22 iso images. I have no idea what can I do :( Any help would be very appreciated. Best Regards, Jaewook. ================================================ *Jaewook Oh* (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Tue Mar 26 02:53:27 2019 From: yong.hu at intel.com (Hu, Yong) Date: Tue, 26 Mar 2019 02:53:27 +0000 Subject: [Starlingx-discuss] [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" In-Reply-To: References: Message-ID: <06F50A69-BBA2-4A6E-986C-74C7B8452A44@intel.com> Have you installed 2 controllers already? If by far you only setup 1 controller, this alarm seems reasonable because it expects to communicate with another controller through mgt network. Regards, Yong From: 오재욱 Date: Tuesday, 26 March 2019 at 10:45 AM To: starlingx-discuss Subject: [Starlingx-discuss] [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" Hello StarlingX Teams, I finally deployed duplex starlingx model on two physical servers. However, it was not truly deployed. The "all-in-one controller-1" has deploy failed, The fault management alarm shows, 200.005 Failure: is experiencing a persistent critical 'Management Network' communication failure." And I think above fault is the main reason of deploy failed I followed BIOS Setup for all nodes, and used Feb 22 iso images. I have no idea what can I do :( Any help would be very appreciated. Best Regards, Jaewook. ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: From kyle.oh95 at gmail.com Tue Mar 26 02:58:52 2019 From: kyle.oh95 at gmail.com (=?UTF-8?B?7Jik7J6s7Jqx?=) Date: Tue, 26 Mar 2019 11:58:52 +0900 Subject: [Starlingx-discuss] Fwd: [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" In-Reply-To: References: <06F50A69-BBA2-4A6E-986C-74C7B8452A44@intel.com> Message-ID: ---------- Forwarded message --------- 보낸사람: 오재욱 Date: 2019년 3월 26일 (화) 오전 11:58 Subject: Re: [Starlingx-discuss] [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" To: Hu, Yong Hi Yong, Umm I think the controller0 was completely installed, but the controller1 was not. When I unlocked the controller1, fm alarm shows the error. So it does mean the controller1 was not completely installed. If so, do you think there is a reason for the installation not being completed elsewhere? Thank you for help, BR, Jaewook. 2019년 3월 26일 (화) 오전 11:53, Hu, Yong 님이 작성: > Have you installed 2 controllers already? > > If by far you only setup 1 controller, this alarm seems reasonable > because it expects to communicate with another controller through mgt > network. > > > > Regards, > > Yong > > > > *From: *오재욱 > *Date: *Tuesday, 26 March 2019 at 10:45 AM > *To: *starlingx-discuss > *Subject: *[Starlingx-discuss] [starlingx-discuss] [critical error after > deployment] About "persistent critical 'Management Network'" > > > > Hello StarlingX Teams, > > > > I finally deployed duplex starlingx model on two physical servers. > > However, it was not truly deployed. The "all-in-one controller-1" has > deploy failed, > > The fault management alarm shows, > > 200.005 > > Failure: is experiencing a persistent critical 'Management > Network' communication failure." > > And I think above fault is the main reason of deploy failed > > > > I followed BIOS Setup for all nodes, > > and used Feb 22 iso images. > > > > I have no idea what can I do :( > > > > Any help would be very appreciated. > > > > Best Regards, > > Jaewook. > > ================================================ > *Jaewook Oh* (오재욱) > IISTRC - Internet Infra System Technology Research Center > 369 Sangdo-ro, Dongjak-gu, > 06978, Seoul, Republic of Korea > -- ================================================ *Jaewook Oh* (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Mar 26 03:29:31 2019 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 26 Mar 2019 03:29:31 +0000 Subject: [Starlingx-discuss] Fwd: [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" In-Reply-To: References: <06F50A69-BBA2-4A6E-986C-74C7B8452A44@intel.com> Message-ID: Hi Jaewook: Could you run ‘system host-list’ or ‘system host-show controller-1’ to see the status of controller-1? Is it available degrade or others ? Thanks. BR Austin Sun. From: 오재욱 [mailto:kyle.oh95 at gmail.com] Sent: Tuesday, March 26, 2019 10:59 AM To: starlingx-discuss Subject: [Starlingx-discuss] Fwd: [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" ---------- Forwarded message --------- 보낸사람: 오재욱 > Date: 2019년 3월 26일 (화) 오전 11:58 Subject: Re: [Starlingx-discuss] [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" To: Hu, Yong > Hi Yong, Umm I think the controller0 was completely installed, but the controller1 was not. When I unlocked the controller1, fm alarm shows the error. So it does mean the controller1 was not completely installed. If so, do you think there is a reason for the installation not being completed elsewhere? Thank you for help, BR, Jaewook. 2019년 3월 26일 (화) 오전 11:53, Hu, Yong >님이 작성: Have you installed 2 controllers already? If by far you only setup 1 controller, this alarm seems reasonable because it expects to communicate with another controller through mgt network. Regards, Yong From: 오재욱 > Date: Tuesday, 26 March 2019 at 10:45 AM To: starlingx-discuss > Subject: [Starlingx-discuss] [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" Hello StarlingX Teams, I finally deployed duplex starlingx model on two physical servers. However, it was not truly deployed. The "all-in-one controller-1" has deploy failed, The fault management alarm shows, 200.005 Failure: is experiencing a persistent critical 'Management Network' communication failure." And I think above fault is the main reason of deploy failed I followed BIOS Setup for all nodes, and used Feb 22 iso images. I have no idea what can I do :( Any help would be very appreciated. Best Regards, Jaewook. ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -- ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Tue Mar 26 03:48:19 2019 From: yong.hu at intel.com (Hu, Yong) Date: Tue, 26 Mar 2019 03:48:19 +0000 Subject: [Starlingx-discuss] Fwd: [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" In-Reply-To: References: <06F50A69-BBA2-4A6E-986C-74C7B8452A44@intel.com> Message-ID: Jaewook, I just now looked through your puppet log, and there was no error message at all. Though the alarm was about “management network” communication failure, the essence of problem might be just about controller-1 was not under a right state. Anyway, we guess maybe something wrong with ovs on your controller-1 and it led controller-1 unlock failure. You can have a check with these stuffs: 1. Check if any errors are in “/var/log/openvswitch/ovs-vswitchd.log” in controller-1 2. Run “sudo ovs-vsctl show” on controller-1 Regards, Yong From: "Sun, Austin" Date: Tuesday, 26 March 2019 at 11:31 AM To: 오재욱 , starlingx-discuss Subject: Re: [Starlingx-discuss] Fwd: [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" Hi Jaewook: Could you run ‘system host-list’ or ‘system host-show controller-1’ to see the status of controller-1? Is it available degrade or others ? Thanks. BR Austin Sun. From: 오재욱 [mailto:kyle.oh95 at gmail.com] Sent: Tuesday, March 26, 2019 10:59 AM To: starlingx-discuss Subject: [Starlingx-discuss] Fwd: [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" ---------- Forwarded message --------- 보낸사람: 오재욱 > Date: 2019년 3월 26일 (화) 오전 11:58 Subject: Re: [Starlingx-discuss] [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" To: Hu, Yong > Hi Yong, Umm I think the controller0 was completely installed, but the controller1 was not. When I unlocked the controller1, fm alarm shows the error. So it does mean the controller1 was not completely installed. If so, do you think there is a reason for the installation not being completed elsewhere? Thank you for help, BR, Jaewook. 2019년 3월 26일 (화) 오전 11:53, Hu, Yong >님이 작성: Have you installed 2 controllers already? If by far you only setup 1 controller, this alarm seems reasonable because it expects to communicate with another controller through mgt network. Regards, Yong From: 오재욱 > Date: Tuesday, 26 March 2019 at 10:45 AM To: starlingx-discuss > Subject: [Starlingx-discuss] [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" Hello StarlingX Teams, I finally deployed duplex starlingx model on two physical servers. However, it was not truly deployed. The "all-in-one controller-1" has deploy failed, The fault management alarm shows, 200.005 Failure: is experiencing a persistent critical 'Management Network' communication failure." And I think above fault is the main reason of deploy failed I followed BIOS Setup for all nodes, and used Feb 22 iso images. I have no idea what can I do :( Any help would be very appreciated. Best Regards, Jaewook. ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -- ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: From himanshugoyal500 at gmail.com Tue Mar 26 05:53:20 2019 From: himanshugoyal500 at gmail.com (Himanshu Goyal) Date: Tue, 26 Mar 2019 11:23:20 +0530 Subject: [Starlingx-discuss] cpu model Passthrough with Intel/Skylake-Server-IBRS In-Reply-To: References: Message-ID: + prashant, som Adding my team members in the same. Regards, Himanshu Goyal On Mon, Mar 25, 2019 at 1:33 PM Himanshu Goyal wrote: > Hi, > > I tried manual installation of rpm packages > "qemu-kvm-ev-3.0.0-0.tis.97.x86_64.rpm" but it is not working, Please help > how can i upgrade the required packages. > > Many thanks, > Himanshu Goyal > > > On Fri, Mar 22, 2019 at 3:57 PM Himanshu Goyal > wrote: > >> Hi, >> >> I'm using starlingX release "stx.2018.10", and "Intel/Skylake-Server-IBRS" >> as my compute server, trying to create a VM with cpu_model as passthrough >> but it is giving a error. >> >> Error: >> No valid host was found. There are not enough hosts available. compute-0: >> (ComputeFilter) host is disabled, reason: disabled by VIM*, compute-1: >> (VCpuModelFilter) Host VCPU model Skylake-Server-IBRS required Passthrough* >> >> >> I checked the starling-Discuss page & found it is fixed with qemu-kvm >> version:qemu-kvm-ev-3.0.0-0.tis.97 >> >> *starling-discuss link:* >> >> http://lists.starlingx.io/pipermail/starlingx-discuss/2018-December/002110.html >> >> Current qemu-kvm version in my setup: >> q*emu-img version 2.10.0(qemu-kvm-ev-2.10.0-0.tis.0)* >> >> Please let me know how can i upgrade qemu-kvm package in my compute >> without disturbing much running setup. >> >> Many Thanks, >> Himanshu Goyal >> >> >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Mar 26 06:37:23 2019 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 26 Mar 2019 06:37:23 +0000 Subject: [Starlingx-discuss] cpu model Passthrough with Intel/Skylake-Server-IBRS In-Reply-To: References: Message-ID: Hi : You have to patch (stx-nova) https://github.com/starlingx-staging/stx-nova/pull/17/files/2556ad28eb44a6916922ad2b489ac610db2ffeb5 and (stx-glance) https://github.com/starlingx-staging/stx-glance/pull/5/commits/35d76808893cf0869b54f758d958769a19c0c879 into your system and restart the necessary nova , glance services Thanks. BR Austin Sun. From: Himanshu Goyal [mailto:himanshugoyal500 at gmail.com] Sent: Tuesday, March 26, 2019 1:53 PM To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Hu, Yong ; Prashant.Patil at radisys.com; Somshekar.Ydlapur at radisys.com Subject: Re: [Starlingx-discuss] cpu model Passthrough with Intel/Skylake-Server-IBRS + prashant, som Adding my team members in the same. Regards, Himanshu Goyal On Mon, Mar 25, 2019 at 1:33 PM Himanshu Goyal > wrote: Hi, I tried manual installation of rpm packages "qemu-kvm-ev-3.0.0-0.tis.97.x86_64.rpm" but it is not working, Please help how can i upgrade the required packages. Many thanks, Himanshu Goyal On Fri, Mar 22, 2019 at 3:57 PM Himanshu Goyal > wrote: Hi, I'm using starlingX release "stx.2018.10", and "Intel/Skylake-Server-IBRS" as my compute server, trying to create a VM with cpu_model as passthrough but it is giving a error. Error: No valid host was found. There are not enough hosts available. compute-0: (ComputeFilter) host is disabled, reason: disabled by VIM, compute-1: (VCpuModelFilter) Host VCPU model Skylake-Server-IBRS required Passthrough I checked the starling-Discuss page & found it is fixed with qemu-kvm version:qemu-kvm-ev-3.0.0-0.tis.97 starling-discuss link: http://lists.starlingx.io/pipermail/starlingx-discuss/2018-December/002110.html Current qemu-kvm version in my setup: qemu-img version 2.10.0(qemu-kvm-ev-2.10.0-0.tis.0) Please let me know how can i upgrade qemu-kvm package in my compute without disturbing much running setup. Many Thanks, Himanshu Goyal -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Tue Mar 26 08:00:16 2019 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Tue, 26 Mar 2019 08:00:16 +0000 Subject: [Starlingx-discuss] cpu model Passthrough with Intel/Skylake-Server-IBRS In-Reply-To: References: , Message-ID: what about the also supported AMD EPYC CPUs by kvm? /usr/lib/python2.7/site-packages/nova/scheduler/filters/vcpu_model_filter.py def _is_host_kvm(self, cpu_info): info = jsonutils.loads(cpu_info) if 'vmx' in info['features']: return True if 'svm' in info['features']: //this add AMD support return True return False -------------- /usr/lib/python2.7/site-packages/nova/objects/fields.py # WRS: List of Intel based guest CPU models that can be selected from a user # defined instance type class CPUModel(BaseNovaEnum): # We use the ordering of the cpu models to determine whether a # given host can emulate a specified virtual model, so it's not # just an enum. ALL = ("Passthrough", "EPYC", // add AMD EPYC "EPYC-IBPB", // add AMD EPYC-IBPB "Conroe", "Penryn", ... Volker... ________________________________ Von: Sun, Austin [austin.sun at intel.com] Gesendet: Dienstag, 26. März 2019 07:37 An: Himanshu Goyal; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Hu, Yong; Prashant.Patil at radisys.com; Somshekar.Ydlapur at radisys.com Betreff: Re: [Starlingx-discuss] cpu model Passthrough with Intel/Skylake-Server-IBRS Hi : You have to patch (stx-nova) https://github.com/starlingx-staging/stx-nova/pull/17/files/2556ad28eb44a6916922ad2b489ac610db2ffeb5 and (stx-glance) https://github.com/starlingx-staging/stx-glance/pull/5/commits/35d76808893cf0869b54f758d958769a19c0c879 into your system and restart the necessary nova , glance services Thanks. BR Austin Sun. From: Himanshu Goyal [mailto:himanshugoyal500 at gmail.com] Sent: Tuesday, March 26, 2019 1:53 PM To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Hu, Yong ; Prashant.Patil at radisys.com; Somshekar.Ydlapur at radisys.com Subject: Re: [Starlingx-discuss] cpu model Passthrough with Intel/Skylake-Server-IBRS + prashant, som Adding my team members in the same. Regards, Himanshu Goyal On Mon, Mar 25, 2019 at 1:33 PM Himanshu Goyal > wrote: Hi, I tried manual installation of rpm packages "qemu-kvm-ev-3.0.0-0.tis.97.x86_64.rpm" but it is not working, Please help how can i upgrade the required packages. Many thanks, Himanshu Goyal On Fri, Mar 22, 2019 at 3:57 PM Himanshu Goyal > wrote: Hi, I'm using starlingX release "stx.2018.10", and "Intel/Skylake-Server-IBRS" as my compute server, trying to create a VM with cpu_model as passthrough but it is giving a error. Error: No valid host was found. There are not enough hosts available. compute-0: (ComputeFilter) host is disabled, reason: disabled by VIM, compute-1: (VCpuModelFilter) Host VCPU model Skylake-Server-IBRS required Passthrough I checked the starling-Discuss page & found it is fixed with qemu-kvm version:qemu-kvm-ev-3.0.0-0.tis.97 starling-discuss link: http://lists.starlingx.io/pipermail/starlingx-discuss/2018-December/002110.html Current qemu-kvm version in my setup: qemu-img version 2.10.0(qemu-kvm-ev-2.10.0-0.tis.0) Please let me know how can i upgrade qemu-kvm package in my compute without disturbing much running setup. Many Thanks, Himanshu Goyal -------------- next part -------------- An HTML attachment was scrubbed... URL: From himanshugoyal500 at gmail.com Tue Mar 26 13:00:11 2019 From: himanshugoyal500 at gmail.com (Himanshu Goyal) Date: Tue, 26 Mar 2019 18:30:11 +0530 Subject: [Starlingx-discuss] cpu model Passthrough with Intel/Skylake-Server-IBRS In-Reply-To: References: Message-ID: Thanks a lot Austin and Volker, After applied shared Patch cpu model as passthrough is working fine. Regards, Himanshu Goyal On Tue, Mar 26, 2019 at 1:30 PM von Hoesslin, Volker < Volker.Hoesslin at swsn.de> wrote: > what about the also supported AMD EPYC CPUs by kvm? > > > /usr/lib/python2.7/site-packages/nova/scheduler/filters/vcpu_model_filter.py > > def _is_host_kvm(self, cpu_info): > info = jsonutils.loads(cpu_info) > if 'vmx' in info['features']: > return True > if 'svm' in info['features']: //this add AMD support > return True > return False > > -------------- > > /usr/lib/python2.7/site-packages/nova/objects/fields.py > > # WRS: List of Intel based guest CPU models that can be selected from a > user > # defined instance type > class CPUModel(BaseNovaEnum): > # We use the ordering of the cpu models to determine whether a > # given host can emulate a specified virtual model, so it's not > # just an enum. > ALL = ("Passthrough", > "EPYC", // add AMD EPYC > "EPYC-IBPB", // add AMD EPYC-IBPB > "Conroe", > "Penryn", > ... > > > Volker... > > > > > ------------------------------ > *Von:* Sun, Austin [austin.sun at intel.com] > *Gesendet:* Dienstag, 26. März 2019 07:37 > *An:* Himanshu Goyal; starlingx-discuss at lists.starlingx.io; Alonso, Juan > Carlos; Hu, Yong; Prashant.Patil at radisys.com; > Somshekar.Ydlapur at radisys.com > *Betreff:* Re: [Starlingx-discuss] cpu model Passthrough with > Intel/Skylake-Server-IBRS > > Hi : > > You have to patch (stx-nova) > https://github.com/starlingx-staging/stx-nova/pull/17/files/2556ad28eb44a6916922ad2b489ac610db2ffeb5 > and (stx-glance) > https://github.com/starlingx-staging/stx-glance/pull/5/commits/35d76808893cf0869b54f758d958769a19c0c879 > > into your system and restart the necessary nova , glance services > > > > Thanks. > > BR > Austin Sun. > > > > > > *From:* Himanshu Goyal [mailto:himanshugoyal500 at gmail.com] > *Sent:* Tuesday, March 26, 2019 1:53 PM > *To:* starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos < > juan.carlos.alonso at intel.com>; Hu, Yong ; > Prashant.Patil at radisys.com; Somshekar.Ydlapur at radisys.com > *Subject:* Re: [Starlingx-discuss] cpu model Passthrough with > Intel/Skylake-Server-IBRS > > > > + prashant, som > > > > Adding my team members in the same. > > > > Regards, > > Himanshu Goyal > > > > On Mon, Mar 25, 2019 at 1:33 PM Himanshu Goyal > wrote: > > Hi, > > > > I tried manual installation of rpm packages > "qemu-kvm-ev-3.0.0-0.tis.97.x86_64.rpm" but it is not working, Please help > how can i upgrade the required packages. > > > > Many thanks, > > Himanshu Goyal > > > > > > On Fri, Mar 22, 2019 at 3:57 PM Himanshu Goyal > wrote: > > Hi, > > > > I'm using starlingX release "stx.2018.10", and "Intel/Skylake-Server-IBRS" > as my compute server, trying to create a VM with cpu_model as passthrough > but it is giving a error. > > > > Error: > > No valid host was found. There are not enough hosts available. compute-0: > (ComputeFilter) host is disabled, reason: disabled by VIM*, compute-1: > (VCpuModelFilter) Host VCPU model Skylake-Server-IBRS required Passthrough* > > > > > I checked the starling-Discuss page & found it is fixed with qemu-kvm > version:qemu-kvm-ev-3.0.0-0.tis.97 > > > > *starling-discuss link:* > > > http://lists.starlingx.io/pipermail/starlingx-discuss/2018-December/002110.html > > > > Current qemu-kvm version in my setup: > > q*emu-img version 2.10.0(qemu-kvm-ev-2.10.0-0.tis.0)* > > > > Please let me know how can i upgrade qemu-kvm package in my compute > without disturbing much running setup. > > > > Many Thanks, > > Himanshu Goyal > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Tue Mar 26 13:04:39 2019 From: serverascode at gmail.com (Curtis) Date: Tue, 26 Mar 2019 09:04:39 -0400 Subject: [Starlingx-discuss] Offline docker images install? In-Reply-To: References: <11547091552947706@myt3-964eae3a5b05.qloud-c.yandex.net> Message-ID: FYI, it turns out I was using "docker import" and should have been using "docker load". It appears docker import flattens the images and you lose some things like entrypoint, cmd, etc. Thanks for the help, Curtis On Fri, Mar 22, 2019 at 8:22 AM Curtis wrote: > > > On Thu, Mar 21, 2019 at 10:11 PM Qi, Mingyuan > wrote: > >> Erich & Cristopher, >> >> >> >> We’ll have to add a wiki page for setting up a private registry, would >> you please add the recipes for that? Including all the images need by >> starlingx. >> >> I planned to do that after I finish my current story, but in case more >> people are asking about the private registry these days, at least an image >> list is needed asap. >> >> >> > > This would be very helpful. I've based my private registry on a stx > install from the public regsitries. But it was a fairly convoluted process > to determine image names and tags, strip public repo names from the names, > and get them saved, imported, and pushed to the registry, but I've only > done this once and I'm assuming there must be an easier way to save and > upload images to a private registry. :) > > Thanks, > Curtis > > > >> Mingyuan >> >> >> >> *From:* Qi, Mingyuan [mailto:mingyuan.qi at intel.com] >> *Sent:* Friday, March 22, 2019 9:56 >> *To:* Curtis ; Miller, Frank < >> Frank.Miller at windriver.com> >> *Cc:* Erich Cordoba ; >> starlingx-discuss at lists.starlingx.io >> *Subject:* Re: [Starlingx-discuss] Offline docker images install? >> >> >> >> Curtis, >> >> >> >> I’ve updated a comment in LP, please check the images listed in your >> private registry. >> >> >> >> Mingyuan >> >> >> >> *From:* Curtis [mailto:serverascode at gmail.com ] >> *Sent:* Thursday, March 21, 2019 23:32 >> *To:* Miller, Frank >> *Cc:* Erich Cordoba ; >> starlingx-discuss at lists.starlingx.io >> *Subject:* Re: [Starlingx-discuss] Offline docker images install? >> >> >> >> On Thu, Mar 21, 2019 at 10:23 AM Miller, Frank < >> Frank.Miller at windriver.com> wrote: >> >> I’ve assigned the LP to Mingyuan as he was prime on implementing this >> feature. Mingyuan can you please provide some assistance to Curtis with >> his setup? Thanks. >> >> >> >> >> >> Thanks for looking at the bug and assigning someone. Will be great to get >> this figured out. :) >> >> >> >> Thanks, >> >> Curtis >> >> >> >> >> >> Frank >> >> >> >> *From:* Curtis [mailto:serverascode at gmail.com] >> *Sent:* Thursday, March 21, 2019 8:47 AM >> *To:* Erich Cordoba >> *Cc:* starlingx-discuss at lists.starlingx.io >> *Subject:* Re: [Starlingx-discuss] Offline docker images install? >> >> >> >> On Wed, Mar 20, 2019 at 4:31 PM Curtis wrote: >> >> >> >> >> >> On Mon, Mar 18, 2019 at 6:21 PM Erich Cordoba >> wrote: >> >> Cristopher has setup an internal/local docker registry with all needed >> images. I think he can (tomorrow, today is Mexican holiday) give more >> insights on this. >> >> >> >> >> >> If anyone has any hints on this, I'm running into a problem where kubeadm >> init seems to be failing during config_controller when using an alternative >> registry for all the public ones. Not finding meaningful error messages yet. >> >> >> >> >> >> FYI I entered a bug report: >> https://bugs.launchpad.net/starlingx/+bug/1821090 >> >> Thanks, >> >> Curtis >> >> >> >> >> >> Thanks, >> >> Curtis >> >> >> >> >> >> -Erich >> >> -- >> Sent from Yandex.Mail for mobile >> >> 18.03.2019, 16:17, "Curtis" : >> >> Hi All, >> >> >> >> I apologise if this has been covered somewhere, did a bit of >> searching...what if I want to install all the docker images for stx from an >> offline file. Was there some mention of these being included in the ISO >> (thought maybe I'd heard that), or can I import them prior to installation >> of openstack? >> >> >> >> Mostly I am coming from the perspective of the upcoming stx workshop at >> the openinfra summit. Would like to avoid students having to all download >> at the same time, or all hitting a local proxy, if possible. >> >> >> >> Sorry if I missed it. >> >> >> >> Thanks, >> >> Curtis >> >> >> >> PS. Thanks for the docs at >> https://wiki.openstack.org/wiki/StarlingX/Containers/Installation ran >> through it today, all good. :) >> >> >> -- >> >> Blog: serverascode.com >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> >> >> -- >> >> Blog: serverascode.com >> >> >> >> -- >> >> Blog: serverascode.com >> >> >> >> -- >> >> Blog: serverascode.com >> > > > -- > Blog: serverascode.com > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Tue Mar 26 13:23:06 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 26 Mar 2019 13:23:06 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack Distro meeting, 3/27 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35EDA17D@SHSMSX104.ccr.corp.intel.com> Agenda for 3/27 meeting: - Ceph upgrade update (Ovidiu/Daniel, Tingjie/Yong) - DevStack update (Dean/Yi) - Opens (all) -----Original Appointment----- From: Xie, Cindy Sent: Monday, November 5, 2018 2:27 PM To: Xie, Cindy; Waheed, Numan; Hu, Yong; starlingx-discuss at lists.starlingx.io; Liu, ZhipengS; Shang, Dehao; Wold, Saul; Lin, Shuicheng; Zhu, Vivian; Somerville, Jim; Sun, Austin; 'Khalil, Ghada'; Jones, Bruce E; Troyer, Dean; 'Rowsell, Brent' Cc: 'Poncea, Ovidiu'; Gomez, Juan P; Lara, Cesar; Fang, Liang A; Cobbley, David A; 'Chen, Jacky'; Perez Rodriguez, Humberto I; Martinez Monroy, Elio; 'Seiler, Glenn'; Arce Moreno, Abraham; 'Waines, Greg'; 'Eslimi, Dariush'; 'Hellmann, Gil'; Shuquan Huang; 'Young, Ken'; Perez Carranza, Jose; Hu, Wei W; Martinez Landa, Hayde; Armstrong, Robert H Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, March 27, 2019 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 Bill.Zvonar at windriver.com Tue Mar 26 13:27:49 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 26 Mar 2019 13:27:49 +0000 Subject: [Starlingx-discuss] Community Call (March 27, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC0A209A0@ALA-MBD.corp.ad.wrs.com> Reminder of tomorrow's Community call - please feel free to add to the agenda at [0]. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1500_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190327T1400 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eric.MacDonald at windriver.com Tue Mar 26 13:44:16 2019 From: Eric.MacDonald at windriver.com (MacDonald, Eric) Date: Tue, 26 Mar 2019 13:44:16 +0000 Subject: [Starlingx-discuss] Fwd: [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" In-Reply-To: References: <06F50A69-BBA2-4A6E-986C-74C7B8452A44@intel.com> Message-ID: <210898B96CA058408C55992CCAD98676B9FBD1FA@ALA-MBD.corp.ad.wrs.com> That alarm is indication that Maintenance is failing Heartbeat over the Management network. Please check your network and maybe specifically its support for multicast messaging. If you lock controller-1 can you ping it from the active controller. If you need further assistance please provide the active controller’s mtcAgent.log and hbsAgent.log files You can always run ‘collect’ or ‘collect all’ on the active controller to get a summary of the system state and use those logs for off system debug of your issue. Eric MacDonald. From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Monday, March 25, 2019 11:48 PM To: Sun, Austin; 오재욱; starlingx-discuss Subject: Re: [Starlingx-discuss] Fwd: [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" Jaewook, I just now looked through your puppet log, and there was no error message at all. Though the alarm was about “management network” communication failure, the essence of problem might be just about controller-1 was not under a right state. Anyway, we guess maybe something wrong with ovs on your controller-1 and it led controller-1 unlock failure. You can have a check with these stuffs: 1. Check if any errors are in “/var/log/openvswitch/ovs-vswitchd.log” in controller-1 2. Run “sudo ovs-vsctl show” on controller-1 Regards, Yong From: "Sun, Austin" Date: Tuesday, 26 March 2019 at 11:31 AM To: 오재욱 , starlingx-discuss Subject: Re: [Starlingx-discuss] Fwd: [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" Hi Jaewook: Could you run ‘system host-list’ or ‘system host-show controller-1’ to see the status of controller-1? Is it available degrade or others ? Thanks. BR Austin Sun. From: 오재욱 [mailto:kyle.oh95 at gmail.com] Sent: Tuesday, March 26, 2019 10:59 AM To: starlingx-discuss Subject: [Starlingx-discuss] Fwd: [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" ---------- Forwarded message --------- 보낸사람: 오재욱 > Date: 2019년 3월 26일 (화) 오전 11:58 Subject: Re: [Starlingx-discuss] [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" To: Hu, Yong > Hi Yong, Umm I think the controller0 was completely installed, but the controller1 was not. When I unlocked the controller1, fm alarm shows the error. So it does mean the controller1 was not completely installed. If so, do you think there is a reason for the installation not being completed elsewhere? Thank you for help, BR, Jaewook. 2019년 3월 26일 (화) 오전 11:53, Hu, Yong >님이 작성: Have you installed 2 controllers already? If by far you only setup 1 controller, this alarm seems reasonable because it expects to communicate with another controller through mgt network. Regards, Yong From: 오재욱 > Date: Tuesday, 26 March 2019 at 10:45 AM To: starlingx-discuss > Subject: [Starlingx-discuss] [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" Hello StarlingX Teams, I finally deployed duplex starlingx model on two physical servers. However, it was not truly deployed. The "all-in-one controller-1" has deploy failed, The fault management alarm shows, 200.005 Failure: is experiencing a persistent critical 'Management Network' communication failure." And I think above fault is the main reason of deploy failed I followed BIOS Setup for all nodes, and used Feb 22 iso images. I have no idea what can I do :( Any help would be very appreciated. Best Regards, Jaewook. ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -- ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Tue Mar 26 14:30:04 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 26 Mar 2019 14:30:04 +0000 Subject: [Starlingx-discuss] Distro.openstack meeting notes Mar 26 2019 Message-ID: <9A85D2917C58154C960D95352B22818BD070808E@fmsmsx123.amr.corp.intel.com> Meeting notes and agenda for the 3/26 meeting * Update on Dean & Bruce's discussion with Eric F (new Nova PTL) * We briefed Eric on StarlingX, asked him for help, and got the answer "Please attend the PTG and advocate for your items. Understand the Nova team has lots of work". Dean will reach out to the OpenStack mailing list explaining our upstream first policy and our short term need for a small set of backport patches. * Review tracking spreadsheet - new tabs for "Backport items" and "Stx stories" * Email update from Shuquan - AR Bruce to update the spreadsheet. AR Shuquan to meet with Gerry Kopec in Ottawa CA, and will update the dates / tasks based on that conversation. * Review Stories in the backlog - update stale ones, add any remaining to the Spreadsheet * Brent to clean up https://storyboard.openstack.org/#!/story/2003108 and others. * Horizon configurable page refresh - Who did the original work? Please have them attend the next call * Review https://bugs.launchpad.net/starlingx/+bug/1820882 and assign it to someone who can post it upstream to Nova * Assigned to Boxiang, thank you! * Ready to pull the f/stein branch? * Nova branched last week. We don't have anything to put into the branch today. Will take a bit of work from Dean to clean up some things before he creates the branch. Hold off for now. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Peters at windriver.com Tue Mar 26 15:10:07 2019 From: Matt.Peters at windriver.com (Peters, Matt) Date: Tue, 26 Mar 2019 15:10:07 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA4D1AA8@ALA-MBD.corp.ad.wrs.com> Message-ID: <72A55890-B007-4E93-A74A-291C725B158E@windriver.com> Hello Chenjie, Can you clarify this statement? “NUMA sections missing bug still exits”. Did you mean to say that the missing NUMA sections in the domain XML are now present, but you still can’t ping over the vhost port, or are you saying the NUMA sections are still missing? Do you have multiple systems that are experiencing this issue, or is it isolated to a single system that you are having problems with the NUMA topology? I believe you mentioned that you saw the same connectivity issues on a standard load from the mirror, so that still points to a test system / environment issue. As Ghada mentioned, I think the next steps are to get results from the sanity systems with the same load baseline and to test with your custom load on a system that has been proven to work on the standard load. -Matt From: Ghada Khalil Date: Tuesday, March 26, 2019 at 9:28 AM To: "Xu, Chenjie" , "Peters, Matt" , "Martinez Monroy, Elio" , "Lin, Shuicheng" , "Cabrales, Ada" , "Perez, Ricardo O" Cc: "'starlingx-discuss at lists.starlingx.io'" , "Zhao, Forrest" Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Has Elio or Rich from the test team tried the new load as well on their systems? Do they see the same issues you reported? I think we need some data for another system to compare. Ada, As part of this thread, I also requested that a VM connectivity test be added to regular sanity so that there is data from the daily cengn builds w/o the new version of ovs-dpdk. Has the sanity suite been updated? Thanks, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 26, 2019 7:09 AM To: Peters, Matt; Martinez Monroy, Elio; Khalil, Ghada; Lin, Shuicheng; Cabrales, Ada; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I installed StarlingX using the new 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals. NUMA sections missing bug still exits: https://bugs.launchpad.net/starlingx/+bug/1820378 This time I update the docker images to latest before installing StarlingX. And the docker images versions and build baseline have been attached. Could you please help review the docker image versions? Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Friday, March 22, 2019 8:31 PM To: Xu, Chenjie >; Martinez Monroy, Elio >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Comparing the image list to our labs shows a difference in the image IDs (sha), but I’m not sure if that is just a difference in build baselines or an actual difference in the images. Since some of them align, I think you might be running a different set of images. Can you confirm what the build baseline is that you pulled the images from? I have attached a sample list from our labs for comparison. -Matt From: "Xu, Chenjie" > Date: Friday, March 22, 2019 at 7:25 AM To: "Peters, Matt" >, "Martinez Monroy, Elio" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, The docker image versions in my environment and helm-charts-manifest-no-tests.tgz has been attached. The helm-charts-manifest-no-tests.tgz is built by Shuicheng for the OVSDPDK Upgrade Testing ISO image. Best Regards, Xu, Chenjie From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Thursday, March 21, 2019 11:20 PM To: Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Perfect, I will be cheking my mail for that new ISO. Adding Richo , he is the one that is going to execute the tests. Thanks BR Elio From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, March 21, 2019 9:15 AM To: Lin, Shuicheng >; Cabrales, Ada >; Martinez Monroy, Elio > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, We discussed this in the networking bi-weekly team meeting today. Please re-enable the mlx pmd – re-apply the following patch: https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch Then please rebase to the latest master and build a new load for Ada’s team to start testing Hi Elio, One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 Thanks, Ghada From: Khalil, Ghada Sent: Thursday, March 21, 2019 9:12 AM To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. Can you confirm that the load being used has the mellanox pmd enabled in it? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 21, 2019 9:03 AM To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie for the testing. Hi all, Does it mean greenlight for code merge, or any other test is needed? Here is the patch list: https://review.openstack.org/642672 https://review.openstack.org/642673 Best Regards Shuicheng From: Xu, Chenjie Sent: Thursday, March 21, 2019 5:46 PM To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcel at schaible-consulting.de Tue Mar 26 15:32:17 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Tue, 26 Mar 2019 16:32:17 +0100 (CET) Subject: [Starlingx-discuss] /etc/nova/openrc missing Message-ID: <725995971.1373484.1553614337425@communicator.strato.com> Hi, after installing the image from 20190320 I am not seeing the /etc/nova/openrc script. Is there a way to regenerate it? Thanks Marcel From Al.Bailey at windriver.com Tue Mar 26 15:34:52 2019 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Tue, 26 Mar 2019 15:34:52 +0000 Subject: [Starlingx-discuss] /etc/nova/openrc missing In-Reply-To: <725995971.1373484.1553614337425@communicator.strato.com> References: <725995971.1373484.1553614337425@communicator.strato.com> Message-ID: Use /etc/platform/openrc Nova is no longer installed on the bare metal controller (its in a container) Al -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Tuesday, March 26, 2019 11:32 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] /etc/nova/openrc missing Hi, after installing the image from 20190320 I am not seeing the /etc/nova/openrc script. Is there a way to regenerate it? Thanks Marcel _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From marcel at schaible-consulting.de Tue Mar 26 15:38:09 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Tue, 26 Mar 2019 16:38:09 +0100 (CET) Subject: [Starlingx-discuss] /etc/nova/openrc missing In-Reply-To: References: <725995971.1373484.1553614337425@communicator.strato.com> Message-ID: <779006153.1373893.1553614690031@communicator.strato.com> Thanks! Works. > "Bailey, Henry Albert (Al)" hat am 26. März 2019 um 16:34 geschrieben: > > > Use /etc/platform/openrc > > Nova is no longer installed on the bare metal controller (its in a container) > > Al > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Tuesday, March 26, 2019 11:32 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] /etc/nova/openrc missing > > Hi, > > after installing the image from 20190320 I am not seeing the /etc/nova/openrc script. > > Is there a way to regenerate it? > > Thanks > > Marcel > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From juan.carlos.alonso at intel.com Tue Mar 26 15:39:41 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Tue, 26 Mar 2019 15:39:41 +0000 Subject: [Starlingx-discuss] Will be a new ISO for today? Message-ID: <8557B550001AFB46A43A0CCC314BF85153CAE9E3@FMSMSX108.amr.corp.intel.com> Hi, The latest ISO is from yesterday, at 22:11hrs. A new ISO is being generated for today? http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcel at schaible-consulting.de Tue Mar 26 16:40:39 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Tue, 26 Mar 2019 17:40:39 +0100 (CET) Subject: [Starlingx-discuss] Duplex: Configuring provider networks at installation does not work Message-ID: <1944270328.1377976.1553618439610@communicator.strato.com> Hi, I am trying to Setup an Duplex configuration with the Image from 20190320 and the following documentation: https://docs.starlingx.io/installation_guide/latest/duplex.html#provisioning-the-controller-0-host. Setting up the providernet fails with: [root at localhost network-scripts(keystone_admin)]# neutron providernet-create providernet-a --type=vlan neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. Unknown command [u'providernet-create', u'providernet-a', u'--type=vlan'] Any idea how to setup the providernet correctly? Thanks Marcel [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-create providernet-a --type=vlan [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-range-create --name providernet-a-range1 --range 100-400 providernet-a From jose.perez.carranza at intel.com Tue Mar 26 16:47:18 2019 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Tue, 26 Mar 2019 16:47:18 +0000 Subject: [Starlingx-discuss] Duplex: Configuring provider networks at installation does not work In-Reply-To: <1944270328.1377976.1553618439610@communicator.strato.com> References: <1944270328.1377976.1553618439610@communicator.strato.com> Message-ID: <0A5D9A624DF90343892F8F3FE7DE525A2A959409@fmsmsx101.amr.corp.intel.com> Hi You are pointing to the documentation of installation steps for "pre-containers" ISO, In your case you are using a recent ISO with containerized services hence you should use the Installation steps listed here [1] 1. https://wiki.openstack.org/wiki/StarlingX/Containers Regards, José > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Tuesday, March 26, 2019 10:41 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Duplex: Configuring provider networks at > installation does not work > > Hi, > > I am trying to Setup an Duplex configuration with the Image from 20190320 > and the following documentation: > > https://docs.starlingx.io/installation_guide/latest/duplex.html#provisioning- > the-controller-0-host. > > Setting up the providernet fails with: > > [root at localhost network-scripts(keystone_admin)]# neutron providernet- > create providernet-a --type=vlan neutron CLI is deprecated and will be > removed in the future. Use openstack CLI instead. > Unknown command [u'providernet-create', u'providernet-a', u'--type=vlan'] > > > Any idea how to setup the providernet correctly? > > Thanks > > Marcel > > > > > [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-create > providernet-a --type=vlan > [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-range-create > --name providernet-a-range1 --range 100-400 providernet-a > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From juan.carlos.alonso at intel.com Tue Mar 26 16:47:47 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Tue, 26 Mar 2019 16:47:47 +0000 Subject: [Starlingx-discuss] Duplex: Configuring provider networks at installation does not work In-Reply-To: <1944270328.1377976.1553618439610@communicator.strato.com> References: <1944270328.1377976.1553618439610@communicator.strato.com> Message-ID: <8557B550001AFB46A43A0CCC314BF85153CAEA54@FMSMSX108.amr.corp.intel.com> Hi, I think you are using an out to date installation guide. This is the current steps we use: https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnAIODX https://wiki.openstack.org/wiki/StarlingX/Containers Regards. Juan Carlos Alonso -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Tuesday, March 26, 2019 10:41 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Duplex: Configuring provider networks at installation does not work Hi, I am trying to Setup an Duplex configuration with the Image from 20190320 and the following documentation: https://docs.starlingx.io/installation_guide/latest/duplex.html#provisioning-the-controller-0-host. Setting up the providernet fails with: [root at localhost network-scripts(keystone_admin)]# neutron providernet-create providernet-a --type=vlan neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. Unknown command [u'providernet-create', u'providernet-a', u'--type=vlan'] Any idea how to setup the providernet correctly? Thanks Marcel [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-create providernet-a --type=vlan [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-range-create --name providernet-a-range1 --range 100-400 providernet-a _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From marcel at schaible-consulting.de Tue Mar 26 17:14:04 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Tue, 26 Mar 2019 18:14:04 +0100 (CET) Subject: [Starlingx-discuss] Duplex: Configuring provider networks at installation does not work In-Reply-To: <8557B550001AFB46A43A0CCC314BF85153CAEA54@FMSMSX108.amr.corp.intel.com> References: <1944270328.1377976.1553618439610@communicator.strato.com> <8557B550001AFB46A43A0CCC314BF85153CAEA54@FMSMSX108.amr.corp.intel.com> Message-ID: <1735146338.1379770.1553620444861@communicator.strato.com> Thanks for the hint. Looks better now except for the unlock. > "Alonso, Juan Carlos" hat am 26. März 2019 um 17:47 geschrieben: > > > Hi, > > I think you are using an out to date installation guide. > This is the current steps we use: https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnAIODX > > https://wiki.openstack.org/wiki/StarlingX/Containers > > Regards. > Juan Carlos Alonso > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Tuesday, March 26, 2019 10:41 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Duplex: Configuring provider networks at installation does not work > > Hi, > > I am trying to Setup an Duplex configuration with the Image from 20190320 and the following documentation: > > https://docs.starlingx.io/installation_guide/latest/duplex.html#provisioning-the-controller-0-host. > > Setting up the providernet fails with: > > [root at localhost network-scripts(keystone_admin)]# neutron providernet-create providernet-a --type=vlan neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. > Unknown command [u'providernet-create', u'providernet-a', u'--type=vlan'] > > > Any idea how to setup the providernet correctly? > > Thanks > > Marcel > > > > > [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-create providernet-a --type=vlan > [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-range-create --name providernet-a-range1 --range 100-400 providernet-a > > _______________________________________________ > 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 Tue Mar 26 17:14:51 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 26 Mar 2019 17:14:51 +0000 Subject: [Starlingx-discuss] Skydive? Message-ID: <9A85D2917C58154C960D95352B22818BD0708212@fmsmsx123.amr.corp.intel.com> Does anyone have any experience with the Skydive project? http://skydive.network/. Is it something that would be interesting or helpful for StarlingX users? brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcel at schaible-consulting.de Tue Mar 26 17:18:25 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Tue, 26 Mar 2019 18:18:25 +0100 (CET) Subject: [Starlingx-discuss] Duplex: Unlock fails with "Can not unlock node until at least one OSD is configured" Message-ID: <1046703319.1379926.1553620705662@communicator.strato.com> Hi, following the instructions from https://wiki.openstack.org/wiki/StarlingX/Containers/Installation#Prepare_the_host_for_running_the_containerized_services and with the image from 20190320 I'll get the following error when I try to unlock controller-0: [root at localhost network-scripts(keystone_admin)]# system host-unlock controller- Can not unlock node until at least one OSD is configured. The osd tree Looks like this: [root at localhost network-scripts(keystone_admin)]# ceph osd tree ID WEIGHT TYPE NAME UP/DOWN REWEIGHT PRIMARY-AFFINITY -1 0 root storage-tier -2 0 chassis group-0 -4 0 host controller-0 -3 0 host controller-1 I'll guess the controller-1 is configured after unlocking controller-0. Any idea what is missing? Thanks Marcel From Al.Bailey at windriver.com Tue Mar 26 17:34:20 2019 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Tue, 26 Mar 2019 17:34:20 +0000 Subject: [Starlingx-discuss] Duplex: Unlock fails with "Can not unlock node until at least one OSD is configured" In-Reply-To: <1046703319.1379926.1553620705662@communicator.strato.com> References: <1046703319.1379926.1553620705662@communicator.strato.com> Message-ID: Are you following the steps for AIO-DX? https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnAIODX Although, many of the AIO-DX steps refer back to that AIO-SX page you hyperlinked. The "Configure Ceph for Controller-0" is probably the step that you are missing. Al -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Tuesday, March 26, 2019 1:18 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Duplex: Unlock fails with "Can not unlock node until at least one OSD is configured" Hi, following the instructions from https://wiki.openstack.org/wiki/StarlingX/Containers/Installation#Prepare_the_host_for_running_the_containerized_services and with the image from 20190320 I'll get the following error when I try to unlock controller-0: [root at localhost network-scripts(keystone_admin)]# system host-unlock controller- Can not unlock node until at least one OSD is configured. The osd tree Looks like this: [root at localhost network-scripts(keystone_admin)]# ceph osd tree ID WEIGHT TYPE NAME UP/DOWN REWEIGHT PRIMARY-AFFINITY -1 0 root storage-tier -2 0 chassis group-0 -4 0 host controller-0 -3 0 host controller-1 I'll guess the controller-1 is configured after unlocking controller-0. Any idea what is missing? Thanks Marcel _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From serverascode at gmail.com Tue Mar 26 18:06:35 2019 From: serverascode at gmail.com (Curtis) Date: Tue, 26 Mar 2019 14:06:35 -0400 Subject: [Starlingx-discuss] Publish container image list? Message-ID: Hi All, If we are not already (which maybe we are, this is a big project) I think it would be useful to publish a list of containers that match up with a particular release. Otherwise I have to build it on my own anyways (for example for building out a repeatable workshop setup). I know we publish an ISO, RPMs, and Helm charts, but it's be nice to have a list of image and tags to use to be able to populate local docker registries. Or a way to generate that list from existing artifacts...if it doesn't exist already that is. Also, right now my list has many of the stx images as "dev-centos-master-latest" and I'd like to firm that up with versions if possible. Thanks, Curtis -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Mar 26 18:09:52 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 26 Mar 2019 18:09:52 +0000 Subject: [Starlingx-discuss] Publish container image list? In-Reply-To: References: Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA46BAB1@ALA-MBD.corp.ad.wrs.com> Hi Curtis, That work is in progress now. We’ve updated the image build tool to record versions, which will be an input to building the application charts. Additionally, an upcoming work item will be to publish these records as part of the CENGN build. Cheers, Don. From: Curtis [mailto:serverascode at gmail.com] Sent: Tuesday, March 26, 2019 2:07 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Publish container image list? Hi All, If we are not already (which maybe we are, this is a big project) I think it would be useful to publish a list of containers that match up with a particular release. Otherwise I have to build it on my own anyways (for example for building out a repeatable workshop setup). I know we publish an ISO, RPMs, and Helm charts, but it's be nice to have a list of image and tags to use to be able to populate local docker registries. Or a way to generate that list from existing artifacts...if it doesn't exist already that is. Also, right now my list has many of the stx images as "dev-centos-master-latest" and I'd like to firm that up with versions if possible. Thanks, Curtis -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Tue Mar 26 18:13:29 2019 From: serverascode at gmail.com (Curtis) Date: Tue, 26 Mar 2019 14:13:29 -0400 Subject: [Starlingx-discuss] Publish container image list? In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA46BAB1@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA46BAB1@ALA-MBD.corp.ad.wrs.com> Message-ID: On Tue, Mar 26, 2019 at 2:10 PM Penney, Don wrote: > Hi Curtis, > > > > That work is in progress now. We’ve updated the image build tool to record > versions, which will be an input to building the application charts. > Additionally, an upcoming work item will be to publish these records as > part of the CENGN build. > > > Ah, Ok that is great to hear. I'll keep a lookout for that. Thanks Don! Thanks, Curtis > Cheers, > > Don. > > > > *From:* Curtis [mailto:serverascode at gmail.com] > *Sent:* Tuesday, March 26, 2019 2:07 PM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] Publish container image list? > > > > Hi All, > > > > If we are not already (which maybe we are, this is a big project) I think > it would be useful to publish a list of containers that match up with a > particular release. Otherwise I have to build it on my own anyways (for > example for building out a repeatable workshop setup). > > > > I know we publish an ISO, RPMs, and Helm charts, but it's be nice to have > a list of image and tags to use to be able to populate local docker > registries. Or a way to generate that list from existing artifacts...if it > doesn't exist already that is. > > > > Also, right now my list has many of the stx images as > "dev-centos-master-latest" and I'd like to firm that up with versions if > possible. > > > > Thanks, > > Curtis > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From ada.cabrales at intel.com Mon Mar 25 22:50:13 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Mon, 25 Mar 2019 22:50:13 +0000 Subject: [Starlingx-discuss] Canceled: Weekly StarlingX Test meeting - 9:00 PDT Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CDAF1C4@FMSMSX114.amr.corp.intel.com> Hello, I'm cancelling this week meeting due to a conflict and revisiting of the meeting dates for the May release. Any question, please contact me by email. Thanks Ada Changing the frequency to weekly. 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: 4801 bytes Desc: not available URL: From kyle.oh95 at gmail.com Tue Mar 26 05:12:37 2019 From: kyle.oh95 at gmail.com (=?UTF-8?B?7Jik7J6s7Jqx?=) Date: Tue, 26 Mar 2019 14:12:37 +0900 Subject: [Starlingx-discuss] Fwd: [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" In-Reply-To: References: <06F50A69-BBA2-4A6E-986C-74C7B8452A44@intel.com> Message-ID: Thanks Yong, 1. checked my ovs-vswitchd.log, and I think br-int has some problem. I found something weird in the log, "2019-03-25T06:11:01.884Z|00192|rconn|WARN| br-int<->tcp:127.0.0.1:6633: connection failed (Connection refused)" Is this the main reason of the problem? 2. And below is my ovs-vsctl show result: controller-1:~$ sudo ovs-vsctl show 10fb65fb-9bac-4ef2-9221-8c27f53afcd3 Manager "ptcp:6639:127.0.0.1" is_connected: true Bridge "br-phy0" Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure Port "br-phy0" Interface "br-phy0" type: internal Port "phy-br-phy0" Interface "phy-br-phy0" type: patch options: {peer="int-br-phy0"} Port "lldp6b8235ce-e2" Interface "lldp6b8235ce-e2" type: internal Port "eth0" Interface "eth0" type: dpdk options: {dpdk-devargs="0000:81:00.0", n_rxq="2"} Bridge br-int Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure Port br-int Interface br-int type: internal Port "int-br-phy0" Interface "int-br-phy0" type: patch options: {peer="phy-br-phy0"} ovs_version: "2.9.0" BR, Jaewook. 2019년 3월 26일 (화) 오후 12:48, Hu, Yong 님이 작성: > Jaewook, > > I just now looked through your puppet log, and there was no error message > at all. > > Though the alarm was about “management network” communication failure, the > essence of problem might be just about controller-1 was not under a right > state. > > > > Anyway, we guess maybe something wrong with ovs on your controller-1 and > it led controller-1 unlock failure. > > You can have a check with these stuffs: > > 1. Check if any errors are in “/var/log/openvswitch/ovs-vswitchd.log” > in controller-1 > 2. Run “sudo ovs-vsctl show” on controller-1 > > > > > > Regards, > > Yong > > *From: *"Sun, Austin" > *Date: *Tuesday, 26 March 2019 at 11:31 AM > *To: *오재욱 , starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > *Subject: *Re: [Starlingx-discuss] Fwd: [starlingx-discuss] [critical > error after deployment] About "persistent critical 'Management Network'" > > > > Hi Jaewook: > > Could you run ‘system host-list’ or ‘system host-show controller-1’ to see > the status of controller-1? Is it available degrade or others ? > > > > Thanks. > > BR > Austin Sun. > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ovs-vswitchd.log Type: application/octet-stream Size: 197609 bytes Desc: not available URL: From chenjie.xu at intel.com Tue Mar 26 11:08:45 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Tue, 26 Mar 2019 11:08:45 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> <7027C5CE-7CC6-44FF-9649-2287F2B233D1@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F35ECF687@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530564B4@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CF4CB@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9F898@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CFA11@ALA-MBD.corp.ad.wrs.com> <1466AF2176E6F040BD63860D0A241BBD46CA30D1@FMSMSX109.amr.corp.intel.com> Message-ID: Hi Matt, I installed StarlingX using the new 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals. NUMA sections missing bug still exits: https://bugs.launchpad.net/starlingx/+bug/1820378 This time I update the docker images to latest before installing StarlingX. And the docker images versions and build baseline have been attached. Could you please help review the docker image versions? Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Friday, March 22, 2019 8:31 PM To: Xu, Chenjie ; Martinez Monroy, Elio ; Khalil, Ghada ; Lin, Shuicheng ; Cabrales, Ada ; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io' ; Zhao, Forrest Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Comparing the image list to our labs shows a difference in the image IDs (sha), but I’m not sure if that is just a difference in build baselines or an actual difference in the images. Since some of them align, I think you might be running a different set of images. Can you confirm what the build baseline is that you pulled the images from? I have attached a sample list from our labs for comparison. -Matt From: "Xu, Chenjie" > Date: Friday, March 22, 2019 at 7:25 AM To: "Peters, Matt" >, "Martinez Monroy, Elio" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, The docker image versions in my environment and helm-charts-manifest-no-tests.tgz has been attached. The helm-charts-manifest-no-tests.tgz is built by Shuicheng for the OVSDPDK Upgrade Testing ISO image. Best Regards, Xu, Chenjie From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Thursday, March 21, 2019 11:20 PM To: Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Perfect, I will be cheking my mail for that new ISO. Adding Richo , he is the one that is going to execute the tests. Thanks BR Elio From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, March 21, 2019 9:15 AM To: Lin, Shuicheng >; Cabrales, Ada >; Martinez Monroy, Elio > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, We discussed this in the networking bi-weekly team meeting today. Please re-enable the mlx pmd – re-apply the following patch: https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch Then please rebase to the latest master and build a new load for Ada’s team to start testing Hi Elio, One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 Thanks, Ghada From: Khalil, Ghada Sent: Thursday, March 21, 2019 9:12 AM To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. Can you confirm that the load being used has the mellanox pmd enabled in it? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 21, 2019 9:03 AM To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie for the testing. Hi all, Does it mean greenlight for code merge, or any other test is needed? Here is the patch list: https://review.openstack.org/642672 https://review.openstack.org/642673 Best Regards Shuicheng From: Xu, Chenjie Sent: Thursday, March 21, 2019 5:46 PM To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: 0322-compute-0.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: 0322-controller-0.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: build-info.txt URL: From Ghada.Khalil at windriver.com Tue Mar 26 13:28:06 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 26 Mar 2019 13:28:06 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> <7027C5CE-7CC6-44FF-9649-2287F2B233D1@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F35ECF687@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530564B4@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CF4CB@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9F898@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CFA11@ALA-MBD.corp.ad.wrs.com> <1466AF2176E6F040BD63860D0A241BBD46CA30D1@FMSMSX109.amr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4D1AA8@ALA-MBD.corp.ad.wrs.com> Has Elio or Rich from the test team tried the new load as well on their systems? Do they see the same issues you reported? I think we need some data for another system to compare. Ada, As part of this thread, I also requested that a VM connectivity test be added to regular sanity so that there is data from the daily cengn builds w/o the new version of ovs-dpdk. Has the sanity suite been updated? Thanks, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 26, 2019 7:09 AM To: Peters, Matt; Martinez Monroy, Elio; Khalil, Ghada; Lin, Shuicheng; Cabrales, Ada; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I installed StarlingX using the new 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals. NUMA sections missing bug still exits: https://bugs.launchpad.net/starlingx/+bug/1820378 This time I update the docker images to latest before installing StarlingX. And the docker images versions and build baseline have been attached. Could you please help review the docker image versions? Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Friday, March 22, 2019 8:31 PM To: Xu, Chenjie >; Martinez Monroy, Elio >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Comparing the image list to our labs shows a difference in the image IDs (sha), but I’m not sure if that is just a difference in build baselines or an actual difference in the images. Since some of them align, I think you might be running a different set of images. Can you confirm what the build baseline is that you pulled the images from? I have attached a sample list from our labs for comparison. -Matt From: "Xu, Chenjie" > Date: Friday, March 22, 2019 at 7:25 AM To: "Peters, Matt" >, "Martinez Monroy, Elio" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, The docker image versions in my environment and helm-charts-manifest-no-tests.tgz has been attached. The helm-charts-manifest-no-tests.tgz is built by Shuicheng for the OVSDPDK Upgrade Testing ISO image. Best Regards, Xu, Chenjie From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Thursday, March 21, 2019 11:20 PM To: Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Perfect, I will be cheking my mail for that new ISO. Adding Richo , he is the one that is going to execute the tests. Thanks BR Elio From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, March 21, 2019 9:15 AM To: Lin, Shuicheng >; Cabrales, Ada >; Martinez Monroy, Elio > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, We discussed this in the networking bi-weekly team meeting today. Please re-enable the mlx pmd – re-apply the following patch: https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch Then please rebase to the latest master and build a new load for Ada’s team to start testing Hi Elio, One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 Thanks, Ghada From: Khalil, Ghada Sent: Thursday, March 21, 2019 9:12 AM To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. Can you confirm that the load being used has the mellanox pmd enabled in it? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 21, 2019 9:03 AM To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie for the testing. Hi all, Does it mean greenlight for code merge, or any other test is needed? Here is the patch list: https://review.openstack.org/642672 https://review.openstack.org/642673 Best Regards Shuicheng From: Xu, Chenjie Sent: Thursday, March 21, 2019 5:46 PM To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From mario.alfredo.c.arevalo at intel.com Tue Mar 26 19:38:13 2019 From: mario.alfredo.c.arevalo at intel.com (Arevalo, Mario Alfredo C) Date: Tue, 26 Mar 2019 19:38:13 +0000 Subject: [Starlingx-discuss] Fault Management Containerization (SB 2004008) Follow Up In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F35ED90C1@SHSMSX104.ccr.corp.intel.com> References: <6594B51DBE477C48AAE23675314E6C466459EDD6@fmsmsx107.amr.corp.intel.com>, <2FD5DDB5A04D264C80D42CA35194914F35ED90C1@SHSMSX104.ccr.corp.intel.com> Message-ID: <6594B51DBE477C48AAE23675314E6C466459F616@fmsmsx107.amr.corp.intel.com> Hi Cindy, The first version of the patches will take around 2 weeks, after that, a validation step will start. In this step I am going to update the patches according to the feedback received from the community and Luis Botello will help to validate the functionality of the patches. As final step, I would like to execute the sanity when all patches are reviewed by the community an they are ready to be merged. This final step could vary around 2-3 weeks, it will depend on the response time from the community and the complexity of the required updates, in addition to the validation tasks. Best regards. Mario. ________________________________________ From: Xie, Cindy Sent: Monday, March 25, 2019 5:44 PM To: Arevalo, Mario Alfredo C; Arce Moreno, Abraham; starlingx-discuss at lists.starlingx.io Cc: Tao Liu; Frank.Miller at windriver.com Subject: RE: [Starlingx-discuss] Fault Management Containerization (SB 2004008) Follow Up Mario, Nice to know that you're getting all information and having better understanding for the tasks. We probably needs to get a little bit more detail granularity of your plan, for each task in the storyboard: - when the patches will be uploaded for review; - what tests you're planning to do? Any support required from Ada's team? and when... - when you expect the patch review comments can be addressed and patch merged to master. Thanks. - cindy -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Tuesday, March 26, 2019 8:38 AM To: Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Cc: Tao Liu ; Frank.Miller at windriver.com Subject: Re: [Starlingx-discuss] Fault Management Containerization (SB 2004008) Follow Up Hi team, Thank you for your feedback from our last meeting, and this is my update. I am checking all points described in this thread. Actually I have got progress in the topic related to snmp and the relation with oamcontroller, sysinv and cgts-client. I plan to send a PR with information about findings/architecture to the stx-fault/doc in a future. I think, it is not necessary another meeting as it was mentioned, I think I have enough information to continue and I am going to update the current reviews and send news according to the points discussed until today, and contact Tao for specific questions. Thanks Tao, Abraham and Frank. Best regards. Mario. ________________________________________ From: Arce Moreno, Abraham Sent: Friday, March 22, 2019 10:37 AM To: starlingx-discuss at lists.starlingx.io Cc: Arevalo, Mario Alfredo C; Tao Liu Subject: Fault Management Containerization (SB 2004008) Follow Up Thanks Frank for setting this up. Thanks everyone for your attendance to this meeting, here you have high level notes and ToDos based in the topics covered. In Summary - The presentation Stx-Fault/Containers is located at [0]. - Tao will kindly update the Fault Management architecture diagram, slide 8. - Mario will send an email no later than Monday afternoon with the latest findings / questions based in his 5 ToDos. - We will meet again on Tuesday to finalize on tasks and implementation details. If we are forgetting about any key point in this email, please do not hesitate to reply. StarlingX Architecture - 2 instances for each of the following projects: - Keystone - Horizon - Barbican - Fault Management will have 2 instances as well. Fault Management Architecture - [ToDo] [Tao] to modify the Fault Management architecture (Slide 8) Thanks Tao! - fm-api runs in compute node, snmp provide interfaces - [ToDo] [Mario] to check these statements Fault Management REST API - [ToDo] [Mario] to write the next level of details for REST API mapping / implementation, consider to include PUT to Event Log. Fault Management Architecture - python-fmclient is a wrapper to fm_cli / fm_api - [ToDo] [Mario] to understand more about fm_cli as a wrapper and how does it interact and affects fault management containerized strategy. FM Proposal - Remove mysql, fm-api, fm-common - [ToDo] [Mario] to understand about the removal of fm-api and fm-common from the containerized instance. - Dependency to cgts-client - [ToDo] [Mario] to understand what is cgtc-client and how does it interacts with fault management and the new containerized instance. OpenStack Applications The following 2 projects will make use of the Fault Management containerized: - starlingx-dashboard - stx-nfv [0] https://docs.google.com/presentation/d/1_vG83aHTToXlIdJxaJpVL-MHWfRGnxLuyEdFDt-nfwo/edit?usp=sharing _______________________________________________ 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 Tue Mar 26 20:04:02 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Tue, 26 Mar 2019 15:04:02 -0500 Subject: [Starlingx-discuss] stx-nova changes Message-ID: In preparation for using the starlingx-staging/stx-nova repository for hosting our stable branch in the near future I am renaming the existing master branch (previously used for the build pre-container) to stx/old-master. Why? The stable backport branch (stx/stein) will track upstream stable/stein closely and I think having both upstream master and stable/stein in the repo will simplify ongoing maintenance. Summary: * master is renamed to stx/old-master (formerly used for builds) * upstream master synced to master * upstream stable/stein synced to stable/stein * new stx/stein created from stable/stein when required master and stable/stein will be populated soon, stx/stein will be created when we have something to backport to it. dt -- Dean Troyer dtroyer at gmail.com From ada.cabrales at intel.com Tue Mar 26 19:56:44 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Tue, 26 Mar 2019 19:56:44 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA4D1AA8@ALA-MBD.corp.ad.wrs.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE444BA@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4C8F68@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9A029@SHSMSX101.ccr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744D8649@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F35EC47E1@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CA889@ALA-MBD.corp.ad.wrs.com> <97D2D32F-5267-4BEA-AEB8-B7A6D2828049@windriver.com> <7027C5CE-7CC6-44FF-9649-2287F2B233D1@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F35ECF687@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530564B4@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CF4CB@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE9F898@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4CFA11@ALA-MBD.corp.ad.wrs.com> <1466AF2176E6F040BD63860D0A241BBD46CA30D1@FMSMSX109.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4D1AA8@ALA-MBD.corp.ad.wrs.com> Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CDAF922@FMSMSX114.amr.corp.intel.com> Elio confirmed last week that he was able to deploy and configure the ISO, but let me check if he created VMs. Ricardo (Richo) is setting the bare metal config today. VM connectivity on sanity: we started to run the test manually last week. We will continue running it in this way in the meantime the automatic test is done. Ada From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Tuesday, March 26, 2019 7:28 AM To: Xu, Chenjie ; Peters, Matt ; Martinez Monroy, Elio ; Lin, Shuicheng ; Cabrales, Ada ; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io' ; Zhao, Forrest Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Has Elio or Rich from the test team tried the new load as well on their systems? Do they see the same issues you reported? I think we need some data for another system to compare. Ada, As part of this thread, I also requested that a VM connectivity test be added to regular sanity so that there is data from the daily cengn builds w/o the new version of ovs-dpdk. Has the sanity suite been updated? Thanks, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 26, 2019 7:09 AM To: Peters, Matt; Martinez Monroy, Elio; Khalil, Ghada; Lin, Shuicheng; Cabrales, Ada; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I installed StarlingX using the new 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals. NUMA sections missing bug still exits: https://bugs.launchpad.net/starlingx/+bug/1820378 This time I update the docker images to latest before installing StarlingX. And the docker images versions and build baseline have been attached. Could you please help review the docker image versions? Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Friday, March 22, 2019 8:31 PM To: Xu, Chenjie >; Martinez Monroy, Elio >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Comparing the image list to our labs shows a difference in the image IDs (sha), but I’m not sure if that is just a difference in build baselines or an actual difference in the images. Since some of them align, I think you might be running a different set of images. Can you confirm what the build baseline is that you pulled the images from? I have attached a sample list from our labs for comparison. -Matt From: "Xu, Chenjie" > Date: Friday, March 22, 2019 at 7:25 AM To: "Peters, Matt" >, "Martinez Monroy, Elio" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, The docker image versions in my environment and helm-charts-manifest-no-tests.tgz has been attached. The helm-charts-manifest-no-tests.tgz is built by Shuicheng for the OVSDPDK Upgrade Testing ISO image. Best Regards, Xu, Chenjie From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Thursday, March 21, 2019 11:20 PM To: Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Perfect, I will be cheking my mail for that new ISO. Adding Richo , he is the one that is going to execute the tests. Thanks BR Elio From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, March 21, 2019 9:15 AM To: Lin, Shuicheng >; Cabrales, Ada >; Martinez Monroy, Elio > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, We discussed this in the networking bi-weekly team meeting today. Please re-enable the mlx pmd – re-apply the following patch: https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch Then please rebase to the latest master and build a new load for Ada’s team to start testing Hi Elio, One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 Thanks, Ghada From: Khalil, Ghada Sent: Thursday, March 21, 2019 9:12 AM To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. Can you confirm that the load being used has the mellanox pmd enabled in it? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 21, 2019 9:03 AM To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie for the testing. Hi all, Does it mean greenlight for code merge, or any other test is needed? Here is the patch list: https://review.openstack.org/642672 https://review.openstack.org/642673 Best Regards Shuicheng From: Xu, Chenjie Sent: Thursday, March 21, 2019 5:46 PM To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From cesar.lara at intel.com Tue Mar 26 22:15:37 2019 From: cesar.lara at intel.com (Lara, Cesar) Date: Tue, 26 Mar 2019 22:15:37 +0000 Subject: [Starlingx-discuss] [build][meetings] Build team meeting minutes /21/2019 Message-ID: <0B566C62EC792145B40E29EFEBF1AB4710FDBAAB@fmsmsx123.amr.corp.intel.com> Build team meeting Agenda for 03/21/2019 - Update on build bugs and stories - Multi Layer build proposal - Mirror tool - Opens Notes Update on build bugs and stories - just wanted to do a check on the stories and bugs assigned to the build team and make sure those are being worked on Current stories https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.build&project_group_id=86 Need to check with Bruce/Saul if this one is still valid https://storyboard.openstack.org/#!/story/2003288 Current bugs https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.build AR - Build team, please update your bugs o stories Multi-Layer build proposal So far we are on sync with most of the ideas of a multi-layer build on the PoC for Ubuntu that is happening as part of Multi-OS efforts (https://github.com/starlingx-staging/stx-packaging ) but we still need to get agreement on the requirements for enablement, we need to start building a discussion matrix to map these requirements and level set the team as far as to what are the problems that we are trying to solve. Scott also contributed his proposal in which we use the current tools to assign packages to layers, defined by the developer and build only those packages, taking from some of the build avoidance ideas. AR- Cesar to start an Etherpad to facilitate brainstorming around this https://etherpad.openstack.org/p/stx-build-requirements - done Mirror tool Erich presented a demo on this tool, currently at 90% development, and still need to integrate the logic behind build avoidance and the Cengn hosted mirror, spec is also on track to be finished and presented to TSC for approval. Opens CVE check integration to Intel build Automation, currently enabled for manual triggered scans on build automation, still working to have fully automated integration and then find a way to integrate this as part of Cengn automation. Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Wed Mar 27 03:12:35 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Wed, 27 Mar 2019 03:12:35 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190325 Message-ID: <8557B550001AFB46A43A0CCC314BF85153CAEBFF@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Mar-25 (link) Status: YELLOW =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup Manual [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [FAIL] Sanity Platform 07 TCs [FAIL] TOTAL: [ 57 TCs FAIL ] AIO - Duplex Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 05 TCs [PASS] TOTAL: [ 58 TCs PASS ] Standard - Local Storage (2+2) Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 05 TCs [PASS] TOTAL: [ 58 TCs PASS ] Standard - Dedicated Storage (2+2+2) Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 16 TCs [PASS] | 36 TCs [FAIL] Sanity Platform 05 TCs [PASS] TOTAL: [ 22 TCs PASS | 36 TCs FAIL ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [FAIL] Sanity Platform 07 TCs [FAIL] TOTAL: [ 04 TCs PASS | 57 TCs FAIL ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 05 TCs [PASS] TOTAL: [ 62 TCs PASS ] Standard - Local Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 05 TCs [PASS] TOTAL: [ 62 TCs PASS ] Standard - Dedicated Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 05 TCs [PASS] TOTAL: [ 62 TCs PASS ] ------------------------------------------------------------------ Simplex - application-apply fails at 95% - ceilometer pod Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1820928 Could not create VMs on Standard Dedicated Storage, in bare metal environment Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1821841 ------------------------------------------------------------------ This is the list of test cases executed: https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Wed Mar 27 04:03:36 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Wed, 27 Mar 2019 04:03:36 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190325 In-Reply-To: <6345119E91D5C843A93D64F498ACFA13744DE6C0@SHSMSX101.ccr.corp.intel.com> References: <8557B550001AFB46A43A0CCC314BF85153CAEBFF@FMSMSX108.amr.corp.intel.com> <6345119E91D5C843A93D64F498ACFA13744DE6C0@SHSMSX101.ccr.corp.intel.com> Message-ID: <8557B550001AFB46A43A0CCC314BF85153CAEC42@FMSMSX108.amr.corp.intel.com> Hi Forrest, >From next Sanity Test report (tomorrow) will has the tests to ping between VMs. At the end of the report you can find a link to the detailed list of test cases. Regards. Juan Carlos Alonso From: Zhao, Forrest Sent: Tuesday, March 26, 2019 9:22 PM To: Alonso, Juan Carlos Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Sanity Test - ISO 20190325 Hi Carlos, Has VM connectivity test been added to regular sanity test, as is requested in attached email? Besides the number of PASS/FAIL test cases, how can we know/check which test cases are actually PASS/FAIL? Thanks, Forrest From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Wednesday, March 27, 2019 11:13 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190325 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Mar-25 (link) Status: YELLOW =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup Manual [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [FAIL] Sanity Platform 07 TCs [FAIL] TOTAL: [ 57 TCs FAIL ] AIO - Duplex Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 05 TCs [PASS] TOTAL: [ 58 TCs PASS ] Standard - Local Storage (2+2) Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 05 TCs [PASS] TOTAL: [ 58 TCs PASS ] Standard - Dedicated Storage (2+2+2) Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 16 TCs [PASS] | 36 TCs [FAIL] Sanity Platform 05 TCs [PASS] TOTAL: [ 22 TCs PASS | 36 TCs FAIL ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [FAIL] Sanity Platform 07 TCs [FAIL] TOTAL: [ 04 TCs PASS | 57 TCs FAIL ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 05 TCs [PASS] TOTAL: [ 62 TCs PASS ] Standard - Local Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 05 TCs [PASS] TOTAL: [ 62 TCs PASS ] Standard - Dedicated Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 05 TCs [PASS] TOTAL: [ 62 TCs PASS ] ------------------------------------------------------------------ Simplex - application-apply fails at 95% - ceilometer pod Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1820928 Could not create VMs on Standard Dedicated Storage, in bare metal environment Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1821841 ------------------------------------------------------------------ This is the list of test cases executed: https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eric.MacDonald at windriver.com Wed Mar 27 12:38:12 2019 From: Eric.MacDonald at windriver.com (MacDonald, Eric) Date: Wed, 27 Mar 2019 12:38:12 +0000 Subject: [Starlingx-discuss] Fwd: [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" In-Reply-To: References: <06F50A69-BBA2-4A6E-986C-74C7B8452A44@intel.com> <210898B96CA058408C55992CCAD98676B9FBD1FA@ALA-MBD.corp.ad.wrs.com> Message-ID: <210898B96CA058408C55992CCAD98676B9FBDDC7@ALA-MBD.corp.ad.wrs.com> There appears to be something wrong with your multi-cast setup as the hbsAgent is not able to setup its pulse messaging socket for the management interface. hbsAgent.log – This log seems to have rotated due to successive socket resetup retries. 2019-03-27T10:33:55.984 [4194.3824110] controller-0 hbsAgent --- msgClass.cpp (1033) msgClassTx : Info : Creating controller-0 socket on port 2106 with address: 239.1.1.2 2019-03-27T10:33:55.984 [4194.3824111] controller-0 hbsAgent --- msgClass.cpp (1098) initSocket :Error : Failed to bind socket to address (22:Invalid argument) 2019-03-27T10:33:55.984 [4194.3824112] controller-0 hbsAgent hbs hbsAgent.cpp ( 575) _setup_pulse_messaging :Error : Cannot open multicast transmit socket - rc:34 (22:Invalid argument) mtcAgent.log shows that your management interface is bouncing which is causing command failures. 2019-03-22T16:57:19.449 [94960.00107] controller-0 mtcAgent hbs nodeClass.cpp (4288) service_netlink_events : Warn : Management link eno2 is down 2019-03-22T16:57:19.449 [94960.00108] controller-0 mtcAgent hbs nodeClass.cpp (4301) service_netlink_events : Warn : eno2 is down (oper:down) 2019-03-22T16:57:19.881 [94960.00109] controller-0 mtcAgent hbs nodeClass.cpp (4324) service_netlink_events : Warn : Management link eno2 is up 2019-03-22T16:57:20.261 [94960.00110] controller-0 mtcAgent hbs nodeClass.cpp (4288) service_netlink_events : Warn : Management link eno2 is down I suggest you stabilize your management network between the 2 controllers. You can always look for Error or Warn logs in mtcAgent.log as indication of unexpected conditions. The logs are kept quite short and try to indicate the issue at hand. In this case eno2 is bouncing. Eric. From: 오재욱 [mailto:kyle.oh95 at gmail.com] Sent: Tuesday, March 26, 2019 10:03 PM To: MacDonald, Eric Cc: Hu, Yong; Sun, Austin; starlingx-discuss Subject: Re: [Starlingx-discuss] Fwd: [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" Importance: High Hello Eric, thanks for advice. I commented my answer to your advices, 0. Please check your network and maybe specifically its support for multicast messaging. -> Could you tell me how can I check that my network supports multicast messaging? Do I need function like 'omping'? 1. If you lock controller-1 can you ping it from the active controller. -> Yes, I can ping to controller-1 from the active one, with controller-1's management ip (192.168.204.4), and controller-1's oam ip (10.10.10.4). 2. If you need further assistance please provide the active controller’s mtcAgent.log and hbsAgent.log files -> I attached those files :) 3. You can always run ‘collect’ or ‘collect all’ on the active controller to get a summary of the system state and use those logs for off system debug of your issue. -> Thanks, I totally didn't know about those commands! 2019년 3월 26일 (화) 오후 10:45, MacDonald, Eric >님이 작성: That alarm is indication that Maintenance is failing Heartbeat over the Management network. Please check your network and maybe specifically its support for multicast messaging. If you lock controller-1 can you ping it from the active controller. If you need further assistance please provide the active controller’s mtcAgent.log and hbsAgent.log files You can always run ‘collect’ or ‘collect all’ on the active controller to get a summary of the system state and use those logs for off system debug of your issue. Eric MacDonald. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kyle.oh95 at gmail.com Wed Mar 27 12:42:51 2019 From: kyle.oh95 at gmail.com (=?UTF-8?B?7Jik7J6s7Jqx?=) Date: Wed, 27 Mar 2019 21:42:51 +0900 Subject: [Starlingx-discuss] Fwd: [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" In-Reply-To: <210898B96CA058408C55992CCAD98676B9FBDDC7@ALA-MBD.corp.ad.wrs.com> References: <06F50A69-BBA2-4A6E-986C-74C7B8452A44@intel.com> <210898B96CA058408C55992CCAD98676B9FBD1FA@ALA-MBD.corp.ad.wrs.com> <210898B96CA058408C55992CCAD98676B9FBDDC7@ALA-MBD.corp.ad.wrs.com> Message-ID: Thank you very much Eric, I also saw those lines, and I agree with that point. Unfortunately, I'm not sure what to do to stabilize my management network. Is that mean check physical NIC? Or, is there any command that makes network stable? Thank you again, BR, Jaewook. 2019년 3월 27일 (수) 오후 9:38, MacDonald, Eric 님이 작성: > There appears to be something wrong with your multi-cast setup as the > hbsAgent is not able to setup its pulse messaging socket for the management > interface. > > > > hbsAgent.log – This log seems to have rotated due to successive socket > resetup retries. > > 2019-03-27T10:33:55.984 [4194.3824110] controller-0 hbsAgent --- > msgClass.cpp (1033) msgClassTx : Info : Creating > controller-0 socket on port 2106 with address: 239.1.1.2 > > 2019-03-27T10:33:55.984 [4194.3824111] controller-0 hbsAgent --- > msgClass.cpp (1098) initSocket :Error : Failed to bind > socket to address (22:Invalid argument) > > 2019-03-27T10:33:55.984 [4194.3824112] controller-0 hbsAgent hbs > hbsAgent.cpp ( 575) _setup_pulse_messaging :Error : Cannot open > multicast transmit socket - rc:34 (22:Invalid argument) > > > > mtcAgent.log shows that your management interface is bouncing which is > causing command failures. > > 2019-03-22T16:57:19.449 [94960.00107] controller-0 mtcAgent hbs > nodeClass.cpp (4288) service_netlink_events : Warn : Management link > eno2 is down > > 2019-03-22T16:57:19.449 [94960.00108] controller-0 mtcAgent hbs > nodeClass.cpp (4301) service_netlink_events : Warn : eno2 is down > (oper:down) > > 2019-03-22T16:57:19.881 [94960.00109] controller-0 mtcAgent hbs > nodeClass.cpp (4324) service_netlink_events : Warn : Management link > eno2 is up > > 2019-03-22T16:57:20.261 [94960.00110] controller-0 mtcAgent hbs > nodeClass.cpp (4288) service_netlink_events : Warn : Management link > eno2 is down > > > > *I suggest you stabilize your management network between the 2 > controllers.* > > > > You can always look for Error or Warn logs in mtcAgent.log as indication > of unexpected conditions. > > The logs are kept quite short and try to indicate the issue at hand. In > this case eno2 is bouncing. > > > > Eric. > > > > *From:* 오재욱 [mailto:kyle.oh95 at gmail.com] > *Sent:* Tuesday, March 26, 2019 10:03 PM > *To:* MacDonald, Eric > *Cc:* Hu, Yong; Sun, Austin; starlingx-discuss > *Subject:* Re: [Starlingx-discuss] Fwd: [starlingx-discuss] [critical > error after deployment] About "persistent critical 'Management Network'" > *Importance:* High > > > > Hello Eric, > > thanks for advice. > > > > I commented my answer to your advices, > > > > 0. Please check your network and maybe specifically its support for > multicast messaging. > > -> Could you tell me how can I check that my network supports multicast > messaging? Do I need function like 'omping'? > > > > 1. If you lock controller-1 can you ping it from the active controller. > > -> Yes, I can ping to controller-1 from the active one, with > controller-1's management ip (192.168.204.4), and controller-1's oam ip > (10.10.10.4). > > > > 2. If you need further assistance please provide the active controller’s > mtcAgent.log and hbsAgent.log files > > -> I attached those files :) > > > > 3. You can always run ‘collect’ or ‘collect all’ on the active controller > to get a summary of the system state and use those logs for off system > debug of your issue. > > -> Thanks, I totally didn't know about those commands! > > > > 2019년 3월 26일 (화) 오후 10:45, MacDonald, Eric > 님이 작성: > > That alarm is indication that Maintenance is failing Heartbeat over the > Management network. > > > > Please check your network and maybe specifically its support for multicast > messaging. > > > > If you lock controller-1 can you ping it from the active controller. > > > > If you need further assistance please provide the active controller’s > mtcAgent.log and hbsAgent.log files > > > > You can always run ‘collect’ or ‘collect all’ on the active controller to > get a summary of the system state and use those logs for off system debug > of your issue. > > > > Eric MacDonald. > > -- ================================================ *Jaewook Oh* (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Wed Mar 27 13:54:29 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 27 Mar 2019 13:54:29 +0000 Subject: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack Distro meeting, 3/27 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35EDC25F@SHSMSX104.ccr.corp.intel.com> Agenda & Notes for 3/27 meeting: - Ceph upgrade update (Ovidiu/Daniel, Tingjie/Yong) 1. Feature developed (2+2+2 work as expected) - 3/8 (Done as of 3/13) common code base: https://github.com/oponcea?tab=repositories 1.1 mon_max_pg_per_osd needs to be increased - done w/ PR submitted (updated max pg per osd to 2048) 1.2 prevent rados-gw being started by system- issue solved (PR?) 2. Rebase to master w/ container & CentOS7.6 - 3/15 (Done as of 3/20) both Intel & WR built & deploy successfully on AIO-SX/DX and multi-nodes (2+2+2). ISO provided to Ada/Ricardo - AR: Yong to provide the test ISO to Ricardo for engineering testing dry-run. Node re-install the storage/computer node is one of the test cases we should done, AR: Yong follow-up w/ Daniel to make sure re-install controller/compute/storage nodes. mimic release notes review - AR: Daniel/Tingjie work together to review the release notes from mimic and understand the changes. 3. Code ready for review - 3/20 (actual?) Squashing the commits - Daniel WIP Daniel is working on debugging the mimic support in Openstack helm to provide support multiple-tiers of functional support. AR: Frank to treate a seperate task under container SB to track the debug tasks. Patch submitted against master - ETA (Daniel - 4/1 to upload; Changcheng - abandon all the patches on old-feature-branch & master) Rebase starlingx-staging/stx-ceph/tree/stx/v13.2.2 (Changcheng/Dean) - ETA (Changcheng - 4/1) 2 options: option#1 - Dean to remove patches on stx-ceph on starlingx-staging, then cherry-pick your patches to the staging; Clean git history. option#2 - Changcheng refactor all patches to latest code on starling-staging. agreed to do Option#1: Dean to delete the stx/v13.2.2 branch and create a new fresh one from upstream, then Changcheng will do PR on top of new branch. Goal is to generate dev build from master with the pending reviews and rebased stx-Ceph (4/2) 4. System testing - 3/20 ~ 4/5 (actual?) Test case in discussion: https://docs.google.com/spreadsheets/d/1O2zWn-R83Wj1SqmeUtxCP59_DsSM0UNZW0gRALnDn6w/edit#gid=0 The official test cycle with master build next Tuesday (4/2) 5. Patch merge (Ovidiu/Daniel) - 4/5 (actual?) - trending at least 2 wks delay. 4/19 - DevStack update (Dean/Yi) 1. stx-metal: one final review pending (https://review.openstack.org/#/c/641597/) 2. stx-fault: one review pending (https://review.openstack.org/#/c/639501/) Martin will submit another patch against fault. 3. stx-ha: WIP (Shuicheng to provide update) Shuicheng: enabled the ha services running, still checking the status correctness. More debug/testing required before the patch can be upload. ETA: patch upload by next week (4/5) 4. Story#2005285 added to finalize Devstack job structure: Rename/relocate the base StarlingX DevStack job to stx-integ (the least-worst existing home) and make all jobs voting and run on more than just devstack/* files. restructure devstack job definition, moved the base task from stx-fault to stx-integ. change to ha and fault still open. Once the review merged, Devstack will be configured as Zuul voting. Question from Frank: how difficult it is for devs to understand the debug message from Zuul job failure? Devs will debug the issue but if any questions sending to the mailing list for help. - Opens (all) None -----Original Appointment----- From: Xie, Cindy Sent: Monday, November 5, 2018 2:27 PM To: Xie, Cindy; Waheed, Numan; Hu, Yong; starlingx-discuss at lists.starlingx.io; Liu, ZhipengS; Shang, Dehao; Wold, Saul; Lin, Shuicheng; Zhu, Vivian; Somerville, Jim; Sun, Austin; 'Khalil, Ghada'; Jones, Bruce E; Troyer, Dean; 'Rowsell, Brent' Cc: 'Poncea, Ovidiu'; Gomez, Juan P; Lara, Cesar; Fang, Liang A; Cobbley, David A; 'Chen, Jacky'; Perez Rodriguez, Humberto I; Martinez Monroy, Elio; 'Seiler, Glenn'; Arce Moreno, Abraham; 'Waines, Greg'; 'Eslimi, Dariush'; 'Hellmann, Gil'; Shuquan Huang; 'Young, Ken'; Perez Carranza, Jose; Hu, Wei W; Martinez Landa, Hayde; Armstrong, Robert H Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, March 27, 2019 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 marcel at schaible-consulting.de Wed Mar 27 14:51:00 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Wed, 27 Mar 2019 15:51:00 +0100 (CET) Subject: [Starlingx-discuss] DUPLEX: PXE Image does not include the ixgbevf Message-ID: <1592707842.1434226.1553698260345@communicator.strato.com> Hi, I just installed the image from 2019-03-25 and trying to install and configure the controller-1. It seems like that the PXEimage does not include the Intel driver ixgbevf. Is this intended and what is the recommended procedure to get this module into the pxe image? Thanks Marcel From chris.friesen at windriver.com Wed Mar 27 16:12:00 2019 From: chris.friesen at windriver.com (Chris Friesen) Date: Wed, 27 Mar 2019 10:12:00 -0600 Subject: [Starlingx-discuss] stx-nova changes In-Reply-To: References: Message-ID: <6cc338ab-538f-582d-b7c0-5a9081584430@windriver.com> On 3/26/2019 2:04 PM, Dean Troyer wrote: > In preparation for using the starlingx-staging/stx-nova repository for > hosting our stable branch in the near future I am renaming the > existing master branch (previously used for the build pre-container) > to stx/old-master. Why? The stable backport branch (stx/stein) will > track upstream stable/stein closely and I think having both upstream > master and stable/stein in the repo will simplify ongoing maintenance. Just to clarify, would builds be done from stx/stein once created? (And stable/stein if stx/stein doesn't exist?) Chris From Volker.Hoesslin at swsn.de Wed Mar 27 16:16:16 2019 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Wed, 27 Mar 2019 16:16:16 +0000 Subject: [Starlingx-discuss] Unrecognized attribute(s) 'port_security_enabled' Message-ID: Hi! i'm already running on the first stable version of starlingX, so far so good ;) but after time, i got some missing features and problems. i know, in 1-2 month in the future the new "helm" openstack/starlingX version will be released but it is to far away for waiting for me :( i have two essentials problems: 1. some big problems if an instance has multiple interfaces - if i set for any instance interface an floating ip to diffrent external networks, in my case, only one of the floating ip will work. also port-forwarding does not work as alternative path to the instance... 2. i can not create networks with "port-security-enabled", maybe this is in conduction with the first problem? $ openstack network create --enable-port-security --enable test Error while executing command: Unrecognized attribute(s) 'port_security_enabled' (HTTP 400) (Request-ID: req-6296e358-677f-4e03-89cd-86906649ecd4) is there any flags while starlingX installation that will prevent "port-security" ? missing network-driver, or any missing bios magic? greez & thx, volker... -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Wed Mar 27 16:38:37 2019 From: scott.little at windriver.com (Scott Little) Date: Wed, 27 Mar 2019 12:38:37 -0400 Subject: [Starlingx-discuss] Will be a new ISO for today? In-Reply-To: <8557B550001AFB46A43A0CCC314BF85153CAE9E3@FMSMSX108.amr.corp.intel.com> References: <8557B550001AFB46A43A0CCC314BF85153CAE9E3@FMSMSX108.amr.corp.intel.com> Message-ID: <9cff3606-e019-6c00-a76f-a806da10bd42@windriver.com> CENGN automatic builds start at different times depending on if a docker image build is going to be included in the build.  The goal was that the completion time is roughly the same, so that automated test could be scheduled at the same time each day.  Thus the time delta in between builds will be 22,24,or 26 hours.  When build times are converted to UTC, this seems to be walking us back and forth across the midnight dividing line between days.  Some days will appear to have two builds (March 25), while the next might have none (March 26). Is this too confusing? Must we change it back? Scott On 2019-03-26 11:39 a.m., Alonso, Juan Carlos wrote: > > The latest ISO is from yesterday, at 22:11hrs. A new ISO is being > generated for today? > > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kyle.oh95 at gmail.com Wed Mar 27 02:03:27 2019 From: kyle.oh95 at gmail.com (=?UTF-8?B?7Jik7J6s7Jqx?=) Date: Wed, 27 Mar 2019 11:03:27 +0900 Subject: [Starlingx-discuss] Fwd: [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" In-Reply-To: <210898B96CA058408C55992CCAD98676B9FBD1FA@ALA-MBD.corp.ad.wrs.com> References: <06F50A69-BBA2-4A6E-986C-74C7B8452A44@intel.com> <210898B96CA058408C55992CCAD98676B9FBD1FA@ALA-MBD.corp.ad.wrs.com> Message-ID: Hello Eric, thanks for advice. I commented my answer to your advices, 0. Please check your network and maybe specifically its support for multicast messaging. -> Could you tell me how can I check that my network supports multicast messaging? Do I need function like 'omping'? 1. If you lock controller-1 can you ping it from the active controller. -> Yes, I can ping to controller-1 from the active one, with controller-1's management ip (192.168.204.4), and controller-1's oam ip (10.10.10.4). 2. If you need further assistance please provide the active controller’s mtcAgent.log and hbsAgent.log files -> I attached those files :) 3. You can always run ‘collect’ or ‘collect all’ on the active controller to get a summary of the system state and use those logs for off system debug of your issue. -> Thanks, I totally didn't know about those commands! 2019년 3월 26일 (화) 오후 10:45, MacDonald, Eric 님이 작성: > That alarm is indication that Maintenance is failing Heartbeat over the > Management network. > > > > Please check your network and maybe specifically its support for multicast > messaging. > > > > If you lock controller-1 can you ping it from the active controller. > > > > If you need further assistance please provide the active controller’s > mtcAgent.log and hbsAgent.log files > > > > You can always run ‘collect’ or ‘collect all’ on the active controller to > get a summary of the system state and use those logs for off system debug > of your issue. > > > > Eric MacDonald. > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: mtcAgent.log Type: application/octet-stream Size: 471130 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: hbsAgent.log Type: application/octet-stream Size: 4664442 bytes Desc: not available URL: From chenjie.xu at intel.com Wed Mar 27 02:38:27 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Wed, 27 Mar 2019 02:38:27 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <72A55890-B007-4E93-A74A-291C725B158E@windriver.com> References: <151EE31B9FCCA54397A757BC674650F0BA4D1AA8@ALA-MBD.corp.ad.wrs.com> <72A55890-B007-4E93-A74A-291C725B158E@windriver.com> Message-ID: Hi Matt, Sorry for misleading! I mean “NUMA sections are still missing”. I have multiple systems experiencing this issue: 1. 0306 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 2. 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 3. 0305 ISO image on 4 bare metals 4. 0315 ISO image one 1 bare metals The item 1, 2 and 3 use same bare metals. The item 4 use a separate bare metal. I will try 0322 ISO image on 4 bare metals. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 26, 2019 11:10 PM To: Khalil, Ghada ; Xu, Chenjie ; Martinez Monroy, Elio ; Lin, Shuicheng ; Cabrales, Ada ; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io' ; Zhao, Forrest Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Can you clarify this statement? “NUMA sections missing bug still exits”. Did you mean to say that the missing NUMA sections in the domain XML are now present, but you still can’t ping over the vhost port, or are you saying the NUMA sections are still missing? Do you have multiple systems that are experiencing this issue, or is it isolated to a single system that you are having problems with the NUMA topology? I believe you mentioned that you saw the same connectivity issues on a standard load from the mirror, so that still points to a test system / environment issue. As Ghada mentioned, I think the next steps are to get results from the sanity systems with the same load baseline and to test with your custom load on a system that has been proven to work on the standard load. -Matt From: Ghada Khalil > Date: Tuesday, March 26, 2019 at 9:28 AM To: "Xu, Chenjie" >, "Peters, Matt" >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Has Elio or Rich from the test team tried the new load as well on their systems? Do they see the same issues you reported? I think we need some data for another system to compare. Ada, As part of this thread, I also requested that a VM connectivity test be added to regular sanity so that there is data from the daily cengn builds w/o the new version of ovs-dpdk. Has the sanity suite been updated? Thanks, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 26, 2019 7:09 AM To: Peters, Matt; Martinez Monroy, Elio; Khalil, Ghada; Lin, Shuicheng; Cabrales, Ada; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I installed StarlingX using the new 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals. NUMA sections missing bug still exits: https://bugs.launchpad.net/starlingx/+bug/1820378 This time I update the docker images to latest before installing StarlingX. And the docker images versions and build baseline have been attached. Could you please help review the docker image versions? Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Friday, March 22, 2019 8:31 PM To: Xu, Chenjie >; Martinez Monroy, Elio >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Comparing the image list to our labs shows a difference in the image IDs (sha), but I’m not sure if that is just a difference in build baselines or an actual difference in the images. Since some of them align, I think you might be running a different set of images. Can you confirm what the build baseline is that you pulled the images from? I have attached a sample list from our labs for comparison. -Matt From: "Xu, Chenjie" > Date: Friday, March 22, 2019 at 7:25 AM To: "Peters, Matt" >, "Martinez Monroy, Elio" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, The docker image versions in my environment and helm-charts-manifest-no-tests.tgz has been attached. The helm-charts-manifest-no-tests.tgz is built by Shuicheng for the OVSDPDK Upgrade Testing ISO image. Best Regards, Xu, Chenjie From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Thursday, March 21, 2019 11:20 PM To: Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Perfect, I will be cheking my mail for that new ISO. Adding Richo , he is the one that is going to execute the tests. Thanks BR Elio From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, March 21, 2019 9:15 AM To: Lin, Shuicheng >; Cabrales, Ada >; Martinez Monroy, Elio > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, We discussed this in the networking bi-weekly team meeting today. Please re-enable the mlx pmd – re-apply the following patch: https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch Then please rebase to the latest master and build a new load for Ada’s team to start testing Hi Elio, One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 Thanks, Ghada From: Khalil, Ghada Sent: Thursday, March 21, 2019 9:12 AM To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. Can you confirm that the load being used has the mellanox pmd enabled in it? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 21, 2019 9:03 AM To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie for the testing. Hi all, Does it mean greenlight for code merge, or any other test is needed? Here is the patch list: https://review.openstack.org/642672 https://review.openstack.org/642673 Best Regards Shuicheng From: Xu, Chenjie Sent: Thursday, March 21, 2019 5:46 PM To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From forrest.zhao at intel.com Wed Mar 27 03:22:28 2019 From: forrest.zhao at intel.com (Zhao, Forrest) Date: Wed, 27 Mar 2019 03:22:28 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190325 In-Reply-To: <8557B550001AFB46A43A0CCC314BF85153CAEBFF@FMSMSX108.amr.corp.intel.com> References: <8557B550001AFB46A43A0CCC314BF85153CAEBFF@FMSMSX108.amr.corp.intel.com> Message-ID: <6345119E91D5C843A93D64F498ACFA13744DE6C0@SHSMSX101.ccr.corp.intel.com> Hi Carlos, Has VM connectivity test been added to regular sanity test, as is requested in attached email? Besides the number of PASS/FAIL test cases, how can we know/check which test cases are actually PASS/FAIL? Thanks, Forrest From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Wednesday, March 27, 2019 11:13 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190325 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Mar-25 (link) Status: YELLOW =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup Manual [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [FAIL] Sanity Platform 07 TCs [FAIL] TOTAL: [ 57 TCs FAIL ] AIO - Duplex Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 05 TCs [PASS] TOTAL: [ 58 TCs PASS ] Standard - Local Storage (2+2) Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 05 TCs [PASS] TOTAL: [ 58 TCs PASS ] Standard - Dedicated Storage (2+2+2) Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 16 TCs [PASS] | 36 TCs [FAIL] Sanity Platform 05 TCs [PASS] TOTAL: [ 22 TCs PASS | 36 TCs FAIL ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [FAIL] Sanity Platform 07 TCs [FAIL] TOTAL: [ 04 TCs PASS | 57 TCs FAIL ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 05 TCs [PASS] TOTAL: [ 62 TCs PASS ] Standard - Local Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 05 TCs [PASS] TOTAL: [ 62 TCs PASS ] Standard - Dedicated Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 05 TCs [PASS] TOTAL: [ 62 TCs PASS ] ------------------------------------------------------------------ Simplex - application-apply fails at 95% - ceilometer pod Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1820928 Could not create VMs on Standard Dedicated Storage, in bare metal environment Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1821841 ------------------------------------------------------------------ This is the list of test cases executed: https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: "Khalil, Ghada" Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Date: Tue, 26 Mar 2019 13:28:06 +0000 Size: 67341 URL: From chenjie.xu at intel.com Wed Mar 27 09:45:44 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Wed, 27 Mar 2019 09:45:44 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing References: <151EE31B9FCCA54397A757BC674650F0BA4D1AA8@ALA-MBD.corp.ad.wrs.com> <72A55890-B007-4E93-A74A-291C725B158E@windriver.com> Message-ID: Hi Matt, I tried standard 0322 ISO image on 4 bare metals and “NUMA sections are still missing”. The docker images versions and build baseline have been attached. The ISO image link is following: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T174230Z/outputs/iso/ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Wednesday, March 27, 2019 10:38 AM To: 'Peters, Matt' ; Khalil, Ghada ; Martinez Monroy, Elio ; Lin, Shuicheng ; Cabrales, Ada ; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io' ; Zhao, Forrest Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, Sorry for misleading! I mean “NUMA sections are still missing”. I have multiple systems experiencing this issue: 1. 0306 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 2. 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 3. 0305 ISO image on 4 bare metals 4. 0315 ISO image one 1 bare metals The item 1, 2 and 3 use same bare metals. The item 4 use a separate bare metal. I will try 0322 ISO image on 4 bare metals. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 26, 2019 11:10 PM To: Khalil, Ghada >; Xu, Chenjie >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Can you clarify this statement? “NUMA sections missing bug still exits”. Did you mean to say that the missing NUMA sections in the domain XML are now present, but you still can’t ping over the vhost port, or are you saying the NUMA sections are still missing? Do you have multiple systems that are experiencing this issue, or is it isolated to a single system that you are having problems with the NUMA topology? I believe you mentioned that you saw the same connectivity issues on a standard load from the mirror, so that still points to a test system / environment issue. As Ghada mentioned, I think the next steps are to get results from the sanity systems with the same load baseline and to test with your custom load on a system that has been proven to work on the standard load. -Matt From: Ghada Khalil > Date: Tuesday, March 26, 2019 at 9:28 AM To: "Xu, Chenjie" >, "Peters, Matt" >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Has Elio or Rich from the test team tried the new load as well on their systems? Do they see the same issues you reported? I think we need some data for another system to compare. Ada, As part of this thread, I also requested that a VM connectivity test be added to regular sanity so that there is data from the daily cengn builds w/o the new version of ovs-dpdk. Has the sanity suite been updated? Thanks, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 26, 2019 7:09 AM To: Peters, Matt; Martinez Monroy, Elio; Khalil, Ghada; Lin, Shuicheng; Cabrales, Ada; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I installed StarlingX using the new 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals. NUMA sections missing bug still exits: https://bugs.launchpad.net/starlingx/+bug/1820378 This time I update the docker images to latest before installing StarlingX. And the docker images versions and build baseline have been attached. Could you please help review the docker image versions? Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Friday, March 22, 2019 8:31 PM To: Xu, Chenjie >; Martinez Monroy, Elio >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Comparing the image list to our labs shows a difference in the image IDs (sha), but I’m not sure if that is just a difference in build baselines or an actual difference in the images. Since some of them align, I think you might be running a different set of images. Can you confirm what the build baseline is that you pulled the images from? I have attached a sample list from our labs for comparison. -Matt From: "Xu, Chenjie" > Date: Friday, March 22, 2019 at 7:25 AM To: "Peters, Matt" >, "Martinez Monroy, Elio" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, The docker image versions in my environment and helm-charts-manifest-no-tests.tgz has been attached. The helm-charts-manifest-no-tests.tgz is built by Shuicheng for the OVSDPDK Upgrade Testing ISO image. Best Regards, Xu, Chenjie From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Thursday, March 21, 2019 11:20 PM To: Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Perfect, I will be cheking my mail for that new ISO. Adding Richo , he is the one that is going to execute the tests. Thanks BR Elio From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, March 21, 2019 9:15 AM To: Lin, Shuicheng >; Cabrales, Ada >; Martinez Monroy, Elio > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, We discussed this in the networking bi-weekly team meeting today. Please re-enable the mlx pmd – re-apply the following patch: https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch Then please rebase to the latest master and build a new load for Ada’s team to start testing Hi Elio, One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 Thanks, Ghada From: Khalil, Ghada Sent: Thursday, March 21, 2019 9:12 AM To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. Can you confirm that the load being used has the mellanox pmd enabled in it? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 21, 2019 9:03 AM To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie for the testing. Hi all, Does it mean greenlight for code merge, or any other test is needed? Here is the patch list: https://review.openstack.org/642672 https://review.openstack.org/642673 Best Regards Shuicheng From: Xu, Chenjie Sent: Thursday, March 21, 2019 5:46 PM To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: 0322-standard-build-info.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: 0322-standard-compute-0.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: 0322-standard-controller-0.txt URL: From Matt.Peters at windriver.com Wed Mar 27 12:10:13 2019 From: Matt.Peters at windriver.com (Peters, Matt) Date: Wed, 27 Mar 2019 12:10:13 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: References: <151EE31B9FCCA54397A757BC674650F0BA4D1AA8@ALA-MBD.corp.ad.wrs.com> <72A55890-B007-4E93-A74A-291C725B158E@windriver.com> Message-ID: Hello Chenjie, Can you run the following set of commands on your test system compute hosts and provide the output for each? sudo /usr/sbin/dmidecode virsh nodeinfo /usr/bin/topology grep -i numa /var/log/dmesg From: "Xu, Chenjie" Date: Wednesday, March 27, 2019 at 5:45 AM To: "Peters, Matt" , Ghada Khalil , "Martinez Monroy, Elio" , "Lin, Shuicheng" , "Cabrales, Ada" , "Perez, Ricardo O" Cc: "'starlingx-discuss at lists.starlingx.io'" , "Zhao, Forrest" Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I tried standard 0322 ISO image on 4 bare metals and “NUMA sections are still missing”. The docker images versions and build baseline have been attached. The ISO image link is following: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T174230Z/outputs/iso/ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Wednesday, March 27, 2019 10:38 AM To: 'Peters, Matt' ; Khalil, Ghada ; Martinez Monroy, Elio ; Lin, Shuicheng ; Cabrales, Ada ; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io' ; Zhao, Forrest Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, Sorry for misleading! I mean “NUMA sections are still missing”. I have multiple systems experiencing this issue: 1. 0306 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 2. 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 3. 0305 ISO image on 4 bare metals 4. 0315 ISO image one 1 bare metals The item 1, 2 and 3 use same bare metals. The item 4 use a separate bare metal. I will try 0322 ISO image on 4 bare metals. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 26, 2019 11:10 PM To: Khalil, Ghada >; Xu, Chenjie >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Can you clarify this statement? “NUMA sections missing bug still exits”. Did you mean to say that the missing NUMA sections in the domain XML are now present, but you still can’t ping over the vhost port, or are you saying the NUMA sections are still missing? Do you have multiple systems that are experiencing this issue, or is it isolated to a single system that you are having problems with the NUMA topology? I believe you mentioned that you saw the same connectivity issues on a standard load from the mirror, so that still points to a test system / environment issue. As Ghada mentioned, I think the next steps are to get results from the sanity systems with the same load baseline and to test with your custom load on a system that has been proven to work on the standard load. -Matt From: Ghada Khalil > Date: Tuesday, March 26, 2019 at 9:28 AM To: "Xu, Chenjie" >, "Peters, Matt" >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Has Elio or Rich from the test team tried the new load as well on their systems? Do they see the same issues you reported? I think we need some data for another system to compare. Ada, As part of this thread, I also requested that a VM connectivity test be added to regular sanity so that there is data from the daily cengn builds w/o the new version of ovs-dpdk. Has the sanity suite been updated? Thanks, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 26, 2019 7:09 AM To: Peters, Matt; Martinez Monroy, Elio; Khalil, Ghada; Lin, Shuicheng; Cabrales, Ada; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I installed StarlingX using the new 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals. NUMA sections missing bug still exits: https://bugs.launchpad.net/starlingx/+bug/1820378 This time I update the docker images to latest before installing StarlingX. And the docker images versions and build baseline have been attached. Could you please help review the docker image versions? Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Friday, March 22, 2019 8:31 PM To: Xu, Chenjie >; Martinez Monroy, Elio >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Comparing the image list to our labs shows a difference in the image IDs (sha), but I’m not sure if that is just a difference in build baselines or an actual difference in the images. Since some of them align, I think you might be running a different set of images. Can you confirm what the build baseline is that you pulled the images from? I have attached a sample list from our labs for comparison. -Matt From: "Xu, Chenjie" > Date: Friday, March 22, 2019 at 7:25 AM To: "Peters, Matt" >, "Martinez Monroy, Elio" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, The docker image versions in my environment and helm-charts-manifest-no-tests.tgz has been attached. The helm-charts-manifest-no-tests.tgz is built by Shuicheng for the OVSDPDK Upgrade Testing ISO image. Best Regards, Xu, Chenjie From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Thursday, March 21, 2019 11:20 PM To: Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Perfect, I will be cheking my mail for that new ISO. Adding Richo , he is the one that is going to execute the tests. Thanks BR Elio From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, March 21, 2019 9:15 AM To: Lin, Shuicheng >; Cabrales, Ada >; Martinez Monroy, Elio > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, We discussed this in the networking bi-weekly team meeting today. Please re-enable the mlx pmd – re-apply the following patch: https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch Then please rebase to the latest master and build a new load for Ada’s team to start testing Hi Elio, One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 Thanks, Ghada From: Khalil, Ghada Sent: Thursday, March 21, 2019 9:12 AM To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. Can you confirm that the load being used has the mellanox pmd enabled in it? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 21, 2019 9:03 AM To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie for the testing. Hi all, Does it mean greenlight for code merge, or any other test is needed? Here is the patch list: https://review.openstack.org/642672 https://review.openstack.org/642673 Best Regards Shuicheng From: Xu, Chenjie Sent: Thursday, March 21, 2019 5:46 PM To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Wed Mar 27 16:52:27 2019 From: scott.little at windriver.com (Scott Little) Date: Wed, 27 Mar 2019 12:52:27 -0400 Subject: [Starlingx-discuss] Publish container image list? In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA46BAB1@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA46BAB1@ALA-MBD.corp.ad.wrs.com> Message-ID: <610643d3-79d7-ba67-cf44-395b62eae8ff@windriver.com> Starting soon, for cengn builds that include docker images, you can expect to see something like .... http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos//outputs/docker-images/--.rpmlst http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos//outputs/docker-images/--.piplst stx-aodh-centos-dev.piplst: Babel==2.6.0 Jinja2==2.10 Mako==1.0.7 ... stx-aodh-centos-dev.rpmlst: acl-2.2.51-14.el7.x86_64 apr-1.4.8-3.el7_4.1.x86_64 apr-util-1.5.2-6.el7.x86_64 ... If you build your own images, the files are found here ...    $MY_WORKSPACE/std/build-images/ Scott On 2019-03-26 2:09 p.m., Penney, Don wrote: > > Hi Curtis, > > That work is in progress now. We’ve updated the image build tool to > record versions, which will be an input to building the application > charts. Additionally, an upcoming work item will be to publish these > records as part of the CENGN build. > > Cheers, > > Don. > > *From:*Curtis [mailto:serverascode at gmail.com] > *Sent:* Tuesday, March 26, 2019 2:07 PM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] Publish container image list? > > Hi All, > > If we are not already (which maybe we are, this is a big project) I > think it would be useful to publish a list of containers that match up > with a particular release. Otherwise I have to build it on my own > anyways (for example for building out a repeatable workshop setup). > > I know we publish an ISO, RPMs, and Helm charts, but it's be nice to > have a list of image and tags to use to be able to populate local > docker registries. Or a way to generate that list from existing > artifacts...if it doesn't exist already that is. > > Also, right now my list has many of the stx images as > "dev-centos-master-latest" and I'd like to firm that up with versions > if possible. > > Thanks, > > Curtis > > > _______________________________________________ > 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 build.starlingx at gmail.com Wed Mar 27 17:19:29 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 27 Mar 2019 13:19:29 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_publish_docker_images - Build # 48 - Failure! Message-ID: <929469166.44.1553707170961.JavaMail.javamailuser@localhost> Project: STX_publish_docker_images Build #: 48 Status: Failure Timestamp: 20190327T171927Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/.centos/20190327T013001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190327T013001Z OS: centos PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/.centos/20190327T013001Z/logs BUILD_STREAM: dev TIMESTAMP: 20190327T013001Z PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/.centos/20190327T013001Z/logs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/.centos/20190327T013001Z/outputs MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/.centos From dtroyer at gmail.com Wed Mar 27 18:06:57 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Wed, 27 Mar 2019 13:06:57 -0500 Subject: [Starlingx-discuss] stx-nova changes In-Reply-To: <6cc338ab-538f-582d-b7c0-5a9081584430@windriver.com> References: <6cc338ab-538f-582d-b7c0-5a9081584430@windriver.com> Message-ID: On Wed, Mar 27, 2019 at 11:12 AM Chris Friesen wrote: > Just to clarify, would builds be done from stx/stein once created? (And > stable/stein if stx/stein doesn't exist?) When we create the stx-nova stx/stein branch we would change the build to pull from there rather than upstream. Until then I do not expect to change anything. I will mirror upstream master and stable/stein branches into stx-nova after https://review.openstack.org/#/c/648180/ merges so we have a bit of time to find other things still assuming that is the old stx nova tree. dt -- Dean Troyer dtroyer at gmail.com From bruce.e.jones at intel.com Wed Mar 27 19:34:22 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 27 Mar 2019 19:34:22 +0000 Subject: [Starlingx-discuss] Release meeting tomorrow Message-ID: <9A85D2917C58154C960D95352B22818BD0708BBC@fmsmsx123.amr.corp.intel.com> We didn't get the chance to talk about the release issues today at the community meeting. The release team (me, Bill, Ghada) would like to invite all interested community members to join us for the release team meeting tomorrow. It's at 11AM PDT (2PM EDT) on Thursday using the usual Zoom meeting. brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Mar 27 20:03:00 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 27 Mar 2019 20:03:00 +0000 Subject: [Starlingx-discuss] Community Call (March 27, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC0A21644@ALA-MBD.corp.ad.wrs.com> Notes from the Mar 27th call. Please be aware of issues with AIO-SX with recent loads - issue being tracked under https://bugs.launchpad.net/starlingx/+bug/1820928. Bill... - Welcome folks from FiberHome! - Are there any other new community members? - none today - Denver Planning: Open Infrastructure Summit & PTG (Ildiko) - Forum - these are discussions about a particular topic, not a formal presentation - connecting experts & interested parties to share knowledge - Linux distro integration best practices: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23688/cross-project-best-practices-for-integration-with-linux-distributions - StarlingX for Operators: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23661/starlingx-for-openstack-operators - PTG planning etherpad: https://etherpad.openstack.org/p/stx-ptg-preparation-denver-2019 - if you'd like to *attend* the PTG remotely, please let Ildiko know - she's got a "pretty good" microphone for remote attendees - please add your name to the PTG etherpad (just above) and also indicate if you've got any particular topic(s) you'd like discussed - Presentations - - Hands On Workshop - - the following folks indicated that they'll be in Denver - Dean, Brent, Saul, Cesar, Bruce, Greg - Skydive project: https://skydive.network. Cool looking network management software. Is it interesting to StarlingX users? - network visualization/monitoring process - per Curtis, an SDN version of traceroute, like this, could be useful - per Ildiko, the Neutron team may have been using this - so possibly we could ask them about it's usefulness - Distro.openstack (Bruce) - upstream Nova work looking like it won't land til late May / early June - relevant to our release planning - Docs (Michael / Bruce) - Docs team input into restructuring needed: https://docs.google.com/document/d/12Q0XWiEG_-7FDhGSVvSbhvpKmHOTmMszLjX3xkEKFRY/edit?usp=sharing - Networking (Ghada) - much focus on upversioning OVS-DPDK - Issues seen in system used in China even with standard loads. - Same issues are not seen in WR systems. working w/ Ada's test team to get data from their testing. - Current forecast of April 5 will need to be re-forecasted. Expect 2wks delay. - Security (Ken) - first scan completed, by hand, identified real issues - ISO scan being automated (Victor & Memo) - working on container scanning as well - Build (Cesar/Ken) - steady as we go, looking for optimizations - Containers (Frank) - 30 storyboards open - 1 or 2 ready to close - plan is mostly in place, a few items to close - goes out to early June - LP 1820928 - causes application apply to fail, impacts AIO-SX, team is focused on this --- avoid AIO-SX til this bug is resolved - CentOS (Cindy) - per Ada, CentOS 7.6 testing hasn't started yet, focused on OVS-DPDK - Ceph Upgrade (Cindy) - team working on getting all patches onto master by early next week - Ada will plan the testing accordingly - Multi-OS (Cesar) - integration of Ubuntu going as planned - Test (Ada/Numan) - Ada/Numan reviewing per-feature test plans, planning to have a read-out for the release plan meeting tomorrow - Strategy for performance footprint and yardstick (Victor) - https://docs.google.com/presentation/d/1Nr12zDRXf34kpjiA0LsFLU8GIpMY8Y-H2zmiC96CD4A/edit?usp=sharing - Does anyone need help? - we didn't get to this topic, will pick this up in the next Release Planning meeting... - Readout from the release team (Bill, Bruce, Ghada) - We have several long-pole items that are anchor features for the release. - The longest is Dist Cloud. 2nd longest is the OpenStack Backport content. - We are not going to hit our current dates. The release team has a proposal. We have some options - Our previous release policy has been to do time based releases. - If we release on schedule we will have several incomplete anchor features and the system will not be stable. - The reality is that we are currently doing a content based release. - Going foward we should decide if we want to be time based or content based, and if the former, we need to do more upfront work to make sure we come closer to hitting our dates. - We can remove content from the release. - The Distributed Cloud content is candidate. - The OpenStack backports are a candidate - We can do a follow-on release that adds features (e.g. distcloud) and bug fixes. - If we only ship with Container support and it is stable that would be a big win for StarlingX - (Ghada) Still need to work on refining the release back-end plan with focus on the test activities and final bug fixing cyle - Not confident the original durations are sufficient. They were based on a much shorter Feature Development cycle. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ From: Zvonar, Bill Sent: Tuesday, March 26, 2019 9:28 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: Community Call (March 27, 2019) Reminder of tomorrow's Community call - please feel free to add to the agenda at [0]. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1500_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190327T1400 From michael.l.tullis at intel.com Wed Mar 27 20:22:41 2019 From: michael.l.tullis at intel.com (Tullis, Michael L) Date: Wed, 27 Mar 2019 20:22:41 +0000 Subject: [Starlingx-discuss] [docs][meetings] docs team meeting minutes 3/27/2019 Message-ID: <3808363B39586544A6839C76CF81445EA1ADB449@ORSMSX104.amr.corp.intel.com> For notes and new action items from our docs team meeting today, see our etherpad: https://etherpad.openstack.org/p/stx-documentation Join us if you have interest in StarlingX docs! We meet Wednesdays, and call logistics are here: https://wiki.openstack.org/wiki/Starlingx/Meetings. -- Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ken.Young at windriver.com Wed Mar 27 20:35:27 2019 From: Ken.Young at windriver.com (Young, Ken) Date: Wed, 27 Mar 2019 20:35:27 +0000 Subject: [Starlingx-discuss] [build][meetings] Build team meeting minutes /21/2019 In-Reply-To: <0B566C62EC792145B40E29EFEBF1AB4710FDBAAB@fmsmsx123.amr.corp.intel.com> References: <0B566C62EC792145B40E29EFEBF1AB4710FDBAAB@fmsmsx123.amr.corp.intel.com> Message-ID: <34A78B1E-166F-4CB5-8A1F-434D04A3D4BF@windriver.com> Cesar, Thank you for sending the minutes from last week. I am looking forward to our call tomorrow. For tomorrow, I would ask that the following be on the agenda: 1. CVE Correction Bugs 2. CVE Scanning for ISO Regards, Ken Y From: "Lara, Cesar" Date: Tuesday, March 26, 2019 at 6:20 PM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] [build][meetings] Build team meeting minutes /21/2019 Build team meeting Agenda for 03/21/2019 - Update on build bugs and stories - Multi Layer build proposal - Mirror tool - Opens Notes Update on build bugs and stories – just wanted to do a check on the stories and bugs assigned to the build team and make sure those are being worked on Current stories https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.build&project_group_id=86 Need to check with Bruce/Saul if this one is still valid https://storyboard.openstack.org/#!/story/2003288 Current bugs https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.build AR – Build team, please update your bugs o stories Multi-Layer build proposal So far we are on sync with most of the ideas of a multi-layer build on the PoC for Ubuntu that is happening as part of Multi-OS efforts (https://github.com/starlingx-staging/stx-packaging ) but we still need to get agreement on the requirements for enablement, we need to start building a discussion matrix to map these requirements and level set the team as far as to what are the problems that we are trying to solve. Scott also contributed his proposal in which we use the current tools to assign packages to layers, defined by the developer and build only those packages, taking from some of the build avoidance ideas. AR- Cesar to start an Etherpad to facilitate brainstorming around this https://etherpad.openstack.org/p/stx-build-requirements - done Mirror tool Erich presented a demo on this tool, currently at 90% development, and still need to integrate the logic behind build avoidance and the Cengn hosted mirror, spec is also on track to be finished and presented to TSC for approval. Opens CVE check integration to Intel build Automation, currently enabled for manual triggered scans on build automation, still working to have fully automated integration and then find a way to integrate this as part of Cengn automation. Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From cesar.lara at intel.com Wed Mar 27 23:34:53 2019 From: cesar.lara at intel.com (Lara, Cesar) Date: Wed, 27 Mar 2019 23:34:53 +0000 Subject: [Starlingx-discuss] [build][meetings] Build team meeting agenda for 3/28/2019 Message-ID: <0B566C62EC792145B40E29EFEBF1AB4710FDC9F7@fmsmsx123.amr.corp.intel.com> Build team meeting Agenda for 3/28/2019 - CVE Correction Bugs - CVE Scanning for ISO - Multi layer build requirements discussion https://etherpad.openstack.org/p/stx-build-requirements Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Thu Mar 28 00:24:22 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 28 Mar 2019 00:24:22 +0000 Subject: [Starlingx-discuss] DUPLEX: PXE Image does not include the ixgbevf In-Reply-To: <1592707842.1434226.1553698260345@communicator.strato.com> References: <1592707842.1434226.1553698260345@communicator.strato.com> Message-ID: <9700A18779F35F49AF027300A49E7C765FEA1BBF@SHSMSX101.ccr.corp.intel.com> Hi Marcel, Yes, ixgbevf driver is not included in PXE image. Do we need virtual function support during PXE boot stage? If so, we could add VF drivers to PXE image. To add the driver to pxe image, we need modify update-pxe-network-installer script in cgcs-root/build-tools. And follow the build instruction in below Wiki to generate the new pxe image. https://docs.starlingx.io/developer_guide/latest/index.html Best Regards Shuicheng -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Wednesday, March 27, 2019 10:51 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] DUPLEX: PXE Image does not include the ixgbevf Hi, I just installed the image from 2019-03-25 and trying to install and configure the controller-1. It seems like that the PXEimage does not include the Intel driver ixgbevf. Is this intended and what is the recommended procedure to get this module into the pxe image? Thanks Marcel _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From juan.carlos.alonso at intel.com Thu Mar 28 02:11:22 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Thu, 28 Mar 2019 02:11:22 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190327 Message-ID: <8557B550001AFB46A43A0CCC314BF85153CAF038@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Mar-27 (link) Status: YELLOW =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup Manual [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [FAIL] Sanity Platform 07 TCs [FAIL] TOTAL: [ 57 TCs FAIL ] AIO - Duplex Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 51 TCs [PASS] | 01 TCs [FAIL] Sanity Platform 04 TCs [PASS] | 01 TCs [FAIL] TOTAL: [56 TCs PASS | 02 TCs FAIL] Standard - Local Storage (2+2) Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 51 TCs [PASS] | 01 TCs [FAIL] Sanity Platform 04 TCs [PASS] | 01 TCs [FAIL] TOTAL: [ 56 TCs PASS | 02 TCs FAIL ] Standard - Dedicated Storage (2+2+2) Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 16 TCs [PASS] | 36 TCs [FAIL] Sanity Platform 04 TCs [PASS] | 01 TCs [FAIL] TOTAL: [ 21 TCs PASS | 37 TCs FAIL ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [] Provisioning 01 TCs [] Sanity OpenStack 49 TCs [] Sanity Platform 07 TCs [] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [] Provisioning 01 TCs [] Sanity OpenStack 52 TCs [] Sanity Platform 05 TCs [] TOTAL: [ 62 TCs ] Standard - Local Storage Setup 04 TCs [] Provisioning 01 TCs [] Sanity OpenStack 52 TCs [] Sanity Platform 05 TCs [] TOTAL: [ 62 TCs ] Standard - Dedicated Storage Setup 04 TCs [] Provisioning 01 TCs [] Sanity OpenStack 52 TCs [] Sanity Platform 05 TCs [] TOTAL: [ 62 TCs ] ------------------------------------------------------------------ Simplex BM and Virtual - application-apply fails at 95% ceilometer pod Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1820928 Standard Dedicated Storage BM - Could not create VMs Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1821841 All Configurations BM and Virtual - Create Instance Trough Stack: openstack: 'stack create...' is not an openstack command. Will check if still available and update to current openstack command needed to create instances through an stack All Configurations BM and Virtual - Create Check Delete POD: Seems that the docker image is no longer exists. Will update the test to use an available image to create POD. All Configurations Virtual - Our dedicated server got a filesystem error and could not deploy STX systems. ------------------------------------------------------------------ This is the list of test cases executed: https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Peters at windriver.com Thu Mar 28 11:26:22 2019 From: Matt.Peters at windriver.com (Peters, Matt) Date: Thu, 28 Mar 2019 11:26:22 +0000 Subject: [Starlingx-discuss] DUPLEX: PXE Image does not include the ixgbevf In-Reply-To: <1592707842.1434226.1553698260345@communicator.strato.com> References: <1592707842.1434226.1553698260345@communicator.strato.com> Message-ID: <05A48904-06C8-4790-8A7C-69088E9712AF@windriver.com> Hello Marcel, StarlingX does not currently package and load VF drivers on the host. SRIOV interfaces that are managed by StarlingX are currently only consumed by the guest VM instances, and therefore the drivers are not required on the host for the physical devices managed by system inventory. Regards, Matt On 2019-03-27, 10:53 AM, "Marcel Schaible" wrote: Hi, I just installed the image from 2019-03-25 and trying to install and configure the controller-1. It seems like that the PXEimage does not include the Intel driver ixgbevf. Is this intended and what is the recommended procedure to get this module into the pxe image? Thanks Marcel _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ian.Jolliffe at windriver.com Thu Mar 28 12:52:10 2019 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Thu, 28 Mar 2019 12:52:10 +0000 Subject: [Starlingx-discuss] [TSC] Minutes - 3/21 Message-ID: <28BA68B1-AEA7-4E7C-88E5-E34B86CD44F5@windriver.com> Hi all; The minutes and notes from the 3/21 TSC call are below. Packet.com MOU review Everyone on TSC should have recieved a copy; need to get consensus that it's Ok, and then have the OpenStack Foundation (who have already looked at it and have no issues) sign off. Then onto next steps! Consensus is we move forward with MOU Curtis/Shuquan - FYI - StarlingX for OpenStack Operators forum session accepted https://www.openstack.org/summit/denver-2019/summit-schedule/events/23661/starlingx-for-openstack-operators Foundation staff were adding feature to allow more than one moderator to forum sessions This is FYI - at Forum Curtis/Shuquan - OpenInfra Summit Workshop Curtis - Can't seem to install using an "alternative registry" (could be something I'm missing); will make it hard to run the workshop as all students will have to pull images, and sometimes those pulls fail Entered a bug: https://bugs.launchpad.net/starlingx/+bug/1821090 some trials underway for the concept and seems to be working instructions for local registry on Containers Wiki Contrib/Experimental repo - sgw Using Git/hub - starlingX staging repo Saul to recommend directory layout and infrastructure support So this doesn't become a dumping ground PTG - plan - day and a half for STX - Thursday PM and Friday Next week work on PTG agenda Curtis - Adrien @INRIA (French research institute) asked about having some discussions about edge computing and stx Repo Host Name changes 19 Apr 2019 confirmed date repo names will look like https://opendev.org/starlingx/PROJECT Saul - raised STX-Root as one to potentially change - review next week Downtime TBD - mainly due to DNS updates Review again next week TSC election - close on date June 10 - seems to be ok Next release planning - review ether calc https://ethercalc.openstack.org/pj7rsux1c461 Focus on one theme every week Next week - How do we capture STX community contributions to other projects? From marcel at schaible-consulting.de Thu Mar 28 13:24:49 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Thu, 28 Mar 2019 14:24:49 +0100 (CET) Subject: [Starlingx-discuss] DUPLEX: PXE Image does not include the ixgbevf In-Reply-To: <9700A18779F35F49AF027300A49E7C765FEA1BBF@SHSMSX101.ccr.corp.intel.com> References: <1592707842.1434226.1553698260345@communicator.strato.com> <9700A18779F35F49AF027300A49E7C765FEA1BBF@SHSMSX101.ccr.corp.intel.com> Message-ID: <139115820.1489232.1553779489590@communicator.strato.com> Hi Shuicheng, thanks fpr your help. We are using an Artesyn Maxcore box and need the VF drivers for booting our controller-1. For my understanding: After the the controller-1 has booted from PXE and is getting configured via controller-0, are the VF drivers then loaded? Thanks Marcel > "Lin, Shuicheng" hat am 28. März 2019 um 01:24 geschrieben: > > > Hi Marcel, > Yes, ixgbevf driver is not included in PXE image. Do we need virtual function support during PXE boot stage? > If so, we could add VF drivers to PXE image. > To add the driver to pxe image, we need modify update-pxe-network-installer script in cgcs-root/build-tools. > And follow the build instruction in below Wiki to generate the new pxe image. > https://docs.starlingx.io/developer_guide/latest/index.html > > > Best Regards > Shuicheng > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Wednesday, March 27, 2019 10:51 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] DUPLEX: PXE Image does not include the ixgbevf > > Hi, > > I just installed the image from 2019-03-25 and trying to install and configure the controller-1. > > It seems like that the PXEimage does not include the Intel driver ixgbevf. > > Is this intended and what is the recommended procedure to get this module into the pxe image? > > Thanks > > Marcel > > _______________________________________________ > 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 Thu Mar 28 15:51:06 2019 From: Ken.Young at windriver.com (Young, Ken) Date: Thu, 28 Mar 2019 15:51:06 +0000 Subject: [Starlingx-discuss] [build][meetings] Build Team Meeting Minutes for 3/28/2019 Message-ID: <1E434DA4-250E-4E1A-86E7-67F174ADCDCA@windriver.com> Build team meeting Agenda for 3/28/2019 - CVE Correction Bugs - working now on these bugs with Erich - right now 2 CVEs are straightforward - perl - keepalive - systemd package is more work than anticipated - this package is modified; we have patches - the patches need to be rebased - they must not be fuzzy - need to make sure we don't touch the fix - if we do, Victor can creates test to ensure the CVE correction is still valid - testing the new packages - test the package itself - no for keepalive or perl - maybe for systemd if we impact the CVE correction - next: talk to Ada and run a sanity - CVE Scanning for ISO - Memo: - working on putting this in the pipeline - more challenging than anticipated - installation is a challenge - 75% done - automated scans – next steps - automation of the output - publish on a web server - further actions - replication of the setup in the open - wiki - jenkins scripts - CVE Scanning for the Containers - Option 1: use Clair - Create a harbor registry that pulled docker images from dockerHub - run clair scans (give some results immediately - Victor will play with this and review the results - enhance clair with Irene's changes - Option #2 vuls - Victor will compare results - Multi layer build requirements discussion https://etherpad.openstack.org/p/stx-build-requirements - 3 options were discussed 1/ Evolving the current build to augment the build avoidance capabilities 2/ Creating a new layered build 3/ Create a new atomic element build (proposed by Victor) - next steps are to flush out these options and propose a path forward - need Scott for this discussion to ensure we have SME /KenY -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Thu Mar 28 17:19:05 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Thu, 28 Mar 2019 17:19:05 +0000 Subject: [Starlingx-discuss] What is the new openstack command to create an stack? Message-ID: <8557B550001AFB46A43A0CCC314BF85153CAF169@FMSMSX108.amr.corp.intel.com> Hi, Do someone know what is the new openstack command to create an stack? Then to create an instance. I usually use: $openstack stack create --template ${stack_name} --parameter "NetID=${net_id}" But got the below error: openstack: 'stack create...' is not an openstack command. Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.hernandez.gonzalez at intel.com Thu Mar 28 17:28:07 2019 From: fernando.hernandez.gonzalez at intel.com (Hernandez Gonzalez, Fernando) Date: Thu, 28 Mar 2019 17:28:07 +0000 Subject: [Starlingx-discuss] What is the new openstack command to create an stack? In-Reply-To: <8557B550001AFB46A43A0CCC314BF85153CAF169@FMSMSX108.amr.corp.intel.com> References: <8557B550001AFB46A43A0CCC314BF85153CAF169@FMSMSX108.amr.corp.intel.com> Message-ID: <03D458D5BAFF6041973594B00B4E58CE5D68E6B4@CRSMSX104.amr.corp.intel.com> Hi JC, I am almost finishing the "HEAT HOT template" Test cases (the basics)... please look at the next link, under "HEAT_HOT_Template_07", you will see the prerequisites for creation of Nova Server instance and the required template. Regards, Fernando Hernandez Gonzalez Software Engineer Avenida del Bosque #1001 Col, El Bajío Zapopan, Jalisco MX, 45019 ____________________________________ Office: +52.33.16.45.01.34 inet 86450134 From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Thursday, March 28, 2019 11:19 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] What is the new openstack command to create an stack? Hi, Do someone know what is the new openstack command to create an stack? Then to create an instance. I usually use: $openstack stack create --template ${stack_name} --parameter "NetID=${net_id}" But got the below error: openstack: 'stack create...' is not an openstack command. Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ian.Jolliffe at windriver.com Thu Mar 28 17:55:40 2019 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Thu, 28 Mar 2019 17:55:40 +0000 Subject: [Starlingx-discuss] [TSC] Minutes of TSC meeting 3/28 Message-ID: Hi all; Trying to get the notes out in a more timely way. Below are the discussions from today’s meeting. Reviews to look at: https://review.openstack.org/#/c/634074/ Next release https://ethercalc.openstack.org/pj7rsux1c461 Curtis - I find the ethercalc a bit limiting for comments etc We reviewed a number of items today. We discussed we need a better process to work through the list and prioritize - this will be discussed again next week. Miguel and Dean offered good suggestions from other projects. Next meeting please come with ideas on what process we should use. Public service announcement - we are seeking input from users, please see ethercalc. Also, this will be a big topic for the PTG. How do we capture STX community contributions to other projects? Neutron is a big one - new API extension, dynamic management of network segment ranges. Now seeking input OpenStack Helm contributions in flight and completed - ~20 Nova - contributions - Blueprints and bug fixes Horizon - 2 or 3 commits, blueprint to come OPNFV - did try to track this kind of issue within their community - maybe we can leverage something they learned Brent and Bruce going to include in Project Update for the Summit Summit workshop FYI - Blog post is up: https://www.starlingx.io/blog/starlingx-openinfra-summit-workshop-2019.html Draft installation guide: https://docs.google.com/document/d/1P4d2eakEgJTyxU4iD_zlKrjAIyRJp23j3ebJT4tpSQo/edit?usp=sharing From Curtis - Thanks for the help on the issue I ran into using "docker import" vs "docker load" Packet project/PoC Curtis - Nothing new - MOU presumably being signed in the background At some point will need to determine how to manage credentials Would like to start thinking about performance testing in some fashion using packet resources Next week - Topic - Decide on 1st project and how we get this off the ground We didn't get to this, but I have added to the Agenda for next week. Last - if time - Community related Curtis - If anyone knows of any...looking for sponsors for OpenStack meetups in Canada, need food/beverage sponsors for Toronto and Ottawa (OICR and CENGN take care of space respectively). OVH taking care of Montreal. Curtis - Might do the STX Workshop in Toronto at next meetup, perhaps prior to summit From juan.carlos.alonso at intel.com Thu Mar 28 18:07:12 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Thu, 28 Mar 2019 18:07:12 +0000 Subject: [Starlingx-discuss] What is the new openstack command to create an stack? In-Reply-To: <03D458D5BAFF6041973594B00B4E58CE5D68E6B4@CRSMSX104.amr.corp.intel.com> References: <8557B550001AFB46A43A0CCC314BF85153CAF169@FMSMSX108.amr.corp.intel.com> <03D458D5BAFF6041973594B00B4E58CE5D68E6B4@CRSMSX104.amr.corp.intel.com> Message-ID: <8557B550001AFB46A43A0CCC314BF85153CAF1A9@FMSMSX108.amr.corp.intel.com> Hi Fernando, I have the same steps to test. The problem comes when execute "openstack stack create" command. Seems that there was an update with such command. I figured out that the current OpenStack documentation shows that we are using the correct command. Maybe we have a real issue. https://docs.openstack.org/heat/rocky/getting_started/create_a_stack.html Need to confirm. Regards. Juan Carlos Alonso From: Hernandez Gonzalez, Fernando Sent: Thursday, March 28, 2019 11:28 AM To: Alonso, Juan Carlos ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] What is the new openstack command to create an stack? Hi JC, I am almost finishing the "HEAT HOT template" Test cases (the basics)... please look at the next link, under "HEAT_HOT_Template_07", you will see the prerequisites for creation of Nova Server instance and the required template. Regards, Fernando Hernandez Gonzalez Software Engineer Avenida del Bosque #1001 Col, El Bajío Zapopan, Jalisco MX, 45019 ____________________________________ Office: +52.33.16.45.01.34 inet 86450134 From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Thursday, March 28, 2019 11:19 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] What is the new openstack command to create an stack? Hi, Do someone know what is the new openstack command to create an stack? Then to create an instance. I usually use: $openstack stack create --template ${stack_name} --parameter "NetID=${net_id}" But got the below error: openstack: 'stack create...' is not an openstack command. Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Thu Mar 28 18:29:06 2019 From: serverascode at gmail.com (Curtis) Date: Thu, 28 Mar 2019 14:29:06 -0400 Subject: [Starlingx-discuss] What is the new openstack command to create an stack? In-Reply-To: <8557B550001AFB46A43A0CCC314BF85153CAF1A9@FMSMSX108.amr.corp.intel.com> References: <8557B550001AFB46A43A0CCC314BF85153CAF169@FMSMSX108.amr.corp.intel.com> <03D458D5BAFF6041973594B00B4E58CE5D68E6B4@CRSMSX104.amr.corp.intel.com> <8557B550001AFB46A43A0CCC314BF85153CAF1A9@FMSMSX108.amr.corp.intel.com> Message-ID: On Thu, Mar 28, 2019 at 2:09 PM Alonso, Juan Carlos < juan.carlos.alonso at intel.com> wrote: > Hi Fernando, > > > > I have the same steps to test. The problem comes when execute “openstack > stack create” command. > > Seems that there was an update with such command. > > I figured out that the current OpenStack documentation shows that we are > using the correct command. Maybe we have a real issue. > > https://docs.openstack.org/heat/rocky/getting_started/create_a_stack.html > > Need to confirm. > I'm guessing you are missing python-heatclient. Thanks, Curtis > > > Regards. > > Juan Carlos Alonso > > > > *From:* Hernandez Gonzalez, Fernando > *Sent:* Thursday, March 28, 2019 11:28 AM > *To:* Alonso, Juan Carlos ; > starlingx-discuss at lists.starlingx.io > *Subject:* RE: [Starlingx-discuss] What is the new openstack command to > create an stack? > > > > Hi JC, > > > > I am almost finishing the “HEAT HOT template” Test cases (the basics)… please look at the next link , under “HEAT_HOT_Template_07”, you will see the prerequisites for creation of Nova Server instance and the required template. > > > > Regards, > > *Fernando Hernandez Gonzalez* > > *Software Engineer* > > > > Avenida del Bosque #1001 Col, El Bajío > > Zapopan, Jalisco MX, 45019 > > ____________________________________ > > *Office:* +52.33.16.45.01.34 inet 86450134 > > > > *From:* Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com > ] > *Sent:* Thursday, March 28, 2019 11:19 AM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] What is the new openstack command to > create an stack? > > > > Hi, > > > > Do someone know what is the new openstack command to create an stack? Then > to create an instance. > > > > I usually use: > > $openstack stack create --template ${stack_name} --parameter > "NetID=${net_id}" > > > > But got the below error: > > openstack: 'stack create…’ is not an openstack command. > > > > Regards. > > Juan Carlos Alonso > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Thu Mar 28 18:37:44 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 28 Mar 2019 19:37:44 +0100 Subject: [Starlingx-discuss] Initial StarlingX survey - feedback needed Message-ID: <88772002-9A60-4741-8CDF-1BB2D44C6769@gmail.com> Hi StarlingX Community, As I reached out about this earlier a few of us started to draft a survey to learn about what people and companies are doing around edge and to see if they know about StarlingX and getting some initial feedback on what they are interested in. Please note that the idea is to get a high level view and find out about interest as opposed to going into deep details on deployment options, use cases or ways to contribute. In that sense the main objectives for the survey is to keep it short and simple and make it easy to fill out. You will see that the questions are mainly having options to select from as opposed to being free form, the option to specify custom answer is provided where applicable like the use cases one as we can’t list all the possible ones. We also added a question to give any feedback people might have for the community. The OpenStack Foundation will have access to the complete dataset and will provide the anonymized information to the community once it’s available. The survey is available here: https://www.surveymonkey.com/r/StarlingX Please read through the questions and reply back if you have comments or questions. Thanks and Best Regards, Ildikó From elio.martinez.monroy at intel.com Wed Mar 27 18:47:13 2019 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Wed, 27 Mar 2019 18:47:13 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: References: <151EE31B9FCCA54397A757BC674650F0BA4D1AA8@ALA-MBD.corp.ad.wrs.com> <72A55890-B007-4E93-A74A-291C725B158E@windriver.com> Message-ID: <1466AF2176E6F040BD63860D0A241BBD46CA563A@FMSMSX109.amr.corp.intel.com> Hi Matt Just exercising same stuff, please check my outputs from compute-0, please let me know if something else is needed sudo /usr/sbin/dmdecode Password: sudo: /usr/sbin/dmdecode: command not found compute-0:~$ sudo /usr/sbin/dmidecode # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 10 structures occupying 419 bytes. Table at 0x000F6460. Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: SeaBIOS Version: Ubuntu-1.8.2-1ubuntu1 Release Date: 04/01/2014 Address: 0xE8000 Runtime Size: 96 kB ROM Size: 64 kB Characteristics: BIOS characteristics not supported Targeted content distribution is supported BIOS Revision: 0.0 Handle 0x0100, DMI type 1, 27 bytes System Information Manufacturer: QEMU Product Name: Standard PC (i440FX + PIIX, 1996) Version: pc-i440fx-2.5 Serial Number: Not Specified UUID: 71d54a5d-b569-4e1c-83e3-9babf169e824 Wake-up Type: Power Switch SKU Number: Not Specified Family: Not Specified Handle 0x0300, DMI type 3, 21 bytes Chassis Information Manufacturer: QEMU Type: Other Lock: Not Present Version: pc-i440fx-2.5 Serial Number: Not Specified Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: Unknown OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 Handle 0x0400, DMI type 4, 42 bytes Processor Information Socket Designation: CPU 0 Type: Central Processor Family: Other Manufacturer: QEMU ID: A3 06 01 00 FF FB 8B 07 Version: pc-i440fx-2.5 Voltage: Unknown External Clock: Unknown Max Speed: 2000 MHz Current Speed: 2000 MHz Status: Populated, Enabled Upgrade: Other L1 Cache Handle: Not Provided L2 Cache Handle: Not Provided L3 Cache Handle: Not Provided Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Core Count: 6 Core Enabled: 6 Thread Count: 1 Characteristics: None Handle 0x1000, DMI type 16, 23 bytes Physical Memory Array Location: Other Use: System Memory Error Correction Type: Multi-bit ECC Maximum Capacity: 10 GB Error Information Handle: Not Provided Number Of Devices: 1 Handle 0x1100, DMI type 17, 40 bytes Memory Device Array Handle: 0x1000 Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: 10240 MB Form Factor: DIMM Set: None Locator: DIMM 0 Bank Locator: Not Specified Type: RAM Type Detail: Other Speed: Unknown Manufacturer: QEMU Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Rank: Unknown Configured Clock Speed: Unknown Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x1300, DMI type 19, 31 bytes Memory Array Mapped Address Starting Address: 0x00000000000 Ending Address: 0x000BFFFFFFF Range Size: 3 GB Physical Array Handle: 0x1000 Partition Width: 1 Handle 0x1301, DMI type 19, 31 bytes Memory Array Mapped Address Starting Address: 0x00100000000 Ending Address: 0x002BFFFFFFF Range Size: 7 GB Physical Array Handle: 0x1000 Partition Width: 1 Handle 0x2000, DMI type 32, 11 bytes System Boot Information Status: No errors detected Handle 0x7F00, DMI type 127, 4 bytes End Of Table compute-0:~$ virsh nodeinfo CPU model: x86_64 CPU(s): 6 CPU frequency: 3792 MHz CPU socket(s): 1 Core(s) per socket: 6 Thread(s) per core: 1 NUMA cell(s): 1 Memory size: 10485236 KiB compute-0:~$ /usr/bin/topology TOPOLOGY: logical cpus : 6 sockets : 1 cores_per_pkg : 6 threads_per_core : 1 numa_nodes : 1 total_memory : 9.61 GiB memory_per_node : 10.00 GiB LOGICAL CPU TOPOLOGY: cpu_id : 0 1 2 3 4 5 socket_id : 0 0 0 0 0 0 core_id : 0 1 2 3 4 5 thread_id : 0 0 0 0 0 0 CORE TOPOLOGY: cpu_id socket_id core_id thread_id affinity 0 0 0 0 0x1 1 0 1 0 0x2 2 0 2 0 0x4 3 0 3 0 0x8 4 0 4 0 0x10 5 0 5 0 0x20 compute-0:~$ grep -i numa /var/log/dmesg [ 0.000000] No NUMA configuration found From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 27, 2019 6:10 AM To: Xu, Chenjie ; Khalil, Ghada ; Martinez Monroy, Elio ; Lin, Shuicheng ; Cabrales, Ada ; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io' ; Zhao, Forrest ; Rowsell, Brent Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Can you run the following set of commands on your test system compute hosts and provide the output for each? sudo /usr/sbin/dmidecode virsh nodeinfo /usr/bin/topology grep -i numa /var/log/dmesg From: "Xu, Chenjie" > Date: Wednesday, March 27, 2019 at 5:45 AM To: "Peters, Matt" >, Ghada Khalil >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I tried standard 0322 ISO image on 4 bare metals and “NUMA sections are still missing”. The docker images versions and build baseline have been attached. The ISO image link is following: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T174230Z/outputs/iso/ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Wednesday, March 27, 2019 10:38 AM To: 'Peters, Matt' >; Khalil, Ghada >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, Sorry for misleading! I mean “NUMA sections are still missing”. I have multiple systems experiencing this issue: 1. 0306 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 2. 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 3. 0305 ISO image on 4 bare metals 4. 0315 ISO image one 1 bare metals The item 1, 2 and 3 use same bare metals. The item 4 use a separate bare metal. I will try 0322 ISO image on 4 bare metals. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 26, 2019 11:10 PM To: Khalil, Ghada >; Xu, Chenjie >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Can you clarify this statement? “NUMA sections missing bug still exits”. Did you mean to say that the missing NUMA sections in the domain XML are now present, but you still can’t ping over the vhost port, or are you saying the NUMA sections are still missing? Do you have multiple systems that are experiencing this issue, or is it isolated to a single system that you are having problems with the NUMA topology? I believe you mentioned that you saw the same connectivity issues on a standard load from the mirror, so that still points to a test system / environment issue. As Ghada mentioned, I think the next steps are to get results from the sanity systems with the same load baseline and to test with your custom load on a system that has been proven to work on the standard load. -Matt From: Ghada Khalil > Date: Tuesday, March 26, 2019 at 9:28 AM To: "Xu, Chenjie" >, "Peters, Matt" >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Has Elio or Rich from the test team tried the new load as well on their systems? Do they see the same issues you reported? I think we need some data for another system to compare. Ada, As part of this thread, I also requested that a VM connectivity test be added to regular sanity so that there is data from the daily cengn builds w/o the new version of ovs-dpdk. Has the sanity suite been updated? Thanks, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 26, 2019 7:09 AM To: Peters, Matt; Martinez Monroy, Elio; Khalil, Ghada; Lin, Shuicheng; Cabrales, Ada; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I installed StarlingX using the new 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals. NUMA sections missing bug still exits: https://bugs.launchpad.net/starlingx/+bug/1820378 This time I update the docker images to latest before installing StarlingX. And the docker images versions and build baseline have been attached. Could you please help review the docker image versions? Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Friday, March 22, 2019 8:31 PM To: Xu, Chenjie >; Martinez Monroy, Elio >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Comparing the image list to our labs shows a difference in the image IDs (sha), but I’m not sure if that is just a difference in build baselines or an actual difference in the images. Since some of them align, I think you might be running a different set of images. Can you confirm what the build baseline is that you pulled the images from? I have attached a sample list from our labs for comparison. -Matt From: "Xu, Chenjie" > Date: Friday, March 22, 2019 at 7:25 AM To: "Peters, Matt" >, "Martinez Monroy, Elio" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, The docker image versions in my environment and helm-charts-manifest-no-tests.tgz has been attached. The helm-charts-manifest-no-tests.tgz is built by Shuicheng for the OVSDPDK Upgrade Testing ISO image. Best Regards, Xu, Chenjie From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Thursday, March 21, 2019 11:20 PM To: Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Perfect, I will be cheking my mail for that new ISO. Adding Richo , he is the one that is going to execute the tests. Thanks BR Elio From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, March 21, 2019 9:15 AM To: Lin, Shuicheng >; Cabrales, Ada >; Martinez Monroy, Elio > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, We discussed this in the networking bi-weekly team meeting today. Please re-enable the mlx pmd – re-apply the following patch: https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch Then please rebase to the latest master and build a new load for Ada’s team to start testing Hi Elio, One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 Thanks, Ghada From: Khalil, Ghada Sent: Thursday, March 21, 2019 9:12 AM To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. Can you confirm that the load being used has the mellanox pmd enabled in it? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 21, 2019 9:03 AM To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie for the testing. Hi all, Does it mean greenlight for code merge, or any other test is needed? Here is the patch list: https://review.openstack.org/642672 https://review.openstack.org/642673 Best Regards Shuicheng From: Xu, Chenjie Sent: Thursday, March 21, 2019 5:46 PM To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Peters at windriver.com Wed Mar 27 19:18:44 2019 From: Matt.Peters at windriver.com (Peters, Matt) Date: Wed, 27 Mar 2019 19:18:44 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <1466AF2176E6F040BD63860D0A241BBD46CA563A@FMSMSX109.amr.corp.intel.com> References: <151EE31B9FCCA54397A757BC674650F0BA4D1AA8@ALA-MBD.corp.ad.wrs.com> <72A55890-B007-4E93-A74A-291C725B158E@windriver.com> <1466AF2176E6F040BD63860D0A241BBD46CA563A@FMSMSX109.amr.corp.intel.com> Message-ID: <608E4D93-FDFF-4F00-A166-A89EA6683B90@windriver.com> Hello, From the output below, this data is taken from a virtual system. In a QEMU/KVM environment, it is not expected to have a NUMA topology unless it has been explicitly configured in the domain configuration of the emulated host. I’m assuming the tests being performed by Chenjie are in a HW lab. This can be confirmed by providing the same set of data for those test systems. Thanks, Matt From: "Martinez Monroy, Elio" Date: Wednesday, March 27, 2019 at 2:47 PM To: "Peters, Matt" , "Xu, Chenjie" , Ghada Khalil , "Lin, Shuicheng" , "Cabrales, Ada" , "Perez, Ricardo O" Cc: "'starlingx-discuss at lists.starlingx.io'" , "Zhao, Forrest" , Brent Rowsell Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt Just exercising same stuff, please check my outputs from compute-0, please let me know if something else is needed sudo /usr/sbin/dmdecode Password: sudo: /usr/sbin/dmdecode: command not found compute-0:~$ sudo /usr/sbin/dmidecode # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 10 structures occupying 419 bytes. Table at 0x000F6460. Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: SeaBIOS Version: Ubuntu-1.8.2-1ubuntu1 Release Date: 04/01/2014 Address: 0xE8000 Runtime Size: 96 kB ROM Size: 64 kB Characteristics: BIOS characteristics not supported Targeted content distribution is supported BIOS Revision: 0.0 Handle 0x0100, DMI type 1, 27 bytes System Information Manufacturer: QEMU Product Name: Standard PC (i440FX + PIIX, 1996) Version: pc-i440fx-2.5 Serial Number: Not Specified UUID: 71d54a5d-b569-4e1c-83e3-9babf169e824 Wake-up Type: Power Switch SKU Number: Not Specified Family: Not Specified Handle 0x0300, DMI type 3, 21 bytes Chassis Information Manufacturer: QEMU Type: Other Lock: Not Present Version: pc-i440fx-2.5 Serial Number: Not Specified Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: Unknown OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 Handle 0x0400, DMI type 4, 42 bytes Processor Information Socket Designation: CPU 0 Type: Central Processor Family: Other Manufacturer: QEMU ID: A3 06 01 00 FF FB 8B 07 Version: pc-i440fx-2.5 Voltage: Unknown External Clock: Unknown Max Speed: 2000 MHz Current Speed: 2000 MHz Status: Populated, Enabled Upgrade: Other L1 Cache Handle: Not Provided L2 Cache Handle: Not Provided L3 Cache Handle: Not Provided Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Core Count: 6 Core Enabled: 6 Thread Count: 1 Characteristics: None Handle 0x1000, DMI type 16, 23 bytes Physical Memory Array Location: Other Use: System Memory Error Correction Type: Multi-bit ECC Maximum Capacity: 10 GB Error Information Handle: Not Provided Number Of Devices: 1 Handle 0x1100, DMI type 17, 40 bytes Memory Device Array Handle: 0x1000 Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: 10240 MB Form Factor: DIMM Set: None Locator: DIMM 0 Bank Locator: Not Specified Type: RAM Type Detail: Other Speed: Unknown Manufacturer: QEMU Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Rank: Unknown Configured Clock Speed: Unknown Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x1300, DMI type 19, 31 bytes Memory Array Mapped Address Starting Address: 0x00000000000 Ending Address: 0x000BFFFFFFF Range Size: 3 GB Physical Array Handle: 0x1000 Partition Width: 1 Handle 0x1301, DMI type 19, 31 bytes Memory Array Mapped Address Starting Address: 0x00100000000 Ending Address: 0x002BFFFFFFF Range Size: 7 GB Physical Array Handle: 0x1000 Partition Width: 1 Handle 0x2000, DMI type 32, 11 bytes System Boot Information Status: No errors detected Handle 0x7F00, DMI type 127, 4 bytes End Of Table compute-0:~$ virsh nodeinfo CPU model: x86_64 CPU(s): 6 CPU frequency: 3792 MHz CPU socket(s): 1 Core(s) per socket: 6 Thread(s) per core: 1 NUMA cell(s): 1 Memory size: 10485236 KiB compute-0:~$ /usr/bin/topology TOPOLOGY: logical cpus : 6 sockets : 1 cores_per_pkg : 6 threads_per_core : 1 numa_nodes : 1 total_memory : 9.61 GiB memory_per_node : 10.00 GiB LOGICAL CPU TOPOLOGY: cpu_id : 0 1 2 3 4 5 socket_id : 0 0 0 0 0 0 core_id : 0 1 2 3 4 5 thread_id : 0 0 0 0 0 0 CORE TOPOLOGY: cpu_id socket_id core_id thread_id affinity 0 0 0 0 0x1 1 0 1 0 0x2 2 0 2 0 0x4 3 0 3 0 0x8 4 0 4 0 0x10 5 0 5 0 0x20 compute-0:~$ grep -i numa /var/log/dmesg [ 0.000000] No NUMA configuration found From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 27, 2019 6:10 AM To: Xu, Chenjie ; Khalil, Ghada ; Martinez Monroy, Elio ; Lin, Shuicheng ; Cabrales, Ada ; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io' ; Zhao, Forrest ; Rowsell, Brent Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Can you run the following set of commands on your test system compute hosts and provide the output for each? sudo /usr/sbin/dmidecode virsh nodeinfo /usr/bin/topology grep -i numa /var/log/dmesg From: "Xu, Chenjie" > Date: Wednesday, March 27, 2019 at 5:45 AM To: "Peters, Matt" >, Ghada Khalil >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I tried standard 0322 ISO image on 4 bare metals and “NUMA sections are still missing”. The docker images versions and build baseline have been attached. The ISO image link is following: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T174230Z/outputs/iso/ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Wednesday, March 27, 2019 10:38 AM To: 'Peters, Matt' >; Khalil, Ghada >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, Sorry for misleading! I mean “NUMA sections are still missing”. I have multiple systems experiencing this issue: 1. 0306 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 2. 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 3. 0305 ISO image on 4 bare metals 4. 0315 ISO image one 1 bare metals The item 1, 2 and 3 use same bare metals. The item 4 use a separate bare metal. I will try 0322 ISO image on 4 bare metals. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 26, 2019 11:10 PM To: Khalil, Ghada >; Xu, Chenjie >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Can you clarify this statement? “NUMA sections missing bug still exits”. Did you mean to say that the missing NUMA sections in the domain XML are now present, but you still can’t ping over the vhost port, or are you saying the NUMA sections are still missing? Do you have multiple systems that are experiencing this issue, or is it isolated to a single system that you are having problems with the NUMA topology? I believe you mentioned that you saw the same connectivity issues on a standard load from the mirror, so that still points to a test system / environment issue. As Ghada mentioned, I think the next steps are to get results from the sanity systems with the same load baseline and to test with your custom load on a system that has been proven to work on the standard load. -Matt From: Ghada Khalil > Date: Tuesday, March 26, 2019 at 9:28 AM To: "Xu, Chenjie" >, "Peters, Matt" >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Has Elio or Rich from the test team tried the new load as well on their systems? Do they see the same issues you reported? I think we need some data for another system to compare. Ada, As part of this thread, I also requested that a VM connectivity test be added to regular sanity so that there is data from the daily cengn builds w/o the new version of ovs-dpdk. Has the sanity suite been updated? Thanks, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 26, 2019 7:09 AM To: Peters, Matt; Martinez Monroy, Elio; Khalil, Ghada; Lin, Shuicheng; Cabrales, Ada; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I installed StarlingX using the new 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals. NUMA sections missing bug still exits: https://bugs.launchpad.net/starlingx/+bug/1820378 This time I update the docker images to latest before installing StarlingX. And the docker images versions and build baseline have been attached. Could you please help review the docker image versions? Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Friday, March 22, 2019 8:31 PM To: Xu, Chenjie >; Martinez Monroy, Elio >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Comparing the image list to our labs shows a difference in the image IDs (sha), but I’m not sure if that is just a difference in build baselines or an actual difference in the images. Since some of them align, I think you might be running a different set of images. Can you confirm what the build baseline is that you pulled the images from? I have attached a sample list from our labs for comparison. -Matt From: "Xu, Chenjie" > Date: Friday, March 22, 2019 at 7:25 AM To: "Peters, Matt" >, "Martinez Monroy, Elio" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, The docker image versions in my environment and helm-charts-manifest-no-tests.tgz has been attached. The helm-charts-manifest-no-tests.tgz is built by Shuicheng for the OVSDPDK Upgrade Testing ISO image. Best Regards, Xu, Chenjie From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Thursday, March 21, 2019 11:20 PM To: Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Perfect, I will be cheking my mail for that new ISO. Adding Richo , he is the one that is going to execute the tests. Thanks BR Elio From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, March 21, 2019 9:15 AM To: Lin, Shuicheng >; Cabrales, Ada >; Martinez Monroy, Elio > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, We discussed this in the networking bi-weekly team meeting today. Please re-enable the mlx pmd – re-apply the following patch: https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch Then please rebase to the latest master and build a new load for Ada’s team to start testing Hi Elio, One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 Thanks, Ghada From: Khalil, Ghada Sent: Thursday, March 21, 2019 9:12 AM To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. Can you confirm that the load being used has the mellanox pmd enabled in it? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 21, 2019 9:03 AM To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie for the testing. Hi all, Does it mean greenlight for code merge, or any other test is needed? Here is the patch list: https://review.openstack.org/642672 https://review.openstack.org/642673 Best Regards Shuicheng From: Xu, Chenjie Sent: Thursday, March 21, 2019 5:46 PM To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From elio.martinez.monroy at intel.com Wed Mar 27 19:35:43 2019 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Wed, 27 Mar 2019 19:35:43 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <608E4D93-FDFF-4F00-A166-A89EA6683B90@windriver.com> References: <151EE31B9FCCA54397A757BC674650F0BA4D1AA8@ALA-MBD.corp.ad.wrs.com> <72A55890-B007-4E93-A74A-291C725B158E@windriver.com> <1466AF2176E6F040BD63860D0A241BBD46CA563A@FMSMSX109.amr.corp.intel.com> <608E4D93-FDFF-4F00-A166-A89EA6683B90@windriver.com> Message-ID: <1466AF2176E6F040BD63860D0A241BBD46CA56BA@FMSMSX109.amr.corp.intel.com> So, in order to develop our NUMA test cases, we should configure that topology in our VM’s? How can we do it? Do you have the steps? BR Elio From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 27, 2019 1:19 PM To: Martinez Monroy, Elio ; Xu, Chenjie ; Khalil, Ghada ; Lin, Shuicheng ; Cabrales, Ada ; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io' ; Zhao, Forrest ; Rowsell, Brent Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello, From the output below, this data is taken from a virtual system. In a QEMU/KVM environment, it is not expected to have a NUMA topology unless it has been explicitly configured in the domain configuration of the emulated host. I’m assuming the tests being performed by Chenjie are in a HW lab. This can be confirmed by providing the same set of data for those test systems. Thanks, Matt From: "Martinez Monroy, Elio" > Date: Wednesday, March 27, 2019 at 2:47 PM To: "Peters, Matt" >, "Xu, Chenjie" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" >, Brent Rowsell > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt Just exercising same stuff, please check my outputs from compute-0, please let me know if something else is needed sudo /usr/sbin/dmdecode Password: sudo: /usr/sbin/dmdecode: command not found compute-0:~$ sudo /usr/sbin/dmidecode # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 10 structures occupying 419 bytes. Table at 0x000F6460. Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: SeaBIOS Version: Ubuntu-1.8.2-1ubuntu1 Release Date: 04/01/2014 Address: 0xE8000 Runtime Size: 96 kB ROM Size: 64 kB Characteristics: BIOS characteristics not supported Targeted content distribution is supported BIOS Revision: 0.0 Handle 0x0100, DMI type 1, 27 bytes System Information Manufacturer: QEMU Product Name: Standard PC (i440FX + PIIX, 1996) Version: pc-i440fx-2.5 Serial Number: Not Specified UUID: 71d54a5d-b569-4e1c-83e3-9babf169e824 Wake-up Type: Power Switch SKU Number: Not Specified Family: Not Specified Handle 0x0300, DMI type 3, 21 bytes Chassis Information Manufacturer: QEMU Type: Other Lock: Not Present Version: pc-i440fx-2.5 Serial Number: Not Specified Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: Unknown OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 Handle 0x0400, DMI type 4, 42 bytes Processor Information Socket Designation: CPU 0 Type: Central Processor Family: Other Manufacturer: QEMU ID: A3 06 01 00 FF FB 8B 07 Version: pc-i440fx-2.5 Voltage: Unknown External Clock: Unknown Max Speed: 2000 MHz Current Speed: 2000 MHz Status: Populated, Enabled Upgrade: Other L1 Cache Handle: Not Provided L2 Cache Handle: Not Provided L3 Cache Handle: Not Provided Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Core Count: 6 Core Enabled: 6 Thread Count: 1 Characteristics: None Handle 0x1000, DMI type 16, 23 bytes Physical Memory Array Location: Other Use: System Memory Error Correction Type: Multi-bit ECC Maximum Capacity: 10 GB Error Information Handle: Not Provided Number Of Devices: 1 Handle 0x1100, DMI type 17, 40 bytes Memory Device Array Handle: 0x1000 Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: 10240 MB Form Factor: DIMM Set: None Locator: DIMM 0 Bank Locator: Not Specified Type: RAM Type Detail: Other Speed: Unknown Manufacturer: QEMU Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Rank: Unknown Configured Clock Speed: Unknown Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x1300, DMI type 19, 31 bytes Memory Array Mapped Address Starting Address: 0x00000000000 Ending Address: 0x000BFFFFFFF Range Size: 3 GB Physical Array Handle: 0x1000 Partition Width: 1 Handle 0x1301, DMI type 19, 31 bytes Memory Array Mapped Address Starting Address: 0x00100000000 Ending Address: 0x002BFFFFFFF Range Size: 7 GB Physical Array Handle: 0x1000 Partition Width: 1 Handle 0x2000, DMI type 32, 11 bytes System Boot Information Status: No errors detected Handle 0x7F00, DMI type 127, 4 bytes End Of Table compute-0:~$ virsh nodeinfo CPU model: x86_64 CPU(s): 6 CPU frequency: 3792 MHz CPU socket(s): 1 Core(s) per socket: 6 Thread(s) per core: 1 NUMA cell(s): 1 Memory size: 10485236 KiB compute-0:~$ /usr/bin/topology TOPOLOGY: logical cpus : 6 sockets : 1 cores_per_pkg : 6 threads_per_core : 1 numa_nodes : 1 total_memory : 9.61 GiB memory_per_node : 10.00 GiB LOGICAL CPU TOPOLOGY: cpu_id : 0 1 2 3 4 5 socket_id : 0 0 0 0 0 0 core_id : 0 1 2 3 4 5 thread_id : 0 0 0 0 0 0 CORE TOPOLOGY: cpu_id socket_id core_id thread_id affinity 0 0 0 0 0x1 1 0 1 0 0x2 2 0 2 0 0x4 3 0 3 0 0x8 4 0 4 0 0x10 5 0 5 0 0x20 compute-0:~$ grep -i numa /var/log/dmesg [ 0.000000] No NUMA configuration found From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 27, 2019 6:10 AM To: Xu, Chenjie >; Khalil, Ghada >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Rowsell, Brent > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Can you run the following set of commands on your test system compute hosts and provide the output for each? sudo /usr/sbin/dmidecode virsh nodeinfo /usr/bin/topology grep -i numa /var/log/dmesg From: "Xu, Chenjie" > Date: Wednesday, March 27, 2019 at 5:45 AM To: "Peters, Matt" >, Ghada Khalil >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I tried standard 0322 ISO image on 4 bare metals and “NUMA sections are still missing”. The docker images versions and build baseline have been attached. The ISO image link is following: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T174230Z/outputs/iso/ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Wednesday, March 27, 2019 10:38 AM To: 'Peters, Matt' >; Khalil, Ghada >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, Sorry for misleading! I mean “NUMA sections are still missing”. I have multiple systems experiencing this issue: 1. 0306 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 2. 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 3. 0305 ISO image on 4 bare metals 4. 0315 ISO image one 1 bare metals The item 1, 2 and 3 use same bare metals. The item 4 use a separate bare metal. I will try 0322 ISO image on 4 bare metals. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 26, 2019 11:10 PM To: Khalil, Ghada >; Xu, Chenjie >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Can you clarify this statement? “NUMA sections missing bug still exits”. Did you mean to say that the missing NUMA sections in the domain XML are now present, but you still can’t ping over the vhost port, or are you saying the NUMA sections are still missing? Do you have multiple systems that are experiencing this issue, or is it isolated to a single system that you are having problems with the NUMA topology? I believe you mentioned that you saw the same connectivity issues on a standard load from the mirror, so that still points to a test system / environment issue. As Ghada mentioned, I think the next steps are to get results from the sanity systems with the same load baseline and to test with your custom load on a system that has been proven to work on the standard load. -Matt From: Ghada Khalil > Date: Tuesday, March 26, 2019 at 9:28 AM To: "Xu, Chenjie" >, "Peters, Matt" >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Has Elio or Rich from the test team tried the new load as well on their systems? Do they see the same issues you reported? I think we need some data for another system to compare. Ada, As part of this thread, I also requested that a VM connectivity test be added to regular sanity so that there is data from the daily cengn builds w/o the new version of ovs-dpdk. Has the sanity suite been updated? Thanks, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 26, 2019 7:09 AM To: Peters, Matt; Martinez Monroy, Elio; Khalil, Ghada; Lin, Shuicheng; Cabrales, Ada; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I installed StarlingX using the new 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals. NUMA sections missing bug still exits: https://bugs.launchpad.net/starlingx/+bug/1820378 This time I update the docker images to latest before installing StarlingX. And the docker images versions and build baseline have been attached. Could you please help review the docker image versions? Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Friday, March 22, 2019 8:31 PM To: Xu, Chenjie >; Martinez Monroy, Elio >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Comparing the image list to our labs shows a difference in the image IDs (sha), but I’m not sure if that is just a difference in build baselines or an actual difference in the images. Since some of them align, I think you might be running a different set of images. Can you confirm what the build baseline is that you pulled the images from? I have attached a sample list from our labs for comparison. -Matt From: "Xu, Chenjie" > Date: Friday, March 22, 2019 at 7:25 AM To: "Peters, Matt" >, "Martinez Monroy, Elio" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, The docker image versions in my environment and helm-charts-manifest-no-tests.tgz has been attached. The helm-charts-manifest-no-tests.tgz is built by Shuicheng for the OVSDPDK Upgrade Testing ISO image. Best Regards, Xu, Chenjie From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Thursday, March 21, 2019 11:20 PM To: Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Perfect, I will be cheking my mail for that new ISO. Adding Richo , he is the one that is going to execute the tests. Thanks BR Elio From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, March 21, 2019 9:15 AM To: Lin, Shuicheng >; Cabrales, Ada >; Martinez Monroy, Elio > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, We discussed this in the networking bi-weekly team meeting today. Please re-enable the mlx pmd – re-apply the following patch: https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch Then please rebase to the latest master and build a new load for Ada’s team to start testing Hi Elio, One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 Thanks, Ghada From: Khalil, Ghada Sent: Thursday, March 21, 2019 9:12 AM To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. Can you confirm that the load being used has the mellanox pmd enabled in it? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 21, 2019 9:03 AM To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie for the testing. Hi all, Does it mean greenlight for code merge, or any other test is needed? Here is the patch list: https://review.openstack.org/642672 https://review.openstack.org/642673 Best Regards Shuicheng From: Xu, Chenjie Sent: Thursday, March 21, 2019 5:46 PM To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Mar 28 19:13:02 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 28 Mar 2019 19:13:02 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <1466AF2176E6F040BD63860D0A241BBD46CA56BA@FMSMSX109.amr.corp.intel.com> References: <151EE31B9FCCA54397A757BC674650F0BA4D1AA8@ALA-MBD.corp.ad.wrs.com> <72A55890-B007-4E93-A74A-291C725B158E@windriver.com> <1466AF2176E6F040BD63860D0A241BBD46CA563A@FMSMSX109.amr.corp.intel.com> <608E4D93-FDFF-4F00-A166-A89EA6683B90@windriver.com> <1466AF2176E6F040BD63860D0A241BBD46CA56BA@FMSMSX109.amr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4D2C9E@ALA-MBD.corp.ad.wrs.com> Hi Elio, ovs-dpdk testing needs to be done on hardware. Virtual environments will be using ovs only moving forward. The code required to allow this was merged earlier today. More details will be sent shortly. https://review.openstack.org/#/c/633924/ Using OVS in a virtual env is required because master neutron doesn’t support ovs-dpdk in virtual environments. We have been carrying an stx specific patch to allow users to continue working on virtual env. But with the above code now merging, this patch will be discarded once the above feature is sufficiently tested. Hope this clarifies things. Thanks, Ghada From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Wednesday, March 27, 2019 3:36 PM To: Peters, Matt; Xu, Chenjie; Khalil, Ghada; Lin, Shuicheng; Cabrales, Ada; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Rowsell, Brent Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing So, in order to develop our NUMA test cases, we should configure that topology in our VM’s? How can we do it? Do you have the steps? BR Elio From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 27, 2019 1:19 PM To: Martinez Monroy, Elio >; Xu, Chenjie >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Rowsell, Brent > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello, From the output below, this data is taken from a virtual system. In a QEMU/KVM environment, it is not expected to have a NUMA topology unless it has been explicitly configured in the domain configuration of the emulated host. I’m assuming the tests being performed by Chenjie are in a HW lab. This can be confirmed by providing the same set of data for those test systems. Thanks, Matt From: "Martinez Monroy, Elio" > Date: Wednesday, March 27, 2019 at 2:47 PM To: "Peters, Matt" >, "Xu, Chenjie" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" >, Brent Rowsell > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt Just exercising same stuff, please check my outputs from compute-0, please let me know if something else is needed sudo /usr/sbin/dmdecode Password: sudo: /usr/sbin/dmdecode: command not found compute-0:~$ sudo /usr/sbin/dmidecode # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 10 structures occupying 419 bytes. Table at 0x000F6460. Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: SeaBIOS Version: Ubuntu-1.8.2-1ubuntu1 Release Date: 04/01/2014 Address: 0xE8000 Runtime Size: 96 kB ROM Size: 64 kB Characteristics: BIOS characteristics not supported Targeted content distribution is supported BIOS Revision: 0.0 Handle 0x0100, DMI type 1, 27 bytes System Information Manufacturer: QEMU Product Name: Standard PC (i440FX + PIIX, 1996) Version: pc-i440fx-2.5 Serial Number: Not Specified UUID: 71d54a5d-b569-4e1c-83e3-9babf169e824 Wake-up Type: Power Switch SKU Number: Not Specified Family: Not Specified Handle 0x0300, DMI type 3, 21 bytes Chassis Information Manufacturer: QEMU Type: Other Lock: Not Present Version: pc-i440fx-2.5 Serial Number: Not Specified Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: Unknown OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 Handle 0x0400, DMI type 4, 42 bytes Processor Information Socket Designation: CPU 0 Type: Central Processor Family: Other Manufacturer: QEMU ID: A3 06 01 00 FF FB 8B 07 Version: pc-i440fx-2.5 Voltage: Unknown External Clock: Unknown Max Speed: 2000 MHz Current Speed: 2000 MHz Status: Populated, Enabled Upgrade: Other L1 Cache Handle: Not Provided L2 Cache Handle: Not Provided L3 Cache Handle: Not Provided Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Core Count: 6 Core Enabled: 6 Thread Count: 1 Characteristics: None Handle 0x1000, DMI type 16, 23 bytes Physical Memory Array Location: Other Use: System Memory Error Correction Type: Multi-bit ECC Maximum Capacity: 10 GB Error Information Handle: Not Provided Number Of Devices: 1 Handle 0x1100, DMI type 17, 40 bytes Memory Device Array Handle: 0x1000 Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: 10240 MB Form Factor: DIMM Set: None Locator: DIMM 0 Bank Locator: Not Specified Type: RAM Type Detail: Other Speed: Unknown Manufacturer: QEMU Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Rank: Unknown Configured Clock Speed: Unknown Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x1300, DMI type 19, 31 bytes Memory Array Mapped Address Starting Address: 0x00000000000 Ending Address: 0x000BFFFFFFF Range Size: 3 GB Physical Array Handle: 0x1000 Partition Width: 1 Handle 0x1301, DMI type 19, 31 bytes Memory Array Mapped Address Starting Address: 0x00100000000 Ending Address: 0x002BFFFFFFF Range Size: 7 GB Physical Array Handle: 0x1000 Partition Width: 1 Handle 0x2000, DMI type 32, 11 bytes System Boot Information Status: No errors detected Handle 0x7F00, DMI type 127, 4 bytes End Of Table compute-0:~$ virsh nodeinfo CPU model: x86_64 CPU(s): 6 CPU frequency: 3792 MHz CPU socket(s): 1 Core(s) per socket: 6 Thread(s) per core: 1 NUMA cell(s): 1 Memory size: 10485236 KiB compute-0:~$ /usr/bin/topology TOPOLOGY: logical cpus : 6 sockets : 1 cores_per_pkg : 6 threads_per_core : 1 numa_nodes : 1 total_memory : 9.61 GiB memory_per_node : 10.00 GiB LOGICAL CPU TOPOLOGY: cpu_id : 0 1 2 3 4 5 socket_id : 0 0 0 0 0 0 core_id : 0 1 2 3 4 5 thread_id : 0 0 0 0 0 0 CORE TOPOLOGY: cpu_id socket_id core_id thread_id affinity 0 0 0 0 0x1 1 0 1 0 0x2 2 0 2 0 0x4 3 0 3 0 0x8 4 0 4 0 0x10 5 0 5 0 0x20 compute-0:~$ grep -i numa /var/log/dmesg [ 0.000000] No NUMA configuration found From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 27, 2019 6:10 AM To: Xu, Chenjie >; Khalil, Ghada >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Rowsell, Brent > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Can you run the following set of commands on your test system compute hosts and provide the output for each? sudo /usr/sbin/dmidecode virsh nodeinfo /usr/bin/topology grep -i numa /var/log/dmesg From: "Xu, Chenjie" > Date: Wednesday, March 27, 2019 at 5:45 AM To: "Peters, Matt" >, Ghada Khalil >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I tried standard 0322 ISO image on 4 bare metals and “NUMA sections are still missing”. The docker images versions and build baseline have been attached. The ISO image link is following: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T174230Z/outputs/iso/ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Wednesday, March 27, 2019 10:38 AM To: 'Peters, Matt' >; Khalil, Ghada >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, Sorry for misleading! I mean “NUMA sections are still missing”. I have multiple systems experiencing this issue: 1. 0306 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 2. 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 3. 0305 ISO image on 4 bare metals 4. 0315 ISO image one 1 bare metals The item 1, 2 and 3 use same bare metals. The item 4 use a separate bare metal. I will try 0322 ISO image on 4 bare metals. Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From chenjie.xu at intel.com Thu Mar 28 01:58:58 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Thu, 28 Mar 2019 01:58:58 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <1466AF2176E6F040BD63860D0A241BBD46CA56BA@FMSMSX109.amr.corp.intel.com> References: <151EE31B9FCCA54397A757BC674650F0BA4D1AA8@ALA-MBD.corp.ad.wrs.com> <72A55890-B007-4E93-A74A-291C725B158E@windriver.com> <1466AF2176E6F040BD63860D0A241BBD46CA563A@FMSMSX109.amr.corp.intel.com> <608E4D93-FDFF-4F00-A166-A89EA6683B90@windriver.com> <1466AF2176E6F040BD63860D0A241BBD46CA56BA@FMSMSX109.amr.corp.intel.com> Message-ID: Hi Matt, I run the following commands on compute-0. The outputs of commands have been attached. sudo /usr/sbin/dmidecode > dmidecode.txt virsh nodeinfo > nodeinfo.txt /usr/bin/topology > topology.txt grep -i numa /var/log/dmesg > dmesg.txt And the StarlingX is installed with standard 0322 ISO image: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T174230Z/outputs/iso/ Best Regards, Xu, Chenjie From: Martinez Monroy, Elio Sent: Thursday, March 28, 2019 3:36 AM To: Peters, Matt ; Xu, Chenjie ; Khalil, Ghada ; Lin, Shuicheng ; Cabrales, Ada ; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io' ; Zhao, Forrest ; Rowsell, Brent Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing So, in order to develop our NUMA test cases, we should configure that topology in our VM’s? How can we do it? Do you have the steps? BR Elio From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 27, 2019 1:19 PM To: Martinez Monroy, Elio >; Xu, Chenjie >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Rowsell, Brent > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello, From the output below, this data is taken from a virtual system. In a QEMU/KVM environment, it is not expected to have a NUMA topology unless it has been explicitly configured in the domain configuration of the emulated host. I’m assuming the tests being performed by Chenjie are in a HW lab. This can be confirmed by providing the same set of data for those test systems. Thanks, Matt From: "Martinez Monroy, Elio" > Date: Wednesday, March 27, 2019 at 2:47 PM To: "Peters, Matt" >, "Xu, Chenjie" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" >, Brent Rowsell > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt Just exercising same stuff, please check my outputs from compute-0, please let me know if something else is needed sudo /usr/sbin/dmdecode Password: sudo: /usr/sbin/dmdecode: command not found compute-0:~$ sudo /usr/sbin/dmidecode # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 10 structures occupying 419 bytes. Table at 0x000F6460. Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: SeaBIOS Version: Ubuntu-1.8.2-1ubuntu1 Release Date: 04/01/2014 Address: 0xE8000 Runtime Size: 96 kB ROM Size: 64 kB Characteristics: BIOS characteristics not supported Targeted content distribution is supported BIOS Revision: 0.0 Handle 0x0100, DMI type 1, 27 bytes System Information Manufacturer: QEMU Product Name: Standard PC (i440FX + PIIX, 1996) Version: pc-i440fx-2.5 Serial Number: Not Specified UUID: 71d54a5d-b569-4e1c-83e3-9babf169e824 Wake-up Type: Power Switch SKU Number: Not Specified Family: Not Specified Handle 0x0300, DMI type 3, 21 bytes Chassis Information Manufacturer: QEMU Type: Other Lock: Not Present Version: pc-i440fx-2.5 Serial Number: Not Specified Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: Unknown OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 Handle 0x0400, DMI type 4, 42 bytes Processor Information Socket Designation: CPU 0 Type: Central Processor Family: Other Manufacturer: QEMU ID: A3 06 01 00 FF FB 8B 07 Version: pc-i440fx-2.5 Voltage: Unknown External Clock: Unknown Max Speed: 2000 MHz Current Speed: 2000 MHz Status: Populated, Enabled Upgrade: Other L1 Cache Handle: Not Provided L2 Cache Handle: Not Provided L3 Cache Handle: Not Provided Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Core Count: 6 Core Enabled: 6 Thread Count: 1 Characteristics: None Handle 0x1000, DMI type 16, 23 bytes Physical Memory Array Location: Other Use: System Memory Error Correction Type: Multi-bit ECC Maximum Capacity: 10 GB Error Information Handle: Not Provided Number Of Devices: 1 Handle 0x1100, DMI type 17, 40 bytes Memory Device Array Handle: 0x1000 Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: 10240 MB Form Factor: DIMM Set: None Locator: DIMM 0 Bank Locator: Not Specified Type: RAM Type Detail: Other Speed: Unknown Manufacturer: QEMU Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Rank: Unknown Configured Clock Speed: Unknown Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x1300, DMI type 19, 31 bytes Memory Array Mapped Address Starting Address: 0x00000000000 Ending Address: 0x000BFFFFFFF Range Size: 3 GB Physical Array Handle: 0x1000 Partition Width: 1 Handle 0x1301, DMI type 19, 31 bytes Memory Array Mapped Address Starting Address: 0x00100000000 Ending Address: 0x002BFFFFFFF Range Size: 7 GB Physical Array Handle: 0x1000 Partition Width: 1 Handle 0x2000, DMI type 32, 11 bytes System Boot Information Status: No errors detected Handle 0x7F00, DMI type 127, 4 bytes End Of Table compute-0:~$ virsh nodeinfo CPU model: x86_64 CPU(s): 6 CPU frequency: 3792 MHz CPU socket(s): 1 Core(s) per socket: 6 Thread(s) per core: 1 NUMA cell(s): 1 Memory size: 10485236 KiB compute-0:~$ /usr/bin/topology TOPOLOGY: logical cpus : 6 sockets : 1 cores_per_pkg : 6 threads_per_core : 1 numa_nodes : 1 total_memory : 9.61 GiB memory_per_node : 10.00 GiB LOGICAL CPU TOPOLOGY: cpu_id : 0 1 2 3 4 5 socket_id : 0 0 0 0 0 0 core_id : 0 1 2 3 4 5 thread_id : 0 0 0 0 0 0 CORE TOPOLOGY: cpu_id socket_id core_id thread_id affinity 0 0 0 0 0x1 1 0 1 0 0x2 2 0 2 0 0x4 3 0 3 0 0x8 4 0 4 0 0x10 5 0 5 0 0x20 compute-0:~$ grep -i numa /var/log/dmesg [ 0.000000] No NUMA configuration found From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 27, 2019 6:10 AM To: Xu, Chenjie >; Khalil, Ghada >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Rowsell, Brent > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Can you run the following set of commands on your test system compute hosts and provide the output for each? sudo /usr/sbin/dmidecode virsh nodeinfo /usr/bin/topology grep -i numa /var/log/dmesg From: "Xu, Chenjie" > Date: Wednesday, March 27, 2019 at 5:45 AM To: "Peters, Matt" >, Ghada Khalil >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I tried standard 0322 ISO image on 4 bare metals and “NUMA sections are still missing”. The docker images versions and build baseline have been attached. The ISO image link is following: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T174230Z/outputs/iso/ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Wednesday, March 27, 2019 10:38 AM To: 'Peters, Matt' >; Khalil, Ghada >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, Sorry for misleading! I mean “NUMA sections are still missing”. I have multiple systems experiencing this issue: 1. 0306 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 2. 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 3. 0305 ISO image on 4 bare metals 4. 0315 ISO image one 1 bare metals The item 1, 2 and 3 use same bare metals. The item 4 use a separate bare metal. I will try 0322 ISO image on 4 bare metals. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 26, 2019 11:10 PM To: Khalil, Ghada >; Xu, Chenjie >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Can you clarify this statement? “NUMA sections missing bug still exits”. Did you mean to say that the missing NUMA sections in the domain XML are now present, but you still can’t ping over the vhost port, or are you saying the NUMA sections are still missing? Do you have multiple systems that are experiencing this issue, or is it isolated to a single system that you are having problems with the NUMA topology? I believe you mentioned that you saw the same connectivity issues on a standard load from the mirror, so that still points to a test system / environment issue. As Ghada mentioned, I think the next steps are to get results from the sanity systems with the same load baseline and to test with your custom load on a system that has been proven to work on the standard load. -Matt From: Ghada Khalil > Date: Tuesday, March 26, 2019 at 9:28 AM To: "Xu, Chenjie" >, "Peters, Matt" >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Has Elio or Rich from the test team tried the new load as well on their systems? Do they see the same issues you reported? I think we need some data for another system to compare. Ada, As part of this thread, I also requested that a VM connectivity test be added to regular sanity so that there is data from the daily cengn builds w/o the new version of ovs-dpdk. Has the sanity suite been updated? Thanks, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 26, 2019 7:09 AM To: Peters, Matt; Martinez Monroy, Elio; Khalil, Ghada; Lin, Shuicheng; Cabrales, Ada; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I installed StarlingX using the new 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals. NUMA sections missing bug still exits: https://bugs.launchpad.net/starlingx/+bug/1820378 This time I update the docker images to latest before installing StarlingX. And the docker images versions and build baseline have been attached. Could you please help review the docker image versions? Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Friday, March 22, 2019 8:31 PM To: Xu, Chenjie >; Martinez Monroy, Elio >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Comparing the image list to our labs shows a difference in the image IDs (sha), but I’m not sure if that is just a difference in build baselines or an actual difference in the images. Since some of them align, I think you might be running a different set of images. Can you confirm what the build baseline is that you pulled the images from? I have attached a sample list from our labs for comparison. -Matt From: "Xu, Chenjie" > Date: Friday, March 22, 2019 at 7:25 AM To: "Peters, Matt" >, "Martinez Monroy, Elio" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, The docker image versions in my environment and helm-charts-manifest-no-tests.tgz has been attached. The helm-charts-manifest-no-tests.tgz is built by Shuicheng for the OVSDPDK Upgrade Testing ISO image. Best Regards, Xu, Chenjie From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Thursday, March 21, 2019 11:20 PM To: Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Perfect, I will be cheking my mail for that new ISO. Adding Richo , he is the one that is going to execute the tests. Thanks BR Elio From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, March 21, 2019 9:15 AM To: Lin, Shuicheng >; Cabrales, Ada >; Martinez Monroy, Elio > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, We discussed this in the networking bi-weekly team meeting today. Please re-enable the mlx pmd – re-apply the following patch: https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch Then please rebase to the latest master and build a new load for Ada’s team to start testing Hi Elio, One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 Thanks, Ghada From: Khalil, Ghada Sent: Thursday, March 21, 2019 9:12 AM To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. Can you confirm that the load being used has the mellanox pmd enabled in it? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 21, 2019 9:03 AM To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie for the testing. Hi all, Does it mean greenlight for code merge, or any other test is needed? Here is the patch list: https://review.openstack.org/642672 https://review.openstack.org/642673 Best Regards Shuicheng From: Xu, Chenjie Sent: Thursday, March 21, 2019 5:46 PM To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: dmesg.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: dmidecode.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: nodeinfo.txt URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: topology.txt URL: From bruce.e.jones at intel.com Thu Mar 28 19:49:00 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 28 Mar 2019 19:49:00 +0000 Subject: [Starlingx-discuss] DRAFT release policy Message-ID: <9A85D2917C58154C960D95352B22818BD0709720@fmsmsx123.amr.corp.intel.com> We've been working on a draft release policy in the Release team. Please review and share your comments, feedback or suggestions in the etherpad or on this thread. The draft is located at https://etherpad.openstack.org/p/stx-release-policy-draft The current text is below. Brucej Release Policy =========== The StarlingX project determines release schedules based on when the release content is ready to be released. We should explicitly move away from the idea of time based releases. We should continue our current twice per year release cycle * We should consider changing our release naming convention to something that doesn't include dates. The Release team, together with the Test team TLs/PLs, shall make a recommendation to the community and TSC that a release is ready to go. Upon TSC approval, the release branches are tagged and the release documented. That recommendation should be based on: 1. Whether or not all anchor features in the release are complete, as per the input of the team(s) implementing the features and the results of Test team testing of the features ? Assumption: The TSC will create a list of approved features during the release planning process, and that some (or all) of these features will be identified by the TSC as "release gating" or "anchor" features that would block a release if not complete. ? Assumption: We are planning our releases at the PTG meetings every 6 months. 2. The results of formal Testing performed by the Test team, measured by the percentage of planned tests attempted and the test pass rate ? Proposal: 100% test cases attemped and 95% test cases passing in all configurations 3. The severity and number of bugs open against the release ? Proposal: No open Critical or High severity bugs against the release candidate. Or maybe 1-3 Highs if we have a clear resolution plan (and a plan to release a patch against the release?) ? See Bug Severity definitions below. We should discuss the option of doing a mid-cycle "bug fix" release against the latest release - allowing key defects to get fixed more rapidly. In such a case, the release team would make a recommendation to the TSC to approve the release plan and content. If approved by the TSC, the fixes shall be cherry-picked or merged into the release branch and a new build tested (and managed as per this policy). Bug Severity ========== Critical: The software does not operate as intended (e.g. the software fails to install, does not run, crashes, etc...). Or the issue is a Securty/CVE issue with a rating of Critical or High. In Launchpad this is "Fix as soon as possible" High: An important feature of the software does not operate as intended (e.g. live migration, fault reporting, etc...). Or the issue is a Security/CVE issue with a rating of Medium or lower. In Launchpad this is "Fix soon". Medium: A minor feature of the software does not operate as intended or there is an intermitant failure. In Launchpad this is "Fix when convienent or schedule to fix later". Low: A bug that does not impact normal operation of the software. In Launchpad this is "Fix when convienent". -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtroyer at gmail.com Thu Mar 28 20:02:51 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Thu, 28 Mar 2019 15:02:51 -0500 Subject: [Starlingx-discuss] What is the new openstack command to create an stack? In-Reply-To: References: <8557B550001AFB46A43A0CCC314BF85153CAF169@FMSMSX108.amr.corp.intel.com> <03D458D5BAFF6041973594B00B4E58CE5D68E6B4@CRSMSX104.amr.corp.intel.com> <8557B550001AFB46A43A0CCC314BF85153CAF1A9@FMSMSX108.amr.corp.intel.com> Message-ID: On Thu, Mar 28, 2019 at 1:30 PM Curtis wrote: > I'm guessing you are missing python-heatclient. Yup... >> From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] >> $openstack stack create --template ${stack_name} --parameter "NetID=${net_id}" >> openstack: 'stack create…’ is not an openstack command. This means that the plugin that implements the stack commands (python-heatclient) is not installed. dt -- Dean Troyer dtroyer at gmail.com From Jeff.Gowan at windriver.com Thu Mar 28 20:27:34 2019 From: Jeff.Gowan at windriver.com (Gowan, Jeff) Date: Thu, 28 Mar 2019 20:27:34 +0000 Subject: [Starlingx-discuss] Initial StarlingX survey - feedback needed Message-ID: Ildiko, Here are a couple of thoughts on the survey. Question 1 "Smary city" should be Smart city Can we add virtual RAN? Question 3 Can we add "colleague/associate" to capture word of mouth? Thanks, -Jeff On 3/28/19, 12:33 PM, "starlingx-discuss-request at lists.starlingx.io" 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: What is the new openstack command to create an stack? (Curtis) 2. Initial StarlingX survey - feedback needed (Ildiko Vancsa) 3. Re: OVS-DPDK Upgrade Testing (Martinez Monroy, Elio) ---------------------------------------------------------------------- Message: 1 Date: Thu, 28 Mar 2019 14:29:06 -0400 From: Curtis To: "Alonso, Juan Carlos" Cc: "Hernandez Gonzalez, Fernando" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] What is the new openstack command to create an stack? Message-ID: Content-Type: text/plain; charset="utf-8" On Thu, Mar 28, 2019 at 2:09 PM Alonso, Juan Carlos < juan.carlos.alonso at intel.com> wrote: > Hi Fernando, > > > > I have the same steps to test. The problem comes when execute “openstack > stack create” command. > > Seems that there was an update with such command. > > I figured out that the current OpenStack documentation shows that we are > using the correct command. Maybe we have a real issue. > > https://docs.openstack.org/heat/rocky/getting_started/create_a_stack.html > > Need to confirm. > I'm guessing you are missing python-heatclient. Thanks, Curtis > > > Regards. > > Juan Carlos Alonso > > > > *From:* Hernandez Gonzalez, Fernando > *Sent:* Thursday, March 28, 2019 11:28 AM > *To:* Alonso, Juan Carlos ; > starlingx-discuss at lists.starlingx.io > *Subject:* RE: [Starlingx-discuss] What is the new openstack command to > create an stack? > > > > Hi JC, > > > > I am almost finishing the “HEAT HOT template” Test cases (the basics)… please look at the next link , under “HEAT_HOT_Template_07”, you will see the prerequisites for creation of Nova Server instance and the required template. > > > > Regards, > > *Fernando Hernandez Gonzalez* > > *Software Engineer* > > > > Avenida del Bosque #1001 Col, El Bajío > > Zapopan, Jalisco MX, 45019 > > ____________________________________ > > *Office:* +52.33.16.45.01.34 inet 86450134 > > > > *From:* Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com > ] > *Sent:* Thursday, March 28, 2019 11:19 AM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] What is the new openstack command to > create an stack? > > > > Hi, > > > > Do someone know what is the new openstack command to create an stack? Then > to create an instance. > > > > I usually use: > > $openstack stack create --template ${stack_name} --parameter > "NetID=${net_id}" > > > > But got the below error: > > openstack: 'stack create…’ is not an openstack command. > > > > Regards. > > Juan Carlos Alonso > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 2 Date: Thu, 28 Mar 2019 19:37:44 +0100 From: Ildiko Vancsa To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Initial StarlingX survey - feedback needed Message-ID: <88772002-9A60-4741-8CDF-1BB2D44C6769 at gmail.com> Content-Type: text/plain; charset=utf-8 Hi StarlingX Community, As I reached out about this earlier a few of us started to draft a survey to learn about what people and companies are doing around edge and to see if they know about StarlingX and getting some initial feedback on what they are interested in. Please note that the idea is to get a high level view and find out about interest as opposed to going into deep details on deployment options, use cases or ways to contribute. In that sense the main objectives for the survey is to keep it short and simple and make it easy to fill out. You will see that the questions are mainly having options to select from as opposed to being free form, the option to specify custom answer is provided where applicable like the use cases one as we can’t list all the possible ones. We also added a question to give any feedback people might have for the community. The OpenStack Foundation will have access to the complete dataset and will provide the anonymized information to the community once it’s available. The survey is available here: https://www.surveymonkey.com/r/StarlingX Please read through the questions and reply back if you have comments or questions. Thanks and Best Regards, Ildikó ------------------------------ Message: 3 Date: Wed, 27 Mar 2019 18:47:13 +0000 From: "Martinez Monroy, Elio" To: "Peters, Matt" , "Xu, Chenjie" , "Khalil, Ghada" , "Lin, Shuicheng" , "Cabrales, Ada" , "Perez, Ricardo O" Cc: "'starlingx-discuss at lists.starlingx.io'" , "Zhao, Forrest" , "Rowsell, Brent" Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Message-ID: <1466AF2176E6F040BD63860D0A241BBD46CA563A at FMSMSX109.amr.corp.intel.com> Content-Type: text/plain; charset="utf-8" Hi Matt Just exercising same stuff, please check my outputs from compute-0, please let me know if something else is needed sudo /usr/sbin/dmdecode Password: sudo: /usr/sbin/dmdecode: command not found compute-0:~$ sudo /usr/sbin/dmidecode # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 10 structures occupying 419 bytes. Table at 0x000F6460. Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: SeaBIOS Version: Ubuntu-1.8.2-1ubuntu1 Release Date: 04/01/2014 Address: 0xE8000 Runtime Size: 96 kB ROM Size: 64 kB Characteristics: BIOS characteristics not supported Targeted content distribution is supported BIOS Revision: 0.0 Handle 0x0100, DMI type 1, 27 bytes System Information Manufacturer: QEMU Product Name: Standard PC (i440FX + PIIX, 1996) Version: pc-i440fx-2.5 Serial Number: Not Specified UUID: 71d54a5d-b569-4e1c-83e3-9babf169e824 Wake-up Type: Power Switch SKU Number: Not Specified Family: Not Specified Handle 0x0300, DMI type 3, 21 bytes Chassis Information Manufacturer: QEMU Type: Other Lock: Not Present Version: pc-i440fx-2.5 Serial Number: Not Specified Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: Unknown OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 Handle 0x0400, DMI type 4, 42 bytes Processor Information Socket Designation: CPU 0 Type: Central Processor Family: Other Manufacturer: QEMU ID: A3 06 01 00 FF FB 8B 07 Version: pc-i440fx-2.5 Voltage: Unknown External Clock: Unknown Max Speed: 2000 MHz Current Speed: 2000 MHz Status: Populated, Enabled Upgrade: Other L1 Cache Handle: Not Provided L2 Cache Handle: Not Provided L3 Cache Handle: Not Provided Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Core Count: 6 Core Enabled: 6 Thread Count: 1 Characteristics: None Handle 0x1000, DMI type 16, 23 bytes Physical Memory Array Location: Other Use: System Memory Error Correction Type: Multi-bit ECC Maximum Capacity: 10 GB Error Information Handle: Not Provided Number Of Devices: 1 Handle 0x1100, DMI type 17, 40 bytes Memory Device Array Handle: 0x1000 Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: 10240 MB Form Factor: DIMM Set: None Locator: DIMM 0 Bank Locator: Not Specified Type: RAM Type Detail: Other Speed: Unknown Manufacturer: QEMU Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Rank: Unknown Configured Clock Speed: Unknown Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x1300, DMI type 19, 31 bytes Memory Array Mapped Address Starting Address: 0x00000000000 Ending Address: 0x000BFFFFFFF Range Size: 3 GB Physical Array Handle: 0x1000 Partition Width: 1 Handle 0x1301, DMI type 19, 31 bytes Memory Array Mapped Address Starting Address: 0x00100000000 Ending Address: 0x002BFFFFFFF Range Size: 7 GB Physical Array Handle: 0x1000 Partition Width: 1 Handle 0x2000, DMI type 32, 11 bytes System Boot Information Status: No errors detected Handle 0x7F00, DMI type 127, 4 bytes End Of Table compute-0:~$ virsh nodeinfo CPU model: x86_64 CPU(s): 6 CPU frequency: 3792 MHz CPU socket(s): 1 Core(s) per socket: 6 Thread(s) per core: 1 NUMA cell(s): 1 Memory size: 10485236 KiB compute-0:~$ /usr/bin/topology TOPOLOGY: logical cpus : 6 sockets : 1 cores_per_pkg : 6 threads_per_core : 1 numa_nodes : 1 total_memory : 9.61 GiB memory_per_node : 10.00 GiB LOGICAL CPU TOPOLOGY: cpu_id : 0 1 2 3 4 5 socket_id : 0 0 0 0 0 0 core_id : 0 1 2 3 4 5 thread_id : 0 0 0 0 0 0 CORE TOPOLOGY: cpu_id socket_id core_id thread_id affinity 0 0 0 0 0x1 1 0 1 0 0x2 2 0 2 0 0x4 3 0 3 0 0x8 4 0 4 0 0x10 5 0 5 0 0x20 compute-0:~$ grep -i numa /var/log/dmesg [ 0.000000] No NUMA configuration found From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 27, 2019 6:10 AM To: Xu, Chenjie ; Khalil, Ghada ; Martinez Monroy, Elio ; Lin, Shuicheng ; Cabrales, Ada ; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io' ; Zhao, Forrest ; Rowsell, Brent Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Can you run the following set of commands on your test system compute hosts and provide the output for each? sudo /usr/sbin/dmidecode virsh nodeinfo /usr/bin/topology grep -i numa /var/log/dmesg From: "Xu, Chenjie" > Date: Wednesday, March 27, 2019 at 5:45 AM To: "Peters, Matt" >, Ghada Khalil >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I tried standard 0322 ISO image on 4 bare metals and “NUMA sections are still missing”. The docker images versions and build baseline have been attached. The ISO image link is following: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T174230Z/outputs/iso/ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Wednesday, March 27, 2019 10:38 AM To: 'Peters, Matt' >; Khalil, Ghada >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, Sorry for misleading! I mean “NUMA sections are still missing”. I have multiple systems experiencing this issue: 1. 0306 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 2. 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 3. 0305 ISO image on 4 bare metals 4. 0315 ISO image one 1 bare metals The item 1, 2 and 3 use same bare metals. The item 4 use a separate bare metal. I will try 0322 ISO image on 4 bare metals. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 26, 2019 11:10 PM To: Khalil, Ghada >; Xu, Chenjie >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Can you clarify this statement? “NUMA sections missing bug still exits”. Did you mean to say that the missing NUMA sections in the domain XML are now present, but you still can’t ping over the vhost port, or are you saying the NUMA sections are still missing? Do you have multiple systems that are experiencing this issue, or is it isolated to a single system that you are having problems with the NUMA topology? I believe you mentioned that you saw the same connectivity issues on a standard load from the mirror, so that still points to a test system / environment issue. As Ghada mentioned, I think the next steps are to get results from the sanity systems with the same load baseline and to test with your custom load on a system that has been proven to work on the standard load. -Matt From: Ghada Khalil > Date: Tuesday, March 26, 2019 at 9:28 AM To: "Xu, Chenjie" >, "Peters, Matt" >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Has Elio or Rich from the test team tried the new load as well on their systems? Do they see the same issues you reported? I think we need some data for another system to compare. Ada, As part of this thread, I also requested that a VM connectivity test be added to regular sanity so that there is data from the daily cengn builds w/o the new version of ovs-dpdk. Has the sanity suite been updated? Thanks, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 26, 2019 7:09 AM To: Peters, Matt; Martinez Monroy, Elio; Khalil, Ghada; Lin, Shuicheng; Cabrales, Ada; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I installed StarlingX using the new 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals. NUMA sections missing bug still exits: https://bugs.launchpad.net/starlingx/+bug/1820378 This time I update the docker images to latest before installing StarlingX. And the docker images versions and build baseline have been attached. Could you please help review the docker image versions? Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Friday, March 22, 2019 8:31 PM To: Xu, Chenjie >; Martinez Monroy, Elio >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Comparing the image list to our labs shows a difference in the image IDs (sha), but I’m not sure if that is just a difference in build baselines or an actual difference in the images. Since some of them align, I think you might be running a different set of images. Can you confirm what the build baseline is that you pulled the images from? I have attached a sample list from our labs for comparison. -Matt From: "Xu, Chenjie" > Date: Friday, March 22, 2019 at 7:25 AM To: "Peters, Matt" >, "Martinez Monroy, Elio" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, The docker image versions in my environment and helm-charts-manifest-no-tests.tgz has been attached. The helm-charts-manifest-no-tests.tgz is built by Shuicheng for the OVSDPDK Upgrade Testing ISO image. Best Regards, Xu, Chenjie From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Thursday, March 21, 2019 11:20 PM To: Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Perfect, I will be cheking my mail for that new ISO. Adding Richo , he is the one that is going to execute the tests. Thanks BR Elio From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, March 21, 2019 9:15 AM To: Lin, Shuicheng >; Cabrales, Ada >; Martinez Monroy, Elio > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, We discussed this in the networking bi-weekly team meeting today. Please re-enable the mlx pmd – re-apply the following patch: https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch Then please rebase to the latest master and build a new load for Ada’s team to start testing Hi Elio, One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 Thanks, Ghada From: Khalil, Ghada Sent: Thursday, March 21, 2019 9:12 AM To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. Can you confirm that the load being used has the mellanox pmd enabled in it? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 21, 2019 9:03 AM To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie for the testing. Hi all, Does it mean greenlight for code merge, or any other test is needed? Here is the patch list: https://review.openstack.org/642672 https://review.openstack.org/642673 Best Regards Shuicheng From: Xu, Chenjie Sent: Thursday, March 21, 2019 5:46 PM To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie -------------- 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 10, Issue 156 ************************************************** From ildiko.vancsa at gmail.com Thu Mar 28 20:32:58 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 28 Mar 2019 21:32:58 +0100 Subject: [Starlingx-discuss] Initial StarlingX survey - feedback needed In-Reply-To: References: Message-ID: <764976D5-E76F-47C5-A99E-6F59AC7D6401@gmail.com> Hi Jeff, Thanks for the comments and catching the typo. I like the word of mouth idea and also open to add the vRAN use case. I would not want to grow the list too big, but we can certainly add one or two more items that we see current. Thanks, Ildikó > On 2019. Mar 28., at 21:27, Gowan, Jeff wrote: > > Ildiko, > > Here are a couple of thoughts on the survey. > > Question 1 > "Smary city" should be Smart city > Can we add virtual RAN? > > Question 3 > Can we add "colleague/associate" to capture word of mouth? > > Thanks, > > -Jeff > > On 3/28/19, 12:33 PM, "starlingx-discuss-request at lists.starlingx.io" 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: What is the new openstack command to create an stack? (Curtis) > 2. Initial StarlingX survey - feedback needed (Ildiko Vancsa) > 3. Re: OVS-DPDK Upgrade Testing (Martinez Monroy, Elio) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 28 Mar 2019 14:29:06 -0400 > From: Curtis > To: "Alonso, Juan Carlos" > Cc: "Hernandez Gonzalez, Fernando" > , > "starlingx-discuss at lists.starlingx.io" > > Subject: Re: [Starlingx-discuss] What is the new openstack command to > create an stack? > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > On Thu, Mar 28, 2019 at 2:09 PM Alonso, Juan Carlos < > juan.carlos.alonso at intel.com> wrote: > >> Hi Fernando, >> >> >> >> I have the same steps to test. The problem comes when execute “openstack >> stack create” command. >> >> Seems that there was an update with such command. >> >> I figured out that the current OpenStack documentation shows that we are >> using the correct command. Maybe we have a real issue. >> >> https://docs.openstack.org/heat/rocky/getting_started/create_a_stack.html >> >> Need to confirm. >> > > I'm guessing you are missing python-heatclient. > > Thanks, > Curtis > > > >> >> >> Regards. >> >> Juan Carlos Alonso >> >> >> >> *From:* Hernandez Gonzalez, Fernando >> *Sent:* Thursday, March 28, 2019 11:28 AM >> *To:* Alonso, Juan Carlos ; >> starlingx-discuss at lists.starlingx.io >> *Subject:* RE: [Starlingx-discuss] What is the new openstack command to >> create an stack? >> >> >> >> Hi JC, >> >> >> >> I am almost finishing the “HEAT HOT template” Test cases (the basics)… please look at the next link , under “HEAT_HOT_Template_07”, you will see the prerequisites for creation of Nova Server instance and the required template. >> >> >> >> Regards, >> >> *Fernando Hernandez Gonzalez* >> >> *Software Engineer* >> >> >> >> Avenida del Bosque #1001 Col, El Bajío >> >> Zapopan, Jalisco MX, 45019 >> >> ____________________________________ >> >> *Office:* +52.33.16.45.01.34 inet 86450134 >> >> >> >> *From:* Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com >> ] >> *Sent:* Thursday, March 28, 2019 11:19 AM >> *To:* starlingx-discuss at lists.starlingx.io >> *Subject:* [Starlingx-discuss] What is the new openstack command to >> create an stack? >> >> >> >> Hi, >> >> >> >> Do someone know what is the new openstack command to create an stack? Then >> to create an instance. >> >> >> >> I usually use: >> >> $openstack stack create --template ${stack_name} --parameter >> "NetID=${net_id}" >> >> >> >> But got the below error: >> >> openstack: 'stack create…’ is not an openstack command. >> >> >> >> Regards. >> >> Juan Carlos Alonso >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > > -- > Blog: serverascode.com > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > ------------------------------ > > Message: 2 > Date: Thu, 28 Mar 2019 19:37:44 +0100 > From: Ildiko Vancsa > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Initial StarlingX survey - feedback > needed > Message-ID: <88772002-9A60-4741-8CDF-1BB2D44C6769 at gmail.com> > Content-Type: text/plain; charset=utf-8 > > Hi StarlingX Community, > > As I reached out about this earlier a few of us started to draft a survey to learn about what people and companies are doing around edge and to see if they know about StarlingX and getting some initial feedback on what they are interested in. > > Please note that the idea is to get a high level view and find out about interest as opposed to going into deep details on deployment options, use cases or ways to contribute. > > In that sense the main objectives for the survey is to keep it short and simple and make it easy to fill out. You will see that the questions are mainly having options to select from as opposed to being free form, the option to specify custom answer is provided where applicable like the use cases one as we can’t list all the possible ones. We also added a question to give any feedback people might have for the community. > > The OpenStack Foundation will have access to the complete dataset and will provide the anonymized information to the community once it’s available. > > The survey is available here: https://www.surveymonkey.com/r/StarlingX > > Please read through the questions and reply back if you have comments or questions. > > Thanks and Best Regards, > Ildikó > > > > > > ------------------------------ > > Message: 3 > Date: Wed, 27 Mar 2019 18:47:13 +0000 > From: "Martinez Monroy, Elio" > To: "Peters, Matt" , "Xu, Chenjie" > , "Khalil, Ghada" , > "Lin, Shuicheng" , "Cabrales, Ada" > , "Perez, Ricardo O" > > Cc: "'starlingx-discuss at lists.starlingx.io'" > , "Zhao, Forrest" > , "Rowsell, Brent" > > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing > Message-ID: > <1466AF2176E6F040BD63860D0A241BBD46CA563A at FMSMSX109.amr.corp.intel.com> > > Content-Type: text/plain; charset="utf-8" > > Hi Matt > > Just exercising same stuff, please check my outputs from compute-0, please let me know if something else is needed > > sudo /usr/sbin/dmdecode > Password: > sudo: /usr/sbin/dmdecode: command not found > compute-0:~$ sudo /usr/sbin/dmidecode > # dmidecode 3.1 > Getting SMBIOS data from sysfs. > SMBIOS 2.8 present. > 10 structures occupying 419 bytes. > Table at 0x000F6460. > > Handle 0x0000, DMI type 0, 24 bytes > BIOS Information > Vendor: SeaBIOS > Version: Ubuntu-1.8.2-1ubuntu1 > Release Date: 04/01/2014 > Address: 0xE8000 > Runtime Size: 96 kB > ROM Size: 64 kB > Characteristics: > BIOS characteristics not supported > Targeted content distribution is supported > BIOS Revision: 0.0 > > Handle 0x0100, DMI type 1, 27 bytes > System Information > Manufacturer: QEMU > Product Name: Standard PC (i440FX + PIIX, 1996) > Version: pc-i440fx-2.5 > Serial Number: Not Specified > UUID: 71d54a5d-b569-4e1c-83e3-9babf169e824 > Wake-up Type: Power Switch > SKU Number: Not Specified > Family: Not Specified > > Handle 0x0300, DMI type 3, 21 bytes > Chassis Information > Manufacturer: QEMU > Type: Other > Lock: Not Present > Version: pc-i440fx-2.5 > Serial Number: Not Specified > Asset Tag: Not Specified > Boot-up State: Safe > Power Supply State: Safe > Thermal State: Safe > Security Status: Unknown > OEM Information: 0x00000000 > Height: Unspecified > Number Of Power Cords: Unspecified > Contained Elements: 0 > > Handle 0x0400, DMI type 4, 42 bytes > Processor Information > Socket Designation: CPU 0 > Type: Central Processor > Family: Other > Manufacturer: QEMU > ID: A3 06 01 00 FF FB 8B 07 > Version: pc-i440fx-2.5 > Voltage: Unknown > External Clock: Unknown > Max Speed: 2000 MHz > Current Speed: 2000 MHz > Status: Populated, Enabled > Upgrade: Other > L1 Cache Handle: Not Provided > L2 Cache Handle: Not Provided > L3 Cache Handle: Not Provided > Serial Number: Not Specified > Asset Tag: Not Specified > Part Number: Not Specified > Core Count: 6 > Core Enabled: 6 > Thread Count: 1 > Characteristics: None > > Handle 0x1000, DMI type 16, 23 bytes > Physical Memory Array > Location: Other > Use: System Memory > Error Correction Type: Multi-bit ECC > Maximum Capacity: 10 GB > Error Information Handle: Not Provided > Number Of Devices: 1 > > Handle 0x1100, DMI type 17, 40 bytes > Memory Device > Array Handle: 0x1000 > Error Information Handle: Not Provided > Total Width: Unknown > Data Width: Unknown > Size: 10240 MB > Form Factor: DIMM > Set: None > Locator: DIMM 0 > Bank Locator: Not Specified > Type: RAM > Type Detail: Other > Speed: Unknown > Manufacturer: QEMU > Serial Number: Not Specified > Asset Tag: Not Specified > Part Number: Not Specified > Rank: Unknown > Configured Clock Speed: Unknown > Minimum Voltage: Unknown > Maximum Voltage: Unknown > Configured Voltage: Unknown > > Handle 0x1300, DMI type 19, 31 bytes > Memory Array Mapped Address > Starting Address: 0x00000000000 > Ending Address: 0x000BFFFFFFF > Range Size: 3 GB > Physical Array Handle: 0x1000 > Partition Width: 1 > > Handle 0x1301, DMI type 19, 31 bytes > Memory Array Mapped Address > Starting Address: 0x00100000000 > Ending Address: 0x002BFFFFFFF > Range Size: 7 GB > Physical Array Handle: 0x1000 > Partition Width: 1 > > Handle 0x2000, DMI type 32, 11 bytes > System Boot Information > Status: No errors detected > > Handle 0x7F00, DMI type 127, 4 bytes > End Of Table > > compute-0:~$ virsh nodeinfo > CPU model: x86_64 > CPU(s): 6 > CPU frequency: 3792 MHz > CPU socket(s): 1 > Core(s) per socket: 6 > Thread(s) per core: 1 > NUMA cell(s): 1 > Memory size: 10485236 KiB > > compute-0:~$ /usr/bin/topology > TOPOLOGY: > logical cpus : 6 > sockets : 1 > cores_per_pkg : 6 > threads_per_core : 1 > numa_nodes : 1 > total_memory : 9.61 GiB > memory_per_node : 10.00 GiB > > LOGICAL CPU TOPOLOGY: > cpu_id : 0 1 2 3 4 5 > socket_id : 0 0 0 0 0 0 > core_id : 0 1 2 3 4 5 > thread_id : 0 0 0 0 0 0 > > CORE TOPOLOGY: > cpu_id socket_id core_id thread_id affinity > 0 0 0 0 0x1 > 1 0 1 0 0x2 > 2 0 2 0 0x4 > 3 0 3 0 0x8 > 4 0 4 0 0x10 > 5 0 5 0 0x20 > compute-0:~$ grep -i numa /var/log/dmesg > [ 0.000000] No NUMA configuration found > > From: Peters, Matt [mailto:Matt.Peters at windriver.com] > Sent: Wednesday, March 27, 2019 6:10 AM > To: Xu, Chenjie ; Khalil, Ghada ; Martinez Monroy, Elio ; Lin, Shuicheng ; Cabrales, Ada ; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' ; Zhao, Forrest ; Rowsell, Brent > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Hello Chenjie, > Can you run the following set of commands on your test system compute hosts and provide the output for each? > > sudo /usr/sbin/dmidecode > virsh nodeinfo > /usr/bin/topology > grep -i numa /var/log/dmesg > > From: "Xu, Chenjie" > > Date: Wednesday, March 27, 2019 at 5:45 AM > To: "Peters, Matt" >, Ghada Khalil >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Hi Matt, > I tried standard 0322 ISO image on 4 bare metals and “NUMA sections are still missing”. The docker images versions and build baseline have been attached. The ISO image link is following: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T174230Z/outputs/iso/ > > Best Regards, > Xu, Chenjie > > From: Xu, Chenjie > Sent: Wednesday, March 27, 2019 10:38 AM > To: 'Peters, Matt' >; Khalil, Ghada >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Hi Matt, > Sorry for misleading! I mean “NUMA sections are still missing”. > > I have multiple systems experiencing this issue: > 1. 0306 ISO image for OVSDPDK Upgrade Testing on 4 bare metals > 2. 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals > 3. 0305 ISO image on 4 bare metals > 4. 0315 ISO image one 1 bare metals > The item 1, 2 and 3 use same bare metals. The item 4 use a separate bare metal. > > I will try 0322 ISO image on 4 bare metals. > > Best Regards, > Xu, Chenjie > > From: Peters, Matt [mailto:Matt.Peters at windriver.com] > Sent: Tuesday, March 26, 2019 11:10 PM > To: Khalil, Ghada >; Xu, Chenjie >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Hello Chenjie, > Can you clarify this statement? “NUMA sections missing bug still exits”. > Did you mean to say that the missing NUMA sections in the domain XML are now present, but you still can’t ping over the vhost port, or are you saying the NUMA sections are still missing? > > Do you have multiple systems that are experiencing this issue, or is it isolated to a single system that you are having problems with the NUMA topology? I believe you mentioned that you saw the same connectivity issues on a standard load from the mirror, so that still points to a test system / environment issue. > > As Ghada mentioned, I think the next steps are to get results from the sanity systems with the same load baseline and to test with your custom load on a system that has been proven to work on the standard load. > > -Matt > > From: Ghada Khalil > > Date: Tuesday, March 26, 2019 at 9:28 AM > To: "Xu, Chenjie" >, "Peters, Matt" >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Has Elio or Rich from the test team tried the new load as well on their systems? Do they see the same issues you reported? I think we need some data for another system to compare. > > Ada, > As part of this thread, I also requested that a VM connectivity test be added to regular sanity so that there is data from the daily cengn builds w/o the new version of ovs-dpdk. Has the sanity suite been updated? > > Thanks, > Ghada > > From: Xu, Chenjie [mailto:chenjie.xu at intel.com] > Sent: Tuesday, March 26, 2019 7:09 AM > To: Peters, Matt; Martinez Monroy, Elio; Khalil, Ghada; Lin, Shuicheng; Cabrales, Ada; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Hi Matt, > I installed StarlingX using the new 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals. NUMA sections missing bug still exits: > https://bugs.launchpad.net/starlingx/+bug/1820378 > > This time I update the docker images to latest before installing StarlingX. And the docker images versions and build baseline have been attached. Could you please help review the docker image versions? > > Best Regards, > Xu, Chenjie > > From: Peters, Matt [mailto:Matt.Peters at windriver.com] > Sent: Friday, March 22, 2019 8:31 PM > To: Xu, Chenjie >; Martinez Monroy, Elio >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Hello Chenjie, > Comparing the image list to our labs shows a difference in the image IDs (sha), but I’m not sure if that is just a difference in build baselines or an actual difference in the images. Since some of them align, I think you might be running a different set of images. Can you confirm what the build baseline is that you pulled the images from? > > I have attached a sample list from our labs for comparison. > > -Matt > > From: "Xu, Chenjie" > > Date: Friday, March 22, 2019 at 7:25 AM > To: "Peters, Matt" >, "Martinez Monroy, Elio" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Hi Matt, > The docker image versions in my environment and helm-charts-manifest-no-tests.tgz has been attached. The helm-charts-manifest-no-tests.tgz is built by Shuicheng for the OVSDPDK Upgrade Testing ISO image. > > Best Regards, > Xu, Chenjie > > From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] > Sent: Thursday, March 21, 2019 11:20 PM > To: Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Perfect, I will be cheking my mail for that new ISO. > > Adding Richo , he is the one that is going to execute the tests. > > Thanks > > BR > > Elio > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Thursday, March 21, 2019 9:15 AM > To: Lin, Shuicheng >; Cabrales, Ada >; Martinez Monroy, Elio > > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Hi Shuicheng, > We discussed this in the networking bi-weekly team meeting today. > > Please re-enable the mlx pmd – re-apply the following patch: > https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch > > Then please rebase to the latest master and build a new load for Ada’s team to start testing > > Hi Elio, > One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. > > Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: > https://bugs.launchpad.net/starlingx/+bug/1821150 > https://bugs.launchpad.net/starlingx/+bug/1821135 > https://bugs.launchpad.net/starlingx/+bug/1820378 > > Thanks, > Ghada > > From: Khalil, Ghada > Sent: Thursday, March 21, 2019 9:12 AM > To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Hi Shuicheng, > There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. > > Can you confirm that the load being used has the mellanox pmd enabled in it? > > Thanks, > Ghada > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > Sent: Thursday, March 21, 2019 9:03 AM > To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Thanks Chenjie for the testing. > > Hi all, > Does it mean greenlight for code merge, or any other test is needed? > Here is the patch list: > https://review.openstack.org/642672 > https://review.openstack.org/642673 > > > Best Regards > Shuicheng > > From: Xu, Chenjie > Sent: Thursday, March 21, 2019 5:46 PM > To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Hi team, > I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: > > Bug Summary: > No bug related to OVSDPDK Upgrade. > 3 bugs related to cutting over to container and configuration. > https://bugs.launchpad.net/starlingx/+bug/1821150 > https://bugs.launchpad.net/starlingx/+bug/1821135 > https://bugs.launchpad.net/starlingx/+bug/1820378 > > The following features have been tested: > N/S traffic for FLAT/VLAN network > E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) > QOS > Security Group > MTU > > Best Regards, > Xu, Chenjie > > > -------------- 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 10, Issue 156 > ************************************************** > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Jeff.Gowan at windriver.com Thu Mar 28 20:37:38 2019 From: Jeff.Gowan at windriver.com (Gowan, Jeff) Date: Thu, 28 Mar 2019 20:37:38 +0000 Subject: [Starlingx-discuss] Initial StarlingX survey - feedback needed In-Reply-To: <764976D5-E76F-47C5-A99E-6F59AC7D6401@gmail.com> References: <764976D5-E76F-47C5-A99E-6F59AC7D6401@gmail.com> Message-ID: <93EB76DD-D95A-4944-9036-1F63E24E0F34@windriver.com> Ildiko On the use case we may just want to go with the 6 high-level use cases we've identified (vRAN, MEC, vCPE, Transportation, Industrial, Healthcare) in order to test those assumptions, then include a 7th other category. -Jeff On 3/28/19, 1:33 PM, "Ildiko Vancsa" wrote: Hi Jeff, Thanks for the comments and catching the typo. I like the word of mouth idea and also open to add the vRAN use case. I would not want to grow the list too big, but we can certainly add one or two more items that we see current. Thanks, Ildikó > On 2019. Mar 28., at 21:27, Gowan, Jeff wrote: > > Ildiko, > > Here are a couple of thoughts on the survey. > > Question 1 > "Smary city" should be Smart city > Can we add virtual RAN? > > Question 3 > Can we add "colleague/associate" to capture word of mouth? > > Thanks, > > -Jeff > > On 3/28/19, 12:33 PM, "starlingx-discuss-request at lists.starlingx.io" 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: What is the new openstack command to create an stack? (Curtis) > 2. Initial StarlingX survey - feedback needed (Ildiko Vancsa) > 3. Re: OVS-DPDK Upgrade Testing (Martinez Monroy, Elio) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 28 Mar 2019 14:29:06 -0400 > From: Curtis > To: "Alonso, Juan Carlos" > Cc: "Hernandez Gonzalez, Fernando" > , > "starlingx-discuss at lists.starlingx.io" > > Subject: Re: [Starlingx-discuss] What is the new openstack command to > create an stack? > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > On Thu, Mar 28, 2019 at 2:09 PM Alonso, Juan Carlos < > juan.carlos.alonso at intel.com> wrote: > >> Hi Fernando, >> >> >> >> I have the same steps to test. The problem comes when execute “openstack >> stack create” command. >> >> Seems that there was an update with such command. >> >> I figured out that the current OpenStack documentation shows that we are >> using the correct command. Maybe we have a real issue. >> >> https://docs.openstack.org/heat/rocky/getting_started/create_a_stack.html >> >> Need to confirm. >> > > I'm guessing you are missing python-heatclient. > > Thanks, > Curtis > > > >> >> >> Regards. >> >> Juan Carlos Alonso >> >> >> >> *From:* Hernandez Gonzalez, Fernando >> *Sent:* Thursday, March 28, 2019 11:28 AM >> *To:* Alonso, Juan Carlos ; >> starlingx-discuss at lists.starlingx.io >> *Subject:* RE: [Starlingx-discuss] What is the new openstack command to >> create an stack? >> >> >> >> Hi JC, >> >> >> >> I am almost finishing the “HEAT HOT template” Test cases (the basics)… please look at the next link , under “HEAT_HOT_Template_07”, you will see the prerequisites for creation of Nova Server instance and the required template. >> >> >> >> Regards, >> >> *Fernando Hernandez Gonzalez* >> >> *Software Engineer* >> >> >> >> Avenida del Bosque #1001 Col, El Bajío >> >> Zapopan, Jalisco MX, 45019 >> >> ____________________________________ >> >> *Office:* +52.33.16.45.01.34 inet 86450134 >> >> >> >> *From:* Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com >> ] >> *Sent:* Thursday, March 28, 2019 11:19 AM >> *To:* starlingx-discuss at lists.starlingx.io >> *Subject:* [Starlingx-discuss] What is the new openstack command to >> create an stack? >> >> >> >> Hi, >> >> >> >> Do someone know what is the new openstack command to create an stack? Then >> to create an instance. >> >> >> >> I usually use: >> >> $openstack stack create --template ${stack_name} --parameter >> "NetID=${net_id}" >> >> >> >> But got the below error: >> >> openstack: 'stack create…’ is not an openstack command. >> >> >> >> Regards. >> >> Juan Carlos Alonso >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > > -- > Blog: serverascode.com > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > ------------------------------ > > Message: 2 > Date: Thu, 28 Mar 2019 19:37:44 +0100 > From: Ildiko Vancsa > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Initial StarlingX survey - feedback > needed > Message-ID: <88772002-9A60-4741-8CDF-1BB2D44C6769 at gmail.com> > Content-Type: text/plain; charset=utf-8 > > Hi StarlingX Community, > > As I reached out about this earlier a few of us started to draft a survey to learn about what people and companies are doing around edge and to see if they know about StarlingX and getting some initial feedback on what they are interested in. > > Please note that the idea is to get a high level view and find out about interest as opposed to going into deep details on deployment options, use cases or ways to contribute. > > In that sense the main objectives for the survey is to keep it short and simple and make it easy to fill out. You will see that the questions are mainly having options to select from as opposed to being free form, the option to specify custom answer is provided where applicable like the use cases one as we can’t list all the possible ones. We also added a question to give any feedback people might have for the community. > > The OpenStack Foundation will have access to the complete dataset and will provide the anonymized information to the community once it’s available. > > The survey is available here: https://www.surveymonkey.com/r/StarlingX > > Please read through the questions and reply back if you have comments or questions. > > Thanks and Best Regards, > Ildikó > > > > > > ------------------------------ > > Message: 3 > Date: Wed, 27 Mar 2019 18:47:13 +0000 > From: "Martinez Monroy, Elio" > To: "Peters, Matt" , "Xu, Chenjie" > , "Khalil, Ghada" , > "Lin, Shuicheng" , "Cabrales, Ada" > , "Perez, Ricardo O" > > Cc: "'starlingx-discuss at lists.starlingx.io'" > , "Zhao, Forrest" > , "Rowsell, Brent" > > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing > Message-ID: > <1466AF2176E6F040BD63860D0A241BBD46CA563A at FMSMSX109.amr.corp.intel.com> > > Content-Type: text/plain; charset="utf-8" > > Hi Matt > > Just exercising same stuff, please check my outputs from compute-0, please let me know if something else is needed > > sudo /usr/sbin/dmdecode > Password: > sudo: /usr/sbin/dmdecode: command not found > compute-0:~$ sudo /usr/sbin/dmidecode > # dmidecode 3.1 > Getting SMBIOS data from sysfs. > SMBIOS 2.8 present. > 10 structures occupying 419 bytes. > Table at 0x000F6460. > > Handle 0x0000, DMI type 0, 24 bytes > BIOS Information > Vendor: SeaBIOS > Version: Ubuntu-1.8.2-1ubuntu1 > Release Date: 04/01/2014 > Address: 0xE8000 > Runtime Size: 96 kB > ROM Size: 64 kB > Characteristics: > BIOS characteristics not supported > Targeted content distribution is supported > BIOS Revision: 0.0 > > Handle 0x0100, DMI type 1, 27 bytes > System Information > Manufacturer: QEMU > Product Name: Standard PC (i440FX + PIIX, 1996) > Version: pc-i440fx-2.5 > Serial Number: Not Specified > UUID: 71d54a5d-b569-4e1c-83e3-9babf169e824 > Wake-up Type: Power Switch > SKU Number: Not Specified > Family: Not Specified > > Handle 0x0300, DMI type 3, 21 bytes > Chassis Information > Manufacturer: QEMU > Type: Other > Lock: Not Present > Version: pc-i440fx-2.5 > Serial Number: Not Specified > Asset Tag: Not Specified > Boot-up State: Safe > Power Supply State: Safe > Thermal State: Safe > Security Status: Unknown > OEM Information: 0x00000000 > Height: Unspecified > Number Of Power Cords: Unspecified > Contained Elements: 0 > > Handle 0x0400, DMI type 4, 42 bytes > Processor Information > Socket Designation: CPU 0 > Type: Central Processor > Family: Other > Manufacturer: QEMU > ID: A3 06 01 00 FF FB 8B 07 > Version: pc-i440fx-2.5 > Voltage: Unknown > External Clock: Unknown > Max Speed: 2000 MHz > Current Speed: 2000 MHz > Status: Populated, Enabled > Upgrade: Other > L1 Cache Handle: Not Provided > L2 Cache Handle: Not Provided > L3 Cache Handle: Not Provided > Serial Number: Not Specified > Asset Tag: Not Specified > Part Number: Not Specified > Core Count: 6 > Core Enabled: 6 > Thread Count: 1 > Characteristics: None > > Handle 0x1000, DMI type 16, 23 bytes > Physical Memory Array > Location: Other > Use: System Memory > Error Correction Type: Multi-bit ECC > Maximum Capacity: 10 GB > Error Information Handle: Not Provided > Number Of Devices: 1 > > Handle 0x1100, DMI type 17, 40 bytes > Memory Device > Array Handle: 0x1000 > Error Information Handle: Not Provided > Total Width: Unknown > Data Width: Unknown > Size: 10240 MB > Form Factor: DIMM > Set: None > Locator: DIMM 0 > Bank Locator: Not Specified > Type: RAM > Type Detail: Other > Speed: Unknown > Manufacturer: QEMU > Serial Number: Not Specified > Asset Tag: Not Specified > Part Number: Not Specified > Rank: Unknown > Configured Clock Speed: Unknown > Minimum Voltage: Unknown > Maximum Voltage: Unknown > Configured Voltage: Unknown > > Handle 0x1300, DMI type 19, 31 bytes > Memory Array Mapped Address > Starting Address: 0x00000000000 > Ending Address: 0x000BFFFFFFF > Range Size: 3 GB > Physical Array Handle: 0x1000 > Partition Width: 1 > > Handle 0x1301, DMI type 19, 31 bytes > Memory Array Mapped Address > Starting Address: 0x00100000000 > Ending Address: 0x002BFFFFFFF > Range Size: 7 GB > Physical Array Handle: 0x1000 > Partition Width: 1 > > Handle 0x2000, DMI type 32, 11 bytes > System Boot Information > Status: No errors detected > > Handle 0x7F00, DMI type 127, 4 bytes > End Of Table > > compute-0:~$ virsh nodeinfo > CPU model: x86_64 > CPU(s): 6 > CPU frequency: 3792 MHz > CPU socket(s): 1 > Core(s) per socket: 6 > Thread(s) per core: 1 > NUMA cell(s): 1 > Memory size: 10485236 KiB > > compute-0:~$ /usr/bin/topology > TOPOLOGY: > logical cpus : 6 > sockets : 1 > cores_per_pkg : 6 > threads_per_core : 1 > numa_nodes : 1 > total_memory : 9.61 GiB > memory_per_node : 10.00 GiB > > LOGICAL CPU TOPOLOGY: > cpu_id : 0 1 2 3 4 5 > socket_id : 0 0 0 0 0 0 > core_id : 0 1 2 3 4 5 > thread_id : 0 0 0 0 0 0 > > CORE TOPOLOGY: > cpu_id socket_id core_id thread_id affinity > 0 0 0 0 0x1 > 1 0 1 0 0x2 > 2 0 2 0 0x4 > 3 0 3 0 0x8 > 4 0 4 0 0x10 > 5 0 5 0 0x20 > compute-0:~$ grep -i numa /var/log/dmesg > [ 0.000000] No NUMA configuration found > > From: Peters, Matt [mailto:Matt.Peters at windriver.com] > Sent: Wednesday, March 27, 2019 6:10 AM > To: Xu, Chenjie ; Khalil, Ghada ; Martinez Monroy, Elio ; Lin, Shuicheng ; Cabrales, Ada ; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' ; Zhao, Forrest ; Rowsell, Brent > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Hello Chenjie, > Can you run the following set of commands on your test system compute hosts and provide the output for each? > > sudo /usr/sbin/dmidecode > virsh nodeinfo > /usr/bin/topology > grep -i numa /var/log/dmesg > > From: "Xu, Chenjie" > > Date: Wednesday, March 27, 2019 at 5:45 AM > To: "Peters, Matt" >, Ghada Khalil >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Hi Matt, > I tried standard 0322 ISO image on 4 bare metals and “NUMA sections are still missing”. The docker images versions and build baseline have been attached. The ISO image link is following: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T174230Z/outputs/iso/ > > Best Regards, > Xu, Chenjie > > From: Xu, Chenjie > Sent: Wednesday, March 27, 2019 10:38 AM > To: 'Peters, Matt' >; Khalil, Ghada >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Hi Matt, > Sorry for misleading! I mean “NUMA sections are still missing”. > > I have multiple systems experiencing this issue: > 1. 0306 ISO image for OVSDPDK Upgrade Testing on 4 bare metals > 2. 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals > 3. 0305 ISO image on 4 bare metals > 4. 0315 ISO image one 1 bare metals > The item 1, 2 and 3 use same bare metals. The item 4 use a separate bare metal. > > I will try 0322 ISO image on 4 bare metals. > > Best Regards, > Xu, Chenjie > > From: Peters, Matt [mailto:Matt.Peters at windriver.com] > Sent: Tuesday, March 26, 2019 11:10 PM > To: Khalil, Ghada >; Xu, Chenjie >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Hello Chenjie, > Can you clarify this statement? “NUMA sections missing bug still exits”. > Did you mean to say that the missing NUMA sections in the domain XML are now present, but you still can’t ping over the vhost port, or are you saying the NUMA sections are still missing? > > Do you have multiple systems that are experiencing this issue, or is it isolated to a single system that you are having problems with the NUMA topology? I believe you mentioned that you saw the same connectivity issues on a standard load from the mirror, so that still points to a test system / environment issue. > > As Ghada mentioned, I think the next steps are to get results from the sanity systems with the same load baseline and to test with your custom load on a system that has been proven to work on the standard load. > > -Matt > > From: Ghada Khalil > > Date: Tuesday, March 26, 2019 at 9:28 AM > To: "Xu, Chenjie" >, "Peters, Matt" >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Has Elio or Rich from the test team tried the new load as well on their systems? Do they see the same issues you reported? I think we need some data for another system to compare. > > Ada, > As part of this thread, I also requested that a VM connectivity test be added to regular sanity so that there is data from the daily cengn builds w/o the new version of ovs-dpdk. Has the sanity suite been updated? > > Thanks, > Ghada > > From: Xu, Chenjie [mailto:chenjie.xu at intel.com] > Sent: Tuesday, March 26, 2019 7:09 AM > To: Peters, Matt; Martinez Monroy, Elio; Khalil, Ghada; Lin, Shuicheng; Cabrales, Ada; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Hi Matt, > I installed StarlingX using the new 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals. NUMA sections missing bug still exits: > https://bugs.launchpad.net/starlingx/+bug/1820378 > > This time I update the docker images to latest before installing StarlingX. And the docker images versions and build baseline have been attached. Could you please help review the docker image versions? > > Best Regards, > Xu, Chenjie > > From: Peters, Matt [mailto:Matt.Peters at windriver.com] > Sent: Friday, March 22, 2019 8:31 PM > To: Xu, Chenjie >; Martinez Monroy, Elio >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Hello Chenjie, > Comparing the image list to our labs shows a difference in the image IDs (sha), but I’m not sure if that is just a difference in build baselines or an actual difference in the images. Since some of them align, I think you might be running a different set of images. Can you confirm what the build baseline is that you pulled the images from? > > I have attached a sample list from our labs for comparison. > > -Matt > > From: "Xu, Chenjie" > > Date: Friday, March 22, 2019 at 7:25 AM > To: "Peters, Matt" >, "Martinez Monroy, Elio" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Hi Matt, > The docker image versions in my environment and helm-charts-manifest-no-tests.tgz has been attached. The helm-charts-manifest-no-tests.tgz is built by Shuicheng for the OVSDPDK Upgrade Testing ISO image. > > Best Regards, > Xu, Chenjie > > From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] > Sent: Thursday, March 21, 2019 11:20 PM > To: Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Perfect, I will be cheking my mail for that new ISO. > > Adding Richo , he is the one that is going to execute the tests. > > Thanks > > BR > > Elio > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Thursday, March 21, 2019 9:15 AM > To: Lin, Shuicheng >; Cabrales, Ada >; Martinez Monroy, Elio > > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Hi Shuicheng, > We discussed this in the networking bi-weekly team meeting today. > > Please re-enable the mlx pmd – re-apply the following patch: > https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch > > Then please rebase to the latest master and build a new load for Ada’s team to start testing > > Hi Elio, > One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. > > Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: > https://bugs.launchpad.net/starlingx/+bug/1821150 > https://bugs.launchpad.net/starlingx/+bug/1821135 > https://bugs.launchpad.net/starlingx/+bug/1820378 > > Thanks, > Ghada > > From: Khalil, Ghada > Sent: Thursday, March 21, 2019 9:12 AM > To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Hi Shuicheng, > There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. > > Can you confirm that the load being used has the mellanox pmd enabled in it? > > Thanks, > Ghada > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > Sent: Thursday, March 21, 2019 9:03 AM > To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Thanks Chenjie for the testing. > > Hi all, > Does it mean greenlight for code merge, or any other test is needed? > Here is the patch list: > https://review.openstack.org/642672 > https://review.openstack.org/642673 > > > Best Regards > Shuicheng > > From: Xu, Chenjie > Sent: Thursday, March 21, 2019 5:46 PM > To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing > > Hi team, > I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: > > Bug Summary: > No bug related to OVSDPDK Upgrade. > 3 bugs related to cutting over to container and configuration. > https://bugs.launchpad.net/starlingx/+bug/1821150 > https://bugs.launchpad.net/starlingx/+bug/1821135 > https://bugs.launchpad.net/starlingx/+bug/1820378 > > The following features have been tested: > N/S traffic for FLAT/VLAN network > E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) > QOS > Security Group > MTU > > Best Regards, > Xu, Chenjie > > > -------------- 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 10, Issue 156 > ************************************************** > > > _______________________________________________ > 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 Thu Mar 28 20:55:47 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 28 Mar 2019 21:55:47 +0100 Subject: [Starlingx-discuss] Initial StarlingX survey - feedback needed In-Reply-To: <93EB76DD-D95A-4944-9036-1F63E24E0F34@windriver.com> References: <764976D5-E76F-47C5-A99E-6F59AC7D6401@gmail.com> <93EB76DD-D95A-4944-9036-1F63E24E0F34@windriver.com> Message-ID: <5C97D085-1492-457E-86D4-B265FEBE1F05@gmail.com> Thanks for reminding I forgot we went through this exercise earlier. I tried to come up with items that may resonate closer to people, but I’m good with keeping it high level as well. I’ll wait to see if we have other views on this and update the survey when we reached agreement. Thanks, Ildikó > On 2019. Mar 28., at 21:37, Gowan, Jeff wrote: > > Ildiko > On the use case we may just want to go with the 6 high-level use cases we've identified (vRAN, MEC, vCPE, Transportation, Industrial, Healthcare) in order to test those assumptions, then include a 7th other category. > -Jeff > > On 3/28/19, 1:33 PM, "Ildiko Vancsa" wrote: > > Hi Jeff, > > Thanks for the comments and catching the typo. > > I like the word of mouth idea and also open to add the vRAN use case. I would not want to grow the list too big, but we can certainly add one or two more items that we see current. > > Thanks, > Ildikó > > >> On 2019. Mar 28., at 21:27, Gowan, Jeff wrote: >> >> Ildiko, >> >> Here are a couple of thoughts on the survey. >> >> Question 1 >> "Smary city" should be Smart city >> Can we add virtual RAN? >> >> Question 3 >> Can we add "colleague/associate" to capture word of mouth? >> >> Thanks, >> >> -Jeff >> >> On 3/28/19, 12:33 PM, "starlingx-discuss-request at lists.starlingx.io" 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: What is the new openstack command to create an stack? (Curtis) >> 2. Initial StarlingX survey - feedback needed (Ildiko Vancsa) >> 3. Re: OVS-DPDK Upgrade Testing (Martinez Monroy, Elio) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Thu, 28 Mar 2019 14:29:06 -0400 >> From: Curtis >> To: "Alonso, Juan Carlos" >> Cc: "Hernandez Gonzalez, Fernando" >> , >> "starlingx-discuss at lists.starlingx.io" >> >> Subject: Re: [Starlingx-discuss] What is the new openstack command to >> create an stack? >> Message-ID: >> >> Content-Type: text/plain; charset="utf-8" >> >> On Thu, Mar 28, 2019 at 2:09 PM Alonso, Juan Carlos < >> juan.carlos.alonso at intel.com> wrote: >> >>> Hi Fernando, >>> >>> >>> >>> I have the same steps to test. The problem comes when execute “openstack >>> stack create” command. >>> >>> Seems that there was an update with such command. >>> >>> I figured out that the current OpenStack documentation shows that we are >>> using the correct command. Maybe we have a real issue. >>> >>> https://docs.openstack.org/heat/rocky/getting_started/create_a_stack.html >>> >>> Need to confirm. >>> >> >> I'm guessing you are missing python-heatclient. >> >> Thanks, >> Curtis >> >> >> >>> >>> >>> Regards. >>> >>> Juan Carlos Alonso >>> >>> >>> >>> *From:* Hernandez Gonzalez, Fernando >>> *Sent:* Thursday, March 28, 2019 11:28 AM >>> *To:* Alonso, Juan Carlos ; >>> starlingx-discuss at lists.starlingx.io >>> *Subject:* RE: [Starlingx-discuss] What is the new openstack command to >>> create an stack? >>> >>> >>> >>> Hi JC, >>> >>> >>> >>> I am almost finishing the “HEAT HOT template” Test cases (the basics)… please look at the next link , under “HEAT_HOT_Template_07”, you will see the prerequisites for creation of Nova Server instance and the required template. >>> >>> >>> >>> Regards, >>> >>> *Fernando Hernandez Gonzalez* >>> >>> *Software Engineer* >>> >>> >>> >>> Avenida del Bosque #1001 Col, El Bajío >>> >>> Zapopan, Jalisco MX, 45019 >>> >>> ____________________________________ >>> >>> *Office:* +52.33.16.45.01.34 inet 86450134 >>> >>> >>> >>> *From:* Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com >>> ] >>> *Sent:* Thursday, March 28, 2019 11:19 AM >>> *To:* starlingx-discuss at lists.starlingx.io >>> *Subject:* [Starlingx-discuss] What is the new openstack command to >>> create an stack? >>> >>> >>> >>> Hi, >>> >>> >>> >>> Do someone know what is the new openstack command to create an stack? Then >>> to create an instance. >>> >>> >>> >>> I usually use: >>> >>> $openstack stack create --template ${stack_name} --parameter >>> "NetID=${net_id}" >>> >>> >>> >>> But got the below error: >>> >>> openstack: 'stack create…’ is not an openstack command. >>> >>> >>> >>> Regards. >>> >>> Juan Carlos Alonso >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >> >> >> -- >> Blog: serverascode.com >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> >> ------------------------------ >> >> Message: 2 >> Date: Thu, 28 Mar 2019 19:37:44 +0100 >> From: Ildiko Vancsa >> To: starlingx-discuss at lists.starlingx.io >> Subject: [Starlingx-discuss] Initial StarlingX survey - feedback >> needed >> Message-ID: <88772002-9A60-4741-8CDF-1BB2D44C6769 at gmail.com> >> Content-Type: text/plain; charset=utf-8 >> >> Hi StarlingX Community, >> >> As I reached out about this earlier a few of us started to draft a survey to learn about what people and companies are doing around edge and to see if they know about StarlingX and getting some initial feedback on what they are interested in. >> >> Please note that the idea is to get a high level view and find out about interest as opposed to going into deep details on deployment options, use cases or ways to contribute. >> >> In that sense the main objectives for the survey is to keep it short and simple and make it easy to fill out. You will see that the questions are mainly having options to select from as opposed to being free form, the option to specify custom answer is provided where applicable like the use cases one as we can’t list all the possible ones. We also added a question to give any feedback people might have for the community. >> >> The OpenStack Foundation will have access to the complete dataset and will provide the anonymized information to the community once it’s available. >> >> The survey is available here: https://www.surveymonkey.com/r/StarlingX >> >> Please read through the questions and reply back if you have comments or questions. >> >> Thanks and Best Regards, >> Ildikó >> >> >> >> >> >> ------------------------------ >> >> Message: 3 >> Date: Wed, 27 Mar 2019 18:47:13 +0000 >> From: "Martinez Monroy, Elio" >> To: "Peters, Matt" , "Xu, Chenjie" >> , "Khalil, Ghada" , >> "Lin, Shuicheng" , "Cabrales, Ada" >> , "Perez, Ricardo O" >> >> Cc: "'starlingx-discuss at lists.starlingx.io'" >> , "Zhao, Forrest" >> , "Rowsell, Brent" >> >> Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing >> Message-ID: >> <1466AF2176E6F040BD63860D0A241BBD46CA563A at FMSMSX109.amr.corp.intel.com> >> >> Content-Type: text/plain; charset="utf-8" >> >> Hi Matt >> >> Just exercising same stuff, please check my outputs from compute-0, please let me know if something else is needed >> >> sudo /usr/sbin/dmdecode >> Password: >> sudo: /usr/sbin/dmdecode: command not found >> compute-0:~$ sudo /usr/sbin/dmidecode >> # dmidecode 3.1 >> Getting SMBIOS data from sysfs. >> SMBIOS 2.8 present. >> 10 structures occupying 419 bytes. >> Table at 0x000F6460. >> >> Handle 0x0000, DMI type 0, 24 bytes >> BIOS Information >> Vendor: SeaBIOS >> Version: Ubuntu-1.8.2-1ubuntu1 >> Release Date: 04/01/2014 >> Address: 0xE8000 >> Runtime Size: 96 kB >> ROM Size: 64 kB >> Characteristics: >> BIOS characteristics not supported >> Targeted content distribution is supported >> BIOS Revision: 0.0 >> >> Handle 0x0100, DMI type 1, 27 bytes >> System Information >> Manufacturer: QEMU >> Product Name: Standard PC (i440FX + PIIX, 1996) >> Version: pc-i440fx-2.5 >> Serial Number: Not Specified >> UUID: 71d54a5d-b569-4e1c-83e3-9babf169e824 >> Wake-up Type: Power Switch >> SKU Number: Not Specified >> Family: Not Specified >> >> Handle 0x0300, DMI type 3, 21 bytes >> Chassis Information >> Manufacturer: QEMU >> Type: Other >> Lock: Not Present >> Version: pc-i440fx-2.5 >> Serial Number: Not Specified >> Asset Tag: Not Specified >> Boot-up State: Safe >> Power Supply State: Safe >> Thermal State: Safe >> Security Status: Unknown >> OEM Information: 0x00000000 >> Height: Unspecified >> Number Of Power Cords: Unspecified >> Contained Elements: 0 >> >> Handle 0x0400, DMI type 4, 42 bytes >> Processor Information >> Socket Designation: CPU 0 >> Type: Central Processor >> Family: Other >> Manufacturer: QEMU >> ID: A3 06 01 00 FF FB 8B 07 >> Version: pc-i440fx-2.5 >> Voltage: Unknown >> External Clock: Unknown >> Max Speed: 2000 MHz >> Current Speed: 2000 MHz >> Status: Populated, Enabled >> Upgrade: Other >> L1 Cache Handle: Not Provided >> L2 Cache Handle: Not Provided >> L3 Cache Handle: Not Provided >> Serial Number: Not Specified >> Asset Tag: Not Specified >> Part Number: Not Specified >> Core Count: 6 >> Core Enabled: 6 >> Thread Count: 1 >> Characteristics: None >> >> Handle 0x1000, DMI type 16, 23 bytes >> Physical Memory Array >> Location: Other >> Use: System Memory >> Error Correction Type: Multi-bit ECC >> Maximum Capacity: 10 GB >> Error Information Handle: Not Provided >> Number Of Devices: 1 >> >> Handle 0x1100, DMI type 17, 40 bytes >> Memory Device >> Array Handle: 0x1000 >> Error Information Handle: Not Provided >> Total Width: Unknown >> Data Width: Unknown >> Size: 10240 MB >> Form Factor: DIMM >> Set: None >> Locator: DIMM 0 >> Bank Locator: Not Specified >> Type: RAM >> Type Detail: Other >> Speed: Unknown >> Manufacturer: QEMU >> Serial Number: Not Specified >> Asset Tag: Not Specified >> Part Number: Not Specified >> Rank: Unknown >> Configured Clock Speed: Unknown >> Minimum Voltage: Unknown >> Maximum Voltage: Unknown >> Configured Voltage: Unknown >> >> Handle 0x1300, DMI type 19, 31 bytes >> Memory Array Mapped Address >> Starting Address: 0x00000000000 >> Ending Address: 0x000BFFFFFFF >> Range Size: 3 GB >> Physical Array Handle: 0x1000 >> Partition Width: 1 >> >> Handle 0x1301, DMI type 19, 31 bytes >> Memory Array Mapped Address >> Starting Address: 0x00100000000 >> Ending Address: 0x002BFFFFFFF >> Range Size: 7 GB >> Physical Array Handle: 0x1000 >> Partition Width: 1 >> >> Handle 0x2000, DMI type 32, 11 bytes >> System Boot Information >> Status: No errors detected >> >> Handle 0x7F00, DMI type 127, 4 bytes >> End Of Table >> >> compute-0:~$ virsh nodeinfo >> CPU model: x86_64 >> CPU(s): 6 >> CPU frequency: 3792 MHz >> CPU socket(s): 1 >> Core(s) per socket: 6 >> Thread(s) per core: 1 >> NUMA cell(s): 1 >> Memory size: 10485236 KiB >> >> compute-0:~$ /usr/bin/topology >> TOPOLOGY: >> logical cpus : 6 >> sockets : 1 >> cores_per_pkg : 6 >> threads_per_core : 1 >> numa_nodes : 1 >> total_memory : 9.61 GiB >> memory_per_node : 10.00 GiB >> >> LOGICAL CPU TOPOLOGY: >> cpu_id : 0 1 2 3 4 5 >> socket_id : 0 0 0 0 0 0 >> core_id : 0 1 2 3 4 5 >> thread_id : 0 0 0 0 0 0 >> >> CORE TOPOLOGY: >> cpu_id socket_id core_id thread_id affinity >> 0 0 0 0 0x1 >> 1 0 1 0 0x2 >> 2 0 2 0 0x4 >> 3 0 3 0 0x8 >> 4 0 4 0 0x10 >> 5 0 5 0 0x20 >> compute-0:~$ grep -i numa /var/log/dmesg >> [ 0.000000] No NUMA configuration found >> >> From: Peters, Matt [mailto:Matt.Peters at windriver.com] >> Sent: Wednesday, March 27, 2019 6:10 AM >> To: Xu, Chenjie ; Khalil, Ghada ; Martinez Monroy, Elio ; Lin, Shuicheng ; Cabrales, Ada ; Perez, Ricardo O >> Cc: 'starlingx-discuss at lists.starlingx.io' ; Zhao, Forrest ; Rowsell, Brent >> Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing >> >> Hello Chenjie, >> Can you run the following set of commands on your test system compute hosts and provide the output for each? >> >> sudo /usr/sbin/dmidecode >> virsh nodeinfo >> /usr/bin/topology >> grep -i numa /var/log/dmesg >> >> From: "Xu, Chenjie" > >> Date: Wednesday, March 27, 2019 at 5:45 AM >> To: "Peters, Matt" >, Ghada Khalil >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > >> Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > >> Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing >> >> Hi Matt, >> I tried standard 0322 ISO image on 4 bare metals and “NUMA sections are still missing”. The docker images versions and build baseline have been attached. The ISO image link is following: >> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T174230Z/outputs/iso/ >> >> Best Regards, >> Xu, Chenjie >> >> From: Xu, Chenjie >> Sent: Wednesday, March 27, 2019 10:38 AM >> To: 'Peters, Matt' >; Khalil, Ghada >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > >> Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > >> Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing >> >> Hi Matt, >> Sorry for misleading! I mean “NUMA sections are still missing”. >> >> I have multiple systems experiencing this issue: >> 1. 0306 ISO image for OVSDPDK Upgrade Testing on 4 bare metals >> 2. 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals >> 3. 0305 ISO image on 4 bare metals >> 4. 0315 ISO image one 1 bare metals >> The item 1, 2 and 3 use same bare metals. The item 4 use a separate bare metal. >> >> I will try 0322 ISO image on 4 bare metals. >> >> Best Regards, >> Xu, Chenjie >> >> From: Peters, Matt [mailto:Matt.Peters at windriver.com] >> Sent: Tuesday, March 26, 2019 11:10 PM >> To: Khalil, Ghada >; Xu, Chenjie >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > >> Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > >> Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing >> >> Hello Chenjie, >> Can you clarify this statement? “NUMA sections missing bug still exits”. >> Did you mean to say that the missing NUMA sections in the domain XML are now present, but you still can’t ping over the vhost port, or are you saying the NUMA sections are still missing? >> >> Do you have multiple systems that are experiencing this issue, or is it isolated to a single system that you are having problems with the NUMA topology? I believe you mentioned that you saw the same connectivity issues on a standard load from the mirror, so that still points to a test system / environment issue. >> >> As Ghada mentioned, I think the next steps are to get results from the sanity systems with the same load baseline and to test with your custom load on a system that has been proven to work on the standard load. >> >> -Matt >> >> From: Ghada Khalil > >> Date: Tuesday, March 26, 2019 at 9:28 AM >> To: "Xu, Chenjie" >, "Peters, Matt" >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > >> Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > >> Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing >> >> Has Elio or Rich from the test team tried the new load as well on their systems? Do they see the same issues you reported? I think we need some data for another system to compare. >> >> Ada, >> As part of this thread, I also requested that a VM connectivity test be added to regular sanity so that there is data from the daily cengn builds w/o the new version of ovs-dpdk. Has the sanity suite been updated? >> >> Thanks, >> Ghada >> >> From: Xu, Chenjie [mailto:chenjie.xu at intel.com] >> Sent: Tuesday, March 26, 2019 7:09 AM >> To: Peters, Matt; Martinez Monroy, Elio; Khalil, Ghada; Lin, Shuicheng; Cabrales, Ada; Perez, Ricardo O >> Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest >> Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing >> >> Hi Matt, >> I installed StarlingX using the new 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals. NUMA sections missing bug still exits: >> https://bugs.launchpad.net/starlingx/+bug/1820378 >> >> This time I update the docker images to latest before installing StarlingX. And the docker images versions and build baseline have been attached. Could you please help review the docker image versions? >> >> Best Regards, >> Xu, Chenjie >> >> From: Peters, Matt [mailto:Matt.Peters at windriver.com] >> Sent: Friday, March 22, 2019 8:31 PM >> To: Xu, Chenjie >; Martinez Monroy, Elio >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > >> Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > >> Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing >> >> Hello Chenjie, >> Comparing the image list to our labs shows a difference in the image IDs (sha), but I’m not sure if that is just a difference in build baselines or an actual difference in the images. Since some of them align, I think you might be running a different set of images. Can you confirm what the build baseline is that you pulled the images from? >> >> I have attached a sample list from our labs for comparison. >> >> -Matt >> >> From: "Xu, Chenjie" > >> Date: Friday, March 22, 2019 at 7:25 AM >> To: "Peters, Matt" >, "Martinez Monroy, Elio" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > >> Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > >> Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing >> >> Hi Matt, >> The docker image versions in my environment and helm-charts-manifest-no-tests.tgz has been attached. The helm-charts-manifest-no-tests.tgz is built by Shuicheng for the OVSDPDK Upgrade Testing ISO image. >> >> Best Regards, >> Xu, Chenjie >> >> From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] >> Sent: Thursday, March 21, 2019 11:20 PM >> To: Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > >> Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > >> Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing >> >> Perfect, I will be cheking my mail for that new ISO. >> >> Adding Richo , he is the one that is going to execute the tests. >> >> Thanks >> >> BR >> >> Elio >> >> From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] >> Sent: Thursday, March 21, 2019 9:15 AM >> To: Lin, Shuicheng >; Cabrales, Ada >; Martinez Monroy, Elio > >> Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > >> Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing >> >> Hi Shuicheng, >> We discussed this in the networking bi-weekly team meeting today. >> >> Please re-enable the mlx pmd – re-apply the following patch: >> https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch >> >> Then please rebase to the latest master and build a new load for Ada’s team to start testing >> >> Hi Elio, >> One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. >> >> Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: >> https://bugs.launchpad.net/starlingx/+bug/1821150 >> https://bugs.launchpad.net/starlingx/+bug/1821135 >> https://bugs.launchpad.net/starlingx/+bug/1820378 >> >> Thanks, >> Ghada >> >> From: Khalil, Ghada >> Sent: Thursday, March 21, 2019 9:12 AM >> To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada >> Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng >> Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing >> >> Hi Shuicheng, >> There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. >> >> Can you confirm that the load being used has the mellanox pmd enabled in it? >> >> Thanks, >> Ghada >> >> From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] >> Sent: Thursday, March 21, 2019 9:03 AM >> To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada >> Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng >> Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing >> >> Thanks Chenjie for the testing. >> >> Hi all, >> Does it mean greenlight for code merge, or any other test is needed? >> Here is the patch list: >> https://review.openstack.org/642672 >> https://review.openstack.org/642673 >> >> >> Best Regards >> Shuicheng >> >> From: Xu, Chenjie >> Sent: Thursday, March 21, 2019 5:46 PM >> To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > >> Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > >> Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing >> >> Hi team, >> I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: >> >> Bug Summary: >> No bug related to OVSDPDK Upgrade. >> 3 bugs related to cutting over to container and configuration. >> https://bugs.launchpad.net/starlingx/+bug/1821150 >> https://bugs.launchpad.net/starlingx/+bug/1821135 >> https://bugs.launchpad.net/starlingx/+bug/1820378 >> >> The following features have been tested: >> N/S traffic for FLAT/VLAN network >> E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) >> QOS >> Security Group >> MTU >> >> Best Regards, >> Xu, Chenjie >> >> >> -------------- 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 10, Issue 156 >> ************************************************** >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > From ricardo.o.perez at intel.com Thu Mar 28 21:16:32 2019 From: ricardo.o.perez at intel.com (Perez, Ricardo O) Date: Thu, 28 Mar 2019 21:16:32 +0000 Subject: [Starlingx-discuss] Skydive? In-Reply-To: <9A85D2917C58154C960D95352B22818BD0708212@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BD0708212@fmsmsx123.amr.corp.intel.com> Message-ID: Hi Bruce, I don't have any experience with skydrive, however I have taken a quick look, and seems to be awesome !!!. I believe it would be very useful to track the traffic and see visually al the connections between internal / external networks, which, for debug purpose I believe is very useful. Moreover, it seems to be very compatible with our current StarlingX components like Neutron / OVS. So I would like to have it as part of our StarlingX system. Regards -Richo From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Tuesday, March 26, 2019 11:15 AM To: starlingx-discuss Subject: [Starlingx-discuss] Skydive? Does anyone have any experience with the Skydive project? http://skydive.network/. Is it something that would be interesting or helpful for StarlingX users? brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From abraham.arce.moreno at intel.com Thu Mar 28 22:01:02 2019 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Thu, 28 Mar 2019 22:01:02 +0000 Subject: [Starlingx-discuss] Edge Computing Use Case, Deployment Advice Needed Message-ID: Hi StarlingX Community, We need your advice to determine the most appropriate way to migrate an existing demo deployed via containers to StarlingX infrastructure with cloud features in mind (e.g. zero touch provisioning). We are integrating this demo in our spare time to ramp up in cloud technologies and one of its imperatives is a working solution. It started as a use case proposal around unmanned aerial systems [0], then decided to avoid some of the complexity involved in flying the drones, and finally landed it as a use case around home automation / smart cities at the network edge. Three key aspects for you to consider: - Edge computing foundation is all about "things" interchanging "data" with "servers", same foundation when both use case proposals were envisioned. - "Data" will include "video streaming" pipelines, considered in both use case proposals. - "Video streaming" pipelines will serve as an input to "machine learning / deep learning" services offloaded to different hardware (CPU, GPU, VPU, FPGA) also considered in both use case proposal, which gives an interesting workload to showcase some of the StarlingX characteristics: reliability, scalability and ultra-low latency. [ General Architecture ] The high level architecture [2] is compromised of the following components (naming still under review): - Core Applications - Services [ Core Applications ] Core Applications [3] give the foundation of the demo, the following have been integrated: - Home Assistant: Open Source Home Automation - InfluxDB: Time Seria Database Platform - Grafana: Data Visualization and Monitoring - Mosquitto: MQTT Message Broker - Glances: System Monitoring Tool - Portainer: Docker Environment Manager - Node-RED: Programming Tool for Hardware Devices - Netdata: Systems and Applications Monitoring - Plex: Media Server - motionEye: Video Signal Monitoring [ Services ] Services [4] are designed to perform a specific function in a specific device for a specific period of time (on demand) and will work with other micro services to form higher-level decisions, from a machine learning 'bot' service that use time-series data from the different sensors for simple control and personalization to a deep learning computer vision service that use existing network video recorder streams for video surveillance and video analytics. This demo has currently integrated samples of computer vision applications with the following services: - OpenCV (Computer Vision) - Haar Cascades - OpenVINO (Computer Vision) - Gstreamer (Video Stream) - Mjpeg- Streamer (Video Stream) - You Only Look Once (Object Detection) This demo has currently integrated the following acceleration resources: - GPU - VPU (Movidius NCS) Once demo has a solid foundation and stability with these first services, the following components are next to be integrated: - FPGA - Intel Accelerated Stack [ StarlingX Deployment ] [ Offload ] What would be the preferred way to deploy this use case proposal in StarlingX? We understand the following options are available including its preference: 1. Via Kubernetes (Not Preferred) 2. Via Virtual Machine (Preferred) 3. Via Bare Metal (Preferred) Are the above options and their preference, correct? If not, can you please give us some hints behind your answer. [ StarlingX Deployment ] [ Provisioning ] As mentioned at the beginning, another of our imperatives, is to exercise zero touch provisioning. Does it makes sense to split the provisioning in 2 parts based in the required time for the demo components to live? - The core applications 100% uptime - Services on demand / 100 uptime in some cases Is there any other cloud feature we would want consider, to take a look and use for this first version of the demo? [ StarlingX Deployment ] [ Provisioning ] [ Core Applications ] Would it make sense to create a cloud image with the core applications integrated? If not, what would be your best approach for the core applications? [ StarlingX Deployment ] [ Provisioning ] [ Services ] Since Services will be on demand, there might be some options: - Service running in containers under a virtual machine / bare metal - Services running in single virtual machines - Any other? This part is the most important for the demo since user experience might be affected (e.g. time taken for the system to start a face recognition service under camera one) [ Thanks ] We appreciate your time to read this email and your support so we can understand the best provisioning architecture for the use case proposal / demo. One of the additional things we are working on is a workshop taking this learning with the final objective to deploy in StarlingX in community events, still in an early development phase [5]. [0] https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Unmanned_Aircraft_Systems_.28Drones.29 [1] https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Smart_Home [2] https://github.com/bacabhome/bacabhome [3] https://github.com/bacabhome/bacabhome/blob/master/docker-compose.yml [4] https://github.com/bacabhome/bacabhome/tree/master/services [5] http://bit.ly/SmartHomeSolution -------------- next part -------------- An HTML attachment was scrubbed... URL: From glenn.seiler at windriver.com Thu Mar 28 23:37:52 2019 From: glenn.seiler at windriver.com (Seiler, Glenn) Date: Thu, 28 Mar 2019 23:37:52 +0000 Subject: [Starlingx-discuss] DRAFT release policy In-Reply-To: <9A85D2917C58154C960D95352B22818BD0709720@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BD0709720@fmsmsx123.amr.corp.intel.com> Message-ID: Bruce, Release team; Thank you for putting this in writing. I have to admit I find the basic strategy statements confusing: 1- We need to move away from time-based releases 2- We need to do twice a year releases. This stmt, by definition, implies a time-gated release. Maybe it isn't a specific date, but it is still time-gated. As a nascent project, I think we need to show gradual and consistent progress. I did listen to much of the release team meeting today, and realize the trade-offs between big-rocks and timing are very difficult. Given the difficult choice of functionality versus timing, I personally think we need to show progress in getting to Stein and a container based distribution as major milestones in 1H and perhaps defer the Distributed Cloud capability to a 2H release. I don't see anything intrinsically wrong with moving a specific date out; it happens all the time. But I also think a release should have some gate; i.e. we don't move out of 1H. And if some functionality isn't ready, then we move the functionality to another release in 2H. Anyway, that would be my vote, if I have one. From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, March 28, 2019 12:49 PM To: starlingx-discuss Subject: [Starlingx-discuss] DRAFT release policy We've been working on a draft release policy in the Release team. Please review and share your comments, feedback or suggestions in the etherpad or on this thread. The draft is located at https://etherpad.openstack.org/p/stx-release-policy-draft The current text is below. Brucej Release Policy =========== The StarlingX project determines release schedules based on when the release content is ready to be released. We should explicitly move away from the idea of time based releases. We should continue our current twice per year release cycle * We should consider changing our release naming convention to something that doesn't include dates. The Release team, together with the Test team TLs/PLs, shall make a recommendation to the community and TSC that a release is ready to go. Upon TSC approval, the release branches are tagged and the release documented. That recommendation should be based on: 1. Whether or not all anchor features in the release are complete, as per the input of the team(s) implementing the features and the results of Test team testing of the features * Assumption: The TSC will create a list of approved features during the release planning process, and that some (or all) of these features will be identified by the TSC as "release gating" or "anchor" features that would block a release if not complete. * Assumption: We are planning our releases at the PTG meetings every 6 months. 2. The results of formal Testing performed by the Test team, measured by the percentage of planned tests attempted and the test pass rate * Proposal: 100% test cases attemped and 95% test cases passing in all configurations 3. The severity and number of bugs open against the release * Proposal: No open Critical or High severity bugs against the release candidate. Or maybe 1-3 Highs if we have a clear resolution plan (and a plan to release a patch against the release?) * See Bug Severity definitions below. We should discuss the option of doing a mid-cycle "bug fix" release against the latest release - allowing key defects to get fixed more rapidly. In such a case, the release team would make a recommendation to the TSC to approve the release plan and content. If approved by the TSC, the fixes shall be cherry-picked or merged into the release branch and a new build tested (and managed as per this policy). Bug Severity ========== Critical: The software does not operate as intended (e.g. the software fails to install, does not run, crashes, etc...). Or the issue is a Securty/CVE issue with a rating of Critical or High. In Launchpad this is "Fix as soon as possible" High: An important feature of the software does not operate as intended (e.g. live migration, fault reporting, etc...). Or the issue is a Security/CVE issue with a rating of Medium or lower. In Launchpad this is "Fix soon". Medium: A minor feature of the software does not operate as intended or there is an intermitant failure. In Launchpad this is "Fix when convienent or schedule to fix later". Low: A bug that does not impact normal operation of the software. In Launchpad this is "Fix when convienent". -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Thu Mar 28 23:56:10 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Thu, 28 Mar 2019 23:56:10 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190328 Message-ID: <8557B550001AFB46A43A0CCC314BF85153CAF2D2@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Mar-28 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup Manual [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 55 TCs [FAIL] Sanity Platform 07 TCs [FAIL] TOTAL: [ 63 TCs FAIL ] AIO - Duplex Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 19 TCs [PASS] | 39 TCs [FAIL] Sanity Platform 04 TCs [PASS] | 01 TCs [FAIL] TOTAL: [24 TCs PASS | 40 TCs FAIL ] Standard - Local Storage (2+2) Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 19 TCs [PASS] | 39 TCs [FAIL] Sanity Platform 04 TCs [PASS] | 01 TCs [FAIL] TOTAL: [ 24 TCs PASS | 40 TCs FAIL ] Standard - Dedicated Storage (2+2+2) Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 16 TCs [PASS] | 42 TCs [FAIL] Sanity Platform 04 TCs [PASS] | 01 TCs [FAIL] TOTAL: [ 21 TCs PASS | 43 TCs FAIL ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [FAIL] Sanity Platform 07 TCs [FAIL] TOTAL: [ 04 TCs PASS | 57 TCs FAIL ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 51 TCs [PASS] | 01 TCs [FAIL] Sanity Platform 05 TCs [PASS] TOTAL: [ 61 TCs PASS | 01 TCs FAIL ] Standard - Local Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 19 TCs [PASS] | 33 TCs [FAIL] Sanity Platform 05 TCs [PASS] TOTAL: [ 29 TCs PASS | 33 TCs FAIL ] Standard - Dedicated Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 51 TCs [PASS] | 01 TCs [FAIL] Sanity Platform 05 TCs [PASS] TOTAL: [ 61 TCs PASS | 01 TCs FAIL ] ------------------------------------------------------------------ Simplex BM and Virtual - application-apply fails at 95% ceilometer pod Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1820928 Standard Dedicated Storage BM and Virtual - Could not create VMs Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1821841 All Configurations BM and Virtual - python-heatclient package is not currently installed on ISO. Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1822200 All Configurations BM and Virtual - Console of instances in Horizon is not available Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1822212 ------------------------------------------------------------------ This is the list of test cases executed: https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Fri Mar 29 00:03:51 2019 From: kennelson11 at gmail.com (Kendall Nelson) Date: Thu, 28 Mar 2019 17:03:51 -0700 Subject: [Starlingx-discuss] PTG Team Photos Message-ID: Hello! If your team is interested in having a team photo taken, here is the signup[1]! There are slots Thursday and Friday from 10:00 AM to 4:30 PM. The location is TBD but will likely be close to where registration will be. I'll send an email out the day before with a reminder of your time slot and an exact location. -Kendall (diablo_rojo) [1] https://docs.google.com/spreadsheets/d/1DgsRHVWW2YLv7ewfX0M21zWJRf4wUfPG4ff2V5XtaMg/edit?usp=sharing -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtroyer at gmail.com Fri Mar 29 02:29:29 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Thu, 28 Mar 2019 21:29:29 -0500 Subject: [Starlingx-discuss] DRAFT release policy In-Reply-To: References: <9A85D2917C58154C960D95352B22818BD0709720@fmsmsx123.amr.corp.intel.com> Message-ID: On Thu, Mar 28, 2019 at 6:39 PM Seiler, Glenn wrote: > 1- We need to move away from time-based releases > 2- We need to do twice a year releases. This stmt, by definition, implies a time-gated release. Maybe it isn’t a specific date, but it is still time-gated. The wording does need work, yes. After a short conversation with Bruce this afternoon (Bruce, correct me if I'm wrong here) I came away with the intention being more of increasing the lag from OpenStack releases rather than separating completely from the OpenStack release cycle which is likely to stay at approx 6 months for a while (that's a rabbit hole under the bike shed I'd like to avoid just now). > As a nascent project, I think we need to show gradual and consistent progress. ++ > I did listen to much of the release team meeting today, and realize the trade-offs between big-rocks and timing are very difficult. > > Given the difficult choice of functionality versus timing, I personally think we need to show progress in getting to Stein and a container based distribution as major milestones in 1H and perhaps defer the Distributed Cloud capability to a 2H release. > > I don’t see anything intrinsically wrong with moving a specific date out; it happens all the time. But I also think a release should have some gate; i.e. we don’t move out of 1H. And if some functionality isn’t ready, then we move the functionality to another release in 2H. We took a stab at estimating and missed, making adjustments now is normal and to be expected. I agree with considering pushing distcloud to the next release because it is a) new functionality, and b) devs overlap with the container work and I think making the k8s infrastructure rock solid is much more important. If we are too far off with system stability the ramifications will be harder to overcome than delaying a new feature. > Anyway, that would be my vote, if I have one. You totally have a voice as part of the community, I would like to hear from more folks here... dt -- Dean Troyer dtroyer at gmail.com From cheng1.li at intel.com Fri Mar 29 02:59:23 2019 From: cheng1.li at intel.com (Li, Cheng1) Date: Fri, 29 Mar 2019 02:59:23 +0000 Subject: [Starlingx-discuss] Running OVS in container is supported now Message-ID: Hi, I was working on OVS containerization. The patch [1] was merged hours ago. So we support running OVS in container now. And this is the *default* setting. We still support OVS-DPDK, but you need to set it explicitly. I have also updated the deployment guides at [2] [3] [4] [5]. Please note, OVS-DPDK will be supported only on Bare Metal deployment. VM deployment doesn't support OVS-DPDK anymore. [1] https://review.openstack.org/#/c/633924/ [2] https://wiki.openstack.org/wiki/StarlingX/Containers/Installation#Configure_the_vswitch_type_.28optional.29 [3] https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnAIODX#Configure_the_vswitch_type_.28optional.29 [4 ]https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnStandard#Configure_the_vswitch_type_.28optional.29 [5] https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnStandardStorage#Configure_the_vswitch_type_.28optional.29 Thanks, Cheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Fri Mar 29 05:35:06 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Fri, 29 Mar 2019 05:35:06 +0000 Subject: [Starlingx-discuss] pep 8 issue need to be fixed Message-ID: <93814834B4855241994F290E959305C753057919@SHSMSX104.ccr.corp.intel.com> Hi all, When I update my patch for stx-integ, it report below errors, which causes "Verified -1 Zuul" Not sure why we have this issue now. It is a common issue that I also saw in other patches submitted recently. Do we need a new ticket to fix this pep8 issue or just disable B009 and B010? Any comment? pep8 run-test: commands[0] | flake8 setting PATH=/home/zuul/src/git.openstack.org/openstack/stx-integ/.tox/pep8/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games [4871] /home/zuul/src/git.openstack.org/openstack/stx-integ$ /home/zuul/src/git.openstack.org/openstack/stx-integ/.tox/pep8/bin/flake8 ./tools/storage-topology/storage-topology/storage_topology/exec/storage_topology.py:339:50: B009 Do not call getattr with a constant attribute value, it is not any safer than normal property access. ./tools/storage-topology/storage-topology/storage_topology/exec/storage_topology.py:340:50: B009 Do not call getattr with a constant attribute value, it is not any safer than normal property access. ./tools/storage-topology/storage-topology/storage_topology/exec/storage_topology.py:345:50: B009 Do not call getattr with a constant attribute value, it is not any safer than normal property access. ./tools/vm-topology/vm-topology/vm_topology/exec/vm_topology.py:400:13: B010 Do not call setattr with a constant attribute value, it is not any safer than normal property access. ./tools/vm-topology/vm-topology/vm_topology/exec/vm_topology.py:401:34: B009 Do not call getattr with a constant attribute value, it is not any safer than normal property access. ./tools/vm-topology/vm-topology/vm_topology/exec/vm_topology.py:403:13: B010 Do not call setattr with a constant attribute value, it is not any safer than normal property access. ./tools/vm-topology/vm-topology/vm_topology/exec/vm_topology.py:405:13: B009 Do not call getattr with a constant attribute value, it is not any safer than normal property access. ./tools/vm-topology/vm-topology/vm_topology/exec/vm_topology.py:407:13: B010 Do not call setattr with a constant attribute value, it is not any safer than normal property access. ERROR: InvocationError for command /home/zuul/src/git.openstack.org/openstack/stx-integ/.tox/pep8/bin/flake8 (exited with code 1) Thanks! zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Fri Mar 29 09:54:01 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Fri, 29 Mar 2019 09:54:01 +0000 Subject: [Starlingx-discuss] PCI Interrupt affinity task Message-ID: <93814834B4855241994F290E959305C753057963@SHSMSX104.ccr.corp.intel.com> Hi Jim and Brent, For this task, I have almost finished it, including improvement according to review commends from community. However, it still have some dependency on nova master version now. This affinity agent could not get both pci_device info and numa info of server from nova. In nova stage version, we added below two for server. server["wrs-res:topology"] server["wrs-res:pci_devices"] In nova master, no these attributions for server. For topology, I can see that there is a patch of adding numa topology pending for merge https://review.openstack.org/#/c/621476 Add server sub-resource topology API Do you have any proposal for it? Thanks! Zhipeng From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: 2019年3月4日 10:34 To: Gauld, James ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] PCI Interrupt affinity task Hi Jim and all, I have submitted all my patches for PCI Interrupt affinity feature as below link. https://review.openstack.org/#/c/640264/ https://review.openstack.org/#/c/640263/ Below one is the patch for removing pci-irq-affinity function from nova. https://github.com/hustlzp1981/stx-nova/commit/c52432b3e7a240817a2de06321a2459f4862ab6a Your comments are appreciated! Thanks! Zhipeng From: Gauld, James [mailto:James.Gauld at windriver.com] Sent: 2019年2月26日 22:07 To: Liu, ZhipengS >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] PCI Interrupt affinity task Zhipeng, Option 1) is a reasonable choice. I agree with your reasoning. FYI, I don’t think we depend on nova-sriov script anymore, but we haven't actually tested with that removed. Please add me to your code inspection. -Jim From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: February-21-19 10:24 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] PCI Interrupt affinity task Hi all Recently, I have being working on pci interrupt affinity task (https://storyboard.openstack.org/#!/story/2004600) So far I have finished coding, basic deployment test and function test. Now, I’m preparing for uploading my patch for code review. However, I need to decide where to put code folder. >From my point, there are two options below. 1) stx-integ/utilities/nova-utils/pci-affinity-agent 2) stx-config/sysinv/pci-affinity-agent (I put code here currently) I prefer option 1 as nova-utils is just used to install nova-sriov script only and pci affinity is also an extended feature for nova. We can reuse nova-utils package with additional RPM for pci-affinity-agent Any comment from you? Thanks! zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From kyle.oh95 at gmail.com Fri Mar 29 10:13:16 2019 From: kyle.oh95 at gmail.com (=?UTF-8?B?7Jik7J6s7Jqx?=) Date: Fri, 29 Mar 2019 19:13:16 +0900 Subject: [Starlingx-discuss] Fwd: [starlingx-discuss] [critical error after deployment] About "persistent critical 'Management Network'" In-Reply-To: <210898B96CA058408C55992CCAD98676B9FBDDC7@ALA-MBD.corp.ad.wrs.com> References: <06F50A69-BBA2-4A6E-986C-74C7B8452A44@intel.com> <210898B96CA058408C55992CCAD98676B9FBD1FA@ALA-MBD.corp.ad.wrs.com> <210898B96CA058408C55992CCAD98676B9FBDDC7@ALA-MBD.corp.ad.wrs.com> Message-ID: Hello all, I finally added controller-1 successfully. At first I used 1G NIC for management network, but did not work. Today I changed 10G NIC for the network, and it worked well! Thank you very much :) Best Regards, Jaewook. 2019년 3월 27일 (수) 오후 9:38, MacDonald, Eric 님이 작성: > There appears to be something wrong with your multi-cast setup as the > hbsAgent is not able to setup its pulse messaging socket for the management > interface. > > > > hbsAgent.log – This log seems to have rotated due to successive socket > resetup retries. > > 2019-03-27T10:33:55.984 [4194.3824110] controller-0 hbsAgent --- > msgClass.cpp (1033) msgClassTx : Info : Creating > controller-0 socket on port 2106 with address: 239.1.1.2 > > 2019-03-27T10:33:55.984 [4194.3824111] controller-0 hbsAgent --- > msgClass.cpp (1098) initSocket :Error : Failed to bind > socket to address (22:Invalid argument) > > 2019-03-27T10:33:55.984 [4194.3824112] controller-0 hbsAgent hbs > hbsAgent.cpp ( 575) _setup_pulse_messaging :Error : Cannot open > multicast transmit socket - rc:34 (22:Invalid argument) > > > > mtcAgent.log shows that your management interface is bouncing which is > causing command failures. > > 2019-03-22T16:57:19.449 [94960.00107] controller-0 mtcAgent hbs > nodeClass.cpp (4288) service_netlink_events : Warn : Management link > eno2 is down > > 2019-03-22T16:57:19.449 [94960.00108] controller-0 mtcAgent hbs > nodeClass.cpp (4301) service_netlink_events : Warn : eno2 is down > (oper:down) > > 2019-03-22T16:57:19.881 [94960.00109] controller-0 mtcAgent hbs > nodeClass.cpp (4324) service_netlink_events : Warn : Management link > eno2 is up > > 2019-03-22T16:57:20.261 [94960.00110] controller-0 mtcAgent hbs > nodeClass.cpp (4288) service_netlink_events : Warn : Management link > eno2 is down > > > > *I suggest you stabilize your management network between the 2 > controllers.* > > > > You can always look for Error or Warn logs in mtcAgent.log as indication > of unexpected conditions. > > The logs are kept quite short and try to indicate the issue at hand. In > this case eno2 is bouncing. > > > > Eric. > ================================================ *Jaewook Oh* (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.p.gomez at intel.com Thu Mar 28 23:00:39 2019 From: juan.p.gomez at intel.com (Gomez, Juan P) Date: Thu, 28 Mar 2019 23:00:39 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: References: <151EE31B9FCCA54397A757BC674650F0BA4D1AA8@ALA-MBD.corp.ad.wrs.com> <72A55890-B007-4E93-A74A-291C725B158E@windriver.com> <1466AF2176E6F040BD63860D0A241BBD46CA563A@FMSMSX109.amr.corp.intel.com> <608E4D93-FDFF-4F00-A166-A89EA6683B90@windriver.com> <1466AF2176E6F040BD63860D0A241BBD46CA56BA@FMSMSX109.amr.corp.intel.com> Message-ID: <0483622846A57742B81A944248DD69042FC28FFD@fmsmsx101.amr.corp.intel.com> Hi Ghada, Ricardo and I were working in different systems ( Duplex and Standard Controller 2+2 ) and We were able to reproduced the issues, bugs have been updated Also We have run the Sanity Test on both configurations with no issues Matt, Also We have attached the logs from both configurations Best Regards, JP From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Wednesday, March 27, 2019 7:59 PM To: Martinez Monroy, Elio ; Peters, Matt ; Khalil, Ghada ; Lin, Shuicheng ; Cabrales, Ada ; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io' ; Zhao, Forrest ; Rowsell, Brent Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I run the following commands on compute-0. The outputs of commands have been attached. sudo /usr/sbin/dmidecode > dmidecode.txt virsh nodeinfo > nodeinfo.txt /usr/bin/topology > topology.txt grep -i numa /var/log/dmesg > dmesg.txt And the StarlingX is installed with standard 0322 ISO image: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T174230Z/outputs/iso/ Best Regards, Xu, Chenjie From: Martinez Monroy, Elio Sent: Thursday, March 28, 2019 3:36 AM To: Peters, Matt >; Xu, Chenjie >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Rowsell, Brent > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing So, in order to develop our NUMA test cases, we should configure that topology in our VM’s? How can we do it? Do you have the steps? BR Elio From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 27, 2019 1:19 PM To: Martinez Monroy, Elio >; Xu, Chenjie >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Rowsell, Brent > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello, From the output below, this data is taken from a virtual system. In a QEMU/KVM environment, it is not expected to have a NUMA topology unless it has been explicitly configured in the domain configuration of the emulated host. I’m assuming the tests being performed by Chenjie are in a HW lab. This can be confirmed by providing the same set of data for those test systems. Thanks, Matt From: "Martinez Monroy, Elio" > Date: Wednesday, March 27, 2019 at 2:47 PM To: "Peters, Matt" >, "Xu, Chenjie" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" >, Brent Rowsell > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt Just exercising same stuff, please check my outputs from compute-0, please let me know if something else is needed sudo /usr/sbin/dmdecode Password: sudo: /usr/sbin/dmdecode: command not found compute-0:~$ sudo /usr/sbin/dmidecode # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 10 structures occupying 419 bytes. Table at 0x000F6460. Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: SeaBIOS Version: Ubuntu-1.8.2-1ubuntu1 Release Date: 04/01/2014 Address: 0xE8000 Runtime Size: 96 kB ROM Size: 64 kB Characteristics: BIOS characteristics not supported Targeted content distribution is supported BIOS Revision: 0.0 Handle 0x0100, DMI type 1, 27 bytes System Information Manufacturer: QEMU Product Name: Standard PC (i440FX + PIIX, 1996) Version: pc-i440fx-2.5 Serial Number: Not Specified UUID: 71d54a5d-b569-4e1c-83e3-9babf169e824 Wake-up Type: Power Switch SKU Number: Not Specified Family: Not Specified Handle 0x0300, DMI type 3, 21 bytes Chassis Information Manufacturer: QEMU Type: Other Lock: Not Present Version: pc-i440fx-2.5 Serial Number: Not Specified Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: Unknown OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 Handle 0x0400, DMI type 4, 42 bytes Processor Information Socket Designation: CPU 0 Type: Central Processor Family: Other Manufacturer: QEMU ID: A3 06 01 00 FF FB 8B 07 Version: pc-i440fx-2.5 Voltage: Unknown External Clock: Unknown Max Speed: 2000 MHz Current Speed: 2000 MHz Status: Populated, Enabled Upgrade: Other L1 Cache Handle: Not Provided L2 Cache Handle: Not Provided L3 Cache Handle: Not Provided Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Core Count: 6 Core Enabled: 6 Thread Count: 1 Characteristics: None Handle 0x1000, DMI type 16, 23 bytes Physical Memory Array Location: Other Use: System Memory Error Correction Type: Multi-bit ECC Maximum Capacity: 10 GB Error Information Handle: Not Provided Number Of Devices: 1 Handle 0x1100, DMI type 17, 40 bytes Memory Device Array Handle: 0x1000 Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: 10240 MB Form Factor: DIMM Set: None Locator: DIMM 0 Bank Locator: Not Specified Type: RAM Type Detail: Other Speed: Unknown Manufacturer: QEMU Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Rank: Unknown Configured Clock Speed: Unknown Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x1300, DMI type 19, 31 bytes Memory Array Mapped Address Starting Address: 0x00000000000 Ending Address: 0x000BFFFFFFF Range Size: 3 GB Physical Array Handle: 0x1000 Partition Width: 1 Handle 0x1301, DMI type 19, 31 bytes Memory Array Mapped Address Starting Address: 0x00100000000 Ending Address: 0x002BFFFFFFF Range Size: 7 GB Physical Array Handle: 0x1000 Partition Width: 1 Handle 0x2000, DMI type 32, 11 bytes System Boot Information Status: No errors detected Handle 0x7F00, DMI type 127, 4 bytes End Of Table compute-0:~$ virsh nodeinfo CPU model: x86_64 CPU(s): 6 CPU frequency: 3792 MHz CPU socket(s): 1 Core(s) per socket: 6 Thread(s) per core: 1 NUMA cell(s): 1 Memory size: 10485236 KiB compute-0:~$ /usr/bin/topology TOPOLOGY: logical cpus : 6 sockets : 1 cores_per_pkg : 6 threads_per_core : 1 numa_nodes : 1 total_memory : 9.61 GiB memory_per_node : 10.00 GiB LOGICAL CPU TOPOLOGY: cpu_id : 0 1 2 3 4 5 socket_id : 0 0 0 0 0 0 core_id : 0 1 2 3 4 5 thread_id : 0 0 0 0 0 0 CORE TOPOLOGY: cpu_id socket_id core_id thread_id affinity 0 0 0 0 0x1 1 0 1 0 0x2 2 0 2 0 0x4 3 0 3 0 0x8 4 0 4 0 0x10 5 0 5 0 0x20 compute-0:~$ grep -i numa /var/log/dmesg [ 0.000000] No NUMA configuration found From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 27, 2019 6:10 AM To: Xu, Chenjie >; Khalil, Ghada >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Rowsell, Brent > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Can you run the following set of commands on your test system compute hosts and provide the output for each? sudo /usr/sbin/dmidecode virsh nodeinfo /usr/bin/topology grep -i numa /var/log/dmesg From: "Xu, Chenjie" > Date: Wednesday, March 27, 2019 at 5:45 AM To: "Peters, Matt" >, Ghada Khalil >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I tried standard 0322 ISO image on 4 bare metals and “NUMA sections are still missing”. The docker images versions and build baseline have been attached. The ISO image link is following: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T174230Z/outputs/iso/ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Wednesday, March 27, 2019 10:38 AM To: 'Peters, Matt' >; Khalil, Ghada >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, Sorry for misleading! I mean “NUMA sections are still missing”. I have multiple systems experiencing this issue: 1. 0306 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 2. 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 3. 0305 ISO image on 4 bare metals 4. 0315 ISO image one 1 bare metals The item 1, 2 and 3 use same bare metals. The item 4 use a separate bare metal. I will try 0322 ISO image on 4 bare metals. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 26, 2019 11:10 PM To: Khalil, Ghada >; Xu, Chenjie >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Can you clarify this statement? “NUMA sections missing bug still exits”. Did you mean to say that the missing NUMA sections in the domain XML are now present, but you still can’t ping over the vhost port, or are you saying the NUMA sections are still missing? Do you have multiple systems that are experiencing this issue, or is it isolated to a single system that you are having problems with the NUMA topology? I believe you mentioned that you saw the same connectivity issues on a standard load from the mirror, so that still points to a test system / environment issue. As Ghada mentioned, I think the next steps are to get results from the sanity systems with the same load baseline and to test with your custom load on a system that has been proven to work on the standard load. -Matt From: Ghada Khalil > Date: Tuesday, March 26, 2019 at 9:28 AM To: "Xu, Chenjie" >, "Peters, Matt" >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Has Elio or Rich from the test team tried the new load as well on their systems? Do they see the same issues you reported? I think we need some data for another system to compare. Ada, As part of this thread, I also requested that a VM connectivity test be added to regular sanity so that there is data from the daily cengn builds w/o the new version of ovs-dpdk. Has the sanity suite been updated? Thanks, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 26, 2019 7:09 AM To: Peters, Matt; Martinez Monroy, Elio; Khalil, Ghada; Lin, Shuicheng; Cabrales, Ada; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I installed StarlingX using the new 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals. NUMA sections missing bug still exits: https://bugs.launchpad.net/starlingx/+bug/1820378 This time I update the docker images to latest before installing StarlingX. And the docker images versions and build baseline have been attached. Could you please help review the docker image versions? Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Friday, March 22, 2019 8:31 PM To: Xu, Chenjie >; Martinez Monroy, Elio >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Comparing the image list to our labs shows a difference in the image IDs (sha), but I’m not sure if that is just a difference in build baselines or an actual difference in the images. Since some of them align, I think you might be running a different set of images. Can you confirm what the build baseline is that you pulled the images from? I have attached a sample list from our labs for comparison. -Matt From: "Xu, Chenjie" > Date: Friday, March 22, 2019 at 7:25 AM To: "Peters, Matt" >, "Martinez Monroy, Elio" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, The docker image versions in my environment and helm-charts-manifest-no-tests.tgz has been attached. The helm-charts-manifest-no-tests.tgz is built by Shuicheng for the OVSDPDK Upgrade Testing ISO image. Best Regards, Xu, Chenjie From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Thursday, March 21, 2019 11:20 PM To: Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Perfect, I will be cheking my mail for that new ISO. Adding Richo , he is the one that is going to execute the tests. Thanks BR Elio From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, March 21, 2019 9:15 AM To: Lin, Shuicheng >; Cabrales, Ada >; Martinez Monroy, Elio > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, We discussed this in the networking bi-weekly team meeting today. Please re-enable the mlx pmd – re-apply the following patch: https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch Then please rebase to the latest master and build a new load for Ada’s team to start testing Hi Elio, One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 Thanks, Ghada From: Khalil, Ghada Sent: Thursday, March 21, 2019 9:12 AM To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. Can you confirm that the load being used has the mellanox pmd enabled in it? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 21, 2019 9:03 AM To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie for the testing. Hi all, Does it mean greenlight for code merge, or any other test is needed? Here is the patch list: https://review.openstack.org/642672 https://review.openstack.org/642673 Best Regards Shuicheng From: Xu, Chenjie Sent: Thursday, March 21, 2019 5:46 PM To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Duplex_logs.zip Type: application/x-zip-compressed Size: 7326 bytes Desc: Duplex_logs.zip URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Std Controller 2+2.zip Type: application/x-zip-compressed Size: 6743 bytes Desc: Std Controller 2+2.zip URL: From chenjie.xu at intel.com Fri Mar 29 05:32:10 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Fri, 29 Mar 2019 05:32:10 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing In-Reply-To: <0483622846A57742B81A944248DD69042FC28FFD@fmsmsx101.amr.corp.intel.com> References: <151EE31B9FCCA54397A757BC674650F0BA4D1AA8@ALA-MBD.corp.ad.wrs.com> <72A55890-B007-4E93-A74A-291C725B158E@windriver.com> <1466AF2176E6F040BD63860D0A241BBD46CA563A@FMSMSX109.amr.corp.intel.com> <608E4D93-FDFF-4F00-A166-A89EA6683B90@windriver.com> <1466AF2176E6F040BD63860D0A241BBD46CA56BA@FMSMSX109.amr.corp.intel.com> <0483622846A57742B81A944248DD69042FC28FFD@fmsmsx101.amr.corp.intel.com> Message-ID: Hi JP, Could you please run following commands on your compute node to check if the problem in our environment is caused by the same cause? sudo bash virsh list virsh dumpxml $vm_num > vm.xml In my environment, following sections can’t be found in vm.xml and this is the root cause of the problem: I have a workaround for this problem and it may be useful to you. You can find my workaround in the comment #7 in following bug report: https://bugs.launchpad.net/starlingx/+bug/1820378 Best Regards, Xu, Chenjie From: Gomez, Juan P Sent: Friday, March 29, 2019 7:01 AM To: Xu, Chenjie ; Martinez Monroy, Elio ; Peters, Matt ; Khalil, Ghada ; Lin, Shuicheng ; Cabrales, Ada ; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io' ; Zhao, Forrest ; Rowsell, Brent Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Ghada, Ricardo and I were working in different systems ( Duplex and Standard Controller 2+2 ) and We were able to reproduced the issues, bugs have been updated Also We have run the Sanity Test on both configurations with no issues Matt, Also We have attached the logs from both configurations Best Regards, JP From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Wednesday, March 27, 2019 7:59 PM To: Martinez Monroy, Elio >; Peters, Matt >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Rowsell, Brent > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I run the following commands on compute-0. The outputs of commands have been attached. sudo /usr/sbin/dmidecode > dmidecode.txt virsh nodeinfo > nodeinfo.txt /usr/bin/topology > topology.txt grep -i numa /var/log/dmesg > dmesg.txt And the StarlingX is installed with standard 0322 ISO image: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T174230Z/outputs/iso/ Best Regards, Xu, Chenjie From: Martinez Monroy, Elio Sent: Thursday, March 28, 2019 3:36 AM To: Peters, Matt >; Xu, Chenjie >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Rowsell, Brent > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing So, in order to develop our NUMA test cases, we should configure that topology in our VM’s? How can we do it? Do you have the steps? BR Elio From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 27, 2019 1:19 PM To: Martinez Monroy, Elio >; Xu, Chenjie >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Rowsell, Brent > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello, From the output below, this data is taken from a virtual system. In a QEMU/KVM environment, it is not expected to have a NUMA topology unless it has been explicitly configured in the domain configuration of the emulated host. I’m assuming the tests being performed by Chenjie are in a HW lab. This can be confirmed by providing the same set of data for those test systems. Thanks, Matt From: "Martinez Monroy, Elio" > Date: Wednesday, March 27, 2019 at 2:47 PM To: "Peters, Matt" >, "Xu, Chenjie" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" >, Brent Rowsell > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt Just exercising same stuff, please check my outputs from compute-0, please let me know if something else is needed sudo /usr/sbin/dmdecode Password: sudo: /usr/sbin/dmdecode: command not found compute-0:~$ sudo /usr/sbin/dmidecode # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 10 structures occupying 419 bytes. Table at 0x000F6460. Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: SeaBIOS Version: Ubuntu-1.8.2-1ubuntu1 Release Date: 04/01/2014 Address: 0xE8000 Runtime Size: 96 kB ROM Size: 64 kB Characteristics: BIOS characteristics not supported Targeted content distribution is supported BIOS Revision: 0.0 Handle 0x0100, DMI type 1, 27 bytes System Information Manufacturer: QEMU Product Name: Standard PC (i440FX + PIIX, 1996) Version: pc-i440fx-2.5 Serial Number: Not Specified UUID: 71d54a5d-b569-4e1c-83e3-9babf169e824 Wake-up Type: Power Switch SKU Number: Not Specified Family: Not Specified Handle 0x0300, DMI type 3, 21 bytes Chassis Information Manufacturer: QEMU Type: Other Lock: Not Present Version: pc-i440fx-2.5 Serial Number: Not Specified Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: Unknown OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 Handle 0x0400, DMI type 4, 42 bytes Processor Information Socket Designation: CPU 0 Type: Central Processor Family: Other Manufacturer: QEMU ID: A3 06 01 00 FF FB 8B 07 Version: pc-i440fx-2.5 Voltage: Unknown External Clock: Unknown Max Speed: 2000 MHz Current Speed: 2000 MHz Status: Populated, Enabled Upgrade: Other L1 Cache Handle: Not Provided L2 Cache Handle: Not Provided L3 Cache Handle: Not Provided Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Core Count: 6 Core Enabled: 6 Thread Count: 1 Characteristics: None Handle 0x1000, DMI type 16, 23 bytes Physical Memory Array Location: Other Use: System Memory Error Correction Type: Multi-bit ECC Maximum Capacity: 10 GB Error Information Handle: Not Provided Number Of Devices: 1 Handle 0x1100, DMI type 17, 40 bytes Memory Device Array Handle: 0x1000 Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: 10240 MB Form Factor: DIMM Set: None Locator: DIMM 0 Bank Locator: Not Specified Type: RAM Type Detail: Other Speed: Unknown Manufacturer: QEMU Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Rank: Unknown Configured Clock Speed: Unknown Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x1300, DMI type 19, 31 bytes Memory Array Mapped Address Starting Address: 0x00000000000 Ending Address: 0x000BFFFFFFF Range Size: 3 GB Physical Array Handle: 0x1000 Partition Width: 1 Handle 0x1301, DMI type 19, 31 bytes Memory Array Mapped Address Starting Address: 0x00100000000 Ending Address: 0x002BFFFFFFF Range Size: 7 GB Physical Array Handle: 0x1000 Partition Width: 1 Handle 0x2000, DMI type 32, 11 bytes System Boot Information Status: No errors detected Handle 0x7F00, DMI type 127, 4 bytes End Of Table compute-0:~$ virsh nodeinfo CPU model: x86_64 CPU(s): 6 CPU frequency: 3792 MHz CPU socket(s): 1 Core(s) per socket: 6 Thread(s) per core: 1 NUMA cell(s): 1 Memory size: 10485236 KiB compute-0:~$ /usr/bin/topology TOPOLOGY: logical cpus : 6 sockets : 1 cores_per_pkg : 6 threads_per_core : 1 numa_nodes : 1 total_memory : 9.61 GiB memory_per_node : 10.00 GiB LOGICAL CPU TOPOLOGY: cpu_id : 0 1 2 3 4 5 socket_id : 0 0 0 0 0 0 core_id : 0 1 2 3 4 5 thread_id : 0 0 0 0 0 0 CORE TOPOLOGY: cpu_id socket_id core_id thread_id affinity 0 0 0 0 0x1 1 0 1 0 0x2 2 0 2 0 0x4 3 0 3 0 0x8 4 0 4 0 0x10 5 0 5 0 0x20 compute-0:~$ grep -i numa /var/log/dmesg [ 0.000000] No NUMA configuration found From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, March 27, 2019 6:10 AM To: Xu, Chenjie >; Khalil, Ghada >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Rowsell, Brent > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Can you run the following set of commands on your test system compute hosts and provide the output for each? sudo /usr/sbin/dmidecode virsh nodeinfo /usr/bin/topology grep -i numa /var/log/dmesg From: "Xu, Chenjie" > Date: Wednesday, March 27, 2019 at 5:45 AM To: "Peters, Matt" >, Ghada Khalil >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I tried standard 0322 ISO image on 4 bare metals and “NUMA sections are still missing”. The docker images versions and build baseline have been attached. The ISO image link is following: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190322T174230Z/outputs/iso/ Best Regards, Xu, Chenjie From: Xu, Chenjie Sent: Wednesday, March 27, 2019 10:38 AM To: 'Peters, Matt' >; Khalil, Ghada >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, Sorry for misleading! I mean “NUMA sections are still missing”. I have multiple systems experiencing this issue: 1. 0306 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 2. 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals 3. 0305 ISO image on 4 bare metals 4. 0315 ISO image one 1 bare metals The item 1, 2 and 3 use same bare metals. The item 4 use a separate bare metal. I will try 0322 ISO image on 4 bare metals. Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, March 26, 2019 11:10 PM To: Khalil, Ghada >; Xu, Chenjie >; Martinez Monroy, Elio >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Can you clarify this statement? “NUMA sections missing bug still exits”. Did you mean to say that the missing NUMA sections in the domain XML are now present, but you still can’t ping over the vhost port, or are you saying the NUMA sections are still missing? Do you have multiple systems that are experiencing this issue, or is it isolated to a single system that you are having problems with the NUMA topology? I believe you mentioned that you saw the same connectivity issues on a standard load from the mirror, so that still points to a test system / environment issue. As Ghada mentioned, I think the next steps are to get results from the sanity systems with the same load baseline and to test with your custom load on a system that has been proven to work on the standard load. -Matt From: Ghada Khalil > Date: Tuesday, March 26, 2019 at 9:28 AM To: "Xu, Chenjie" >, "Peters, Matt" >, "Martinez Monroy, Elio" >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Has Elio or Rich from the test team tried the new load as well on their systems? Do they see the same issues you reported? I think we need some data for another system to compare. Ada, As part of this thread, I also requested that a VM connectivity test be added to regular sanity so that there is data from the daily cengn builds w/o the new version of ovs-dpdk. Has the sanity suite been updated? Thanks, Ghada From: Xu, Chenjie [mailto:chenjie.xu at intel.com] Sent: Tuesday, March 26, 2019 7:09 AM To: Peters, Matt; Martinez Monroy, Elio; Khalil, Ghada; Lin, Shuicheng; Cabrales, Ada; Perez, Ricardo O Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, I installed StarlingX using the new 0322 ISO image for OVSDPDK Upgrade Testing on 4 bare metals. NUMA sections missing bug still exits: https://bugs.launchpad.net/starlingx/+bug/1820378 This time I update the docker images to latest before installing StarlingX. And the docker images versions and build baseline have been attached. Could you please help review the docker image versions? Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Friday, March 22, 2019 8:31 PM To: Xu, Chenjie >; Martinez Monroy, Elio >; Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hello Chenjie, Comparing the image list to our labs shows a difference in the image IDs (sha), but I’m not sure if that is just a difference in build baselines or an actual difference in the images. Since some of them align, I think you might be running a different set of images. Can you confirm what the build baseline is that you pulled the images from? I have attached a sample list from our labs for comparison. -Matt From: "Xu, Chenjie" > Date: Friday, March 22, 2019 at 7:25 AM To: "Peters, Matt" >, "Martinez Monroy, Elio" >, Ghada Khalil >, "Lin, Shuicheng" >, "Cabrales, Ada" >, "Perez, Ricardo O" > Cc: "'starlingx-discuss at lists.starlingx.io'" >, "Zhao, Forrest" > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Matt, The docker image versions in my environment and helm-charts-manifest-no-tests.tgz has been attached. The helm-charts-manifest-no-tests.tgz is built by Shuicheng for the OVSDPDK Upgrade Testing ISO image. Best Regards, Xu, Chenjie From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Thursday, March 21, 2019 11:20 PM To: Khalil, Ghada >; Lin, Shuicheng >; Cabrales, Ada >; Perez, Ricardo O > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: Re: [Starlingx-discuss] OVS-DPDK Upgrade Testing Perfect, I will be cheking my mail for that new ISO. Adding Richo , he is the one that is going to execute the tests. Thanks BR Elio From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, March 21, 2019 9:15 AM To: Lin, Shuicheng >; Cabrales, Ada >; Martinez Monroy, Elio > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, We discussed this in the networking bi-weekly team meeting today. Please re-enable the mlx pmd – re-apply the following patch: https://github.com/openstack/stx-integ/blob/master/networking/openvswitch/centos/meta_patches/0005-enable-mlx-pmds.patch Then please rebase to the latest master and build a new load for Ada’s team to start testing Hi Elio, One a new build is available, please start testing as per our previous plans. You need to run a networking regression on various NICs – including the mellanox. Testing was planned for about two weeks with the target for the code to merge after testing is complete by April 5. Please provide regular updates. Please also verify if you see the 3 bugs that Chenjie reports below (please test on both a cengn load as well as the load with the ovs-dpdk upgrade). Please note that none of these issues are reproducible in WR labs: https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 Thanks, Ghada From: Khalil, Ghada Sent: Thursday, March 21, 2019 9:12 AM To: 'Lin, Shuicheng'; Xu, Chenjie; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi Shuicheng, There is still testing planned by Ada’s team before merging the code related to networking regression. This will cover the mellanox NIC as well. Can you confirm that the load being used has the mellanox pmd enabled in it? Thanks, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, March 21, 2019 9:03 AM To: Xu, Chenjie; Khalil, Ghada; Liu, ZhipengS; Xie, Cindy; Cabrales, Ada Cc: 'starlingx-discuss at lists.starlingx.io'; Zhao, Forrest; Peters, Matt; Richard, Joseph; Winnicki, Chris; Peng, Peng; Martinez Monroy, Elio; Jones, Bruce E; Qin, Kailun; Guo, Ruijing; Le, Huifeng Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Thanks Chenjie for the testing. Hi all, Does it mean greenlight for code merge, or any other test is needed? Here is the patch list: https://review.openstack.org/642672 https://review.openstack.org/642673 Best Regards Shuicheng From: Xu, Chenjie Sent: Thursday, March 21, 2019 5:46 PM To: Khalil, Ghada >; Liu, ZhipengS >; Xie, Cindy >; Cabrales, Ada > Cc: 'starlingx-discuss at lists.starlingx.io' >; Zhao, Forrest >; Peters, Matt >; Richard, Joseph >; Winnicki, Chris >; Lin, Shuicheng >; Peng, Peng >; Martinez Monroy, Elio >; Jones, Bruce E >; Qin, Kailun >; Guo, Ruijing >; Le, Huifeng > Subject: RE: [Starlingx-discuss] OVS-DPDK Upgrade Testing Hi team, I have finished the Basic Functional Testing for OVSDPDK Upgrade. Please check following summaries: Bug Summary: No bug related to OVSDPDK Upgrade. 3 bugs related to cutting over to container and configuration. https://bugs.launchpad.net/starlingx/+bug/1821150 https://bugs.launchpad.net/starlingx/+bug/1821135 https://bugs.launchpad.net/starlingx/+bug/1820378 The following features have been tested: N/S traffic for FLAT/VLAN network E/W traffic for FLAT/VLAN/VXLAN network (E/W traffic within same host and across hosts) QOS Security Group MTU Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Fri Mar 29 12:43:08 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Fri, 29 Mar 2019 12:43:08 +0000 Subject: [Starlingx-discuss] pep 8 issue need to be fixed In-Reply-To: <93814834B4855241994F290E959305C753057919@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C753057919@SHSMSX104.ccr.corp.intel.com> Message-ID: <20190329124308.aufoetl6ppunxour@yuggoth.org> On 2019-03-29 05:35:06 +0000 (+0000), Liu, ZhipengS wrote: [...] > When I update my patch for stx-integ, it report below errors, > which causes "Verified -1 Zuul" Not sure why we have this issue > now. It is a common issue that I also saw in other patches > submitted recently. Do we need a new ticket to fix this pep8 issue > or just disable B009 and B010? Any comment? [...] Your tox.ini in that repository seems to include the flake8-bugbear plugin (with no version specifier) in the deps list for testenv:pep8. According to https://pypi.org/project/flake8-bugbear/#history they released a new version yesterday (19.3.0). Their changelog indicates they introduced new checks B009, B010 and B011 in that release. One tactic we take to avoid having these sorts of issues in OpenStack is for projects to pick what versions of static analysis tools they're going to use at the start of a release cycle and pin them like flake8-bugbear<19 for the duration of that cycle, then advance the version pin at the start of the next cycle to bring in the latest versions and fix whatever those have started warning about. This minimizes the chances of disruption at later points in the cycle when they may more significantly detract from things like release-focused work. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From serverascode at gmail.com Fri Mar 29 13:38:31 2019 From: serverascode at gmail.com (Curtis) Date: Fri, 29 Mar 2019 09:38:31 -0400 Subject: [Starlingx-discuss] Publish container image list? In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA46BAB1@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA46BAB1@ALA-MBD.corp.ad.wrs.com> Message-ID: On Tue, Mar 26, 2019 at 2:10 PM Penney, Don wrote: > Hi Curtis, > > > > That work is in progress now. We’ve updated the image build tool to record > versions, which will be an input to building the application charts. > Additionally, an upcoming work item will be to publish these records as > part of the CENGN build. > > > As an FYI, this is what my list looks like in YAML: https://github.com/ccollicutt/starlingx-workshop/blob/master/ansible/roles/docker-registry/defaults/main.yml#L8 I'd love to be able to just download that as a release file. My example is a bit different because I'm getting image files from a big tar file I created, but the idea is the same. :) Thanks, Curtis > Cheers, > > Don. > > > > *From:* Curtis [mailto:serverascode at gmail.com] > *Sent:* Tuesday, March 26, 2019 2:07 PM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] Publish container image list? > > > > Hi All, > > > > If we are not already (which maybe we are, this is a big project) I think > it would be useful to publish a list of containers that match up with a > particular release. Otherwise I have to build it on my own anyways (for > example for building out a repeatable workshop setup). > > > > I know we publish an ISO, RPMs, and Helm charts, but it's be nice to have > a list of image and tags to use to be able to populate local docker > registries. Or a way to generate that list from existing artifacts...if it > doesn't exist already that is. > > > > Also, right now my list has many of the stx images as > "dev-centos-master-latest" and I'd like to firm that up with versions if > possible. > > > > Thanks, > > Curtis > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcel at schaible-consulting.de Fri Mar 29 14:03:09 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Fri, 29 Mar 2019 15:03:09 +0100 (CET) Subject: [Starlingx-discuss] Kubernetes Kubelet Server restart Message-ID: <522779436.1548041.1553868189144@communicator.strato.com> Hi, we are using the centos image from 20190325 in a duplex configuration. The controller-1 has the problem that the Kubernetes Kublet Server is restarting multiple times and after some time the controller-1 reboots. Any idea what can be root cause of that behaviour= Thanks Marcel From Don.Penney at windriver.com Fri Mar 29 14:07:26 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Fri, 29 Mar 2019 14:07:26 +0000 Subject: [Starlingx-discuss] pep 8 issue need to be fixed In-Reply-To: <20190329124308.aufoetl6ppunxour@yuggoth.org> References: <93814834B4855241994F290E959305C753057919@SHSMSX104.ccr.corp.intel.com> <20190329124308.aufoetl6ppunxour@yuggoth.org> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA46DA46@ALA-MBD.corp.ad.wrs.com> Al has posted a review for a quick fix to resolve the stx-integ issues: https://review.openstack.org/#/c/648694/1 -----Original Message----- From: Jeremy Stanley [mailto:fungi at yuggoth.org] Sent: Friday, March 29, 2019 8:43 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] pep 8 issue need to be fixed On 2019-03-29 05:35:06 +0000 (+0000), Liu, ZhipengS wrote: [...] > When I update my patch for stx-integ, it report below errors, which > causes "Verified -1 Zuul" Not sure why we have this issue now. It is a > common issue that I also saw in other patches submitted recently. Do > we need a new ticket to fix this pep8 issue or just disable B009 and > B010? Any comment? [...] Your tox.ini in that repository seems to include the flake8-bugbear plugin (with no version specifier) in the deps list for testenv:pep8. According to https://pypi.org/project/flake8-bugbear/#history they released a new version yesterday (19.3.0). Their changelog indicates they introduced new checks B009, B010 and B011 in that release. One tactic we take to avoid having these sorts of issues in OpenStack is for projects to pick what versions of static analysis tools they're going to use at the start of a release cycle and pin them like flake8-bugbear<19 for the duration of that cycle, then advance the version pin at the start of the next cycle to bring in the latest versions and fix whatever those have started warning about. This minimizes the chances of disruption at later points in the cycle when they may more significantly detract from things like release-focused work. -- Jeremy Stanley From Volker.Hoesslin at swsn.de Fri Mar 29 14:53:23 2019 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Fri, 29 Mar 2019 14:53:23 +0000 Subject: [Starlingx-discuss] pre-stable version bevor next release? Message-ID: Hi anybody, i realy love this project but I have some reason to deploy now an working stack. Is there currently an working version or have to wait until new release date? The current stable version isn't working in all details for me, look at discuss "Unrecognized attribute(s) 'port_security_enabled'". Thx, Volker... -------------- next part -------------- An HTML attachment was scrubbed... URL: From michel.thebeau at windriver.com Fri Mar 29 15:09:35 2019 From: michel.thebeau at windriver.com (Michel Thebeau) Date: Fri, 29 Mar 2019 11:09:35 -0400 Subject: [Starlingx-discuss] pre-stable version bevor next release? In-Reply-To: References: Message-ID: <1553872175.13803.23.camel@windriver.com> Hi Volker, I expect your requirements are not compatible with the "latest development branch".  However, an approach you can take is: look for "Sanity Test" emails on this list and grab one that isnt' "fail, fail, fail, fail, ..." Here is a quick summary: 20190328  fail 20190327  simplex fail, dedicated storage fail, Duplex/Standard mostly pass 20190325  mostly pass, simplex fail M On Fri, 2019-03-29 at 14:53 +0000, von Hoesslin, Volker wrote: > Hi anybody, > i realy love this project but I have some reason to deploy now an > working stack. Is there currently an working version or have to wait > until new release date? The current stable version isn’t working in > all details for me, look at discuss “Unrecognized attribute(s) > 'port_security_enabled'”. >   > Thx, > Volker… > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From marcel at schaible-consulting.de Fri Mar 29 15:15:14 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Fri, 29 Mar 2019 16:15:14 +0100 (CET) Subject: [Starlingx-discuss] How to delete all active alarms? Message-ID: <1179826664.1551681.1553872514544@communicator.strato.com> Hi, how can I delete all active alarms and where to find the uuid of the alarms? Thanks Marcel From scott.little at windriver.com Fri Mar 29 15:14:07 2019 From: scott.little at windriver.com (Scott Little) Date: Fri, 29 Mar 2019 11:14:07 -0400 Subject: [Starlingx-discuss] [build] New naming convention for docker images Message-ID: CENGN builds have converted to use the method of building docker images.  The STREAM argument is replacing the OPENSTACK_RELEASE. The result is that docker images have also been renamed. e.g.     stx-nova:dev-centos-master-latest -> stx-nova:master-centos-dev-latest The images build are published in lst files http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ images-centos-dev-latest.lst: docker.io/slittlewrs/stx-nova-api-proxy:master-centos-dev-latest    docker.io/slittlewrs/stx-aodh:master-centos-dev-latest    docker.io/slittlewrs/stx-ironic:master-centos-dev-latest    docker.io/slittlewrs/stx-magnum:master-centos-dev-latest    docker.io/slittlewrs/stx-murano:master-centos-dev-latest    docker.io/slittlewrs/stx-panko:master-centos-dev-latest    docker.io/slittlewrs/stx-barbican:master-centos-dev-latest    docker.io/slittlewrs/stx-ceilometer:master-centos-dev-latest    docker.io/slittlewrs/stx-cinder:master-centos-dev-latest    docker.io/slittlewrs/stx-glance:master-centos-dev-latest    docker.io/slittlewrs/stx-gnocchi:master-centos-dev-latest    docker.io/slittlewrs/stx-heat:master-centos-dev-latest    docker.io/slittlewrs/stx-horizon:master-centos-dev-latest    docker.io/slittlewrs/stx-keystone:master-centos-dev-latest    docker.io/slittlewrs/stx-neutron:master-centos-dev-latest    docker.io/slittlewrs/stx-nova:master-centos-dev-latest images-centos-stable-latest.lst: docker.io/slittlewrs/stx-fm-rest-api:master-centos-stable-latest    docker.io/slittlewrs/stx-mariadb:master-centos-stable-latest    docker.io/slittlewrs/stx-libvirt:master-centos-stable-latest docker.io/slittlewrs/stx-nova-api-proxy:master-centos-stable-latest Note: for you convenience, pending the delivery of a feature that will remove your 'need to know' about these details, we will also retag the stable images as dev images so that you may us the same "master-centos-dev-latest" tag for all images.    e.g. stx-libvirt:master-centos-stable-latest will also be tagged as stx-libvirt:master-centos-dev-latest We are also now publishing the content of the docker images in two files that list content installed vis rpm and via pip... e.g. http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_docker_image_build/outputs/docker-images/stx-libvirt-centos-stable.piplst http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_docker_image_build/outputs/docker-images/stx-libvirt-centos-stable.rpmlst http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_docker_image_build/outputs/docker-images/stx-nova-centos-dev.rpmlst http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_docker_image_build/outputs/docker-images/stx-nova-centos-dev.piplst    ... stx-nova-centos-dev.rpmlst:    ...    libcephfs1-10.2.6-0.el7.tis.7.x86_64    libcgroup-0.41-20.el7.x86_64    libcgroup-tools-0.41-20.el7.x86_64    ... stx-nova-centos-dev.piplst:    ...    netifaces==0.10.9    networkx==2.2    nova==19.1.0.dev59    ... -------------- next part -------------- An HTML attachment was scrubbed... URL: From yang.liu at windriver.com Fri Mar 29 15:24:51 2019 From: yang.liu at windriver.com (Liu, Yang) Date: Fri, 29 Mar 2019 15:24:51 +0000 Subject: [Starlingx-discuss] How to delete all active alarms? In-Reply-To: <1179826664.1551681.1553872514544@communicator.strato.com> References: <1179826664.1551681.1553872514544@communicator.strato.com> Message-ID: <19C65A6E92EA384D809B1772130CD7F8621A26D9@ALA-MBD.corp.ad.wrs.com> To delete using uuid: fm alarm-list --uuid fm alarm-delete The alarm might come back later though with a different uuid. You can also suppress the alarm using alarm id, so it will not be listed in alarm-list until unsupressed: fm event-suppress --alarm_id BR, Yang -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: March-29-19 11:15 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] How to delete all active alarms? Hi, how can I delete all active alarms and where to find the uuid of the alarms? Thanks Marcel _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Tao.Liu at windriver.com Fri Mar 29 15:28:42 2019 From: Tao.Liu at windriver.com (Liu, Tao) Date: Fri, 29 Mar 2019 15:28:42 +0000 Subject: [Starlingx-discuss] How to delete all active alarms Message-ID: <7242A3DC72E453498E3D783BBB134C3E9DDD4913@ALA-MBD.corp.ad.wrs.com> Hi Marcel, Use 'fm alarm-list --uuid' to show uuid Use 'fm alarm-delete ' to delete the alarm The 'fm alarm-delete' command should only be used to clear a stuck alarm. If the alarm condition is still outstanding, it will be raised again by the applications that audit the alarms. Regards, Tao ------------------------------ Message: 7 Date: Fri, 29 Mar 2019 16:15:14 +0100 (CET) From: Marcel Schaible To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] How to delete all active alarms? Message-ID: <1179826664.1551681.1553872514544 at communicator.strato.com> Content-Type: text/plain; charset=UTF-8 Hi, how can I delete all active alarms and where to find the uuid of the alarms? Thanks Marcel ------------------------------ 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 10, Issue 172 ************************************************** From marcel at schaible-consulting.de Fri Mar 29 15:41:02 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Fri, 29 Mar 2019 16:41:02 +0100 (CET) Subject: [Starlingx-discuss] Why are some services are not enabled by default? Message-ID: <548571452.1775559.1553874062995@communicator.strato.com> Hi, Our configuration: Duplex, Image 20190325, bare metal 1. I just ran into the problem that the drbd service is not enabled at boot time. Is this a Problem with our Installation or is it intended to manually enable/start this service? 2. In the boot log we get this warning: Checking connectivity to controller-platform-nfs for up to 70 seconds over interface 172.27.1.4 Is this a problem and if yes how to fix it? 3. In the boot log of controller-1 I see [ 68.257083] controller_config[8075]: ***************************************************** [ 68.268176] controller_config[8075]: ***************************************************** [ 68.278198] controller_config[8075]: Unable to retrieve installation uuid from active controller [ 68.289118] controller_config[8075]: ***************************************************** [ 68.300167] controller_config[8075]: ***************************************************** [ 68.310145] controller_config[8075]: Pausing for 5 seconds… Any idea? Thanks Marcel From serverascode at gmail.com Fri Mar 29 15:41:11 2019 From: serverascode at gmail.com (Curtis) Date: Fri, 29 Mar 2019 11:41:11 -0400 Subject: [Starlingx-discuss] Edge Computing Use Case, Deployment Advice Needed In-Reply-To: References: Message-ID: I added some points/questions inline. On Thu, Mar 28, 2019 at 6:02 PM Arce Moreno, Abraham < abraham.arce.moreno at intel.com> wrote: > Hi StarlingX Community, > > > > We need your advice to determine the most appropriate way to migrate an > existing demo deployed via containers to StarlingX infrastructure with > cloud features in mind (e.g. zero touch provisioning). > > > > We are integrating this demo in our spare time to ramp up in cloud > technologies and one of its imperatives is a working solution. It started > as a use case proposal around unmanned aerial systems [0], then decided to > avoid some of the complexity involved in flying the drones, and finally > landed it as a use case around home automation / smart cities at the > network edge. > First off, I'd like to let people know that we are planning on doing some kind of "edge" proof-of-concept with Packet.com resources, so perhaps the project you discuss could fit in with that. I'm sure we'll chat about it at some point here. At the next TSC meeting we'll discuss how to get the packet projects off the ground, so feel free to attend. :) > > Three key aspects for you to consider: > > > > - Edge computing foundation is all about “things” interchanging “data” > with “servers”, same foundation when both use case proposals were > envisioned. > > - ”Data” will include “video streaming” pipelines, considered in both use > case proposals. > > - “Video streaming” pipelines will serve as an input to “machine learning > / deep learning” services offloaded to different hardware (CPU, GPU, VPU, > FPGA) also considered in both use case proposal, which gives an interesting > workload to showcase some of the StarlingX characteristics: reliability, > scalability and ultra-low latency. > > > > [ General Architecture ] > > > > The high level architecture [2] is compromised of the following components > (naming still under review): > > - Core Applications > > - Services > > > > [ Core Applications ] > > > > Core Applications [3] give the foundation of the demo, the following have > been integrated: > > > > - Home Assistant: Open Source Home Automation > > - InfluxDB: Time Seria Database Platform > > - Grafana: Data Visualization and Monitoring > > - Mosquitto: MQTT Message Broker > > - Glances: System Monitoring Tool > > - Portainer: Docker Environment Manager > > - Node-RED: Programming Tool for Hardware Devices > > - Netdata: Systems and Applications Monitoring > > - Plex: Media Server > > - motionEye: Video Signal Monitoring > > > > [ Services ] > > > > Services [4] are designed to perform a specific function in a specific > device for a specific period of time (on demand) and will work with other > micro services to form higher-level decisions, from a machine learning > ‘bot’ service that use time-series data from the different sensors for > simple control and personalization to a deep learning computer vision > service that use existing network video recorder streams for video > surveillance and video analytics. > > > > This demo has currently integrated samples of computer vision applications > with the following services: > > - OpenCV (Computer Vision) > > - Haar Cascades > > - OpenVINO (Computer Vision) > > - Gstreamer (Video Stream) > > - Mjpeg- Streamer (Video Stream) > > - You Only Look Once (Object Detection) > > > > This demo has currently integrated the following acceleration resources: > > - GPU > > - VPU (Movidius NCS) > I would not expect a USB device like the Movidius NCS to be available in most STX deployments, but maybe? > > Once demo has a solid foundation and stability with these first services, > the following components are next to be integrated: > > - FPGA > > - Intel Accelerated Stack > > > > [ StarlingX Deployment ] [ Offload ] > > > > What would be the preferred way to deploy this use case proposal in > StarlingX? We understand the following options are available including its > preference: > > > > 1. Via Kubernetes (Not Preferred) > > 2. Via Virtual Machine (Preferred) > > 3. Via Bare Metal (Preferred) > > > > Are the above options and their preference, correct? If not, can you > please give us some hints behind your answer. > >From my standpoint, I think #3 would be the least common option. #2 would be a good place to start, but I don't think #1 is "not preferred", I guess it depends on where these preferences are coming from. > > > [ StarlingX Deployment ] [ Provisioning ] > > > > As mentioned at the beginning, another of our imperatives, is to exercise > zero touch provisioning. > > > > Does it makes sense to split the provisioning in 2 parts based in the > required time for the demo components to live? > > - The core applications 100% uptime > > - Services on demand / 100 uptime in some cases > By zero touch provisioning do you just mean automation using IaaS APIs? eg. the docker compose file you link to? Or something else? Thanks, Curtis > > > Is there any other cloud feature we would want consider, to take a look > and use for this first version of the demo? > > > > [ StarlingX Deployment ] [ Provisioning ] [ Core Applications ] > > > > Would it make sense to create a cloud image with the core applications > integrated? If not, what would be your best approach for the core > applications? > > > [ StarlingX Deployment ] [ Provisioning ] [ Services ] > > > > Since Services will be on demand, there might be some options: > > > > - Service running in containers under a virtual machine / bare > metal > > - Services running in single virtual machines > > - Any other? > > > > This part is the most important for the demo since user experience might > be affected (e.g. time taken for the system to start a face recognition > service under camera one) > > > > [ Thanks ] > > > > We appreciate your time to read this email and your support so we can > understand the best provisioning architecture for the use case proposal / > demo. One of the additional things we are working on is a workshop taking > this learning with the final objective to deploy in StarlingX in community > events, still in an early development phase [5]. > > > > [0] > https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Unmanned_Aircraft_Systems_.28Drones.29 > > [1] > https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Smart_Home > > [2] https://github.com/bacabhome/bacabhome > > [3] https://github.com/bacabhome/bacabhome/blob/master/docker-compose.yml > > [4] https://github.com/bacabhome/bacabhome/tree/master/services > > [5] http://bit.ly/SmartHomeSolution > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Fri Mar 29 16:07:23 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 29 Mar 2019 16:07:23 +0000 Subject: [Starlingx-discuss] pre-stable version bevor next release? In-Reply-To: <1553872175.13803.23.camel@windriver.com> References: <1553872175.13803.23.camel@windriver.com> Message-ID: <9A85D2917C58154C960D95352B22818BD070A0AD@fmsmsx123.amr.corp.intel.com> Following on - Volker, are you using the October release image (2018.10)? Michel is right, if you're using the tip of development (or near it), that is very much a moving target right now. brucej -----Original Message----- From: Michel Thebeau [mailto:michel.thebeau at windriver.com] Sent: Friday, March 29, 2019 8:10 AM To: von Hoesslin, Volker ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] pre-stable version bevor next release? Hi Volker, I expect your requirements are not compatible with the "latest development branch".  However, an approach you can take is: look for "Sanity Test" emails on this list and grab one that isnt' "fail, fail, fail, fail, ..." Here is a quick summary: 20190328  fail 20190327  simplex fail, dedicated storage fail, Duplex/Standard mostly pass 20190325  mostly pass, simplex fail M On Fri, 2019-03-29 at 14:53 +0000, von Hoesslin, Volker wrote: > Hi anybody, > i realy love this project but I have some reason to deploy now an > working stack. Is there currently an working version or have to wait > until new release date? The current stable version isn’t working in > all details for me, look at discuss “Unrecognized attribute(s) > 'port_security_enabled'”. >   > 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 serverascode at gmail.com Fri Mar 29 16:52:57 2019 From: serverascode at gmail.com (Curtis) Date: Fri, 29 Mar 2019 12:52:57 -0400 Subject: [Starlingx-discuss] Remote access to APIs, Horizon Message-ID: Hi All, Are there docs or what is the current thinking around remote access of APIs and Horizon for OpenStack deployments in STX? I looked around a bit but might of missed it if there are some. I see endpoints with cluster ips and a nodeport for Horizon on port 31000, after that I'm outta the loop. :) Thanks, Curtis -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Fri Mar 29 17:05:59 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 29 Mar 2019 17:05:59 +0000 Subject: [Starlingx-discuss] DRAFT release policy In-Reply-To: References: <9A85D2917C58154C960D95352B22818BD0709720@fmsmsx123.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BD070A26A@fmsmsx123.amr.corp.intel.com> Dean, Glenn - thank you for the feedback. I agree with it. There is also some feedback in the etherpad. I'm going to respond to both sets in the etherpad and try to improve the policy and the wording. https://etherpad.openstack.org/p/stx-release-policy-draft Thanks! brucej -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Thursday, March 28, 2019 7:29 PM To: Seiler, Glenn Cc: Jones, Bruce E ; starlingx-discuss Subject: Re: [Starlingx-discuss] DRAFT release policy On Thu, Mar 28, 2019 at 6:39 PM Seiler, Glenn wrote: > 1- We need to move away from time-based releases > 2- We need to do twice a year releases. This stmt, by definition, implies a time-gated release. Maybe it isn’t a specific date, but it is still time-gated. The wording does need work, yes. After a short conversation with Bruce this afternoon (Bruce, correct me if I'm wrong here) I came away with the intention being more of increasing the lag from OpenStack releases rather than separating completely from the OpenStack release cycle which is likely to stay at approx 6 months for a while (that's a rabbit hole under the bike shed I'd like to avoid just now). > As a nascent project, I think we need to show gradual and consistent progress. ++ > I did listen to much of the release team meeting today, and realize the trade-offs between big-rocks and timing are very difficult. > > Given the difficult choice of functionality versus timing, I personally think we need to show progress in getting to Stein and a container based distribution as major milestones in 1H and perhaps defer the Distributed Cloud capability to a 2H release. > > I don’t see anything intrinsically wrong with moving a specific date out; it happens all the time. But I also think a release should have some gate; i.e. we don’t move out of 1H. And if some functionality isn’t ready, then we move the functionality to another release in 2H. We took a stab at estimating and missed, making adjustments now is normal and to be expected. I agree with considering pushing distcloud to the next release because it is a) new functionality, and b) devs overlap with the container work and I think making the k8s infrastructure rock solid is much more important. If we are too far off with system stability the ramifications will be harder to overcome than delaying a new feature. > Anyway, that would be my vote, if I have one. You totally have a voice as part of the community, I would like to hear from more folks here... dt -- Dean Troyer dtroyer at gmail.com From bruce.e.jones at intel.com Fri Mar 29 18:10:04 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 29 Mar 2019 18:10:04 +0000 Subject: [Starlingx-discuss] DRAFT release policy In-Reply-To: <9A85D2917C58154C960D95352B22818BD070A26A@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BD0709720@fmsmsx123.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BD070A26A@fmsmsx123.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BD070A293@fmsmsx123.amr.corp.intel.com> I've updated the etherpad with changes that reflect the current feedback. Please review and add any additional feedback there. Thank you! https://etherpad.openstack.org/p/stx-release-policy-draft brucej -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Friday, March 29, 2019 10:06 AM To: Dean Troyer ; Seiler, Glenn Cc: starlingx-discuss Subject: Re: [Starlingx-discuss] DRAFT release policy Dean, Glenn - thank you for the feedback. I agree with it. There is also some feedback in the etherpad. I'm going to respond to both sets in the etherpad and try to improve the policy and the wording. https://etherpad.openstack.org/p/stx-release-policy-draft Thanks! brucej -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Thursday, March 28, 2019 7:29 PM To: Seiler, Glenn Cc: Jones, Bruce E ; starlingx-discuss Subject: Re: [Starlingx-discuss] DRAFT release policy On Thu, Mar 28, 2019 at 6:39 PM Seiler, Glenn wrote: > 1- We need to move away from time-based releases > 2- We need to do twice a year releases. This stmt, by definition, implies a time-gated release. Maybe it isn’t a specific date, but it is still time-gated. The wording does need work, yes. After a short conversation with Bruce this afternoon (Bruce, correct me if I'm wrong here) I came away with the intention being more of increasing the lag from OpenStack releases rather than separating completely from the OpenStack release cycle which is likely to stay at approx 6 months for a while (that's a rabbit hole under the bike shed I'd like to avoid just now). > As a nascent project, I think we need to show gradual and consistent progress. ++ > I did listen to much of the release team meeting today, and realize the trade-offs between big-rocks and timing are very difficult. > > Given the difficult choice of functionality versus timing, I personally think we need to show progress in getting to Stein and a container based distribution as major milestones in 1H and perhaps defer the Distributed Cloud capability to a 2H release. > > I don’t see anything intrinsically wrong with moving a specific date out; it happens all the time. But I also think a release should have some gate; i.e. we don’t move out of 1H. And if some functionality isn’t ready, then we move the functionality to another release in 2H. We took a stab at estimating and missed, making adjustments now is normal and to be expected. I agree with considering pushing distcloud to the next release because it is a) new functionality, and b) devs overlap with the container work and I think making the k8s infrastructure rock solid is much more important. If we are too far off with system stability the ramifications will be harder to overcome than delaying a new feature. > Anyway, that would be my vote, if I have one. You totally have a voice as part of the community, I would like to hear from more folks here... 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 Frank.Miller at windriver.com Fri Mar 29 18:22:30 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Fri, 29 Mar 2019 18:22:30 +0000 Subject: [Starlingx-discuss] Request use of StarlingX BugTemplate Message-ID: Hello StarlingX Team: I am noticing that some Launchpad bugs (example [1]) are not using the StarlingX template. Please use our project template [2] as it has some additional helpful fields including branch/pull time etc. For reference this can be found on the project's Defect Handling wiki [3]. Thank-you. Frank [1] https://bugs.launchpad.net/starlingx/+bug/1822212 [2] https://wiki.openstack.org/wiki/StarlingX/BugTemplate [3] https://wiki.openstack.org/wiki/StarlingX/Defect_Handling_Process -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Fri Mar 29 18:43:31 2019 From: serverascode at gmail.com (Curtis) Date: Fri, 29 Mar 2019 14:43:31 -0400 Subject: [Starlingx-discuss] pre-stable version bevor next release? In-Reply-To: References: Message-ID: On Fri, Mar 29, 2019 at 10:55 AM von Hoesslin, Volker < Volker.Hoesslin at swsn.de> wrote: > Hi anybody, > > i realy love this project but I have some reason to deploy now an working > stack. Is there currently an working version or have to wait until new > release date? The current stable version isn’t working in all details for > me, look at discuss “Unrecognized attribute(s) 'port_security_enabled'”. > > > With regards to port security, I tried to write this email a couple times, it's tough b/c I don't know the history, but here are my thoughts: - Security groups are effectively disabled in stx (noop driver), at least in my deployment from an ISO from last week - This is probably for performance reasons, ie. iptables, but I'm not sure of the history - Maybe it's time to revisit security groups? eg. k8s is there and uses iptables, or maybe openflow based driver would be an option...or other? - Likely we (the project) just need to make sure it gets properly documented, if it's not already Maybe some others with more history will chip in. :) Thanks, Curtis > Thx, > > Volker… > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcel at schaible-consulting.de Fri Mar 29 19:13:03 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Fri, 29 Mar 2019 20:13:03 +0100 (CET) Subject: [Starlingx-discuss] DUPLEX: Controller-1 is not adding nova-local on initial unlock Message-ID: <344066004.1781399.1553886783759@communicator.strato.com> Image centos 20190325 Duplex Hi, following the instructions from https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnAIODX the controller-1 is not adding the nova-local and osd is in the state "configuring-on-unlock" In the boot log I see a problem on Controller-1 to get the uuid from the active controller-0: [ 20.549131] controller_config[7585]: Checking connectivity to controller-platform-nfs for up to 70 seconds over interface 172.27.1.4 Starting Titanium Cloud libvirt QEMU cleanup... [ 20.581204] controller_config[7585]: ***************************************************** [ OK ] Started Titanium Cloud libvirt QEMU cleanup. [ 20.611110] controller_config[7585]: ***************************************************** [ 20.632070] controller_config[7585]: Unable to retrieve installation uuid from active controller [ 20.643064] controller_config[7585]: ***************************************************** [ 20.654068] controller_config[7585]: ***************************************************** [ 20.665357] controller_config[7585]: Pausing for 5 seconds... [ OK ] Started Crash recovery kernel arming. [ OK ] Started Titanium Cloud Affine Platform. Additionally in the Web-UI I see the following: nova-local adding (on unlock) - 0.0 0.0 0 0 and the related PV lists: /dev/nvme0n1p5 Info UUID 280ce844-d5d5-4f26-bc80-2b9f64836b93 State adding Type partition Volume Group Name nova-local Physical Volume UUID None Physical Volume Name /dev/nvme0n1p5 Physical Volume Size 0 bytes Physical Extents Total 0 Physical Extents Allocated 0 Is this normal that the size are in this Phase are 0GB? I have configured them with 500G. The Output from "system host-list": +----+--------------+-------------+----------------+-------------+--------------+ | id | hostname | personality | administrative | operational | availability | +----+--------------+-------------+----------------+-------------+--------------+ | 1 | controller-0 | controller | unlocked | enabled | available | | 5 | controller-1 | controller | locked | disabled | offline | +----+--------------+-------------+----------------+-------------+--------------+ and "ceph -s": [wrsroot at controller-0 ~(keystone_admin)]$ ceph -s cluster 1769254c-c103-460e-afb3-c8368993b91a health HEALTH_WARN 448 pgs degraded 448 pgs stuck degraded 448 pgs stuck unclean 448 pgs stuck undersized 448 pgs undersized recovery 1116/2232 objects degraded (50.000%) monmap e1: 1 mons at {controller=172.27.1.2:6789/0} election epoch 5, quorum 0 controller osdmap e24: 2 osds: 1 up, 1 in flags sortbitwise,require_jewel_osds pgmap v1056: 448 pgs, 7 pools, 1588 bytes data, 1116 objects 76376 kB used, 952 GB / 952 GB avail 1116/2232 objects degraded (50.000%) 448 active+undersized+degraded Any idea or hint is welcome! Thanks Marcel From Al.Bailey at windriver.com Fri Mar 29 20:12:30 2019 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Fri, 29 Mar 2019 20:12:30 +0000 Subject: [Starlingx-discuss] What is the new openstack command to create an stack? In-Reply-To: References: <8557B550001AFB46A43A0CCC314BF85153CAF169@FMSMSX108.amr.corp.intel.com> <03D458D5BAFF6041973594B00B4E58CE5D68E6B4@CRSMSX104.amr.corp.intel.com> <8557B550001AFB46A43A0CCC314BF85153CAF1A9@FMSMSX108.amr.corp.intel.com> Message-ID: A review is up for this bug: https://review.openstack.org/#/c/648767/ Al -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Thursday, March 28, 2019 4:03 PM To: Curtis Cc: Alonso, Juan Carlos; Hernandez Gonzalez, Fernando; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] What is the new openstack command to create an stack? On Thu, Mar 28, 2019 at 1:30 PM Curtis wrote: > I'm guessing you are missing python-heatclient. Yup... >> From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] >> $openstack stack create --template ${stack_name} --parameter "NetID=${net_id}" >> openstack: 'stack create…’ is not an openstack command. This means that the plugin that implements the stack commands (python-heatclient) is not installed. 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 Don.Penney at windriver.com Fri Mar 29 21:05:16 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Fri, 29 Mar 2019 21:05:16 +0000 Subject: [Starlingx-discuss] StarlingX container images: pike/master migrated to stable/dev Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA46DD08@ALA-MBD.corp.ad.wrs.com> Hi folks, For the interest of any who are building images, we've migrated from pike/master naming to stable/dev build streams. This should help clarify the builds, as there has been some confusion here or there due to the pike/master naming convention. Build stream definitions: * stable: The "stable" build stream is analogous to the previous "pike" image builds. This build uses an stx-centos base image that is configured to have yum repo access to the StarlingX build output for RPM installation. In addition, once Stein is released, we'll setup stable image builds for the Openstack services that point to stable/stein branches. * dev: The "dev" build stream is analogous to the previous "master" image builds, and reflects that these images are generally "bleeding edge" images. The build wiki has been updated to reflect these changes: https://wiki.openstack.org/wiki/StarlingX/Containers/BuildingImages As per the email from Scott earlier this afternoon, CENGN has been updated to build the stable and dev images. The sysinv and chart default image tags have been updated to point to the new master-centos-dev-latest ($BRANCH-$OS-$BUILD_STREAM-$VERSION) tag with the following review: https://review.openstack.org/#/c/648756/ The earlier pike and master build config files will be removed in the next week or two. Please let me know if there are any questions. Cheers, Don. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Fri Mar 29 21:50:18 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 29 Mar 2019 21:50:18 +0000 Subject: [Starlingx-discuss] DUPLEX: PXE Image does not include the ixgbevf In-Reply-To: <139115820.1489232.1553779489590@communicator.strato.com> References: <1592707842.1434226.1553698260345@communicator.strato.com> <9700A18779F35F49AF027300A49E7C765FEA1BBF@SHSMSX101.ccr.corp.intel.com> <139115820.1489232.1553779489590@communicator.strato.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4D354D@ALA-MBD.corp.ad.wrs.com> Hi Marcel, Yes the ixgbevf driver is included in the host iso, but not in the installer image as you've discovered. As Shuicheng points out, it can be added. Can you include the driver based on Shuicheng's instructions and verify that it is working on your system? Once confirmed, you can open a Story in storyboard to have the change pushed to the master branch. https://storyboard.openstack.org/#!/project_group/86 Thanks, Ghada -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Thursday, March 28, 2019 9:25 AM To: Lin, Shuicheng; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] DUPLEX: PXE Image does not include the ixgbevf Hi Shuicheng, thanks fpr your help. We are using an Artesyn Maxcore box and need the VF drivers for booting our controller-1. For my understanding: After the the controller-1 has booted from PXE and is getting configured via controller-0, are the VF drivers then loaded? Thanks Marcel > "Lin, Shuicheng" hat am 28. März 2019 um 01:24 geschrieben: > > > Hi Marcel, > Yes, ixgbevf driver is not included in PXE image. Do we need virtual function support during PXE boot stage? > If so, we could add VF drivers to PXE image. > To add the driver to pxe image, we need modify update-pxe-network-installer script in cgcs-root/build-tools. > And follow the build instruction in below Wiki to generate the new pxe image. > https://docs.starlingx.io/developer_guide/latest/index.html > > > Best Regards > Shuicheng > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Wednesday, March 27, 2019 10:51 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] DUPLEX: PXE Image does not include the ixgbevf > > Hi, > > I just installed the image from 2019-03-25 and trying to install and configure the controller-1. > > It seems like that the PXEimage does not include the Intel driver ixgbevf. > > Is this intended and what is the recommended procedure to get this module into the pxe image? > > Thanks > > Marcel > > _______________________________________________ > 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 juan.carlos.alonso at intel.com Sat Mar 30 17:17:49 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Sat, 30 Mar 2019 17:17:49 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190329 Message-ID: <8557B550001AFB46A43A0CCC314BF85153CAF674@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Mar-29 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup Manual [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 55 TCs [FAIL] Sanity Platform 07 TCs [FAIL] TOTAL: [ 63 TCs FAIL ] AIO - Duplex Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 51 TCs [PASS] | 01 TCs [FAIL] Sanity Platform 04 TCs [PASS] | 01 TCs [FAIL] TOTAL: [ 56 TCs PASS | 02 TCs FAIL ] Standard - Local Storage (2+2) Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 41 TCs [PASS] | 11 TCs [FAIL] Sanity Platform 04 TCs [PASS] | 01 TCs [FAIL] TOTAL: [ 46 TCs PASS | 12 TCs FAIL ] Standard - Dedicated Storage (2+2+2) Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 16 TCs [PASS] | 36 TCs [FAIL] Sanity Platform 04 TCs [PASS] | 01 TCs [FAIL] TOTAL: [ 21 TCs PASS | 37 TCs FAIL ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [FAIL] Sanity Platform 07 TCs [FAIL] TOTAL: [ 04 TCs PASS | 57 TCs FAIL ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 51 TCs [PASS] | 01 TCs [FAIL] Sanity Platform 05 TCs [PASS] TOTAL: [ 61 TCs PASS | 01 TCs FAIL ] Standard - Local Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 19 TCs [PASS] | 33 TCs [FAIL] Sanity Platform 05 TCs [PASS] TOTAL: [ 29 TCs PASS | 33 TCs FAIL ] Standard - Dedicated Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 51 TCs [PASS] | 01 TCs [FAIL] Sanity Platform 05 TCs [PASS] TOTAL: [ 61 TCs PASS | 01 TCs FAIL ] ------------------------------------------------------------------ Simplex BM and Virtual - application-apply fails at 95% ceilometer pod Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1820928 Standard Dedicated Storage BM and Virtual - Could not create VMs Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1821841 All Configurations BM and Virtual - python-heatclient package is not currently installed on ISO. Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1822200 All Configurations BM and Virtual - Console of instances in Horizon is not available Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1822212 ------------------------------------------------------------------ This is the list of test cases executed: https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: