[nemo-dev] 答复: [nemo]user manual

Bert Wijnen (IETF) bwietf at bwijnen.net
Mon Sep 28 08:11:25 UTC 2015


Great.

And I am looking forward to an updated user manual and a Reference manual.

Bert

On 28/09/15 04:45, zhangyali (D) wrote:
> Hi Bert, thanks for your review for this user manual. This version is a initial version, which needs to be improved continuously. And I am very grateful to you for your question and advice.
>
> For your question,
> 1. I also plan to list all predefined types in a reference manual, which I think it's more clear to show what types are supported by our engine naturally. I am doing some work in the reference manual, and will upload it soon.
> 2. About the VN, as you have said, it is a virtual namespace. Every tenant has his own namespace, which is isolated with other namespaces. In this namespace, tenant could construct his own virtual network and deploy his policies. And another key point is, the tenant should maintain their namespace by himself, such as, policy conflict.
> 3. About the relationship between connection and communication, we have discussed about it for a long time. I think connection represents the physical resources between nodes. In the connection, we can assign its bandwidth. And node can communicate with other nodes as long as we can find the path between them, and the path can be one connection or the combination between many connections. In your example, the connection between n1, n2,n3, represents that there are direct resources could connect these nodes together. And these nodes are allowed to communicate with each other, including n1 and n3.
>
> I will update the user manual and reference manual soon, and look forward to your suggestions. Thanks so much!
>
>
> Yali
>   
> -----邮件原件-----
> 发件人: Bert Wijnen (IETF) [mailto:bwietf at bwijnen.net]
> 发送时间: 2015年9月25日 21:22
> 收件人: zhangyali (D); nemo-dev at lists.opendaylight.org
> 主题: Re: [nemo-dev] [nemo]user manual
>
> Thanks for that work.
>
> Maybe I expect too much from a "user manual". But I think I see TYPE sometimes as fw, sometimes as lb, then as l2-group .... etc.
>
> Is there a fixed list of types? Or are they dynamically specified/defined/created? That is (for me at least) unclear from the manual. I would expect a list of valid types, no? You could say that such belongs in a reference manual. I can agree, but then would love to see that reference manual soon.
>
> You also use VN in the first figure and further throughout the manual. You explain that each tenant has his own VN space. What does VN stand for? Virtual Network maybe? Or is it Virtual Namespace, or what?
>
> In your figure about c3, nodes n1, n2, n3. you speak about the fact that you create a connection.
> In our IETF bar-bof we had discussion about this, namely, is it a physical connection, or a logical connection? And there was also confusion and dicussion on the question what it exactly means.
> Some stated that it means that a connection (communication) is allowed between those nodes.
> So we had an example aka
>
>         n1 ---- n2
>                       |
>                       |
>                      n3
>
> And in this case soem people thought that n1 was allowed to communicate with n2 That n2 was allowed to communicate with n3 But it did NOT imply that n1 was allowed to communicate with n3.
>
> I am not sure we got a final answer during our IETF bar-bof discussions. From you manual, I cannot also not determine waht the above picture would mean. Would be great if that can be made clear.
>
> Bert Wijnen
> On 25/09/15 11:16, zhangyali (D) wrote:
>> Hi Team,
>>
>> I have generated a NEMO user manual according to our latest design and implement.
>>
>> The wiki link is at:
>>
>> https://wiki.opendaylight.org/view/NEMO:User_Manual
>>
>> Please review and comment.
>>
>> Thanks,
>>
>> Yali
>>
>> Best Regards,
>>
>> Yali
>>
>>
>>
>> _______________________________________________
>> nemo-dev mailing list
>> nemo-dev at lists.opendaylight.org
>> https://lists.opendaylight.org/mailman/listinfo/nemo-dev



More information about the nemo-dev mailing list