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

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

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

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

Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tricircle]How to address TCs concerns in Tricircle big-tent application If you're going with the approach of having a master region (which seems sensible), you're going to want an admin API that checks all of the regions setup

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

zjommJSsisDiKJiurbhaQg7E, > your thoughts are welcome, and let's have more discussion in this weekly > meeting. > > Best Regards > Chaoyi Huang(joehuang) > > *From:* joehuang > *Sent:* 24 August 2016 16:35 > *To:* openstack-dev > *Subject:* [openstack-dev][tricircle]age

[openstack-dev] [tricircle]agenda of weekly meeting Aug.31

the mail. Best Regards Chaoyi Huang ( joehuang ) From: joehuang Sent: 24 August 2016 16:35 To: openstack-dev Subject: [openstack-dev][tricircle]agenda of weekly meeting Aug.24 Hello, team, Agenda of Aug.24 weekly meeting: # progress review and concerns

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

August 2016 16:35 To: openstack-dev Subject: [openstack-dev][tricircle]agenda of weekly meeting Aug.24 Hello, team, Agenda of Aug.24 weekly meeting: # progress review and concerns on the features like micro versions, policy control, dynamic pod binding, cross pod L2 networking # How to address

[openstack-dev] [tricircle]agenda of weekly meeting Aug.24

Hello, team, Agenda of Aug.24 weekly meeting: # progress review and concerns on the features like micro versions, policy control, dynamic pod binding, cross pod L2 networking # How to address TCs concerns in Tricircle big-tent application # open discussion How to join: # IRC meeting:

[openstack-dev] [tricircle]agenda of weekly meeting Aug.17

Hello, team, Great movement, more and more patches coming in the review queue https://review.openstack.org/#/q/project:openstack/tricircle. Let's continue the discussion. Agenda: # progress review and concerns on the features like micro versions, policy control, dynamic pod binding,

[openstack-dev] [tricircle]agenda of weekly meeting Aug.10

Hello, team, Cross pod L2 networking(shared VLAN) has made good progress, let's continue the discussion: IRC meeting: https://webchat.freenode.net/?channels=openstack-meetingon every Wednesday starting from UTC 13:00. The agenda of this weekly meeting is: # progress review in feature

[openstack-dev] [tricircle]agenda of weekly meeting Aug.3

Hi, team, IRC meeting: https://webchat.freenode.net/?channels=openstack-meetingon every Wednesday starting from UTC 13:00. The agenda of this weekly meeting is: # progress review in feature parity, cross pod L2 networking, dynamic pod binding:

[openstack-dev] [tricircle]agenda of weekly meeting Jul.27

Hi, team, IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 13:00. There are two rounds of discussion in TC weekly meeting for Tricircle big-tent application, so let's discuss on this: The agenda of this weekly meeting is: #

Re: [openstack-dev] [tricircle] A new contributor

Hi, team, Welcome Xiulin to join the team. Best Regards Chaoyi Huang ( joehuang ) From: Shinobu Kinjo [shinobu...@gmail.com] Sent: 20 July 2016 15:49 To: OpenStack Development Mailing List (not for usage questions) Cc: yinxiulin Subject: [openstack-dev

[openstack-dev] [tricircle] A new contributor

Hi Team, Please welcome a new contributor (CCed) for the Tricircle project. Cheers, Shinobu -- Email: shin...@linux.com shin...@redhat.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [tricircle]agenda of weekly meeting Jul.20

Hi, team, IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 13:00. The agenda of this weekly meeting is: # microversion support # Tricircle API feature paity planning: *

Re: [openstack-dev] [tricircle]Mascot/logo for Tricircle

On Mon, Jul 18, 2016 at 1:58 PM, Zhipeng Huang wrote: > Mascot does not necessarily need to reflect the team name, although would > definitely be better if it does. > O.k, I am now pretty much wondering - Which is *true* - What is *necessary* and - What are

Re: [openstack-dev] [tricircle]Mascot/logo for Tricircle

Mascot does not necessarily need to reflect the team name, although would definitely be better if it does. We could think outside the box, how about just use panda ? :P BTW Panda has three black circles on the face (eyes and nose) :P http://www.edinburghzoo.org.uk/media/3455/ezpanda.png On Mon,

[openstack-dev] [tricircle]Mascot/logo for Tricircle

Hello, According to the community proposal, let's select the Tricircle mascot too? The project name of "Tricircle" itself is comming from a fractal: https://www.google.com/search?q=tricircle+fractal=2=1366=667=isch=u=univ=X=0ahUKEwiut7_o-PvNAhXBj5QKHd1EB5AQsAQIUw=1 So how do you think

[openstack-dev] [tricircle]cancellation of weekly meeting of Jul.13

Due to flight delay, this weekly meeting of the Tricircle project will be canceled. Sent from HUAWEI AnyOffice 发件人：黄朝意 收件人：openstack-dev, 时间：2016-07-06 14:15:43 主题:[openstack-dev][tricircle]agenda of weekly meeting of Jul.6 Hi, team, IRC meeting: https://webchat.freenode.net/?channels

[openstack-dev] [tricircle]agenda of weekly meeting of Jul.6

Hi, team, IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 13:00. The agenda of this weekly meeting is: # bugs review: https://bugs.launchpad.net/tricircle # bump to Nova 2.1: https://review.openstack.org/#/c/324226/ # L2/L3

Re: [openstack-dev] [tricircle]

# This email is true to reply. Would you attach local.conf you're using? On Mon, Jul 4, 2016 at 4:10 PM, Luck Dog wrote: > Hello everyone, > > I am trying to run DevStack on Ubuntu 14.04 in a single VirtualBox. An > error turns up before it successfully starts. Yesterday I

[openstack-dev] [tricircle]

Hello everyone, I am trying to run DevStack on Ubuntu 14.04 in a single VirtualBox. An error turns up before it successfully starts. Yesterday I clarified this question not clearly enough，so I make a supplication for it. My steps are: 1), Git clone DevStack, 2), Copy devstack/local.conf.sample

Re: [openstack-dev] [tricircle] Error when running Devstack

Hi Dongfeng, I've noted in the title [Tricircle], but in your body mail, nothing related to Tricircle! It's not recommended to use the sample configuration file as it's, make sure that you edit it as per your preferred configuration. Also, note that it's good to run stack.sh as stack user, you

[openstack-dev] [tricircle] Error when running Devstack

Hello everyone, I am trying to run DevStack on Ubuntu 14.04 in a single VirtualBox. An error turns up before it successfully starts. My steps are: 1), Git clone DevStack, 2), Copy devstack/local.conf.sample to DevStack folder and rename it to local.conf. The errors are as follows： Request

[openstack-dev] [tricircle]tricircle wiki update

Hello, team, The wiki page of Tricircle was updated in the architecture and value section, other sections also with minor update Please review and comment, and update accordingly for obvious error. If you have any question and topic to discuss, also let's discussion in the m-l. Thanks Sent

Re: [openstack-dev] [tricircle] About registering and loading a plugin

It may be better to attach setup.cfg you using, and paste traceback (if there). Cheers, Shinobu On Wed, Jun 29, 2016 at 4:57 PM, Yipei Niu wrote: > Hi all, > > I have succeed in registering a config option and obtaining it. So how to > load an option from a customized file?

[openstack-dev] [tricircle]agenda of weekly meeting of Jun.29

Hi, team, After some feature spec patches merged and Mitaka tagging finished, and the feauture development is ongoing, the agenda of this weekly meeting is: IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 13:00. # progress of

Re: [openstack-dev] [tricircle] About registering and loading a plugin

