[Starlingx-discuss] Starlingx-discuss Digest, Vol 7, Issue 45

Tue Dec 11 01:43:42 UTC 2018

Hi chenzz

You can get a china mainland customized repo, baidu  repo 清华.  You will get expected tool.

BR!

Martin, Chen
SSG OTC, Software Engineer
021-61164330

-----Original Message-----
From: starlingx-discuss-request at lists.starlingx.io [mailto:starlingx-discuss-request at lists.starlingx.io] 
Sent: Tuesday, December 11, 2018 9:32 AM
To: starlingx-discuss at lists.starlingx.io
Subject: Starlingx-discuss Digest, Vol 7, Issue 45

Send Starlingx-discuss mailing list submissions to
	starlingx-discuss at lists.starlingx.io

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
or, via email, send a message with subject or body 'help' to
	starlingx-discuss-request at lists.starlingx.io

You can reach the person managing the list at
	starlingx-discuss-owner at lists.starlingx.io

When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..."

Today's Topics:

   1. [ Test ] Meeting agenda - 12/11/2018 (Cabrales, Ada)
   2. Re: [build] CentOS 7.6 rebase into	feature	branch (Lin, Shuicheng)
   3. Re: CentOS 7.6 upgrade (Lin, Shuicheng)
   4. Re: Problems in build StatlingX mirror. Asking	for help. (chenzz)

----------------------------------------------------------------------

Message: 1
Date: Mon, 10 Dec 2018 22:27:04 +0000
From: "Cabrales, Ada" <ada.cabrales at intel.com>
To: "'starlingx-discuss at lists.starlingx.io'"
	<starlingx-discuss at lists.starlingx.io>
Subject: [Starlingx-discuss] [ Test ] Meeting agenda - 12/11/2018
Message-ID:
	<4F6AACE4B0F173488D033B02A8BB5B7E7CD4710D at FMSMSX114.amr.corp.intel.com>

Content-Type: text/plain; charset="us-ascii"

Testing team agenda for 12/11/2018

   * Test case template - Numan
   * proposal for an unified test suite - Jose
   * Sanity testing: coverage improvements - JC
   * Opens

Regards
Ada

------------------------------

Message: 2
Date: Tue, 11 Dec 2018 00:30:24 +0000
From: "Lin, Shuicheng" <shuicheng.lin at intel.com>
To: Dean Troyer <dtroyer at gmail.com>, "McKenna, Jason"
	<Jason.McKenna at windriver.com>
Cc: "starlingx-discuss at lists.starlingx.io"
	<starlingx-discuss at lists.starlingx.io>
Subject: Re: [Starlingx-discuss] [build] CentOS 7.6 rebase into
	feature	branch
Message-ID:
	<9700A18779F35F49AF027300A49E7C765FE5548E at SHSMSX101.ccr.corp.intel.com>

Content-Type: text/plain; charset="utf-8"

Thanks Dean for help create the feature branch.

Hi Jason,
All CentOS 7.6 related code will be submitted to feature branch.

Best Regards
Shuicheng

-----Original Message-----
From: Dean Troyer [mailto:dtroyer at gmail.com]
Sent: Tuesday, December 11, 2018 3:02 AM
To: McKenna, Jason <Jason.McKenna at windriver.com>
Cc: starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] [build] CentOS 7.6 rebase into feature branch

On Mon, Dec 10, 2018 at 7:28 AM McKenna, Jason <Jason.McKenna at windriver.com> wrote:
> I’m starting to see some code reviews come through which have to do with the rebase to CentOS 7.6.  When these come through, please ensure they are against the feature branch and not the “master” branch.  I do not see the feature branch yet created, but I’m assuming it will be called “f/centos76”.  There is an AR to creates the branch pending (meeting minutes “Notes: Weekly StarlingX non-OpenStack Distro meeting, 12/5”).

The f/centos76 branch has been created in stx-integ stx-root stx-tools stx-upstream.

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

