Re: [openstack-dev] [tricircle] Tricircle or Trio2o

[linghucongsong]

HI !



we have made the tri020 work with the master version openstack as the below pr。

https://review.openstack.org/#/c/596258/



in our plan in the next step we will make tri020 work with the tricircle。see 
below plan.



https://etherpad.openstack.org/p/tricircle-stein-plan




At 2018-08-03 22:57:06, "Andrea Franceschini" 
 wrote:
>Hello  Ling,
>
>thank you for answering, I'm glad to see that Trio2o project will be
>revived in the near future.
>
>Meanwhile it would be nice to know what approach people use to deploy
>multi-site openstack.
>
>I mean, I've read somewhere about solutions using something like a
>multi-site heat, but I failed to dig into this as I couldn't find any
>resource.
>
>Thanks,
>
>Andrea
>
>Il giorno gio 2 ago 2018 alle ore 05:01 linghucongsong
> ha scritto:
>>
>> HI  Andrea !
>> Yes, just as you said.The tricircle is now only work for network.Because the 
>> trio2o do not
>> as the openstack official project. so it is a long time nobody contribute to 
>> it.
>> But recently In the next openstack stein circle. we have plan to make 
>> tricircle and
>> trio2o work together in the tricircle stein plan. see below link:
>> https://etherpad.openstack.org/p/tricircle-stein-plan
>> After this fininsh we can play tricircle and tri2o2 together and make 
>> multisite openstack
>> solutions more effictive.
>>
>>
>>
>>
>>
>> At 2018-08-02 00:55:30, "Andrea Franceschini" 
>>  wrote:
>> >Hello All,
>> >
>> >While I was looking for multisite openstack solutions I stumbled on
>> >Tricircle project which seemed fairly perfect for the job except that
>> >l it was split in two parts, tricircle itself for the network part and
>> >Trio2o for all the rest.
>> >
>> >Now it seems that the Trio2o project is no longer maintained  and I'm
>> >wondering what other options exist for multisite openstack, stated
>> >that tricircle seems more NFV oriented.
>> >
>> >Actually a heat multisite solution would work too, but I cannot find
>> >any  reference to this kind of solutions.
>> >
>> >Do you have any idea/advice?
>> >
>> >Thanks,
>> >
>> >Andrea
>> >
>> >__
>> >OpenStack Development Mailing List (not for usage questions)
>> >Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] Nominate change in tricircle core team

[zmj1981123]

+1


2018-08-09 20:04 GMT+08:00 linghucongsong :



Hi team, I would like to nominate Zhuo Tang (ztang) for tricircle core member. 
ztang has actively joined the discussion of feature development in our offline 
meeting and has participated in contribute important blueprints since Rocky, 
like network deletion reliability and service function chaining. I really think 
his experience will help us substantially improve tricircle.

Bye the way the vote unitl 2018-8-16 beijing time.


Best Wishes!
Baisen





 


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] Nominate change in tricircle core team

[陈亚光]

+1

2018-08-09 20:04 GMT+08:00 linghucongsong :

>
> Hi team, I would like to nominate Zhuo Tang (ztang) for tricircle core
> member. ztang has actively joined the discussion of feature development in
> our offline meeting and has participated in contribute important
> blueprints since Rocky, like network deletion reliability and service
> function chaining. I really think his experience will help us substantially
> improve tricircle.
> Bye the way the vote unitl 2018-8-16 beijing time.
>
> Best Wishes!
> Baisen
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] Nominate change in tricircle core team

[zhangchi]

+1



在 2018-08-11 10:04，linghucongsong 写道：

At 2018-08-09 20:04:40, "linghucongsong" 
wrote:


Hi team, I would like to nominate Zhuo Tang (ztang) for tricircle
core member. ztang has actively joined the discussion of feature
development in our offline meeting and has participated in
contribute important blueprints since Rocky, like network deletion
reliability and service function chaining. I really think his
experience will help us substantially improve tricircle.
Bye the way the vote unitl 2018-8-16 beijing time.

Best Wishes!
Baisen


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] Tricircle or Trio2o

[Andrea Franceschini]

Hello  Ling,

thank you for answering, I'm glad to see that Trio2o project will be
revived in the near future.

Meanwhile it would be nice to know what approach people use to deploy
multi-site openstack.

I mean, I've read somewhere about solutions using something like a
multi-site heat, but I failed to dig into this as I couldn't find any
resource.

Thanks,

Andrea

Il giorno gio 2 ago 2018 alle ore 05:01 linghucongsong
 ha scritto:
>
> HI  Andrea !
> Yes, just as you said.The tricircle is now only work for network.Because the 
> trio2o do not
> as the openstack official project. so it is a long time nobody contribute to 
> it.
> But recently In the next openstack stein circle. we have plan to make 
> tricircle and
> trio2o work together in the tricircle stein plan. see below link:
> https://etherpad.openstack.org/p/tricircle-stein-plan
> After this fininsh we can play tricircle and tri2o2 together and make 
> multisite openstack
> solutions more effictive.
>
>
>
>
>
> At 2018-08-02 00:55:30, "Andrea Franceschini" 
>  wrote:
> >Hello All,
> >
> >While I was looking for multisite openstack solutions I stumbled on
> >Tricircle project which seemed fairly perfect for the job except that
> >l it was split in two parts, tricircle itself for the network part and
> >Trio2o for all the rest.
> >
> >Now it seems that the Trio2o project is no longer maintained  and I'm
> >wondering what other options exist for multisite openstack, stated
> >that tricircle seems more NFV oriented.
> >
> >Actually a heat multisite solution would work too, but I cannot find
> >any  reference to this kind of solutions.
> >
> >Do you have any idea/advice?
> >
> >Thanks,
> >
> >Andrea
> >
> >__
> >OpenStack Development Mailing List (not for usage questions)
> >Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] Tricircle or Trio2o

[linghucongsong]

HI  Andrea !

Yes, just as you said.The tricircle is now only work for network.Because the 
trio2o do not

as the openstack official project. so it is a long time nobody contribute to it.
But recently In the next openstack stein circle. we have plan to make tricircle 
and

trio2o work together in the tricircle stein plan. see below link:
https://etherpad.openstack.org/p/tricircle-stein-plan

After this fininsh we can play tricircle and tri2o2 together and make multisite 
openstack

solutions more effictive.









At 2018-08-02 00:55:30, "Andrea Franceschini" 
 wrote:
>Hello All,
>
>While I was looking for multisite openstack solutions I stumbled on
>Tricircle project which seemed fairly perfect for the job except that
>l it was split in two parts, tricircle itself for the network part and
>Trio2o for all the rest.
>
>Now it seems that the Trio2o project is no longer maintained  and I'm
>wondering what other options exist for multisite openstack, stated
>that tricircle seems more NFV oriented.
>
>Actually a heat multisite solution would work too, but I cannot find
>any  reference to this kind of solutions.
>
>Do you have any idea/advice?
>
>Thanks,
>
>Andrea
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] Zuul v3 integration status

[Boden Russell]

Thanks for that.

I'm a bit concerned about how to proceed with dependencies in the
meantime, it's not realistic to hold all such patches until S.

Perhaps we can continue this discussion in [1]?

[1] https://bugs.launchpad.net/tricircle/+bug/1776922



On 6/19/18 7:38 PM, linghucongsong wrote:
> we will plan this as a bp, but maybe can not finished it
>
> in the R release, we promise must be finish it in the next openstack
> version.
>


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] Zuul v3 integration status

[linghucongsong]

Hi Boden！



I am song, I have discussed with the ptl zhiyuan.


we all think it is not a simple work to finish this.



we will plan this as a bp, but maybe can not finished it



in the R release, we promise must be finish it in the next openstack version.





At 2018-06-19 10:13:47, "linghucongsong"  wrote:



Hi Boden！ Thanks for report this bug.


we will talk about this bug in our meeting this week wednesday 9:00 beijing 
time.


if you have time i would like you join it in the openstack-meeting channel.









At 2018-06-15 21:56:29, "Boden Russell"  wrote:
>Is there anyone who can speak to the status of tricircle's adoption of
>Zuul v3?
>
>As per [1] it doesn't seem like the project is setup properly for Zuul
>v3. Thus, it's difficult/impossible to land patches like [2] that
>require neutron/master + a depends on patch.
>
>Assuming tricircle is still being maintained, IMO we need to find a way
>to get it up to speed with zuul v3; otherwise some of our neutron
>efforts will be held up, or tricircle will fall behind with respect to
>neutron-lib adoption.
>
>Thanks
>
>
>[1] https://bugs.launchpad.net/tricircle/+bug/1776922
>[2] https://review.openstack.org/#/c/565879/
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] Zuul v3 integration status

[linghucongsong]

Hi Boden！ Thanks for report this bug.


we will talk about this bug in our meeting this week wednesday 9:00 beijing 
time.


if you have time i would like you join it in the openstack-meeting channel.









At 2018-06-15 21:56:29, "Boden Russell"  wrote:
>Is there anyone who can speak to the status of tricircle's adoption of
>Zuul v3?
>
>As per [1] it doesn't seem like the project is setup properly for Zuul
>v3. Thus, it's difficult/impossible to land patches like [2] that
>require neutron/master + a depends on patch.
>
>Assuming tricircle is still being maintained, IMO we need to find a way
>to get it up to speed with zuul v3; otherwise some of our neutron
>efforts will be held up, or tricircle will fall behind with respect to
>neutron-lib adoption.
>
>Thanks
>
>
>[1] https://bugs.launchpad.net/tricircle/+bug/1776922
>[2] https://review.openstack.org/#/c/565879/
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] Nominate change in tricircle core team (crh)

[Yipei Niu]

+1.

Best regards,
Yipei
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] Nominate change in tricircle core team

[crh]

+1. It is so cool to see the new core reviewer



--



Best regards,
Ronghui Cao, Ph.D. Candidate
College of Information Science and Engineering
Hunan University, Changsha 410082, Hunan, China

At 2018-03-12 09:12:48, "joehuang"  wrote:



+1. Baisen has contributed lots of patches in Tricircle.



Best Regards
Chaoyi Huang (joehuang)
From: Vega Cai [luckyveg...@gmail.com]
Sent: 12 March 2018 9:04
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [tricircle] Nominate change in tricircle core team


Hi team, I would like to nominate Baisen Song (songbaisen) for tricircle core 
reviewer. Baisen has actively joined the discussion of feature development and 
has contributed important patches since Queens, like resource deletion 
reliability and openstack-sdk new version adaption. I really think his 
experience will help us substantially improve tricircle.


BR
Zhiyuan
--

BR
Zhiyuan__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] Nominate change in tricircle core team

[joehuang]

+1. Baisen has contributed lots of patches in Tricircle.

Best Regards
Chaoyi Huang (joehuang)

From: Vega Cai [luckyveg...@gmail.com]
Sent: 12 March 2018 9:04
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [tricircle] Nominate change in tricircle core team

Hi team, I would like to nominate Baisen Song (songbaisen) for tricircle core 
reviewer. Baisen has actively joined the discussion of feature development and 
has contributed important patches since Queens, like resource deletion 
reliability and openstack-sdk new version adaption. I really think his 
experience will help us substantially improve tricircle.

BR
Zhiyuan
--
BR
Zhiyuan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]Distinguish the direction of requests

[Vega Cai]

For the first question, since api-paste.ini is a configuration file, you
can just add your new filter to the configuration file so your filter can
take effect. As Joe suggests, you can add embed the information in the
oslo.context object so plugin can get it from context which is passed to
plugin.

On Fri, 3 Nov 2017 at 12:29 joehuang  wrote:

> Hello,
>
> As you are talking about how to distinguish the request to local Neutron
> and central Neutron, do you mean how to set the "USER_AGENT" in the request
> header, and how to extract the "USER_AGENT" and stored it in the context?
> Though it's mentioned in
> https://developer.openstack.org/sdks/python/openstacksdk/users/connection.html
>
> This field has not been extracted neither in oslo.context, nor neutron-lib
> context:
>
>
> https://github.com/openstack/oslo.context/blob/master/oslo_context/context.py
> https://github.com/openstack/neutron-lib/blob/master/neutron_lib/context.py
>
>
> May be we can add it in oslo.context?
>
> Best Regards
> Chaoyi Huang (joehuang)
> --
> *From:* XuZhuang [xu_ly...@163.com]
> *Sent:* 01 November 2017 19:49
> *To:* openstack-dev@lists.openstack.org
> *Subject:* [openstack-dev] [tricircle]Distinguish the direction of
> requests
>
> Hello,
>
> I have some questions in how to distinguish the direction of requests
> between local neutron and central neutron.
>
>
> There is the preliminary plan
>
>
> 1. For how to distinguish the requests in central neutron
>
> we can add a filter in neutron/…./etc/api-paste.ini. Using this filter we
> can get some values about the source.
>
> But the question is that the process of loading filter is in Neutron.
> Without changing Neutron how could we add a filter? Could we change Neutron?
>
>
> 2. For how to add a signal in the requests
>
> The module of common.client in Tricircle is responsible for sending
> requests. So we can add a signal in the header of requests. And central
> plugin will get this signal using the filter.
>
>
> Best Regards
>
> Zhuangzhuang Xu (Lyman Xu)
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-- 
BR
Zhiyuan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]Distinguish the direction of requests

[joehuang]

Hello,

As you are talking about how to distinguish the request to local Neutron and 
central Neutron, do you mean how to set the "USER_AGENT" in the request header, 
and how to extract the "USER_AGENT" and stored it in the context? Though it's 
mentioned in 
https://developer.openstack.org/sdks/python/openstacksdk/users/connection.html

This field has not been extracted neither in oslo.context, nor neutron-lib 
context:

https://github.com/openstack/oslo.context/blob/master/oslo_context/context.py
https://github.com/openstack/neutron-lib/blob/master/neutron_lib/context.py

May be we can add it in oslo.context?

Best Regards
Chaoyi Huang (joehuang)

From: XuZhuang [xu_ly...@163.com]
Sent: 01 November 2017 19:49
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [tricircle]Distinguish the direction of requests

Hello,


I have some questions in how to distinguish the direction of requests between 
local neutron and central neutron.


There is the preliminary plan


1. For how to distinguish the requests in central neutron

we can add a filter in neutron/…./etc/api-paste.ini. Using this filter we can 
get some values about the source.

But the question is that the process of loading filter is in Neutron. Without 
changing Neutron how could we add a filter? Could we change Neutron?


2. For how to add a signal in the requests

The module of common.client in Tricircle is responsible for sending requests. 
So we can add a signal in the header of requests. And central plugin will get 
this signal using the filter.


Best Regards

Zhuangzhuang Xu (Lyman Xu)




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle-Problem accessing the instance console]

[Vega Cai]

Hi Meher,

You can first check whether the nova-consoleauth and nova-novncproxy
services are correctly running. If you use DevStack, the window names for
these two services are n-cauth and n-novnc.

BR
Zhiyuan

On Wed, 23 Aug 2017 at 23:55  wrote:

> Hello to the Tricircle community,
>
>
>
> I am sending you this mail in order to ask for help concerning the launch
> of the console of the instances created in the different regions.
>
>
>
> I have two regions each with an active instance and its status is
> "running", for the first region, I can not open the console from the
> dashboard and for the second, the console is displayed but with an error of
> connection to the server.
>
> PS: access to both console worked without problems before I restarted my
> server.
>
>
>
> Thank you in advance for your help.
>
>
>
> Best regards,
>
>
>
> Meher
>
>
>
> (+33) 7 58 38 68 87 <+33%207%2058%2038%2068%2087>
>
>
>
> [image: Logo Orange] 
>
>
>
> *Meher Hihi *
> Intern
> ORANGE/IMT/OLN/WTC/CMA/MAX
>
> Fixe : +33 2 96 07 03 71
> 
> Mobile : +33 7 58 38 68 87
> 
> meher.h...@orange.com
>
>
>
>
>
> _
>
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
> ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou 
> falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged 
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete 
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been 
> modified, changed or falsified.
> Thank you.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-- 
BR
Zhiyuan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle-North South Networking via Direct Provider Networks]

[Vega Cai]

Also, you can upload a new image with OpenStack client, when horizon
service is not running:

https://docs.openstack.org/python-openstackclient/latest/cli/command-objects/image.html#image-create

Since Nova service is running on RegionOne and RegionTwo, the image should
be also uploaded to RegionOne and RegionTwo, by specifying --os-region-name
for the command.

BR
Zhiyuan

On Sat, 19 Aug 2017 at 21:56 joehuang  wrote:

> Hello, Meher,
>
> By default, only one nic will come up for the
> instance from cirros image.
>
> You can log into the instance, follow this mail thread to bring up
> the second nic.
>
> http://lists.openstack.org/pipermail/openstack-dev/2014-October/048574.html
>
> Best Regards
> Chaoyi Huang(joehuang)
> *发件人：*meher.h...@orange.com
> *收件人：*openstack-dev
> *时间：*2017-08-18 23:30:01
> *主题:*[openstack-dev] [tricircle-North South Networking via Direct
> Provider Networks]
>
> Hello everyone,
>
>
>
> Still in the test phase of the scenarios proposed by the Tricircle
> documentation, I try to do "North South Networking via Direct Provider
> Networks" but I failed to start an instance with 2 NICs, apparently the
> Cirros image does not support this option by default.
>
>
>
> So I will add a new image and so I need the horizon service which is
> disabled when installing Tricircle. Thanks in advance for giving me an idea
> on how to add the dashboard without re-deploying!
>
>
>
> Best regards,
>
>
>
> Meher
>
>
>
> [image: Logo Orange] 
>
>
>
> *Meher Hihi *
> Intern
> ORANGE/IMT/OLN/WTC/CMA/MAX
>
> Fixe : +33 2 96 07 03 71
> 
> Mobile : +33 7 58 38 68 87
> 
> meher.h...@orange.com
>
>
>
>
>
> _
>
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
> ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou 
> falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged 
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete 
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been 
> modified, changed or falsified.
> Thank you.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-- 
BR
Zhiyuan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle-North South Networking via Direct Provider Networks]

[joehuang]

Hello, Meher,

By default, only one nic will come up for the
instance from cirros image.

You can log into the instance, follow this mail thread to bring up
the second nic.

http://lists.openstack.org/pipermail/openstack-dev/2014-October/048574.html

Best Regards
Chaoyi Huang(joehuang)
发件人：meher.h...@orange.com
收件人：openstack-dev
时间：2017-08-18 23:30:01
主题:[openstack-dev] [tricircle-North South Networking via Direct Provider 
Networks]

Hello everyone,

Still in the test phase of the scenarios proposed by the Tricircle 
documentation, I try to do "North South Networking via Direct Provider 
Networks" but I failed to start an instance with 2 NICs, apparently the Cirros 
image does not support this option by default.

So I will add a new image and so I need the horizon service which is disabled 
when installing Tricircle. Thanks in advance for giving me an idea on how to 
add the dashboard without re-deploying!

Best regards,

Meher

[Logo Orange]

Meher Hihi
Intern
ORANGE/IMT/OLN/WTC/CMA/MAX
Fixe : +33 2 96 07 03 
71
Mobile : +33 7 58 38 68 
87
meher.h...@orange.com



_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle-Service Function Chaining]

[meher.hihi]

Hi Zhiyuan,

Thank you very much, I'll join the next meeting! 

Meher




Message: 3
Date: Thu, 17 Aug 2017 12:26:06 +
From: Vega Cai <luckyveg...@gmail.com>
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [tricircle-Service Function Chaining]
Message-ID:

Re: [openstack-dev] [tricircle-Service Function Chaining]

[Vega Cai]

Hi Meher,

The document structure of networking-sfc has been changed so the link in
the guide is not accurate. Since you have already deployed Tricircle and
would like to enable service function chaining feature, I think you can
refer to these guides[1, 2] to setup local Neutron server. The
configuration for local Neutron server is /etc/neutron/neutron.conf
and /etc/neutron/plugins/ml2/ml2_conf.ini for the DevStack setup. And
/etc/neutron/neutron.conf.0 is the configuration file for central Neutron
server.

BTW, would you like to join our weekly meeting? The current time(9:00 am
UTC+8 on Wednesday) may not be suitable for you, but we can figure out a
proper time and rearrange the meeting.

[1] https://docs.openstack.org/networking-sfc/latest/install/install.html
[2]
https://docs.openstack.org/networking-sfc/latest/install/configuration.html

BR
Zhiyuan

On Thu, 17 Aug 2017 at 18:10  wrote:

> Hello to all the community of Tricircle,
>
>
>
> I deployed Tricircle according to the architecture proposed by "Multi-pod
> Installation with DevStack". Now I'm trying to apply the "Networking Guide"
> tutorial and more specifically "Service Function Chaining Guide". Indeed, I
> find that the configuration is somewhat ambiguous with regard to the
> configuration of local neutron.
>
>
>
> I thank you in advance for helping me on this by a more detailed
> explanation. Have a great day!
>
>
>
> Best regards,
>
>
>
> Meher
>
>
>
> [image: Logo Orange] 
>
>
>
> *Meher Hihi *
> Intern
> ORANGE/IMT/OLN/WTC/CMA/MAX
>
> Fixe : +33 2 96 07 03 71
> 
> Mobile : +33 7 58 38 68 87
> 
> meher.h...@orange.com
>
>
>
>
>
> _
>
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
> ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou 
> falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged 
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete 
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been 
> modified, changed or falsified.
> Thank you.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-- 
BR
Zhiyuan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]

[meher.hihi]

Hello,

The problem was related to the proxy, I added the ip address of keystone to the 
variable no_proxy, so that Tricircle is now successfully installed in the two 
nodes.

Regards,

Meher

[Logo Orange]

Meher Hihi
Intern
ORANGE/IMT/OLN/WTC/CMA/MAX
Fixe : +33 2 96 07 03 
71
Mobile : +33 7 58 38 68 
87
meher.h...@orange.com


De : HIHI Meher IMT/OLN
Envoyé : lundi 31 juillet 2017 15:32
À : 'openstack-dev@lists.openstack.org'
Objet : [openstack-dev] [tricircle]

Hello everybody,

I just installed Tricirle on a single node. Now I'm trying to install it on two 
nodes (two VMs), everything was fine with the first node, Tricirle is well 
installed, on the second node, at the end of the script install it stops on An 
error "Failed to discover available versions when contacting 
http://192.168.123.129/identity. Attempting to parse version from URL."

So it seems that there is a connection problem with the keystone service on the 
first machine, as far as the connectivity between the 2 nodes is concerned, it 
is perfect.

I am sending you this mail to find out if anyone can help me on this. I thank 
you in advance!

Regards,

Meher

[Logo Orange]

Meher Hihi
Intern
ORANGE/IMT/OLN/WTC/CMA/MAX
Fixe : +33 2 96 07 03 
71
Mobile : +33 7 58 38 68 
87
meher.h...@orange.com



_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]

[joehuang]

Hello, Meher,

For the second node, the devstack configuration file local.conf should be 
configured carefully, especially for the keystone part(sample file 
https://github.com/openstack/tricircle/blob/master/devstack/local.conf.node_2.sample):

HOST_IP=10.250.201.25
REGION_NAME=RegionTwo
KEYSTONE_REGION_NAME=RegionOne
SERVICE_HOST=$HOST_IP
KEYSTONE_SERVICE_HOST=10.250.201.24
KEYSTONE_AUTH_HOST=10.250.201.24

HOST_IP is the second node's IP, KEYSTONE_SERVICE_HOST/KEYSTONE_AUTH_HOST 
should be configured with the first node's IP.

Best Regards
Chaoyi Huang (joehuang)

From: meher.h...@orange.com [meher.h...@orange.com]
Sent: 31 July 2017 21:31
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [tricircle]

Hello everybody,

I just installed Tricirle on a single node. Now I'm trying to install it on two 
nodes (two VMs), everything was fine with the first node, Tricirle is well 
installed, on the second node, at the end of the script install it stops on An 
error "Failed to discover available versions when contacting 
http://192.168.123.129/identity. Attempting to parse version from URL.”

So it seems that there is a connection problem with the keystone service on the 
first machine, as far as the connectivity between the 2 nodes is concerned, it 
is perfect.

I am sending you this mail to find out if anyone can help me on this. I thank 
you in advance!

Regards,

Meher

[Logo Orange]

Meher Hihi
Intern
ORANGE/IMT/OLN/WTC/CMA/MAX
Fixe : +33 2 96 07 03 
71
Mobile : +33 7 58 38 68 
87
meher.h...@orange.com



_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]

[Morales, Victor]

Hi Meher,

Can you include the paste for this? Can you also verify that your 
global-requirements file contains the tricircleclient module[1]?.  It seems 
like the pip_install_gr function [2][3] is not resolving [4] the 
tricircleclient module[5]

Regards,
Victor Morales

[1] 
https://github.com/openstack/requirements/blob/master/global-requirements.txt#L233
[2] https://github.com/openstack/tricircle/blob/master/devstack/plugin.sh#L323
[3] https://github.com/openstack-dev/devstack/blob/master/inc/python#L59-L70
[4] https://github.com/openstack-dev/devstack/blob/master/inc/python#L362-L372
[5] https://pypi.python.org/pypi/tricircleclient


From: "meher.h...@orange.com" 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Monday, July 24, 2017 at 8:57 AM
To: "openstack-dev@lists.openstack.org" 
Subject: [openstack-dev] [tricircle]

Hello to the community of Openstack-Tricircle,

I hope you are all well! I postulated the problem that I encountered during the 
trial of "Single pod installation with DevStack", I managed to deploy the 
solution by trying the install on Ubuntu and not on RHEL.

Now I try "Multi-pod Installation with DevStack". On the first node, the script 
stops with an error of this form: "[ERROR] / opt / stack / devstack / inc / 
python: 256 Can not find package tricircleclient in requirements". I wanted to 
know if you have any idea how to fix this error.

I thank you in advance!

Meher

[ogo Orange]

Meher Hihi
Intern
ORANGE/IMT/OLN/WTC/CMA/MAX
Fixe : +33 2 96 07 03 
71
Mobile : +33 7 58 38 68 
87
meher.h...@orange.com



_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]PTL non-candidacy

[Fred Li]

Hi Joe,

Thanks a lot for your work for Tricircle, and glad to continue work with
you in this project.
Hope Tricircle will serve more and more customers.

Fred

On Friday, July 21, 2017, joehuang  wrote:

> Hello, all,
>
> Next cycle PTL nomination is approaching, as I announced in the last
> weekly meeting, I am not planning to run for Queen PTL position. It's
> exciting and joyful journey to work in the Tricircle project, not only for
> the interesting features, but also for the excellent team:
>
> 1) Basic tenant L2/L3 networking among OpenStack regions can work now, and
> it's quite useful to help applications achieve cloud level high
> availability: https://www.youtube.com/watch?v=tbcc7-eZnkY
> 2) Tricircle+Neutron can also work with Nova cells V2 to scale single
> OpenStack, it's something more than what we have planned.
>
> I would like to thank everyone who has contributed/is contributing in
> Tricricle, and I'm sure community can continue making it even better.
>
> Nomination period will start soon, whoever the next PTL might be, I'll
> continue serving as core reviewer to help the project.
>
> Thank you very much and best wishes.
>
> Best Regards
> Chaoyi Huang (joehuang)
>


-- 
Regards
Fred Li (李永乐)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]

[Vega Cai]

Hi Meher,

According to the DevStack script, for RHEL, the Apache configuration files
are placed in /etc/httpd/conf.d

BR
Zhiyuan

On Mon, 10 Jul 2017 at 22:14  wrote:

> Hello everybody,
>
>
>
> I posted before a problem related to installing the tricircle on a single
> node, the script stopped with a keystone startup. You advised me to see the
> / etc / apache2 / sites-enabled folder to see if the keystone config files
> are included. But, I have not found this folder, yet the httpd service is
> properly installed, the name of this file changes according to the
> distribution? I use RHEL 7, thank you in advance!
>
>
>
> Meher
>
>
>
> [image: Logo Orange] 
>
>
>
> *Meher Hihi *
> Intern
> ORANGE/IMT/OLN/WTC/CMA/MAX
>
> Fixe : +33 2 96 07 03 71
> 
> Mobile : +33 7 58 38 68 87
> 
> meher.h...@orange.com
>
>
>
>
>
> *De :* HIHI Meher IMT/OLN
> *Envoyé :* mercredi 28 juin 2017 15:12
> *À :* 'openstack-dev@lists.openstack.org'
> *Objet :* [openstack-dev][tricircle]
>
>
>
> Hello everyone,
>
>
>
> I introduce myself; Meher Hihi; I am doing my internship at Orange Labs
> Networks Lannion-France for the diploma of computer network and
> telecommunications engineer.
>
>
>
> I am working on innovative distribution solutions for the virtualization
> infrastructure of the network functions and more specifically on the
> Openstack Tricircle solution, which is why I join your community to
> participate in your discussions and learn from your advice.
>
>
>
> Indeed, I try to install Tricircle on a single node by following this
> documentation “
> https://docs.openstack.org/developer/tricircle/installation-guide.html#single-pod-installation-with-devstack
> ”.
>
> I managed to install Devstack without any problems, but when I modify the
> local.conf file by adding the Tricircle plugin integration and the HOST_IP,
> the script does not want to work and stops on an error of Start of the
> Keystone service.
>
>
>
> I wanted to know if the problem is with my config file that is attached or
> I lack other things to configure. You will also find in the file the IP
> address of the machine.
>
>
>
> I thank you in advance for the help you will bring me. Sincerely,
>
>
>
> Best regards,
>
>
>
> Meher
>
>
>
> [image: Logo Orange] 
>
>
>
> *Meher Hihi *
> Intern
> ORANGE/IMT/OLN/WNI/ODIS/NAVI
>
> Fixe : +33 2 96 07 03 71
> 
> Mobile : +33 7 58 38 68 87
> 
> meher.h...@orange.com
>
>
>
>
>
> _
>
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
> ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou 
> falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged 
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete 
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been 
> modified, changed or falsified.
> Thank you.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-- 
BR
Zhiyuan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]

[meher.hihi]

Hello everybody,

I posted before a problem related to installing the tricircle on a single node, 
the script stopped with a keystone startup. You advised me to see the / etc / 
apache2 / sites-enabled folder to see if the keystone config files are 
included. But, I have not found this folder, yet the httpd service is properly 
installed, the name of this file changes according to the distribution? I use 
RHEL 7, thank you in advance!

Meher

[Logo Orange]

Meher Hihi
Intern
ORANGE/IMT/OLN/WTC/CMA/MAX
Fixe : +33 2 96 07 03 
71
Mobile : +33 7 58 38 68 
87
meher.h...@orange.com


De : HIHI Meher IMT/OLN
Envoyé : mercredi 28 juin 2017 15:12
À : 'openstack-dev@lists.openstack.org'
Objet : [openstack-dev][tricircle]

Hello everyone,

I introduce myself; Meher Hihi; I am doing my internship at Orange Labs 
Networks Lannion-France for the diploma of computer network and 
telecommunications engineer.

I am working on innovative distribution solutions for the virtualization 
infrastructure of the network functions and more specifically on the Openstack 
Tricircle solution, which is why I join your community to participate in your 
discussions and learn from your advice.

Indeed, I try to install Tricircle on a single node by following this 
documentation 
"https://docs.openstack.org/developer/tricircle/installation-guide.html#single-pod-installation-with-devstack;.
I managed to install Devstack without any problems, but when I modify the 
local.conf file by adding the Tricircle plugin integration and the HOST_IP, the 
script does not want to work and stops on an error of Start of the Keystone 
service.

I wanted to know if the problem is with my config file that is attached or I 
lack other things to configure. You will also find in the file the IP address 
of the machine.

I thank you in advance for the help you will bring me. Sincerely,

Best regards,

Meher

[Logo Orange]

Meher Hihi
Intern
ORANGE/IMT/OLN/WNI/ODIS/NAVI
Fixe : +33 2 96 07 03 
71
Mobile : +33 7 58 38 68 
87
meher.h...@orange.com



_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]

[joehuang]

Hello, Meher

Except checking the sites-enabled in Apache, because single-node installation 
is mainly for very limited feature development, multi-node installation is 
recommended: 
https://docs.openstack.org/developer/tricircle/installation-guide.html#multi-pod-installation-with-devstack

If you only have one node, you don't need to install the second node even if 
you follow the multi-node guide.

You can also talk to us directly through IRC channel #openstack-tricircle in 
freenode.

Best Regards
Chaoyi Huang (joehuang)

From: Vega Cai [luckyveg...@gmail.com]
Sent: 29 June 2017 10:28
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle]

Hi Meher,

Welcome to join Tricircle!

Both Keystone and Tricircle services are running under Apache, so if Keystone 
failed to start after enabling Tricircle, I guess there might be some problems 
of Apache configuration. You can check what services are enabled in Apache by 
listing this folder: /etc/apache2/sites-enabled.

tricircle@zhiyuan-1:~/devstack$ ls /etc/apache2/sites-enabled/
keystone-wsgi-admin.conf  keystone-wsgi-public.conf  nova-placement-api.conf  
tricircle-api.conf

Above is the result from my Ubuntu machine.

Also, could you provide me the log of DevStack after enabling Tricircle so I 
can get more hints.

BR
Zhiyuan

On Wed, 28 Jun 2017 at 21:17 
<meher.h...@orange.com<mailto:meher.h...@orange.com>> wrote:
Hello everyone,

I introduce myself; Meher Hihi; I am doing my internship at Orange Labs 
Networks Lannion-France for the diploma of computer network and 
telecommunications engineer.

I am working on innovative distribution solutions for the virtualization 
infrastructure of the network functions and more specifically on the Openstack 
Tricircle solution, which is why I join your community to participate in your 
discussions and learn from your advice.

Indeed, I try to install Tricircle on a single node by following this 
documentation 
“https://docs.openstack.org/developer/tricircle/installation-guide.html#single-pod-installation-with-devstack”.
I managed to install Devstack without any problems, but when I modify the 
local.conf file by adding the Tricircle plugin integration and the HOST_IP, the 
script does not want to work and stops on an error of Start of the Keystone 
service.

I wanted to know if the problem is with my config file that is attached or I 
lack other things to configure. You will also find in the file the IP address 
of the machine.

I thank you in advance for the help you will bring me. Sincerely,

Best regards,

Meher

<http://www.orange.com/>

Meher Hihi
Intern
ORANGE/IMT/OLN/WNI/ODIS/NAVI
Fixe : +33 2 96 07 03 
71<https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33296070371>
Mobile : +33 7 58 38 68 
87<https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33758386887>
meher.h...@orange.com<mailto:meher.h...@orange.com>



_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
BR
Zhiyuan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]

[Vega Cai]

Hi Meher,

Welcome to join Tricircle!

Both Keystone and Tricircle services are running under Apache, so if
Keystone failed to start after enabling Tricircle, I guess there might be
some problems of Apache configuration. You can check what services are
enabled in Apache by listing this folder: /etc/apache2/sites-enabled.

tricircle@zhiyuan-1:~/devstack$ ls /etc/apache2/sites-enabled/
keystone-wsgi-admin.conf  keystone-wsgi-public.conf
 nova-placement-api.conf  tricircle-api.conf

Above is the result from my Ubuntu machine.

Also, could you provide me the log of DevStack after enabling Tricircle so
I can get more hints.

BR
Zhiyuan

On Wed, 28 Jun 2017 at 21:17  wrote:

> Hello everyone,
>
>
>
> I introduce myself; Meher Hihi; I am doing my internship at Orange Labs
> Networks Lannion-France for the diploma of computer network and
> telecommunications engineer.
>
>
>
> I am working on innovative distribution solutions for the virtualization
> infrastructure of the network functions and more specifically on the
> Openstack Tricircle solution, which is why I join your community to
> participate in your discussions and learn from your advice.
>
>
>
> Indeed, I try to install Tricircle on a single node by following this
> documentation “
> https://docs.openstack.org/developer/tricircle/installation-guide.html#single-pod-installation-with-devstack
> ”.
>
> I managed to install Devstack without any problems, but when I modify the
> local.conf file by adding the Tricircle plugin integration and the HOST_IP,
> the script does not want to work and stops on an error of Start of the
> Keystone service.
>
>
>
> I wanted to know if the problem is with my config file that is attached or
> I lack other things to configure. You will also find in the file the IP
> address of the machine.
>
>
>
> I thank you in advance for the help you will bring me. Sincerely,
>
>
>
> Best regards,
>
>
>
> Meher
>
>
>
> [image: Logo Orange] 
>
>
>
> *Meher Hihi *
> Intern
> ORANGE/IMT/OLN/WNI/ODIS/NAVI
>
> Fixe : +33 2 96 07 03 71
> 
> Mobile : +33 7 58 38 68 87
> 
> meher.h...@orange.com
>
>
>
>
>
> _
>
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
> ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou 
> falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged 
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete 
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been 
> modified, changed or falsified.
> Thank you.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-- 
BR
Zhiyuan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] Tricircle vs Trio2o

[joehuang]

Hello, Silvia,

Thank you for your interest in Tricircle and Trio2o.

See inline comments.

Best Regards
Chaoyi Huang (joehuang)

From: Silvia Fichera [fichera@gmail.com]
Sent: 28 June 2017 5:16
To: OpenStack Development Mailing List (not for usage questions); 
openst...@lists.openstack.org
Subject: [openstack-dev] [tricircle] Tricircle vs Trio2o


Hi all,
I would like to build up a multi-region openstack and I read that both 
tricircle and trio2o are the most suitable solutions.
I have few questions:

- from the wikis I couldn't deeply understand the differences between the two: 
ad far as I understood tricircle deploys a shared neutron module, trio2o 
provides a gateway in the case of a single nova/glance module.Is it right?

[joehuang] Yes, Tricircle is to provide networking capability across multiple 
neutron servers in OpenStack mult-region deployment or Nova cells V2 multi-cell 
deployment, one shared Neutron module providing such cross Neutron server 
functionalities and provide the API entrance.  For trio2o, it's major purpose 
is to gateway, and it's not active after it's moved outside from Tricircle, 
during the Tricricle bightent application, some TCs were worried about the API 
consistency if one gateway layer is there, so it's not accepted into OpenStack. 
Though I know many cloud operators expressed the need for single API entry 
point for multiple OpenStack instances. [/joehuang]

- Could you better explain the architecture? For instance: where is the 
Controller? Are the compute nodes the same of the one site implementation?

[joehuang] for the architecture and work flow, you can refer to the slides and 
video we presented in OPNFV Beijing summit: video 
https://www.youtube.com/watch?v=tbcc7-eZnkY  , slides 
https://docs.google.com/presentation/d/1WBdra-ZaiB-K8_m3Pv76o_jhylEqJXTTxzEZ-cu8u2A/
 , 
https://www.slideshare.net/JoeHuang7/shared-networks-to-support-vnf-high-availability-across-openstack-multiregion-deployment-77283728
I don't know what do you mean for Controller, Tricircle only provides plugins 
to Neutron: Neutron server with different plugin plays different role, for 
central Neutron with Tricicle central plugin, it'll play as the networking 
coordination for multiple local Neutrons which will be installed with Tricircle 
local plugin. Each local Neutron work as usual with ML2 plugin/OVS backend or 
SDN controller backend, just install one slim hook layer of Tricircle local 
Neutron plugin. You can experience it through the guide: 
https://docs.openstack.org/developer/tricircle/installation-guide.html#multi-pod-installation-with-devstack
  [/joehuang]

- Is it possible to connect distributed compute nodes with an SDN network, in 
order to use it as data plane?
[joehuang] Yes, it's possible with an SDN network, currently we use in-tree OVS 
implemetation to connect distributed compute nodes, Tricricle is able to carry 
shadow port/shadow agent information to other Neutron servers, so SDN 
controller can use these information to build cross Neutron network. If SDN 
controller can communicate with each other by themselves, and establish cross 
Neutron network, it's also fine, Tricircle support this mode. During OPNFV 
summit, Vikram and I had one idea to see if OVN can work together with 
Tricircle.  Could you describe your idea for the SDN network in more detail, 
then I can check whether my understanding is correct, and provide my valuable 
comment.  [/joehuang]

- If not, what kind of network is in the middle? I suppose that a network is 
necessary to connect the different pod.

[joehuang]  Please refer to the last comment  [/joehuang]

Could you please clarify these points?
Thanks a lot

--
Silvia Fichera
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]poll for new weekly meeting time slot

[joehuang]

Hello,

According to the poll, most of contributors prefer the option "Wed  UTC 01:00, 
Beijing 9:00 AM, PDT(-1 day) 6:00 PM". I'll submit a patch to update the weekly 
meeting time slot.

Best Regards
Chaoyi Huang (joehuang)

From: joehuang
Sent: 24 April 2017 16:12
To: openstack-dev
Subject: [openstack-dev][tricircle]poll for new weekly meeting time slot

Hello,

We's like to reschedule our weekly time according to our discussion, there are 
four options after some offline communication:

Wed  UTC 01:00, Beijing 9:00 AM, PDT(-1 day) 6:00 PM
Wed  UTC 13:00, Beijing 9:00 PM, PDT 6:00 AM
Thu  UTC 01:00, Beijing 9:00 AM, PDT(-1 day) 6:00 PM
Fri  UTC 01:00, Beijing 9:00 AM, PDT(-1 day) 6:00 PM


Please vote in the doodle poll: http://doodle.com/poll/ypd2xpqppzaqek5u thanks 
a lot.

Best Regards
Chaoyi Huang (joehuang)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] mascot for the Tricircle

[joehuang]

Hello, team,

Great, if no other comment, then the following cute Panda is Tricircle's mascot.

Thank you all!

[X]

Best Regards
Chaoyi Huang (joehuang)

From: Yipei Niu [newy...@gmail.com]
Sent: 25 April 2017 9:25
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle] mascot for the Tricircle

+1.

Best regards,
Yipei

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]poll for new weekly meeting time

[Yipei Niu]

Wed  UTC 01:00, Beijing 9:00 AM, PDT(-1 day) 6:00 PM +1.

Best regards,
Yipei
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] mascot for the Tricircle

[Yipei Niu]

+1.

Best regards,
Yipei
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]mascot for the Tricircle project

[Morales, Victor]

+1

From: Zhipeng Huang <zhipengh...@gmail.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Date: Monday, April 24, 2017 at 3:06 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [tricircle]mascot for the Tricircle project

perfect XD

On Mon, Apr 24, 2017 at 2:59 PM, joehuang 
<joehu...@huawei.com<mailto:joehu...@huawei.com>> wrote:
Hello, team,

What about the mascot of Tricircle project?

Your comments are welcome.

Best Regards
Chaoyi Huang(joehuang)


From: Heidi Joy Tretheway 
[heidi...@openstack.org<mailto:heidi...@openstack.org>]
Sent: 22 April 2017 6:15
To: joehuang
Subject: Re: Question about the Tricircle mascot
Hi Joe,
Following up on your team’s mascot request, our illustrators came back with a 
beautiful piece. Would you please let me know what your team thinks?

[cid:image001.png@01D2BCCF.02FAD1D0]






__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com<mailto:huangzhip...@huawei.com>
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu<mailto:zhipe...@uci.edu>
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]mascot for the Tricircle project

[Vega Cai]

So cute XD

Zhiyuan

On Mon, 24 Apr 2017 at 16:11 Zhipeng Huang  wrote:

> perfect XD
>
> On Mon, Apr 24, 2017 at 2:59 PM, joehuang  wrote:
>
>> Hello, team,
>>
>> What about the mascot of Tricircle project?
>>
>> Your comments are welcome.
>>
>> Best Regards
>> Chaoyi Huang(joehuang)
>>
>>
>> *From:* Heidi Joy Tretheway [heidi...@openstack.org]
>> *Sent:* 22 April 2017 6:15
>> *To:* joehuang
>> *Subject:* Re: Question about the Tricircle mascot
>>
>> Hi Joe,
>> Following up on your team’s mascot request, our illustrators came back
>> with a beautiful piece. Would you please let me know what your team thinks?
>>
>>
>>
>>
>>
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Zhipeng (Howard) Huang
>
> Standard Engineer
> IT Standard & Patent/IT Product Line
> Huawei Technologies Co,. Ltd
> Email: huangzhip...@huawei.com
> Office: Huawei Industrial Base, Longgang, Shenzhen
>
> (Previous)
> Research Assistant
> Mobile Ad-Hoc Network Lab, Calit2
> University of California, Irvine
> Email: zhipe...@uci.edu
> Office: Calit2 Building Room 2402
>
> OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-- 
BR
Zhiyuan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]mascot for the Tricircle project

[Zhipeng Huang]

perfect XD

On Mon, Apr 24, 2017 at 2:59 PM, joehuang  wrote:

> Hello, team,
>
> What about the mascot of Tricircle project?
>
> Your comments are welcome.
>
> Best Regards
> Chaoyi Huang(joehuang)
>
>
> *From:* Heidi Joy Tretheway [heidi...@openstack.org]
> *Sent:* 22 April 2017 6:15
> *To:* joehuang
> *Subject:* Re: Question about the Tricircle mascot
>
> Hi Joe,
> Following up on your team’s mascot request, our illustrators came back
> with a beautiful piece. Would you please let me know what your team thinks?
>
>
>
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]reschedule the weekly meeting

[joehuang]

Hello,

The patch was merged, the weekly meeting
will be held on UTC 1400 ~ UTC 1500 every
Wednesday from this week.

Best Regards
Chaoyi Huang(joehuang)
发件人：黄朝意
收件人：openstack-dev,Morales, 
Victor,sindhu.dev...@intel.com,prince.a.owusu.boat...@intel.com
时间：2017-03-06 10:07:14
主题:RE: [openstack-dev][tricircle]reschedule the weekly meeting

Hello,

According to the poll[1], the weekly meeting will be rescheduled to UTC 1400 ~ 
UTC 1500 every Wednesday, once the patch[2] was merged, we can start the weekly 
meeting at new time slot.

[1]poll of weekly meeting time: http://doodle.com/poll/hz436r6wm99h4eka#table
[2]new weekly meeting time patch: https://review.openstack.org/#/c/441727/

Best Regards
Chaoyi Huang (joehuang)

From: joehuang
Sent: 01 March 2017 11:59
To: openstack-dev; victor.mora...@intel.com; sindhu.dev...@intel.com; 
prince.a.owusu.boat...@intel.com
Subject: RE: [openstack-dev][tricircle]reschedule the weekly meeting

Hello, team,

According to the discussion in the IRC, we'd like to move the weekly meeting 
from UTC1300 to UTC1400, there are several options for this time slot, please 
vote before next Monday, then I'll submit a patch to occupy the new time slot 
and release the old time slot.

Poll link: http://doodle.com/poll/hz436r6wm99h4eka

Note: before the new weekly meeting time is settled, we have to have weekly 
meeting at old time slot.

Best Regards
Chaoyi Huang (joehuang)

From: joehuang
Sent: 27 February 2017 21:48
To: openstack-dev; victor.mora...@intel.com; sindhu.dev...@intel.com; 
prince.a.owusu.boat...@intel.com
Subject: [openstack-dev][tricircle]reschedule the weekly meeting

Hello,

Currently the Tricircle weekly meeting is held regularly at UTC 13:00~14:00 
every Wednesday, it's not convenient for contributors from USA.

The available time slots could be found at
https://docs.google.com/spreadsheets/d/1lQHKCQa4wQmnWpTMB3DLltY81kIChZumHLHzoMNF07c/edit#gid=0

Other contributors are mostly from East Asia, the time zone is around 
UTC+8/UTC+9.

Please propose some your preferred time slots, and then let's have a poll for 
the new weekly meeting time.

Best Regards
Chaoyi Huang (joehuang)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]reschedule the weekly meeting

[joehuang]

Hello,

According to the poll[1], the weekly meeting will be rescheduled to UTC 1400 ~ 
UTC 1500 every Wednesday, once the patch[2] was merged, we can start the weekly 
meeting at new time slot.

[1]poll of weekly meeting time: http://doodle.com/poll/hz436r6wm99h4eka#table
[2]new weekly meeting time patch: https://review.openstack.org/#/c/441727/

Best Regards
Chaoyi Huang (joehuang)

From: joehuang
Sent: 01 March 2017 11:59
To: openstack-dev; victor.mora...@intel.com; sindhu.dev...@intel.com; 
prince.a.owusu.boat...@intel.com
Subject: RE: [openstack-dev][tricircle]reschedule the weekly meeting

Hello, team,

According to the discussion in the IRC, we'd like to move the weekly meeting 
from UTC1300 to UTC1400, there are several options for this time slot, please 
vote before next Monday, then I'll submit a patch to occupy the new time slot 
and release the old time slot.

Poll link: http://doodle.com/poll/hz436r6wm99h4eka

Note: before the new weekly meeting time is settled, we have to have weekly 
meeting at old time slot.

Best Regards
Chaoyi Huang (joehuang)

From: joehuang
Sent: 27 February 2017 21:48
To: openstack-dev; victor.mora...@intel.com; sindhu.dev...@intel.com; 
prince.a.owusu.boat...@intel.com
Subject: [openstack-dev][tricircle]reschedule the weekly meeting

Hello,

Currently the Tricircle weekly meeting is held regularly at UTC 13:00~14:00 
every Wednesday, it's not convenient for contributors from USA.

The available time slots could be found at
https://docs.google.com/spreadsheets/d/1lQHKCQa4wQmnWpTMB3DLltY81kIChZumHLHzoMNF07c/edit#gid=0

Other contributors are mostly from East Asia, the time zone is around 
UTC+8/UTC+9.

Please propose some your preferred time slots, and then let's have a poll for 
the new weekly meeting time.

Best Regards
Chaoyi Huang (joehuang)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]Nominating Victor Morales as Tricircle Core

[hejiawei]

+1 for my vote


Best wish
Hejiawei





At 2017-03-01 10:38:00, "joehuang"  wrote:

Hi Team,

Victor Morales has made many review contributions[1] to Trircircle since the 
Ocata cycle, and he also created the python-tricircleclient sub-project[2]. I 
would like to nominate him to be Tricircle core reviewer. I really think his 
experience will help us substantially improve Trircircle.


 It's now time to vote :)

[1] http://stackalytics.com/report/contribution/tricircle/120
[2] https://git.openstack.org/cgit/openstack/python-tricircleclient/




Best Regards
Chaoyi Huang (joehuang)__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]Nominating Victor Morales as Tricircle Core

[Morales, Victor]

Thanks everyone for voting, I started recently and I’m sure that I’ve many 
things to learn but something that I discover since the beginning was the 
enthusiasm and welcoming aptitudes of this community.  I’m going to do my best 
for keeping high standards of the code

Thanks
Victor Morales
irc: electrocucaracha

From: joehuang <joehu...@huawei.com<mailto:joehu...@huawei.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, March 2, 2017 at 1:25 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [tricircle]Nominating Victor Morales as Tricircle 
Core

Thank you all for your voting.

Victor, you are now included in the core team.

Best Regards
Chaoyi Huang (joehuang)



From: Yipei Niu [newy...@gmail.com<mailto:newy...@gmail.com>]
Sent: 01 March 2017 15:06
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle]Nominating Victor Morales as Tricircle 
Core

+1.


From: joehuang
Sent: 01 March 2017 11:44
To: OpenStack Development Mailing List (not for usage questions)
Subject: RE: [openstack-dev] [tricircle]Nominating Victor Morales as Tricircle 
Core

+1 from my vote.

Best Regards
Chaoyi Huang (joehuang)

From: Vega Cai [luckyveg...@gmail.com<mailto:luckyveg...@gmail.com>]
Sent: 01 March 2017 11:42
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle]Nominating Victor Morales as Tricircle 
Core

+1

Zhiyuan

On Wed, 1 Mar 2017 at 11:41 Devale, Sindhu 
<sindhu.dev...@intel.com<mailto:sindhu.dev...@intel.com>> wrote:
+1

Sindhu

From: joehuang <joehu...@huawei.com<mailto:joehu...@huawei.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date: Tuesday, February 28, 2017 at 8:38 PM
To: openstack-dev 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: [openstack-dev] [tricircle]Nominating Victor Morales as Tricircle Core

Hi Team,

Victor Morales has made many review contributions[1] to Trircircle since the 
Ocata cycle, and he also created the python-tricircleclient sub-project[2]. I 
would like to nominate him to be Tricircle core reviewer. I really think his 
experience will help us substantially improve Trircircle.

 It's now time to vote :)

[1] http://stackalytics.com/report/contribution/tricircle/120
[2] https://git.openstack.org/cgit/openstack/python-tricircleclient/


Best Regards
Chaoyi Huang (joehuang)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
BR
Zhiyuan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]Nominating Victor Morales as Tricircle Core

[cr_...@126.com]

+1

Thanks for his great contribution.

Best Regards
Ronghui Cao__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]Nominating Victor Morales as Tricircle Core

[joehuang]

Thank you all for your voting.

Victor, you are now included in the core team.

Best Regards
Chaoyi Huang (joehuang)



From: Yipei Niu [newy...@gmail.com]
Sent: 01 March 2017 15:06
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle]Nominating Victor Morales as Tricircle 
Core

+1.


From: joehuang
Sent: 01 March 2017 11:44
To: OpenStack Development Mailing List (not for usage questions)
Subject: RE: [openstack-dev] [tricircle]Nominating Victor Morales as Tricircle 
Core

+1 from my vote.

Best Regards
Chaoyi Huang (joehuang)

From: Vega Cai [luckyveg...@gmail.com]
Sent: 01 March 2017 11:42
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle]Nominating Victor Morales as Tricircle 
Core

+1

Zhiyuan

On Wed, 1 Mar 2017 at 11:41 Devale, Sindhu 
<sindhu.dev...@intel.com<mailto:sindhu.dev...@intel.com>> wrote:
+1

Sindhu

From: joehuang <joehu...@huawei.com<mailto:joehu...@huawei.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date: Tuesday, February 28, 2017 at 8:38 PM
To: openstack-dev 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: [openstack-dev] [tricircle]Nominating Victor Morales as Tricircle Core

Hi Team,

Victor Morales has made many review contributions[1] to Trircircle since the 
Ocata cycle, and he also created the python-tricircleclient sub-project[2]. I 
would like to nominate him to be Tricircle core reviewer. I really think his 
experience will help us substantially improve Trircircle.

 It's now time to vote :)

[1] http://stackalytics.com/report/contribution/tricircle/120
[2] https://git.openstack.org/cgit/openstack/python-tricircleclient/


Best Regards
Chaoyi Huang (joehuang)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
BR
Zhiyuan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]Nominating Victor Morales as Tricircle Core

[Yipei Niu]

+1.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]reschedule the weekly meeting

[joehuang]

Hello, team,

According to the discussion in the IRC, we'd like to move the weekly meeting 
from UTC1300 to UTC1400, there are several options for this time slot, please 
vote before next Monday, then I'll submit a patch to occupy the new time slot 
and release the old time slot.

Poll link: http://doodle.com/poll/hz436r6wm99h4eka

Note: before the new weekly meeting time is settled, we have to have weekly 
meeting at old time slot.

Best Regards
Chaoyi Huang (joehuang)

From: joehuang
Sent: 27 February 2017 21:48
To: openstack-dev; victor.mora...@intel.com; sindhu.dev...@intel.com; 
prince.a.owusu.boat...@intel.com
Subject: [openstack-dev][tricircle]reschedule the weekly meeting

Hello,

Currently the Tricircle weekly meeting is held regularly at UTC 13:00~14:00 
every Wednesday, it's not convenient for contributors from USA.

The available time slots could be found at
https://docs.google.com/spreadsheets/d/1lQHKCQa4wQmnWpTMB3DLltY81kIChZumHLHzoMNF07c/edit#gid=0

Other contributors are mostly from East Asia, the time zone is around 
UTC+8/UTC+9.

Please propose some your preferred time slots, and then let's have a poll for 
the new weekly meeting time.

Best Regards
Chaoyi Huang (joehuang)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]Nominating Victor Morales as Tricircle Core

[joehuang]

+1 from my vote.

Best Regards
Chaoyi Huang (joehuang)

From: Vega Cai [luckyveg...@gmail.com]
Sent: 01 March 2017 11:42
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle]Nominating Victor Morales as Tricircle 
Core

+1

Zhiyuan

On Wed, 1 Mar 2017 at 11:41 Devale, Sindhu 
<sindhu.dev...@intel.com<mailto:sindhu.dev...@intel.com>> wrote:
+1

Sindhu

From: joehuang <joehu...@huawei.com<mailto:joehu...@huawei.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date: Tuesday, February 28, 2017 at 8:38 PM
To: openstack-dev 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: [openstack-dev] [tricircle]Nominating Victor Morales as Tricircle Core

Hi Team,

Victor Morales has made many review contributions[1] to Trircircle since the 
Ocata cycle, and he also created the python-tricircleclient sub-project[2]. I 
would like to nominate him to be Tricircle core reviewer. I really think his 
experience will help us substantially improve Trircircle.

 It's now time to vote :)

[1] http://stackalytics.com/report/contribution/tricircle/120
[2] https://git.openstack.org/cgit/openstack/python-tricircleclient/


Best Regards
Chaoyi Huang (joehuang)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
BR
Zhiyuan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]Nominating Victor Morales as Tricircle Core

[Vega Cai]

+1

Zhiyuan

On Wed, 1 Mar 2017 at 11:41 Devale, Sindhu  wrote:

> +1
>
> Sindhu
>
> From: joehuang 
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Date: Tuesday, February 28, 2017 at 8:38 PM
> To: openstack-dev 
> Subject: [openstack-dev] [tricircle]Nominating Victor Morales as
> Tricircle Core
>
> Hi Team,
>
> Victor Morales has made many review contributions[1] to Trircircle since
> the Ocata cycle, and he also created the python-tricircleclient
> sub-project[2]. I would like to nominate him to be Tricircle core
> reviewer. I really think his experience will help us substantially
> improve Trircircle.
>
>  It's now time to vote :)
>
> [1] http://stackalytics.com/report/contribution/tricircle/120
> [2] https://git.openstack.org/cgit/openstack/python-tricircleclient/
>
>
> Best Regards
> Chaoyi Huang (joehuang)
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-- 
BR
Zhiyuan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]Nominating Victor Morales as Tricircle Core

[Dongfeng Huang]

It's wonderful for Victor Morales to be Tricircle core. Thanks for his
great contribution.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]Nominating Victor Morales as Tricircle Core

[Devale, Sindhu]

+1

Sindhu

From: joehuang >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Tuesday, February 28, 2017 at 8:38 PM
To: openstack-dev 
>
Subject: [openstack-dev] [tricircle]Nominating Victor Morales as Tricircle Core

Hi Team,

Victor Morales has made many review contributions[1] to Trircircle since the 
Ocata cycle, and he also created the python-tricircleclient sub-project[2]. I 
would like to nominate him to be Tricircle core reviewer. I really think his 
experience will help us substantially improve Trircircle.

 It's now time to vote :)

[1] http://stackalytics.com/report/contribution/tricircle/120
[2] https://git.openstack.org/cgit/openstack/python-tricircleclient/


Best Regards
Chaoyi Huang (joehuang)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle][all] guide for reading source code

[Vega Cai]

Wow, awesome guide!!

My suggestion will be no matter where we maintain the guide, it will be
better to not just update the original guide directly, to make readers easy
to follow the changes of logic.

BR
Zhiyuan

On Tue, 21 Feb 2017 at 11:00 joehuang  wrote:

> Hello,
>
> For those who are interested in digging into Tricircle source code, it'll
> be good to have a step by step guide. I prepared a wiki page to navigate
> the source code of Tricircle:
>
> https://wiki.openstack.org/wiki/TricircleHowToReadCode
>
> It was linked to the wiki page of Tricircle:
> https://wiki.openstack.org/wiki/Tricircle
>
> And also please feel free to update the wiki to make it being more
> readable and consistent with the code.
>
> Should we include it into the source code repo, and maintain it at the
> same time if we update the code logic?
>
> Best Regards
> Chaoyi Huang (joehuang)
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-- 
BR
Zhiyuan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] python-tricircleclient repo officially created

[joehuang]

Hi, Victor,

Pretty cool! No need to type the boring curl  any more.

Best Regards
Chaoyi Huang (joehuang)

From: Morales, Victor [victor.mora...@intel.com]
Sent: 16 February 2017 0:19
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [tricircle] python-tricircleclient repo officially 
created

Howdy,

I’m happy to announce that after OpenStack Governance has approved[1] and infra 
them processed the request[2],  the python-tricircleclient repository  has been 
created[3].  This client pretends to make things simpler for users who require 
multi region solutions which can be addressed by Tricircle.  Hopefully this 
project helps for the adoption and visibility of this solution.  Lastly,  this 
client is still under developing and requires all your expertise to improve it 
so feel free to add new capabilities and features that you consider necessary.

Regards,
Victor Morales
irc: electrocucaracha

[1] https://review.openstack.org/#/c/426419/
[2] https://review.openstack.org/#/c/426859/
[3] http://git.openstack.org/cgit/openstack/python-tricircleclient/
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] python-tricircleclient repo officially created

[Das, Anindita]

Awesome Victor!! Congratulations. ☺

Anindita

From: "Morales, Victor" 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Wednesday, February 15, 2017 at 10:19 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [openstack-dev] [tricircle] python-tricircleclient repo officially 
created

Howdy,

I’m happy to announce that after OpenStack Governance has approved[1] and infra 
them processed the request[2],  the python-tricircleclient repository  has been 
created[3].  This client pretends to make things simpler for users who require 
multi region solutions which can be addressed by Tricircle.  Hopefully this 
project helps for the adoption and visibility of this solution.  Lastly,  this 
client is still under developing and requires all your expertise to improve it 
so feel free to add new capabilities and features that you consider necessary.

Regards,
Victor Morales
irc: electrocucaracha

[1] https://review.openstack.org/#/c/426419/
[2] https://review.openstack.org/#/c/426859/
[3] http://git.openstack.org/cgit/openstack/python-tricircleclient/
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] python-tricircleclient repo officially created

[Zhipeng Huang]

Thanks Victor ! : )

On Thu, Feb 16, 2017 at 12:19 AM, Morales, Victor 
wrote:

> Howdy,
>
> I’m happy to announce that after OpenStack Governance has approved[1] and
> infra them processed the request[2],  the python-tricircleclient repository
>  has been created[3].  This client pretends to make things simpler for
> users who require multi region solutions which can be addressed by
> Tricircle.  Hopefully this project helps for the adoption and visibility of
> this solution.  Lastly,  this client is still under developing and requires
> all your expertise to improve it so feel free to add new capabilities and
> features that you consider necessary.
>
> Regards,
> Victor Morales
> irc: electrocucaracha
>
> [1] https://review.openstack.org/#/c/426419/
> [2] https://review.openstack.org/#/c/426859/
> [3] http://git.openstack.org/cgit/openstack/python-tricircleclient/
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Prooduct Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] Example EVPN question/use-case

[joehuang]

Hello, Curtis and Greg,

This is a quite good use case. Thanks for the sharing.

Tricircle is working on VxLAN based L2 network across OpenStack clouds for 
different backends (non-SDN, SDN, L2 GW or non L2 GW). The spec is in review: 
https://review.openstack.org/#/c/429155/.

Currently only SDN controllers which can support using BGP to exchange 
tunneling endpoint information is considered. It's worth to take this use case 
into consideration.

Please join the review and give your comments, thanks.

Best Regards
Chaoyi Huang (joehuang)


From: Curtis [serverasc...@gmail.com]
Sent: 08 February 2017 1:49
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [tricircle] Example EVPN question/use-case

Hi,

I'm not sure if this is useful at all, but there is a blog post [1]
from one of the people behind the PacketPushers podcast regarding
connecting two OpenStack clouds with a EVPN. They are wondering how to
do it.

They want to connect an NSX based cloud with a OpenContrail based
cloud and do it at very high speeds. Interesting use case, real world.

Thanks,
Curtis.

[1]: 
http://etherealmind.com/help-wanted-stitching-a-federated-sdn-on-openstack-with-evpn/

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]Pike design topics discussion

[joehuang]

Hello,

(Repost)

As what's discussed during the weekly meeting, let's discuss what's to do in 
Pike in etherpad next Tuesday morning UTC 1:30 am (9:30am Beijing time, 10:30 
Korea/Japan time, Monday 5:30pm PST time)

The etherpad link https://etherpad.openstack.org/p/tricircle-pike-design-topics

Please input your concerns on what to do in Pike into the etherpad, and let's 
discuss that time, the duration is around 1.5 hour.

Best Regards
Chaoyi Huang (joehuang)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]Tricircle Pike PTG

[joehuang]

Hello,

As only few of us may go to Atlanta, the etherpad has been renamed to reflect 
the fact of our "virtually distributed PTG"

https://etherpad.openstack.org/p/tricircle-pike-design-topics

We will discuss this in the weekly meeting, "What date and time and venu during 
the PTG, and meetup for contributors who can't go to Atlanta? It would be great 
to hold it at the same time, like virtually distributed PTG: some in PTG 
Atlanta, some in other place, but are inter-connectted through online etherpad."

Best Regards
Chaoyi Huang (joehuang)

From: joehuang
Sent: 17 January 2017 10:22
To: openstack-dev
Subject: [openstack-dev][tricircle]Tricircle Pike PTG

As the Ocata stable branch will be created and released soon, it's time to 
prepare what we need to discuss and implement in Pike release:

The etherpad has been created at: 
https://etherpad.openstack.org/p/tricircle-ptg-pike

Please feel free to add the topics, ideas into the etherpad, and let's plan the 
agenda as well.

Best Regards
Chaoyi Huang (joehuang)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]agenda of weekly meeting Dec.7

[joehuang]

Hello, Dims,

Thank you very much, interesting to know their work. Would like to get in touch 
with those folks.

Best Regards
Chaoyi Huang (joehuang)


From: Davanum Srinivas [dava...@gmail.com]
Sent: 07 December 2016 19:40
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle]agenda of weekly meeting Dec.7

Chaoyi,

Is there any interest in this work?
http://cs.brown.edu/~rfonseca/pubs/yu16netex.pdf
https://goo.gl/photos/hwHfMNo4xDMfVK8j8

Please let me know and i'll get you in touch with those folks.

Thanks,
Dims


On Wed, Dec 7, 2016 at 3:00 AM, joehuang <joehu...@huawei.com> wrote:
> Hello, team,
>
> Bug-smash and meetup in last week is very good, let's continue the weekly
> meeting.
>
> Agenda of Dec.7 weekly meeting:
>
> Bug smash and meetup summary
> Ocata feature development review
> legacy tables clean after splitting
> Open Discussion
>
>
> How to join:
>
> #  IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on
> every Wednesday starting from UTC 13:00.
>
>
> If you  have other topics to be discussed in the weekly meeting, please
> reply the mail.
>
>
> Best Regards
> Chaoyi Huang (joehuang)
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



--
Davanum Srinivas :: https://twitter.com/dims

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]agenda of weekly meeting Dec.7

[Davanum Srinivas]

Chaoyi,

Is there any interest in this work?
http://cs.brown.edu/~rfonseca/pubs/yu16netex.pdf
https://goo.gl/photos/hwHfMNo4xDMfVK8j8

Please let me know and i'll get you in touch with those folks.

Thanks,
Dims


On Wed, Dec 7, 2016 at 3:00 AM, joehuang  wrote:
> Hello, team,
>
> Bug-smash and meetup in last week is very good, let's continue the weekly
> meeting.
>
> Agenda of Dec.7 weekly meeting:
>
> Bug smash and meetup summary
> Ocata feature development review
> legacy tables clean after splitting
> Open Discussion
>
>
> How to join:
>
> #  IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on
> every Wednesday starting from UTC 13:00.
>
>
> If you  have other topics to be discussed in the weekly meeting, please
> reply the mail.
>
>
> Best Regards
> Chaoyi Huang (joehuang)
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Davanum Srinivas :: https://twitter.com/dims

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]Questions about Tricircle L2 and L3 implementation

[joehuang]

Hello, Dina,

Currently EVPN L2 networking has not started to design and implemented yet. 
Currently only shared VLAN L2 networking was supported, and is discussing VxLAN 
based L2 networking across OpenStack.

If there are EVPN networking contributors, we can put it into agenda and set 
priority.

Could you help review this patch https://review.openstack.org/#/c/396564/, to 
see if the L2/L3 networking can meet your demand?

Best Regards
Chaoyi Huang ( Joe Huang )

From: dina@orange.com [mailto:dina@orange.com]
Sent: Wednesday, November 23, 2016 7:04 PM
To: joehuang; openstack-dev
Subject: RE: [openstack-dev][tricircle]Questions about Tricircle L2 and L3 
implementation

Hello Chaoyi,

Thanks for your answer.

Related to Route Target parameter (RT) : I referred to the figure displaying 
pods interconnection through an E-VPN L2 network ("Tricircle in a nutshell" 
presentation).

My question is : how are there populated and/or exchanged through the E-VPN 
interconnection ?

Thanks,

Best Regards,

Dina

De : joehuang [mailto:joehu...@huawei.com]
Envoyé : mercredi 23 novembre 2016 04:20
À : SOL Dina IMT/OLN; openstack-dev
Objet : RE: [openstack-dev][tricircle]Questions about Tricircle L2 and L3 
implementation

Hello, Dina,

Thank you for your comments, it'll be good to discuss tricircle related topic 
in openstack-dev so that more people can be involved in if necessary, and keep 
the project transparent. So I copied the reply to  
openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>.

For L2VxLAN, the VNI identifiers will be allocated in central Neutron, and then 
same VNI segment will be used for local Neutron during get_network or get_port 
from Nova, the local plugin in local Neutron will query the network segment 
info. and persist same uuid and VNI in local Neutron. But VxLAN based cross 
Neutron L2 networking has not started yet, the spec has not submitted for 
review yet, currently only VLAN based L2/L3 networking were implemented, 
supported features could be found in the release 
notes:https://github.com/openstack/tricircle/blob/master/releasenotes/notes/initial-release-notes.yaml
 .

 VxLAN L2 networking and VxLAN as the bridge network for L3 networking will 
rely on the patch for "formalize the tunnel termination point by adding it to 
the port binding data model" which is mentioned in "Eliminating L2pop as a 
mechanism driver" 
http://lists.openstack.org/pipermail/openstack-dev/2016-November/107061.html

Before VxLAN L2 networking and VxLAN as the bridge network for L3 networking, 
this spec is being reviewed, https://review.openstack.org/#/c/396564/, please 
join the review to see whether it can meet your demands, especially for the 
cross Neutron networking models.

What is "RT parameters"?

Tricircle supported L3 networking based on shared VLAN bridge network, you can 
refer to "6.6  L3 Networking across Neutron", but just as what mentioned in the 
release notes,  only VLAN L2 network and shared VLAN as the bridge network for 
L3 networking are supported.

There are todo list for the usage documentation in ocata release, you are 
welcome to join the contribution, no matter documentation or source code or 
review.

Best Regards
Chaoyi Huang (joehuang)

From: dina@orange.com<mailto:dina@orange.com> [dina@orange.com]
Sent: 22 November 2016 21:54
To: joehuang
Subject: Questions about Tricircle L2 and L3 implementation
Hello Chaoyi Huang,

I have read Tricirle wiki documentation and some presentations.
May I ask you I have few questions about Tricircle implementation ?
Here there are :

1°) L2 VxLAN
How are choosen VNI identifiers ?
How are choosen RT parameters ? Is a control plane used or all is configured 
within a pool ?

2°) L3
Does Tricircle support L3 interconnection ?
Have you documentation about that ?

Thanks,
Best Regards,

Dina SOL

[logo-Orange]
Dina Sol
Orange/ IMT/ OLN/ WTC/ IEE/ NAVI (Network Automation and Virtualized 
Infrastructure)
Orange Labs
2, avenue Pierre Marzin
22307 Lannion Cedex
tel : 00 33 (0)2 96 07 11 22
dina@orange.com<mailto:dina@orange-ftgroup.com>



_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should no

Re: [openstack-dev] [tricircle]Questions about Tricircle L2 and L3 implementation

[dina.sol]

Hello Chaoyi,

Thanks for your answer.

Related to Route Target parameter (RT) : I referred to the figure displaying 
pods interconnection through an E-VPN L2 network ("Tricircle in a nutshell" 
presentation).

My question is : how are there populated and/or exchanged through the E-VPN 
interconnection ?

Thanks,

Best Regards,

Dina

De : joehuang [mailto:joehu...@huawei.com]
Envoyé : mercredi 23 novembre 2016 04:20
À : SOL Dina IMT/OLN; openstack-dev
Objet : RE: [openstack-dev][tricircle]Questions about Tricircle L2 and L3 
implementation

Hello, Dina,

Thank you for your comments, it'll be good to discuss tricircle related topic 
in openstack-dev so that more people can be involved in if necessary, and keep 
the project transparent. So I copied the reply to  
openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>.

For L2VxLAN, the VNI identifiers will be allocated in central Neutron, and then 
same VNI segment will be used for local Neutron during get_network or get_port 
from Nova, the local plugin in local Neutron will query the network segment 
info. and persist same uuid and VNI in local Neutron. But VxLAN based cross 
Neutron L2 networking has not started yet, the spec has not submitted for 
review yet, currently only VLAN based L2/L3 networking were implemented, 
supported features could be found in the release 
notes:https://github.com/openstack/tricircle/blob/master/releasenotes/notes/initial-release-notes.yaml
 .

 VxLAN L2 networking and VxLAN as the bridge network for L3 networking will 
rely on the patch for "formalize the tunnel termination point by adding it to 
the port binding data model" which is mentioned in "Eliminating L2pop as a 
mechanism driver" 
http://lists.openstack.org/pipermail/openstack-dev/2016-November/107061.html

Before VxLAN L2 networking and VxLAN as the bridge network for L3 networking, 
this spec is being reviewed, https://review.openstack.org/#/c/396564/, please 
join the review to see whether it can meet your demands, especially for the 
cross Neutron networking models.

What is "RT parameters"?

Tricircle supported L3 networking based on shared VLAN bridge network, you can 
refer to "6.6  L3 Networking across Neutron", but just as what mentioned in the 
release notes,  only VLAN L2 network and shared VLAN as the bridge network for 
L3 networking are supported.

There are todo list for the usage documentation in ocata release, you are 
welcome to join the contribution, no matter documentation or source code or 
review.

Best Regards
Chaoyi Huang (joehuang)

From: dina@orange.com<mailto:dina@orange.com> [dina@orange.com]
Sent: 22 November 2016 21:54
To: joehuang
Subject: Questions about Tricircle L2 and L3 implementation
Hello Chaoyi Huang,

I have read Tricirle wiki documentation and some presentations.
May I ask you I have few questions about Tricircle implementation ?
Here there are :

1°) L2 VxLAN
How are choosen VNI identifiers ?
How are choosen RT parameters ? Is a control plane used or all is configured 
within a pool ?

2°) L3
Does Tricircle support L3 interconnection ?
Have you documentation about that ?

Thanks,
Best Regards,

Dina SOL

[logo-Orange]
Dina Sol
Orange/ IMT/ OLN/ WTC/ IEE/ NAVI (Network Automation and Virtualized 
Infrastructure)
Orange Labs
2, avenue Pierre Marzin
22307 Lannion Cedex
tel : 00 33 (0)2 96 07 11 22
dina@orange.com<mailto:dina@orange-ftgroup.com>



_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi qu

Re: [openstack-dev] [tricircle]Tricricle cleanning

[joehuang]

Great, all patches are ready now for Tricircle cleaning:

Review and Merge order:

1.central and local plugin for l3: https://review.openstack.org/#/c/378476/
2. remove api gateway code: https://review.openstack.org/#/c/384182/
3.  security group support: https://review.openstack.org/#/c/380054/
4: Single Node installation: https://review.openstack.org/#/c/384872/
5. Multi nodes installation:  https://review.openstack.org/#/c/385306/

Best Regards
Chaoyi Huang (joehuang)

From: Vega Cai [luckyveg...@gmail.com]
Sent: 12 October 2016 15:52
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle]Tricricle cleanning

Hello, patch for installation guide update of multi-node deployment has just 
been submitted.  Here is the link:
https://review.openstack.org/#/c/385306/

BR
Zhiyuan

On Wed, 12 Oct 2016 at 10:17 joehuang 
<joehu...@huawei.com<mailto:joehu...@huawei.com>> wrote:
Hello, Team,

Understand this period is keeping us quite busy, for the Tricircle cleaning is 
in parallel with newton release period. Fortunately we have made great progress 
for the Tricircle cleaning and Newton release is approaching completeness.

(https://etherpad.openstack.org/p/TricircleSplitting)


  *   DONE 1. update README: https://review.openstack.org/#/c/375218/

  *   DONE 1. local plugin spec: https://review.openstack.org/#/c/368529/

  *   DONE 1. local and central plugin: https://review.openstack.org/#/c/375281/

  *
  *   2.central and local plugin for l3: 
https://review.openstack.org/#/c/378476/

  *   2. remove api gateway code: https://review.openstack.org/#/c/384182/

  *   3.  security group support: https://review.openstack.org/#/c/380054/

  *   3. installation guide update(no api gateway):

  *   Part1: Single Node installation: https://review.openstack.org/#/c/384872/

  *   Part2: Multi nodes installation: WIP

  *

  *   - Try to get these above cleaning patches merged before Oct.19, 
before Barcelona summit.

Except the patch " Multi nodes installation", all other patches are in the 
queue of review for the Tricircle cleaning. After these patches get merged, we 
can have a first clean Tricircle baseline for networking automation, it's good 
to have a tagging for this baseline as a milestone.

Best Regards
Chaoyi Huang (joehuang)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
BR
Zhiyuan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]Tricricle cleanning

[Vega Cai]

Hello, patch for installation guide update of multi-node deployment has
just been submitted.  Here is the link:
https://review.openstack.org/#/c/385306/

BR
Zhiyuan

On Wed, 12 Oct 2016 at 10:17 joehuang  wrote:

> Hello, Team,
>
> Understand this period is keeping us quite busy, for the Tricircle
> cleaning is in parallel with newton release period. Fortunately we have
> made great progress for the Tricircle cleaning and Newton release is
> approaching completeness.
>
> (https://etherpad.openstack.org/p/TricircleSplitting)
>
>
>- DONE 1. update README: https://review.openstack.org/#/c/375218/
>
>
>- DONE 1. local plugin spec: https://review.openstack.org/#/c/368529/
>
>
>- DONE 1. local and central plugin:
>https://review.openstack.org/#/c/375281/
>
>
>-
>- 2.central and local plugin for l3:
>https://review.openstack.org/#/c/378476/
>
>
>- 2. remove api gateway code: https://review.openstack.org/#/c/384182/
>
>
>- 3.  security group support: https://review.openstack.org/#/c/380054/
>
>
>- 3. installation guide update(no api gateway):
>
>
>- Part1: Single Node installation:
>https://review.openstack.org/#/c/384872/
>
>
>- Part2: Multi nodes installation: WIP
>
>
>-
>
>
>- - Try to get these above cleaning patches merged before Oct.19,
>before Barcelona summit.
>
>
>
>
> Except the patch " Multi nodes installation", all other patches are in
> the queue of review for the Tricircle cleaning. After these patches get
> merged, we can have a first clean Tricircle baseline for networking
> automation, it's good to have a tagging for this baseline as a milestone.
>
> Best Regards
> Chaoyi Huang (joehuang)
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-- 
BR
Zhiyuan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]

[Swapnil Kulkarni (coolsvap)]

Glad to see you here sir :)

Best Regards,
Swapnil

On Fri, Sep 30, 2016 at 6:17 PM, Chandrakant Bagade
 wrote:
> Hello ,
>
>
>
> Myself Chandrakant Bagade , working at Persistent System Ltd.
>
> I was trying Tricircle with devstack and found it , a very helpful  idea to
> datacenter management.
>
>
>
> I can see feature like provisioning , image/vm/volume management therein.
>
> I was wondering if features like monitoring/inventory management is also
> available there or planned for coming released. I read the docs but couldn’t
> find the information.
>
>
>
> Can someone from Tricircle team , help me with my query. If these are
> available , then pointer/documents to those would be much appreciated.
>
>
>
> Thanks,
>
> Chandrakant
>
> DISCLAIMER == This e-mail may contain privileged and confidential
> information which is the property of Persistent Systems Ltd. It is intended
> only for the use of the individual or entity to which it is addressed. If
> you are not the intended recipient, you are not authorized to read, retain,
> copy, print, distribute or use this message. If you have received this
> communication in error, please notify the sender and delete all copies of
> this message. Persistent Systems Ltd. does not accept any liability for
> virus infected mails.
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]

[joehuang]

Hello, Chandrakant,

Thank you for your interest on Tricircle.

There is no features about monitoring/inventory management yet in Tricircle.