Hi all, I have succeed in registering a config option and obtaining it. So how to load an option from a customized file? Through cfg.CONF(default_config_files=[setup.cfg]? Still fails loading the config options in setup.cfg. Best regards, Yipei On Wed, Jun 29, 2016 at 8:36 AM, joehuang

Re: [openstack-dev] [tricircle] About registering and loading a plugin

Hi, Yipei, "Moreover, I tried to load drivers by line "cfg.CONF.nyp.plugins.simple", the console prompts oslo_config.cfg.NoSuchOptError: no such option in group DEFAULT: nyp. The setup.cfg is defined as follows." You are using entry point but not configuration options for plugin discovery,

Re: [openstack-dev] [tricircle] About registering and loading a plugin

Hi all, Thanks a lot for your valuable advice. I have already succeed in registering and loading a self-defined plugin. The entry_point is generated by executing setup.py, and found in .egg-info/entry_points.txt, which is different from using setup.cfg in https://review.openstack.org/#/c/331638/.

Re: [openstack-dev] [tricircle] About registering and loading a plugin

Hi Yipei, You can also refer to my network type driver implementation: https://review.openstack.org/#/c/331638/ Type driver is registered in setup.cfg and loaded by code. BR Zhiyuan On 27 June 2016 at 21:44, Yipei Niu wrote: > Dear all, > > Recently, I learn to name a

Re: [openstack-dev] [tricircle] About registering and loading a plugin

Hello, Yipei, You can use entry point inspector to check whether there is some error in the plugin registration and loading: sudo pip install entry_point_inspector epi group list epi group show epi ep show https://pypi.python.org/pypi/entry_point_inspector If there is some error

[openstack-dev] [tricircle] About registering and loading a plugin

Dear all, Recently, I learn to name a plugin based on the doc http://docs.openstack.org/developer/stevedore/tutorial/naming.html#. I define a new entry_point for the plugin, then it fails. The console prompts "stevedore.exception.NoMatches: No 'net.nyp.formatter' driver found, looking for

[openstack-dev] [tricircle] Overlay L2 networking across OpenStack slides used in OPNFV summit

Hello, In last week OPNFV summit in Berlin, a presentation was given about "Overlay L2 networking across OpenStack", the slides is for your reference: https://docs.google.com/presentation/d/1Cv23dLAmSB57IpD-nt-TH5lrCehcoeiml7HpvgUWauo/edit#slide=id.g1478638225_0_0 Best Regards Chaoyi Huang (

[openstack-dev] [tricircle]this weekly meeting

Hello, I am on the trip to attend the OPNFV Berlin summit, would like to know if someone can chair the weekly meeting of Tricircle. If no volunteer before Jun. 22, we may have to skip this weekly meeting. Best Regards Chaoyi Huang ( joehuang )

[openstack-dev] [tricircle]Pypi job works, and tagging leads to a package publish

Hello, team, After the pypi job configuration and help from the community, the first package of Tricircle is published automatically after tagging the version 2.0.1 in stable/mitaka branch. https://pypi.python.org/pypi/tricircle The package verified the release publish process, and

[openstack-dev] [tricircle]agenda of weekly meeting of Jun.15

Hi, IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 13:00. Today's agenda: # spec review and status of 'cross pod L2 networking' and 'dynamic pod binding' # integration test in the CI pipeline # policy enforcement for API access If

[openstack-dev] [tricircle] About the specification for dynamic pod binding

Dear Shinobu, I have revised the description of dynamic pod binding and submitted a new patch. Here is the link of the path: https://review.openstack.org/#/c/306224/12. Is the description clear enough to help readers understand the patch. Could you please go through the description and give me

[openstack-dev] [tricircle]agenda of weekly meeting of Jun.8

Hi, IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 13:00. Today's agenda: # spec review and status of 'cross pod L2 networking' and 'dynamic pod binding' # policy enforcement for API access # tempest test integration If you have

[openstack-dev] [tricircle]cherry pick patches to stable/mitaka release

Hello, As the job "publish to PyPI" has been added to the infra pipeline, I suggest to cherry pick the following patches(which has been merged to the master branch) to stable/mitaka branch, then we can make an initial release in stable/mitaka branch, and also to test the release publish

Re: [openstack-dev] [tricircle] reviewed by multiple eyes

) -Original Message- From: Shinobu Kinjo [mailto:shinobu...@gmail.com] Sent: Friday, June 03, 2016 7:28 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [tricircle] reviewed by multiple eyes Hi Team, There are some patch sets reviewed by only myself

