Re: [openstack-dev] [nova] Removing BDM devices from POST requests

On 4/2/2017 10:10 PM, Matt Riedemann wrote: On 4/2/2017 8:08 PM, Feodor Tersin wrote: Can you give some more details? How does this actually "merge" or replace BDMs defined in the image metadata? Is this because we use device name as part of a hack for a primary key in the datab

[openstack-dev] [puppet] stepping down from puppet-openstack core

I am stepping down as core in the puppet openstack project. This is the culmination of a long and slow refocus of my work efforts into other areas. Additionally I'm not sure what the future holds for me at this point, and although it's possible that I will be doing puppet again but it's not fair

Re: [openstack-dev] [novaclient] novaclient and httpretty - unable to record

to me. -- Thanks, Matt __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Cinder] [Nova] Extend attached volume

On 4/3/2017 5:30 PM, Matt Riedemann wrote: On 4/3/2017 2:21 PM, Mathieu Gagné wrote: I would like to share our private implementation (based on Mitaka): https://gist.github.com/mgagne/9402089c11f8c80f6d6cd49f3db76512 The implementation makes it so Cinder leverages the existing Nova external

Re: [openstack-dev] [Cinder] [Nova] Extend attached volume

want me to contribute upstream. I didn't read the patch in detail, but if you're interested in contributing this upstream we could use a simple spec to start the process. Note that nova spec freeze for Pike is April 13. -- Thanks, Matt

Re: [openstack-dev] [nova] Removing BDM devices from POST requests

nd some simply won't work for older BDM or image resources, so are non-starters. I'm hoping some others with a fresh perspective on this can chime in with ideas, otherwise I'll bring it up in the nova API subteam meeting this week so we can talk about the best way forward. Thanks again Feodor

Re: [openstack-dev] [nova] Removing BDM devices from POST requests

g_v2, something like that. What do you think about that alternative? [1] https://github.com/openstack/nova/blob/468916ee57fede4d0c89fbf9c776269943e2cb44/nova/db/sqlalchemy/api.py#L4170-L4175 -- Thanks, Matt __ OpenStack

Re: [openstack-dev] [nova] Removing BDM devices from POST requests

On 4/2/2017 10:13 AM, Matt Riedemann wrote: On 4/1/2017 1:01 PM, Matt Riedemann wrote: I know we've talked about this over and over and another bug [1] reminded me of it. We have long talked about removing the ability to specify a block device name when creating a server or attaching a volume

Re: [openstack-dev] [nova] Removing BDM devices from POST requests

On 4/1/2017 1:01 PM, Matt Riedemann wrote: I know we've talked about this over and over and another bug [1] reminded me of it. We have long talked about removing the ability to specify a block device name when creating a server or attaching a volume because we can't honor the requested device

Re: [openstack-dev] [nova] Removing BDM devices from POST requests

On 4/1/2017 1:01 PM, Matt Riedemann wrote: I know we've talked about this over and over and another bug [1] reminded me of it. We have long talked about removing the ability to specify a block device name when creating a server or attaching a volume because we can't honor the requested device

Re: [openstack-dev] [all] BOS Forum - User/Dev Feedback session for your project?

, or more interesting sessions happening at the same time, I'm not sure. But that's why we don't schedule these types of sessions anymore. I'm sure we'll get more questions and feedback in the other sessions we've already proposed. -- Thanks, Matt

Re: [openstack-dev] [Cinder] [Nova] Extend attached volume

On 4/1/2017 12:17 PM, Jay Bryant wrote: Matt, I think discussion on this goes all the way back to Tokyo. There was work on the Cinder side to send the notification to Nova which I believe all the pieces were in place for. The missing part (sticking point) was doing a rescan of the SCSI bus

[openstack-dev] [nova] Removing BDM devices from POST requests

-- Thanks, Matt __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Cinder] [Nova] Extend attached volume

operations not already solve this use case? -- Thanks, Matt __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org

Re: [openstack-dev] [nova][vmware] CI results show up about a week late, if at all

On 3/29/2017 2:27 PM, Tracy Jones wrote: Just FYI the VMware NSX CI job is back up and running! We have added more resources and doing more updates so we can remain stable and timely. Thanks for your patience Tracy Thanks for the update Tracy. -- Thanks, Matt

Re: [openstack-dev] [horizon][nova][tc] nova-network deprecation in horizon

#/c/447707/ __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Tha

Re: [openstack-dev] [nova] [neutron] What the behavior of AddFixedIp API should be?