And Tricircle is cleaning to be a project dedicated for networking automation 
across Neutron, and API gateway related function will be moved to a new project 
"Trio2o". You can refer to https://etherpad.openstack.org/p/TricircleSplitting 
for the cleaning, or track the splitting through the blueprint: 
https://blueprints.launchpad.net/tricircle/+spec/make-tricircle-dedicated-for-networking-automation-across-neutron

Are you interested in contributing in these projects?

Best Regards
Chaoyi Huang (joehuang)

From: Chandrakant Bagade [chandrakant_bag...@persistent.com]
Sent: 30 September 2016 20:47
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [tricircle]

Hello ,

Myself Chandrakant Bagade , working at Persistent System Ltd.
I was trying Tricircle with devstack and found it , a very helpful  idea to 
datacenter management.

I can see feature like provisioning , image/vm/volume management therein.
I was wondering if features like monitoring/inventory management is also 
available there or planned for coming released. I read the docs but couldn’t 
find the information.

Can someone from Tricircle team , help me with my query. If these are available 
, then pointer/documents to those would be much appreciated.

Thanks,
Chandrakant

DISCLAIMER == This e-mail may contain privileged and confidential 
information which is the property of Persistent Systems Ltd. It is intended 
only for the use of the individual or entity to which it is addressed. If you 
are not the intended recipient, you are not authorized to read, retain, copy, 
print, distribute or use this message. If you have received this communication 
in error, please notify the sender and delete all copies of this message. 
Persistent Systems Ltd. does not accept any liability for virus infected mails.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]freeze date and patches to be merged for Newton release

[joehuang]

Thank you all for the great effort, now only two patches of MUST TO HAVE are on 
the way to be merged:

https://review.openstack.org/#/c/372414/ installation update
https://review.openstack.org/#/c/326192/ volume detach

Best Regards
Chaoyi Huang (joehuang)

From: joehuang
Sent: 22 September 2016 9:42
To: openstack-dev
Subject: [openstack-dev][tricircle]freeze date and patches to be merged for 
Newton release

Hello,

During yesterday's weekly meeting, patches were identified for these must be 
merged before freeze date for Newton release:

Freeze date: Sept.30, 2016

Must to have: must be merged before Sept.30, basic feature for Tricircle Newton 
release
https://review.openstack.org/#/c/356187/ framework for dynamic pod binding
https://review.openstack.org/354604 floating ip deletion
https://review.openstack.org/355847 subnet deletion
https://review.openstack.org/360848 router deletion
https://review.openstack.org/#/c/366606/ server action part1
https://review.openstack.org/#/c/369958/ server action part2
https://review.openstack.org/#/c/372414/ installation update
https://review.openstack.org/#/c/326192/ volume detach

Good to have: best effort
https://review.openstack.org/#/c/323687/ add resource_affinity_tag
https://review.openstack.org/368529 spec for local plugin
https://review.openstack.org/#/c/359561/
others not mentioned here

You can also refer to https://etherpad.openstack.org/p/TricircleNewtonFreeze  
for the discussion log.

Let's update patch and review in time to ensure "Must to have" get merged 
before freeze date Sept.30.

Thank you for your great effort. The Newton branch will be created at UTC 
9:00AM Sept.30.

Best Regards
Chaoyi Huang (joehuang)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]freeze date and patches to be merged for Newton release

[joehuang]

Good idea, Two patches got merged yesterday.

Reorganized the items as follows, updated in 
https://etherpad.openstack.org/p/TricircleNewtonFreeze:

MUST TO HAVE: subnet deletion

  *   https://review.openstack.org/355847

  *

MUST TO HAVE: router deletion

  *   https://review.openstack.org/360848

  *

MUST TO HAVE: server action part2

  *   https://review.openstack.org/#/c/369958/

MUST TO HAVE: framework for dynamic pod binding

  *   https://review.openstack.org/#/c/356187/

  *

MUST TO HAVE: volume detach

  *   https://review.openstack.org/#/c/326192/

MUST TO HAVE: installation update

  *   https://review.openstack.org/#/c/372414/

  *

MUST TO HAVE: floating ip deletion (merged)

  *   https://review.openstack.org/354604

  *

MUST TO HAVE: server action part1 (merged)

  *   https://review.openstack.org/#/c/366606/

GOOD TO HAVE: add resource_affinity_tag

  *   https://review.openstack.org/#/c/323687/

  *

GOOD TO HAVE: spec for local plugin

  *   https://review.openstack.org/368529

  *

GOOD TO HAVE: force detach volume

  *   https://review.openstack.org/#/c/359561/

GOOD TO HAVE: others not mentioned here


It's hard to rank these MUST TO HAVE items, so let's review MUST TO HAVE patch 
in time when it's ready or with new update.

Best Regards
Chaoyi Huang (joehuang)

From: Shinobu Kinjo [shinobu...@gmail.com]
Sent: 22 September 2016 18:00
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle]freeze date and patches to be merged 
for Newton release

Please add 1 line above description of each patch.

MUST TO HAVE
or
GOOD TO HAVE

e.g.,
https://review.openstack.org/#/c/356187/

 MUST TO HAVE
 The framework of dynamic pod binding.

So that we can prioritize clearly and easily.

Ideally we should have made priority for each *MUST* case.

Regards,
Shinobu


On Thu, Sep 22, 2016 at 10:42 AM, joehuang 
<joehu...@huawei.com<mailto:joehu...@huawei.com>> wrote:
Hello,

During yesterday's weekly meeting, patches were identified for these must be 
merged before freeze date for Newton release:

Freeze date: Sept.30, 2016

Must to have: must be merged before Sept.30, basic feature for Tricircle Newton 
release
https://review.openstack.org/#/c/356187/ framework for dynamic pod binding
https://review.openstack.org/354604 floating ip deletion
https://review.openstack.org/355847 subnet deletion
https://review.openstack.org/360848 router deletion
https://review.openstack.org/#/c/366606/ server action part1
https://review.openstack.org/#/c/369958/ server action part2
https://review.openstack.org/#/c/372414/ installation update
https://review.openstack.org/#/c/326192/ volume detach

Good to have: best effort
https://review.openstack.org/#/c/323687/ add resource_affinity_tag
https://review.openstack.org/368529 spec for local plugin
https://review.openstack.org/#/c/359561/
others not mentioned here

You can also refer to https://etherpad.openstack.org/p/TricircleNewtonFreeze  
for the discussion log.

Let's update patch and review in time to ensure "Must to have" get merged 
before freeze date Sept.30.

Thank you for your great effort. The Newton branch will be created at UTC 
9:00AM Sept.30.

Best Regards
Chaoyi Huang (joehuang)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




--
Email:
shin...@linux.com<mailto:shin...@linux.com>
shin...@redhat.com<mailto:shin...@redhat.com>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]freeze date and patches to be merged for Newton release

[Shinobu Kinjo]

Please add 1 line above description of each patch.

MUST TO HAVE
or
GOOD TO HAVE

e.g.,
https://review.openstack.org/#/c/356187/

 MUST TO HAVE
 The framework of dynamic pod binding.

So that we can prioritize clearly and easily.

Ideally we should have made priority for each *MUST* case.

Regards,
Shinobu


On Thu, Sep 22, 2016 at 10:42 AM, joehuang  wrote:

> Hello,
>
> During yesterday's weekly meeting, patches were identified for these must
> be merged before freeze date for Newton release:
>
> Freeze date: Sept.30, 2016
>
> Must to have: must be merged before Sept.30, basic feature for Tricircle
> Newton release
> https://review.openstack.org/#/c/356187/ framework for dynamic pod binding
> https://review.openstack.org/354604 floating ip deletion
> https://review.openstack.org/355847 subnet deletion
> https://review.openstack.org/360848 router deletion
> https://review.openstack.org/#/c/366606/ server action part1
> https://review.openstack.org/#/c/369958/ server action part2
> https://review.openstack.org/#/c/372414/ installation update
> https://review.openstack.org/#/c/326192/ volume detach
>
> Good to have: best effort
> https://review.openstack.org/#/c/323687/ add resource_affinity_tag
> https://review.openstack.org/368529 spec for local plugin
> https://review.openstack.org/#/c/359561/
> others not mentioned here
>
> You can also refer to https://etherpad.openstack.
> org/p/TricircleNewtonFreeze  for the discussion log.
>
> Let's update patch and review in time to ensure "Must to have" get merged
> before freeze date Sept.30.
>
> Thank you for your great effort. The Newton branch will be created at UTC
> 9:00AM Sept.30.
>
> Best Regards
> Chaoyi Huang (joehuang)
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Email:
shin...@linux.com
shin...@redhat.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] Should we discuss the use cases of force volume detach in the Tricircle

[joehuang]

Hello,

I think Duncan's comments in another thread make sense to me. How do you think 
about it?

Best Regards
Chaoyi Huang (joehuang)

From: D'Angelo, Scott [scott.dang...@hpe.com]
Sent: 19 September 2016 20:34
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle] Should we discuss the use cases of 
force volume detach in the Tricircle


Please keep in mind that Nova keeps some volume state in the BlockDeviceMapping 
table. Without changes to Nova, a force_detach function is not complete.

I am interested in this use case, as are other Cinder developers. Please feel 
free to contact me in IRC with questions as "scottda".


Scott D'Angelo


From: joehuang <joehu...@huawei.com>
Sent: Sunday, September 18, 2016 3:29:29 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle] Should we discuss the use cases of 
force volume detach in the Tricircle

This is a good question. I also sent a mail in cinder thread that wants to know 
why the tempest test cases missing for the "force volume detach".
The spec for the "force volume detach" could be found here: 
https://github.com/openstack/cinder-specs/blob/master/specs/liberty/implement-force-detach-for-safe-cleanup.rst

From: cr_...@126.com [cr_...@126.com]
Sent: 18 September 2016 16:53
To: openstack-dev
Subject: [openstack-dev] [tricircle] Should we discuss the use cases of force 
volume detach in the Tricircle

Hello，
When the patch "force volume detach" has submited , some proposals have came 
back.
The important point is wheathe this function is needed or safe.
Should we disscuss some uses cases of this function. Such as the define of this 
function, when this function been triggered.



Best regards,
Ronghui Cao, Ph.D. Candidate
College of Information Science and Engineering
Hunan University, Changsha 410082, Hunan, China
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]freeze date and tricircle splitting

[joehuang]

very good, let's look over each patch (for all patches in review) in the weekly 
meeting to decide whether it should be merged before freeze.

Best Regards
Chaoyi Huang (joehuang)


From: Shinobu Kinjo [shinobu...@gmail.com]
Sent: 20 September 2016 15:45
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle]freeze date and tricircle splitting

Good point.

On Tue, Sep 20, 2016 at 3:00 PM, Vega Cai <luckyveg...@gmail.com> wrote:
> Since the patches for layer 3 networking automation has been merged, I think
> we'd better include the patches for resource cleaning in the tagged branch.
> Here is the list:
>
> Floating ip deletion: https://review.openstack.org/354604
> Subnet cleaning: https://review.openstack.org/355847
> Router cleaning: https://review.openstack.org/360848
>
> Shinobu Kinjo <shinobu...@gmail.com>于2016年9月20日周二 下午12:04写道：
>>
>> This announcement should have been first to avoid any unnecessary work -;
>>
>> On Tue, Sep 20, 2016 at 12:51 PM, joehuang <joehu...@huawei.com> wrote:
>> > Hello, as the Trio2o repository has been established, it's time for us
>> > to
>> > discuss the freeze date and tagging(newton branch) for the last release
>> > of
>> > Tricircle with gateway function.
>> >
>> > The freeze date is the gate for patches to be merged before
>> > tagging(newton
>> > branch). If a patch can't finish review process before the freeze date,
>> > and
>> > not able to be merged in Tricircle, then it's suggested to be handled
>> > like
>> > this:
>> >
>> > 1. If it's networking automation related patch, continue the review
>> > process
>> > in Tricircle after tagging(newton branch), will be merged in Tricircle
>> > trunk
>> > in the future .
>> >
>> > 2. If it's gateway related patch, abandon the patch, re-submit the patch
>> > in
>> > Trio2o.
>> >
>> > 3. If it's patch about pod management, for it's common feature, so
>> > continue
>> > the review process in tricircle  after tagging(newton branch) , and
>> > submit a
>> > new patch for this feature in Trio2o separately.
>> >
>> > Exception request after freeze date, before tagging(newton branch): If
>> > there
>> > is some patch must be merged before the tagging(newton branch), then
>> > need to
>> > send the exception request in the mail-list for the patch, and approved
>> > by
>> > PTL.
>> >
>> > That means we need to define a deadline for patches to be merged in
>> > Tricircle before tagging(newton branch), and define the scope of patches
>> > wish to be merged in Trcircle before splitting.
>> >
>> > Your thoughts, proposal for the freeze date and patches to be merged?
>> >
>> > (As the old thread containing both Trio2o and Tricircle in the subject,
>> > not
>> > good to follow, so a new thread is started)
>> >
>> > Best Regards
>> > Chaoyi Huang (joehuang)
>> >
>> > 
>> > From: joehuang
>> > Sent: 18 September 2016 16:34
>> > To: OpenStack Development Mailing List (not for usage questions)
>> > Subject: RE: [openstack-dev] [tricircle][trio2o] trio2o git repo ready
>> > and
>> > tricircle splitting
>> >
>> > Thank you for your comment, Zhiyuan.
>> >
>> > For pod management, because these two projects need to run
>> > independently, I
>> > think submit patches separately as needed may be a better choice.
>> >
>> > Best Regards
>> > Chaoyi Huang(joehuang)
>> > 
>> > From: Vega Cai [luckyveg...@gmail.com]
>> > Sent: 18 September 2016 16:27
>> > To: OpenStack Development Mailing List (not for usage questions)
>> > Subject: Re: [openstack-dev] [tricircle][trio2o] trio2o git repo ready
>> > and
>> > tricircle splitting
>> >
>> > +1 for the proposal. What about the codes for Pod operation? It seems
>> > that
>> > both Tricircle and Trio2o need these codes. We submit patches to these
>> > two
>> > projects separately?
>> >
>> > Zhiyuan
>> >
>> > joehuang <joehu...@huawei.com>于2016年9月18日周日 下午4:17写道：
>> >>
>> >> hello, team,
>> >>
>> >> Trio2o git repository is ready now: https://github.com/openstack/trio2o
>> >>
>&g

Re: [openstack-dev] [tricircle]freeze date and tricircle splitting

[Shinobu Kinjo]

This announcement should have been first to avoid any unnecessary work -;

On Tue, Sep 20, 2016 at 12:51 PM, joehuang <joehu...@huawei.com> wrote:
> Hello, as the Trio2o repository has been established, it's time for us to
> discuss the freeze date and tagging(newton branch) for the last release of
> Tricircle with gateway function.
>
> The freeze date is the gate for patches to be merged before tagging(newton
> branch). If a patch can't finish review process before the freeze date, and
> not able to be merged in Tricircle, then it's suggested to be handled like
> this:
>
> 1. If it's networking automation related patch, continue the review process
> in Tricircle after tagging(newton branch), will be merged in Tricircle trunk
> in the future .
>
> 2. If it's gateway related patch, abandon the patch, re-submit the patch in
> Trio2o.
>
> 3. If it's patch about pod management, for it's common feature, so continue
> the review process in tricircle  after tagging(newton branch) , and submit a
> new patch for this feature in Trio2o separately.
>
> Exception request after freeze date, before tagging(newton branch): If there
> is some patch must be merged before the tagging(newton branch), then need to
> send the exception request in the mail-list for the patch, and approved by
> PTL.
>
> That means we need to define a deadline for patches to be merged in
> Tricircle before tagging(newton branch), and define the scope of patches
> wish to be merged in Trcircle before splitting.
>
> Your thoughts, proposal for the freeze date and patches to be merged?
>
> (As the old thread containing both Trio2o and Tricircle in the subject, not
> good to follow, so a new thread is started)
>
> Best Regards
> Chaoyi Huang (joehuang)
>
> 
> From: joehuang
> Sent: 18 September 2016 16:34
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: RE: [openstack-dev] [tricircle][trio2o] trio2o git repo ready and
> tricircle splitting
>
> Thank you for your comment, Zhiyuan.
>
> For pod management, because these two projects need to run independently, I
> think submit patches separately as needed may be a better choice.
>
> Best Regards
> Chaoyi Huang(joehuang)
> ________
> From: Vega Cai [luckyveg...@gmail.com]
> Sent: 18 September 2016 16:27
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [tricircle][trio2o] trio2o git repo ready and
> tricircle splitting
>
> +1 for the proposal. What about the codes for Pod operation? It seems that
> both Tricircle and Trio2o need these codes. We submit patches to these two
> projects separately?
>
> Zhiyuan
>
> joehuang <joehu...@huawei.com>于2016年9月18日周日 下午4:17写道：
>>
>> hello, team,
>>
>> Trio2o git repository is ready now: https://github.com/openstack/trio2o
>>
>> The repository inherited all files and commit messages from Tricircle.
>>
>> It's now the time start to do the tricircle splitting: a blue print is
>> registere for Tricircle cleaning:
>> https://blueprints.launchpad.net/tricircle/+spec/make-tricircle-dedicated-for-networking-automation-across-neutron.There
>> are lots of documentation work to do. Please review these doc in the BP,
>> thanks.
>>
>> There are some proposal for patches during the splitting:
>>
>> 1. For patch which is already in review status, let's review it in
>> Tricircle (no matter it's for Trio2o or Tricircle), after it's get merged,
>> then port it to Trio2o. After all patches get merged, let's have a last tag
>> for Tricircle to cover both gateway and networking automation function. Then
>> the cleaning will be done in Tricircle to make Tricircle as a project for
>> networking automation only
>> 2. For new patch which is only applicable to Trio2o, I propose that we
>> submit such patches in Trio2o only, no need to submit in Tricircle.
>>
>> Would like to know your thoughts on the splitting.
>>
>> Best Regards
>> Chaoyi Huang(joehuang)
>>
>>
>>
>>
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Email:
shin...@linux.com
shin...@redhat.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] Should we discuss the use cases of force volume detach in the Tricircle

[D'Angelo, Scott]

Please keep in mind that Nova keeps some volume state in the BlockDeviceMapping 
table. Without changes to Nova, a force_detach function is not complete.

I am interested in this use case, as are other Cinder developers. Please feel 
free to contact me in IRC with questions as "scottda".


Scott D'Angelo


From: joehuang <joehu...@huawei.com>
Sent: Sunday, September 18, 2016 3:29:29 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle] Should we discuss the use cases of 
force volume detach in the Tricircle

This is a good question. I also sent a mail in cinder thread that wants to know 
why the tempest test cases missing for the "force volume detach".
The spec for the "force volume detach" could be found here: 
https://github.com/openstack/cinder-specs/blob/master/specs/liberty/implement-force-detach-for-safe-cleanup.rst

From: cr_...@126.com [cr_...@126.com]
Sent: 18 September 2016 16:53
To: openstack-dev
Subject: [openstack-dev] [tricircle] Should we discuss the use cases of force 
volume detach in the Tricircle

Hello，
When the patch "force volume detach" has submited , some proposals have came 
back.
The important point is wheathe this function is needed or safe.
Should we disscuss some uses cases of this function. Such as the define of this 
function, when this function been triggered.



Best regards,
Ronghui Cao, Ph.D. Candidate
College of Information Science and Engineering
Hunan University, Changsha 410082, Hunan, China
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]PTL candidacy

[HU, BIN]

+1

From: joehuang [mailto:joehu...@huawei.com]
Sent: Sunday, September 18, 2016 2:27 AM
To: openstack-dev 
Subject: [openstack-dev] [tricircle]PTL candidacy

Hello,

This is Chaoyi Huang(nick: joehuang), I would like to nominate myself as 
Tricircle PTL in Ocata release.

Before look forward to what to do in Ocata release, I want to have a short look 
back what's Tricircle has done in Newton release. The objectives and our 
progress in Newton release are:
* Cross OpenStack L2 networking: "local network" and "shared vlan" supported in 
Tricircle for L2/L3 networking functionalities, this is a great fundamental for 
our Newton release.
* Dynamic pod binding: the framework is in review.
* Tempest and basic VM/Volume operation: tempest based check and gate test has 
been integrated into the process, support basic features tempest
* Keep Tricircle follow OpenStack open source development guideline to make 
Tricircle project as open as any other OpenStack project, so that more and
more talents would like to join and contribute in Tricircle, and target at 
being a big tent project of OpenStack, being member of OpenStack eco-system and 
help the eco-system to address the problem domain in multi-OpenStack cloud, no 
matter it's in one site or multi-site: now Tricircle is applying big-tent 
application, and the splitting is ongoing, and glad to see more and more 
contributors join Tricricle community.