[openstack-dev] [tricircle] reviewed by multiple eyes

Hi Team, There are some patch sets reviewed by only myself. >From my point of view, any patch set needs to be reviewed by multiple eyes. It's because anyone is not perfect. And there should be anything missing. Please take a look, if you get notification to review. Cheers, Shinobu -- Email:

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

Hi, IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 13:00. Let's continue the working items: # tempest plugin and test cases # implementation discussion of 'cross pod L2 networking' and 'dynamic pod binding' # bugs review If you have

Re: [openstack-dev] [tricircle] Launch work group for cross-pod L2 networking feature

Hi Team, Reading today's discussion log, I would encourage you to refer to each documentation as much as you can. [1] https://docs.google.com/document/d/18kZZ1snMOCD9IQvUKI5NVDzSASpw-QKj7l2zNqMEd3g/edit#heading=h.fx4zy2u9se10 [2]

Re: [openstack-dev] [tricircle] Launch work group for cross-pod L2 networking feature

Hi members, Thanks for attending the work group meeting. Our discussion log can be viewed here: https://docs.google.com/document/d/15meGv7wL2ClWZMKd4BPN0Q3br-ac2JDmTvFPLOgUHt0/edit?usp=sharing BR Zhiyuan On 24 May 2016 at 09:51, Yipei Niu wrote: > Hi, all, > > Since I have

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

Hi, IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 13:00. Let's continue the working items: # implementation discussion of 'cross pod L2 networking' and 'dynamic pod binding' # bugs review If you have other topics to be discussed in

Re: [openstack-dev] [tricircle] Launch work group for cross-pod L2 networking feature

Hi, all, Since I have to attend the dissertation defense of my master degree on Wednesday morning, I cannot attend the group meeting. Sorry about that. If it is inconvenient to reschedule the meeting, I will keep online in #openstack-tricircle so as to receive the meeting log. Best regards,

[openstack-dev] [tricircle] Launch work group for cross-pod L2 networking feature

Hi members, Sorry that it's a bit late to launch our cross-pod L2 networking work group since I was attending OSCON last week. What about having our first work group meeting on Wednesday 10am(Beijing time UTC+8), in #openstack-tricircle channel? Topics I think we can discuss: (1) feature

Re: [openstack-dev] [tricircle] Cross OpenStac L2 Networking Specification

Hi, Shinobu, Agree with you that we need to complete the spec ASAP but without compromising on quality. Sent from HUAWEI AnyOffice 发件人：shinobu.kj 收件人：openstack-dev, 时间：2016-05-20 14:40:54 主题:[openstack-dev] [tricircle] Cross OpenStac L2 Networking Specification Hi Team, Probably we would

[openstack-dev] [tricircle] Cross OpenStac L2 Networking Specification

Hi Team, Probably we would not be able to make any progress without completing ${subject} which is under review right now. [1] It's because: 1.Blueprint of the Tricircle is almost based on this feature at the moment. 2.Further implementation will be mostly based on this feature. 3.Our

Re: [openstack-dev] [tricircle] Coding style guidelines

ob/master/tricircle/db/core.py > > Best Regards > Chaoyi Huang ( Joe Huang ) > > > -Original Message- > From: Shinobu Kinjo [mailto:shinobu...@gmail.com] > Sent: Friday, May 20, 2016 11:54 AM > To: OpenStack Development Mailing List (not for usage questions) > Su

Re: [openstack-dev] [tricircle] Coding style guidelines

(not for usage questions) Subject: Re: [openstack-dev] [tricircle] Coding style guidelines Hi Zhipeng, Please have a look at the following script. e.g., import orders. ./tricirlce/db/core.py Cheers, Shinobu On Fri, May 20, 2016 at 12:41 PM, Zhipeng Huang <zhipengh...@gmail.com> wrote: > H

Re: [openstack-dev] [tricircle] Coding style guidelines

