[openstack-dev] [Fuel] Nominate Denys Klepikov for fuel-docs core

Fuelers, I'd like to nominate Denys Klepikov for the fuel-docs-core team. He has contributed a lot into documentation to Fuel over the past several months with being diligent reviewer. He has been working hard to improve UX, clarifying complex aspects and providing detailed feedback for the alre

Re: [openstack-dev] [neutron] Adding results to extension callbacks (ml2 port_update ext handling).

Hi Bob, Miguel On Tue, Jul 14, 2015 at 5:19 PM, Robert Kukura wrote: > I haven't had a chance to review this patch in detail yet, but am > wondering if this is being integrated with ML2 as an extension driver? If > so, that should clearly address how dictionaries are extended and input > values

Re: [openstack-dev] [Fuel] Nominate Denys Klepikov for fuel-docs core

+1 Great work, Denys! On Wed, Jul 15, 2015, 00:04 Irina Povolotskaya wrote: > Fuelers, > > I'd like to nominate Denys Klepikov for the fuel-docs-core team. > > He has contributed a lot into documentation to Fuel over the past several > months with being diligent reviewer. > > He has been workin

Re: [openstack-dev] [neutron][hyper-v] Instance can't get fixed ip on hyper-v compute node

Hi there, I finally figured it out that the problem is caused by the mismatch of the VLAN range between my openstack installation and the physical switch setting. Thank you all for your kindly help. Best regards, Lily Xing On Mon, Jul 6, 2015 at 2:02 PM, Lily.Sing wrote: > Hi Claudiu, > > Than

[openstack-dev] [opesntack-puppet] mistral puppet

Hi all, I have puppet for mistral and i would like to contribute it. Any objection/comments? Thanks Limor Stotland ALCATEL-LUCENT SENIOR SOFTWARE ENGINEER CLOUDBAND BUSINESS UNIT 16 Atir Yeda St. Kfar-Saba 44643, ISRAEL T:  +972 (0) 9 793 3166 M: +972 (0) 54 585 3736 limor.bort...@alcatel-lucent.

[openstack-dev] [openstack-puppet] mistral puppet

Hi all, I have puppet for mistral and i would like to contribute it. Any objection/comments? Thanks Limor Stotland ALCATEL-LUCENT SENIOR SOFTWARE ENGINEER CLOUDBAND BUSINESS UNIT 16 Atir Yeda St. Kfar-Saba 44643, ISRAEL T:  +972 (0) 9 793 3166 M: +972 (0) 54 585 3736 limor.bort...@alcatel-lucent.

Re: [openstack-dev] [mistral] A new BP - Support large datasets being passed

I agree. We will try to allocate someone soon for this but it seems that all are very busy. With the use cases I had encountered – the columns listed in the BP were OK. Do you have any suggestion for other columns? Another important thing – when I changed the columns just for testing purposes

Re: [openstack-dev] [Openstack][nova] proxy quota/limits info from neutron

2015-07-15 5:14 GMT+08:00 Matt Riedemann : > > > On 7/14/2015 3:43 PM, Cale Rath wrote: > >> Hi, >> >> I created a patch to fail on the proxy call to Neutron for used limits, >> found here: https://review.openstack.org/#/c/199604/ >> >> This patch was done because of this: >> >> http://docs.openst

Re: [openstack-dev] [nova] Switching the bug status of ~200 bugs at once; Problem?

Matt Riedemann wrote on 07/14/2015 07:28:45 PM: > From: Matt Riedemann > To: [email protected] > Date: 07/14/2015 07:40 PM > Subject: Re: [openstack-dev] [nova] Switching the bug status of ~200 > bugs at once; Problem? > [...] > > Markus, > > Since you'll be at the meetup nex

Re: [openstack-dev] [Openstack][nova] proxy quota/limits info from neutron

Some comments inline. Salvatore On 15 July 2015 at 10:24, Alex Xu wrote: > > > 2015-07-15 5:14 GMT+08:00 Matt Riedemann : > >> >> >> On 7/14/2015 3:43 PM, Cale Rath wrote: >> >>> Hi, >>> >>> I created a patch to fail on the proxy call to Neutron for used limits, >>> found here: https://review.o

Re: [openstack-dev] [keystone] Liberty SFE Request - Dynamic Policies

Adam Young wrote: > On 07/03/2015 08:36 AM, Samuel de Medeiros Queiroz wrote: >> Hi Thierry, >> >> Thanks for clarifying. A Spec Freeze Exception is what I was supposed >> to ask for. >> >> Rectifying: >> >> On behalf of the team working on the Dynamic Policies subject, I would >> like to ask for a