This is great progress for Tricricle based on every contributor's great effort.

As the Tricircle will be splitted and dedicate for cross Neutron networking 
automation, my vision for Tricircle Ocata will based on our basis in Newton 
release and what we discussed in these weeks:

* Ensure the Tricircle splitting smoothly with quality.
* Continue cross OpenStack L2/L3 networking, and work with upstream projects 
like Neutron, L2GW
* Being better citizen in OpenStack, continue the big-tent application, and 
collaboration with other projects
* enhance the installation method and make it easier to play Tricircle, so that 
more contributors would like to join Tricircle.
* Start advance networking service support in Ocata for Tricircle if possible

Since the Tricircle project tries to address very fundamental cross Neutron 
networking automation chanllenges, it's exciting to work and contribute in such 
a project, let's enjoy the journey.

Best Regards
Chaoyi Huang(joehuang)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]PTL candidacy

[Shinobu Kinjo]

No objection.
I really appreciate your great leadership.

Cheers,
Shinobu

On Sun, Sep 18, 2016 at 6:26 PM, joehuang  wrote:
> Hello,
>
> This is Chaoyi Huang(nick: joehuang), I would like to nominate myself as
> Tricircle PTL in Ocata release.
>
> Before look forward to what to do in Ocata release, I want to have a short
> look back what's Tricircle has done in Newton release. The objectives and
> our progress in Newton release are:
>
> * Cross OpenStack L2 networking: "local network" and "shared vlan" supported
> in Tricircle for L2/L3 networking functionalities, this is a great
> fundamental for our Newton release.
> * Dynamic pod binding: the framework is in review.
> * Tempest and basic VM/Volume operation: tempest based check and gate test
> has been integrated into the process, support basic features tempest
> * Keep Tricircle follow OpenStack open source development guideline to make
> Tricircle project as open as any other OpenStack project, so that more and
> more talents would like to join and contribute in Tricircle, and target at
> being a big tent project of OpenStack, being member of OpenStack eco-system
> and help the eco-system to address the problem domain in multi-OpenStack
> cloud, no matter it's in one site or multi-site: now Tricircle is applying
> big-tent application, and the splitting is ongoing, and glad to see more and
> more contributors join Tricricle community.
>
>
> This is great progress for Tricricle based on every contributor's great
> effort.
>
> As the Tricircle will be splitted and dedicate for cross Neutron networking
> automation, my vision for Tricircle Ocata will based on our basis in Newton
> release and what we discussed in these weeks:
>
> * Ensure the Tricircle splitting smoothly with quality.
> * Continue cross OpenStack L2/L3 networking, and work with upstream projects
> like Neutron, L2GW
> * Being better citizen in OpenStack, continue the big-tent application, and
> collaboration with other projects
> * enhance the installation method and make it easier to play Tricircle, so
> that more contributors would like to join Tricircle.
> * Start advance networking service support in Ocata for Tricircle if
> possible
>
> Since the Tricircle project tries to address very fundamental cross Neutron
> networking automation chanllenges, it's exciting to work and contribute in
> such a project, let's enjoy the journey.
>
> Best Regards
> Chaoyi Huang(joehuang)
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Email:
shin...@linux.com
shin...@redhat.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] Should we discuss the use cases of force volume detach in the Tricircle

[joehuang]

This is a good question. I also sent a mail in cinder thread that wants to know 
why the tempest test cases missing for the "force volume detach".
The spec for the "force volume detach" could be found here: 
https://github.com/openstack/cinder-specs/blob/master/specs/liberty/implement-force-detach-for-safe-cleanup.rst

From: cr_...@126.com [cr_...@126.com]
Sent: 18 September 2016 16:53
To: openstack-dev
Subject: [openstack-dev] [tricircle] Should we discuss the use cases of force 
volume detach in the Tricircle

Hello，
When the patch "force volume detach" has submited , some proposals have came 
back.
The important point is wheathe this function is needed or safe.
Should we disscuss some uses cases of this function. Such as the define of this 
function, when this function been triggered.



Best regards,
Ronghui Cao, Ph.D. Candidate
College of Information Science and Engineering
Hunan University, Changsha 410082, Hunan, China
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle][trio2o] trio2o git repo ready and tricircle splitting

[joehuang]

Thank you for your comment, Zhiyuan.

For pod management, because these two projects need to run independently, I 
think submit patches separately as needed may be a better choice.

Best Regards
Chaoyi Huang(joehuang)

From: Vega Cai [luckyveg...@gmail.com]
Sent: 18 September 2016 16:27
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle][trio2o] trio2o git repo ready and 
tricircle splitting

+1 for the proposal. What about the codes for Pod operation? It seems that both 
Tricircle and Trio2o need these codes. We submit patches to these two projects 
separately?

Zhiyuan

joehuang <joehu...@huawei.com<mailto:joehu...@huawei.com>>于2016年9月18日周日 
下午4:17写道：
hello, team,

Trio2o git repository is ready now: https://github.com/openstack/trio2o

The repository inherited all files and commit messages from Tricircle.

It's now the time start to do the tricircle splitting: a blue print is 
registere for Tricircle cleaning: 
https://blueprints.launchpad.net/tricircle/+spec/make-tricircle-dedicated-for-networking-automation-across-neutron.There
 are lots of documentation work to do. Please review these doc in the BP, 
thanks.

There are some proposal for patches during the splitting:

1. For patch which is already in review status, let's review it in Tricircle 
(no matter it's for Trio2o or Tricircle), after it's get merged, then port it 
to Trio2o. After all patches get merged, let's have a last tag for Tricircle to 
cover both gateway and networking automation function. Then the cleaning will 
be done in Tricircle to make Tricircle as a project for networking automation 
only
2. For new patch which is only applicable to Trio2o, I propose that we submit 
such patches in Trio2o only, no need to submit in Tricircle.

Would like to know your thoughts on the splitting.

Best Regards
Chaoyi Huang(joehuang)






__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle][trio2o] trio2o git repo ready and tricircle splitting

[Vega Cai]

+1 for the proposal. What about the codes for Pod operation? It seems that
both Tricircle and Trio2o need these codes. We submit patches to these two
projects separately?

Zhiyuan

joehuang 于2016年9月18日周日 下午4:17写道：

> hello, team,
>
> Trio2o git repository is ready now: https://github.com/openstack/trio2o
>
> The repository inherited all files and commit messages from Tricircle.
>
> It's now the time start to do the tricircle splitting: a blue print is
> registere for Tricircle cleaning:
> https://blueprints.launchpad.net/tricircle/+spec/make-tricircle-dedicated-for-networking-automation-across-neutron
> .There are lots of documentation work to do. Please review these doc in
> the BP, thanks.
>
> There are some proposal for patches during the splitting:
>
> 1. For patch which is already in review status, let's review it in
> Tricircle (no matter it's for Trio2o or Tricircle), after it's get merged,
> then port it to Trio2o. After all patches get merged, let's have a last tag
> for Tricircle to cover both gateway and networking automation function.
> Then the cleaning will be done in Tricircle to make Tricircle as a project
> for networking automation only
> 2. For new patch which is only applicable to Trio2o, I propose that we
> submit such patches in Trio2o only, no need to submit in Tricircle.
>
> Would like to know your thoughts on the splitting.
>
> Best Regards
> Chaoyi Huang(joehuang)
>
>
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] your proposal for the name of networking and gateway sub-projects

[joehuang]

For oral interpretation, Trio2o could be "Try OpenStack api gateway to 
OpenStack for large scale and/or distributed cloud", but for formal 
interpretation, how about "Trio2o is to provide APIs gateway for multiple 
OpenStack clouds to act as a single OpenStack cloud".

And for Tricircle, "Tricircle is to provide networking automation across 
Neutron". 

Your thoughts?

Best Regards
Chaoyi Huang(joehuang)


From: joehuang
Sent: 08 September 2016 8:57
To: ski...@redhat.com; OpenStack Development Mailing List (not for usage 
questions)
Subject: RE: [openstack-dev] [tricircle] your proposal for the name of 
networking and gateway sub-projects

Hi, Shinobu and team,

For Trio2o we can define it more specifically as:

Try OpenStack api gateway to OpenStack for large scale cloud: so the meaning in 
short is trio2o.

This is my personal interpretation, how do you think about this interpretation?

-

And now the vote results are:

Trio2o, 8 votes
Triangel, 3 votes
Trifennal, 2 votes

Consider most of our active contributors have already vote for the naming, so 
Trio2o will be the name for the gateway project.

Best Regards
Chaoyi Huang (joehuang)

From: Shinobu Kinjo [shinobu...@gmail.com]
Sent: 07 September 2016 18:20
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle] your proposal for the name of 
networking and gateway sub-projects

I prefer this.

4. Trio2o, 3 votes

But I would like to make sure what this actually means more specifically.
How can we define this word?

openstack-to-openstack

Cheers,
Shinobu



On Tue, Sep 6, 2016 at 9:01 PM, liukun <kk_li...@163.com> wrote:
> Triangel +1
>
> At 2016-09-06 16:27:22, "joehuang" <joehu...@huawei.com> wrote:
>
> Hello,
>
> After the discussion in the #openstack-tricircle channel and mail-list, 4
> candidates
> available now, please vote the name for the new sub-project for api-gateway
> functionality:
>
> 1. Triangel, 2 votes
>   The Triangel are dolls that bring luck. Found some meaning may not all
> people like it, Zhiyuan proposed another candidate "Trio2o"
> 2. Tridonut, 0 votes
>   Three Donuts. Delicious food, often buy 3 get 1 free.
> 3. Trifennel, 2 votes
>   Three Fennel. Fennel is highly prized for its licorice-like flavor and
>   the myriad of health benefits it provides
> 4. Trio2o, 3 votes
>   openstack-to-openstack
>
> Some team members just joined the mail-list, so please continue to vote for
> the api-gateway project name.
>
> Best Regards
> Chaoyi Huang(joehuang)
>
> ________________
> From: joehuang
> Sent: 06 September 2016 9:04
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: RE: [openstack-dev] [tricircle] your proposal for the name of
> networking and gateway sub-projects
>
> I also like trio2o, +1 for trio2o.
>
> ________________
> From: xiulin yin [yinxiuli...@gmail.com]
> Sent: 05 September 2016 18:44
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [tricircle] your proposal for the name of
> networking and gateway sub-projects
>
> trio2o +1， Accurately express the function of the project.
>
> 2016-09-05 17:34 GMT+08:00 Vega Cai <luckyveg...@gmail.com>:
>>
>> Oops, sorry for "triangel". Then what about "trio2o",
>> openstack-to-openstack
>>
>> Zhiyuan
>>
>> Yipei Niu <newy...@gmail.com>于2016年9月5日周一 上午11:22写道：
>>>
>>> Trifennel +1
>>>
>>> Best regards,
>>> Yipei
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
> From: Dongfeng Huang [dfhua...@gmail.com]
> Sent: 05 September 2016 20:17
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [tricircle]your proposal for the name of
> networking and gateway sub-projects (joehuang)
>
>  Trifennel +1
>
>
>
>
>
>
> __
> OpenStack D

Re: [openstack-dev] [tricircle] your proposal for the name of networking and gateway sub-projects

[joehuang]

Hi, Shinobu and team,

For Trio2o we can define it more specifically as:

Try OpenStack api gateway to OpenStack for large scale cloud: so the meaning in 
short is trio2o.

This is my personal interpretation, how do you think about this interpretation?

-

And now the vote results are: 

Trio2o, 8 votes
Triangel, 3 votes
Trifennal, 2 votes

Consider most of our active contributors have already vote for the naming, so 
Trio2o will be the name for the gateway project.

Best Regards
Chaoyi Huang (joehuang)

From: Shinobu Kinjo [shinobu...@gmail.com]
Sent: 07 September 2016 18:20
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle] your proposal for the name of 
networking and gateway sub-projects

I prefer this.

4. Trio2o, 3 votes

But I would like to make sure what this actually means more specifically.
How can we define this word?

openstack-to-openstack

Cheers,
Shinobu



On Tue, Sep 6, 2016 at 9:01 PM, liukun <kk_li...@163.com> wrote:
> Triangel +1
>
> At 2016-09-06 16:27:22, "joehuang" <joehu...@huawei.com> wrote:
>
> Hello,
>
> After the discussion in the #openstack-tricircle channel and mail-list, 4
> candidates
> available now, please vote the name for the new sub-project for api-gateway
> functionality:
>
> 1. Triangel, 2 votes
>   The Triangel are dolls that bring luck. Found some meaning may not all
> people like it, Zhiyuan proposed another candidate "Trio2o"
> 2. Tridonut, 0 votes
>   Three Donuts. Delicious food, often buy 3 get 1 free.
> 3. Trifennel, 2 votes
>   Three Fennel. Fennel is highly prized for its licorice-like flavor and
>   the myriad of health benefits it provides
> 4. Trio2o, 3 votes
>   openstack-to-openstack
>
> Some team members just joined the mail-list, so please continue to vote for
> the api-gateway project name.
>
> Best Regards
> Chaoyi Huang(joehuang)
>
> 
> From: joehuang
> Sent: 06 September 2016 9:04
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: RE: [openstack-dev] [tricircle] your proposal for the name of
> networking and gateway sub-projects
>
> I also like trio2o, +1 for trio2o.
>
> 
> From: xiulin yin [yinxiuli...@gmail.com]
> Sent: 05 September 2016 18:44
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [tricircle] your proposal for the name of
> networking and gateway sub-projects
>
> trio2o +1， Accurately express the function of the project.
>
> 2016-09-05 17:34 GMT+08:00 Vega Cai <luckyveg...@gmail.com>:
>>
>> Oops, sorry for "triangel". Then what about "trio2o",
>> openstack-to-openstack
>>
>> Zhiyuan
>>
>> Yipei Niu <newy...@gmail.com>于2016年9月5日周一 上午11:22写道：
>>>
>>> Trifennel +1
>>>
>>> Best regards,
>>> Yipei
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
> From: Dongfeng Huang [dfhua...@gmail.com]
> Sent: 05 September 2016 20:17
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [tricircle]your proposal for the name of
> networking and gateway sub-projects (joehuang)
>
>  Trifennel +1
>
>
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



--
Email:
shin...@linux.com
shin...@redhat.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] your proposal for the name of networking and gateway sub-projects

[Shinobu Kinjo]

I prefer this.

4. Trio2o, 3 votes

But I would like to make sure what this actually means more specifically.
How can we define this word?

openstack-to-openstack

Cheers,
Shinobu



On Tue, Sep 6, 2016 at 9:01 PM, liukun <kk_li...@163.com> wrote:
> Triangel +1
>
> At 2016-09-06 16:27:22, "joehuang" <joehu...@huawei.com> wrote:
>
> Hello,
>
> After the discussion in the #openstack-tricircle channel and mail-list, 4
> candidates
> available now, please vote the name for the new sub-project for api-gateway
> functionality:
>
> 1. Triangel, 2 votes
>   The Triangel are dolls that bring luck. Found some meaning may not all
> people like it, Zhiyuan proposed another candidate "Trio2o"
> 2. Tridonut, 0 votes
>   Three Donuts. Delicious food, often buy 3 get 1 free.
> 3. Trifennel, 2 votes
>   Three Fennel. Fennel is highly prized for its licorice-like flavor and
>   the myriad of health benefits it provides
> 4. Trio2o, 3 votes
>   openstack-to-openstack
>
> Some team members just joined the mail-list, so please continue to vote for
> the api-gateway project name.
>
> Best Regards
> Chaoyi Huang(joehuang)
>
> 
> From: joehuang
> Sent: 06 September 2016 9:04
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: RE: [openstack-dev] [tricircle] your proposal for the name of
> networking and gateway sub-projects
>
> I also like trio2o, +1 for trio2o.
>
> 
> From: xiulin yin [yinxiuli...@gmail.com]
> Sent: 05 September 2016 18:44
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [tricircle] your proposal for the name of
> networking and gateway sub-projects
>
> trio2o +1， Accurately express the function of the project.
>
> 2016-09-05 17:34 GMT+08:00 Vega Cai <luckyveg...@gmail.com>:
>>
>> Oops, sorry for "triangel". Then what about "trio2o",
>> openstack-to-openstack
>>
>> Zhiyuan
>>
>> Yipei Niu <newy...@gmail.com>于2016年9月5日周一 上午11:22写道：
>>>
>>> Trifennel +1
>>>
>>> Best regards,
>>> Yipei
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
> From: Dongfeng Huang [dfhua...@gmail.com]
> Sent: 05 September 2016 20:17
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [tricircle]your proposal for the name of
> networking and gateway sub-projects (joehuang)
>
>  Trifennel +1
>
>
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Email:
shin...@linux.com
shin...@redhat.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]

[joehuang]

Welcome persisyemcelzy!

From: persistencelzy [persistence...@163.com]
Sent: 06 September 2016 19:22
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [tricircle]

Hello。












__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]

[joehuang]

Welcome, seems lots of contributors are joining the mail-list and landing in 
tricircle after the message sent in the irc.


From: liukun [kk_li...@163.com]
Sent: 06 September 2016 19:43
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [tricircle]

Tricircle,I am coming!




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]

[joehuang]

Welcome yuquanle,  new contributor!

From: yuquanle [yuqua...@126.com]
Sent: 06 September 2016 19:36
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [tricircle]

hello！








__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] your proposal for the name of networking and gateway sub-projects

[liukun]

Triangel +1

At 2016-09-06 16:27:22, "joehuang" <joehu...@huawei.com> wrote:

Hello,


After the discussion in the #openstack-tricircle channel and mail-list, 4 
candidates
available now, please vote the name for the new sub-project for api-gateway
functionality:


1. Triangel, 2 votes
  The Triangel are dolls that bring luck. Found some meaning may not all people 
like it, Zhiyuan proposed another candidate "Trio2o"
2. Tridonut, 0 votes
  Three Donuts. Delicious food, often buy 3 get 1 free.
3. Trifennel, 2 votes
  Three Fennel. Fennel is highly prized for its licorice-like flavor and
  the myriad of health benefits it provides
4. Trio2o, 3 votes
  openstack-to-openstack


Some team members just joined the mail-list, so please continue to vote for the 
api-gateway project name.


Best Regards
Chaoyi Huang(joehuang)


From: joehuang
Sent: 06 September 2016 9:04
To: OpenStack Development Mailing List (not for usage questions)
Subject: RE: [openstack-dev] [tricircle] your proposal for the name of 
networking and gateway sub-projects


I also like trio2o, +1 for trio2o.


From: xiulin yin [yinxiuli...@gmail.com]
Sent: 05 September 2016 18:44
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle] your proposal for the name of 
networking and gateway sub-projects


trio2o +1， Accurately express the function of the project.



2016-09-05 17:34 GMT+08:00 Vega Cai <luckyveg...@gmail.com>:

Oops, sorry for "triangel". Then what about "trio2o", openstack-to-openstack


Zhiyuan 


Yipei Niu <newy...@gmail.com>于2016年9月5日周一 上午11:22写道：

Trifennel +1


Best regards,
Yipei
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


From: Dongfeng Huang [dfhua...@gmail.com]
Sent: 05 September 2016 20:17
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [tricircle]your proposal for the name of 
networking and gateway sub-projects (joehuang)


 Trifennel +1__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] your proposal for the name of networking and gateway sub-projects

[yuquanle]

+1 for trio2o.

At 2016-09-06 16:27:22, "joehuang" <joehu...@huawei.com> wrote:

Hello,


After the discussion in the #openstack-tricircle channel and mail-list, 4 
candidates
available now, please vote the name for the new sub-project for api-gateway
functionality:


1. Triangel, 2 votes
  The Triangel are dolls that bring luck. Found some meaning may not all people 
like it, Zhiyuan proposed another candidate "Trio2o"
2. Tridonut, 0 votes
  Three Donuts. Delicious food, often buy 3 get 1 free.
3. Trifennel, 2 votes
  Three Fennel. Fennel is highly prized for its licorice-like flavor and
  the myriad of health benefits it provides
