Bug 1689866

Summary: Import os-ken project to OSP as Neutron's dependency
Product: Red Hat OpenStack Reporter: Slawek Kaplonski <skaplons>
Component: python-os-kenAssignee: Lon Hohberger <lhh>
Status: CLOSED ERRATA QA Contact: Toni Freger <tfreger>
Severity: medium Docs Contact:
Priority: medium    
Version: 15.0 (Stein)CC: bcafarel, ekuris, jjoyce, markmc
Target Milestone: betaKeywords: Triaged
Target Release: 15.0 (Stein)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-os-ken-0.3.1-0.20190312190758.a74bac9.el8ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-09-21 11:20:49 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:

Description Slawek Kaplonski 2019-03-18 10:22:41 UTC
We need os-ken package to be available in OSP-15 as it is Neutron's dependency now.
Os-ken is fork of Ryu, maintained by Openstack Neutron upstream community.

Link to os-ken repository: https://github.com/openstack/os-ken

RDO packaging: https://github.com/rdo-packages/os-ken-distgit

RDO build: https://cbs.centos.org/koji/buildinfo?buildID=25360

Ownership of this package will be vNES squad from Networking DFG.

Default CC list should be the same as DFG:networking Squad:vNES CC list.

Default QE contact should be the same as DFG:networking Squad:vNES QE contact.

Comment 6 Tomer 2019-07-23 12:52:11 UTC
On OSP15 there is the relevant rpm -

[root@controller-0 ~]# podman exec c7eb71c3061e rpm -qa | grep ken
python3-os-ken-0.3.1-0.20190312190758.a74bac9.el8ost.noarch

Comment 9 errata-xmlrpc 2019-09-21 11:20:49 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-2019:2811