On 3/27/2017 11:42 PM, Rui Chen wrote: Thank you Matt, the background information is important. Seems all the peoples don't know how the add-fixed-ip API works, and there is no exact use case about it. Now neutron port-update API also support to set multiple fixed ip for a port, and the fixed-ip

Re: [openstack-dev] [nova] [neutron] What the behavior of AddFixedIp API should be?

r this API, but I think all it does is attach an interface and make sure that does not blow up, it does not try to use the interface to ssh into the guest, for example. -- Thanks, Matt __ OpenStack Development Ma

Re: [openstack-dev] [nova] remove-mox-pike blueprint

t here. -- Thanks, Matt __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Project Navigator Updates - Feedback Request

e and more projects are moving to using microversions. -- Thanks, Matt __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists

[openstack-dev] [nova] Spec review sprint on Tuesday April 4th

://wiki.openstack.org/wiki/Nova/Pike_Release_Schedule -- Thanks, Matt __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org

[openstack-dev] [nova] Can we deprecate the os-hosts API?

/ -- Thanks, Matt __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all][ptl] Action required ! - Please submit Boston Forum sessions before April 2nd

more than just nova (so we'll talk about the nova stuff in the free room area in other words). -- Thanks, Matt __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.ope

Re: [openstack-dev] [all][ptl] Action required ! - Please submit Boston Forum sessions before April 2nd

to sort that all out. -- Thanks, Matt __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman

Re: [openstack-dev] [i18n] [nova] understanding log domain change - https://review.openstack.org/#/c/439500

? -- Thanks, Matt __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] questions about Openstack Ocata replacement API

the keystone_authtoken config in nova.conf was causing some issues with getting the placement service user to get a token from the nova services. And you updated your httpd placement config based on the latest from the ubuntu packages. You did some debugging with curl too. -- Thanks, Matt

[openstack-dev] [nova] Should we delete the (unexposed) os-pci API?

/1673869 [4] https://github.com/openstack/nova/blob/15.0.0/setup.cfg#L132 [5] https://bugs.launchpad.net/nova/+bug/1426241 [6] https://docs.openstack.org/developer/nova/policies.html?highlight=metrics#metrics-gathering [7] https://review.openstack.org/#/c/51135/ -- Thanks, Matt

Re: [openstack-dev] [Openstack-operators] [nova] [neutron] Hooks for instance actions like creation, deletion

On 3/17/2017 9:13 AM, Matt Riedemann wrote: There is also dynamic vendordata v2 which was added in Newton: https://docs.openstack.org/developer/nova/vendordata.html We got feedback during the Pike PTG from some people, using hooks during instance create, that the dynamic vendordata serves

Re: [openstack-dev] [i18n] [nova] understanding log domain change - https://review.openstack.org/#/c/439500

to write and review. Doug I would suggest someone put some notes in the oslo.i18n docs to convey the message that those instructions are no longer relevant: https://docs.openstack.org/developer/oslo.i18n/guidelines.html#log-translation -- Thanks, Matt

[openstack-dev] [nova][vmware] CI results show up about a week late, if at all

experimental now since we don't actually know what state it's in since there don't appear to be maintainers and the CI is not reliable. [1] https://review.openstack.org/#/c/435010/ -- Thanks, Matt __ OpenStack Development Mailing

Re: [openstack-dev] [ptls] Project On-Boarding Rooms

?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev We have at least one person from the Nova team that can host an on-boarding session for Nova if we can get a slot. I promise to send our friendliest people. -- Thanks, Matt

[openstack-dev] [nova] Pike summit attendance

can take that into account when scheduling sessions (or whatever we'll be doing at the Forum). [1] https://etherpad.openstack.org/p/BOS-Nova-brainstorming -- Thanks, Matt __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] 回复： [nova][nova-scheduler] Instance boot stuck in"Scheduling" state

it. It shouldn't be left in scheduling state. You may want to run this to make sure your setup is done properly: nova-status upgrade check That should give you some basic readiness/health information about cells v2 and placement in your setup. -- Thanks, Matt

Re: [openstack-dev] [nova] [placement] experimenting with extracting placement

in working on, please let me know. [1] https://blueprints.launchpad.net/nova/+spec/placement-osc-plugin -- Thanks, Matt __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ

Re: [openstack-dev] [api][qa][tc][nova][cinder] Testing of a microversioned world

on master. On the devstack stable branch we cap the max_microversion, e.g.: https://github.com/openstack-dev/devstack/blob/stable/newton/lib/tempest#L339 -- Thanks, Matt __ OpenStack Development Mailing List (not for usage

[openstack-dev] [nova] Core team changes

work that you're doing to keep moving Nova forward. -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http

Re: [openstack-dev] [nova] Question to clarify versioned notifications

had this all straight since I was jumping around from specs and docs and code quite a bit yesterday piecing this together and wanted to make sure I had it straight. Plus you don't apparently work 20 hours a day gibi so I couldn't ask you in IRC. :) -- Thanks, Matt Riedemann