Hi Zhipeng, Please have a look at the following script. e.g., import orders. ./tricirlce/db/core.py Cheers, Shinobu On Fri, May 20, 2016 at 12:41 PM, Zhipeng Huang wrote: > Hi shinobu, could you provide an example of which part of code need > modification to fit the

Re: [openstack-dev] [tricircle] Coding style guidelines

Hi shinobu, could you provide an example of which part of code need modification to fit the guideline ? On Fri, May 20, 2016 at 11:04 AM, Shinobu Kinjo wrote: > Hi Team, > > Please make sure that your coding style follows OpenStack style > guidelines. [1] > > I understand

[openstack-dev] [tricircle] Coding style guidelines

Hi Team, Please make sure that your coding style follows OpenStack style guidelines. [1] I understand that it's really painful but readability, and maintenanceability point of view, it is very important to follow standard. Working through code bases, some of them do not follow the guidelines.

Re: [openstack-dev] [tricircle]PTL election conclusion

uang ( Joe Huang ) -Original Message- From: Shinobu Kinjo [mailto:shinobu...@gmail.com] Sent: Wednesday, May 18, 2016 6:38 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tricircle]PTL election conclusion Hi Chaoyi, Great! On Wed, May 18, 20

Re: [openstack-dev] [tricircle]PTL election conclusion

t; To: 'OpenStack Development Mailing List (not for usage questions)' > Subject: RE: [openstack-dev][tricircle]PTL election of Tricircle for Newton > release > > Hi, team, > > If you want to be the PTL for Newton release of Tricircle, please send your > self nomination

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

the mail. Best Regards Chaoyi Huang ( Joe Huang ) From: joehuang Sent: Wednesday, May 11, 2016 3:36 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev][tricircle]weekly meeting of May. 11 Hi, IRC meeting: https://webchat.freenode.net/?channels=openstack

[openstack-dev] [tricircle]PTL election conclusion

Subject: RE: [openstack-dev][tricircle]PTL election of Tricircle for Newton release Hi, team, If you want to be the PTL for Newton release of Tricircle, please send your self nomination letter in the mail-list this week. Best Regards Chaoyi Huang ( Joe Huang ) -Original Message- From: j

Re: [openstack-dev] [tricircle] [Blueprint] Stateless design definition

mentioned. Best Regards Chaoyi Huang ( Joe Huang ) -Original Message- From: Shinobu Kinjo [mailto:shinobu...@gmail.com] Sent: Saturday, May 14, 2016 2:37 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [tricircle] [Blueprint] Stateless design

Re: [openstack-dev] [tricircle] [Blueprint] Stateless design definition

Hi Team, Sorry for this spam -; Please ignore previous message. I will file that as a doc bug. Cheers, S On Sat, May 14, 2016 at 3:36 PM, Shinobu Kinjo wrote: > Hi Team, > > In page1, we define "stateless design" as follows: > > Note: Stateless proposal is working on

[openstack-dev] [tricircle] [Blueprint] Stateless design definition

Hi Team, In page1, we define "stateless design" as follows: Note: Stateless proposal is working on the “experiment” branch: https://github.com/openstack/tricircle/tree/experiment But, in section 7, we define this design as follows: A PoC was done to verify the feasibility of stateless

[openstack-dev] [tricircle]PTL Candidacy for Tricircle in Newton release

AM To: 'ski...@redhat.com'; OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev][tricircle]PTL election of Tricircle for Newton release Hello, As discussed in yesterday weekly meeting, PTL nomination period from May 9 ~ May 13, election from May 16 ~ May 20

Re: [openstack-dev] [tricircle] [document] Experimental design

ot; <joehu...@huawei.com> To: ski...@redhat.com, "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Sent: Wednesday, May 11, 2016 5:23:34 PM Subject: RE: [openstack-dev] [tricircle] [document] Experimental design Hi, Shinobu, Do you t

Re: [openstack-dev] [tricircle] [document] Experimental design

