[Starlingx-discuss] <StarlingX-Discuss> StarlingX 2018.10 without DPDK query

Fri Jun 21 01:00:13 UTC 2019

Hi Team,

Can someone please provide any pointer to resolve the issue.

Regards
Anirudh Gupta
________________________________
From: Anirudh Gupta
Sent: Thursday, June 20, 2019 6:55:15 PM
To: Zhao, Forrest; Xie, Cindy; Jones, Bruce E; Winnicki, Chris; Ildiko Vancsa; Miller, Frank; Arce Moreno, Abraham; Hernandez Gonzalez, Fernando; yong.hu at intel.com; Khalil, Ghada
Cc: starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io
Subject: RE: <StarlingX-Discuss> StarlingX 2018.10 without DPDK query

Hi Cindy, Yong, Ghada & Team,

I need to create AIO 2018.10 Simplex Bare Metal Setup.
As discussed in the mail chain, I have arranged a server with DPDK NIC and tried installing the ISO downloaded from the link

http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/outputs/iso/

The server configuration is as below:

CPU core – 16
Hard disk – 2 Hardisk each of 930GB
RAM – 64 GB
DPDK supported NIC – Yes

controller-0:~$ lspci | grep -i ethernet
03:00.0 Ethernet controller: Intel Corporation Ethernet Connection X552/X557-AT 10GBASE-T
03:00.1 Ethernet controller: Intel Corporation Ethernet Connection X552/X557-AT 10GBASE-T
06:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
06:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)

When I ran the config_controller command, it throws me an error in 02/08 Step : Applying Bootstrap Manifest”

EXT4-fs error (device drb0): ext4_journal_check_start:56: Detected aborted journal
EXT4-fs error(dbr0): Remounting filesystem read-only

The completed screenshot of the error is attached in the mail.

I also tried following the below mailing list
http://lists.starlingx.io/pipermail/starlingx-discuss/2019-February/003140.html

There are 2 Hard-disk attached in the server each of 930 GB
I had tried configured my server in RAID 0 and RAID 1, but getting the same error of running the config_controller command in the step 2.

I am also attaching the complete logs of path /var/log/ for your reference.

Please help me in resolving the issue.

Regards
Anirudh Gupta
(Senior Engineer)

From: Khalil, Ghada <Ghada.Khalil at windriver.com>
Sent: 19 June 2019 06:07
To: Anirudh Gupta <Anirudh.Gupta at hsc.com>; Zhao, Forrest <forrest.zhao at intel.com>; Xie, Cindy <cindy.xie at intel.com>; Jones, Bruce E <bruce.e.jones at intel.com>; Winnicki, Chris <Chris.Winnicki at windriver.com>; Ildiko Vancsa <ildiko.vancsa at gmail.com>; Miller, Frank <Frank.Miller at windriver.com>; Arce Moreno, Abraham <abraham.arce.moreno at intel.com>; Hazzim Anaya Casas? <hazzim.i.anaya.casas at intel.com>; Hernandez Gonzalez, Fernando <fernando.hernandez.gonzalez at intel.com>
Cc: starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io
Subject: RE: <StarlingX-Discuss> StarlingX 2018.10 without DPDK query

I’m not aware of a way to allow the use of ovs (w/o dpdk) in 2018.10

To use OVS, you will need to use a recent load built from master and follow the updated deployment instructions:
http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/<https://ind01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmirror.starlingx.cengn.ca%2Fmirror%2Fstarlingx%2Fmaster%2Fcentos%2F&data=02%7C01%7C%7C48f6d2919e1e4cd8659b08d6f44e5240%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C636965014586577405&sdata=ex2PeFC%2Fyh54GNj%2BdLVApAlAqVdK%2BOw16i%2BLO%2FWgzzs%3D&reserved=0>

The last green sanity was using ISO 20190613. You can use the symlink: latest_green_build or monitor the sanity emails sent regularly to the mailing list.

Regards,
Ghada

