Khanh-Toan Tran <khanh-toan.t...@cloudwatt.com> wrote on 10/29/2013
09:10:00 AM:
> ...
> 1) Member of a group is recursive. A member can be group or an
> instance. In this case there are two different declaration formats
> for members, as with http-server-group-1 ("name, "policy", "edge")
> and Http-Server-1 ("name", "request_spec", "type"). Would it be
> better if group-typed member also have "type" field to better
> interpret the member? Like policy which has "type" field to declare
> that's a egde-typed policy or group-typed policy.
I have no strong opinion on this.
> 2) The "edge" is not clear to me. It seems to me that "edge" is just
> a place holder for the edge policy. Does it have some particular
> configuration like group members (e.g. group-typed member is
> described by its "member","edge" and "policy", while instance-typed
> member is described by its "request_spec") ?
Yes, an edge is just a way to apply a policy to an ordered pair of groups.
> 3) Members & groups have policy declaration nested in them. Why is
> edge-policy is declared outside of edge's declaration?
I agree, it would be more natural to write an edge's policy references
inside the edge object itself.
Thanks,
Mike
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