(not for usage questions) Subject: [openstack-dev] [tricircle] [document] Experimental design Hi Team, There is a link pointing to old documentation called "The experimental design" in blueprint. [1] Since I would really like to focus on only blueprint, I would like to freeze this old doc

[openstack-dev] [tricircle] [document] Experimental design

Hi Team, There is a link pointing to old documentation called "The experimental design" in blueprint. [1] Since I would really like to focus on only blueprint, I would like to freeze this old documentation. That means that there is no comment expected, and required on that documentation. What

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

Hi, IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 13:00. Agenda: # cross pod L2 networking, Local Network/Shared VLAN network # dynamic pod binding # features required for tempest If you have other topics to be discussed in the

Re: [openstack-dev] [tricircle] About the dynamic pod binding

Hi Yipei, On Tue, May 10, 2016 at 10:59 AM, Yipei Niu wrote: > Hi, all, > > I think I understand how does tricircle schedule pods. Based on the flavor > extra_specs or volume extra_specs tags, tricircle queries the pod table for > the records in which resource_affinity_tag is

Re: [openstack-dev] [tricircle]Welcome Shinobu Kinjo to be the core reviewer of Tricircle

> > From: joehuang > > Sent: Tuesday, May 03, 2016 9:04 PM > > To: OpenStack Development Mailing List (not for usage questions) > > Subject: [openstack-dev][tricircle]Proposing Shinobu Kinjo for Tricircle > core reviewer > > > > Hi, > > &

Re: [openstack-dev] [tricircle]Welcome Shinobu Kinjo to be the core reviewer of Tricircle

Cheers, S > > Best Regards > Chaoyi Huang ( Joe Huang ) > > -Original Message- > From: joehuang > Sent: Tuesday, May 03, 2016 9:04 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: [openstack-dev][tricircle]Proposing Shinobu Ki

Re: [openstack-dev] [tricircle]PTL election of Tricircle for Newton release

Development Mailing List (not for usage questions) Subject: [openstack-dev][tricircle]PTL election of Tricircle for Newton release Hello, As discussed in yesterday weekly meeting, PTL nomination period from May 9 ~ May 13, election from May 16 ~ May 20 if more than one nomination . If you want

[openstack-dev] [tricircle]Welcome Shinobu Kinjo to be the core reviewer of Tricircle

:04 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev][tricircle]Proposing Shinobu Kinjo for Tricircle core reviewer Hi, I would like to propose adding Shinobu Kinjo to the Tricircle core reviewer team. Shinobu has been a highly valuable reviewer

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

