Sounds good.
You should read CONTRIBUTING.md and CodingStyle.md.
On Thu, Oct 06, 2016 at 09:48:06PM +0200, Łukasz Rząsik wrote:
> Hi,
>
> I wanted to start contributing to the project.
> If no one else is already working on that, I will try to implement it and
> submit a patch as a start.
>
> BR,
> Lucas
>
> 2016-10-04 3:19 GMT+02:00 Ben Pfaff <b...@ovn.org>:
>
> > This can occupy a lot of space.
> >
> > If you want to support ranges, you can submit a patch.
> >
> > On Mon, Oct 03, 2016 at 10:29:53PM +0000, my_ovs_disc...@yahoo.com wrote:
> > > Thanks Ben for the response.
> > > I see that whenever an ovs-vsctl command is issued it seems to go into
> > conf.db in JSON format as follows.
> > > ------------------------------------------------------------
> > ------------------------------------------------------------
> > -------------------------------------------------------------------
> > >
> > > OVSDB JSON 350 adea54d6f5617de72668fbac82f4ba47f5aa9459
> > > {"_date":1475533349806,"Port":{"a2a185d4-c018-481c-9c41-
> > a96998df77b7":{"trunks":["set",[2,3,4,5,6,7,8,9,10,11,12,13,
> > 14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,
> > 34,35,36,37,38,39,4094]]}},"_comment":"ovs-vsctl
> > > : /bin/ovs-vsctl add port 123456789012345 trunks
> > 39","Open_vSwitch":{"a0d40d36-fae6-4862-90cf-586bded25ae3":{
> > "next_cfg":63}}}
> > > OVSDB JSON 95 c2c2528b873474056ff64640cf5186a9ba1dbadb
> > > {"_date":1475533349814,"Open_vSwitch":{"a0d40d36-fae6-4862-
> > 90cf-586bded25ae3":{"cur_cfg":63}}}
> > > OVSDB JSON 353 ccbb33817b428a65406d93070f3dc3c85f5181b5
> > > {"_date":1475533349837,"Port":{"a2a185d4-c018-481c-9c41-
> > a96998df77b7":{"trunks":["set",[2,3,4,5,6,7,8,9,10,11,12,13,
> > 14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,
> > 34,35,36,37,38,39,40,4094]]}},"_comment":"ovs-vs
> > > ctl: /bin/ovs-vsctl add port 123456789012345 trunks
> > 40","Open_vSwitch":{"a0d40d36-fae6-4862-90cf-586bded25ae3":{
> > "next_cfg":64}}}
> > > OVSDB JSON 95 642d4c5ea430d66ca1ce4bd18747cb06d2f9227b
> > > {"_date":1475533349845,"Open_vSwitch":{"a0d40d36-fae6-4862-
> > 90cf-586bded25ae3":{"cur_cfg":64}}}
> > > OVSDB JSON 356 72c1435d0ce4e8393aa0a95da6238ca81b78142c
> > > {"_date":1475533349889,"Port":{"a2a185d4-c018-481c-9c41-
> > a96998df77b7":{"trunks":["set",[2,3,4,5,6,7,8,9,10,11,12,13,
> > 14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,
> > 34,35,36,37,38,39,40,41,4094]]}},"_comment":"ovs
> > > -vsctl: /bin/ovs-vsctl add port 123456789012345 trunks
> > 41","Open_vSwitch":{"a0d40d36-fae6-4862-90cf-586bded25ae3":{
> > "next_cfg":65}}}
> > > OVSDB JSON 95 618d1e741f0fbf7e373afb6245b7f2a882123d56
> > > {"_date":1475533349897,"Open_vSwitch":{"a0d40d36-fae6-4862-
> > 90cf-586bded25ae3":{"cur_cfg":65}}}
> > > OVSDB JSON 359 c05800747de4d9e5a9559ac2230e94826106f27f
> > > {"_date":1475533349924,"Port":{"a2a185d4-c018-481c-9c41-
> > a96998df77b7":{"trunks":["set",[2,3,4,5,6,7,8,9,10,11,12,13,
> > 14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,
> > 34,35,36,37,38,39,40,41,42,4094]]}},"_comment":"
> > > ovs-vsctl: /bin/ovs-vsctl add port 123456789012345 trunks
> > 42","Open_vSwitch":{"a0d40d36-fae6-4862-90cf-586bded25ae3":{
> > "next_cfg":66}}}
> > > OVSDB JSON 95 e501f33c436fdc44cbb73c5bf40d8527473b7895
> > > {"_date":1475533349945,"Open_vSwitch":{"a0d40d36-fae6-4862-
> > 90cf-586bded25ae3":{"cur_cfg":66}}}
> > > ------------------------------------------------------------
> > ------------------------------------------------------------
> > -------------------------------------
> > > For each trunk we add, this whole text is getting appended into conf.db
> > and this is per port. This seems to occupy lot of space onfile system.
> > > Is there a way to avoid this and keep only one instance of the config?
> > > -Thanks
> > >
> > >
> > > Sent from Yahoo Mail. Get the app
> > >
> > > From: Ben Pfaff <b...@ovn.org>
> > > To: my_ovs_disc...@yahoo.com
> > > Cc: "discuss@openvswitch.org" <discuss@openvswitch.org>
> > > Sent: Monday, October 3, 2016 2:29 PM
> > > Subject: Re: [ovs-discuss] Specifying range for bridge port trunks
> > >
> > > On Mon, Oct 03, 2016 at 09:23:59PM +0000, my_ovs_disc...@yahoo.com
> > wrote:
> > > > Hi, We are using openvswitch-2.5.0
> > > > Is there a way to specify a range for trunks under bridge port, like
> > > > vsctl add port port1 trunks 100-250
> > > > It could be for add/set.
> > > > In the conf.db, these trunks seem to be getting stored as individual
> > strings like 100,101,102, ... 250 and it seems to expect the command also
> > likevsctl add port port1 trunks 100,101,102,103...150
> > > > If I have to specify such ranges for multiple ports, the conf.db seems
> > to occupy a lot of space and this format also seems little difficult to
> > specify 100s of integers.
> > > > As I am not that familiar with OVS yet, am I missing something? Is
> > there a way to specify ranges and also minimize the conf.db space by
> > storing the ranges?
> > >
> > > OVS doesn't support ranges here. You can submit a patch to add a new
> > > feature, if you like.
> > >
> > >
> > >
> > _______________________________________________
> > discuss mailing list
> > discuss@openvswitch.org
> > http://openvswitch.org/mailman/listinfo/discuss
> >
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
