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 to set the virtual switch to OVS.

From: Xie, Cindy
Sent: Tuesday, June 18, 2019 8:35 PM
To: Anirudh Gupta <Anirudh.Gupta@hsc.com>; Jones, Bruce E <bruce.e.jones@intel.com>; Winnicki, Chris <Chris.Winnicki@windriver.com>; Ildiko Vancsa <ildiko.vancsa@gmail.com>; Ghada Khalil? <Ghada.Khalil@windriver.com>; Jones, Bruce E <bruce.e.jones@intel.com>; Frank Miller <frank.miller@windriver.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Hazzim Anaya Casas? <hazzim.i.anaya.casas@intel.com>; Hernandez Gonzalez, Fernando <fernando.hernandez.gonzalez@intel.com>; Zhao, Forrest <forrest.zhao@intel.com>
Cc: starlingx-discuss@lists.starlingx.io; starlingx-announce@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@hsc.com]
Sent: Tuesday, June 18, 2019 7:22 PM
To: Xie, Cindy <cindy.xie@intel.com>; Jones, Bruce E <bruce.e.jones@intel.com>; Winnicki, Chris <Chris.Winnicki@windriver.com>; Ildiko Vancsa <ildiko.vancsa@gmail.com>; Ghada Khalil? <Ghada.Khalil@windriver.com>; Jones, Bruce E <bruce.e.jones@intel.com>; Frank Miller <frank.miller@windriver.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Hazzim Anaya Casas? <hazzim.i.anaya.casas@intel.com>; Hernandez Gonzalez, Fernando <fernando.hernandez.gonzalez@intel.com>
Cc: starlingx-discuss@lists.starlingx.io; starlingx-announce@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@intel.com>
Sent: 18 June 2019 15:30
To: Anirudh Gupta <Anirudh.Gupta@hsc.com>; Jones, Bruce E <bruce.e.jones@intel.com>; Winnicki, Chris <Chris.Winnicki@windriver.com>; Ildiko Vancsa <ildiko.vancsa@gmail.com>; Ghada Khalil? <Ghada.Khalil@windriver.com>; Jones, Bruce E <bruce.e.jones@intel.com>; Frank Miller <frank.miller@windriver.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Hazzim Anaya Casas? <hazzim.i.anaya.casas@intel.com>; Hernandez Gonzalez, Fernando <fernando.hernandez.gonzalez@intel.com>
Cc: starlingx-discuss@lists.starlingx.io; starlingx-announce@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@hsc.com]
Sent: Tuesday, June 18, 2019 5:11 PM
To: Jones, Bruce E <bruce.e.jones@intel.com>; Winnicki, Chris <Chris.Winnicki@windriver.com>; Ildiko Vancsa <ildiko.vancsa@gmail.com>; Ghada Khalil <Ghada.Khalil@windriver.com>; Jones, Bruce E <bruce.e.jones@intel.com>; Frank Miller <frank.miller@windriver.com>; Xie, Cindy <cindy.xie@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Hazzim Anaya Casas <hazzim.i.anaya.casas@intel.com>; Hernandez Gonzalez, Fernando <fernando.hernandez.gonzalez@intel.com>
Cc: starlingx-discuss@lists.starlingx.io; starlingx-announce@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

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

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

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://docs.starlingx.io/deployment_guides/latest/aio_duplex/index.html

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.