Re: [openstack-dev] [tc] [all] [glance] On operating a high throughput or otherwise team

Erno, TBH, you clearly haven't taken the time to understand what I meant to say here. Clearly, thus self-justifying my email about ML discussions. Hence, I do not want to spend too much time writing a response. There are a few things that struck, so comments inline. Also, I do not want to comment

Re: [openstack-dev] [Congress] Nominating Anusha Ramineni and Eric Kao for core reviewer

+1. On 2016/05/14 9:16, Tim Hinrichs wrote: Hi all, I'm writing to nominate Anusha Ramineni and Eric Kao as Congress core reviewers. Both Anusha and Eric have been active and consistent contributors in terms of code, reviewing, and interacting with the community since September--for all of

Re: [openstack-dev] [Storlets] Swift copy middlleware

> I agree with Kota, and I think this is the easiest way to fix the problem. I noticed that placing storlets_middleware outside copy may require some changes about slo handling, because now it is assumed that storlets_middleware is placed "inside" slo, right? (I noticed this just after sending

Re: [openstack-dev] [Storlets] Swift copy middlleware

Hi Eran and Kota, > For temprary, that would work but I thought we could (*not sure*) fix the > issue just replace the order of pipeline, right? (i.e. storlets handler > should be the left of copy middleware) That is because the storlets middlware > have the logic to translate

Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes

On Sun, May 15, 2016 at 10:49:39PM +, Hongbin Lu wrote: > Hi all, > > This is a continued discussion from the design summit. For recap, Magnum > manages bay nodes by using ResourceGroup from Heat. This approach works but > it is infeasible to manage the heterogeneity across bay nodes, which

Re: [openstack-dev] [nova][neutron] Is it still valid/supported to create a network with a br- id?

On Sun, May 15, 2016 at 3:56 PM, Sean M. Collins wrote: > Matt Riedemann wrote: >> The nova create-server API allows passing a network id that's prefixed with >> br- [1]. That was added due to this bug from Folsom [2]. >> >> I'm wondering if that's still valid? Looking at the

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

Hi, Shinobu, You found a bug, yeah. The design has been moved to the master branch, so the description: 'Note: Stateless proposal is working on the “experiment” branch:' 'https://github.com/openstack/tricircle/tree/experiment' Just been removed from the design blueprint as you

Re: [openstack-dev] [Storlets] Swift copy middlleware

Hey Eran, This is what I was concerning in Bristol Hackathon :/ > As a quick and temporary resolution I have changes the tox.ini dependency > to be 2.7.0 > Instead of master. We still need, however, to port the code accordingly, For temprary, that would work but I thought we could (*not sure*)

Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes

Hi, I think, user also want to specify the deleting node. So we should manage “node” individually. For example: $ magnum node-create —bay … $ magnum node-list —bay $ magnum node-delete $NODE_UUID Anyway, if magnum want to manage a lifecycle of container infrastructure. This feature is

Re: [openstack-dev] [cross-project][infra][keystone] Moving towards a Identity v3-only on Devstack - Next Steps

On 13 May 2016 at 04:15, Sean Dague wrote: > On 05/12/2016 01:47 PM, Morgan Fainberg wrote: > > This also comes back to the conversation at the summit. We need to > > propose the timeline to turn over for V3 (regardless of > > voting/non-voting today) so that it is possible to

Re: [openstack-dev] [nova][neutron] Is it still valid/supported to create a network with a br- id?

> On May 15, 2016, at 10:17 AM, Matt Riedemann > wrote: > >> On 5/15/2016 10:56 AM, Sean M. Collins wrote: >> Matt Riedemann wrote: >>> The nova create-server API allows passing a network id that's prefixed with >>> br- [1]. That was added due to this bug from

Re: [openstack-dev] [Openstack-operators] [glance] glance-registry deprecation: Request for feedback

> On 14 May 2016, at 5:36 AM, Flavio Percoco wrote: > >> On 5/12/16 9:20 PM, Sam Morrison wrote: >> >> We find glance registry quite useful. Have a central glance-registry api >> is useful when you have multiple datacenters all with glance-apis and >> talking back to a

[openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes

Hi all, This is a continued discussion from the design summit. For recap, Magnum manages bay nodes by using ResourceGroup from Heat. This approach works but it is infeasible to manage the heterogeneity across bay nodes, which is a frequently demanded feature. As an example, there is a request

[openstack-dev] [Storlets] Swift copy middlleware

Today the Swift team has merged copy middleware - congrats! For us, however, it breaks the copy code path, which in fact can get much simpler now. As a quick and temporary resolution I have changes the tox.ini dependency to be 2.7.0 Instead of master. We still need, however, to port the code

Re: [openstack-dev] [cross-project][quotas][delimiter] Austin Summit - Design Session Summary

On 16:06 May 14, Nikhil Komawar wrote: > On 5/14/16 2:35 PM, Mike Perez wrote: > > Reading this thread, Nikhil who is speaking for the quota team is worried > > about > > the amount of overhead caused by governance, instead of first focusing on > > making something actually exist. I see quite a

Re: [openstack-dev] [cross-project][quotas][delimiter]My thoughts on how Delimiter uses generation-id for sequencing

Amrith, your code in SQL statements below is identical to mine in Python with two exceptions that make your code less scalable and more problematic: 1) You have your generation on a "resources" table instead of a "consumers" table, which means you have an extremely high likelihood of needing

Re: [openstack-dev] [cross-project][quotas][delimiter]My thoughts on how Delimiter uses generation-id for sequencing

Qijing, As a simple example, let's assume that I use this schema. I realize that it does not provide the resource provider thing that Jay talked about in a previous (couple of weeks ago) email, but I believe that it serves to illustrate how the generations are used. create table resources (

Re: [openstack-dev] [cross-project][quotas][delimiter]My thoughts on how Delimiter uses generation-id for sequencing

I'm not thrilled that there are two API's one for a quota check and one for a consumption, and where it is up to the caller to properly return the results of one to the other. I'd much rather have consume accept the quotas and the request and 'just do it'. With that approach, the generation id's

Re: [openstack-dev] [tc] [all] [glance] On operating a high throughput or otherwise team

I'm not sure why I'm spending one of these very rare sunny Sunday afternoons on this but perhaps it's just important enough. Thanks Nikhil and Chris for such a verbal start for the discussion. I will at least try to keep my part shorter. I will quote both of your e-mails by name from which one it

Re: [openstack-dev] [nova][neutron] Is it still valid/supported to create a network with a br- id?

On 5/15/2016 10:56 AM, Sean M. Collins wrote: Matt Riedemann wrote: The nova create-server API allows passing a network id that's prefixed with br- [1]. That was added due to this bug from Folsom [2]. I'm wondering if that's still valid? Looking at the network.id data model in Neutron it

Re: [openstack-dev] [nova][neutron] Is it still valid/supported to create a network with a br- id?

Matt Riedemann wrote: > The nova create-server API allows passing a network id that's prefixed with > br- [1]. That was added due to this bug from Folsom [2]. > > I'm wondering if that's still valid? Looking at the network.id data model in > Neutron it doesn't look like it would be [3]. Wow.

Re: [openstack-dev] [cross-project][quotas][delimiter]My thoughts on how Delimiter uses generation-id for sequencing

On 05/15/2016 04:16 AM, Qijing Li wrote: Hi Vilobh, Here is my thoughts on how Delimiter uses generation-id to guarantee sequencing. Please correct me if I understand it wrong. First, the Delimiter need to introduce another model ResourceProvider who has two attributes: * resource_id *

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

On Sat, May 14, 2016 at 7:13 PM, Clint Byrum wrote: > Excerpts from Dieterly, Deklan's message of 2016-05-14 01:18:20 +: > > Python 2.x will not be supported for much longer, and let¹s face it, > > Python is easy, but it just does not scale. Nor does Python have the > >

Re: [openstack-dev] [cross-project][quotas][delimiter]My thoughts on how Delimiter uses generation-id for sequencing

Qijing, I don't believe that this is correct. I promised to send a description to the ML, I'll do that today. -amrith On Sun, 2016-05-15 at 01:16 -0700, Qijing Li wrote: > Hi Vilobh, > > Here is my thoughts on how Delimiter uses generation-id to guarantee > sequencing. Please correct me if

Re: [openstack-dev] [tc] [all] [glance] On operating a high throughput or otherwise team

Hey Nikhil, found this all very interesting. Given your next to last paragraph where you ask for a "judiciary" it sounds like there is more going on here than I'm aware of, so apologies if my comments are not entirely germane: I found some of your analysis very interesting and related to things

[openstack-dev] [Infra][Kuryr] New sub projects created

Hello all, We have created the following repositories as part of Kuryr: https://github.com/openstack?utf8=%E2%9C%93=kuryr Would love if anyone from Infra that has access can allow kuryr-core team to also be able to review/merge code in these new repositories. Would also love if the TC can

Re: [openstack-dev] [openstack-ansible] LBaaSv2 / Octavia support

On 14 May 2016 at 00:27, Major Hayden wrote: > > For what it's worth, I have a (somewhat dated) branch with Octavia support > in Github[1]. > > > Great stuff! - that's covered everything I've been looking at so far, except that we're not wanting to run neutron-server (and

[openstack-dev] [cross-project][quotas][delimiter]My thoughts on how Delimiter uses generation-id for sequencing

Hi Vilobh, Here is my thoughts on how Delimiter uses generation-id to guarantee sequencing. Please correct me if I understand it wrong. First, the Delimiter need to introduce another model ResourceProvider who has two attributes: - resource_id - generation_id The followings are the