On Thu, Jan 15, 2015 at 12:34:18PM +0530, Sahina Bose wrote: > > > I've updated the feature page with the REST API and other comments. On > further thought, there will be no change to Add brick API, as the engine > will select the network to be used based on the networks setup for the host. > If "Storage network" role is associated with any of the networks, this will > be used. Otherwise, the host's address will be used to add the brick. >
<snip> The paragraph above rules out the use case I lay below. Could you relate to it? Isn't it a reasonable use case? > >If I am not mistaken, it could make sense to have a setup with one brick > >using network A and another - using network B. Does your design support > >this? I think that this would be particularly important on upgraded > >clusters, where the management network is already used, but newly > >created bricks should start using another network. > > May I repeat my follow request? It would help me understand the content of the feature. > >Would you add a feature page section regarding modification to the > >Vdsm/Engine API? > >One last comment - may I ask that new APIs accept both ipv4 and ipv6 > >addresses? There is an ongoing effort to support ipv6 on Vdsm. _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel