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