From: Anirudh Gupta [mailto:Anirudh.Gupta at hsc.com]
Sent: Tuesday, June 18, 2019 2:14 PM
To: Zhao, Forrest; Xie, Cindy; Jones, Bruce E; Winnicki, Chris; Ildiko Vancsa; Khalil, Ghada; Miller, Frank; Arce Moreno, Abraham; Hazzim Anaya Casas?; Hernandez Gonzalez, Fernando
Cc: starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>; starlingx-announce at lists.starlingx.io<mailto:starlingx-announce at lists.starlingx.io>
Subject: Re: <StarlingX-Discuss> StarlingX 2018.10 without DPDK query

Hi Forrest & Team
I agree that there is no such instruction mentioned in the document for 2018.10 AIO Simplex Mode for OVS.
It's just that my system doesn't have DPDK support and I need to deploy 2018.10 release until Release 2.0 is released in August 2019 as per the plan.
So Can I setup STARLINGX 2018.10 AIO SIMPLEX in my bare metal without DPDK support?
Is there any flag that could be disabled or any workaround that can work for me?
Looking Forward for your response.
Regards
Anirudh Gupta

From: Zhao, Forrest
Sent: Tuesday, 18 June, 7:28 PM
Subject: RE: <StarlingX-Discuss> StarlingX 2018.10 without DPDK query
To: Xie, Cindy, Anirudh Gupta, Jones, Bruce E, Winnicki, Chris, Ildiko Vancsa, Ghada Khalil?, Jones, Bruce E, Frank Miller, Arce Moreno, Abraham, Hazzim Anaya Casas?, Hernandez Gonzalez, Fernando
Cc: starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>, starlingx-announce at lists.starlingx.io<mailto:starlingx-announce at lists.starlingx.io>
If I remember correctly, 2018.10 release only support OVS-DPDK as virtual switch. Ghada may be able to double confirm that.

Also I can’t find any instruction in 2018.10 AIO simplex deployment guide https://docs.starlingx.io/deployment_guides/current/simplex.html<https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.starlingx.io%2Fdeployment_guides%2Fcurrent%2Fsimplex.html&data=02%7C01%7C%7C48f6d2919e1e4cd8659b08d6f44e5240%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C636965014586587399&sdata=sKzn2mNn2Cg5OzwxNQA%2F3I9F7UWc8PqexxYmEM8p0iU%3D&reserved=0> to set the virtual switch to OVS.

From: Xie, Cindy
Sent: Tuesday, June 18, 2019 8:35 PM
To: Anirudh Gupta <Anirudh.Gupta at hsc.com<mailto:Anirudh.Gupta at hsc.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>; Winnicki, Chris <Chris.Winnicki at windriver.com<mailto:Chris.Winnicki at windriver.com>>; Ildiko Vancsa <ildiko.vancsa at gmail.com<mailto:ildiko.vancsa at gmail.com>>; Ghada Khalil? <Ghada.Khalil at windriver.com<mailto:Ghada.Khalil at windriver.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>; Frank Miller <frank.miller at windriver.com<mailto:frank.miller at windriver.com>>; Arce Moreno, Abraham <abraham.arce.moreno at intel.com<mailto:abraham.arce.moreno at intel.com>>; Hazzim Anaya Casas? <hazzim.i.anaya.casas at intel.com<mailto:hazzim.i.anaya.casas at intel.com>>; Hernandez Gonzalez, Fernando <fernando.hernandez.gonzalez at intel.com<mailto:fernando.hernandez.gonzalez at intel.com>>; Zhao, Forrest <forrest.zhao at intel.com<mailto:forrest.zhao at intel.com>>
Cc: starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>; starlingx-announce at lists.starlingx.io<mailto:starlingx-announce at lists.starlingx.io>
Subject: RE: <StarlingX-Discuss> StarlingX 2018.10 without DPDK query

+ Forrest, do you have good answer to Gupta about using OVS without DPDK for 2018.10 release?  I understand that we have the containerized OVS option without DPDK with vswitch type to “none” in stx.2.0 today. Not sure about the behavior in 2018.10 release.

