On Fri, Jun 30, 2023 at 3:31 AM Frode Nordahl <frode.nord...@canonical.com>
wrote:

> Hello all,
>
> On Tue, May 30, 2023 at 5:16 PM Felix Huettner
> <felix.huettner@mail.schwarz> wrote:
> >
> > Hi Dumitru,
> >
> > On Fri, May 26, 2023 at 01:30:54PM +0200, Dumitru Ceara wrote:
> > > On 5/24/23 09:37, Felix Huettner wrote:
> > > > Hi everyone,
> > >
> > > Hi Felix,
> > >
> > > >
> > > > Ilya mentioned to me that you will want to bring openstack examples
> to
> > > > ovn-heater.
> > > >
> > >
> > > Yes, we're discussing that.
> > >
> > > > I wanted to ask how to best join this effort. It would be great for
> us
> > >
> > > Everyone is welcome to contribute! :)
> > >
> >
> > Great, we will try that out.
>
> Thank you for your interest in this effort, as promised I'm in the
> process of organizing a community meeting to get this going.
>
> Below are some proposals for dates and times, please respond with a
> prioritized list of what works best for you and we'll try to land on a
> single date/time for a first meeting:
> Wednesday July 5th 13:00 UTC
> Tuesday July 11th 13:30 UTC
>

I'm interested in the topic. I am in EST and I don't think 8:30 UTC would
work for anyone in US / Canada. If possible, I'd suggest to hold it ~13 -
13:30 as the two options above.

Thanks!