------------------------------

Message: 3
Date: Tue, 11 Dec 2018 00:54:37 +0000
From: "Lin, Shuicheng" <shuicheng.lin at intel.com>
To: "Xie, Cindy" <cindy.xie at intel.com>,
	"starlingx-discuss at lists.starlingx.io"
	<starlingx-discuss at lists.starlingx.io>
Subject: Re: [Starlingx-discuss] CentOS 7.6 upgrade
Message-ID:
	<9700A18779F35F49AF027300A49E7C765FE555C0 at SHSMSX101.ccr.corp.intel.com>

Content-Type: text/plain; charset="utf-8"

Thanks Cindy.
I have added the detail task list, and some more description in the story.
https://storyboard.openstack.org/#!/story/2004522

Best Regards
Shuicheng

-----Original Message-----
From: Xie, Cindy
Sent: Monday, December 10, 2018 5:12 PM
To: Lin, Shuicheng <shuicheng.lin at intel.com>; starlingx-discuss at lists.starlingx.io
Subject: RE: CentOS 7.6 upgrade

Shuicheng,
>>> I will create another story to track these srpm.
There is already one storyboard for sRPM upgrade to 7.6: https://storyboard.openstack.org/#!/story/2004522. What you need to do is to add tasks for each sRPM needs upgrade.

Thx. - cindy

-----Original Message-----
From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com]
Sent: Monday, December 10, 2018 2:41 PM
To: starlingx-discuss at lists.starlingx.io
Subject: [Starlingx-discuss] CentOS 7.6 upgrade

Hi all,
I attached the srpm list we plan to upgrade for you reference.
These packages are downloaded with current repo lst + new created CentOS 7.6 repo [0].

There are total 86 srpm in our rpms list now, and 51 of them will be upgraded.
Kernel upgrade will be done at master with story [1].
Other 49 srpm will be done at feature branch, which is not created yet.
I will create another story to track these srpm.
Please help review attached doc and share me your thought.
Thanks.

[0]: https://review.openstack.org/623975
[1]: https://storyboard.openstack.org/#!/story/2004521

Best Regards
Shuicheng

------------------------------

Message: 4
Date: Tue, 11 Dec 2018 09:31:33 +0800
From: chenzz <chenzz at certusnet.com.cn>
To: starlingx-discuss <starlingx-discuss at lists.starlingx.io>
Subject: Re: [Starlingx-discuss] Problems in build StatlingX mirror.
	Asking	for help.
Message-ID: <201812110931334306841 at certusnet.com.cn>
Content-Type: text/plain; charset="gb2312"

Hi,

I’m en engineer from CertusNet. At present, we are developing edge computing terminal products that we need to use StarlingX.

I have some problems when deploying the StarlingX, when I made the StarlingX ISO, I have downloaded the source code library and run it with ‘repo init -u https://git.starlingx.io/stx-manifest 

 -m default.xml’, the system report:

Then i have configured the HTTP proxy, but the error was still reported.

Please help me check this problem. Thank you. 

 by the way do you have StaringX internal discussion groups such like Wechat group 

Bill chen | CertusNet
Building 18, No. 699-22 Xuanwu Avenue, Xuanwu District, Nanjing, 210042, P.R.China
Tel: +86 25 6642 3768 -XXXX  Mobile: +86 15295592415
Web: www.certusnet.com.cn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20181211/453d762d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: InsertPic_(12-11-09-30-05).png
Type: image/png
Size: 325 bytes
Desc: not available
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20181211/453d762d/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: InsertPic_BDE4(12-11-09-30-05).png
Type: image/png
Size: 3902 bytes
Desc: not available
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20181211/453d762d/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: InsertPic_25EC(12-11-09-30-05).png
Type: image/png
Size: 3354 bytes
Desc: not available
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20181211/453d762d/attachment-0002.png>

------------------------------

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 7, Issue 45
************************************************