From: Anirudh Gupta [mailto:Anirudh.Gupta at hsc.com]
Sent: Tuesday, June 18, 2019 7:22 PM
To: Xie, Cindy <cindy.xie at intel.com<mailto:cindy.xie at intel.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>; Winnicki, Chris <Chris.Winnicki at windriver.com<mailto:Chris.Winnicki at windriver.com>>; Ildiko Vancsa <ildiko.vancsa at gmail.com<mailto:ildiko.vancsa at gmail.com>>; Ghada Khalil? <Ghada.Khalil at windriver.com<mailto:Ghada.Khalil at windriver.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>; Frank Miller <frank.miller at windriver.com<mailto:frank.miller at windriver.com>>; Arce Moreno, Abraham <abraham.arce.moreno at intel.com<mailto:abraham.arce.moreno at intel.com>>; Hazzim Anaya Casas? <hazzim.i.anaya.casas at intel.com<mailto:hazzim.i.anaya.casas at intel.com>>; Hernandez Gonzalez, Fernando <fernando.hernandez.gonzalez at intel.com<mailto:fernando.hernandez.gonzalez at intel.com>>
Cc: starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>; starlingx-announce at lists.starlingx.io<mailto:starlingx-announce at lists.starlingx.io>
Subject: <StarlingX-Discuss> StarlingX 2018.10 without DPDK query

Note :- Subject Changed

Hi Cindy,

Thanks for the update.

I want to setup StarlingX simplex 2018.10 setup, but I don't have DPDK support on my machine as a result of which the compute is in degraded state.
I can see error in ovs-vswitch logs.

Error Message:
error: "Error attaching device '0000:03:00.0' to DPDK"

Can you please suggest an alternative to this?

I have tried setting the vswitch type to be “none” and “ovs”, using the below command
system modify –vswitch_type=ovs system modify –vswitch_type=none

But after unlocking the host each time, when the system boots up, all my services (openvswitch, neutron-openvswitch-agent and nova-compute) remains in dead-state.
I need to manually start all the services, but even after starting the services, my compute remains in “degraded” state.

Can’t I create a StarlingX Simplex 2018.10 Setup without DPDK support?

Regards
Anirudh Gupta
(Senior Engineer)

From: Xie, Cindy <cindy.xie at intel.com<mailto:cindy.xie at intel.com>>
Sent: 18 June 2019 15:30
To: Anirudh Gupta <Anirudh.Gupta at hsc.com<mailto:Anirudh.Gupta at hsc.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>; Winnicki, Chris <Chris.Winnicki at windriver.com<mailto:Chris.Winnicki at windriver.com>>; Ildiko Vancsa <ildiko.vancsa at gmail.com<mailto:ildiko.vancsa at gmail.com>>; Ghada Khalil? <Ghada.Khalil at windriver.com<mailto:Ghada.Khalil at windriver.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>; Frank Miller <frank.miller at windriver.com<mailto:frank.miller at windriver.com>>; Arce Moreno, Abraham <abraham.arce.moreno at intel.com<mailto:abraham.arce.moreno at intel.com>>; Hazzim Anaya Casas? <hazzim.i.anaya.casas at intel.com<mailto:hazzim.i.anaya.casas at intel.com>>; Hernandez Gonzalez, Fernando <fernando.hernandez.gonzalez at intel.com<mailto:fernando.hernandez.gonzalez at intel.com>>
Cc: starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>; starlingx-announce at lists.starlingx.io<mailto:starlingx-announce at lists.starlingx.io>
Subject: RE: <StarlingX-Discuss> StarlingX 2019.05 Release Queries

Gupta,
-        We are still on track to release our release 2 (stx.2.0) on Aug’19
-        StarlingX will be based on K8s from stx.2.0 release, and we will have another ISO released. If you want to try the ISO, you can get our daily build and get an idea of footprint.
-        Right now, we do not support the version upgrade from 2018.10 release to new release. You need to re-deploy your cluster.

Thx. - cindy

