[goals][IPv6-Only Deployments and Testing] Week R-4 Update
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+(statu...) 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
Hi Ghanshyam,
On 17 Sep 2019, at 04:51, Ghanshyam Mann <gmann@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?
* 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+(statu...)
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
---- On Mon, 16 Sep 2019 23:28:53 -0700 Slawek Kaplonski <skaplons@redhat.com> wrote ----
Hi Ghanshyam,
On 17 Sep 2019, at 04:51, Ghanshyam Mann <gmann@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+(statu...)
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
Hi,
On 17 Sep 2019, at 18:49, Ghanshyam Mann <gmann@ghanshyammann.com> wrote:
---- On Mon, 16 Sep 2019 23:28:53 -0700 Slawek Kaplonski <skaplons@redhat.com> wrote ----
Hi Ghanshyam,
On 17 Sep 2019, at 04:51, Ghanshyam Mann <gmann@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.
Thx for confirmation :)
-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+(statu...)
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
— Slawek Kaplonski Senior software engineer Red Hat
---- On Tue, 17 Sep 2019 09:58:05 -0700 Slawek Kaplonski <skaplons@redhat.com> wrote ----
Hi,
On 17 Sep 2019, at 18:49, Ghanshyam Mann <gmann@ghanshyammann.com> wrote:
---- On Mon, 16 Sep 2019 23:28:53 -0700 Slawek Kaplonski <skaplons@redhat.com> wrote ----
Hi Ghanshyam,
On 17 Sep 2019, at 04:51, Ghanshyam Mann <gmann@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.
Thx for confirmation :)
I have prepared the jobs for all projects you listed here[1]. - networking-midonet: https://review.opendev.org/#/c/682707/ - networking-bgpvpn: https://review.opendev.org/#/c/682710/ - networking-bagpipe: https://review.opendev.org/#/c/682709/ - neutron-dynamic-routing: https://review.opendev.org/#/c/682700/ - networking-odl: https://review.opendev.org/#/c/673501/ - networking-ovn: https://review.opendev.org/#/c/673488/2 [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-July/008084.html -gmann
-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+(statu...)
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
— Slawek Kaplonski Senior software engineer Red Hat
Hi, On Tue, Sep 17, 2019 at 11:32:44AM -0700, Ghanshyam Mann wrote:
---- On Tue, 17 Sep 2019 09:58:05 -0700 Slawek Kaplonski <skaplons@redhat.com> wrote ----
Hi,
On 17 Sep 2019, at 18:49, Ghanshyam Mann <gmann@ghanshyammann.com> wrote:
---- On Mon, 16 Sep 2019 23:28:53 -0700 Slawek Kaplonski <skaplons@redhat.com> wrote ----
Hi Ghanshyam,
On 17 Sep 2019, at 04:51, Ghanshyam Mann <gmann@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.
Thx for confirmation :)
I have prepared the jobs for all projects you listed here[1].
- networking-midonet: https://review.opendev.org/#/c/682707/ - networking-bgpvpn: https://review.opendev.org/#/c/682710/ - networking-bagpipe: https://review.opendev.org/#/c/682709/ - neutron-dynamic-routing: https://review.opendev.org/#/c/682700/ - networking-odl: https://review.opendev.org/#/c/673501/ - networking-ovn: https://review.opendev.org/#/c/673488/2
[1] http://lists.openstack.org/pipermail/openstack-discuss/2019-July/008084.html
Thx for this list. I will check all of them this week.
-gmann
-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+(statu...)
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
— Slawek Kaplonski Senior software engineer Red Hat
-- Slawek Kaplonski Senior software engineer Red Hat
Hi, For networking-odl the patch (https://review.opendev.org/673501) is still waiting for other things to be merged. We are struggling to make tempest working with the latest ODL releases, and passing again with networking-odl and ODL. Regards Lajos Slawek Kaplonski <skaplons@redhat.com> ezt írta (időpont: 2019. szept. 17., K, 8:31):
Hi Ghanshyam,
On 17 Sep 2019, at 04:51, Ghanshyam Mann <gmann@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?
* 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+(statu...)
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
On 9/17/19 4:51 AM, Ghanshyam Mann 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
We're hopelessly stuck with it. Finishing such a job in the Ussuri cycle would be an achievement already IMO. Dmitry
* 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+(statu...)
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
---- On Tue, 17 Sep 2019 02:54:53 -0700 Dmitry Tantsur <dtantsur@redhat.com> wrote ----
On 9/17/19 4:51 AM, Ghanshyam Mann 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
We're hopelessly stuck with it. Finishing such a job in the Ussuri cycle would be an achievement already IMO.
I understand your concern, goal is to finish in Train. I prepared the IPv6 jobs for Ironic project: - Ironic - https://review.opendev.org/#/c/682692/ - Ironic-inspector - https://review.opendev.org/#/c/682691/ - networking-generic-switch - https://review.opendev.org/#/c/682690/ rest all repo does not need IPv6 job as such. let's see how they run. -gmann
Dmitry
* 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+(statu...)
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
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/681573 We are testing CentOS and multinode and hence need overlay VXLAN to reach sensible levels of stability there - https://review.opendev.org/670690 The 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. Kind regards, Radek wt., 17 wrz 2019 o 04:58 Ghanshyam Mann <gmann@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+(statu...)
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
---- On Tue, 17 Sep 2019 03:12:22 -0700 Radosław Piliszek <radoslaw.piliszek@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@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+(statu...)
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
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. Kind regards, Radek wt., 17 wrz 2019 o 16:32 Ghanshyam Mann <gmann@ghanshyammann.com> napisał(a):
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
---- On Tue, 17 Sep 2019 03:12:22 -0700 Radosław Piliszek < radoslaw.piliszek@gmail.com> wrote ---- 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@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+(statu...)
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
---- On Tue, 17 Sep 2019 08:28:32 -0700 Radosław Piliszek <radoslaw.piliszek@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@ghanshyammann.com> napisał(a): ---- On Tue, 17 Sep 2019 03:12:22 -0700 Radosław Piliszek <radoslaw.piliszek@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@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+(statu...)
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
On Tue, Sep 17, 2019, at 3:12 AM, Radosław Piliszek 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/681573 We are testing CentOS and multinode and hence need overlay VXLAN to reach sensible levels of stability there - https://review.opendev.org/670690 The 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.
It is worth noting that you could test with the existing overlay network tooling that the infra team provides. This has been proven to work over years of multinode testing. Then we could incrementally improve it to address some of the deficiencies you have pointed out with it. This was sort of what I was trying to get across on IRC. Rather than go and reinvent the wheel to the detriment of meeting this goal on time: instead use what is there and works. Then improve what is there over time.
Kind regards, Radek
Hi Clark, no problem - Mark laid the ground already before we learnt about the Zuul roles - having learnt they had issues with ipv6 we decided to foster our approach. Remember we don't use OVS for that, so it's not entirely reinventing the wheel. So far we used multinode without the overlay network - it worked fine with IPv4 as long as there was private addressing. ;-) IPv6 has this issue that CentOS does not pick up IPv6 addresses properly - and they are public and not guaranteed anyway. wt., 17 wrz 2019 o 19:23 Clark Boylan <cboylan@sapwetik.org> napisał(a):
On Tue, Sep 17, 2019, at 3:12 AM, Radosław Piliszek 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/681573 We are testing CentOS and multinode and hence need overlay VXLAN to reach sensible levels of stability there - https://review.opendev.org/670690 The 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.
It is worth noting that you could test with the existing overlay network tooling that the infra team provides. This has been proven to work over years of multinode testing. Then we could incrementally improve it to address some of the deficiencies you have pointed out with it.
This was sort of what I was trying to get across on IRC. Rather than go and reinvent the wheel to the detriment of meeting this goal on time: instead use what is there and works. Then improve what is there over time.
Kind regards, Radek
On Tue, 17 Sep 2019 at 18:18, Clark Boylan <cboylan@sapwetik.org> wrote:
On Tue, Sep 17, 2019, at 3:12 AM, Radosław Piliszek 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/681573 We are testing CentOS and multinode and hence need overlay VXLAN to reach sensible levels of stability there - https://review.opendev.org/670690 The 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.
It is worth noting that you could test with the existing overlay network tooling that the infra team provides. This has been proven to work over years of multinode testing. Then we could incrementally improve it to address some of the deficiencies you have pointed out with it.
This was sort of what I was trying to get across on IRC. Rather than go and reinvent the wheel to the detriment of meeting this goal on time: instead use what is there and works. Then improve what is there over time.
The reason I used a different approach is that we run a containerised Open vSwitch - using this would not be compatible with the multinode-bridge role, and would also introduce a chicken and egg. I did study the role before reinventing the wheel, and I think the result will benefit everyone if we can push it back to zuul, since it avoids the potential double hop.
Kind regards, Radek
participants (7)
-
Clark Boylan
-
Dmitry Tantsur
-
Ghanshyam Mann
-
Lajos Katona
-
Mark Goddard
-
Radosław Piliszek
-
Slawek Kaplonski