[ptls][tc] OpenStack User Survey Updates
Hi Everyone,
Like Helena mentioned last week, we are closing the 2023 OpenStack User Survey in a few weeks and will then open the 2024 OpenStack User Survey. At this time, we want to offer the project teams and TC the opportunity to update your project specific questions that appear at the end of the survey. As a reminder, for the project-specific questions, these appear if a survey taker selects your project in their deployment and TC questions appear to all survey takers.
If you and your team would like to update the question, please let me know by Friday, August 18. I know that this is a holiday time for many, so if any team needs some extra time, just let me know. I am also able to share the existing questions with any team that needs a refresher on what is currently in the survey.
In the meantime, please continue to promote openstack.org/usersurvey to anyone (and everyone!) you know who is running OpenStack or planning to in the future. We want to get as much feedback as we possibly can.
Cheers, Allison
Hi,
Dnia poniedziałek, 31 lipca 2023 21:17:07 CEST Allison Price pisze:
Hi Everyone,
Like Helena mentioned last week, we are closing the 2023 OpenStack User Survey in a few weeks and will then open the 2024 OpenStack User Survey. At this time, we want to offer the project teams and TC the opportunity to update your project specific questions that appear at the end of the survey. As a reminder, for the project-specific questions, these appear if a survey taker selects your project in their deployment and TC questions appear to all survey takers.
If you and your team would like to update the question, please let me know by Friday, August 18. I know that this is a holiday time for many, so if any team needs some extra time, just let me know. I am also able to share the existing questions with any team that needs a refresher on what is currently in the survey.
In the meantime, please continue to promote openstack.org/usersurvey to anyone (and everyone!) you know who is running OpenStack or planning to in the future. We want to get as much feedback as we possibly can.
Cheers, Allison
Thx Allison for the heads up. I have one question - where I can find existing questions from the survey? Do I need to do 2023 survey to find out what questions are actually there now?
Hi Slawek,
I worked with our team to pull the questions from the survey into this Google Doc [1]. Most of the project specific questions are on the second tab, but there are a few on tab 3 as well.
Please let me know if you have any questions.
Cheers, Allison
[1] https://docs.google.com/spreadsheets/d/1YZu7bJ4k_nog4ByrX1KNkjkFHJsIu6c9DM6g...
On Aug 1, 2023, at 1:53 AM, Slawek Kaplonski skaplons@redhat.com wrote:
Hi,
Dnia poniedziałek, 31 lipca 2023 21:17:07 CEST Allison Price pisze:
Hi Everyone,
Like Helena mentioned last week, we are closing the 2023 OpenStack User Survey in a few weeks and will then open the 2024 OpenStack User Survey. At this time, we want to offer the project teams and TC the opportunity to update your project specific questions that appear at the end of the survey. As a reminder, for the project-specific questions, these appear if a survey taker selects your project in their deployment and TC questions appear to all survey takers.
If you and your team would like to update the question, please let me know by Friday, August 18. I know that this is a holiday time for many, so if any team needs some extra time, just let me know. I am also able to share the existing questions with any team that needs a refresher on what is currently in the survey.
In the meantime, please continue to promote openstack.org/usersurvey to anyone (and everyone!) you know who is running OpenStack or planning to in the future. We want to get as much feedback as we possibly can.
Cheers, Allison
Thx Allison for the heads up. I have one question - where I can find existing questions from the survey? Do I need to do 2023 survey to find out what questions are actually there now?
-- Slawek Kaplonski Principal Software Engineer Red Hat
Hi,
Dnia wtorek, 1 sierpnia 2023 22:02:23 CEST Allison Price pisze:
Hi Slawek,
I worked with our team to pull the questions from the survey into this Google Doc [1]. Most of the project specific questions are on the second tab, but there are a few on tab 3 as well.
Please let me know if you have any questions.
Thank You very much. I will look at the neutron related questions, discuss that in our team and will get back to You if we will want to change something.
Cheers, Allison
[1] https://docs.google.com/spreadsheets/d/1YZu7bJ4k_nog4ByrX1KNkjkFHJsIu6c9DM6g...
On Aug 1, 2023, at 1:53 AM, Slawek Kaplonski skaplons@redhat.com wrote:
Hi,
Dnia poniedziałek, 31 lipca 2023 21:17:07 CEST Allison Price pisze:
Hi Everyone,
Like Helena mentioned last week, we are closing the 2023 OpenStack User Survey in a few weeks and will then open the 2024 OpenStack User Survey. At this time, we want to offer the project teams and TC the opportunity to update your project specific questions that appear at the end of the survey. As a reminder, for the project-specific questions, these appear if a survey taker selects your project in their deployment and TC questions appear to all survey takers.
If you and your team would like to update the question, please let me know by Friday, August 18. I know that this is a holiday time for many, so if any team needs some extra time, just let me know. I am also able to share the existing questions with any team that needs a refresher on what is currently in the survey.
In the meantime, please continue to promote openstack.org/usersurvey to anyone (and everyone!) you know who is running OpenStack or planning to in the future. We want to get as much feedback as we possibly can.
Cheers, Allison
Thx Allison for the heads up. I have one question - where I can find existing questions from the survey? Do I need to do 2023 survey to find out what questions are actually there now?
-- Slawek Kaplonski Principal Software Engineer Red Hat
Hi Allison
On Mon, Jul 31, 2023 at 8:21 PM Allison Price allison@openinfra.dev wrote:
Hi Everyone,
Like Helena mentioned last week, we are closing the 2023 OpenStack User Survey in a few weeks and will then open the 2024 OpenStack User Survey. At this time, we want to offer the project teams and TC the opportunity to update your project specific questions that appear at the end of the survey. As a reminder, for the project-specific questions, these appear if a survey taker selects your project in their deployment and TC questions appear to all survey takers.
If you and your team would like to update the question, please let me know by *Friday, August 18. *I know that this is a holiday time for many, so if any team needs some extra time, just let me know. I am also able to share the existing questions with any team that needs a refresher on what is currently in the survey.
Please can I request the following updates to the survey questions - neither are project specific questions but I think they are gaps in the survey today.
Page 1:
Which projects does this deployment currently use, or are you interested in using in the future? (PoC/Testing)
Request addition of Sunbeam and OpenStack Charms as projects.
Page 2:
Which tools are you using to deploy / manage this cluster?
Request addition of Sunbeam Request update of Juju to OpenStack Charms
Thanks
James
Hi James,
Yes, we can make both of those updates.
Cheers, Allison
On Aug 2, 2023, at 7:56 AM, James Page james.page@canonical.com wrote:
Hi Allison
On Mon, Jul 31, 2023 at 8:21 PM Allison Price <allison@openinfra.dev mailto:allison@openinfra.dev> wrote:
Hi Everyone,
Like Helena mentioned last week, we are closing the 2023 OpenStack User Survey in a few weeks and will then open the 2024 OpenStack User Survey. At this time, we want to offer the project teams and TC the opportunity to update your project specific questions that appear at the end of the survey. As a reminder, for the project-specific questions, these appear if a survey taker selects your project in their deployment and TC questions appear to all survey takers.
If you and your team would like to update the question, please let me know by Friday, August 18. I know that this is a holiday time for many, so if any team needs some extra time, just let me know. I am also able to share the existing questions with any team that needs a refresher on what is currently in the survey.
Please can I request the following updates to the survey questions - neither are project specific questions but I think they are gaps in the survey today.
Page 1:
Which projects does this deployment currently use, or are you interested in using in the future? (PoC/Testing)
Request addition of Sunbeam and OpenStack Charms as projects.
Page 2:
Which tools are you using to deploy / manage this cluster?
Request addition of Sunbeam Request update of Juju to OpenStack Charms
Thanks
James
Hi everyone,
As a reminder, tomorrow (Friday, August 18) is the deadline to submit changes for the 2024 OpenStack User Survey. If you and your team need more time, please let me know.
Cheers, Allison
On Jul 31, 2023, at 2:17 PM, Allison Price allison@openinfra.dev wrote:
Hi Everyone,
Like Helena mentioned last week, we are closing the 2023 OpenStack User Survey in a few weeks and will then open the 2024 OpenStack User Survey. At this time, we want to offer the project teams and TC the opportunity to update your project specific questions that appear at the end of the survey. As a reminder, for the project-specific questions, these appear if a survey taker selects your project in their deployment and TC questions appear to all survey takers.
If you and your team would like to update the question, please let me know by Friday, August 18. I know that this is a holiday time for many, so if any team needs some extra time, just let me know. I am also able to share the existing questions with any team that needs a refresher on what is currently in the survey.
In the meantime, please continue to promote openstack.org/usersurvey to anyone (and everyone!) you know who is running OpenStack or planning to in the future. We want to get as much feedback as we possibly can.
Cheers, Allison
Hi,
Dnia czwartek, 17 sierpnia 2023 16:50:49 CEST Allison Price pisze:
Hi everyone,
As a reminder, tomorrow (Friday, August 18) is the deadline to submit changes for the 2024 OpenStack User Survey. If you and your team need more time, please let me know.
Cheers, Allison
On Jul 31, 2023, at 2:17 PM, Allison Price allison@openinfra.dev wrote:
Hi Everyone,
Like Helena mentioned last week, we are closing the 2023 OpenStack User Survey in a few weeks and will then open the 2024 OpenStack User Survey. At this time, we want to offer the project teams and TC the opportunity to update your project specific questions that appear at the end of the survey. As a reminder, for the project-specific questions, these appear if a survey taker selects your project in their deployment and TC questions appear to all survey takers.
If you and your team would like to update the question, please let me know by Friday, August 18. I know that this is a holiday time for many, so if any team needs some extra time, just let me know. I am also able to share the existing questions with any team that needs a refresher on what is currently in the survey.
In the meantime, please continue to promote openstack.org/usersurvey to anyone (and everyone!) you know who is running OpenStack or planning to in the future. We want to get as much feedback as we possibly can.
Cheers, Allison
Sorry for asking for that but would it be possible if we (Neutron) would send You update at end of the Monday (21.08.2023)? I was at work only 2 days this week and I did not had time to talk about it with Rodolfo who is Neutron PTL to summarize everything. Today I am also off as we have recharge day in Red Hat. And the same is for Rodolfo. I would like to discuss with him everything on Monday morning CEST and then I would send You final version of what we would like to change there. Would that be ok for You? Thx in advance
Hi Slawek,
Yes, that is perfectly fine. Thank you for the heads up!
Cheers, Allison
On Aug 18, 2023, at 12:57 AM, Slawek Kaplonski skaplons@redhat.com wrote:
Hi,
Dnia czwartek, 17 sierpnia 2023 16:50:49 CEST Allison Price pisze:
Hi everyone,
As a reminder, tomorrow (Friday, August 18) is the deadline to submit changes for the 2024 OpenStack User Survey. If you and your team need more time, please let me know.
Cheers, Allison
On Jul 31, 2023, at 2:17 PM, Allison Price allison@openinfra.dev wrote:
Hi Everyone,
Like Helena mentioned last week, we are closing the 2023 OpenStack User Survey in a few weeks and will then open the 2024 OpenStack User Survey. At this time, we want to offer the project teams and TC the opportunity to update your project specific questions that appear at the end of the survey. As a reminder, for the project-specific questions, these appear if a survey taker selects your project in their deployment and TC questions appear to all survey takers.
If you and your team would like to update the question, please let me know by Friday, August 18. I know that this is a holiday time for many, so if any team needs some extra time, just let me know. I am also able to share the existing questions with any team that needs a refresher on what is currently in the survey.
In the meantime, please continue to promote openstack.org/usersurvey to anyone (and everyone!) you know who is running OpenStack or planning to in the future. We want to get as much feedback as we possibly can.
Cheers, Allison
Sorry for asking for that but would it be possible if we (Neutron) would send You update at end of the Monday (21.08.2023)? I was at work only 2 days this week and I did not had time to talk about it with Rodolfo who is Neutron PTL to summarize everything. Today I am also off as we have recharge day in Red Hat. And the same is for Rodolfo. I would like to discuss with him everything on Monday morning CEST and then I would send You final version of what we would like to change there. Would that be ok for You? Thx in advance
-- Slawek Kaplonski Principal Software Engineer Red Hat
Hi Allison,
Dnia piątek, 18 sierpnia 2023 16:34:07 CEST Allison Price pisze:
Hi Slawek,
Yes, that is perfectly fine. Thank you for the heads up!
Thank You. Here's updated proposal for Neutron related questions:
Which OpenStack Network (Neutron) drivers are you using? A10 Networks Arista Big Switch Brocade / Broadcom Calico Cisco UCS / Nexus Embrane Extreme Networks Hyper-V IBM SDN-VE Linux Bridge Mellanox Meta Plugin MidoNet Modular Layer 2 Plugin (ML2) NEC OpenFlow nova-network OpenDaylight Nuage Networks One Convergence NVSD OpenContrail or Juniper Open vSwitch OVN PLUMgrid Ruijie Networks Ryu OpenFlow Controller VMWare NSX (formerly Nicira NVP) ML2 - Alcatel-Lucent Omniswitch ML2 - Arista ML2 - Big Switch ML2 - Brocade VDX/VCS ML2 - Calico ML2 - Cisco APIC ML2 - Cisco DFA ML2 - Cloudbase Hyper-V ML2 - Freescale SDN ML2 - Frescale FWaaS ML2 - Fujitsu Converged Fabric Switch ML2 - Huawei Agile Controller ML2 - Linux Bridge ML2 - Mellanox ML2 - Mellanox SR-IOV ML2 - MidoNet ML2 - Nuage Networks ML2 - ONOS ML2 - One Convergence ML2 - OpenDaylight ML2 - OpenFlow Agent ML2 - Open vSwitch ML2 - OVN ML2 - SR-IOV ML2 - Pluribus ML2 - Tail-F ML2 - VMWare DVS Other Network Driver
Neutron: Which of the following features in the Neutron project are you actively using, interested in using or looking forward to using in your OpenStack deployment? Accelerated virtual switching (e.g. DPDK based) Accelerated virtual switching using software acceleration (DPDK) Accelerated virtual switching using hardware offloading Address Scopes Agent-based availability zones DNS resolution Designate integration (External DNS service) Distributed Virtual routing (DVR) Dynamic routing L2 Gateways ML2 Hierarchical Port Binding Metering Multi-segment provider networks (routed provider networks) Multiple ML2 drivers in the same deployment Multiple routing capabilities in the same deployment (router flavours) Port mirroring/monitoring (TAPaaS) Traffic steering Performance counters Pluggable IPAM Floating IPs Floating IP port forwarding QoS Bandwidth limiting QoS guaranteed minimum bandwidth QoS DSCP Marking QoS Floating IP bandwidth limiting QoS GW bandwidth limiting Placement resource scheduling SR-IOV Software firewalling (FWaas) Security groups Software virtual private networking (VPNaaS) Subnet pools Trunk ports VRRP-based HA routing HA routing ECMP routers transparent vlan, IPv6 Metadata IPv6 NDP Proxy IPv6 Prefix Delegation Live migration
New answers or things added to existing answers are marked with bold font. Things which we would like to remove as they don't makes sense anymore or are covered by other answers are written in the strikethrough font. I hope it will be clear and fine for You and that You will still be able to update those questions :) Please ping me if You would have any additional questions.
Cheers, Allison
On Aug 18, 2023, at 12:57 AM, Slawek Kaplonski skaplons@redhat.com wrote:
Hi,
Dnia czwartek, 17 sierpnia 2023 16:50:49 CEST Allison Price pisze:
Hi everyone,
As a reminder, tomorrow (Friday, August 18) is the deadline to submit changes for the 2024 OpenStack User Survey. If you and your team need more time, please let me know.
Cheers, Allison
On Jul 31, 2023, at 2:17 PM, Allison Price allison@openinfra.dev wrote:
Hi Everyone,
Like Helena mentioned last week, we are closing the 2023 OpenStack User Survey in a few weeks and will then open the 2024 OpenStack User Survey. At this time, we want to offer the project teams and TC the opportunity to update your project specific questions that appear at the end of the survey. As a reminder, for the project-specific questions, these appear if a survey taker selects your project in their deployment and TC questions appear to all survey takers.
If you and your team would like to update the question, please let me know by Friday, August 18. I know that this is a holiday time for many, so if any team needs some extra time, just let me know. I am also able to share the existing questions with any team that needs a refresher on what is currently in the survey.
In the meantime, please continue to promote openstack.org/usersurvey to anyone (and everyone!) you know who is running OpenStack or planning to in the future. We want to get as much feedback as we possibly can.
Cheers, Allison
Sorry for asking for that but would it be possible if we (Neutron) would send You update at end of the Monday (21.08.2023)? I was at work only 2 days this week and I did not had time to talk about it with Rodolfo who is Neutron PTL to summarize everything. Today I am also off as we have recharge day in Red Hat. And the same is for Rodolfo. I would like to discuss with him everything on Monday morning CEST and then I would send You final version of what we would like to change there. Would that be ok for You? Thx in advance
-- Slawek Kaplonski Principal Software Engineer Red Hat
Hi, Opendaylight should be out of the list also, but ML2 - OpenDaylight is in good place.
Lajos
Slawek Kaplonski skaplons@redhat.com ezt írta (időpont: 2023. aug. 21., H, 10:59):
Hi Allison,
Dnia piątek, 18 sierpnia 2023 16:34:07 CEST Allison Price pisze:
Hi Slawek,
Yes, that is perfectly fine. Thank you for the heads up!
Thank You.
Here's updated proposal for Neutron related questions:
Which OpenStack Network (Neutron) drivers are you using?
A10 Networks Arista Big Switch Brocade / Broadcom Calico Cisco UCS / Nexus Embrane Extreme Networks Hyper-V IBM SDN-VE Linux Bridge Mellanox Meta Plugin MidoNet Modular Layer 2 Plugin (ML2) NEC OpenFlow nova-network OpenDaylight Nuage Networks One Convergence NVSD OpenContrail or Juniper Open vSwitch OVN PLUMgrid Ruijie Networks Ryu OpenFlow Controller VMWare NSX (formerly Nicira NVP) ML2 - Alcatel-Lucent Omniswitch ML2 - Arista ML2 - Big Switch ML2 - Brocade VDX/VCS ML2 - Calico ML2 - Cisco APIC ML2 - Cisco DFA ML2 - Cloudbase Hyper-V ML2 - Freescale SDN ML2 - Frescale FWaaS ML2 - Fujitsu Converged Fabric Switch ML2 - Huawei Agile Controller ML2 - Linux Bridge ML2 - Mellanox ML2 - Mellanox SR-IOV ML2 - MidoNet ML2 - Nuage Networks ML2 - ONOS ML2 - One Convergence ML2 - OpenDaylight ML2 - OpenFlow Agent ML2 - Open vSwitch
- ML2 - OVN*
*ML2 - SR-IOV* ML2 - Pluribus ML2 - Tail-F ML2 - VMWare DVS Other Network DriverNeutron: Which of the following features in the Neutron project are you actively using, interested in using or looking forward to using in your OpenStack deployment?
Accelerated virtual switching (e.g. DPDK based) *Accelerated virtualswitching using software acceleration (DPDK)*
Accelerated virtual switching using hardware offloading*
Address Scopes
Agent-based availability zones
DNS resolution
Designate integration (External DNS service)*
Distributed Virtual routing *(DVR)*
Dynamic routing
L2 Gateways
ML2 Hierarchical Port Binding
Metering
Multi-segment provider networks *(routed provider networks)*
Multiple ML2 drivers in the same deployment
Multiple routing capabilities in the same deployment *(router
flavours)*
Port mirroring/monitoring *(TAPaaS)* Traffic steering Performance counters Pluggable IPAM *Floating IPs* *Floating IP *port forwarding QoS Bandwidth limiting QoS guaranteed minimum bandwidth QoS DSCP Marking QoS Floating IP bandwidth limiting *QoS GW bandwidth limiting*
Placement resource scheduling*
SR-IOV
Software firewalling* (FWaas)*
*Security groups*
Software virtual private networking *(VPNaaS)*
Subnet pools
Trunk ports
VRRP-based HA routing *HA routing*
ECMP routers*
*transparent vlan,*
IPv6 Metadata*
IPv6 NDP Proxy*
IPv6 Prefix Delegation*
Live migration*
New answers or things added to existing answers are marked with *bold * font.
Things which we would like to remove as they don't makes sense anymore or are covered by other answers are written in the strikethrough font.
I hope it will be clear and fine for You and that You will still be able to update those questions :)
Please ping me if You would have any additional questions.
Cheers,
Allison
On Aug 18, 2023, at 12:57 AM, Slawek Kaplonski skaplons@redhat.com
wrote:
Hi,
Dnia czwartek, 17 sierpnia 2023 16:50:49 CEST Allison Price pisze:
Hi everyone,
As a reminder, tomorrow (Friday, August 18) is the deadline to submit
changes for the 2024 OpenStack User Survey. If you and your team need more time, please let me know.
Cheers,
Allison
On Jul 31, 2023, at 2:17 PM, Allison Price allison@openinfra.dev
wrote:
Hi Everyone,
Like Helena mentioned last week, we are closing the 2023 OpenStack
User Survey in a few weeks and will then open the 2024 OpenStack User Survey. At this time, we want to offer the project teams and TC the opportunity to update your project specific questions that appear at the end of the survey. As a reminder, for the project-specific questions, these appear if a survey taker selects your project in their deployment and TC questions appear to all survey takers.
If you and your team would like to update the question, please let
me know by Friday, August 18. I know that this is a holiday time for many, so if any team needs some extra time, just let me know. I am also able to share the existing questions with any team that needs a refresher on what is currently in the survey.
In the meantime, please continue to promote openstack.org/usersurvey
to anyone (and everyone!) you know who is running OpenStack or planning to in the future. We want to get as much feedback as we possibly can.
Cheers,
Allison
Sorry for asking for that but would it be possible if we (Neutron)
would send You update at end of the Monday (21.08.2023)? I was at work only 2 days this week and I did not had time to talk about it with Rodolfo who is Neutron PTL to summarize everything. Today I am also off as we have recharge day in Red Hat. And the same is for Rodolfo. I would like to discuss with him everything on Monday morning CEST and then I would send You final version of what we would like to change there. Would that be ok for You? Thx in advance
--
Slawek Kaplonski
Principal Software Engineer
Red Hat
--
Slawek Kaplonski
Principal Software Engineer
Red Hat
Hi,
Dnia poniedziałek, 21 sierpnia 2023 13:04:53 CEST Lajos Katona pisze:
Hi, Opendaylight should be out of the list also, but ML2 - OpenDaylight is in good place.
Thx for confirmation :)
Lajos
Slawek Kaplonski skaplons@redhat.com ezt írta (időpont: 2023. aug. 21., H, 10:59):
Hi Allison,
Dnia piątek, 18 sierpnia 2023 16:34:07 CEST Allison Price pisze:
Hi Slawek,
Yes, that is perfectly fine. Thank you for the heads up!
Thank You.
Here's updated proposal for Neutron related questions:
Which OpenStack Network (Neutron) drivers are you using?
A10 Networks Arista Big Switch Brocade / Broadcom Calico Cisco UCS / Nexus Embrane Extreme Networks Hyper-V IBM SDN-VE Linux Bridge Mellanox Meta Plugin MidoNet Modular Layer 2 Plugin (ML2) NEC OpenFlow nova-network OpenDaylight Nuage Networks One Convergence NVSD OpenContrail or Juniper Open vSwitch OVN PLUMgrid Ruijie Networks Ryu OpenFlow Controller VMWare NSX (formerly Nicira NVP) ML2 - Alcatel-Lucent Omniswitch ML2 - Arista ML2 - Big Switch ML2 - Brocade VDX/VCS ML2 - Calico ML2 - Cisco APIC ML2 - Cisco DFA ML2 - Cloudbase Hyper-V ML2 - Freescale SDN ML2 - Frescale FWaaS ML2 - Fujitsu Converged Fabric Switch ML2 - Huawei Agile Controller ML2 - Linux Bridge ML2 - Mellanox ML2 - Mellanox SR-IOV ML2 - MidoNet ML2 - Nuage Networks ML2 - ONOS ML2 - One Convergence ML2 - OpenDaylight ML2 - OpenFlow Agent ML2 - Open vSwitch
- ML2 - OVN*
*ML2 - SR-IOV* ML2 - Pluribus ML2 - Tail-F ML2 - VMWare DVS Other Network DriverNeutron: Which of the following features in the Neutron project are you actively using, interested in using or looking forward to using in your OpenStack deployment?
Accelerated virtual switching (e.g. DPDK based) *Accelerated virtualswitching using software acceleration (DPDK)*
Accelerated virtual switching using hardware offloading*
Address Scopes
Agent-based availability zones
DNS resolution
Designate integration (External DNS service)*
Distributed Virtual routing *(DVR)*
Dynamic routing
L2 Gateways
ML2 Hierarchical Port Binding
Metering
Multi-segment provider networks *(routed provider networks)*
Multiple ML2 drivers in the same deployment
Multiple routing capabilities in the same deployment *(router
flavours)*
Port mirroring/monitoring *(TAPaaS)* Traffic steering Performance counters Pluggable IPAM *Floating IPs* *Floating IP *port forwarding QoS Bandwidth limiting QoS guaranteed minimum bandwidth QoS DSCP Marking QoS Floating IP bandwidth limiting *QoS GW bandwidth limiting*
Placement resource scheduling*
SR-IOV
Software firewalling* (FWaas)*
*Security groups*
Software virtual private networking *(VPNaaS)*
Subnet pools
Trunk ports
VRRP-based HA routing *HA routing*
ECMP routers*
*transparent vlan,*
IPv6 Metadata*
IPv6 NDP Proxy*
IPv6 Prefix Delegation*
Live migration*
New answers or things added to existing answers are marked with *bold * font.
Things which we would like to remove as they don't makes sense anymore or are covered by other answers are written in the strikethrough font.
I hope it will be clear and fine for You and that You will still be able to update those questions :)
Please ping me if You would have any additional questions.
Cheers,
Allison
On Aug 18, 2023, at 12:57 AM, Slawek Kaplonski skaplons@redhat.com
wrote:
Hi,
Dnia czwartek, 17 sierpnia 2023 16:50:49 CEST Allison Price pisze:
Hi everyone,
As a reminder, tomorrow (Friday, August 18) is the deadline to submit
changes for the 2024 OpenStack User Survey. If you and your team need more time, please let me know.
Cheers,
Allison
On Jul 31, 2023, at 2:17 PM, Allison Price allison@openinfra.dev
wrote:
Hi Everyone,
Like Helena mentioned last week, we are closing the 2023 OpenStack
User Survey in a few weeks and will then open the 2024 OpenStack User Survey. At this time, we want to offer the project teams and TC the opportunity to update your project specific questions that appear at the end of the survey. As a reminder, for the project-specific questions, these appear if a survey taker selects your project in their deployment and TC questions appear to all survey takers.
If you and your team would like to update the question, please let
me know by Friday, August 18. I know that this is a holiday time for many, so if any team needs some extra time, just let me know. I am also able to share the existing questions with any team that needs a refresher on what is currently in the survey.
In the meantime, please continue to promote openstack.org/usersurvey
to anyone (and everyone!) you know who is running OpenStack or planning to in the future. We want to get as much feedback as we possibly can.
Cheers,
Allison
Sorry for asking for that but would it be possible if we (Neutron)
would send You update at end of the Monday (21.08.2023)? I was at work only 2 days this week and I did not had time to talk about it with Rodolfo who is Neutron PTL to summarize everything. Today I am also off as we have recharge day in Red Hat. And the same is for Rodolfo. I would like to discuss with him everything on Monday morning CEST and then I would send You final version of what we would like to change there. Would that be ok for You? Thx in advance
--
Slawek Kaplonski
Principal Software Engineer
Red Hat
--
Slawek Kaplonski
Principal Software Engineer
Red Hat
Hi Slawek,
All of this is very clear and we can make those adjustments.
Cheers, Allison
On Aug 21, 2023, at 9:33 AM, Slawek Kaplonski skaplons@redhat.com wrote:
Hi,
Dnia poniedziałek, 21 sierpnia 2023 13:04:53 CEST Lajos Katona pisze:
Hi, Opendaylight should be out of the list also, but ML2 - OpenDaylight is in good place.
Thx for confirmation :)
Lajos
Slawek Kaplonski skaplons@redhat.com ezt írta (időpont: 2023. aug. 21., H, 10:59):
Hi Allison,
Dnia piątek, 18 sierpnia 2023 16:34:07 CEST Allison Price pisze:
Hi Slawek,
Yes, that is perfectly fine. Thank you for the heads up!
Thank You.
Here's updated proposal for Neutron related questions:
Which OpenStack Network (Neutron) drivers are you using?
A10 Networks
Arista
Big Switch
Brocade / Broadcom
Calico
Cisco UCS / Nexus
Embrane
Extreme Networks
Hyper-V
IBM SDN-VE
Linux Bridge
Mellanox
Meta Plugin
MidoNet
Modular Layer 2 Plugin (ML2)
NEC OpenFlow
nova-network
OpenDaylight
Nuage Networks
One Convergence NVSD
OpenContrail or Juniper
Open vSwitch
OVN
PLUMgrid
Ruijie Networks
Ryu OpenFlow Controller
VMWare NSX (formerly Nicira NVP)
ML2 - Alcatel-Lucent Omniswitch
ML2 - Arista
ML2 - Big Switch
ML2 - Brocade VDX/VCS
ML2 - Calico
ML2 - Cisco APIC
ML2 - Cisco DFA
ML2 - Cloudbase Hyper-V
ML2 - Freescale SDN
ML2 - Frescale FWaaS
ML2 - Fujitsu Converged Fabric Switch
ML2 - Huawei Agile Controller
ML2 - Linux Bridge
ML2 - Mellanox
ML2 - Mellanox SR-IOV
ML2 - MidoNet
ML2 - Nuage Networks
ML2 - ONOS
ML2 - One Convergence
ML2 - OpenDaylight
ML2 - OpenFlow Agent
ML2 - Open vSwitch
- ML2 - OVN*
*ML2 - SR-IOV*
ML2 - Pluribus
ML2 - Tail-F
ML2 - VMWare DVS
Other Network Driver
Neutron: Which of the following features in the Neutron project are you actively using, interested in using or looking forward to using in your OpenStack deployment?
Accelerated virtual switching (e.g. DPDK based) *Accelerated virtual switching using software acceleration (DPDK)*
Accelerated virtual switching using hardware offloading*
Address Scopes
Agent-based availability zones
DNS resolution
Designate integration (External DNS service)*
Distributed Virtual routing *(DVR)*
Dynamic routing
L2 Gateways
ML2 Hierarchical Port Binding
Metering
Multi-segment provider networks *(routed provider networks)*
Multiple ML2 drivers in the same deployment
Multiple routing capabilities in the same deployment *(router
flavours)*
Port mirroring/monitoring *(TAPaaS)*
Traffic steering
Performance counters
Pluggable IPAM
*Floating IPs*
*Floating IP *port forwarding
QoS Bandwidth limiting
QoS guaranteed minimum bandwidth
QoS DSCP Marking
QoS Floating IP bandwidth limiting
*QoS GW bandwidth limiting*
Placement resource scheduling*
SR-IOV
Software firewalling* (FWaas)*
*Security groups*
Software virtual private networking *(VPNaaS)*
Subnet pools
Trunk ports
VRRP-based HA routing *HA routing*
ECMP routers*
*transparent vlan,*
IPv6 Metadata*
IPv6 NDP Proxy*
IPv6 Prefix Delegation*
Live migration*
New answers or things added to existing answers are marked with *bold * font.
Things which we would like to remove as they don't makes sense anymore or are covered by other answers are written in the strikethrough font.
I hope it will be clear and fine for You and that You will still be able to update those questions :)
Please ping me if You would have any additional questions.
Cheers,
Allison
On Aug 18, 2023, at 12:57 AM, Slawek Kaplonski skaplons@redhat.com
wrote:
Hi,
Dnia czwartek, 17 sierpnia 2023 16:50:49 CEST Allison Price pisze:
Hi everyone,
As a reminder, tomorrow (Friday, August 18) is the deadline to submit
changes for the 2024 OpenStack User Survey. If you and your team need more time, please let me know.
Cheers,
Allison
> On Jul 31, 2023, at 2:17 PM, Allison Price allison@openinfra.dev
wrote:
>
> Hi Everyone,
>
> Like Helena mentioned last week, we are closing the 2023 OpenStack
User Survey in a few weeks and will then open the 2024 OpenStack User Survey. At this time, we want to offer the project teams and TC the opportunity to update your project specific questions that appear at the end of the survey. As a reminder, for the project-specific questions, these appear if a survey taker selects your project in their deployment and TC questions appear to all survey takers.
>
> If you and your team would like to update the question, please let
me know by Friday, August 18. I know that this is a holiday time for many, so if any team needs some extra time, just let me know. I am also able to share the existing questions with any team that needs a refresher on what is currently in the survey.
>
> In the meantime, please continue to promote openstack.org/usersurvey
to anyone (and everyone!) you know who is running OpenStack or planning to in the future. We want to get as much feedback as we possibly can.
>
> Cheers,
> Allison
Sorry for asking for that but would it be possible if we (Neutron)
would send You update at end of the Monday (21.08.2023)? I was at work only 2 days this week and I did not had time to talk about it with Rodolfo who is Neutron PTL to summarize everything. Today I am also off as we have recharge day in Red Hat. And the same is for Rodolfo. I would like to discuss with him everything on Monday morning CEST and then I would send You final version of what we would like to change there. Would that be ok for You? Thx in advance
--
Slawek Kaplonski
Principal Software Engineer
Red Hat
--
Slawek Kaplonski
Principal Software Engineer
Red Hat
-- Slawek Kaplonski Principal Software Engineer Red Hat
Hi,
Dnia poniedziałek, 21 sierpnia 2023 16:48:20 CEST Allison Price pisze:
Hi Slawek,
All of this is very clear and we can make those adjustments.
Thx a lot
Cheers, Allison
On Aug 21, 2023, at 9:33 AM, Slawek Kaplonski skaplons@redhat.com wrote:
Hi,
Dnia poniedziałek, 21 sierpnia 2023 13:04:53 CEST Lajos Katona pisze:
Hi, Opendaylight should be out of the list also, but ML2 - OpenDaylight is in good place.
Thx for confirmation :)
Lajos
Slawek Kaplonski skaplons@redhat.com ezt írta (időpont: 2023. aug. 21., H, 10:59):
Hi Allison,
Dnia piątek, 18 sierpnia 2023 16:34:07 CEST Allison Price pisze:
Hi Slawek,
Yes, that is perfectly fine. Thank you for the heads up!
Thank You.
Here's updated proposal for Neutron related questions:
Which OpenStack Network (Neutron) drivers are you using?
A10 Networks
Arista
Big Switch
Brocade / Broadcom
Calico
Cisco UCS / Nexus
Embrane
Extreme Networks
Hyper-V
IBM SDN-VE
Linux Bridge
Mellanox
Meta Plugin
MidoNet
Modular Layer 2 Plugin (ML2)
NEC OpenFlow
nova-network
OpenDaylight
Nuage Networks
One Convergence NVSD
OpenContrail or Juniper
Open vSwitch
OVN
PLUMgrid
Ruijie Networks
Ryu OpenFlow Controller
VMWare NSX (formerly Nicira NVP)
ML2 - Alcatel-Lucent Omniswitch
ML2 - Arista
ML2 - Big Switch
ML2 - Brocade VDX/VCS
ML2 - Calico
ML2 - Cisco APIC
ML2 - Cisco DFA
ML2 - Cloudbase Hyper-V
ML2 - Freescale SDN
ML2 - Frescale FWaaS
ML2 - Fujitsu Converged Fabric Switch
ML2 - Huawei Agile Controller
ML2 - Linux Bridge
ML2 - Mellanox
ML2 - Mellanox SR-IOV
ML2 - MidoNet
ML2 - Nuage Networks
ML2 - ONOS
ML2 - One Convergence
ML2 - OpenDaylight
ML2 - OpenFlow Agent
ML2 - Open vSwitch
- ML2 - OVN*
*ML2 - SR-IOV*
ML2 - Pluribus
ML2 - Tail-F
ML2 - VMWare DVS
Other Network Driver
Neutron: Which of the following features in the Neutron project are you actively using, interested in using or looking forward to using in your OpenStack deployment?
Accelerated virtual switching (e.g. DPDK based) *Accelerated virtual switching using software acceleration (DPDK)*
Accelerated virtual switching using hardware offloading*
Address Scopes
Agent-based availability zones
DNS resolution
Designate integration (External DNS service)*
Distributed Virtual routing *(DVR)*
Dynamic routing
L2 Gateways
ML2 Hierarchical Port Binding
Metering
Multi-segment provider networks *(routed provider networks)*
Multiple ML2 drivers in the same deployment
Multiple routing capabilities in the same deployment *(router
flavours)*
Port mirroring/monitoring *(TAPaaS)*
Traffic steering
Performance counters
Pluggable IPAM
*Floating IPs*
*Floating IP *port forwarding
QoS Bandwidth limiting
QoS guaranteed minimum bandwidth
QoS DSCP Marking
QoS Floating IP bandwidth limiting
*QoS GW bandwidth limiting*
Placement resource scheduling*
SR-IOV
Software firewalling* (FWaas)*
*Security groups*
Software virtual private networking *(VPNaaS)*
Subnet pools
Trunk ports
VRRP-based HA routing *HA routing*
ECMP routers*
*transparent vlan,*
IPv6 Metadata*
IPv6 NDP Proxy*
IPv6 Prefix Delegation*
Live migration*
New answers or things added to existing answers are marked with *bold * font.
Things which we would like to remove as they don't makes sense anymore or are covered by other answers are written in the strikethrough font.
I hope it will be clear and fine for You and that You will still be able to update those questions :)
Please ping me if You would have any additional questions.
Cheers,
Allison
On Aug 18, 2023, at 12:57 AM, Slawek Kaplonski skaplons@redhat.com
wrote:
Hi,
Dnia czwartek, 17 sierpnia 2023 16:50:49 CEST Allison Price pisze:
> Hi everyone,
>
> As a reminder, tomorrow (Friday, August 18) is the deadline to submit
changes for the 2024 OpenStack User Survey. If you and your team need more time, please let me know.
>
> Cheers,
> Allison
>
>
>
>> On Jul 31, 2023, at 2:17 PM, Allison Price allison@openinfra.dev
wrote:
>>
>> Hi Everyone,
>>
>> Like Helena mentioned last week, we are closing the 2023 OpenStack
User Survey in a few weeks and will then open the 2024 OpenStack User Survey. At this time, we want to offer the project teams and TC the opportunity to update your project specific questions that appear at the end of the survey. As a reminder, for the project-specific questions, these appear if a survey taker selects your project in their deployment and TC questions appear to all survey takers.
>>
>> If you and your team would like to update the question, please let
me know by Friday, August 18. I know that this is a holiday time for many, so if any team needs some extra time, just let me know. I am also able to share the existing questions with any team that needs a refresher on what is currently in the survey.
>>
>> In the meantime, please continue to promote openstack.org/usersurvey
to anyone (and everyone!) you know who is running OpenStack or planning to in the future. We want to get as much feedback as we possibly can.
>>
>> Cheers,
>> Allison
>
>
Sorry for asking for that but would it be possible if we (Neutron)
would send You update at end of the Monday (21.08.2023)? I was at work only 2 days this week and I did not had time to talk about it with Rodolfo who is Neutron PTL to summarize everything. Today I am also off as we have recharge day in Red Hat. And the same is for Rodolfo. I would like to discuss with him everything on Monday morning CEST and then I would send You final version of what we would like to change there. Would that be ok for You? Thx in advance
--
Slawek Kaplonski
Principal Software Engineer
Red Hat
--
Slawek Kaplonski
Principal Software Engineer
Red Hat
-- Slawek Kaplonski Principal Software Engineer Red Hat
Hi Slawek,
I did have a follow up question on the drivers question specifically. Can you elaborate on why certain drivers are being removed? For instance, Open vSwitch is being removed, but it is commonly one of the most selected Neutron driver. Before we remove any drivers, it would be good to make sure we understand why. Even if something is not actively maintained upstream, it is often still put into production which is good knowledge for the community.
Thanks, Allison
On Aug 21, 2023, at 10:06 AM, Slawek Kaplonski skaplons@redhat.com wrote:
Hi,
Dnia poniedziałek, 21 sierpnia 2023 16:48:20 CEST Allison Price pisze:
Hi Slawek,
All of this is very clear and we can make those adjustments.
Thx a lot
Cheers, Allison
On Aug 21, 2023, at 9:33 AM, Slawek Kaplonski skaplons@redhat.com wrote:
Hi,
Dnia poniedziałek, 21 sierpnia 2023 13:04:53 CEST Lajos Katona pisze:
Hi, Opendaylight should be out of the list also, but ML2 - OpenDaylight is in good place.
Thx for confirmation :)
Lajos
Slawek Kaplonski skaplons@redhat.com ezt írta (időpont: 2023. aug. 21., H, 10:59):
Hi Allison,
Dnia piątek, 18 sierpnia 2023 16:34:07 CEST Allison Price pisze:
Hi Slawek,
Yes, that is perfectly fine. Thank you for the heads up!
Thank You.
Here's updated proposal for Neutron related questions:
Which OpenStack Network (Neutron) drivers are you using?
A10 Networks
Arista
Big Switch
Brocade / Broadcom
Calico
Cisco UCS / Nexus
Embrane
Extreme Networks
Hyper-V
IBM SDN-VE
Linux Bridge
Mellanox
Meta Plugin
MidoNet
Modular Layer 2 Plugin (ML2)
NEC OpenFlow
nova-network
OpenDaylight
Nuage Networks
One Convergence NVSD
OpenContrail or Juniper
Open vSwitch
OVN
PLUMgrid
Ruijie Networks
Ryu OpenFlow Controller
VMWare NSX (formerly Nicira NVP)
ML2 - Alcatel-Lucent Omniswitch
ML2 - Arista
ML2 - Big Switch
ML2 - Brocade VDX/VCS
ML2 - Calico
ML2 - Cisco APIC
ML2 - Cisco DFA
ML2 - Cloudbase Hyper-V
ML2 - Freescale SDN
ML2 - Frescale FWaaS
ML2 - Fujitsu Converged Fabric Switch
ML2 - Huawei Agile Controller
ML2 - Linux Bridge
ML2 - Mellanox
ML2 - Mellanox SR-IOV
ML2 - MidoNet
ML2 - Nuage Networks
ML2 - ONOS
ML2 - One Convergence
ML2 - OpenDaylight
ML2 - OpenFlow Agent
ML2 - Open vSwitch
- ML2 - OVN*
*ML2 - SR-IOV*
ML2 - Pluribus
ML2 - Tail-F
ML2 - VMWare DVS
Other Network Driver
Neutron: Which of the following features in the Neutron project are you actively using, interested in using or looking forward to using in your OpenStack deployment?
Accelerated virtual switching (e.g. DPDK based) *Accelerated virtual switching using software acceleration (DPDK)*
Accelerated virtual switching using hardware offloading*
Address Scopes
Agent-based availability zones
DNS resolution
Designate integration (External DNS service)*
Distributed Virtual routing *(DVR)*
Dynamic routing
L2 Gateways
ML2 Hierarchical Port Binding
Metering
Multi-segment provider networks *(routed provider networks)*
Multiple ML2 drivers in the same deployment
Multiple routing capabilities in the same deployment *(router
flavours)*
Port mirroring/monitoring *(TAPaaS)*
Traffic steering
Performance counters
Pluggable IPAM
*Floating IPs*
*Floating IP *port forwarding
QoS Bandwidth limiting
QoS guaranteed minimum bandwidth
QoS DSCP Marking
QoS Floating IP bandwidth limiting
*QoS GW bandwidth limiting*
Placement resource scheduling*
SR-IOV
Software firewalling* (FWaas)*
*Security groups*
Software virtual private networking *(VPNaaS)*
Subnet pools
Trunk ports
VRRP-based HA routing *HA routing*
ECMP routers*
*transparent vlan,*
IPv6 Metadata*
IPv6 NDP Proxy*
IPv6 Prefix Delegation*
Live migration*
New answers or things added to existing answers are marked with *bold * font.
Things which we would like to remove as they don't makes sense anymore or are covered by other answers are written in the strikethrough font.
I hope it will be clear and fine for You and that You will still be able to update those questions :)
Please ping me if You would have any additional questions.
Cheers,
Allison
> On Aug 18, 2023, at 12:57 AM, Slawek Kaplonski skaplons@redhat.com
wrote:
>
> Hi,
>
> Dnia czwartek, 17 sierpnia 2023 16:50:49 CEST Allison Price pisze:
>> Hi everyone,
>>
>> As a reminder, tomorrow (Friday, August 18) is the deadline to submit
changes for the 2024 OpenStack User Survey. If you and your team need more time, please let me know.
>>
>> Cheers,
>> Allison
>>
>>
>>
>>> On Jul 31, 2023, at 2:17 PM, Allison Price allison@openinfra.dev
wrote:
>>>
>>> Hi Everyone,
>>>
>>> Like Helena mentioned last week, we are closing the 2023 OpenStack
User Survey in a few weeks and will then open the 2024 OpenStack User Survey. At this time, we want to offer the project teams and TC the opportunity to update your project specific questions that appear at the end of the survey. As a reminder, for the project-specific questions, these appear if a survey taker selects your project in their deployment and TC questions appear to all survey takers.
>>>
>>> If you and your team would like to update the question, please let
me know by Friday, August 18. I know that this is a holiday time for many, so if any team needs some extra time, just let me know. I am also able to share the existing questions with any team that needs a refresher on what is currently in the survey.
>>>
>>> In the meantime, please continue to promote openstack.org/usersurvey
to anyone (and everyone!) you know who is running OpenStack or planning to in the future. We want to get as much feedback as we possibly can.
>>>
>>> Cheers,
>>> Allison
>>
>>
>
> Sorry for asking for that but would it be possible if we (Neutron)
would send You update at end of the Monday (21.08.2023)? I was at work only 2 days this week and I did not had time to talk about it with Rodolfo who is Neutron PTL to summarize everything. Today I am also off as we have recharge day in Red Hat. And the same is for Rodolfo. I would like to discuss with him everything on Monday morning CEST and then I would send You final version of what we would like to change there. Would that be ok for You? Thx in advance
>
> --
> Slawek Kaplonski
> Principal Software Engineer
> Red Hat
--
Slawek Kaplonski
Principal Software Engineer
Red Hat
-- Slawek Kaplonski Principal Software Engineer Red Hat
-- Slawek Kaplonski Principal Software Engineer Red Hat
On 2023-08-21 12:50:57 -0500 (-0500), Allison Price wrote: [...]
Even if something is not actively maintained upstream, it is often still put into production which is good knowledge for the community.
[...]
For that matter, we tend to avoid removing options which were valid for old releases, because many respondents are in fact running (sometimes very) old releases.
Hi,
Dnia poniedziałek, 21 sierpnia 2023 20:10:38 CEST Jeremy Stanley pisze:
On 2023-08-21 12:50:57 -0500 (-0500), Allison Price wrote: [...]
Even if something is not actively maintained upstream, it is often still put into production which is good knowledge for the community.
[...]
For that matter, we tend to avoid removing options which were valid for old releases, because many respondents are in fact running (sometimes very) old releases. -- Jeremy Stanley
In this question there are actually mixed core plugins (like old Openvswitch) and ML2 plugin's mechanism drivers (like e.g. ML2-Openvswitch). Those old core plugins which we proposed to remove were removed from Neutron around version (2015.0.0 and 7.0.0 - I don't even remember what OpenStack version it was then). Currently we think that this may be confusing for people as we have seen pretty many people choosing it (Openvswitch 43% and ML2-Openvswitch 46% for example in 2022 survey) but I really doubt that 43% of responders are still using Neutron 2015.0.0 so they are really using old Openvswitch core plugin. And it's similar for other old core plugins which don't exists anymore for long time and have "duplicated" answers as ML2 driver in the same question.
For us the best would be to have 2 separate questions related to that: 1. What core plugin are You using? 2. (Optional) If You choose ML2 in previous question, what mechanism drivers are You using?
And then in 1. we could keep all those very old and not existing core plugins like Openvswitch or Linuxbridge and in the second question have all the "ML2 - ...." answers. But I'm not sure if we can add yet another Neutron related question to the survey so that's why we though it will be better to not confuse people with very old core plugins and current ML2 drivers for the same backend technology.
Hello:
I agree with Slawek. Some options only introduce confusion and blur the results of the survey. For those in-tree drivers (LB, OVS, OVN, SRIOV), it doesn't make sense to have other than ML2-driver option. And for other drivers (Calico, Big Switch, OpenDaylight) it could be possible that the user is using it in the undelaying network, although that is not very common.
Regards.
On Tue, Aug 22, 2023 at 9:22 AM Slawek Kaplonski skaplons@redhat.com wrote:
Hi,
Dnia poniedziałek, 21 sierpnia 2023 20:10:38 CEST Jeremy Stanley pisze:
On 2023-08-21 12:50:57 -0500 (-0500), Allison Price wrote:
[...]
Even if something is not actively maintained upstream, it is often
still put into production which is good knowledge for the
community.
[...]
For that matter, we tend to avoid removing options which were valid
for old releases, because many respondents are in fact running
(sometimes very) old releases.
--
Jeremy Stanley
In this question there are actually mixed core plugins (like old Openvswitch) and ML2 plugin's mechanism drivers (like e.g. ML2-Openvswitch).
Those old core plugins which we proposed to remove were removed from Neutron around version (2015.0.0 and 7.0.0 - I don't even remember what OpenStack version it was then).
Currently we think that this may be confusing for people as we have seen pretty many people choosing it (Openvswitch 43% and ML2-Openvswitch 46% for example in 2022 survey) but I really doubt that 43% of responders are still using Neutron 2015.0.0 so they are really using old Openvswitch core plugin.
And it's similar for other old core plugins which don't exists anymore for long time and have "duplicated" answers as ML2 driver in the same question.
For us the best would be to have 2 separate questions related to that:
What *core* *plugin *are You using?
(Optional) If You choose *ML2* in previous question, what mechanism
drivers are You using?
And then in 1. we could keep all those very old and not existing core plugins like Openvswitch or Linuxbridge and in the second question have all the "ML2 - ...." answers.
But I'm not sure if we can add yet another Neutron related question to the survey so that's why we though it will be better to not confuse people with very old core plugins and current ML2 drivers for the same backend technology.
--
Slawek Kaplonski
Principal Software Engineer
Red Hat
On 2023-08-22 09:21:03 +0200 (+0200), Slawek Kaplonski wrote: [...]
In this question there are actually mixed core plugins (like old Openvswitch) and ML2 plugin's mechanism drivers (like e.g. ML2-Openvswitch). Those old core plugins which we proposed to remove were removed from Neutron around version (2015.0.0 and 7.0.0 - I don't even remember what OpenStack version it was then).
[...]
According to https://releases.openstack.org/ Juno was 2014.2 and Kilo was 2015.1.0 (there was no 2015.0.0), while Liberty was 7.0.0.
If these were all removed by Mitaka and there are very few respondents indicating they're running deployments that old, then it may make sense to clean those options up. If they were still available options for a while after that (merely deprecated) or if there are still a lot of respondents with deployments of that vintage, then it may make more sense to reword those options for clarity, to something like:
"Old/Legacy Openvswitch core plugin (OpenStack Liberty and earlier)"
In the 2023 results so far, approximately 8% of deployments are running a release older than Mitaka. So while it’s a very small amount, I think it’s the most beneficial to the community to get the most accurate representation possible.
If that means adding a second question like Slawek proposes, we can make that work. I would just need to know how the answer choices very by question. If y’all can provide that, I can make that update.
On Aug 22, 2023, at 8:38 AM, Jeremy Stanley fungi@yuggoth.org wrote:
On 2023-08-22 09:21:03 +0200 (+0200), Slawek Kaplonski wrote: [...]
In this question there are actually mixed core plugins (like old Openvswitch) and ML2 plugin's mechanism drivers (like e.g. ML2-Openvswitch). Those old core plugins which we proposed to remove were removed from Neutron around version (2015.0.0 and 7.0.0 - I don't even remember what OpenStack version it was then).
[...]
According to https://releases.openstack.org/ Juno was 2014.2 and Kilo was 2015.1.0 (there was no 2015.0.0), while Liberty was 7.0.0.
If these were all removed by Mitaka and there are very few respondents indicating they're running deployments that old, then it may make sense to clean those options up. If they were still available options for a while after that (merely deprecated) or if there are still a lot of respondents with deployments of that vintage, then it may make more sense to reword those options for clarity, to something like:
"Old/Legacy Openvswitch core plugin (OpenStack Liberty and earlier)"
-- Jeremy Stanley
Hi,
Dnia wtorek, 22 sierpnia 2023 19:31:15 CEST Allison Price pisze:
In the 2023 results so far, approximately 8% of deployments are running a release older than Mitaka. So while it’s a very small amount, I think it’s the most beneficial to the community to get the most accurate representation possible.
If that means adding a second question like Slawek proposes, we can make that work. I would just need to know how the answer choices very by question. If y’all can provide that, I can make that update.
So those old core plugins were completly dropped (removed from neutron repo) in Neutron 8.0.0 (Mitaka). In 7.0.0 (Liberty) most of them were removed but not all. In Mitaka all except ML2 and Hyper-v was deleted already. To have most accurate representation possible and if we can split it into two questions then we would like it to be be like:
1. Which OpenStack Network (Neutron) core plugin are you using? A10 Networks Arista Big Switch Brocade / Broadcom Calico Cisco UCS / Nexus Embrane Extreme Networks Hyper-V IBM SDN-VE Linux Bridge Mellanox Meta Plugin MidoNet Modular Layer 2 Plugin (ML2) NEC OpenFlow nova-network OpenDaylight Nuage Networks One Convergence NVSD OpenContrail or Juniper Open vSwitch PLUMgrid Ruijie Networks VMWare NSX (formerly Nicira NVP)
2. If You choose Modular Layer 2 Plugin (ML2) in the previous question, what mechanism driver(s) are You using? Alcatel-Lucent Omniswitch Arista Big Switch Brocade VDX/VCS Calico Cisco APIC Cisco DFA Cloudbase Hyper-V Freescale SDN Frescale FWaaS Fujitsu Converged Fabric Switch Huawei Agile Controller Linux Bridge Mellanox Mellanox SR-IOV MidoNet Nuage Networks ONOS One Convergence OpenDaylight OpenFlow Agent Open vSwitch OVN SR-IOV Pluribus Tail-F VMWare DVS Other Mechanism Driver
Please let me know if that would be fine for You too. Thx in advance
On Aug 22, 2023, at 8:38 AM, Jeremy Stanley fungi@yuggoth.org wrote:
On 2023-08-22 09:21:03 +0200 (+0200), Slawek Kaplonski wrote: [...]
In this question there are actually mixed core plugins (like old Openvswitch) and ML2 plugin's mechanism drivers (like e.g. ML2-Openvswitch). Those old core plugins which we proposed to remove were removed from Neutron around version (2015.0.0 and 7.0.0 - I don't even remember what OpenStack version it was then).
[...]
According to https://releases.openstack.org/ Juno was 2014.2 and Kilo was 2015.1.0 (there was no 2015.0.0), while Liberty was 7.0.0.
If these were all removed by Mitaka and there are very few respondents indicating they're running deployments that old, then it may make sense to clean those options up. If they were still available options for a while after that (merely deprecated) or if there are still a lot of respondents with deployments of that vintage, then it may make more sense to reword those options for clarity, to something like:
"Old/Legacy Openvswitch core plugin (OpenStack Liberty and earlier)"
-- Jeremy Stanley
On Wed, 23 Aug 2023, 10:09 Slawek Kaplonski, skaplons@redhat.com wrote:
Hi,
Dnia wtorek, 22 sierpnia 2023 19:31:15 CEST Allison Price pisze:
In the 2023 results so far, approximately 8% of deployments are running
a release older than Mitaka. So while it’s a very small amount, I think it’s the most beneficial to the community to get the most accurate representation possible.
If that means adding a second question like Slawek proposes, we can make
that work. I would just need to know how the answer choices very by question. If y’all can provide that, I can make that update.
So those old core plugins were completly dropped (removed from neutron repo) in Neutron 8.0.0 (Mitaka). In 7.0.0 (Liberty) most of them were removed but not all. In Mitaka all except ML2 and Hyper-v was deleted already.
To have most accurate representation possible and if we can split it into two questions then we would like it to be be like:
Which OpenStack Network (Neutron) *core plugin* are you using?
A10 Networks
Arista
Big Switch
Brocade / Broadcom
Calico
Cisco UCS / Nexus
Embrane
Extreme Networks
Hyper-V
IBM SDN-VE
Linux Bridge
Mellanox
Meta Plugin
MidoNet
Modular Layer 2 Plugin (ML2)
NEC OpenFlow
nova-network
OpenDaylight
Nuage Networks
One Convergence NVSD
OpenContrail or Juniper
Open vSwitch
PLUMgrid
Ruijie Networks
VMWare NSX (formerly Nicira NVP)
If You choose *Modular Layer 2 Plugin (ML2)* in the previous question,
what mechanism driver(s) are You using?
Alcatel-Lucent Omniswitch Arista Big Switch Brocade VDX/VCS Calico Cisco APIC Cisco DFA Cloudbase Hyper-V Freescale SDN Frescale FWaaS Fujitsu Converged Fabric Switch Huawei Agile Controller Linux Bridge Mellanox Mellanox SR-IOV MidoNet Nuage Networks ONOS One Convergence OpenDaylight OpenFlow Agent Open vSwitch OVN SR-IOV Pluribus Tail-F VMWare DVS Other Mechanism DriverPlease let me know if that would be fine for You too. Thx in advance
For what it's worth, I agree that that is a better way to ask these questions, compared with the previous arrangement.
I wonder, though, if we might simplify further by glossing over the core plugin vs. ML2 driver distinction?
- On the users' side, is it possible that some respondents wouldn't be sure of this detail, and so would find the survey harder to complete?
- On the developers' side, does anyone really care if a networking solution is being used as a core plugin instead of as an ML2 driver, or vice versa?
(I can confirm that Calico continues to be available out-of-tree both as a core plugin and as an ML2 mechanism driver.)
Best wishes - Nell
On Aug 22, 2023, at 8:38 AM, Jeremy Stanley fungi@yuggoth.org wrote:
On 2023-08-22 09:21:03 +0200 (+0200), Slawek Kaplonski wrote:
[...]
In this question there are actually mixed core plugins (like old
Openvswitch) and ML2 plugin's mechanism drivers (like e.g.
ML2-Openvswitch). Those old core plugins which we proposed to
remove were removed from Neutron around version (2015.0.0 and
7.0.0 - I don't even remember what OpenStack version it was then).
[...]
According to https://releases.openstack.org/ Juno was 2014.2 and
Kilo was 2015.1.0 (there was no 2015.0.0), while Liberty was 7.0.0.
If these were all removed by Mitaka and there are very few
respondents indicating they're running deployments that old, then it
may make sense to clean those options up. If they were still
available options for a while after that (merely deprecated) or if
there are still a lot of respondents with deployments of that
vintage, then it may make more sense to reword those options for
clarity, to something like:
"Old/Legacy Openvswitch core plugin (OpenStack Liberty and earlier)"
--
Jeremy Stanley
--
Slawek Kaplonski
Principal Software Engineer
Red Hat
Hi,
Dnia środa, 23 sierpnia 2023 11:45:31 CEST Nell Jerram pisze:
On Wed, 23 Aug 2023, 10:09 Slawek Kaplonski, skaplons@redhat.com wrote:
Hi,
Dnia wtorek, 22 sierpnia 2023 19:31:15 CEST Allison Price pisze:
In the 2023 results so far, approximately 8% of deployments are running
a release older than Mitaka. So while it’s a very small amount, I think it’s the most beneficial to the community to get the most accurate representation possible.
If that means adding a second question like Slawek proposes, we can make
that work. I would just need to know how the answer choices very by question. If y’all can provide that, I can make that update.
So those old core plugins were completly dropped (removed from neutron repo) in Neutron 8.0.0 (Mitaka). In 7.0.0 (Liberty) most of them were removed but not all. In Mitaka all except ML2 and Hyper-v was deleted already.
To have most accurate representation possible and if we can split it into two questions then we would like it to be be like:
Which OpenStack Network (Neutron) *core plugin* are you using?
A10 Networks
Arista
Big Switch
Brocade / Broadcom
Calico
Cisco UCS / Nexus
Embrane
Extreme Networks
Hyper-V
IBM SDN-VE
Linux Bridge
Mellanox
Meta Plugin
MidoNet
Modular Layer 2 Plugin (ML2)
NEC OpenFlow
nova-network
OpenDaylight
Nuage Networks
One Convergence NVSD
OpenContrail or Juniper
Open vSwitch
PLUMgrid
Ruijie Networks
VMWare NSX (formerly Nicira NVP)
If You choose *Modular Layer 2 Plugin (ML2)* in the previous question,
what mechanism driver(s) are You using?
Alcatel-Lucent Omniswitch Arista Big Switch Brocade VDX/VCS Calico Cisco APIC Cisco DFA Cloudbase Hyper-V Freescale SDN Frescale FWaaS Fujitsu Converged Fabric Switch Huawei Agile Controller Linux Bridge Mellanox Mellanox SR-IOV MidoNet Nuage Networks ONOS One Convergence OpenDaylight OpenFlow Agent Open vSwitch OVN SR-IOV Pluribus Tail-F VMWare DVS Other Mechanism DriverPlease let me know if that would be fine for You too. Thx in advance
For what it's worth, I agree that that is a better way to ask these questions, compared with the previous arrangement.
I wonder, though, if we might simplify further by glossing over the core plugin vs. ML2 driver distinction?
- On the users' side, is it possible that some respondents wouldn't be sure
of this detail, and so would find the survey harder to complete?
As they aren't today and IMO having e.g. both "Openvswitch" and "ML2 - Openvswitch" options in the same question may be confusing as well.
- On the developers' side, does anyone really care if a networking solution
is being used as a core plugin instead of as an ML2 driver, or vice versa?
It's maybe not that critical for developers but IMO it would be good to see how many users are using "default" ML2 plugin and how many are using some custom, 3rd party implementations of Neutron.
(I can confirm that Calico continues to be available out-of-tree both as a core plugin and as an ML2 mechanism driver.)
Best wishes - Nell
On Aug 22, 2023, at 8:38 AM, Jeremy Stanley fungi@yuggoth.org wrote:
On 2023-08-22 09:21:03 +0200 (+0200), Slawek Kaplonski wrote:
[...]
In this question there are actually mixed core plugins (like old
Openvswitch) and ML2 plugin's mechanism drivers (like e.g.
ML2-Openvswitch). Those old core plugins which we proposed to
remove were removed from Neutron around version (2015.0.0 and
7.0.0 - I don't even remember what OpenStack version it was then).
[...]
According to https://releases.openstack.org/ Juno was 2014.2 and
Kilo was 2015.1.0 (there was no 2015.0.0), while Liberty was 7.0.0.
If these were all removed by Mitaka and there are very few
respondents indicating they're running deployments that old, then it
may make sense to clean those options up. If they were still
available options for a while after that (merely deprecated) or if
there are still a lot of respondents with deployments of that
vintage, then it may make more sense to reword those options for
clarity, to something like:
"Old/Legacy Openvswitch core plugin (OpenStack Liberty and earlier)"
--
Jeremy Stanley
--
Slawek Kaplonski
Principal Software Engineer
Red Hat
Ok, we will make it two separate questions.
Thank you for your flexibility on this!
Allison
On Aug 23, 2023, at 4:03 AM, Slawek Kaplonski skaplons@redhat.com wrote:
Hi,
Dnia wtorek, 22 sierpnia 2023 19:31:15 CEST Allison Price pisze:
In the 2023 results so far, approximately 8% of deployments are running a release older than Mitaka. So while it’s a very small amount, I think it’s the most beneficial to the community to get the most accurate representation possible.
If that means adding a second question like Slawek proposes, we can make that work. I would just need to know how the answer choices very by question. If y’all can provide that, I can make that update.
So those old core plugins were completly dropped (removed from neutron repo) in Neutron 8.0.0 (Mitaka). In 7.0.0 (Liberty) most of them were removed but not all. In Mitaka all except ML2 and Hyper-v was deleted already. To have most accurate representation possible and if we can split it into two questions then we would like it to be be like:
Which OpenStack Network (Neutron) core plugin are you using? A10 Networks Arista Big Switch Brocade / Broadcom Calico Cisco UCS / Nexus Embrane Extreme Networks Hyper-V IBM SDN-VE Linux Bridge Mellanox Meta Plugin MidoNet Modular Layer 2 Plugin (ML2) NEC OpenFlow nova-network OpenDaylight Nuage Networks One Convergence NVSD OpenContrail or Juniper Open vSwitch PLUMgrid Ruijie Networks VMWare NSX (formerly Nicira NVP)
If You choose Modular Layer 2 Plugin (ML2) in the previous question, what mechanism driver(s) are You using? Alcatel-Lucent Omniswitch Arista Big Switch Brocade VDX/VCS Calico Cisco APIC Cisco DFA Cloudbase Hyper-V Freescale SDN Frescale FWaaS Fujitsu Converged Fabric Switch Huawei Agile Controller Linux Bridge Mellanox Mellanox SR-IOV MidoNet Nuage Networks ONOS One Convergence OpenDaylight OpenFlow Agent Open vSwitch OVN SR-IOV Pluribus Tail-F VMWare DVS Other Mechanism Driver
Please let me know if that would be fine for You too. Thx in advance
On Aug 22, 2023, at 8:38 AM, Jeremy Stanley fungi@yuggoth.org wrote:
On 2023-08-22 09:21:03 +0200 (+0200), Slawek Kaplonski wrote: [...]
In this question there are actually mixed core plugins (like old Openvswitch) and ML2 plugin's mechanism drivers (like e.g. ML2-Openvswitch). Those old core plugins which we proposed to remove were removed from Neutron around version (2015.0.0 and 7.0.0 - I don't even remember what OpenStack version it was then).
[...]
According to https://releases.openstack.org/ Juno was 2014.2 and Kilo was 2015.1.0 (there was no 2015.0.0), while Liberty was 7.0.0.
If these were all removed by Mitaka and there are very few respondents indicating they're running deployments that old, then it may make sense to clean those options up. If they were still available options for a while after that (merely deprecated) or if there are still a lot of respondents with deployments of that vintage, then it may make more sense to reword those options for clarity, to something like:
"Old/Legacy Openvswitch core plugin (OpenStack Liberty and earlier)"
-- Jeremy Stanley
-- Slawek Kaplonski Principal Software Engineer Red Hat
Hi,
Dnia czwartek, 24 sierpnia 2023 22:49:08 CEST Allison Price pisze:
Ok, we will make it two separate questions.
Thx a lot.
Thank you for your flexibility on this!
Allison
On Aug 23, 2023, at 4:03 AM, Slawek Kaplonski skaplons@redhat.com wrote:
Hi,
Dnia wtorek, 22 sierpnia 2023 19:31:15 CEST Allison Price pisze:
In the 2023 results so far, approximately 8% of deployments are running a release older than Mitaka. So while it’s a very small amount, I think it’s the most beneficial to the community to get the most accurate representation possible.
If that means adding a second question like Slawek proposes, we can make that work. I would just need to know how the answer choices very by question. If y’all can provide that, I can make that update.
So those old core plugins were completly dropped (removed from neutron repo) in Neutron 8.0.0 (Mitaka). In 7.0.0 (Liberty) most of them were removed but not all. In Mitaka all except ML2 and Hyper-v was deleted already. To have most accurate representation possible and if we can split it into two questions then we would like it to be be like:
Which OpenStack Network (Neutron) core plugin are you using? A10 Networks Arista Big Switch Brocade / Broadcom Calico Cisco UCS / Nexus Embrane Extreme Networks Hyper-V IBM SDN-VE Linux Bridge Mellanox Meta Plugin MidoNet Modular Layer 2 Plugin (ML2) NEC OpenFlow nova-network OpenDaylight Nuage Networks One Convergence NVSD OpenContrail or Juniper Open vSwitch PLUMgrid Ruijie Networks VMWare NSX (formerly Nicira NVP)
If You choose Modular Layer 2 Plugin (ML2) in the previous question, what mechanism driver(s) are You using? Alcatel-Lucent Omniswitch Arista Big Switch Brocade VDX/VCS Calico Cisco APIC Cisco DFA Cloudbase Hyper-V Freescale SDN Frescale FWaaS Fujitsu Converged Fabric Switch Huawei Agile Controller Linux Bridge Mellanox Mellanox SR-IOV MidoNet Nuage Networks ONOS One Convergence OpenDaylight OpenFlow Agent Open vSwitch OVN SR-IOV Pluribus Tail-F VMWare DVS Other Mechanism Driver
Please let me know if that would be fine for You too. Thx in advance
On Aug 22, 2023, at 8:38 AM, Jeremy Stanley fungi@yuggoth.org wrote:
On 2023-08-22 09:21:03 +0200 (+0200), Slawek Kaplonski wrote: [...]
In this question there are actually mixed core plugins (like old Openvswitch) and ML2 plugin's mechanism drivers (like e.g. ML2-Openvswitch). Those old core plugins which we proposed to remove were removed from Neutron around version (2015.0.0 and 7.0.0 - I don't even remember what OpenStack version it was then).
[...]
According to https://releases.openstack.org/ Juno was 2014.2 and Kilo was 2015.1.0 (there was no 2015.0.0), while Liberty was 7.0.0.
If these were all removed by Mitaka and there are very few respondents indicating they're running deployments that old, then it may make sense to clean those options up. If they were still available options for a while after that (merely deprecated) or if there are still a lot of respondents with deployments of that vintage, then it may make more sense to reword those options for clarity, to something like:
"Old/Legacy Openvswitch core plugin (OpenStack Liberty and earlier)"
-- Jeremy Stanley
-- Slawek Kaplonski Principal Software Engineer Red Hat
participants (7)
-
Allison Price
-
James Page
-
Jeremy Stanley
-
Lajos Katona
-
Nell Jerram
-
Rodolfo Alonso Hernandez
-
Slawek Kaplonski