[openstack-dev] [nova] Question to clarify versioned notifications

different event types format will be an issue. [1] https://specs.openstack.org/openstack/nova-specs/specs/mitaka/implemented/versioned-notification-api.html [2] https://github.com/openstack/searchlight/blob/2.0.0/searchlight/elasticsearch/plugins/nova/notification_handler.py#L82

Re: [openstack-dev] [all] Some information about the Forum at the Summit in Boston

dvantage of the face-to-face time to work on some of the priority items for the Pike release in the free hacking/meetup space but without knowing when the other sessions are going to be it's hard to know when we can schedule space in the hacking pit. If that's all TBD that's fair,

Re: [openstack-dev] [kolla][keystone] better way to rotate and distribution keystone fernet keys in container env

I don't think it would cause an issue if every controller rotated all at once. The issues are more along the lines of rotating to key C when there are tokens out there that are encrypted with keys A and B. In other words over-rotation. As long as your keys are properly staged, do the rotation all

Re: [openstack-dev] [i18n] [nova] understanding log domain change - https://review.openstack.org/#/c/439500

, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova][searchlight] When do instances get removed from Searchlight?

instances will be stored in searchlight before it's removed. Again, I'm not sure if nova would control this or if it's something searchlight supports already. [1] https://review.openstack.org/#/c/441692/ -- Thanks, Matt

Re: [openstack-dev] [nova] placement/resource providers update 13

structure in placement error responses so that it is easier to distinguish between different types of, for example, 409 responses. We were just talking about the need for this in IRC yesterday so I'm glad to see someone was already working on it. Thanks for the detailed update Chris. -- Tha

Re: [openstack-dev] [placement][nova] PTG summary

work as well as integration with the nova-scheduler for traits and shared providers. The os-traits patches are all merged and the 0.2.0 release request is here: https://review.openstack.org/#/c/441437/ -- Thanks, Matt Riedemann

[openstack-dev] Disabling glance v1 by default in devstack

this by setting GLANCE_V1_ENABLED=True in the settings/localrc for your devstack plugin. [1] https://review.openstack.org/#/c/343129/ -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions

Re: [openstack-dev] [ptl][release] Pike release management communications

e openstack-dev list with [release] in the subject line. 4. Reply to this message, off-list, to me so I know that you have received it. A simple “ack” is enough :) ack -- Thanks, Matt Riedemann __ OpenStack Development Mailing

Re: [openstack-dev] [ptl][release] Pike release management communications

On 3/3/2017 10:16 AM, Matt Riedemann wrote: On 3/3/2017 9:56 AM, Thierry Carrez wrote: Hello, fellow PTLs, As Doug did for the past few cycles, I want to start the Pike cycle by making sure the expectations for communications with the release team are clear to everyone so there is no confusion

[openstack-dev] [nova] Freeze dates for Pike

://eavesdrop.openstack.org/meetings/nova/2017/nova.2017-03-02-21.00.log.html#l-119 [2] https://wiki.openstack.org/wiki/Nova/Pike_Release_Schedule [3] http://lists.openstack.org/pipermail/openstack-dev/2017-February/111639.html [4] https://releases.openstack.org/pike/schedule.html -- Thanks, Matt Riedemann

Re: [openstack-dev] [nova][telemetry] gate breakage

On 3/2/2017 10:26 AM, Matt Riedemann wrote: Tracking this under bug: https://bugs.launchpad.net/nova/+bug/1669473 The details are in the bug. We've figured out the root cause and I've got a workaround patch up in nova and Mehdi has a workaround patch up in devstack, and we're testing the nova

Re: [openstack-dev] [nova][telemetry] gate breakage

On 3/2/2017 8:29 AM, Matt Riedemann wrote: On 3/2/2017 8:14 AM, Mehdi Abaakouk wrote: Example of failure: Our test assertion (that does a GET /v2.1/servers/detail HTTP/1.1) that returns [] instead of the list of instances http://logs.openstack.org/56/439156/2/check/gate-telemetry-dsvm

