Re: [openstack-dev] [Nova][Manila] Nova API to attach/detach file volume/share

Sorry, using vsock is: -1 Need more discussion. On Tue, Oct 27, 2015 at 2:13 PM, Sage Weil wrote: > On Mon, 26 Oct 2015, Ben Swartzlander wrote: > > On 10/25/2015 01:25 PM, Sage Weil wrote: > > > Hi everyone, > > > > > > We're currently working on an improved mechanism for

Re: [openstack-dev] [Nova][Manila] Nova API to attach/detach file volume/share

Yes, I will. On Wed, Oct 28, 2015 at 4:37 AM, Steve Gordon <sgor...@redhat.com> wrote: > - Original Message - > > From: "Shinobu Kinjo" <shinobu...@gmail.com> > > To: "OpenStack Development Mailing List (not for usage questions)" <

Re: [openstack-dev] [Nova] SR-IOV subteam

That's good to know. Thank you! Shinobu - Original Message - From: "Moshe Levi" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Wednesday, November 4, 2015 4:56:05 PM Subject: Re: [openstack-dev] [Nova]

Re: [openstack-dev] [Manila] CephFS native driver

Yes, let's discuss this in Tokyo. Shinobu - Original Message - From: "Clinton Knight" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Thursday, October 8, 2015 2:15:52 AM Subject: Re:

Re: [openstack-dev] Proposed solution to "Admin" ness improperly scoped:

Just question. Will be scopes of non-admin users projects in admin scoped project? Shinobu - Original Message - From: "Adam Young" To: "OpenStack Development Mailing List" Sent: Monday, October 12, 2015 3:38:01 AM Subject:

Re: [openstack-dev] [keystone] Let's get together and fix all the bugs

So what's the procedure? Shinobu - Original Message - From: "Adam Young" To: openstack-dev@lists.openstack.org Sent: Saturday, October 10, 2015 12:11:35 PM Subject: Re: [openstack-dev] [keystone] Let's get together and fix all the bugs On 10/09/2015 11:04 PM, Chen,

Re: [openstack-dev] Proposed solution to "Admin" ness improperly scoped:

ubject: Re: [openstack-dev] Proposed solution to "Admin" ness improperly scoped: On 10/12/2015 08:07 PM, Shinobu Kinjo wrote: > Just question. > Will be scopes of non-admin users projects in admin scoped project? I'm sorry I don't understand what you are asking. > > Shinob

Re: [openstack-dev] [Keystone] PTL Candidacy: Adam Young

I'm not sure if I should reply to you or not since I am not developer of this project but another. But I would like to let you know what I am really really thinking how the Keystone should work is: Just HUB I know that this description would be confusing you and developers subscribing

Re: [openstack-dev] [Manila] CephFS native driver

Is there any plan to merge those branches to master? Or is there anything needs to be done more? Shinobu - Original Message - From: "Ben Swartzlander" To: "OpenStack Development Mailing List (not for usage questions)" Sent:

Re: [openstack-dev] [Manila] CephFS native driver

> For ultra isolation, the RADOS pools would also be configured to map to > different OSDs. This is really good idea, and will be motivation to me. > Separate RADOS namespaces do not provide physical separation (multiple > namespaces exist within one pool, hence on the same OSDs), but they >

Re: [openstack-dev] CephFS native driver

eph on the other hand scales very nicely and its very fault tollerent out of the box. Thanks, Kevin From: Shinobu Kinjo [ski...@redhat.com] Sent: Friday, September 25, 2015 12:04 AM To: OpenStack Development Mailing List (not for usage questions); John Spr

Re: [openstack-dev] [Manila] CephFS native driver

Thanks! Keep me in the loop. Shinobu - Original Message - From: "John Spray" <jsp...@redhat.com> To: "Shinobu Kinjo" <ski...@redhat.com> Cc: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org

Re: [openstack-dev] [Manila] CephFS native driver

So here are questions from my side. Just question. 1.What is the biggest advantage comparing others such as RDB? We should be able to implement what you are going to do in existing module, shouldn't we? 2.What are you going to focus on with a new implementation? It seems to be to use

