a capability for
this which gets modeled in placement as a standard trait on the compute
node resource provider. Then the API could check for that trait from
Placement and fail if it's not found.
--
Thanks,
Matt
__
OpenStack
able the upstream
refstack group.
## Ruck / Rover:
* Matt Young (myoung) and Sagi Shnaidman (sshnaidm)
* https://review.rdoproject.org/etherpad/p/ruckrover-sprint13
## CI Squad
* Put in place voting update jobs (
https://review.openstack.org/#/q/topic:gate_update)
* Add additional check/gate jobs to
.2018-05-03.log.html#t2018-05-03T18:49:58
[2]
https://review.openstack.org/#/q/topic:bug/1170237+(status:open+OR+status:merged
[3]
https://github.com/openstack/nova/blob/4b0d0ea9f18139d58103a520a6a4e9119e19a4de/nova/compute/vm_states.py#L69-L72
--
Thanks,
Matt
.2018-05-03.log.html#t2018-05-03T18:49:58
[2]
https://review.openstack.org/#/q/topic:bug/1170237+(status:open+OR+status:merged
[3]
https://github.com/openstack/nova/blob/4b0d0ea9f18139d58103a520a6a4e9119e19a4de/nova/compute/vm_states.py#L69-L72
--
Thanks,
Matt
.
--
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
On 5/2/2018 12:39 PM, Matt Riedemann wrote:
FWIW, I think we can also backport the data migration CLI to stable
branches once we have it available so you can do your migration in let's
say Queens before g
FYI, here is the start on the data migration CLI:
https://review.openstack.org/#/c
let's say they change the hypervisor or something less drastic
but still image property invalidating.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.ope
your migration in let's
say Queens before getting to Rocky.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
, required in Ocata).
[1] https://review.openstack.org/#/c/492210/
[2] https://etherpad.openstack.org/p/nova-ptg-rocky-placement
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
repo <https://github.com/openstack/puppet-tripleo>.
Why wouldn't you start on master, or queens, and then move backward to
the older branches?
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage ques
tus:merged)
--
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
in with different
perspective, like melwitt or dansmith.
All of the solutions are bad in their own way, either because they add
technical debt and poor user experience, or because they make rebuild
more complicated and harder to maintain for the developers.
--
Thanks,
Matt
ible,
despite the fact that ImagePropertiesFilter is optional (although I'm
pretty sure everyone enables it).
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.
during a rebuild.
Changing the allocation would mean it is not a rebuild any more but a
resize.
Agree.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
out if rebuliding the instance with the
new image with new required traits but on the same host would result in
new allocation requests, and if so, we should fail - but we can (only?)
determine that via the response from GET /allocation_candidates.
--
Thanks,
Matt
.
--
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
in #openstack-nova and discussing it.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi
Sean to magically appear to reply to this thread, I
thought I'd pass this along.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
://review.openstack.org/#/c/543263/
If you can find the bug, or report a new one, I could take a look.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
priority. I'm not sure if there is a problem
here, or a solution needed, or if it would be useful for the people that
pick the sessions to give a heads up before the deadline that there are
still a lot of slots open.
--
Thanks,
Matt
On 4/25/2018 10:34 AM, Sreeram Vancheeswaran wrote:
Thank you so much Matt for the detailed steps. We are doing boot from
image and are probably running into the issue mentioned in [2] in your
email.
Hmm, OK, but that doesn't really make sense how you're going down this
path [1] in the code
ird that cinder-api is hitting an RPC messaging timeout even
though cinder-volume clearly failed, that should be raised back up to
cinder-api and spewed back to the caller (nova-compute) as a 500 error.
Also, I shoul
://review.openstack.org/#/c/547856/
--
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
to me. I know Lance is active on stable reviews for
Keystone and is aware of the guidelines.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
o the
API database.
--
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
on BlueJeans [2], typically ~14:30 UTC. Please feel free to add
items to the agenda [2] or simply come and chat.
Thanks,
Matt
[1] https://bluejeans.com/7050859455
<https://www.google.com/url?q=https%3A%2F%2Fbluejeans.com%2F7050859455>
[2] https://etherpad.openstack.org/p/tripleo-ci-squad-m
then yeah that sounds like an improvement on option 2 or 3 in my
original email and resolves the issue without having to call (or change)
"GET /allocation_candidates". I still think it should happen from within
ImagePropertiesFilter, but that's an implementation detail.
] https://etherpad.openstack.org/p/nova-ptg-rocky (L362)
[6] https://developer.openstack.org/api-ref/compute/#list-migrations
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
tion until #4 is
done, but I think the best long-term solution to this problem is #4.
[1] https://review.openstack.org/#/c/560718/
[2] https://review.openstack.org/#/c/546357/
[3] https://bugs.launchpad.net/nova/+bug/1763766
[4] https://review.openstack.org/#/c/532407/
--
Thanks,
Matt
back into our docs for people to find
later when they are trying to learn.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
.
The certificate validation stuff in there for the John Hopkins team is a
prime example of how this is putting focus on something that has
otherwise been getting deferred since at least the Ocata summit.
[1] https://etherpad.openstack.org/p/nova-runways-rocky
--
Thanks,
Matt
nstack/nova/tree/doc/source/install/verify.rst#n103,
it is there - so, closed invalid IMHO,
Done, thanks for the feedback.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
need root, or
something with access to those commands (sudo)?
I'm not sure how prescriptive we should be with stuff like this in the
docs because if we did start saying this, I feel like we'd have to say
it everywhere.
[1] https://bugs.launchpad.net/nova/+bug/1764530
--
Tha
to release python-novaclient 10.x
in Queens and it prevented us from being able to include it in
upper-constraints for Queens because it negatively impacted some other
projects due to backward incompatible changes in the 10.x series of
novaclient. So learn from my mistakes.
--
Thanks,
Matt
ion to the existing "nova live-migration" CLI if people want to
retain the functionality but hate the other name.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsu
On 4/19/2018 11:06 AM, Matthew Booth wrote:
I'm ambivalent, tbh, but I think it's better to pick one. I thought
we'd picked 'evacuate' based on the TODOs from Matt R:
http://git.openstack.org/cgit/openstack/nova/tree/nova/compute/manager.py#n2985
http://git.openstack.org/cgit/openstack/nova
requesting, which is something we talked about a long time ago.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs
/project:openstack/trove-dashboard+status:open+NOT+branch:master
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
NoValidHost.
--
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
--
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
as
well as against Heat, Mistral, Ironic, Tempest and python-tempestconf
upstream"
"Finish work items carried from sprint 11 or other side work going on."
Epic: https://trello.com/c/ifIYQsxs/680-sprint-12-undercloud-tempest
Tasks: https://tinyurl.com/y8k6yvbm
For any que
progress if possible.
[1] https://review.openstack.org/#/c/486204/
[2]
https://specs.openstack.org/openstack/nova-specs/specs/rocky/approved/nova-validate-certificates.html
--
Thanks,
Matt
__
OpenStack Development Mailing
the user knows exactly what they are opting into
rather than rely on default behavior in the server, which might bite you
(or us) later if we ever want to change that default behavior.
--
Thanks,
Matt
__
OpenStack D
core
team for the project.
[1] https://docs.openstack.org/project-team-guide/stable-branches.html
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
pleo/+bug/1758143
https://bugs.launchpad.net/tripleo/+bug/1757134
https://bugs.launchpad.net/tripleo/+bug/1755485
https://bugs.launchpad.net/tripleo/+bug/1758932
https://bugs.launchpad.net/tripleo/+bug/1751180
If you have any questions and/or suggestions, please contact us in #tripleo
Thanks,
cking the zvm
stuff for this specific issue, because we can really go down a rabbit
hole if we want to be pedantic on this, for example, os-brick is only
used by a couple of virt drivers, taskflow is only used by powervm,
castellan is optional since we don't require a real key manager, etc.
runs, it's just an extra set of
dependencies to list in the tox.ini.
Having said all this, I don't have the energy to help push for
consistency myself, but will happily watch you from the sidelines.
--
Thanks,
Matt
to
the nova-compute host where the instance is currently running.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
On 4/9/2018 4:58 AM, Kashyap Chamarthy wrote:
Keep in mind that Matt has a tendency to sometimes unfairly
over-simplify others views;-). More seriously, c'mon Matt; I went out
of my way to spend time learning about Debian's packaging structure and
trying to get the details right by talking
. Maybe mdbooth would like to weigh in on
this given he's present in this thread.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
that uses this interface, heads up
that you'll need to be using the tuple form if you are not already doing so.
[1] https://review.openstack.org/#/c/558059/
--
Thanks,
Matt
__
OpenStack Development Mailing List
level changes on
the nova side.
--
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
ut bumping from
minimum required (in Rocky) libvirt 1.3.1 to at least 3.0.0 (in Stein)
and qemu 2.5.0 to at least 2.8.0, so I think that's already covering
some good ground. Let's not get greedy. :)
--
Thanks,
Matt
__
On 4/6/2018 5:09 AM, Matthew Booth wrote:
I think you're talking at cross purposes here: this won't require a
swap volume. Apart from anything else, swap volume only works on an
attached volume, and as previously discussed Nova will detach and
re-attach.
Gorka, the Nova api Matt is referring
can still support the features for the newer versions if
you're running a system with those versions, but not penalize people
with slightly older versions if not.
--
Thanks,
Matt
__
OpenStack Development Mailing List
attachment
for the new connection. I think that would be similar to how shelve and
unshelve works in nova.
Would this really require a swap volume call from Cinder? I'd hope not
since swap volume in itself is a pretty gross operation on the nova side.
--
Thanks,
Matt
do we
do with the original volume (delete it?), etc).
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.o
ldn't wait for the volume to go to 'available', we don't want it
to go to 'available', we'd just wait for it to go back to 'reserved'.
During a rebuild the instance still needs to keep the volume logically
attached to it so another instance can't grab it.
--
Tha
most of the points
from Sydney and Dublin.
Please check it out:
https://review.openstack.org/#/c/552733/
Yours Tony.
[1]https://review.openstack.org/548916
+ops
--
Thanks,
Matt
__
OpenStack Development Mailing List
connector, connect on the host, and complete the attachment (marks the
volume as in-use again)
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.ope
On 3/29/2018 2:44 AM, Radoslav Gerganov wrote:
While running the VMware CI continues to be a challenge, I must say this
patch fixes a regression introduced by Matt Riedemann's patch:
https://review.openstack.org/#/c/549411/
for which the VMware CI clearly indicated there was a problem
that come to mind are:
nova/compute/manager.py
nova/virt/
nova/virt/block_device.py
There are likely others.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
before I sent the original email.
I had the same question, and it looks like the tests that failed in [1]
aren't being run in [2].
[1] https://review.openstack.org/#/c/549411/
[2] https://review.openstack.org/#/c/557256/
--
Thanks,
Matt
the aggregate name? Because I think the
former could get done in Rocky, but the latter probably not.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
in #openstack-helm if you'd like to get looped
in.
Thanks,
Matt
-Original Message-
From: Paul Bourke [mailto:paul.bou...@oracle.com]
Sent: Wednesday, March 28, 2018 11:17 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev]
[kolla][kolla-kubernete][tc][openstack-helm]propose
On 3/28/2018 11:21 AM, Andrey Kurilin wrote:
PS: https://review.openstack.org/#/c/59694/
PS2: it was abandoned due to several -2 :)
Look how nice I was as a reviewer 5 years ago...
--
Thanks,
Matt
__
OpenStack
n the past.
--
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
Larry Rensing
Darla Ahlert
These folks helped set the direction of OpenStack-Helm, and I can't thank them
enough for their contributions and dedication. They'll always be part of the
team, and circumstances permitting in the future, I hope to collaborate closely
again!
Thanks,
Matt McEuen
On 3/26/2018 9:00 PM, melanie witt wrote:
To the existing core team members, please respond with your comments,
+1s, or objections within one week.
+1
--
Thanks,
Matt
__
OpenStack Development Mailing List
is now possible.
--
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
in the API, and should just be fixed without a
microversion. In other words, you shouldn't have to opt out of broken
behavior using microversions.
[1] https://review.openstack.org/#/c/446446/
--
Thanks,
Matt
__
OpenStack
FYI
Forwarded Message
Subject: [openstack-dev] [nova][placement] Upgrade placement first!
Date: Mon, 26 Mar 2018 15:02:23 -0500
From: Eric Fried
Reply-To: OpenStack Development Mailing List (not for usage questions)
ices=[None,
'pcid'] and you can either specify None or 'pcied' for that option
(default to None).
Right now the code that's relying on this option just has a hard-coded
check for the value which is OK.
--
Thanks,
Matt
__
://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
/
https://review.openstack.org/#/c/282872/
I don't remember exactly where those fell down, but it's worth looking
at this first before trying to do this again.
--
Thanks,
Matt
__
OpenStack Development Mailing List
://review.openstack.org/#/c/532407
Once again, there are already existing threads about this topic, please
don't continue to try and start new threads or send new reminders about
it. You can reply on the existing discussion thread if you have new info.
--
Thanks,
Matt
ust saying, "we don't need to review more specs because
we already have enough approved specs to get through the related code
changes", and that's fair, I've said the same before, but those are two
different things.
to approve more specs along
the way if we find we're flushing the queue down enough.
This is what I'd prefer to see.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
/2018/nova.2018-03-22-14.00.log.html#l-205
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org
+1
On Thu, Mar 22, 2018 at 10:03 AM, Jonathan Proulx wrote:
> On Wed, Mar 21, 2018 at 08:32:38PM -0400, Paul Belanger wrote:
>
> :6. Spandau loses to Solar by 195–88, loses to Springer by 125–118
>
> Given this is at #6 and formal vetting is yet to come it's probably
> not
. Not that my schedule matters, just FYI.
But regardless of that, I think the earlier the better to flush out
what's already there, since we've already approved quite a few
blueprints this cycle (32 to so far).
--
Thanks,
Matt
microversion - we have a lot of TODOs for
similar stuff like this in the API
I think https://review.openstack.org/#/c/546925/ will supersede ^ so we
should probably hold off on Takashi's spec until we know for sure what
we're doing about the hard-affinity policy limit stuff.
--
Thanks,
Matt
else crop up related to this, just let me
know.
Thanks for wrangling this one.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
, it's not
really an option.
--
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
aware of a proposed alternative
for that option.
The names used should conform to RFC952, see:
https://github.com/openstack/nova/blob/7cbb5764d499dfdc90ef4a963daf217d58c840d4/nova//utils.py#L543
--
Thanks,
Matt
__
O
don't know if ^ will work, but it's what I'd try.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.o
Rechecking changes at this point isn't going to help much.
It looks like the spike started around March 13 so can people help look
for things like new tests which maybe pushed over the number of
concurrently created volumes/snapshots in a single test run?
--
Thanks,
Matt
since he was the one asking about this at the PTG I think.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
to specify
delete_on_termination=True, thinking about the implications, which then
means they can't rebuild their volume-backed instance later because nova
can't / won't delete the volume.
If we can solve this without deleting the volume at all and just
re-image it, then it's a non-issue.
--
Tha
ates.
--
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
, what should
the rebuild operation do? Log a warning and just detach the volume but
not delete it and continue, or fail?
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack
leaving a
lot of volumes lying around that the user then has to clean up,
otherwise they'll eventually go over quota.
We need user (and operator) feedback on this issue and what they would
expect to happen.
--
Thanks,
Matt
.
--
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
there wasn't
precedent.
I don't think we need a blueprint for this, it's just a bug.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
.
2. Dan Smith mentioned another idea such that we could index the
aggregate metadata keys like filter_tenant_id0, filter_tenant_id1, ...
filter_tenant_idN and then combine those so you have one host aggregate
filter_tenant_id* key per tenant.
--
Tha
. Also Neutron will report inventories on those RPs
- Nova will do the claim of the port related resources in placement
and the consumer_id will be the instance UUID
--
Thanks,
Matt
__
OpenStack Development Mailing
magnificence.
--
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
is some unsolicited feedback that I'm going to give now.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
ssions about all of this. Tony, save 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
)
--
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
301 - 400 of 2548 matches
Mail list logo