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