Re: [openstack-dev] [Manila] CephFS native driver

pic. That's interesting to me. Shinobu - Original Message - From: "John Spray" <jsp...@redhat.com> To: "Shinobu Kinjo" <ski...@redhat.com> Cc: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> S

[openstack-dev] [heat] Deployment of Lock / Unlock Operation like MUTEX

Hello, Here is a situation which I faced, that can be reproduced. I did heat resource-signal multiple times simultaneously to scale instance. As a result 3 resources were made in the scaling group having max_size=2. stack-list -n showed me 3 stacks in one parent. Heat itself seems not to

Re: [openstack-dev] [all] tox 2.3.0 broke tempest jobs

What is the current status of this failure? > 2015-12-13 08:55:04.863 | ValueError: need more than 1 value to unpack Thank you Shinobu On Sun, Dec 13, 2015 at 4:48 AM, Yuriy Taraday wrote: > On Sat, Dec 12, 2015 at 10:27 PM Jeremy Stanley wrote: > >>

Re: [openstack-dev] [all] tox 2.3.0 broke tempest jobs

Thank you for your confirmation. Something installed tox onto my CentOS7, 3.10.0-229.el7.x86_64 because of dependency. I need to elaborate more. Shinobu On Sun, Dec 13, 2015 at 6:47 PM, Yuriy Taraday <yorik@gmail.com> wrote: > On Sun, Dec 13, 2015 at 12:14 PM Shinobu Kinjo

Re: [openstack-dev] [Openstack-dev][Manila] status=NONE when share is created

Hello, It's better to discuss this on IRC. https://wiki.openstack.org/wiki/IRC Rgds, Shinobu On Thu, Jan 7, 2016 at 4:11 PM, wrote: > Hi All, > > > > Could someone please reply to the mail below .. > > > > Is this an expected state to get created share status as None?

Re: [openstack-dev] [heat]How does heat work when deleting the stack?

Can you share what exactly you did? Rgds, Shinobu - Original Message - From: "zhu4236926" To: "openstack-dev" Sent: Wednesday, December 30, 2015 12:50:00 AM Subject: [openstack-dev] [heat]How does heat work when deleting the stack?

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

Re: [openstack-dev] [OpenStack-Infra] [Infra][tricircle] patch not able to be merged

Thank you for investigation and some manual operations to fix out the problem. If there would be anything to prevent such as unexpected behaviour, please let us know. Cheers, Shinobu On Fri, Jun 3, 2016 at 11:04 PM, Jeremy Stanley wrote: > On 2016-06-03 03:45:31 +

Re: [openstack-dev] [Installation] RHEL-7 devstack installation failed in bootstrap_keystone

It's better to send this kind of topic to: openst...@lists.openstack.org not *dev* from the next. Rgds, Shinobu - Original Message - From: "Pradip Mukhopadhyay" To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] sqlalchemy-utils fails devstack install

Which branch are you using? Rgds, Shinobu - Original Message - From: "Isao Watanabe" To: openstack-dev@lists.openstack.org Sent: Thursday, February 25, 2016 1:45:48 PM Subject: [openstack-dev] sqlalchemy-utils fails devstack install Hello team Does anyone

Re: [openstack-dev] sqlalchemy-utils fails devstack install

openstack.org> Sent: Thursday, February 25, 2016 2:02:09 PM Subject: Re: [openstack-dev] sqlalchemy-utils fails devstack install Hello, @Shinobu I'm using master branch. Best regards, Watanabe.isao > -Original Message- > From: Shinobu Kinjo [mailto:ski...@redhat.com] >

Re: [openstack-dev] [Nova] Re-booting the SR-IOV meeting

2016 12:26:37 AM Subject: Re: [openstack-dev] [Nova] Re-booting the SR-IOV meeting On 02/26/2016 10:35 PM, Shinobu Kinjo wrote: > Hello, > > Thank you for your message. > Is there any list of only SR-IOV related bugfixes? If there is any > pointer, that would be very useful.

Re: [openstack-dev] Vlan Tenant network

That is a great guide. Cheers, On Mon, Feb 29, 2016 at 5:20 PM, Andreas Scheuring wrote: > Hi Pratti, > yes, this is working! For Openvswitch ml2 driver just configure on the > neutron server in the ml2 configuration file [1][2] > > [ml2] > tenant_network_types =

Re: [openstack-dev] [TripleO] Show TripleO: A terminal dashboard

That's pretty much interesting and fantastic to me. To use the dashboard, is it good enough to activate ironic in devstack? Cheers, Shinobu On Sat, Feb 27, 2016 at 5:06 AM, Ben Nemec wrote: > Interesting! So this could conceivably be another consumer of the API, >

Re: [openstack-dev] [Nova] Re-booting the SR-IOV meeting

Hello, Thank you for your message. Is there any list of only SR-IOV related bugfixes? If there is any pointer, that would be very useful. Cheers, Shinobu On Fri, Feb 26, 2016 at 11:58 PM, Nikola Đipanov wrote: > Hello folks, > > We are closing in on Mitaka-3 and it would

Re: [openstack-dev] [TripleO] Show TripleO: A terminal dashboard

uary 2016, Shinobu Kinjo <shinobu...@gmail.com> wrote: >> >> That's pretty much interesting and fantastic to me. >> To use the dashboard, is it good enough to activate ironic in devstack? > > > It's a bit more complicated than that at the moment. It makes the assumption

Re: [openstack-dev] [nova] patches that improve code quality

Ideally it's good practice to do refactoring the codes to add more readability. In reality, it's kind of impossible. Because there might be another process required after refactoring and it would take a time. But that's good point, honestly. On Thu, Mar 10, 2016 at 1:33 AM, Matt Riedemann

Re: [openstack-dev] [jacket] Introduction to jacket, a new project

On Wed, Mar 16, 2016 at 9:58 PM, zs wrote: > Hi Gordon, > > Thank you for your suggestion. > > I think jacket is different from tricircle. Because tricircle focuses on > OpenStack deployment across multiple sites, but jacket focuses on how to > manage the different clouds just

Re: [openstack-dev] [tricircle] playing tricircle with two node configuration

to fix it. Best regards, Yipei On Tue, Mar 29, 2016 at 2:25 PM, joehuang <joehu...@huawei.com<mailto:joehu...@huawei.com>> wrote: I think we can do it later. It's still a little bit strange that if nova-network in the Local.conf is disabled at first before devstack installation, the

Re: [openstack-dev] [tricircle]weekly meeting of Apr. 6

: > Hi, Shinobu, > > Do you have some ideas on trust relationship between top and bottoms over BGP > across Ass? > > Best Regards > Chaoyi Huang ( Joe Huang ) > > > -Original Message- > From: Shinobu Kinjo [mailto:shinobu...@gmail.com] > Sent: Tuesd

Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

On Wed, Apr 6, 2016 at 7:47 PM, Sean Dague wrote: > On 04/06/2016 04:19 AM, Sylvain Bauza wrote: >> >> >> Le 06/04/2016 06:44, Qiming Teng a écrit : >>> Not an expert of Nova but I am really shocked by such a change. Because >>> I'm not a Nova expert, I don't have a say on the

[openstack-dev] [Tricircle] Original Blueprint

Hi Chaoyi, In blueprint you described for PoC, there are information of tables. [1] They seem to out-to-date. Do you think that those information need to be up-to-date in your blueprint? If it's not necessary, it's better to move those information to different sheet or put some comment like

[openstack-dev] [Tricircle] UUID Mapping

Hi Team, Can we elaborate on uuid mapping more? As described in blueprint, it's expected to be a solution for one of challenges. > The object UUID in the top layer is different from the UUIDs in the bottom > layers. There should theoretical logic, mechanism. But I've not been able to find any

Re: [openstack-dev] [Tricircle] UUID Mapping

ed there, but read the "7.2 > Resource Routing Table". > > Best Regards > Chaoyi Huang ( Joe Huang ) > > > -Original Message- > From: Shinobu Kinjo [mailto:shinobu...@gmail.com] > Sent: Thursday, April 07, 2016 2:35 PM > To: OpenStack Development Ma

Re: [openstack-dev] [Tricircle] Original Blueprint

w > patches. I'm now expecting that *blueprint* is always master; meaning that anyone who would contribute to the Tricircle need to refer, follow *blueprint*. Is it same of what you are thinking of? Cheers, Shinobu > > Best Regards > Chaoyi Huang ( Joe Huang ) > > > -----Orig

Re: [openstack-dev] [puppet][ceph] Puppet-ceph is now a formal member of puppet-openstack

Great! On Tue, Apr 12, 2016 at 6:24 AM, Andrew Woodward wrote: > It's been a while since we started the puppet-ceph module on stackforge as a > friend of OpenStack. Since then Ceph's usage in OpenStack has increased > greatly and we have both the puppet-openstack deployment

Re: [openstack-dev] Constant attempts from Matthew Kassawara to remove Debian from the install-guide

Tom, Would you elaborate more? - Original Message - From: "Tom Fifield" To: openstack-dev@lists.openstack.org Sent: Saturday, April 9, 2016 6:20:31 PM Subject: Re: [openstack-dev] Constant attempts from Matthew Kassawara to remove Debian from the install-guide On

Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

On Wed, Apr 6, 2016 at 1:44 PM, Qiming Teng wrote: > Not an expert of Nova but I am really shocked by such a change. Because > I'm not a Nova expert, I don't have a say on the *huge* efforts in > maintaining some builtin/default flavors. As a user I don't care where >

Re: [openstack-dev] [Tricircle] Original Blueprint

t Regards > Chaoyi Huang ( Joe Huang ) > > > -Original Message- > From: Shinobu Kinjo [mailto:shinobu...@gmail.com] > Sent: Thursday, April 07, 2016 4:16 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [Trici

Re: [openstack-dev] [jacket] Introduction to jacket, a new project

Kevin, Quick question. Does one OpenStack infrastructure have to be dedicated for one Jacket instance? Cheers, Shinobu On Thu, Mar 24, 2016 at 8:24 PM, Kevin.ZhangSen wrote: > Hi Ghanshyam, > > Thank you for your sugesstions, and I agree with your opinion that the >

Re: [openstack-dev] [jacket] Introduction to jacket, a new project

Thanks for your questions. My reply is behind your questions. :) > > Best Regards, > Kevin (Sen Zhang) > > > At 2016-03-17 12:43:14, "Shinobu Kinjo" <shinobu...@gmail.com> wrote: >>Thank you for your explanation in detail. >> >>On Thu, Mar

Re: [openstack-dev] [Manila] Mitaka RC1 done

On Sun, Mar 20, 2016 at 9:34 AM, Ben Swartzlander wrote: > Thanks everyone for the hard work getting RC1 done. We had record high > number of bugs at feature freeze this cycle, and we ended up pushing a few > out, but there were SIXTY bugs fixed in the last 2 weeks which I

Re: [openstack-dev] [tricircle] Using in-memory database for unit tests

mail-list) > > Best Regards > Chaoyi Huang ( joehuang ) > > -Original Message- > From: Shinobu Kinjo [mailto:ski...@redhat.com] > Sent: Tuesday, March 22, 2016 7:43 AM > To: joehuang; khayam.gondal; zhangbinsjtu; shipengfei92; newypei; Liuhaixia; > caizhiyuan (A); h

Re: [openstack-dev] [tricircle] Using in-memory database for unit tests

Thank you for your comment (inline for my message). On Tue, Mar 22, 2016 at 11:53 AM, Vega Cai <luckyveg...@gmail.com> wrote: > Let me try to explain some. > > On 22 March 2016 at 10:09, Shinobu Kinjo <shinobu...@gmail.com> wrote: >> >> On Tue, Mar 22,

Re: [openstack-dev] [Tricircle] Using the reserved keywords reserved as field name

ement-stateless > > Best Regards > Chaoyi Huang ( Joe Huang ) > > > -Original Message- > From: Shinobu Kinjo [mailto:shinobu...@gmail.com] > Sent: Saturday, March 26, 2016 2:39 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: [

Re: [openstack-dev] [Tricircle] Using the reserved keywords reserved as field name

ec/implement-stateless >> >> Best Regards >> Chaoyi Huang ( Joe Huang ) >> >> >> -Original Message- >> From: Shinobu Kinjo [mailto:shinobu...@gmail.com] >> Sent: Saturday, March 26, 2016 2:39 PM >> To: OpenStack Development Mailing List (not for u

[openstack-dev] [Tricircle] Using the reserved keywords reserved as field name

Hi Team, In the Tricircle database, there are three tables having a field name which the MySQL (MariaDB) has as one of the reserved keywords. [1] Table Name: aggregate_metadata instance_type_extra_specs quality_of_service_specs Field Name: key I think it would not be best practice to

Re: [openstack-dev] [Tricircle] Using the reserved keywords reserved as field name

ways and Xjobs > > On Sat, Mar 26, 2016 at 8:11 PM, Shinobu Kinjo <shinobu...@gmail.com> wrote: >> >> Yes, that's one of possibilities. >> >> Cheers, >> Shinobu >> >> On Sat, Mar 26, 2016 at 8:55 PM, Zhipeng Huang <zhipengh...@gmail.com> >

Re: [openstack-dev] [Tricircle] Using the reserved keywords reserved as field name

Yes, that's one of possibilities. Cheers, Shinobu On Sat, Mar 26, 2016 at 8:55 PM, Zhipeng Huang <zhipengh...@gmail.com> wrote: > any possible that we use gRPC for Tricircle ? > > On Sat, Mar 26, 2016 at 6:11 PM, Shinobu Kinjo <shinobu...@gmail.com> wrote: >> &g

Re: [openstack-dev] [tricircle] playing tricircle with two node configuration

On Wed, Mar 23, 2016 at 12:41 PM, joehuang wrote: > Hi, Yipei, > > > > When you play Tricircle, it’s important to know that Tricircle is the > OpenStack API gateway to other OpenStack instances. In the Readme, Pod1, > Pod2 are two OpenStack instances, before trying Tricircle,

Re: [openstack-dev] [jacket] Introduction to jacket, a new project

more differences of clouds' behaviour and function. Jacket's > target is to shield these differences and let users feel that they are using > just one cloud. Cheers, Shinobu > Thanks. > > Best Regards, > Kevin (Sen Zhang) > > > At 2016-03-17 05:47:35, "Shino

Re: [openstack-dev] [Tricircle] LinuxCon+Container Con (Tokyo )

apan > > Let me know if anyone is interested. Especially from Tricircle community. > > On Tue, Mar 8, 2016 at 3:28 PM, Shinobu Kinjo <shinobu...@gmail.com> wrote: >> >> When? >> >> Cheers, >> S >> >> On Tue, Mar 8, 2016 at 5:43 PM,

Re: [openstack-dev] Reg: Configuration Management tool for Openstack.

Good post! http://docs.openstack.org/developer/openstack-ansible/install-guide/index.html So ansible?, I'm puppeter though... Cheers, S On Tue, Mar 8, 2016 at 7:49 PM, Gyorgy Szombathelyi wrote: > Hi, > > Since I think Ansible is the best config

Re: [openstack-dev] [Tricircle] LinuxCon+Container Con (Tokyo )

When? Cheers, S On Tue, Mar 8, 2016 at 5:43 PM, Khayam Gondal wrote: > Does anybody from community is attending the tokyo event. Its from Jul 13-15 > > __ > OpenStack Development Mailing List (not

Re: [openstack-dev] [Manila] Concurrent execution of drivers

What are you facing? On Fri, Mar 4, 2016 at 9:06 PM, John Spray wrote: > Hi, > > What expectations should driver authors have about multiple instances > of the driver being instantiated within different instances of > manila-share? > > For example, should I assume that when

Re: [openstack-dev] [tripleo] Contributing to TripleO is challenging

Any comment? Cheers, S On Sat, Mar 5, 2016 at 11:03 AM, Adam Young wrote: > On 03/04/2016 09:23 AM, Emilien Macchi wrote: > > That's not the name of any Summit's talk, it's just an e-mail I wanted > to write for a long time. > > It is an attempt to expose facts or things I've

Re: [openstack-dev] [Neutron] Heads up: add description to resources breaks decomposed plugin

Thx. Cheers, S - Original Message - From: "Kevin Benton" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Sunday, March 6, 2016 7:26:46 PM Subject: Re: [openstack-dev] [Neutron] Heads up: add description to

Re: [openstack-dev] [Manila] nfs-over-vsock (was: Concurrent execution of drivers)

rtzlander.org> wrote: > On 03/05/2016 05:34 AM, Shinobu Kinjo wrote: >> >> Are we still going to think of nfs-over-vsock? >> Never mind. It's just coming from my curiosity. > > > A lot of work outside Manila has to happen before we can actually deliver > that f

Re: [openstack-dev] [Manila] Concurrent execution of drivers

Are we still going to think of nfs-over-vsock? Never mind. It's just coming from my curiosity. Cheers, S On Fri, Mar 4, 2016 at 11:08 PM, Valeriy Ponomaryov wrote: >> Thanks - so if I understand you correctly, each share instance is >> uniquely associated with a single

Re: [openstack-dev] [Tricircle] LinuxCon+Container Con (Tokyo )

> > Cheers, > S > > On Tue, Mar 8, 2016 at 8:09 PM, Khayam Gondal <khayam.gon...@gmail.com> > wrote: > > July 13,2015 to July 15,2015 in Tokyo Japan. > > http://events.linuxfoundation.org/events/linuxcon-japan > > > > Let me know if anyone is inter

Re: [openstack-dev] [Tricircle] Naming convention

How do you think about this? Best Regards Chaoyi Huang ( Joe Huang ) -Original Message- From: Shinobu Kinjo [mailto:shinobu...@gmail.com] Sent: Tuesday, April 05, 2016 9:46 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Tricircle] Nam

Re: [openstack-dev] [Tricircle] Naming convention

ang ) > > > -Original Message- > From: Shinobu Kinjo [mailto:shinobu...@gmail.com] > Sent: Saturday, April 02, 2016 7:40 AM > To: joehuang; OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [Tricircle] Naming convention

Re: [openstack-dev] [tricircle]weekly meeting of Apr. 6

Hi Chaoyi, Thank you for team mtg every week. One day, we may need to discuss about trust relationship considering secure connection and no-latency issue between top and bottoms over BGP across ASs, in short between DCs. Any thought would be appreciated as usual. Cheers, Shinobu On Tue, Apr 5,

Re: [openstack-dev] [tricircle] playing tricircle with two node configuration

n local.conf, n-net is disabled, which is the same as the sample file of >> tricircle. >> >> [1] http://docs.openstack.org/developer/nova/sample_config.html >> >> Best regards, >> Yipei >> >> On Mon, Mar 28, 2016 at 4:46 PM, Shinobu Kinjo <shinobu...@gma

Re: [openstack-dev] [All][Neutron] Improving development and review velocity - Is it time for a drastic change?

On Fri, Apr 1, 2016 at 10:12 AM, Assaf Muller wrote: > Have you been negatively impacted by slow development and review > velocity? Read on. > > OpenStack has had a slow review velocity for as long as I can > remember. This has a cascading effect where people take up multiple >

Re: [openstack-dev] [tricircle] playing tricircle with two node configuration

E.md > [2] http://shipengfei92.cn/play_tricircle_with_virtualbox > > Best Regards > Chaoyi Huang ( Joe Huang ) > > > -Original Message- > From: Shinobu Kinjo [mailto:shinobu...@gmail.com] > Sent: Tuesday, March 29, 2016 10:48 AM > To: OpenStack Development Maili

Re: [openstack-dev] [tricircle] playing tricircle with two node configuration

_ > > self.invoke_controller(controller, args, kwargs, state) > > File "/usr/local/lib/python2.7/dist-packages/pecan/core.py", line 572, in > invoke_controller > > result = controller(*args, **kwargs) > > File "/opt/stack/tricircle/tricircle/

Re: [openstack-dev] [Tricircle] Naming convention

One of examples is: """ tricircle/db/api.py """ authorize_quota_class_context(context, class_name): # This could become: auth_quota_class_ctx(ctx, class_name): # If we put some comment for this, this also could become: """ Function: Ensure a request has right permission to given the

[openstack-dev] [Tricircle] Naming convention

Hi Team, Probably it's worth thinking of naming convention for classes, methods or whatever we define in source codes. Some names are lengthy and there might be no consistency. At the moment it's fine. But once this project gets growing, situation would become chaotic and could cause bugs. What

Re: [openstack-dev] [tricircle] playing tricircle with two node configuration

dme[1] and pengfei's experience[2] to install Tricircle. >> >> [1] https://github.com/openstack/tricircle/blob/master/README.md >> [2] http://shipengfei92.cn/play_tricircle_with_virtualbox >> >> Best Regards >> Chaoyi Huang ( Joe Huang ) >> >> >&g

Re: [openstack-dev] [tricircle] Using in-memory database for unit tests

On Wed, Mar 23, 2016 at 2:33 PM, Vega Cai <luckyveg...@gmail.com> wrote: > > > On 22 March 2016 at 12:09, Shinobu Kinjo <shinobu...@gmail.com> wrote: >> >> Thank you for your comment (inline for my message). >> >> On Tue, Mar 22, 2016 at 11:53 AM, Veg

Re: [openstack-dev] [Nova] RPC Communication Errors Might Lead to a Bad State

Hi, Just coming from my curiosity (inline). On Thu, Apr 14, 2016 at 12:34 AM, Dan Smith wrote: >> * nova-api should receive an acknowledgement from nova-compute. It is >> unclear to me why today it uses a non-reply mechanism - probably to >> free the worker as fast

[openstack-dev] [TripleO] Change 247669: Ceph Puppet: implement per-pool parameters:

Hi TripleO Team, If you could take care of ${subject}, it would be nice. [1] https://review.openstack.org/#/c/247669 Cheers, S __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [TC][tricircle] ask help from TC and other guru in the OpenStack community

Flavio, On Tue, Apr 26, 2016 at 11:12 PM, Flavio Percoco <fla...@redhat.com> wrote: > On 26/04/16 20:39 +0900, Shinobu Kinjo wrote: >> >> On Tue, Apr 26, 2016 at 12:47 PM, joehuang <joehu...@huawei.com> wrote: >>> >>> Hi, TCs and guru, >>&

Re: [openstack-dev] [all]call for contributors for Tricircle project - for massive distributed edge clouds and large scale cloud.

Hi Chaoyi, At a meeting today, we had a great update from you. I don't write any details here but I'm quite happy with that. I believe that we will have awesome contributors and the Tricircle become one of important projects soon. Cheers, Shinobu On Mon, Apr 25, 2016 at 1:59 PM, joehuang

Re: [openstack-dev] [TC][tricircle] ask help from TC and other guru in the OpenStack community

On Tue, Apr 26, 2016 at 12:47 PM, joehuang wrote: > Hi, TCs and guru, > > > > If tricircle planned to apply being TC approved big tent project, would > someone help to guide our project? I also would like to know what we should do for that so that we focus on specific

Re: [openstack-dev] [TripleO] Change 247669: Ceph Puppet: implement per-pool parameters:

8 PM Subject: Re: [openstack-dev] [TripleO] Change 247669: Ceph Puppet: implement per-pool parameters: On Fri, Apr 22, 2016 at 08:00:02AM -0400, Emilien Macchi wrote: > On Fri, Apr 22, 2016 at 3:51 AM, Shinobu Kinjo <shinobu...@gmail.com> wrote: > > Hi TripleO Team, > > >

[openstack-dev] Requirements for becoming approved official project

Hi Tom, First sorry for bothering you -; We are trying to make the tricircle project [1] one of the opnestack official projects. And we are referring to project team guide to make sure what are requirements. [2]. Reading this guide, what we need to consider right now is open development, I think

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

astructure up, and hope to also have a > template and some other guides for you to help you do this. If you have > questions about getting started on this, please email the docs mailing list: > openstack-d...@lists.openstack.org > > Thanks, > Lana > > On 29/04/16 22:40, Shinobu

Re: [openstack-dev] [tricircle] virtual design summit for Newton

Hi Team, There was no enough time to discuss all topics in the meeting today. I wrote up what we discussed. Please make sure what need to be done and add anything if I've missed. Cheers, Shinobu - Original Message - From: "joehuang" To: "OpenStack Development

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

ation to fit the guideline ? > > On Fri, May 20, 2016 at 11:04 AM, Shinobu Kinjo <shinobu...@gmail.com> > wrote: >> >> Hi Team, >> >> Please make sure that your coding style follows OpenStack style >> guidelines. [1] >> >> I understand that it's re

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

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

[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]PTL election conclusion

dates/newton/Kuryr/Gal_Sagie.txt > [2]http://git.openstack.org/cgit/openstack/election/plain//candidates/newton/Glance/Nikhil_Komawar.txt > [3]http://git.openstack.org/cgit/openstack/election/plain//candidates/newton/Neutron/Armando_Migliaccio.txt > [4]https://wiki.openstack.org/wiki/PTL_El

[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

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

hink we need to remove this link? and freeze this old documentation? Best Regards Chaoyi Huang ( Joe Huang ) -Original Message- From: Shinobu Kinjo [mailto:shinobu...@gmail.com] Sent: Wednesday, May 11, 2016 4:17 PM To: OpenStack Development Mailing List (not for usage questions) Sub

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 <shinobu...@gmail.com> wrote: > Hi Team, > > In page1, we define "stateless design" as follows: > > Note

[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

Re: [openstack-dev] [stackalytics]many projects missing in the "others" category

AFAIK the Tricircle is one of them. [1] How can we fix it out? [1] http://stackalytics.com/report/contribution/tricircle/90 Cheers, S On Tue, May 3, 2016 at 10:11 PM, joehuang wrote: > Hello, > > Very sad to know that some projects are missing again in the "others" >

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

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

ut Ronghui's machine also have very > limited vCPU and memory, so booting serveral VMs to establish the tricircle > and two bottom pods test bed also not possible. That's why Zhiyuan proposed > hacking way to do it. > > Best Regards > Chaoyi Huang ( joehuang ) > > ____

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

On Wed, May 4, 2016 at 10:38 AM, Shinobu Kinjo <shinobu...@gmail.com> wrote: > Hi Chaoyi, > > I didn't consider Ronghui's environment which I have no idea about. Anyhow this is my bad -; Sorry for that! Cheers, S > >> That's why Zhiyuan proposed hacking way t

Re: [openstack-dev] [tc] supporting Go

Could we kindly stop discussing radosgw at this moment? On Wed, May 4, 2016 at 6:47 PM, Thierry Carrez wrote: > Fox, Kevin M wrote: >> >> RadosGW has been excluded from joining the OpenStack community in part due >> to its use of c++. > > > I'm not sure I'd use the word

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

tion. glad to know that we are close to OpenStack > offical project criteria. > > Let's discuss the initial PTL election in weekly meeting, and start initial > PTL election after that if needed. > > Best Regards > Chaoyi Huang ( joehuang ) > _________

Re: [openstack-dev] [tc] supporting Go

- Could we kindly stop discussing radosgw at this moment? + Could we kindly stop discussing any particular application at this moment? On Wed, May 4, 2016 at 7:02 PM, Shinobu Kinjo <shinobu...@gmail.com> wrote: > Could we kindly stop discussing radosgw at this moment? > > On Wed, M

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

Thank you for suggestions. At this stage, we are just trying to become an official project. Cheers, S On Fri, May 6, 2016 at 2:50 AM, Doug Hellmann <d...@doughellmann.com> wrote: > Excerpts from Mike Perez's message of 2016-05-05 09:59:58 -0700: >> On 14:40 Apr 30, Shinobu Kinjo

  1   2   >