Bug 1621701

Summary:	[RFE] Add Arista Support
Product:	Red Hat OpenStack	Reporter:	Dan Radez <dradez>
Component:	python-networking-ansible	Assignee:	Dan Radez <dradez>
Status:	CLOSED ERRATA	QA Contact:	Arkady Shtempler <ashtempl>
Severity:	high	Docs Contact:
Priority:	high
Version:	15.0 (Stein)	CC:	aarapov, acanan, amcleod, bfournie, ccopello, gregraka, jamsmith, jlibosva, michapma, nlevinki, racedoro, sclewis, tfreger
Target Milestone:	Upstream M2	Keywords:	FutureFeature, TechPreview, TestOnly, Triaged
Target Release:	16.0 (Train on RHEL 8.1)	Flags:	tfreger: needinfo+ dradez: needinfo+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Technology Preview
Doc Text:	In Red Hat OpenStack Platform 16.0, a technology preview is added to the OpenStack Bare Metal service (ironic) to configure ML2 networking-ansible functionality with Arista Extensible Operating System (Arista EOS) switches. For more information, see "Enabling networking-ansible ML2 functionality," in the Bare Metal Provisioning guide.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-02-06 14:37:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1788187
Bug Blocks:	1776841

Description Dan Radez 2018-08-23 17:47:29 UTC

An Arista switch has been added to the Networking-Ansible lab.
Code already exists in the driver's code base.

The switch just wasn't available in time to test for OSP14 to make ti officially supported.

The Arista virtual appliance cannot pass packets with any efficiency and therefore is non-viable as a test case for virtual testing.

Comment 5 Toni Freger 2018-12-26 08:58:51 UTC

Following the recent decision to backport ansible-networking project to OSP13, which will add additional work.
It was agreed by Ramon, Assaf and myself that we will remove the QE ack from all OSP15 RFEs, and re-plan it.

Comment 15 Dan Radez 2019-09-25 20:53:22 UTC

This is a test only bug, the code is already upstream.

Comment 19 Toni Freger 2019-12-26 07:30:09 UTC

Hi Ramon, 

The setup is not ready yet, according to my knowledge Dan S. working on it.
We won't be able test it during OSP16 cycle. As usual BM installation takes a lot of effort and seems that Arkady found a bug which block the installation, he is debugging it now. 
The plan is to finish with OSP16 regression cycle then to test trunk RFE with OPS16 and fully automate it for all versions.
The major problem we have is CI,it's broken, entire squad trying to fix it for more than a month, without CI stability we won't be able to add support for additional equipment as Arista or any other features.

I hope this provide some clarity, let me know if more information is needed.

Comment 20 Ramon Acedo 2020-01-07 09:51:53 UTC

Toni, thanks for the update. Please, create and add the BZ that's blocking the installation as a blocker to this one, so that we can track its fix. Thanks.

Comment 21 Ramon Acedo 2020-01-07 10:21:28 UTC

Adding BZ#1788187 as a blocker to testing Arista support reported by QE

Comment 26 Dan Radez 2020-01-28 18:36:54 UTC

Do we reference Heat when we update values that can be put into deploy templates?

The config looks good but I would imagine this would be referenced in our deployment templates or that the "eos" value can be use in the ml2_conf.ini file to configure networking ansible.

Comment 30 errata-xmlrpc 2020-02-06 14:37:23 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:0283