ers, Shinobu > > Best Regards > Chaoyi Huang ( joehuang ) > > > From: Shinobu Kinjo [shinobu...@gmail.com] > Sent: 08 May 2016 10:12 > To: OpenStack Development Mailing List (not for usage questions) > Subject: [openstack-dev] [tr

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

the blueprint to help readers easy to understand? Best Regards Chaoyi Huang ( joehuang ) From: Shinobu Kinjo [shinobu...@gmail.com] Sent: 08 May 2016 10:12 To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [tricircle

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

Hi Team, Since there was no tag [tricircle] in subject, I'm emailing you again. Sorry for spam -; We are trying to describe specification [1] regarding to ""cross OpenStack L2 networking"" [0] as Chaoyi mentioned in previous message. Honestly that description [0] does not accurately describe

Re: [openstack-dev] [tricircle] [blueprint] Definition of strategies

s) Subject: [openstack-dev] [tricircle] [blueprint] Definition of strategies Hi Chaoyi, In the Tricircle's blueprint, there is a section: 7.3 Resource Create Request Dispatch In this section, strategy for each resource is described. It would be better to elaborate on *WHEN* more: *before* or *during*

[openstack-dev] [tricircle] [blueprint] Definition of strategies

Hi Chaoyi, In the Tricircle's blueprint, there is a section: 7.3 Resource Create Request Dispatch In this section, strategy for each resource is described. It would be better to elaborate on *WHEN* more: *before* or *during* or *after* e.g., security group's strategy is defined as follows:

Re: [openstack-dev] [tricircle] About the dynamic pod binding

Yipei, Probably you may be interested in the following section in Blueprint [1]. 7.1 AZ and Pod Binding ... 7.x [1] https://docs.google.com/document/d/18kZZ1snMOCD9IQvUKI5NVDzSASpw-QKj7l2zNqMEd3g/edit#heading=h.x14kdooqhai1 Cheers, S On Fri, May 6, 2016 at 3:58 PM, Shinobu Kinjo

Re: [openstack-dev] [tricircle] About the dynamic pod binding

Yipei, According to Chaoyi, you have a bunch of experiences regarding to the OpenStack, networking which is awesome. I look forward to hearing from you soon. Cheers, Shinobu On Fri, May 6, 2016 at 12:05 PM, Yipei Niu wrote: > Got it with thanks. > > Best regards, > Yipei >

Re: [openstack-dev] [tricircle] Easy Way to Test Tricircle North-South L3 Networking

t; Sent: 04 May 2016 9:38 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [tricircle] Easy Way to Test Tricircle > North-South L3 Networking > > Hi Chaoyi, > > I didn't consider Ronghui's environment which I have no idea abo

Re: [openstack-dev] [tricircle] About the dynamic pod binding

Got it with thanks. Best regards, Yipei On Fri, May 6, 2016 at 9:48 AM, joehuang wrote: > Hi, Yipei, > > Shinobu is correct, this should be taken into consideration in the design > of dynamic pod binding. > > How to schedule pod, you can refer to host-aggregate scheduling

Re: [openstack-dev] [tricircle] About the dynamic pod binding

Hi, Yipei, Shinobu is correct, this should be taken into consideration in the design of dynamic pod binding. How to schedule pod, you can refer to host-aggregate scheduling with flavor, the difference is that the scheduling granularity is on pod level. By the tag in flavor extra-spec and

Re: [openstack-dev] [tricircle] About the dynamic pod binding

Hi Yipei, On Thu, May 5, 2016 at 9:54 PM, Yipei Niu wrote: > Hi, all, > > For dynamic pod binding, I have some questions. > [snip] > 3. How is Tricircle aware of what type of resource wanted by tenants? For > example, a tenant wants to boot VMs for CAD modelling with

[openstack-dev] [tricircle] About the dynamic pod binding

Hi, all, For dynamic pod binding, I have some questions. 1. Do we need to store historical pod binding records in the pod binding table? Why? 2. How do we manage pod binding filters, store them in DB? 3. How is Tricircle aware of what type of resource wanted by tenants? For example, a tenant

[openstack-dev] [tricircle] A number of dummy functions

Team, How many dummy, fake function does the Tricircle have? I understood that we are now in pre-production, and will be in production hopefully soon! But I don't need surprise any more -; e.g., # ./tricircle/cinder_apigw/controllers/volume.py 337 def _convert_header(self, t_release,

[openstack-dev] [tricircle]PTL election of Tricircle for Newton release

...@gmail.com] Sent: Wednesday, May 04, 2016 5:35 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tricircle] Requirements for becoming approved official project Hi Team, There is an additional work to become an official (approval) project. Once we complete

Re: [openstack-dev] [tricircle]Proposing Shinobu Kinjo for Tricircle core reviewer

+1. He is experienced and helps me a lot. He is qualified to be a core reviewer. Best regards, Yipei __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [tricircle]weekly meeting of May. 4

One more agenda in the weekly meeting: PTL election. From: joehuang Sent: 04 May 2016 10:44 To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev][tricircle]weekly meeting of May. 4 Hi, In last virtual design summit meeting

Re: [openstack-dev] [tricircle] Requirements for becoming approved official project

___ > From: Shinobu Kinjo [shinobu...@gmail.com] > Sent: 02 May 2016 18:48 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [tricircle] Requirements for becoming approved > official project > > Hi Thierry, > > On Mon,

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

Hi, In last virtual design summit meeting, some feature was identified blocking the tempest. So let's discuss the these topics in the weekly meeting: Virtual design summit: https://etherpad.openstack.org/p/TricircleNeutonDesignSummit IRC meeting:

