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

Ghanshyam Mann gmann at ghanshyammann.com
Tue Sep 17 15:42:48 UTC 2019


 ---- On Tue, 17 Sep 2019 08:28:32 -0700 Radosław Piliszek <radoslaw.piliszek at gmail.com> wrote ----
 > Ah, great!We are trendsetters here then. 8-)
 > Still, kolla can be crossed out from the current iteration because testing IPv6-only is not applicable to it.

Sure, I will update the list in my next update.

-gmann

 > Kind regards,Radek
 > wt., 17 wrz 2019 o 16:32 Ghanshyam Mann <gmann at ghanshyammann.com> napisał(a):
 >  ---- On Tue, 17 Sep 2019 03:12:22 -0700 Radosław Piliszek <radoslaw.piliszek at gmail.com> wrote ----
 >  > Hiya,
 >  > Kolla is not going to get an IPv6-only job because it builds docker images and is not tested regarding networking (it does not do devstack/tempest either).
 >  > Kolla-Ansible, which does the deployment, is going to get some IPv6-only test jobs - https://review.opendev.org/681573We are testing CentOS and multinode and hence need overlay VXLAN to reach sensible levels of stability there - >https://review.opendev.org/670690The VXLAN patch is probably ready, awaiting review of independent cores. It will be refactored out later to put it in zuul plays as it might be useful to other projects as well.The IPv6 patch needs rebasing on VXLAN and >some small tweaks still.
 > 
 > 
 > This is good news Radosław. Actually deployment projects deploying on IPv6 is out of the scope of this goal(I forgot to add it under do not need section) but this is something we wanted to do as next step. Starting it in kolla is really appreciated and great news.
 > 
 > -gmann
 > 
 >  > Kind regards,Radek
 >  > wt., 17 wrz 2019 o 04:58 Ghanshyam Mann <gmann at ghanshyammann.com> napisał(a):
 >  > 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 
 >  > * 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 
 >  > 
 >  > 
 >  > 
 >  >
 > 
 >




More information about the openstack-discuss mailing list