osdir.com


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[goals][IPv6-Only Deployments and Testing] Week R-4 Update


 ---- On Mon, 16 Sep 2019 23:28:53 -0700 Slawek Kaplonski <skaplons at redhat.com> wrote ----
 > Hi Ghanshyam,
 > 
 > > On 17 Sep 2019, at 04:51, Ghanshyam Mann <gmann at ghanshyammann.com> wrote:
 > > 
 > > Hello Everyone, 
 > > 
 > > Below is the progress on Ipv6 goal during R6 week. I started the legacy job for IPv6 deployment with duplicating the run.yaml which is
 > > the only best way to do. 
 > > 
 > > Summary: 
 > > 
 > > The projects still need to prepare the IPv6 job:
 > > * Ec2-Api 
 > > * Freezer 
 > > * Heat 
 > > * Ironic 
 > > * Karbor
 > > * Kolla
 > > * Kuryr
 > > * Magnum 
 > > * Manila 
 > > * Masakari 
 > > * Mistral 
 > > * Murano 
 > > * Octavia 
 > > * Swift 
 > > 
 > > The projects waiting for IPv6 job patch to merge:
 > > If patch is failing, help me to debug that otherwise review and merge.
 > > * Barbican 
 > > * Blazar 
 > > * Cyborg 
 > > * Tricircle 
 > > * Vitrage 
 > > * Zaqar 
 > > * Cinder 
 > > * Glance 
 > > * Monasca 
 > > * Neutron 
 > 
 > I thought that Neutron is already done. Do You mean patches for some stadium projects which are still not merged? Can You give me links to such patches with failing job to make sure that I didnâ??t miss anything?

Yeah, it is for neutron stadium projects, I am tracking them as neutron only. Few are up I think and other I need to prepare the jobs. I am doing that and let you know the link.

-gmann

 > 
 > > * Qinling 
 > > * Quality Assurance
 > > * Sahara 
 > > * Searchlight
 > > * Senlin 
 > > * Tacker 
 > > 
 > > The projects have merged the IPv6 jobs:
 > > * Designate 
 > > * Murano 
 > > * Trove 
 > > * Cloudkitty
 > > * Congress 
 > > * Horizon
 > > * Keystone 
 > > * Nova 
 > > * Placement 
 > > * Solum 
 > > * Telemetry 
 > > * Watcher 
 > > * Zun 
 > > 
 > > The projects do  not need the IPv6 job (CLI, lib, deployment projects etc ):
 > > If anything I missed and IPv6 job need, please reply otherwise I will mark their task in storyboard as invalid.
 > > 
 > > * Adjutant 
 > > * Documentation
 > > * I18n
 > > * Infrastructure
 > > * Loci
 > > * Openstack Charms 
 > > * Openstack-Chef 
 > > * Openstack-Helm 
 > > * Openstackansible 
 > > * Openstackclient 
 > > * Openstacksdk
 > > * Oslo 
 > > * Packaging-Rpm
 > > * Powervmstackers
 > > * Puppet Openstack 
 > > * Rally 
 > > * Release Management
 > > * Requirements
 > > * Storlets 
 > > * Tripleo 
 > > * Winstackers
 > > 
 > > 
 > > Storyboard: 
 > > ========= 
 > > - https://storyboard.openstack.org/#!/story/2005477 
 > > 
 > > IPv6 missing support found: 
 > > ===================== 
 > > 1. https://review.opendev.org/#/c/673397/ 
 > > 2. https://review.opendev.org/#/c/673449/ 
 > > 3. https://review.opendev.org/#/c/677524/ 
 > > 
 > > How you can help: 
 > > ============== 
 > > - Each project needs to look for and review the ipv6 job patch. 
 > > - Verify it works fine on ipv6 and no ipv4 used in conf etc 
 > > - Any other specific scenario needs to be added as part of project IPv6 verification. 
 > > - Help on debugging and fix the bug in IPv6 job is failing. 
 > > 
 > > Everything related to this goal can be found under this topic: 
 > > Topic: https://review.opendev.org/#/q/topic:ipv6-only-deployment-and-testing+(status:open+OR+status:merged) 
 > > 
 > > How to define and run new IPv6 Job on project side: 
 > > ======================================= 
 > > - I prepared a wiki page to describe this section - https://wiki.openstack.org/wiki/Goal-IPv6-only-deployments-and-testing 
 > > 
 > > Review suggestion: 
 > > ============== 
 > > - Main goal of these jobs will be whether your service is able to listen on IPv6 and can communicate to any 
 > > other services either OpenStack or DB or rabbitmq etc on IPv6 or not. So check your proposed job with 
 > > that point of view. If anything missing, comment on patch. 
 > > - One example was - I missed to configure novnc address to IPv6- https://review.opendev.org/#/c/672493/ 
 > > - base script as part of 'devstack-tempest-ipv6' will do basic checks for endpoints on IPv6 and some devstack var 
 > > setting. But if your project needs more specific verification then it can be added in project side job as post-run 
 > > playbooks as described in wiki page[1]. 
 > > 
 > > [1] https://wiki.openstack.org/wiki/Goal-IPv6-only-deployments-and-testing 
 > > 
 > > -gmann 
 > > 
 > > 
 > > 
 > 
 > â?? 
 > Slawek Kaplonski
 > Senior software engineer
 > Red Hat
 > 
 > 
 >