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

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

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

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

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

+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

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

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

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

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

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

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

[openstack-dev] [tricircle] Tricircle or Trio2o

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

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

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: >

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

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,

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

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

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

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

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

+1. Best regards, Yipei __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

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

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 te

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

+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

[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

[openstack-dev] [tricircle] Rocky Tricircle PTL candidacy

Hi folks, I would like to announce my self nomination for the PTL candidacy in Tricircle Rocky cycle. My name is Zhiyuan Cai, and my IRC handle is zhiyuan. I am currently the PTL of Tricircle for Queens cycle and have been actively participating in the development of this project since Mitaka

[openstack-dev] [tricircle] No Tricircle meeting tomorrow

Hi, Tomorrow I will attend the bug smash in Wuhan so I will not be able to chair the weekly meeting. We will resume the meeting next week. BR Zhiyuan -- BR Zhiyuan __ OpenStack Development Mailing List (not for usage

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

; *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 > betw

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

y 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

[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

[openstack-dev] [tricircle] PTG summary

Hello folks, After the discussion in the PTG on last Friday, we plan the following work items for the Queens circle: queens-1 LBaaS Integration with Nova cell V2 Distinguish request from user and local neutron server Default security group update queens-2 Network deletion reliability Security

[openstack-dev] [tricircle] [ptg] PTG reminder

Hello folks, Just to remind that the PTG of Tricircle team will be held on Sep 15th, from 9:00 am to 17:00 pm(UTC+8). We will discuss our topics in this etherpad page[1] and #openstack-tricircle channel, so you can join the discussion via etherpad and IRC. Also, please feel free to add topic to

[openstack-dev] [tricircle] Tricircle PTG plan

Hello folks, As discussed in our weekly meeting, since most of our developers are in China, we will hold a small scale team gathering in China. Please refer to this etherpad page[1] for the date and place of the gathering. During the gathering, we will discuss our topics in that etherpad page and

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

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

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

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

[openstack-dev] [tricircle]stable/pike brach has been created.

Hello, all, Thank you all for the great contribution, stable/pike has been created on Aug.18: https://git.openstack.org/cgit/openstack/tricircle/log/?h=stable/pike Release notes could be found here: https://docs.openstack.org/releasenotes/tricircle/pike.html Best Regards Chaoyi Huang

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

stance, 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 > *主题:*[opens

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

...@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 Pro

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

ubject: Re: [openstack-dev] [tricircle-Service Function Chaining] Message-ID:

[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

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

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

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

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

[openstack-dev] [tricircle]pike-3 released

Hello, Tricircle 3.4.0 (pike-3) released[1], it's time to do regression test and fix bugs, next milestone is pike-rc. [1]https://review.openstack.org/#/c/488904/ Best Regards Chaoyi Huang (joehuang) __ OpenStack

[openstack-dev] [Tricircle] Queens PTL candidacy

Hi all, I would like to announce my self nomination for the PTL candidacy in Tricircle Queens cycle. My name is Zhiyuan Cai, and my IRC handle is zhiyuan. As a core reviewer of Tricircle project, I have been actively participating in the development of this project since Mitaka cycle. During the

Re: [openstack-dev] [tricircle]

rget=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> De : HIHI Meher IMT/OLN Envoyé : lundi 31 juillet 2017 15:32 À : 'openstack-dev@lists.openstack.org' Objet : [o

Re: [openstack-dev] [tricircle]

) 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

[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

Re: [openstack-dev] [tricircle]

uot;openstack-dev@lists.openstack.org" <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"

[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

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

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

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

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

Re: [openstack-dev] [tricircle]

Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33758386887> > meher.h...@orange.com > > > > > > *De :* HIHI Meher IMT/OLN > *Envoyé :* mercredi 28 juin 2017 15:12 > *À :* 'openstack-dev@lists.open

Re: [openstack-dev] [tricircle]

V2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33758386887> meher.h...@orange.com<mailto: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

Re: [openstack-dev] [tricircle]

...@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

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:

[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

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

); 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

[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

[openstack-dev] [tricircle]weekly meeting of Jun.28

Hello, team, Agenda of Jun.28 weekly meeting: 1. feature implementation review 2. Community wide goals, PTG and Sydney summit topics 3. Open Discussion How to join: # IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 1:00.

[openstack-dev] [tricircle]weekly meeting of Jun.21

Hello, team, Agenda of Jun.21 weekly meeting: 1. summary of tricircle demo in OPNFV summit 3. feature implementation review 4. Open Discussion How to join: # IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 1:00. Best

[openstack-dev] [tricircle]weekly meeting of Jun.21

Hello, team, Agenda of Jun.20 weekly meeting: 1. summary of tricircle demo in OPNFV summit 3. feature implementation review 4. Open Discussion How to join: # IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 1:00. Best

[openstack-dev] [tricircle]weekly meeting of May.24

Hello, team, Agenda of May.24 weekly meeting: 1. feature implementation review 2. Pike-2 preparation 3. Open Discussion How to join: # IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 01:00. If you have other topics to be

[openstack-dev] [tricircle]cancellation of weekly meeting(May 17) due to bug smash

Hello, team, The bug smash will be held May.17~19, the weekly meeting of May. 17 will be cancelled. Best Regards Chaoyi Huang (joehuang) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [tricircle]weekly meeting of May.3

Hello, team, Please note the new weekly meeting time is UTC 01:00, Wednesday. Agenda of May.3 weekly meeting: 1. feature implementation review 2. Pike-1.5 (May.2) review 3. Open Discussion How to join: # IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every

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

il 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

[openstack-dev] [tricircle]weekly meeting APR.26

Hello, According to the plan, we'd like to release pike-1.5 on May.2, the priorities of these patches are as follows: MUST to have(Should be merged before the end of this week): * Release note and doc for multi-gw NS networking, https://review.openstack.org/#/c/458786/ * Add guide for

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

(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

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

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

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

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

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

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

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

[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

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

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

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

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

[openstack-dev] [tricircle]weekly meeting of Apr.19

Hello, team, Agenda of Apr.19 weekly meeting: 1. feature implementation review 2. weekly meeting time 3. Pike-1.5 (May.2) preparation 4. Open Discussion How to join: # IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 14:00.

[openstack-dev] [tricircle]weekly meeting of Apr.12

Hello, team, Agenda of Apr.12 weekly meeting: 1. feature implementation review 2. Pike-1.5 (May.2) preparation 3. Open Discussion How to join: # IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 14:00. If you have other

[openstack-dev] [tricircle]weekly meeting of Apr.5

Hello, team, Agenda of Apr.5 weekly meeting: 1. feature implementation review 2. Pike-2 planning 3. Open Discussion How to join: # IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 14:00. If you have other topics to be

[openstack-dev] [tricircle]weekly meeting of Mar. 29

Hello, team, Agenda of Mar.29 weekly meeting: 1. Pike-1 prioritized patches 2. Requirements from VNF high availability across OpenStack (which will be a demo in OPNFV Beijing Summit) 3. Open Discussion How to join: # IRC meeting:

[openstack-dev] [tricircle]pike-1 patch prioritization

Hello, As we discussed in last weekly meeting, pike-1 is expected to be tagged by the end of this month, Mar.31. These patches are must to have in pike-1: 1. Add multi-region configuration in gate_hook.sh: https://review.openstack.org/#/c/438382/ 2.

[openstack-dev] [tricircle]weekly meeting of Mar. 22

Hello, team, Agenda of Mar.22 weekly meeting: 1. Pike-1 patches review 2. Pike-1 release 3. Demo and talk of VNF high availability across OpenStack with Tricircle in OPNFV Beijing summit 4. Open Discussion How to join: # IRC meeting:

[openstack-dev] [tricircle]weekly meeting of Mar. 15

Hello, team, New weekly meeting time slot is UTC 14:00~UTC 15:00 Agenda of Mar.15 weekly meeting: 1. Test coverage requirement : https://review.openstack.org/#/c/444394/ 2. Demo of VNF high availability across OpenStack with Tricircle in OPNFV Beijing summit 3. Pike-1 prioritized

[openstack-dev] [tricircle]weekly meeting of Mar. 8

Hello, team, Attention please, the new weekly meeting time slot is UTC 14:00~UTC 15:00 Agenda of Mar.8 weekly meeting: 1. Pike-1 feature priority discussion 2. Pike features development 3. Open Discussion How to join: # IRC meeting:

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

...@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

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

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

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

+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

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

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. Vict

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

+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

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

: [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

[openstack-dev] [tricircle]weekly meeting of Mar. 1

Hello, team, Before the new weekly meeting is settled, we'll still hold the weekly meeting in regular time slot: UTC 13:00~UTC 14:00 Agenda of Mar. 1 weekly meeting: 1. Pike release schedule: https://releases.openstack.org/pike/schedule.html 2. Launch pad blueprint registration and spec

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

+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

; 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

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

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

nstack.org> > Date: Tuesday, February 28, 2017 at 8:38 PM > To: openstack-dev <openstack-dev@lists.openstack.org> > Subject: [openstack-dev] [tricircle]Nominating Victor Morales as > Tricircle Core > > Hi Team, > > Victor Morales has made many review contrib

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

It's wonderful for Victor Morales to be Tricircle core. Thanks for his great contribution. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

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

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,

[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

[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

[openstack-dev] [tricircle]weekly meeting of Feb.22

Hello, team, Let's resume weekly meeting after Ocata 3.0.0 released. Agenda of Feb. 22 weekly meeting: 1. Pike features development 2. Open Discussion How to join: # IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 13:00. If

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

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, > >

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

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:

[openstack-dev] [tricircle]Ocata released and Pike meetup

Hello, Thanks for your great contribution, Tricircle 3.0.0 (Ocata release) has been released after the patch[1] was approved, the release notes could be found at [2]. A meetup for Pike will be held: Feb.17, UTC 1:00~8:00( UTC+8: 9:00 am~4:00 pm), Block G, Huawei Industrial Base, Shenzhen.

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

: [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

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

ot;OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> 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 proce

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

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].

[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

[openstack-dev] [tricircle]no weekly meeting Feb.15

Hello, team, Due to the preparation for the Ocata release and meetup on Feb.17, there is no weekly meeting Feb.15. Let's meet on Friday, and for those who will attend Atlanta PTG, you can have a F2F talk with Zhiyuan, he is the representative of Tricircle team. Best Regards Chaoyi Huang

[openstack-dev] [Tricircle] Heading for PTG

Hi folks, I am heading for Atlanta PTG as the representative of Tricircle project, if you are interested in Tricircle project and will also attend Atlanta PTG, we can meet and discuss some topics there. BR Zhiyuan -- BR Zhiyuan

[openstack-dev] [tricircle]schedule for Ocata release and Pike meetup/PTG

Hello,team, Thanks for your great contribution, the Ocata cycle is almost done. As what we discussed in weekly meeting, the schedule for Ocata release and Pike meetup/PTG as follows: 1.Ocata branch this Friday or early 2. Regression test until Feb.15 3. Ocata release Feb.16 4. Pike meetup

[openstack-dev] [tricircle]weekly meeting of Feb. 8

Hello, team, Let's resume weekly meeting after breaks for Chinese New Year. Agenda of Feb. 8 weekly meeting: 1. Ocata release dates 2. Pike meetup before PTG: https://etherpad.openstack.org/p/tricircle-pike-design-topics 3. Representative and topics to PTG 4. Open Discussion How

  1   2   3   4   5   6   >