Re: [openstack-dev] [nova][telemetry] gate breakage

an empty list, while 'openstack server show X' works well. Any ideas are welcome. Cheers, -- Mehdi Abaakouk mail: sil...@sileht.net irc: sileht According to logstash it looks like the regression started around 2/28 so we should look for nova changes that might be related. -- Thanks, Matt

[openstack-dev] [nova] Pike PTG recap - API

g-keystone-policy [3] https://bugs.launchpad.net/nova/+bug/1661360 [4] http://lists.openstack.org/pipermail/openstack-dev/2016-November/107195.html [5] https://docs.openstack.org/developer/nova/vendordata.html [6] https://review.openstack.org/#/c/265282 -- Thanks, Matt

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

nova-specs was also broken, the fix is here for anyone that needs to recheck or rebase nova-specs changes: https://review.openstack.org/#/c/439878/ -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for

[openstack-dev] [nova][docs] Is anyone interested in being the docs liaison for Nova?

e steps up for the docs liaison role, by default it lands on me, so I'd appreciate any help here. [1] https://review.openstack.org/#/c/438328/ -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage

[openstack-dev] [nova][cinder] Pike PTG recap - nova/cinder

ck.org/#/c/420201/ [5] https://review.openstack.org/#/c/373203/ -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs

[openstack-dev] [nova] Pike PTG recap - cells

/c/436094/ [9] https://blueprints.launchpad.net/nova/+spec/convert-consoles-to-objects -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subj

[openstack-dev] [nova][keystone] Pike PTG recap - quotas

[2] https://etherpad.openstack.org/p/ptg-hierarchical-quotas [3] https://review.openstack.org/#/c/411035/ -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.ope

Re: [openstack-dev] [all][swg] per-project "Business only" moderated mailing lists

k-dev" folder. If I find that I'm constantly missing something with a given tag, then I start filtering that into a new folder that's prioritized higher. -- Thanks, Matt Riedemann __ OpenStack Development Ma

Re: [openstack-dev] [all][swg] per-project "Business only" moderated mailing lists

care about properly? I'm a -1 on this unless I'm missing how it makes things much much better somehow. -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev

Re: [openstack-dev] [nova][cinder] Schedule Instances according to Local disk based Volume?

th a block device and specify distance=0 as a required constraint. I'm personally not sure how close we are to functionality like that, it seems like that would be a ways out to me, i.e. we have a lot of other work to do before we get to that point. -- Thanks, Matt

Re: [openstack-dev] [keystone]PKI token VS Fernet token