Re: [openstack-dev] [tricircle] Easy Way to Test Tricircle North-South L3 Networking

questions) Subject: Re: [openstack-dev] [tricircle] Easy Way to Test Tricircle North-South L3 Networking Hi Chaoyi, I didn't consider Ronghui's environment which I have no idea about. > That's why Zhiyuan proposed hacking way to do it. Considering such a limited situation, I underst

Re: [openstack-dev] [tricircle] Easy Way to Test Tricircle North-South L3 Networking

____ >> From: Shinobu Kinjo [shinobu...@gmail.com] >> Sent: 04 May 2016 6:58 >> To: OpenStack Development Mailing List (not for usage questions) >> Subject: Re: [openstack-dev] [tricircle] Easy Way to Test Tricircle >> North-South L3 Networking >> >>

Re: [openstack-dev] [tricircle]Proposing Shinobu Kinjo for Tricircle core reviewer

+1, Shinobu has given me many suggestions in my patches. On 4 May 2016 at 07:57, Zhipeng Huang wrote: > +1, still remember Shinobu getting started from basic concept of > tricircle, and now becoming a maester of multisite openstack :) > > On Tue, May 3, 2016 at 9:03 PM,

Re: [openstack-dev] [tricircle] Easy Way to Test Tricircle North-South L3 Networking

> From: Shinobu Kinjo [shinobu...@gmail.com] > Sent: 04 May 2016 6:58 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [tricircle] Easy Way to Test Tricircle > North-South L3 Networking > > Vega,

Re: [openstack-dev] [tricircle] Easy Way to Test Tricircle North-South L3 Networking

( joehuang ) From: Shinobu Kinjo [shinobu...@gmail.com] Sent: 04 May 2016 6:58 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tricircle] Easy Way to Test Tricircle North-South L3 Networking Vega, On Tue, May 3, 2016

Re: [openstack-dev] [tricircle]Proposing Shinobu Kinjo for Tricircle core reviewer

+1, still remember Shinobu getting started from basic concept of tricircle, and now becoming a maester of multisite openstack :) On Tue, May 3, 2016 at 9:03 PM, joehuang wrote: > Hi, > > I would like to propose adding Shinobu Kinjo to the Tricircle core > reviewer team. > >

Re: [openstack-dev] [tricircle] Easy Way to Test Tricircle North-South L3 Networking

Vega, On Tue, May 3, 2016 at 5:49 PM, Vega Cai wrote: > Hi all, > > Just would like to share a way to test Tricircle north-south L3 networking > without requiring the third interface. > > In the Tricircle readme, it is said that you need to add an interface in > your host

[openstack-dev] [tricircle]Proposing Shinobu Kinjo for Tricircle core reviewer

Hi, I would like to propose adding Shinobu Kinjo to the Tricircle core reviewer team. Shinobu has been a highly valuable reviewer to Tricircle for the past few months. His contribution covers each patch submitted, document, etherpad discussion, and always give valueable, meaningful and

[openstack-dev] [tricircle] Easy Way to Test Tricircle North-South L3 Networking

Hi all, Just would like to share a way to test Tricircle north-south L3 networking without requiring the third interface. In the Tricircle readme, it is said that you need to add an interface in your host to br-ext bridge. One interface to access the host, one interface for east-west networking

[openstack-dev] [tricircle]cross pod L2 networking update in the design doc

Hello, As the cross pod L2 networking is in review, and after some discussion with guy working in L2GW project, I think we don't need to support DCI SDN Controller for cross pod L2 networking, L2GW will be good to provide different networking options. Therefore the design doc

Re: [openstack-dev] [tricircle] Requirements for becoming approved official project

that if needed. Best Regards Chaoyi Huang ( joehuang ) From: Shinobu Kinjo [shinobu...@gmail.com] Sent: 02 May 2016 18:48 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tricircle] Requirements for becoming approved

<    1   2   3   4   5   6   >