From: Anirudh Gupta [mailto:Anirudh.Gupta at hsc.com]
Sent: Tuesday, June 18, 2019 5:11 PM
To: Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>; Winnicki, Chris <Chris.Winnicki at windriver.com<mailto:Chris.Winnicki at windriver.com>>; Ildiko Vancsa <ildiko.vancsa at gmail.com<mailto:ildiko.vancsa at gmail.com>>; Ghada Khalil  <Ghada.Khalil at windriver.com<mailto:Ghada.Khalil at windriver.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>; Frank Miller <frank.miller at windriver.com<mailto:frank.miller at windriver.com>>; Xie, Cindy <cindy.xie at intel.com<mailto:cindy.xie at intel.com>>; Arce Moreno, Abraham <abraham.arce.moreno at intel.com<mailto:abraham.arce.moreno at intel.com>>; Hazzim Anaya Casas  <hazzim.i.anaya.casas at intel.com<mailto:hazzim.i.anaya.casas at intel.com>>; Hernandez Gonzalez, Fernando <fernando.hernandez.gonzalez at intel.com<mailto:fernando.hernandez.gonzalez at intel.com>>
Cc: starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>; starlingx-announce at lists.starlingx.io<mailto:starlingx-announce at lists.starlingx.io>
Subject: <StarlingX-Discuss> StarlingX 2019.05 Release Queries

Hi All,

It would be great if anyone can please address my below queries.

I have prepared All in One Simplex/Duplex Setup on release 2018.10 and would like to further continue my work on the upcoming 2019.05 release.

Going forward, I do have some queries:

As per the recent update, the release 2019.05 is delayed and now is expected to be out in the month of August 2019.

https://wiki.openstack.org/wiki/StarlingX/Release_Plan<https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.openstack.org%2Fwiki%2FStarlingX%2FRelease_Plan&data=02%7C01%7C%7C48f6d2919e1e4cd8659b08d6f44e5240%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C636965014586587399&sdata=5itOi%2BT%2FWxFpdiEsR%2FCGvyTEiudKDa9g54UQUmgUwH8%3D&reserved=0>

Is there any further update on the release date?

As per the release notes of 2018.10, I am using Pre-built StarlingX Image

https://docs.starlingx.io/releasenotes/index.html#release-notes<https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.starlingx.io%2Freleasenotes%2Findex.html%23release-notes&data=02%7C01%7C%7C48f6d2919e1e4cd8659b08d6f44e5240%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C636965014586597394&sdata=94rtQmIMsyQfkbdBq4hC%2BpPpEIaof1uktBKVcCSFzKs%3D&reserved=0>
http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/outputs/iso/<https://ind01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmirror.starlingx.cengn.ca%2Fmirror%2Fstarlingx%2Fcentos%2F2018.10%2F20181110%2Foutputs%2Fiso%2F&data=02%7C01%7C%7C48f6d2919e1e4cd8659b08d6f44e5240%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C636965014586597394&sdata=pVQPMNSg7g7nt1C5Hk4g1V9grWN7lWQn%2Fuz7qh%2F9Rcs%3D&reserved=0>

Will the release 2019.05 be based on Kubernetes? If Yes, What will be the changes in the footprint?

And will there be another ISO with Kubernetes support available for 2019.05 Release?

As per the below links of 2018.10 and 2019.05, the Hardware requirements is same.

https://docs.starlingx.io/deployment_guides/current/duplex.html<https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.starlingx.io%2Fdeployment_guides%2Fcurrent%2Fduplex.html&data=02%7C01%7C%7C48f6d2919e1e4cd8659b08d6f44e5240%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C636965014586607386&sdata=%2BuKWKq%2BHUUOOWZ15Cgjcyn3InY8fSqGLJsu6zdkJiVg%3D&reserved=0>
https://docs.starlingx.io/deployment_guides/latest/aio_duplex/index.html<https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.starlingx.io%2Fdeployment_guides%2Flatest%2Faio_duplex%2Findex.html&data=02%7C01%7C%7C48f6d2919e1e4cd8659b08d6f44e5240%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C636965014586607386&sdata=q653JrJdY7wppzkcyfp1Dn3jUskx%2FIAcM8lPv5TyHYw%3D&reserved=0>

So will there be any change in the Hardware Requirement for both the releases or they’ll remain unchanged?

What efforts would be required if I need to upgrade my system from the current 2018.10 to the new 2019.05 release?

Regards
Anirudh Gupta
(Senior Engineer)
DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.
DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.
DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.
DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190621/44a04065/attachment-0001.html>