On Fri, Feb 24, 2017 at 9:09 PM, joehuang <joehu...@huawei.com> wrote: > Hello, Matt, > > Thank you for your reply, just as what you mentioned, for the slow changed > data, aync. replication should work. My concerns is that the impact of > replication delay, for example (

Re: [openstack-dev] [keystone]PKI token VS Fernet token

> > > At last, we still have one question: > For public cloud, it is very common that multi regions are deployed. And > the distance is usually very far between the regions. So the transport > delay is really a problem. Fernet token requires the data must be the same. > Because of the slow

Re: [openstack-dev] [nova][cinder] Schedule Instances according to Local disk based Volume?

by cinder using BlockDeviceDriver, it is quite different from the approach one you mentioned. The only problem now is that we cannot practially ensure the compute resource located on the same host with the volume, as Matt mentioned above, currently we have to arrange 1:1 AZ in Cinder and Nova to do

Re: [openstack-dev] [stable/ocata] [nova] [devstack multi-node] nova-conductor complaining about "No cell mapping found for cell0"

On 2/22/2017 9:33 AM, Prashant Shetty wrote: Thanks Matt. Here are the steps I have performed, I dont see any error related to cell0 now but n-cond still not able to detect computes after discover as well :(. Do we need any cell setting on nova-compute nodes as well?. vmware@cntr11

Re: [openstack-dev] [stable/ocata] [nova] [devstack multi-node] nova-conductor complaining about "No cell mapping found for cell0"

2-21T15:34:09.00 | - | ++--+---+--+-+---++-+ vmware@cntr11:~$ vmware@cntr11:~$ nova-manage cell_v2 list_cells +--+--+ | Name | UUID | +--+--+ +--+--+ vmware@cntr11:~$ Thanks, Prashant -- Tha

[openstack-dev] [nova] Team photo at the PTG

I've signed us all up for a team photo at 9:50 on Thursday morning. It's outside grand ballroom A on the third floor close to the top of the staircase. -- Thanks, Matt Riedemann __ OpenStack Development Mailing List

[openstack-dev] [nova] Call for upstream training liaison

more. [1] http://lists.openstack.org/pipermail/openstack-dev/2017-February/112270.html -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ

Re: [openstack-dev] Hierarchical quotas at the PTG?

On 2/15/2017 6:22 PM, Matt Riedemann wrote: I have no idea. I'm guessing someone will ping me when the time comes and I'll mosey on over. For whatever doesn't get covered, or needs to spill over, Nova is already going to have a block of time to talk about quota-related things (not just this) so

Re: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday

+2 Thanks for coordinating! From: Kevin Benton Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Friday, February 17, 2017 at 12:18 PM To: "openstack-dev@lists.openstack.org"

[openstack-dev] [nova] Some early feedback from the User Survey

and hooks/plugins/custom APIs are a major part of my operation. = 16 (9%) -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org

Re: [openstack-dev] [stable/ocata] [nova] [devstack multi-node] nova-conductor complaining about "No cell mapping found for cell0"

We do the same in devstack-gate for multinode jobs: https://github.com/openstack-infra/devstack-gate/blob/f5dccd60c20b08be6f0b053265e26a491307946e/devstack-vm-gate.sh#L717 Single-node devstack will take care of discovering the n-cpu compute host as part of the stack.sh run, but the multinod

[openstack-dev] [nova] Will unshelving an offloaded instance respect the original AZ?

with InvalidVolume. If unshelving a server in AZ 1 can't move it outside of AZ 1, then we're fine and the AZ check when unshelving is redundant but harmless. [1] https://review.openstack.org/#/c/335358/38/nova/virt/block_device.py@249 -- Thanks, Matt Riedemann

Re: [openstack-dev] [nova] Nova Bug Team Coordinator for Pike

for stepping up and taking it over. -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org

Re: [openstack-dev] [stable][heat] Heat stable-maint additions

something I'd do first before just adding a bunch of people. [1] https://docs.openstack.org/project-team-guide/stable-branches.html -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions

Re: [openstack-dev] [PKG-Openstack-devel] The end of OpenStack packages in Debian?

e version changes. We had spit-balled some ideas on automating some of that, but just never found the time. -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstac

[openstack-dev] [nova] Final mascot logo

Here are the final logos for the Nova mascot: https://www.dropbox.com/sh/9l1c7ymyjgpa3cc/AAB9iPZ0HIwn16nzC7G5liuza?dl=0 There will be some stickers and other postings of this at the PTG. -- Thanks, Matt Riedemann

Re: [openstack-dev] Hierarchical quotas at the PTG?

is already going to have a block of time to talk about quota-related things (not just this) so we can pick it up there too later in the week. -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [nova] notification impact of moving the instance create to the conductor

/api.py#L1759 [2] https://github.com/openstack/nova/blob/93bf6ba5186a3663606aa843a2f247709173f073/nova/compute/api.py#L1790 [3] https://github.com/openstack/nova/blob/93bf6ba5186a3663606aa843a2f247709173f073/nova/conductor/manager.py#L963 -- Thanks, Matt Riedemann

Re: [openstack-dev] Hierarchical quotas at the PTG?

On 2/15/2017 12:07 PM, Sajeesh Cimson Sasi wrote: Hi Matt, Andrey, CERN-BARC team was working on nested quota implementation in Nova some 3 years back.But at that time, it was decided to fix bugs in the existing quota driver rather than adding more features. After

[openstack-dev] [nova] Ocata retrospective

] https://etherpad.openstack.org/p/nova-newton-retrospective [2] https://etherpad.openstack.org/p/nova-ocata-retrospective -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions) Unsubscribe

Re: [openstack-dev] [nova] FYI: cells v1 job is blocked

On 2/14/2017 9:36 AM, Matt Riedemann wrote: The fix is here: https://review.openstack.org/#/c/433707/ That's approved for master, but if you're seeing failures in that job since yesterday that's why. I'm going to have to backport that all the way back to stable/mitaka too. The fix

Re: [openstack-dev] [nova] Cells meeting on Feb-15 is canceled

can't tell if it's sparse or not. -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org

Re: [openstack-dev] [nova] FYI: cells v1 job is blocked

questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Something wonky happened while I was switching network connections. -- Thanks, Matt Riedemann

[openstack-dev] [nova] FYI: cells v1 job is blocked

The fix is here: https://review.openstack.org/#/c/433707/ That's approved for master, but if you're seeing failures in that job since yesterday that's why. I'm going to have to backport that all the way back to stable/mitaka too. -- Thanks, Matt Riedemann

[openstack-dev] [nova] FYI: cells v1 job is blocked

We have a fix here: -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin

Re: [openstack-dev] [cinder] [nova] confusion on where nova_catalog_admin_info is used in cinder

On 2/14/2017 8:48 AM, Matt Riedemann wrote: OK so the NFS job would tickle it, but that might not be in the experimental queue for devstack (but it is in nova's experimental queue so we could hack this up to test it). I thought we were testing volume retype/migration now though? That calls

Re: [openstack-dev] [cinder] [nova] confusion on where nova_catalog_admin_info is used in cinder

e is something special about the service. https://review.openstack.org/#/c/433272/ <https://review.openstack.org/#/c/433272/> is the change. Matt Riedemann pointed out that this would break Cinder because there is a hardcoded concept of nova_catalog_admin_info - https:/

[openstack-dev] [nova] Pike PTG Planning

, and then whatever is leftover will be discussed on Friday. I know some people won't be around on Friday, or are leaving early, so if that's the case please make a note of that in the etherpad. [1] https://etherpad.openstack.org/p/nova-ptg-pike -- Thanks, Matt Riedemann

Re: [openstack-dev] [Openstack-operators] [nova] Next minimum libvirt version

On 2/11/2017 12:47 PM, Matt Riedemann wrote: So it sounds like we're good to bump the minimum required libvirt to 1.2.9 in Pike which drops support for SLES 12, Ubuntu 14.04, RHEL 7.1 and Oracle 7. We'll bump the minimum required QEMU in Pike to 2.1.0 which in addition to the above distro

Re: [openstack-dev] [Openstack-operators] [nova] Next minimum libvirt version

to 2.1.0 which in addition to the above distro versions also drops support for Oracle 7.3. From my 30 seconds of googling I don't see any upcoming announcements for a newer version of Oracle Linux. -- Thanks, Matt Riedemann

Re: [openstack-dev] [nova][cinder] Should nova just default to use cinder v3 in Pike?

there. But overall yeah I like the idea of just defaulting to cinderv3 in Pike, as long as we can still get cinderv2 coverage in CI in master, which I think we can do via grenade jobs. -- Thanks, Matt Riedemann __ OpenStack

[openstack-dev] Hierarchical quotas at the PTG?

guidance here? [1] http://lists.openstack.org/pipermail/openstack-operators/2017-January/012450.html -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev

[openstack-dev] [api] API WG PTG planning

-- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo

[openstack-dev] [nova][cinder] Should nova just default to use cinder v3 in Pike?

ht. Anyway, I just remembered this and it was middle-of-the-night thinking, so I'm looking to see if this makes sense or what is wrong with it. [1] https://review.openstack.org/#/c/420201/ [2] https://review.openstack.org/#/c/431704/ -- Tha

Re: [openstack-dev] [nova] Next minimum libvirt version

On 2/10/2017 11:18 AM, Thomas Bechtold wrote: For SUSE the wiki is updated and 1.2.9 should be fine. Cheers, Tom Thanks Tom. Would 1.3.1 as the next minimum in Queens be acceptable for SUSE? -- Thanks, Matt Riedemann

Re: [openstack-dev] [release] Support phase clarification

On 2/7/2017 11:52 AM, Jay S Bryant wrote: This would also mean we would need to be careful to ensure that any backports to Newton also make it into Ocata to avoid holes in fix coverage.> You have to do this regardless. Just saying. -- Thanks, Matt Riedem

[openstack-dev] [nova] Next minimum libvirt version

ideas on the next required version after that? I'm hoping some of the Red Hat people can chime in here. [1] https://wiki.openstack.org/wiki/LibvirtDistroSupportMatrix -- Thanks, Matt Riedemann __ OpenStack Development

Re: [openstack-dev] [All] IRC Mishaps

IRC network, and wondered why I was talking to myself. That reminds me of how often I type "testes" when only 50% of the time I'm talking about male genitalia. -- Thanks, Matt Riedemann __ OpenStack Developme

Re: [openstack-dev] [nova] Nova API sub-team meeting

in there which were already topics from the PTG etherpad: https://etherpad.openstack.org/p/nova-ptg-pike -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev

Re: [openstack-dev] [nova] Next notification meeting on 02.14.

certainly hope you'll be passing out Valentines. -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http

<    4   5   6   7   8   9   10   11   12   13   >