Thanks Sir,Since i understand the usability of ovsdb and the standard
interfaces that you have defined, thanks for it
i would like to extend this to my own configurations(which are not Open vSwitch
environments) to be pushed to remote clients by a centralized entity,I have
several clients monitoring on this configuration changes, the configurations
could be anything which is not restricted to only Open vSwitch could you please
let me know if it is not designed/ cannot use . I am going through your OVN
architecture but my immediate requirement is i want to use ovsdb and design a
system that contains a centralized entity and thousands of entity listening to
it for the configuration, could you please let me know if ovsdb is not designed
for this.ThanksVishnu
From: Ben Pfaff <[email protected]>
To: vis reddy <[email protected]>
Cc: "[email protected]" <[email protected]>
Sent: Monday, 23 March 2015 5:17 PM
Subject: Re: [ovs-discuss] ovsdb update operation
On Mon, Mar 23, 2015 at 11:27:01PM +0000, vis reddy wrote:
> Thanks Sir,I have another question, was there any scalability numbers that
> are available?
> I had created 2000 ovsdb-client monitoring on a database and??
> when i do a transact (insert operation) from another client i get following
> error,
> error: Connection reset by peerovsdb-client: transaction failed (Connection
> reset by peer)
> Was there any profiling done on ??ovsdb in terms of how many clients??can be
> supported and also does it depend on ??data in tables?I am using a very large
> tables (potentially running into couple of mb's)
We don't have a use case for that, so we didn't test for it.
In Open vSwitch environments there are normally only a single-digit
number of clients.
What is your use case?
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
