Network traffic shaping.

[Giuseppe Vallarelli]

----- Original Message -----
| From: "Mike Kolesnik" <mkolesni at redhat.com>
| To: "Giuseppe Vallarelli" <gvallare at redhat.com>
| Cc: arch at ovirt.org
| Sent: Thursday, July 11, 2013 8:35:05 AM
| Subject: Re: Network traffic shaping.
| 
| Hi Giuseppe,
| 
| The feature looks like it will be good to have.
| I have some thoughts:
| 
| 1. If the QoS is a different entity that you're creating when creating the
| network,
| I think there should be an option to choose an existing QoS or create a new
| one,
| say a combo box where you can choose an existing QoS (Then the parameters
| appear, but read-only)
| or enter the name of a new QoS and fill the parameters by yourself.

Ok I agree with you, makes sense. Always related to this matter mostly
to the quality of service table, wouldn't be better to have a db table
formed with these attributes: id, avg, burst, peak (table name qos)
so a vnic or a network can link to it - without 'owning' these attributes.

| 2. What is the proposed permissions model?

I form an idea still and update the feature page accordingly.

| 
| 3. Please consider how you would handle this in Setup Networks:
| 3.1. How will you handle only delta?
| 3.2. Are you going to handle this with regards to sync between host actual
| definition, and logical definition?
| 3.3. This would imply that you need to report this data back from VDSM and
| save it per host NIC..
| 
| 4. In the DB change section you should specify which columns/constraints
| you're going to add.

same as point 2. Thanks for the feedback I need to refine furthermore
the proposal.

Cheers, Giuseppe

| 
| Regards,
| Mike


| 
| ----- Original Message -----
| > Hi everybody, I'm working to implement traffic shaping at the network level
| > [1].
| > This feature is composed by two distinct parts: definition of traffic
| > shaping
| > for a logical network entity and optional redefinition of traffic shaping
| > when
| > the user is doing a Setup Host Networks task. Initial focus will be on
| > first
| > part. There are some points of contact with Network Qos [2] that's why I
| > proposed
| > to reuse some code backend side.
| > 
| > Cheers, Giuseppe
| > 
| > [1] http://www.ovirt.org/Features/Network_traffic_shaping
| > [2] http://www.ovirt.org/Features/Network_QoS
| > _______________________________________________
| > Arch mailing list
| > Arch at ovirt.org
| > http://lists.ovirt.org/mailman/listinfo/arch
| > 
|