[openstack-dev] Why the the id can set when creating flavor.

It is uncommon that the id can be set when creating resource. Other resource can not, e.g. instance. I want to know why this is happend only in flavor. history logical or something else? -- Lei Zhang Blog: http://xcodest.me twitter/weibo: @jeffrey4l __

[openstack-dev] [Tricircle]Weekly Team Meeting 2015.07.15

Hi Team, We will have our weekly meeting today at UTC1300, we will be discussing Saggi's new patch https://review.openstack.org/201224 -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Prooduct Line Huawei Technologies Co,. Ltd Email: [email protected] Office: Huawei In

Re: [openstack-dev] [all] Setting epoch in setup.cfg??

Monty Taylor wrote: > [...] > An epoch, being a tool designed for package maintainers to solve package > maintainer problems, is not a tool designed to solve ease of > communication issues for regular users. Most regular users immediately > grasp that 2.0.0 > 1.0.0. Most regular users do NOT intuit

[openstack-dev] [cinder] Need a new release of os-brick for Python 3

Hi, The latest release of os-brick is not compatible with Python 3. Different patches were merged to fix Python 3 support. "tox -e py34" now executes all tests and all tests pass on Python 3.4. I need a release of os-brick to port Cinder to Python 3. A Python 3 issue in os-brick blocks my 4

Re: [openstack-dev] [requirements][all] policy on approving constraint changes

Doug Hellmann wrote: > At one point Robert proposed that we change the policy for approving > constraint changes like https://review.openstack.org/#/c/201408/ to > allow a single reviewer to approve it, assuming the tests were green. > Is that our current policy, or are we waiting for the integrati

[openstack-dev] OSPd, post-installation changes/new components

