Re: [openstack-dev] [openstack-operators][cinder] max_concurrent_builds in Cinder

On 23/05, Ivan Kolodyazhny wrote: > Hi developers and operators, > I would like to get any feedback from you about my idea before I'll start > work on spec. > > In Nova, we've got max_concurrent_builds option [1] to set 'Maximum number > of instance builds to run concurrently' per each compute.

Re: [openstack-dev] [Fuel] YAQL console for master node

Hi, thank you Stas, long awaited tool :) Using it right now on the latest Fuel-10.0, very helpful and saves a lot of time (switching between nodes to test yaql for different roles is super cool). Regards, Alex On Tue, May 24, 2016 at 12:50 PM, Stanislaw Bogatkin

Re: [openstack-dev] [higgins] Should we rename "Higgins"?

Before considering a project rename.m, I suggest you seek guidance from the OpenStack technical committee, and/or the OpenStack-infra team. There is probably a simple workaround to the concern voiced below. -- Adrian > On May 24, 2016, at 1:37 AM, Shuu Mutou wrote: >

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

Excerpts from Geoff O'Callaghan's message of 2016-05-24 15:31:28 +1000: > > > On 24 May 2016, at 3:13 PM, Clint Byrum wrote: > > > > > [snip] > > > those other needs. Grab a python developer, land some code, and your > > feature is there. > > s/python/whateverlanguage/ >

Re: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

On Tue, May 24, 2016 at 1:34 AM, Duncan Thomas wrote: > Cinder bugs list was far more manageable once this had been done. > > It is worth sharing the tool for this? I realise it's fairly trivial to > write one, but some standardisation on the comment format etc seems >

[openstack-dev] Plans to converge on one ldap client?

Hi All, Are there any plans to converge on one ldap client across projects? Some projects have moved to ldap3 and others are using pyldap (both are in global requirements). The issue we're running into in Ubuntu is that we can only have one ldap client in Ubuntu main, while the others will live

[openstack-dev] [nova] Stable disk device instance rescue reviews for libvirt and possible implementation by other virt drivers

Hello all, https://review.openstack.org/#/q/topic:bp/virt-rescue-stable-disk-devices I've been aimlessly pushing my patches around for this spec for a while now and would really appreciate reviews from the community. Tempest and devstack patches are also included in the above topic, reviews

Re: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

On Tue, May 24, 2016 at 11:00:35AM +0200, Markus Zoeller wrote: > On 24.05.2016 09:34, Duncan Thomas wrote: > > Cinder bugs list was far more manageable once this had been done. > > > > It is worth sharing the tool for this? I realise it's fairly trivial to > > write one, but some standardisation

Re: [openstack-dev] [nova] Suggest to not deprecate os-migrations API

On 05/23/2016 10:16 PM, Zhenyu Zheng wrote: > Hi All, > > According > to > https://github.com/openstack/nova/blob/master/releasenotes/notes/os-migrations-ef225e5b309d5497.yaml > , we are going to deprecate the old os-migrations API, and two new APIs: > /servers/{server uuid}/migrations and

Re: [openstack-dev] [Openstack-dev] scaling nova kvm and neutron l3-ha and ml2+openvswitch

Hi! Recently I performed scale testing of Neutron L3 HA Liberty. Test plan and test results can be found http://docs.openstack.org/developer/performance-docs/index.html. On Tue, May 24, 2016 at 3:21 PM, Tobias Urdin wrote: > Hello, > > (I didn't have any luck with

Re: [openstack-dev] [Infra][Cinder] Nominating Zadara Storage VPSA CI for voting permissions

On Tue, May 24, 2016 at 09:47:23AM +0300, Shlomi Avihou wrote: > Hello, > > > > I’d like to nominate Zadara Storage VPSA CI system for voting permissions > in the Cinder program. > > The CI system has been posting comments (non-voting) for the past 24 days. > > > > *Third Party system info:

Re: [openstack-dev] [fuel] release version numbers: let's use semvers

Hey Zigo, In Python community there's a PEP-440 [1] that defines a versioning scheme. The thing you should know is, the PEP __is not__ compatible with semver, and it's totally fine to have two components version. So I don't think we should force version changes from two-components to

[openstack-dev] [Openstack-dev] scaling nova kvm and neutron l3-ha and ml2+openvswitch

Hello, (I didn't have any luck with this question on the openstack-operators list so I'm throwing it out here to see if I can catch anyone, according to Assaf he knew a couple of you devs running a similar environment, if not feel free to do what you please with this email hehe) I'm gonna give

Re: [openstack-dev] [Openstack-operators] [nova] Is verification of images in the image cache necessary?

Hi John and Matt, I actually have a spec and patch up for review addressing some of what you’re referring to below. https://review.openstack.org/#/c/314222/ https://review.openstack.org/#/c/312210/ I think you’re quite right that the existing ImageCacheManager code serves little purpose. What

[openstack-dev] [ironic][neutron] bonding?

Hi, There's rumors floating around about Neutron having a bonding model in the near future. Are there any solid plans for that? For context, as part of the multitenant networking work, ironic has a portgroup concept proposed, where operators can configure bonding for NICs in a baremetal machine.

[openstack-dev] [Kuryr] - IRC Meeting time change

Hello Everyone, Just wanted to let you all know we changed our even biweekly IRC meeting time. It is now one hour earlier. The new meeting time is *every even Monday at 14:00 UTC in #openstack-meeting-4* You can see the changing patch here [1] Thanks Gal. [1]

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

On 24 May 2016 at 02:28, Gregory Haynes wrote: > On Mon, May 23, 2016, at 05:24 PM, Morgan Fainberg wrote: > > I really do not want to "special case" swift. It really doesn't go with > the spirit of inclusion. > > > I am not sure how inclusion is related to special casing.

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

+1 ttx. ("I'd prefer if we didn't have to special-case anyone") -- Dims On Tue, May 24, 2016 at 6:24 AM, Thierry Carrez wrote: > Morgan Fainberg wrote: >> >> [...] If we are accepting golang, I want it to be clearly >> documented that the expectation is it is used

Re: [openstack-dev] [nova] Is verification of images in the image cache necessary?

On Tue, 24 May 2016, Matthew Booth wrote: I understand that corruption of bits on disks is a thing, but it's a thing for more than just the image cache. I feel that this is a problem much better solved at other layers, prime candidates being the block and filesystem layers. There are existing

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

On Tue, 24 May 2016, Thierry Carrez wrote: Chris Dent wrote: So that, of course, leads back to the original question: Is OpenStack supposed to be a unitary. As a data point, since I heard that question rhetorically asked quite a few times over the past year... There is an old answer to that,

[openstack-dev] [all][oslo_config] Improving Config Option Help Texts

Hi all, Based on the not yet merged spec of categorized config options [0] some project seems to have started improving the config option help texts. This is great but I noticed scary trend on clutter to be added on these sections. Now looking individual changes it does not look that bad at all

Re: [openstack-dev] [Openstack-operators] [nova] Is verification of images in the image cache necessary?

On Tue, May 24, 2016 at 11:06 AM, John Garbutt wrote: > On 24 May 2016 at 10:16, Matthew Booth wrote: > > During its periodic task, ImageCacheManager does a checksum of every > image > > in the cache. It verifies this checksum against a previously stored

[openstack-dev] [Fuel] YAQL console for master node

Hi all, as you maybe know, new conditions for Fuel tasks were recently (in master and mitaka branches) introduced. Right after this I got several questions like 'hey, how can I check my new condition?' Answer could be 'use standard yaql console', but it hasn't have Fuel internal yaql functions

[openstack-dev] update congress

Hi Tim and all, May I ask how to update the congress version with the Tokyo Hands on Lab environment? cause I use the command ＂openstack congress list version＂ it show the congress is 2013's version. The reason why I want to update it is that I write a demo driver, which I want to push data into

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

Morgan Fainberg wrote: [...] If we are accepting golang, I want it to be clearly documented that the expectation is it is used exclusively where there is a demonstrable case (such as with swift) and not a carte blanche to use it wherever-you-please. I want this to be a social contract looked

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

Chris Dent wrote: [...] I don't really know. I'm firmly in the camp that OpenStack needs to be smaller and more tightly focused if a unitary thing called OpenStack expects to be any good. So I'm curious about and interested in strategies for figuring out where the boundaries are. So that, of

Re: [openstack-dev] [Openstack-operators] [nova] Is verification of images in the image cache necessary?

On 24 May 2016 at 10:16, Matthew Booth wrote: > During its periodic task, ImageCacheManager does a checksum of every image > in the cache. It verifies this checksum against a previously stored value, > or creates that value if it doesn't already exist.[1] Based on this >

[openstack-dev] [fuel] release version numbers: let's use semvers

Hi, A number of Fuel components were previously tagged as "9.0". This isn't compatible with the semver scheme. Could we agree to switch to x.y.z going forward? Cheers, Thomas Goirand (zigo) __ OpenStack Development Mailing

[openstack-dev] [Nova] Live migration meeting today

Agenda: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration Please add items if you want to guarantee time to talk about them. Paul __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [nova] Is verification of images in the image cache necessary?

During its periodic task, ImageCacheManager does a checksum of every image in the cache. It verifies this checksum against a previously stored value, or creates that value if it doesn't already exist.[1] Based on this information it generates a log message if the image is corrupt, but otherwise

Re: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

On 24.05.2016 09:34, Duncan Thomas wrote: > Cinder bugs list was far more manageable once this had been done. > > It is worth sharing the tool for this? I realise it's fairly trivial to > write one, but some standardisation on the comment format etc seems > valuable, particularly for Q/A folks

[openstack-dev] [oslo] Log spool in the context

Hi, I have a spec: https://review.openstack.org/227766 and implementation: https://review.openstack.org/316162 for adding a spooling logger to oslo.log. Neither is merged yet, reviews welcome. Looking at how I'd actually integrate this into Nova, most classes do: LOG =

[openstack-dev] [Nova] change console proxy URL for cells v2 ?

I am implementing the following spec and have encountered a problem related to the form of the console proxy URL provided to uses. https://specs.openstack.org/openstack/nova-specs/specs/newton/approved/convert-consoles-to-objects.html The spec changes the representation of the console auth

[openstack-dev] [nova] [infra] resolving issues with Intel NFV CI

Hi all, There is an issue with jobs under Intel NFV CI not being registered. The issue is currently being investigated. ThirdPartySystems Wiki was updated. Updates to follow. Waldemar Znoinski -- Intel Research and Development

[openstack-dev] [higgins] Should we rename "Higgins"?

Hi all, Unfortunately "higgins" is used by media server project on Launchpad and CI software on PYPI. Now, we use "python-higgins" for our project on Launchpad. IMO, we should rename project to prevent increasing points to patch. How about "Gatling"? It's only association from Magnum. It's not

Re: [openstack-dev] [magnum][kuryr] Nested containers networking

Hi Hongbin, Thank you for starting this thread. The person that is going to work on this integration is Fawad (CC'ed) and hopefully others will help him (We have another person from Huawei that showed intrest in working on this). I think Fawad, given that he is the primary person working on this

Re: [openstack-dev] [openstack-operators][cinder] max_concurrent_builds in Cinder

On 24 May 2016 at 05:46, John Griffith wrote: > > ​Just curious about a couple things: Is this attempting to solve a > problem in the actual Cinder Volume Service or is this trying to solve > problems with backends that can't keep up and deliver resources under heavy >

Re: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

Cinder bugs list was far more manageable once this had been done. It is worth sharing the tool for this? I realise it's fairly trivial to write one, but some standardisation on the comment format etc seems valuable, particularly for Q/A folks who work between different projects. On 23 May 2016

[openstack-dev] [Infra][Cinder] Nominating Zadara Storage VPSA CI for voting permissions

Hello, I’d like to nominate Zadara Storage VPSA CI system for voting permissions in the Cinder program. The CI system has been posting comments (non-voting) for the past 24 days. *Third Party system info: * https://wiki.openstack.org/wiki/ThirdPartySystems/ZadaraStorage_VPSA_CI *Ci

<    1   2