[openstack-dev] [tricircle] cross-OpenStack L2 Networking spec review

Shinobu Kinjo shinobu.kj at gmail.com
Sun May 8 08:41:14 UTC 2016


Hi Chaoyi,

On Sun, May 8, 2016 at 4:48 PM, joehuang <joehuang at huawei.com> wrote:
> Hi, Shinobu,
>
> Agree with you that it's a challenge to explain Tricircle and cross OpenStack L2 networking in short.

Because the Tricircle is awesome!

> So do you have any suggestion to provide a short but very accurate and clear (concise description) for Tricircle and the feature cross OpenStack L2 networking?
> And how to enhance the blueprint to help readers easy to understand?

This is what I'm trying to do *every single day*.
You may notice that, I guess -;

Cheers,
Shinobu

>
> Best Regards
> Chaoyi Huang ( joehuang )
>
> ________________________________________
> From: Shinobu Kinjo [shinobu.kj at gmail.com]
> Sent: 08 May 2016 10:12
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: [openstack-dev] [tricircle] cross-OpenStack L2 Networking spec review
>
> Hi Team,
>
> Since there was no tag [tricircle] in subject, I'm emailing you again.
> Sorry for spam -;
>
> We are trying to describe specification [1] regarding to ""cross
> OpenStack L2 networking"" [0] as Chaoyi mentioned in previous message.
> Honestly that description [0] does not accurately describe what this
> project is trying to do. And it's hard to be described by few words as
> well.
>
> And he mentioned having a quick look at presentation material. [2]
> This is fine to understand this project. But it's still not good enough.
> AFAK it's because that those kind of materials are completely based on
> our blueprint. [3].
>
> IMHO I would recommend you to start from that blurprint.
> At least from:
>
>  7. Stateless Architecture Proposal
>
> If some sentences are not based on that blueprint, that's a problem.
>
> But even you read that blueprint, you do not really understand what
> this project is trying to do.
> This is a real problem. We have to fix a blueprint first.
>
> Otherwise we face double-writes issue which could cause huge risk to
> this project.
>
> [1] https://review.openstack.org/#/c/304540/
> [2] https://docs.google.com/presentation/d/1UQWeAMIJgJsWw-cyz9R7NvcAuSWUnKvaZFXLfRAQ6fI/edit
> [3] https://docs.google.com/document/d/18kZZ1snMOCD9IQvUKI5NVDzSASpw-QKj7l2zNqMEd3g/edit#
>
> If I've been missing anything, please point it out to me.
>
> Cheers,
> Shinobu
>
> --
> Email:
> shinobu at linux.com
> shinobu at redhat.com
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Email:
shinobu at linux.com
shinobu at redhat.com



More information about the OpenStack-dev mailing list