4. Trio2o, 3 votes
  openstack-to-openstack


Some team members just joined the mail-list, so please continue to vote for the 
api-gateway project name.


Best Regards
Chaoyi Huang(joehuang)


From: joehuang
Sent: 06 September 2016 9:04
To: OpenStack Development Mailing List (not for usage questions)
Subject: RE: [openstack-dev] [tricircle] your proposal for the name of 
networking and gateway sub-projects


I also like trio2o, +1 for trio2o.


From: xiulin yin [yinxiuli...@gmail.com]
Sent: 05 September 2016 18:44
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle] your proposal for the name of 
networking and gateway sub-projects


trio2o +1， Accurately express the function of the project.



2016-09-05 17:34 GMT+08:00 Vega Cai <luckyveg...@gmail.com>:

Oops, sorry for "triangel". Then what about "trio2o", openstack-to-openstack


Zhiyuan 


Yipei Niu <newy...@gmail.com>于2016年9月5日周一 上午11:22写道：

Trifennel +1


Best regards,
Yipei
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


From: Dongfeng Huang [dfhua...@gmail.com]
Sent: 05 September 2016 20:17
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [tricircle]your proposal for the name of 
networking and gateway sub-projects (joehuang)


 Trifennel +1__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] your proposal for the name of networking and gateway sub-projects

[hejiawei]

trio2o +1, it's concise






At 2016-09-06 16:27:22, "joehuang" <joehu...@huawei.com> wrote:

Hello,


After the discussion in the #openstack-tricircle channel and mail-list, 4 
candidates
available now, please vote the name for the new sub-project for api-gateway
functionality:


1. Triangel, 2 votes
  The Triangel are dolls that bring luck. Found some meaning may not all people 
like it, Zhiyuan proposed another candidate "Trio2o"
2. Tridonut, 0 votes
  Three Donuts. Delicious food, often buy 3 get 1 free.
3. Trifennel, 2 votes
  Three Fennel. Fennel is highly prized for its licorice-like flavor and
  the myriad of health benefits it provides
4. Trio2o, 3 votes
  openstack-to-openstack


Some team members just joined the mail-list, so please continue to vote for the 
api-gateway project name.


Best Regards
Chaoyi Huang(joehuang)


From: joehuang
Sent: 06 September 2016 9:04
To: OpenStack Development Mailing List (not for usage questions)
Subject: RE: [openstack-dev] [tricircle] your proposal for the name of 
networking and gateway sub-projects


I also like trio2o, +1 for trio2o.


From: xiulin yin [yinxiuli...@gmail.com]
Sent: 05 September 2016 18:44
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle] your proposal for the name of 
networking and gateway sub-projects


trio2o +1， Accurately express the function of the project.



2016-09-05 17:34 GMT+08:00 Vega Cai <luckyveg...@gmail.com>:

Oops, sorry for "triangel". Then what about "trio2o", openstack-to-openstack


Zhiyuan 


Yipei Niu <newy...@gmail.com>于2016年9月5日周一 上午11:22写道：

Trifennel +1


Best regards,
Yipei
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


From: Dongfeng Huang [dfhua...@gmail.com]
Sent: 05 September 2016 20:17
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [tricircle]your proposal for the name of 
networking and gateway sub-projects (joehuang)


 Trifennel +1__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] your proposal for the name of networking and gateway sub-projects

[joehuang]

Hello,

After the discussion in the #openstack-tricircle channel and mail-list, 4 
candidates
available now, please vote the name for the new sub-project for api-gateway
functionality:

1. Triangel, 2 votes
  The Triangel are dolls that bring luck. Found some meaning may not all people 
like it, Zhiyuan proposed another candidate "Trio2o"
2. Tridonut, 0 votes
  Three Donuts. Delicious food, often buy 3 get 1 free.
3. Trifennel, 2 votes
  Three Fennel. Fennel is highly prized for its licorice-like flavor and
  the myriad of health benefits it provides
4. Trio2o, 3 votes
  openstack-to-openstack

Some team members just joined the mail-list, so please continue to vote for the 
api-gateway project name.

Best Regards
Chaoyi Huang(joehuang)


From: joehuang
Sent: 06 September 2016 9:04
To: OpenStack Development Mailing List (not for usage questions)
Subject: RE: [openstack-dev] [tricircle] your proposal for the name of 
networking and gateway sub-projects

I also like trio2o, +1 for trio2o.


From: xiulin yin [yinxiuli...@gmail.com]
Sent: 05 September 2016 18:44
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle] your proposal for the name of 
networking and gateway sub-projects

trio2o +1， Accurately express the function of the project.

2016-09-05 17:34 GMT+08:00 Vega Cai 
<luckyveg...@gmail.com<mailto:luckyveg...@gmail.com>>:
Oops, sorry for "triangel". Then what about "trio2o", openstack-to-openstack

Zhiyuan

Yipei Niu <newy...@gmail.com<mailto:newy...@gmail.com>>于2016年9月5日周一 上午11:22写道：
Trifennel +1

Best regards,
Yipei
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

From: Dongfeng Huang [dfhua...@gmail.com]
Sent: 05 September 2016 20:17
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [tricircle]your proposal for the name of 
networking and gateway sub-projects (joehuang)

 Trifennel +1
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]

[joehuang]

Hello, Ronghui,

Saw your mail.

Best Regards
Chaoyi Huang(joehuang)

From: crh [cr_...@126.com]
Sent: 06 September 2016 15:44
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [tricircle]

hello



--



Best regards,
Ronghui Cao, Ph.D. Candidate
College of Information Science and Engineering
Hunan University, Changsha 410082, Hunan, China




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]

[joehuang]

Hello, Jiawei,

Now your mail has been sent to the openstack-dev list successfully

Best Regards
Chaoyi Huang(joehuang)

From: hejiawei [h452577...@126.com]
Sent: 06 September 2016 14:51
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [tricircle]

test




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] your proposal for the name of networking and gateway sub-projects

[joehuang]

I also like trio2o, +1 for trio2o.


From: xiulin yin [yinxiuli...@gmail.com]
Sent: 05 September 2016 18:44
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle] your proposal for the name of 
networking and gateway sub-projects

trio2o +1， Accurately express the function of the project.

2016-09-05 17:34 GMT+08:00 Vega Cai 
<luckyveg...@gmail.com<mailto:luckyveg...@gmail.com>>:
Oops, sorry for "triangel". Then what about "trio2o", openstack-to-openstack

Zhiyuan

Yipei Niu <newy...@gmail.com<mailto:newy...@gmail.com>>于2016年9月5日周一 上午11:22写道：
Trifennel +1

Best regards,
Yipei
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]your proposal for the name of networking and gateway sub-projects (joehuang)

[Dongfeng Huang]

 Trifennel +1
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] your proposal for the name of networking and gateway sub-projects

[xiulin yin]

trio2o +1， Accurately express the function of the project.

2016-09-05 17:34 GMT+08:00 Vega Cai :

> Oops, sorry for "triangel". Then what about "trio2o",
> openstack-to-openstack
>
> Zhiyuan
>
> Yipei Niu 于2016年9月5日周一 上午11:22写道：
>
>> Trifennel +1
>>
>> Best regards,
>> Yipei
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] your proposal for the name of networking and gateway sub-projects

[Vega Cai]

Oops, sorry for "triangel". Then what about "trio2o", openstack-to-openstack

Zhiyuan

Yipei Niu 于2016年9月5日周一 上午11:22写道：

> Trifennel +1
>
> Best regards,
> Yipei
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] your proposal for the name of networking and gateway sub-projects

[Yipei Niu]

Trifennel +1

Best regards,
Yipei
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] your proposal for the name of networking and gateway sub-projects

[Yipei Niu]

Triangel +1

Angel is a spiritual being believed to act as an attendant, agent, or
messenger of God, which is very similar to our project.

Best regards,
Yipei
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]your proposal for the name of networking and gateway sub-projects

[Shinobu Kinjo]

On Mon, Sep 5, 2016 at 10:35 AM, joehuang <joehu...@huawei.com> wrote:
> Hello,
>
> You can search "Triangel doll" from google: 
> https://www.google.com.hk/?gws_rd=ssl#safe=strict=triangel+doll
>
> But I also found a definition in 
> http://zh.urbandictionary.com/define.php?term=Triangel, so I don't know it's 
> a good candidate or not.

O.k, interesting enough.

Cheers,
Shinobu

>
> Please vote or recommend a new candidate. Thanks
>
> Best Regards
> Chaoyi Huang(joehuang)
>
> 
> From: Shinobu Kinjo [shinobu...@gmail.com]
> Sent: 05 September 2016 6:21
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [tricircle]your proposal for the name of 
> networking and gateway sub-projects
>
> Be more careful before emailing the list.
>
>   Triangel is not true.
>
>   Triangle is true.
>
> If there is a word expressed by Triangel, please point it out to me.
>
> Cheers,
> Shinobu
>
>
> On Sun, Sep 4, 2016 at 10:49 PM, Vega Cai <luckyveg...@gmail.com> wrote:
>> +1 for Triangel
>>
>> On 2 September 2016 at 17:34, joehuang <joehu...@huawei.com> wrote:
>>>
>>> After the discussion in the #openstack-tricircle channel, 3 candidates
>>> available now, please vote the name for the new sub-project for api-gateway
>>> functionality:
>>>
>>> 1. Triangel
>>> The Triangel are dolls that bring luck
>>> 2. Tridonut
>>> Three Donuts. Delicious food, often buy 3 get 1 free.
>>> 3. Trifennel
>>> Three Fennel. Fennel is highly prized for its licorice-like flavor and
>>> the myriad of health benefits it provides
>>>
>>> Best Regards
>>> Chaoyi Huang(joehuang)
>>>
>>>
>>> From: joehuang
>>> Sent: 02 September 2016 11:19
>>> To: openstack-dev; mord...@inaugust.com
>>> Subject: RE: [openstack-dev][tricircle]your proposal for the name of
>>> networking and gateway sub-projects
>>>
>>> I have some rough ideas about the name of gateway sub-project, for
>>> example, triangle, tridonut, tricookie etc, so that we can see that
>>> Tricircle and the new sub-project are like sibling in OpenStack. And they
>>> often will be listed closely in order.
>>>
>>> Your thoughts?
>>>
>>> Best Regards
>>> Chaoyi Huang(joehuang)
>>>
>>> 
>>> From: joehuang
>>> Sent: 02 September 2016 10:22
>>> To: openstack-dev; mord...@inaugust.com
>>> Subject: [openstack-dev][tricircle]your proposal for the name of
>>> networking and gateway sub-projects
>>>
>>> Hello,
>>>
>>> If we want to divide Tricircle into two sub-projects, your proposals for
>>> the name of sub-projects are welcome.
>>>
>>> Because the Tricircle is applying big-tent application, and the networking
>>> part will be remained in the Tricircle repository, and continue the big-tent
>>> application. So if we change the networking sub-project name from
>>> "Tricircle" to another one, we have to update a lots of places: from infra,
>>> to source code, to documentation, google docs, to wiki, etc, it's a huge
>>> work, and history background will also be lost, from this point of view, I
>>> proposal to remain current Tricircle repository name, but shrink the
>>> Tricircle scope to cross Neutron networking automation.
>>>
>>> And for gateway part, a new repository is required, new project name is
>>> more applicable, this is just my thoughts, would like to know your
>>> proposals.
>>>
>>> Best Regards
>>> Chaoyi Huang(joehuang)
>>>
>>> 
>>> From: joehuang
>>> Sent: 01 September 2016 9:02
>>> To: Monty Taylor; openstack-dev
>>> Subject: RE: [openstack-dev][tricircle]How to address TCs concerns in
>>> Tricircle big-tent application
>>>
>>> Hello, Monty,
>>>
>>> Thank you very much for your guide and encouragement, then let's move on
>>> this direction.
>>>
>>> Best regards
>>> Chaoyi Huang (joehuang)
>>> 
>>> From: Monty Taylor [mord...@inaugust.com]
>>> Sent: 01 September 2016 0:37
>>> To: joehuang; openstack-dev
>>> Subject: Re: [openstack-dev][tricircle]How to address TCs concerns in
>>> Tricircle big-tent application
>&

Re: [openstack-dev] [tricircle]your proposal for the name of networking and gateway sub-projects

[joehuang]

Hello, 

You can search "Triangel doll" from google: 
https://www.google.com.hk/?gws_rd=ssl#safe=strict=triangel+doll

But I also found a definition in 
http://zh.urbandictionary.com/define.php?term=Triangel, so I don't know it's a 
good candidate or not.

Please vote or recommend a new candidate. Thanks

Best Regards
Chaoyi Huang(joehuang)


From: Shinobu Kinjo [shinobu...@gmail.com]
Sent: 05 September 2016 6:21
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tricircle]your proposal for the name of 
networking and gateway sub-projects

Be more careful before emailing the list.

  Triangel is not true.

  Triangle is true.

If there is a word expressed by Triangel, please point it out to me.

Cheers,
Shinobu


On Sun, Sep 4, 2016 at 10:49 PM, Vega Cai <luckyveg...@gmail.com> wrote:
> +1 for Triangel
>
> On 2 September 2016 at 17:34, joehuang <joehu...@huawei.com> wrote:
>>
>> After the discussion in the #openstack-tricircle channel, 3 candidates
>> available now, please vote the name for the new sub-project for api-gateway
>> functionality:
>>
>> 1. Triangel
>> The Triangel are dolls that bring luck
>> 2. Tridonut
>> Three Donuts. Delicious food, often buy 3 get 1 free.
>> 3. Trifennel
>> Three Fennel. Fennel is highly prized for its licorice-like flavor and
>> the myriad of health benefits it provides
>>
>> Best Regards
>> Chaoyi Huang(joehuang)
>>
>>
>> From: joehuang
>> Sent: 02 September 2016 11:19
>> To: openstack-dev; mord...@inaugust.com
>> Subject: RE: [openstack-dev][tricircle]your proposal for the name of
>> networking and gateway sub-projects
>>
>> I have some rough ideas about the name of gateway sub-project, for
>> example, triangle, tridonut, tricookie etc, so that we can see that
>> Tricircle and the new sub-project are like sibling in OpenStack. And they
>> often will be listed closely in order.
>>
>> Your thoughts?
>>
>> Best Regards
>> Chaoyi Huang(joehuang)
>>
>> 
>> From: joehuang
>> Sent: 02 September 2016 10:22
>> To: openstack-dev; mord...@inaugust.com
>> Subject: [openstack-dev][tricircle]your proposal for the name of
>> networking and gateway sub-projects
>>
>> Hello,
>>
>> If we want to divide Tricircle into two sub-projects, your proposals for
>> the name of sub-projects are welcome.
>>
>> Because the Tricircle is applying big-tent application, and the networking
>> part will be remained in the Tricircle repository, and continue the big-tent
>> application. So if we change the networking sub-project name from
>> "Tricircle" to another one, we have to update a lots of places: from infra,
>> to source code, to documentation, google docs, to wiki, etc, it's a huge
>> work, and history background will also be lost, from this point of view, I
>> proposal to remain current Tricircle repository name, but shrink the
>> Tricircle scope to cross Neutron networking automation.
>>
>> And for gateway part, a new repository is required, new project name is
>> more applicable, this is just my thoughts, would like to know your
>> proposals.
>>
>> Best Regards
>> Chaoyi Huang(joehuang)
>>
>> 
>> From: joehuang
>> Sent: 01 September 2016 9:02
>> To: Monty Taylor; openstack-dev
>> Subject: RE: [openstack-dev][tricircle]How to address TCs concerns in
>> Tricircle big-tent application
>>
>> Hello, Monty,
>>
>> Thank you very much for your guide and encouragement, then let's move on
>> this direction.
>>
>> Best regards
>> Chaoyi Huang (joehuang)
>> 
>> From: Monty Taylor [mord...@inaugust.com]
>> Sent: 01 September 2016 0:37
>> To: joehuang; openstack-dev
>> Subject: Re: [openstack-dev][tricircle]How to address TCs concerns in
>> Tricircle big-tent application
>>
>> On 08/31/2016 02:16 AM, joehuang wrote:
>> > Hello, team,
>> >
>> > During last weekly meeting, we discussed how to address TCs concerns in
>> > Tricircle big-tent application. After the weekly meeting, the proposal
>> > was co-prepared by our
>> > contributors:
>> > https://docs.google.com/presentation/d/1kpVo5rsL6p_rq9TvkuczjommJSsisDiKJiurbhaQg7E
>> >
>> > The more doable way is to divide Tricircle into two independent and
>> > decoupled projects, only one of the projects which deal with networking
>>

Re: [openstack-dev] [tricircle]your proposal for the name of networking and gateway sub-projects

[Shinobu Kinjo]

Be more careful before emailing the list.

  Triangel is not true.

  Triangle is true.

If there is a word expressed by Triangel, please point it out to me.

Cheers,
Shinobu


On Sun, Sep 4, 2016 at 10:49 PM, Vega Cai <luckyveg...@gmail.com> wrote:
> +1 for Triangel
>
> On 2 September 2016 at 17:34, joehuang <joehu...@huawei.com> wrote:
>>
>> After the discussion in the #openstack-tricircle channel, 3 candidates
>> available now, please vote the name for the new sub-project for api-gateway
>> functionality:
>>
>> 1. Triangel
>> The Triangel are dolls that bring luck
>> 2. Tridonut
>> Three Donuts. Delicious food, often buy 3 get 1 free.
>> 3. Trifennel
>> Three Fennel. Fennel is highly prized for its licorice-like flavor and
>> the myriad of health benefits it provides
>>
>> Best Regards
>> Chaoyi Huang(joehuang)
>>
>>
>> From: joehuang
>> Sent: 02 September 2016 11:19
>> To: openstack-dev; mord...@inaugust.com
>> Subject: RE: [openstack-dev][tricircle]your proposal for the name of
>> networking and gateway sub-projects
>>
>> I have some rough ideas about the name of gateway sub-project, for
>> example, triangle, tridonut, tricookie etc, so that we can see that
>> Tricircle and the new sub-project are like sibling in OpenStack. And they
>> often will be listed closely in order.
>>
>> Your thoughts?
>>
>> Best Regards
>> Chaoyi Huang(joehuang)
>>
>> 
>> From: joehuang
>> Sent: 02 September 2016 10:22
>> To: openstack-dev; mord...@inaugust.com
>> Subject: [openstack-dev][tricircle]your proposal for the name of
>> networking and gateway sub-projects
>>
>> Hello,
>>
>> If we want to divide Tricircle into two sub-projects, your proposals for
>> the name of sub-projects are welcome.
>>
>> Because the Tricircle is applying big-tent application, and the networking
>> part will be remained in the Tricircle repository, and continue the big-tent
>> application. So if we change the networking sub-project name from
>> "Tricircle" to another one, we have to update a lots of places: from infra,
>> to source code, to documentation, google docs, to wiki, etc, it's a huge
>> work, and history background will also be lost, from this point of view, I
>> proposal to remain current Tricircle repository name, but shrink the
>> Tricircle scope to cross Neutron networking automation.
>>
>> And for gateway part, a new repository is required, new project name is
>> more applicable, this is just my thoughts, would like to know your
>> proposals.
>>
>> Best Regards
>> Chaoyi Huang(joehuang)
>>
>> 
>> From: joehuang
>> Sent: 01 September 2016 9:02
>> To: Monty Taylor; openstack-dev
>> Subject: RE: [openstack-dev][tricircle]How to address TCs concerns in
>> Tricircle big-tent application
>>
>> Hello, Monty,
>>
>> Thank you very much for your guide and encouragement, then let's move on
>> this direction.
>>
>> Best regards
>> Chaoyi Huang (joehuang)
>> 
>> From: Monty Taylor [mord...@inaugust.com]
>> Sent: 01 September 2016 0:37
>> To: joehuang; openstack-dev
>> Subject: Re: [openstack-dev][tricircle]How to address TCs concerns in
>> Tricircle big-tent application
>>
>> On 08/31/2016 02:16 AM, joehuang wrote:
>> > Hello, team,
>> >
>> > During last weekly meeting, we discussed how to address TCs concerns in
>> > Tricircle big-tent application. After the weekly meeting, the proposal
>> > was co-prepared by our
>> > contributors:
>> > https://docs.google.com/presentation/d/1kpVo5rsL6p_rq9TvkuczjommJSsisDiKJiurbhaQg7E
>> >
>> > The more doable way is to divide Tricircle into two independent and
>> > decoupled projects, only one of the projects which deal with networking
>> > automation will try to become an big-tent project, And Nova/Cinder
>> > API-GW will be removed from the scope of big-tent project application,
>> > and put them into another project:
>> >
>> > *TricircleNetworking:* Dedicated for cross Neutron networking automation
>> > in multi-region OpenStack deployment, run without or with
>> > TricircleGateway. Try to become big-tent project in the current
>> > application of https://review.openstack.org/#/c/338796/.
>>
>> Great idea.
>>
>> > *TricircleGateway:* Dedicated to provide API gateway for tho