> Wednesday July 12th 8:30 UTC
>
> > > > to have a tool to scale test ovn. Also we have an ovn deployment with
> > > > currently 450 compute nodes where we can try to extract the typically
> > > > used northbound entries from.
> > > >
> > >
> > > This is great!  I'm not an OpenStack user so I'm probably not using the
> > > right terminology and I might be missing things but I think we're
> > > interested in:
> > > - how many tenant networks do you have in the cluster
> > > - for each tenant network:
> > >   - how many VMs (on average but maybe also min/max/etc)
> > >   - how many floating IPs (dnat-and-snat)
> > >   - how many compute nodes run VMs from this network
> > > - for each compute:
> > >   - how many VMs run on it (on average but also min/max/etc)
> > >
> >
> > Ok, so i'll try to give an overview below.
> > If you need any more detail just ask.
> >
> > General amount of nodes:
> > * ~500 Hypervisors
> > * 9 Nodes that are just serve as gateway chassis (connected to 4
> >   different external networks)
> >
> > Amount of tenant Networks (== logical routers): 2300 (only 1400 are
> > actually hosting VMs).
> >
> > Amount of logical Routers: 2010 (2000 of these have a chassisredirect
> > port that is hosted on one of the 9 nodes.
> >
> > * Amount of VMs:
> >    * min: 1
> >    * max: 300
> >    * avg: 4.5
> >    * 630 networks only have a single VM, 230 have two VMs and 190 have 3
> >      VMs.
> > * Amount of Hypervisors per network:
> >    * min: 1
> >    * max: 90
> >    * avg: 3.6
> >    * 650 networks only strech on a single hypervisor, 250 on two
> >      hypervisors, 180 on three hypervisors
> >
> > Regarding floating ips we have currently 1530. I'll give you the amount
> > per Logical router:
> > * min: 1
> > * max: 230
> > * avg: 2.7
> > * 430 routers have a single floating ip, 140 routers have 2 floating
> >   ips.
> >
> > Regarding VMs per Hypervisor we have:
> > * min: 1
> > * max: 80
> > * avg: 15
> >
> >
> > Other potentially interesting values:
> >
> > * Amount of Load_Balancer: 0
> > * Amount of Logical_Switch_Port type=virtual: 800
> > * Amount of Port_Group: 6000
> > * Amount of ACL: 35500
> >    * All of these referce portgroups in `match` using `@` or `$`
> >    * Referencing other portgroups using `$`: 8300
>
> Thanks alot for providing this information, and gauging the size of
> your deployment, your inputs would be very valuable in this effort.
> One of the main goals of ovn-heater is the ability to simulate
> workloads, because as developers, we seldom have access to actual 500-
> or 1000- node clusters. Having a participant in the project with
> actual hardware installation of such a size would give us the
> opportunity to help confirm the accuracy of our simulations.
>
> --
> Frode Nordahl
>
> > Regards
> > Felix
> >
> > > Mayba Frode and Daniel can expand on this.
> > >
> > > Regards,
> > > Dumitru
> > >
> > > > Thanks
> > > > Felix
> > > >
> > > > On Tue, May 16, 2023 at 05:38:25PM +0200, Daniel Alvarez Sanchez
> wrote:
> > > >> Hey Frode, Dumitru, thanks a lot for initiating this
> > > >>
> > > >> On Thu, May 11, 2023 at 6:05 PM Frode Nordahl <
> frode.nord...@canonical.com>
> > > >> wrote:
> > > >>
> > > >>> Hello, Dumitru, Daniel and team,
> > > >>>
> > > >>> On Thu, May 11, 2023 at 5:23 PM Dumitru Ceara <dce...@redhat.com>
> wrote:
> > > >>>>
> > > >>>> Hi Frode,
> > > >>>>
> > > >>>> During an internal discussion with RedHat OpenStack folks (Daniel
> in cc)
> > > >>>> about scalability of OVN in OpenStack deployments I remembered
> that you
> > > >>>> mentioned that you're thinking of enhancing ovn-heater in order
> to test
> > > >>>> your types of deployments [0].  I assumed that those are also
> OpenStack
> > > >>>> based deployments so I was wondering if there's an opportunity for
> > > >>>> collaboration here.
> > > >>>
> > > >>> Thank you for reaching out to me on this topic. We do indeed have
> scale
> > > >>> testing in the context of OpenStack on our roadmap and welcome the
> > > >>> invitation to collaborate on this.
> > > >>>
> > > >>> As you know we did some preparation work together already as you
> refer
> > > >>> to in [0], and we thank you for your help in upstreaming
> ovn-heater.
> > > >>>
> > > >>> We have yet to schedule exactly when in the cycle to work on this,
> I
> > > >>> guess a next step could be to set up a meet to share some ideas and
> > > >>> see how it aligns?
> > > >>
> > > >>
> > > >>> If that resonates with you, I'd be happy to organize.
> > > >>>
> > > >>
> > > >> Sounds good, please do :)
> > > >>
> > > >>
> > > >>>
> > > >>>> Having OpenStack-like scenarios in ovn-heater would really allow
> OVN
> > > >>>> developers to profile/troubleshoot/optimize OVN for those use
> cases too.
> > > >>>>
> > > >>>> Well, in general, the above is true for any other CMS too.
> > > >>>
> > > >>> Yes, this is what we have been thinking as well. We are supporting
> other
> > > >>> products in their journey with OVN as well, so similar projects
> may come
> > > >>> from those in the future.
> > > >>>
> > > >>
> > > >> Yes, we can try to model OpenStack-like scenarios for ovn-heater
> where the
> > > >> resources are generally more distributed across the hypervisors
> than in k8s
> > > >> for example, perhaps larger L2 domain sizes, etcetera.
> > > >> Happy to discuss further!
> > > >>
> > > >> daniel
> > > >>
> > > >>
> > > >>> --
> > > >>> Frode Nordahl
> > > >>>
> > > >>>> Thanks,
> > > >>>> Dumitru
> > > >>>>
> > > >>>> [0]
> > > >>>
> https://mail.openvswitch.org/pipermail/ovs-dev/2023-March/402680.html
> > > >>>>
> > > >>>
> > > >>>
> > > >> _______________________________________________
> > > >> dev mailing list
> > > >> d...@openvswitch.org
> > > >> https://mail.openvswitch.org/mailman/listinfo/ovs-dev
> > > > Diese E Mail enthält möglicherweise vertrauliche Inhalte und ist nur
> für die Verwertung durch den vorgesehenen Empfänger bestimmt.
> > > > Sollten Sie nicht der vorgesehene Empfänger sein, setzen Sie den
> Absender bitte unverzüglich in Kenntnis und löschen diese E Mail.
> > > >
> > > > Hinweise zum Datenschutz finden Sie hier<
> https://www.datenschutz.schwarz/>.
> > > >
> > > >
> > > > This e-mail may contain confidential content and is intended only
> for the specified recipient/s.
> > > > If you are not the intended recipient, please inform the sender
> immediately and delete this e-mail.
> > > >
> > > > Information on data protection can be found here<
> https://www.datenschutz.schwarz/>.
> > > >
> > >
> > Diese E Mail enthält möglicherweise vertrauliche Inhalte und ist nur für
> die Verwertung durch den vorgesehenen Empfänger bestimmt.
> > Sollten Sie nicht der vorgesehene Empfänger sein, setzen Sie den
> Absender bitte unverzüglich in Kenntnis und löschen diese E Mail.
> >
> > Hinweise zum Datenschutz finden Sie hier<
> https://www.datenschutz.schwarz/>.
> >
> >
> > This e-mail may contain confidential content and is intended only for
> the specified recipient/s.
> > If you are not the intended recipient, please inform the sender
> immediately and delete this e-mail.
> >
> > Information on data protection can be found here<
> https://www.datenschutz.schwarz/>.
> _______________________________________________
> dev mailing list
> d...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-dev
>
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to