Hi, Are there any suggested steps on how to execute post-deployment (OSPd) tuning of components? I see two possible scenarios, but maybe they are the same: a) configuration changes to a component which is managed by OSPd (cinder, nova, etc); b) installation of additional components (Sahara, Tro

Re: [openstack-dev] [mistral] A new BP - Support large datasets being passed

> On 15 Jul 2015, at 14:23, ELISHA, Moshe (Moshe) > wrote: > > With the use cases I had encountered – the columns listed in the BP were OK. > Do you have any suggestion for other columns? Nothing specific at the moment. Need to carefully research that in a BP scope. > Another important thing

Re: [openstack-dev] [openstack-puppet] mistral puppet

Limor, No objections from my side. Just follow regular OpenStack procedures to do it. Thanks Renat Akhmerov @ Mirantis Inc. > On 15 Jul 2015, at 14:19, BORTMAN, Limor (Limor) > wrote: > > Hi all, > I have puppet for mistral and i would like to contribute it. > Any objection/comments? > >

Re: [openstack-dev] [glance] Progress of the Python 3 port

Hi, On 09/07/2015 16:29, Ian Cordasco wrote: Thanks for your hard work Victor! I'll bring up a new release today in the Glance meeting (currently running) and see if Nik and I can bug the release managers for a new release today. Any update on this release? In the meeting report, I read: "14:

Re: [openstack-dev] [openstack-announce] End of life for managed stable/icehouse branches

Thomas Goirand wrote: > On 07/14/2015 10:29 AM, Ihar Hrachyshka wrote: >> On 07/14/2015 12:33 AM, Thomas Goirand wrote: >>> Effectively, under these conditions, I am giving up doing any kind >>> of coordination between distros for security patches of Icehouse. >>> :( >> >> As far as I know, there w

Re: [openstack-dev] [openstack-announce] End of life for managed stable/icehouse branches

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/14/2015 09:14 PM, Thomas Goirand wrote: > On 07/14/2015 10:29 AM, Ihar Hrachyshka wrote: >> On 07/14/2015 12:33 AM, Thomas Goirand wrote: >>> I missed this announce... >> >>> On 07/02/2015 05:32 AM, Jeremy Stanley wrote: Per the Icehouse

Re: [openstack-dev] [Openstack][nova]

On 14 July 2015 at 21:43, Cale Rath wrote: > Hi, > > I created a patch to fail on the proxy call to Neutron for used limits, > found here: https://review.openstack.org/#/c/199604/ > > This patch was done because of this: > http://docs.openstack.org/developer/nova/project_scope.html?highlight=proxy

Re: [openstack-dev] [opesntack-puppet] mistral puppet

On 07/15/2015 04:17 AM, BORTMAN, Limor (Limor) wrote: > Hi all, > I have puppet for mistral and i would like to contribute it. > Any objection/comments? We have a recent Wiki page that explains this process: https://wiki.openstack.org/wiki/Puppet/New_module Please let us know any feedback, >

Re: [openstack-dev] OpenStack Mitaka (三鷹) - Our next release name has been selected

Thank everyone in the community for the great collaboration. :) It seems like Mitaka is hosting great animations everyone loves, Ghibli Museum (http://www.ghibli-museum.jp/en/). We should probably plan an official trip there during Tokyo Summit. :) On Wed, Jul 15, 2015 at 4:00 AM Ian Cordasco

[openstack-dev] Fw:Re: [magnum][bp] Power Magnum to run on metal with Hyper

On Wed, Jul 15, 2015 at 6:52 PM, Peng Zhao < [email protected] > wrote: -- Original -- From: “Adrian Otto”< adrian.otto@rackspace. com >; Date: Wed, Jul 15, 2015 02:31 AM To: “OpenStack Development Mailing List (not for usage questions)“< openstack-dev@ lists.open

[openstack-dev] [NFV][Telco] July 15th meeting cancelled

Hi all, I'm unable to make the meeting today and was unable to get an alternative facilitator to run the meeting, as such it is canceled. Please note that I am still seeking comment on: [Openstack-operators] [nfv][telco] On-going management of telcowg-usecases repository http://lists.

Re: [openstack-dev] [Fuel][Fuel-Packaging][Fuel-CI][Fuel-Infra] How to Deal with CI Failures Induced by Libraries Requirements Drift

Vladimir, We do break developer's workflow in stable branches if we force them to use our local mirrors. Yes, we can hardcode mirror url in tox.ini or something like that. But it looks like a hack for me. Packaging systems were created in order to add ability to set up predictable environment wit

Re: [openstack-dev] July 15th meeting cancelled

Hi Steve I missed the linked mail as it was sent to the openstack-operators list, not openstack-dev - was that intentional? On the substance of the mail, +1 to adding Daniel and Yuriy to the core reviewers list. cheers Calum -Original Message- From: Steve Gordon [mailto:sgor...@redha

Re: [openstack-dev] [Fuel][Fuel-Packaging][Fuel-CI][Fuel-Infra] How to Deal with CI Failures Induced by Libraries Requirements Drift

Dmitry You can fix it by declaring that developer should use particular pypi mirror. On Wed, Jul 15, 2015 at 2:46 PM, Dmitry Pyzhov wrote: > Vladimir, > > We do break developer's workflow in stable branches if we force them to > use our local mirrors. Yes, we can hardcode mirror url in tox.ini

[openstack-dev] Why do we need python-fasteners and not just oslo.concurrency?

Hi, I've seen that the latest version of taskflow needs fasteners, which handles lock stuff. Why can't this goes into oslo.concurrency? Cheers, Thomas Goirand (zigo) __ OpenStack Development Mailing List (not for usage ques

Re: [openstack-dev] [glance] Progress of the Python 3 port

Victor, That was related to stable/kilo branch as stated on the line above: 14:39:58 jokke_: was that you on python-glanceclient stable/kilo 14:39:59 also queued up bunch of stable stuff ... glance_store gotta wait until Cinder gets their client requirements fixed, but glanceclient backports

[openstack-dev] [Cinder][Rally] Cinder API Rally Coverage

Hi Stackers, I've created a short list of Cinder API functions (only API v2 and extensions) and compared it to rally scenarios [2]. We've got pretty good coverage for volumes, snapshots and backups APIs. But we have not any scenarios for the rest of API methods. Looking throw the review requests

[openstack-dev] [puppet] Run neutron db sync also for each neutron module

Hello, I'm not 100% sure about patch [1] I've sent and I'm looking into ideas. Neutron API in liberty will require lbaas, fwaas and vpnaas packages installed if they are set in service_plugins or it won't even start the neutron service. For the modules to work one also needs to run neutron-db-ma

Re: [openstack-dev] [nova][qa] turbo-hipster seems to be out to lunch

Everything is up and running again FYI. Let me know if you spot any further problems. Cheers, Josh On Tue, Jul 14, 2015 at 12:21 AM, Matt Riedemann wrote: > > > On 7/12/2015 1:50 AM, Joshua Hesketh wrote: > >> Hey, >> >> Yes, sorry, I only discovered this yesterday. I should have updated the >>

[openstack-dev] How to get the Physical switch data at the openstack neutron

Hi All, I am working on to display the physical switch topology at the Horizon , i mean the if there are four switches are interconnected . need display same topology at the openstack Horizon. is there any way to get the physical switch topology ?? thanks, M.Ramu

[openstack-dev] [oslo] Need new release of stable oslotest with capped mock

Hello, oslo team. With recent mock nightmare we should not release a new stable version of oslotest so that projects that depend on oslotest but don't directly depend on mock will be unblocked in gate. I found out about this from this review: [0] It fails because stable oslotest 1.5.1 have uncapp

Re: [openstack-dev] How to get the Physical switch data at the openstack neutron

Hi there! On 15/07/15 14:02, Ram Mallagundla wrote: Hi All, I am working on to display the physical switch topology at the Horizon , i mean the if there are four switches are interconnected . need display same topology at the openstack Horizon. is there any way to get the physical switch

[openstack-dev] [all][ptl][release] need to pick release models

PTLs, The release team is working on cleaning up the release-related tags in the governance repository. As part of that work, we want each official repository to have a tag indicating its release model. I have a patch up [1] to do this, but need your help to get the details right. Please look thr

[openstack-dev] [neutron][db] online-schema-migrations patch landed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi all, since it's a high impact change in the migration tree, I wanted to drop an email to everyone affected (basically, anyone who wants to introduce a new migration from now on). So there was a proposal to split migration rules into independent

[openstack-dev] [all] Script to merge sort log files

I expect there are several existing solutions to this problem, but here's mine (attached). Matt -- Matthew Booth Red Hat Engineering, Virtualisation Team Phone: +442070094448 (UK) GPG ID: D33C3490 GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490 log_merge.sh Description: application

[openstack-dev] [murano] [congress] murano congress integration test - trusts

Hi all our congress integration tests were broken by the change [1] (trusts enabled by default). However I suspect problem could be with initialization congress client [2] or in python-congressclient. Any ideas about that? Thanks [1] https://review.openstack.org/#/c/194615/ [2] https://gi

Re: [openstack-dev] [oslo] Need new release of stable oslotest with capped mock

On Wed, Jul 15, 2015 at 4:14 PM Yuriy Taraday wrote: > Hello, oslo team. > > With recent mock nightmare we should not release a new stable version of > oslotest so that projects that depend on oslotest but don't directly depend > on mock will be unblocked in gate. > > I found out about this from

Re: [openstack-dev] Why do we need python-fasteners and not just oslo.concurrency?

On Wed, Jul 15, 2015 at 3:32 PM Thomas Goirand wrote: > I've seen that the latest version of taskflow needs fasteners, which > handles lock stuff. Why can't this goes into oslo.concurrency? > It already did (in a way): https://review.openstack.org/185291 _

Re: [openstack-dev] [neutron][db] online-schema-migrations patch landed

On 7/15/15 9:26 AM, Ihar Hrachyshka wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi all, since it's a high impact change in the migration tree, I wanted to drop an email to everyone affected (basically, anyone who wants to introduce a new migration from now on). So there was a prop

Re: [openstack-dev] How to get the Physical switch data at the openstack neutron

On 07/15/2015 09:02 AM, Ram Mallagundla wrote: Hi All, I am working on to display the physical switch topology at the Horizon , i mean the if there are four switches are interconnected . need display same topology at the openstack Horizon. is there any way to get the physical switch topology

Re: [openstack-dev] How to get the Physical switch data at the openstack neutron

On Wed, Jul 15, 2015 at 8:02 AM, Ram Mallagundla wrote: > Hi All, > > > I am working on to display the physical switch topology at the Horizon , > i mean the if there are four switches are interconnected . need display > same topology at the openstack Horizon. > > > is there any way to get the p

Re: [openstack-dev] [tc] [all] thinking additional tags

The "next tags" workgroup will be having a meeting this week on Friday at 14:00 UTC in #openstack-meeting. Join us if you're interested ! In the mean time, we are braindumping at: https://etherpad.openstack.org/p/next-tags-wg See you there, -- Thierry Carrez (ttx) _

Re: [openstack-dev] [neutron][db] online-schema-migrations patch landed

Do you reckon that the process that led to creating a migration like [1] should also be documented in devref? That might be helplful for developers, unless that process is already documented elsewhere. Salvatore [1] https://review.openstack.org/#/c/202013/1 On 15 July 2015 at 15:54, Mike Bayer

Re: [openstack-dev] [neutron][db] online-schema-migrations patch landed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/15/2015 04:03 PM, Salvatore Orlando wrote: > Do you reckon that the process that led to creating a migration > like [1] should also be documented in devref? That might be > helplful for developers, unless that process is already documented > el

[openstack-dev] [nova] Proposal for an Experiment

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Changing the architecture of a complex system such as Nova is never easy, even when we know that the design isn't working as well as we need it to. And it's even more frustrating because when the change is complete, it's hard to know if the improveme

Re: [openstack-dev] [nova] Proposal for an Experiment

On 7/15/2015 9:18 AM, Ed Leafe wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Changing the architecture of a complex system such as Nova is never easy, even when we know that the design isn't working as well as we need it to. And it's even more frustrating because when the change is co

Re: [openstack-dev] [Openstack][nova] proxy quota/limits info from neutron

On 7/15/2015 3:24 AM, Alex Xu wrote: 2015-07-15 5:14 GMT+08:00 Matt Riedemann mailto:[email protected]>>: On 7/14/2015 3:43 PM, Cale Rath wrote: Hi, I created a patch to fail on the proxy call to Neutron for used limits, found here: https://re

Re: [openstack-dev] [Openstack][nova] proxy quota/limits info from neutron

On 7/15/2015 4:22 AM, Salvatore Orlando wrote: Some comments inline. Salvatore On 15 July 2015 at 10:24, Alex Xu mailto:[email protected]>> wrote: 2015-07-15 5:14 GMT+08:00 Matt Riedemann mailto:[email protected]>>: On 7/14/2015 3:43 PM, Cale Rath wrote:

Re: [openstack-dev] [Openstack][nova]

On 7/15/2015 5:41 AM, John Garbutt wrote: On 14 July 2015 at 21:43, Cale Rath wrote: Hi, I created a patch to fail on the proxy call to Neutron for used limits, found here: https://review.openstack.org/#/c/199604/ This patch was done because of this: http://docs.openstack.org/developer/nova

Re: [openstack-dev] [nova] Proposal for an Experiment

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 07/15/2015 09:49 AM, Matt Riedemann wrote: > Without reading the whole thread, couldn't you just do a feature > branch (but that would require reviews in gerrit which we don't > want), or fork the repo in github and just hack on it there without

Re: [openstack-dev] Why do we need python-fasteners and not just oslo.concurrency?

For the same reason we don't move all of sqlalchemy into oslo.db. This is further explained @ - https://wiki.openstack.org/wiki/Oslo/CreatingANewLibrary#Choosing_a_Name - http://specs.openstack.org/openstack/oslo-specs/specs/policy/naming-libraries.html#proposed-policy Taskflow, tooz and oth

Re: [openstack-dev] [nova] Proposal for an Experiment

I do like experiments! What about going even farther and trying to integrate somehow into mesos? https://mesos.apache.org/documentation/latest/mesos-architecture/ Replace the hadooop executor, MPI executor with a 'VM executor' and perhaps we could eliminate a large part of the scheduler code (

Re: [openstack-dev] [Fuel] Separate repo for Fuel Agent

I'm glad to announce that everything about this task is done. ISO build job uses this new repository [1]. BVT is green. Fuel Agent rpm spec has been moved to the new repo and perestroika has also been switched to build fuel-agent package from the new repo. The only difference that could potentially

[openstack-dev] [neutron] What does flavor mean for a network?

I've been reading available docs about the forthcoming Neutron flavors framework, and am not yet sure I understand what it means for a network. Is it a way for an admin to provide a particular kind of network, and then for a tenant to know what they're attaching their VMs to? How does it diff

[openstack-dev] [all][ptl][release] New library release request process

PTLs and release liaisons, We are ready to take the next step in implementing the new library release process, and start using gerrit for release request reviews. The new repository openstack/releases is set up with back-history for all of our current releases. There are full instructions in the

Re: [openstack-dev] [Fuel] Separate repo for Fuel Agent

Nice work, Vladimir. Thank you for pushing this, it's really important step to decouple things from consolidated repository. -- Best regards, Oleg Gelbukh On Wed, Jul 15, 2015 at 6:47 PM, Vladimir Kozhukalov < [email protected]> wrote: > I'm glad to announce that everything about this tas

Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?

All, IMO virt_type does not properly describe bare metal deployments. What about using the compute_driver parameter? compute_driver = None (StrOpt) Driver to use for controlling virtualization. Options include: libvirt.LibvirtDriver, xenapi.XenAPIDriver, fake.FakeDriver, baremetal.BareMetalD

[openstack-dev] [nova][vmware] questions about some skipped tests in vmware/nsx ci

I was looking at NSX CI results on [1] which is related to volumes and noticed that tempest.api.compute.volumes.test_attach_volume.AttachVolumeTestJSON.test_attach_detach_volume is being skipped, is there a reason why? Attach and detach of volumes is a pretty basic operation for a virt driver i

[openstack-dev] [Nova] Device names supplied to the boot request

I'll keep this email brief since this has been a well known issue for some time now. Problem: Libvirt can't honour device names specified at boot for any volumes requested as part of block_device_mapping. What we currently do is in case they do get specified, we persist them as is, so that we can

Re: [openstack-dev] [neutron] What does flavor mean for a network?

On Wed, Jul 15, 2015 at 10:54 AM, Neil Jerram wrote: > I've been reading available docs about the forthcoming Neutron flavors > framework, and am not yet sure I understand what it means for a network. > > In reality, this is envisioned more for service plugins (e.g. flavors of LBaaS, VPNaaS, and

Re: [openstack-dev] [nova][vmware] questions about some skipped tests in vmware/nsx ci

On 7/15/2015 11:17 AM, Matt Riedemann wrote: I was looking at NSX CI results on [1] which is related to volumes and noticed that tempest.api.compute.volumes.test_attach_volume.AttachVolumeTestJSON.test_attach_detach_volume is being skipped, is there a reason why? Attach and detach of volumes

Re: [openstack-dev] [Magnum] Continuing with heat-coe-templates

On Sun, Jul 05, 2015 at 12:00:55AM +, Steven Dake (stdake) wrote: > Lars had a repo he maintains. Magnum had a repo it maintained. We > wanted one source of truth. The deal was we would merge all the > things into heat-coe-templates, delete larsks/heat-kubernetes and > delete the magnum temp

Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?

Maybe somehow I missed the point, but why not just use raw Nova flavors? They already abstract away irconic vs kvm vs hyperv/etc. Thanks, Kevin From: Daneyon Hansen (danehans) [[email protected]] Sent: Wednesday, July 15, 2015 9:20 AM To: OpenStack Development M

Re: [openstack-dev] [neutron] What does flavor mean for a network?

On Wed, Jul 15, 2015 at 9:25 AM, Kyle Mestery wrote: > On Wed, Jul 15, 2015 at 10:54 AM, Neil Jerram > wrote: > >> I've been reading available docs about the forthcoming Neutron flavors >> framework, and am not yet sure I understand what it means for a network. >> >> > In reality, this is envisi

Re: [openstack-dev] [neutron] What does flavor mean for a network?

> On Jul 15, 2015, at 9:54 AM, Neil Jerram wrote: > > I've been reading available docs about the forthcoming Neutron flavors > framework, and am not yet sure I understand what it means for a network. > > Is it a way for an admin to provide a particular kind of network, and then > for a tenant

Re: [openstack-dev] [Nova] Device names supplied to the boot request

On 7/15/2015 11:23 AM, Nikola Đipanov wrote: I'll keep this email brief since this has been a well known issue for some time now. Problem: Libvirt can't honour device names specified at boot for any volumes requested as part of block_device_mapping. What we currently do is in case they do get

Re: [openstack-dev] [cinder] Need a new release of os-brick for Python 3

On 10:45 Jul 15, Victor Stinner wrote: > Hi, > > The latest release of os-brick is not compatible with Python 3. > Different patches were merged to fix Python 3 support. "tox -e py34" > now executes all tests and all tests pass on Python 3.4. > > I need a release of os-brick to port Cinder to Pyt

[openstack-dev] [neutron] questions on neutron-db-migrations

Hello, I have noticed that neutron project got rid of neutron/db/migration/alembic_migrations/versions/HEAD file and renamed it to neutron/db/migration/alembic_migrations/versions/HEADS May I know the reason why this happened? I may have overlooked some documentation with respect to the change. I

Re: [openstack-dev] [Nova] Device names supplied to the boot request

On 7/15/2015 11:23 AM, Nikola Đipanov wrote: I'll keep this email brief since this has been a well known issue for some time now. Problem: Libvirt can't honour device names specified at boot for any volumes requested as part of block_device_mapping. What we currently do is in case they do get

Re: [openstack-dev] [Cinder] FFE Request: Re-add Quobyte Cinder Driver

Hello Mike! Thanks for looking into this. Yes, the fails are caused by the two open bugs i mentioned [1,2]. We will continue to see into those. Regards Silvan [1] https://bugs.launchpad.net/nova/+bug/1465416 [2] https://bugs.launchpad.net/cinder/+bug/1473116 2015-07-15 0:07 GMT+02:00 Mike Perez

Re: [openstack-dev] [neutron][lbaas] Horizon support for neutron-lbaas v2

Hi, Let’s move it into the LBaaS repo that seems like the right place for me — Thanks, German From: "Jain, Vivek" mailto:[email protected]>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:[email protected]>> Date: Tuesday, July 14, 2015 at 10:22

[openstack-dev] [lbaas] [octavia] No meeting today 7/15

All, This week is the L4-L7 mid cycle so we will skip today¹s meeting ‹ German __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http:

Re: [openstack-dev] [neutron][lbaas] Horizon support for neutron-lbaas v2

I agree with German. Let’s keep things together for now. Susanne From: Eichberger, German Sent: Wednesday, July 15, 2015 1:31 PM To: OpenStack Development Mailing List (not for usage questions) Cc: Balle, Susanne; Tonse, Milan Subject: Re: [openstack-dev] [neutron][lbaas] Horizon support for neutr

Re: [openstack-dev] [nova] Proposal for an Experiment

What you describe is a spike. It's a grand plan, and you don't need anyone's permission, so huzzah for the spike! As far as what should be improved, I hear a lot that having multiple schedulers does not scale well, so I'd suggest that as a primary target (maybe measure the _current_ problem, and t

Re: [openstack-dev] [Nova] Device names supplied to the boot request

On 07/15/15 at 12:19pm, Matt Riedemann wrote: On 7/15/2015 11:23 AM, Nikola Đipanov wrote: I'll keep this email brief since this has been a well known issue for some time now. Problem: Libvirt can't honour device names specified at boot for any volumes requested as part of block_device_mappin

[openstack-dev] [nova] Why is osapi_v3.enabled = False by default?

The osapi_v3.enabled option is False by default [1] even though it's marked as the CURRENT API and the v2 API is marked as SUPPORTED (and we've frozen it for new feature development). I got looking at this because osapi_v3.enabled is True in nova.conf in both the check-tempest-dsvm-nova-v21-fu

Re: [openstack-dev] [nova] Why is osapi_v3.enabled = False by default?

On 07/15/2015 01:44 PM, Matt Riedemann wrote: > The osapi_v3.enabled option is False by default [1] even though it's > marked as the CURRENT API and the v2 API is marked as SUPPORTED (and > we've frozen it for new feature development). > > I got looking at this because osapi_v3.enabled is True in

Re: [openstack-dev] [nova] Proposal for an Experiment

On 07/15/15 20:40, Clint Byrum wrote: What you describe is a spike. It's a grand plan, and you don't need anyone's permission, so huzzah for the spike! As far as what should be improved, I hear a lot that having multiple schedulers does not scale well, so I'd suggest that as a primary target (ma

[openstack-dev] [swift] Swift container sync process is consuming 100% CPU

In our production swift cluster, we have container sync middleware enabled in the pipeline. But swift container sync is not configured. We noticed 100% CPU utilization and a lot of read/write i/os from the swift-container-sync process on our meta data nodes recently after we have seen increasin

[openstack-dev] [tc][all] Tags, explain like I am five?

So I've been following the TC work on tags, and have been slightly confused by the whole work, so I am wondering if I can get a 'explainlikeimfive' (borrowing from reddit terminology) edition of it. I always thought tags were going to be something like: http://i.imgur.com/rcAnMkX.png (I'm not

Re: [openstack-dev] [nova] Proposal for an Experiment

On 16 July 2015 at 02:18, Ed Leafe wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 ... > What I'd like to investigate is replacing the current design of having > the compute nodes communicating with the scheduler via message queues. > This design is overly complex and has several known

Re: [openstack-dev] [grenade] future direction on partial upgrade support

Sean, OK, moving thread to openstack-dev. We'd like to help with this work if there is more to do. What are the next steps and what areas need help? Thanks, Will > -Original Message- > From: Sean Dague [mailto:[email protected]] > Sent: Wednesday, July 15, 2015 3:10 AM > To: Du, Dolpher

Re: [openstack-dev] [tc][all] Tags, explain like I am five?

On Wed, Jul 15, 2015 at 12:25 PM, Joshua Harlow wrote: > So I've been following the TC work on tags, and have been slightly > confused by the whole work, so I am wondering if I can get a > 'explainlikeimfive' (borrowing from reddit terminology) edition of it. > > I always thought tags were going

Re: [openstack-dev] [neutron] What does flavor mean for a network?

Wouldn't it be valid to assign flavors to groups of provider networks? e.g. a tenant wants to attach to a network that is wired up to a 40g router so he/she chooses a network of the "fat pipe" flavor. On Wed, Jul 15, 2015 at 10:40 AM, Madhusudhan Kandadai < [email protected]> wrote:

Re: [openstack-dev] [tc][all] Tags, explain like I am five?

John Griffith wrote: On Wed, Jul 15, 2015 at 12:25 PM, Joshua Harlow mailto:[email protected]>> wrote: So I've been following the TC work on tags, and have been slightly confused by the whole work, so I am wondering if I can get a 'explainlikeimfive' (borrowing from reddit termi

[openstack-dev] [Neutron] Proposing Cedric Brandily to Neutron Core Reviewer Team

As the Neutron L3 Lieutenant along with Kevin Benton for control plane, and Assaf Muller for testing, I would like to propose Cedric Brandily as a member of the Neutron core reviewer team under these areas of focus. Cedric has been a long time contributor to Neutron showing expertise particularly

Re: [openstack-dev] [oslo] Need new release of stable oslotest with capped mock

Excerpts from Yuriy Taraday's message of 2015-07-15 13:14:13 +: > Hello, oslo team. > > With recent mock nightmare we should not release a new stable version of > oslotest so that projects that depend on oslotest but don't directly depend > on mock will be unblocked in gate. > > I found out a

Re: [openstack-dev] [Neutron] Proposing Cedric Brandily to Neutron Core Reviewer Team

+1, Cedric has been a great contributor for a while now! On Wed, Jul 15, 2015 at 1:47 PM, Carl Baldwin wrote: > As the Neutron L3 Lieutenant along with Kevin Benton for control > plane, and Assaf Muller for testing, I would like to propose Cedric > Brandily as a member of the Neutron core review

Re: [openstack-dev] [nova] Proposal for an Experiment

On Jul 15, 2015, at 1:08 PM, Maish Saidel-Keesing wrote: >> * Consider the cost of introducing a brand new technology into the >> deployer space. If there _is_ a way to get the desired improvement with, >> say, just MySQL and some clever sharding, then that might be a smaller >> pill to swallow f

Re: [openstack-dev] [tc][all] Tags, explain like I am five?

On Wed, Jul 15, 2015 at 12:44 PM, Joshua Harlow wrote: > John Griffith wrote: > >> >> >> On Wed, Jul 15, 2015 at 12:25 PM, Joshua Harlow > > wrote: >> >> So I've been following the TC work on tags, and have been slightly >> confused by the whole work, so I am

[openstack-dev] [Tacker][NFV] Devstack plugin support is now available

Heads up. Tacker project now supports installation using a devstack plugin. The latest Tacker installation instruction is available in this wiki [1] Note, the team continues to meet weekly in IRC [2]. Feel free to join if you are interested in an ETSI MANO complaint NFV Orchestrator / VNF Manager.

Re: [openstack-dev] [Neutron] Proposing Cedric Brandily to Neutron Core Reviewer Team

+1 > On Jul 15, 2015, at 1:07 PM, Kyle Mestery wrote: > > +1, Cedric has been a great contributor for a while now! > > On Wed, Jul 15, 2015 at 1:47 PM, Carl Baldwin > wrote: > As the Neutron L3 Lieutenant along with Kevin Benton for control > plane, and Assaf Muller

Re: [openstack-dev] [nova] Proposal for an Experiment

On 16 July 2015 at 07:27, Ed Leafe wrote: > On Jul 15, 2015, at 1:08 PM, Maish Saidel-Keesing wrote: > >>> * Consider the cost of introducing a brand new technology into the >>> deployer space. If there _is_ a way to get the desired improvement with, >>> say, just MySQL and some clever sharding,

Re: [openstack-dev] [neutron] What does flavor mean for a network?

That begins to looks like nova’s metadata tags and scheduler, which is a valid use case. The underpinnings of flavors could do this, but it’s not in the initial implementation. doug > On Jul 15, 2015, at 12:38 PM, Kevin Benton wrote: > > Wouldn't it be valid to assign flavors to groups of pro

  1   2   >