Re: [openstack-dev] [tricircle]your proposal for the name of networking and gateway sub-projects

[Vega Cai]

+1 for Triangel

On 2 September 2016 at 17:34, joehuang <joehu...@huawei.com> wrote:

> After the discussion in the #openstack-tricircle channel, 3 candidates
> available now, please vote the name for the new sub-project for api-gateway
> functionality:
>
> 1. Triangel
> The Triangel are dolls that bring luck
> 2. Tridonut
> Three Donuts. Delicious food, often buy 3 get 1 free.
> 3. Trifennel
> Three Fennel. Fennel is highly prized for its licorice-like flavor and
> the myriad of health benefits it provides
>
> Best Regards
> Chaoyi Huang(joehuang)
>
>
> *From:* joehuang
> *Sent:* 02 September 2016 11:19
> *To:* openstack-dev; mord...@inaugust.com
> *Subject:* RE: [openstack-dev][tricircle]your proposal for the name of
> networking and gateway sub-projects
>
> I have some rough ideas about the name of gateway sub-project, for
> example, triangle, tridonut, tricookie etc, so that we can see that
> Tricircle and the new sub-project are like sibling in OpenStack. And they
> often will be listed closely in order.
>
> Your thoughts?
>
> Best Regards
> Chaoyi Huang(joehuang)
>
> --
> *From:* joehuang
> *Sent:* 02 September 2016 10:22
> *To:* openstack-dev; mord...@inaugust.com
> *Subject:* [openstack-dev][tricircle]your proposal for the name of
> networking and gateway sub-projects
>
> Hello,
>
> If we want to divide Tricircle into two sub-projects, your proposals for
> the name of sub-projects are welcome.
>
> Because the Tricircle is applying big-tent application, and the networking
> part will be remained in the Tricircle repository, and continue the
> big-tent application. So if we change the networking sub-project name from
> "Tricircle" to another one, we have to update a lots of places: from infra,
> to source code, to documentation, google docs, to wiki, etc, it's a huge
> work, and history background will also be lost, from this point of view, I
> proposal to remain current Tricircle repository name, but shrink the
> Tricircle scope to cross Neutron networking automation.
>
> And for gateway part, a new repository is required, new project name is
> more applicable, this is just my thoughts, would like to know your
> proposals.
>
> Best Regards
> Chaoyi Huang(joehuang)
>
> 
> From: joehuang
> Sent: 01 September 2016 9:02
> To: Monty Taylor; openstack-dev
> Subject: RE: [openstack-dev][tricircle]How to address TCs concerns in
> Tricircle big-tent application
>
> Hello, Monty,
>
> Thank you very much for your guide and encouragement, then let's move on
> this direction.
>
> Best regards
> Chaoyi Huang (joehuang)
> 
> From: Monty Taylor [mord...@inaugust.com]
> Sent: 01 September 2016 0:37
> To: joehuang; openstack-dev
> Subject: Re: [openstack-dev][tricircle]How to address TCs concerns in
> Tricircle big-tent application
>
> On 08/31/2016 02:16 AM, joehuang wrote:
> > Hello, team,
> >
> > During last weekly meeting, we discussed how to address TCs concerns in
> > Tricircle big-tent application. After the weekly meeting, the proposal
> > was co-prepared by our
> > contributors: https://docs.google.com/presentation/d/1kpVo5rsL6p_
> rq9TvkuczjommJSsisDiKJiurbhaQg7E
> >
> > The more doable way is to divide Tricircle into two independent and
> > decoupled projects, only one of the projects which deal with networking
> > automation will try to become an big-tent project, And Nova/Cinder
> > API-GW will be removed from the scope of big-tent project application,
> > and put them into another project:
> >
> > *TricircleNetworking:* Dedicated for cross Neutron networking automation
> > in multi-region OpenStack deployment, run without or with
> > TricircleGateway. Try to become big-tent project in the current
> > application of https://review.openstack.org/#/c/338796/.
>
> Great idea.
>
> > *TricircleGateway:* Dedicated to provide API gateway for those who need
> > single Nova/Cinder API endpoint in multi-region OpenStack deployment,
> > run without or with TricircleNetworking. Live as non-big-tent,
> > non-offical-openstack project, just like Tricircle toady’s status. And
> > not pursue big-tent only if the consensus can be achieved in OpenStack
> > community, including Arch WG and TCs, then decide how to get it on board
> > in OpenStack. A new repository is needed to be applied for this project.
> >
> >
> > And consider to remove some overlapping implementation in Nova/Cinder
> > API-GW for global objects like flavor, volume type, we can configure one
&g

Re: [openstack-dev] [tricircle]your proposal for the name of networking and gateway sub-projects

[joehuang]

After the discussion in the #openstack-tricircle channel, 3 candidates 
available now, please vote the name for the new sub-project for api-gateway 
functionality:

1. Triangel
The Triangel are dolls that bring luck
2. Tridonut
Three Donuts. Delicious food, often buy 3 get 1 free.
3. Trifennel
Three Fennel. Fennel is highly prized for its licorice-like flavor and the 
myriad of health benefits it provides

Best Regards
Chaoyi Huang(joehuang)


From: joehuang
Sent: 02 September 2016 11:19
To: openstack-dev; mord...@inaugust.com
Subject: RE: [openstack-dev][tricircle]your proposal for the name of networking 
and gateway sub-projects

I have some rough ideas about the name of gateway sub-project, for example, 
triangle, tridonut, tricookie etc, so that we can see that Tricircle and the 
new sub-project are like sibling in OpenStack. And they often will be listed 
closely in order.

Your thoughts?

Best Regards
Chaoyi Huang(joehuang)


From: joehuang
Sent: 02 September 2016 10:22
To: openstack-dev; mord...@inaugust.com
Subject: [openstack-dev][tricircle]your proposal for the name of networking and 
gateway sub-projects

Hello,

If we want to divide Tricircle into two sub-projects, your proposals for the 
name of sub-projects are welcome.

Because the Tricircle is applying big-tent application, and the networking part 
will be remained in the Tricircle repository, and continue the big-tent 
application. So if we change the networking sub-project name from "Tricircle" 
to another one, we have to update a lots of places: from infra, to source code, 
to documentation, google docs, to wiki, etc, it's a huge work, and history 
background will also be lost, from this point of view, I proposal to remain 
current Tricircle repository name, but shrink the Tricircle scope to cross 
Neutron networking automation.

And for gateway part, a new repository is required, new project name is more 
applicable, this is just my thoughts, would like to know your proposals.

Best Regards
Chaoyi Huang(joehuang)


From: joehuang
Sent: 01 September 2016 9:02
To: Monty Taylor; openstack-dev
Subject: RE: [openstack-dev][tricircle]How to address TCs concerns in Tricircle 
big-tent application

Hello, Monty,

Thank you very much for your guide and encouragement, then let's move on this 
direction.

Best regards
Chaoyi Huang (joehuang)

From: Monty Taylor [mord...@inaugust.com]
Sent: 01 September 2016 0:37
To: joehuang; openstack-dev
Subject: Re: [openstack-dev][tricircle]How to address TCs concerns in Tricircle 
big-tent application

On 08/31/2016 02:16 AM, joehuang wrote:
> Hello, team,
>
> During last weekly meeting, we discussed how to address TCs concerns in
> Tricircle big-tent application. After the weekly meeting, the proposal
> was co-prepared by our
> contributors: 
> https://docs.google.com/presentation/d/1kpVo5rsL6p_rq9TvkuczjommJSsisDiKJiurbhaQg7E
>
> The more doable way is to divide Tricircle into two independent and
> decoupled projects, only one of the projects which deal with networking
> automation will try to become an big-tent project, And Nova/Cinder
> API-GW will be removed from the scope of big-tent project application,
> and put them into another project:
>
> *TricircleNetworking:* Dedicated for cross Neutron networking automation
> in multi-region OpenStack deployment, run without or with
> TricircleGateway. Try to become big-tent project in the current
> application of https://review.openstack.org/#/c/338796/.

Great idea.

> *TricircleGateway:* Dedicated to provide API gateway for those who need
> single Nova/Cinder API endpoint in multi-region OpenStack deployment,
> run without or with TricircleNetworking. Live as non-big-tent,
> non-offical-openstack project, just like Tricircle toady’s status. And
> not pursue big-tent only if the consensus can be achieved in OpenStack
> community, including Arch WG and TCs, then decide how to get it on board
> in OpenStack. A new repository is needed to be applied for this project.
>
>
> And consider to remove some overlapping implementation in Nova/Cinder
> API-GW for global objects like flavor, volume type, we can configure one
> region as master region, all global objects like flavor, volume type,
> server group, etc will be managed in the master Nova/Cinder service. In
> Nova API-GW/Cinder API-GW, all requests for these global objects will be
> forwarded to the master Nova/Cinder, then to get rid of any API
> overlapping-implementation.
>
> More information, you can refer to the proposal draft
> https://docs.google.com/presentation/d/1kpVo5rsL6p_rq9TvkuczjommJSsisDiKJiurbhaQg7E,
>
> your thoughts are welcome, and let's have more discussion in this weekly
> meeting.

I think this is a great approach Joe.

_

Re: [openstack-dev] [tricircle]your proposal for the name of networking and gateway sub-projects

[joehuang]

we are discussing the name in the #openstack-tricircle channel, if you are 
interested in naming a new project, please join. After name is decided, we can 
start to create regarding folder, launchpad, etc..., then divide Tricircle 
project.

Best Regards
Chaoyi Huang(joehuang)

From: joehuang
Sent: 02 September 2016 11:19
To: openstack-dev; mord...@inaugust.com
Subject: RE: [openstack-dev][tricircle]your proposal for the name of networking 
and gateway sub-projects

I have some rough ideas about the name of gateway sub-project, for example, 
triangle, tridonut, tricookie etc, so that we can see that Tricircle and the 
new sub-project are like sibling in OpenStack. And they often will be listed 
closely in order.

Your thoughts?

Best Regards
Chaoyi Huang(joehuang)


From: joehuang
Sent: 02 September 2016 10:22
To: openstack-dev; mord...@inaugust.com
Subject: [openstack-dev][tricircle]your proposal for the name of networking and 
gateway sub-projects

Hello,

If we want to divide Tricircle into two sub-projects, your proposals for the 
name of sub-projects are welcome.

Because the Tricircle is applying big-tent application, and the networking part 
will be remained in the Tricircle repository, and continue the big-tent 
application. So if we change the networking sub-project name from "Tricircle" 
to another one, we have to update a lots of places: from infra, to source code, 
to documentation, google docs, to wiki, etc, it's a huge work, and history 
background will also be lost, from this point of view, I proposal to remain 
current Tricircle repository name, but shrink the Tricircle scope to cross 
Neutron networking automation.

And for gateway part, a new repository is required, new project name is more 
applicable, this is just my thoughts, would like to know your proposals.

Best Regards
Chaoyi Huang(joehuang)


From: joehuang
Sent: 01 September 2016 9:02
To: Monty Taylor; openstack-dev
Subject: RE: [openstack-dev][tricircle]How to address TCs concerns in Tricircle 
big-tent application

Hello, Monty,

Thank you very much for your guide and encouragement, then let's move on this 
direction.

Best regards
Chaoyi Huang (joehuang)

From: Monty Taylor [mord...@inaugust.com]
Sent: 01 September 2016 0:37
To: joehuang; openstack-dev
Subject: Re: [openstack-dev][tricircle]How to address TCs concerns in Tricircle 
big-tent application

On 08/31/2016 02:16 AM, joehuang wrote:
> Hello, team,
>
> During last weekly meeting, we discussed how to address TCs concerns in
> Tricircle big-tent application. After the weekly meeting, the proposal
> was co-prepared by our
> contributors: 
> https://docs.google.com/presentation/d/1kpVo5rsL6p_rq9TvkuczjommJSsisDiKJiurbhaQg7E
>
> The more doable way is to divide Tricircle into two independent and
> decoupled projects, only one of the projects which deal with networking
> automation will try to become an big-tent project, And Nova/Cinder
> API-GW will be removed from the scope of big-tent project application,
> and put them into another project:
>
> *TricircleNetworking:* Dedicated for cross Neutron networking automation
> in multi-region OpenStack deployment, run without or with
> TricircleGateway. Try to become big-tent project in the current
> application of https://review.openstack.org/#/c/338796/.

Great idea.

> *TricircleGateway:* Dedicated to provide API gateway for those who need
> single Nova/Cinder API endpoint in multi-region OpenStack deployment,
> run without or with TricircleNetworking. Live as non-big-tent,
> non-offical-openstack project, just like Tricircle toady’s status. And
> not pursue big-tent only if the consensus can be achieved in OpenStack
> community, including Arch WG and TCs, then decide how to get it on board
> in OpenStack. A new repository is needed to be applied for this project.
>
>
> And consider to remove some overlapping implementation in Nova/Cinder
> API-GW for global objects like flavor, volume type, we can configure one
> region as master region, all global objects like flavor, volume type,
> server group, etc will be managed in the master Nova/Cinder service. In
> Nova API-GW/Cinder API-GW, all requests for these global objects will be
> forwarded to the master Nova/Cinder, then to get rid of any API
> overlapping-implementation.
>
> More information, you can refer to the proposal draft
> https://docs.google.com/presentation/d/1kpVo5rsL6p_rq9TvkuczjommJSsisDiKJiurbhaQg7E,
>
> your thoughts are welcome, and let's have more discussion in this weekly
> meeting.

I think this is a great approach Joe.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]your proposal for the name of networking and gateway sub-projects

[joehuang]

I have some rough ideas about the name of gateway sub-project, for example, 
triangle, tridonut, tricookie etc, so that we can see that Tricircle and the 
new sub-project are like sibling in OpenStack. And they often will be listed 
closely in order.

Your thoughts?

Best Regards
Chaoyi Huang(joehuang)


From: joehuang
Sent: 02 September 2016 10:22
To: openstack-dev; mord...@inaugust.com
Subject: [openstack-dev][tricircle]your proposal for the name of networking and 
gateway sub-projects

Hello,

If we want to divide Tricircle into two sub-projects, your proposals for the 
name of sub-projects are welcome.

Because the Tricircle is applying big-tent application, and the networking part 
will be remained in the Tricircle repository, and continue the big-tent 
application. So if we change the networking sub-project name from "Tricircle" 
to another one, we have to update a lots of places: from infra, to source code, 
to documentation, google docs, to wiki, etc, it's a huge work, and history 
background will also be lost, from this point of view, I proposal to remain 
current Tricircle repository name, but shrink the Tricircle scope to cross 
Neutron networking automation.

And for gateway part, a new repository is required, new project name is more 
applicable, this is just my thoughts, would like to know your proposals.

Best Regards
Chaoyi Huang(joehuang)


From: joehuang
Sent: 01 September 2016 9:02
To: Monty Taylor; openstack-dev
Subject: RE: [openstack-dev][tricircle]How to address TCs concerns in Tricircle 
big-tent application

Hello, Monty,

Thank you very much for your guide and encouragement, then let's move on this 
direction.

Best regards
Chaoyi Huang (joehuang)

From: Monty Taylor [mord...@inaugust.com]
Sent: 01 September 2016 0:37
To: joehuang; openstack-dev
Subject: Re: [openstack-dev][tricircle]How to address TCs concerns in Tricircle 
big-tent application

On 08/31/2016 02:16 AM, joehuang wrote:
> Hello, team,
>
> During last weekly meeting, we discussed how to address TCs concerns in
> Tricircle big-tent application. After the weekly meeting, the proposal
> was co-prepared by our
> contributors: 
> https://docs.google.com/presentation/d/1kpVo5rsL6p_rq9TvkuczjommJSsisDiKJiurbhaQg7E
>
> The more doable way is to divide Tricircle into two independent and
> decoupled projects, only one of the projects which deal with networking
> automation will try to become an big-tent project, And Nova/Cinder
> API-GW will be removed from the scope of big-tent project application,
> and put them into another project:
>
> *TricircleNetworking:* Dedicated for cross Neutron networking automation
> in multi-region OpenStack deployment, run without or with
> TricircleGateway. Try to become big-tent project in the current
> application of https://review.openstack.org/#/c/338796/.

Great idea.

> *TricircleGateway:* Dedicated to provide API gateway for those who need
> single Nova/Cinder API endpoint in multi-region OpenStack deployment,
> run without or with TricircleNetworking. Live as non-big-tent,
> non-offical-openstack project, just like Tricircle toady’s status. And
> not pursue big-tent only if the consensus can be achieved in OpenStack
> community, including Arch WG and TCs, then decide how to get it on board
> in OpenStack. A new repository is needed to be applied for this project.
>
>
> And consider to remove some overlapping implementation in Nova/Cinder
> API-GW for global objects like flavor, volume type, we can configure one
> region as master region, all global objects like flavor, volume type,
> server group, etc will be managed in the master Nova/Cinder service. In
> Nova API-GW/Cinder API-GW, all requests for these global objects will be
> forwarded to the master Nova/Cinder, then to get rid of any API
> overlapping-implementation.
>
> More information, you can refer to the proposal draft
> https://docs.google.com/presentation/d/1kpVo5rsL6p_rq9TvkuczjommJSsisDiKJiurbhaQg7E,
>
> your thoughts are welcome, and let's have more discussion in this weekly
> meeting.

I think this is a great approach Joe.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]How to address TCs concerns in Tricircle big-tent application

[joehuang]

Hello, Monty,

Thank you very much for your guide and encouragement, then let's move on this 
direction.

Best regards
Chaoyi Huang (joehuang)

From: Monty Taylor [mord...@inaugust.com]
Sent: 01 September 2016 0:37
To: joehuang; openstack-dev
Subject: Re: [openstack-dev][tricircle]How to address TCs concerns in Tricircle 
big-tent application

On 08/31/2016 02:16 AM, joehuang wrote:
> Hello, team,
>
> During last weekly meeting, we discussed how to address TCs concerns in
> Tricircle big-tent application. After the weekly meeting, the proposal
> was co-prepared by our
> contributors: 
> https://docs.google.com/presentation/d/1kpVo5rsL6p_rq9TvkuczjommJSsisDiKJiurbhaQg7E
>
> The more doable way is to divide Tricircle into two independent and
> decoupled projects, only one of the projects which deal with networking
> automation will try to become an big-tent project, And Nova/Cinder
> API-GW will be removed from the scope of big-tent project application,
> and put them into another project:
>
> *TricircleNetworking:* Dedicated for cross Neutron networking automation
> in multi-region OpenStack deployment, run without or with
> TricircleGateway. Try to become big-tent project in the current
> application of https://review.openstack.org/#/c/338796/.

Great idea.

> *TricircleGateway:* Dedicated to provide API gateway for those who need
> single Nova/Cinder API endpoint in multi-region OpenStack deployment,
> run without or with TricircleNetworking. Live as non-big-tent,
> non-offical-openstack project, just like Tricircle toady’s status. And
> not pursue big-tent only if the consensus can be achieved in OpenStack
> community, including Arch WG and TCs, then decide how to get it on board
> in OpenStack. A new repository is needed to be applied for this project.
>
>
> And consider to remove some overlapping implementation in Nova/Cinder
> API-GW for global objects like flavor, volume type, we can configure one
> region as master region, all global objects like flavor, volume type,
> server group, etc will be managed in the master Nova/Cinder service. In
> Nova API-GW/Cinder API-GW, all requests for these global objects will be
> forwarded to the master Nova/Cinder, then to get rid of any API
> overlapping-implementation.
>
> More information, you can refer to the proposal draft
> https://docs.google.com/presentation/d/1kpVo5rsL6p_rq9TvkuczjommJSsisDiKJiurbhaQg7E,
>
> your thoughts are welcome, and let's have more discussion in this weekly
> meeting.

I think this is a great approach Joe.


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev