hat, because I don't think you can do this:
GET /flavors?spec=hw%3Acpu_policy=dedicated
Maybe you'd do:
GET /flavors?hw%3Acpu_policy=dedicated
The problem with that is we wouldn't be able to perform any kind of
request schema validation of it, especially sin
maybe we don't know what other operators want
since no one else is at multi-cell cells v2 yet.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...
g not to use the API then deprecation
is probably fine, but I personally don't feel too strongly about it
either way.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
U
like you want #3 or #4.
--
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
any topics you'd like
to discuss to the etherpads!
I look forward to some good sessions tomorrow.
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.open
/613076/
--
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
After hacking on the PoC for awhile [1] I have finally pushed up a spec
[2]. Behold it in all its dark glory!
[1] https://review.openstack.org/#/c/603930/
[2] https://review.openstack.org/#/c/616037/
On 8/22/2018 8:23 PM, Matt Riedemann wrote:
Hi everyone,
I have started an etherpad for
reaks" wouldn't result in anything breaking.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openst
On 11/5/2018 10:43 AM, Matt Riedemann wrote:
If you are seeing this error when implementing and running the upgrade
check command in your project:
Traceback (most recent call last):
File
"/home/osboxes/git/searchlight/.tox/venv/lib/python3.5/site-packages/oslo_upgradecheck/upgradeche
that because of a critical bug, the lazy translation was
disabled in Havana to be fixed in Icehouse but I don't think that ever
happened before IBM developers dropped it upstream, which is further
justification for nuking this code from the various projects.
--
Thanks,
On 11/5/2018 1:17 PM, Matt Riedemann wrote:
I'm thinking of a case like, resize and instance but rather than
confirm/revert it, the user deletes the instance. That would cleanup the
allocations from the target node but potentially not from the source node.
Well this case is at least n
locations?). I'm thinking of a case
like, resize and instance but rather than confirm/revert it, the user
deletes the instance. That would cleanup the allocations from the target
node but potentially not from the source node.
--
Thanks,
Matt
chpad.net/nova/+spec/user-locale-api
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org
Cathy.
Andreas - thanks for the update and good luck on the new position.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
her priority efforts taking the
attention of the core team. Getting agreement on the spec is the first
step and then the runways process should be used to deal with actual
code reviews, but I think the spec review has stalled (I know I am
guilty of not looking at the latest updates to the spec).
fort was abandoned
several years ago. It is probably still called in a lot of "big
tent/stackforge" projects because of initially copying it from the more
core projects. Anyway, just remove it.
I'm talking with the oslo team
e the neutron team has had to deal with
something like this.
[1] https://review.openstack.org/#/q/topic:upgrade-checkers+status:open
[2] https://review.openstack.org/#/c/615196/
--
Thanks,
Matt
__
OpenStack Development Mailing
this elsewhere in the thread.
--
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/ma
s align with old/new flavors used to resize the instance? Did
the resize fail?
Are there mixed compute versions at all, i.e. are you moving instances
around during a rolling upgrade?
--
Thanks,
Matt
__
OpenStack Deve
can avoid the need to continually forward-porting code to
disable it.
[1]
https://specs.openstack.org/openstack/nova-specs/specs/rocky/implemented/placement-mirror-host-aggregates.html
[2] https://bugs.launchpad.net/nova/+bug/1
oes work though. Just
FYI for anyone else having the same problem.
[2] https://storyboard-dev.openstack.org/
[2]
https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22839/storyboard-migration-the-remaining-b
e
is deleted and archived/purged? Because if so, that might be something
we want to add as a nova-manage command.
[1] https://bugs.launchpad.net/nova/+bug/1800755
[2] https://review.openstack.org/#/c/409943/
--
Thanks,
ingle-node). There must be something weird that
tickles those tests in a multi-node configuration and I just haven't dug
into it yet, but maybe one of our intrepid contributors can lend a hand
and debug it.
--
Thanks,
Matt
_
below that one in the series shows how it's
implemented for the libvirt driver.
[1] https://review.openstack.org/#/c/613991/
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubs
https://review.openstack.org/#/c/521041/
[5]
https://github.com/openstack/nova/blob/a0eacbf7f/nova/tests/functional/test_servers.py#L1839
[6]
https://github.com/openstack/nova/blob/a0eacbf7f/nova/compute/resource_tracker.py#L917-L940
--
Thanks,
tches that are ready for review:
https://review.openstack.org/#/q/topic:upgrade-checkers+status:open
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev
an API to change this, and only do
it via config, was not good. But if the keystone limits API solves that
then it's a non-issue.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage ques
tions with the upgrade.
[1]
http://lists.openstack.org/pipermail/openstack-dev/2018-September/134541.html
[2] https://review.openstack.org/#/c/604454/
[3] https://review.openstack.org/#/c/600162/
--
Thanks,
Matt
__
Open
instance_update_at_top to keep
the nova-cell-api db up to date.
There was also the "read from searchlight" idea [1] but that died in Boston.
[1]
https://specs.openstack.org/openstack/nova-specs/specs/pike/approved/list-instances-using-searchlight.html
--
Tha
let's just
wait for unified limits from keystone and let this rot on the vine".
I'd be happy to restore and update that spec.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questio
ject basis, then I'd defer to the core team for
the project.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:u
useful
in Stein.
--
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
e just abandon
the change?
--
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 10/22/2018 11:59 AM, Matt Riedemann wrote:
Thanks for this. Have you debugged to the point of knowing where the
initial DB query is starting from?
Looking at history, my guess is this is the change which introduced it
for all requests:
https://review.openstack.org/#/c/276861/
From that
ev
Thanks for this. Have you debugged to the point of knowing where the
initial DB query is starting from?
Looking at history, my guess is this is the change which introduced it
for all requests:
https://review.openstack.org/#/c/276861/
--
Thanks,
Matt
-checkers+(status:open+OR+status:merged)
[2] https://review.openstack.org/#/c/611812/
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
e.
On 10/15/2018 3:29 PM, Ben Nemec wrote:
On 10/15/18 3:27 AM, Jean-Philippe Evrard wrote:
On Fri, 2018-10-12 at 17:05 -0500, Matt Riedemann wrote:
The big update this week is version 0.1.0 of oslo.upgradecheck was
released. The documentation along with usage examples can be found
here
://review.openstack.org/#/c/611368/
[2] https://review.openstack.org/#/c/66/
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
.org/p/compute-api-microversion-gap-in-osc
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org
patch to test the postgresql-migrate-db.sh script now. [2]
[1]
http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2018-10-16.log.html#t2018-10-16T19:37:25
[2] https://review.openstack.org/#/c/611020/
--
Thanks,
Matt
Lee talking
about encrypted volumes:
https://www.openstack.org/summit/berlin-2018/summit-schedule/global-search?t=yarwood
Unless he just loves it so much he needs to talk about it twice.
--
Thanks,
Matt
__
OpenStack
-10.log.html#t2018-10-10T15:17:17
[4]
http://lists.openstack.org/pipermail/openstack-dev/2018-October/135688.html
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-d
't think we should attempt that. Just fail
if being forced and nested allocations exist on the source.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-
rcing
those types of servers.
--
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/ma
an
AZ that doesn't exist, or some other kind of scheduler hint that we know
won't work so we get a NoValidHost. However, online_data_migrations in
grenade probably don't run on the cell0 database, so I'm not sure we
wou
--
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
t sound like it. With the nova rebuild API, the user
provides an image reference and that is used to re-image the root disk
on the server. So it might not be a snapshot, it could be something new.
--
Thanks,
Matt
__
Open
not a feature I don't think?) - and just
make it clear with a note in the backport commit message why the
backport is different from the original change.
--
Thanks,
Matt
__
OpenStack Development Mailing List
Cinder as well.
--
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
The ocata-em tag request is up for review:
https://review.openstack.org/#/c/608296/
On 9/28/2018 11:21 AM, Matt Riedemann wrote:
Per the other thread on this [1] I've created an etherpad [2] to track
what needs to happen to get nova's stable/ocata branch ready for
Extended Main
I
don't think there's ever been a patch backported by 4 releases.
OK, cool, sounds like killing the heat-agent ocata branch is the thing
to do then.
--
Thanks,
Matt
__
OpenStack Development Mailing List (no
.
Thanks!
Jay (jungleboyj)
+1 from me in the stable-maint-core peanut gallery.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
github.com/openstack/nova/blob/237ced4737a28728408eb30c3d20c6b2c13b4a8d/nova/network/neutronv2/api.py#L1393
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstac
ds, will it
be reasonable to run CI for stable/ocata heat changes against a
heat-agents ocata-eol tag?
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: ope
rom 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
c/591354/2
Actually it will be enabled in both tempest-full and tempest-slow,
because there is also a multiattach test marked as 'slow':
TestMultiAttachVolumeSwap.
I'll push patches today.
--
Thanks,
Matt
___
On 9/30/2018 11:02 AM, Matt Riedemann wrote:
Maybe that's some conditional branch logic we can hack into
devstack-gate [7] like we do for neutron? [8]
I'm hoping this works:
https://review.openstack.org/#/c/606853/
--
Tha
p;repos=
[7]
https://github.com/openstack-infra/devstack-gate/blob/95fa4343104eafa655375cce3546d27139211d13/devstack-vm-gate-wrap.sh#L138
[8]
https://github.com/openstack-infra/devstack-gate/blob/95fa4343104eafa655375cce3546d27139211d13/devstac
d on a similar changes_since test, so we should see
why they are behaving differently.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@list
astic-recheck/#1686542
[2] http://status.openstack.org/elastic-recheck/#1783405
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
[2].
[1] https://storyboard.openstack.org/#!/story/2003657
[2]
http://lists.openstack.org/pipermail/openstack-dev/2018-September/135025.html
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questio
some of which are 33MB *compressed*. So indexing of those
identified problematic screen logs has been disabled:
https://review.openstack.org/#/c/606197/
I've reported bugs against each related project.
--
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
org/p/nova-ocata-em
[3]
https://docs.openstack.org/project-team-guide/stable-branches.html#extended-maintenance
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-d
ere schema could be registered on that thing, and then
you pass a handle (ID reference) to that to nova when creating the
(baremetal) server, nova pulls it down from glare and hands it off to
the virt driver. It's just that no one is d
are
about all of the non-compute API things in OSC either.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs
hing where OSC core doesn't look at a
change until the subteam has +1ed it. We have a similar concept in nova
with virt driver subteams.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage quest
On 9/27/2018 5:23 AM, Sylvain Bauza wrote:
On Thu, Sep 27, 2018 at 2:46 AM Matt Riedemann <mailto:mriede...@gmail.com>> wrote:
On 9/26/2018 5:30 PM, Sylvain Bauza wrote:
> So, during this day, we also discussed about NUMA affinity and we
said
> that we cou
to wait for the Placement API
support ?
Folks, what are you thoughts ?
I'm pretty sure we've said several times already that modeling NUMA in
Placement is not something for which we're holding up the e
s created (nova/cinder/glance/keystone). For
newer projects, like placement, it's not a problem because they never
created any other CLI outside of OSC.
[1] https://etherpad.openstack.org/p/compute-api-microversion-gap-in-osc
[2] https://etherpad.openstack.org/p/nova-ptg-stein (~L721)
--
ies filter?
--
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
b) they mentioned a lack of DRS and HA support, but didn't mention the
Watcher or Masakari projects - maybe they didn't know they exist?
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage qu
On 9/24/2018 2:06 PM, Matt Riedemann wrote:
Are there more specific docs about how to configure the 'image import'
feature so that I can be sure I'm careful? In other words, are there
specific things a "glance-status upgrade check" check could look at and
say, "y
is broken, here are details on how
you should do this"?
I'm willing to help write the upgrade check for glance, but need more
details on that release note.
[1] https://storyboard.openstack.org/#!/story/2003657
[2] https://docs.openstack.org/releasenotes/
e results but then not have any rows,
which could be more confusing.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsu
On 9/21/2018 3:53 PM, Matt Riedemann wrote:
* The reference docs I wrote for writing upgrade checks is published now
[4]. As I've been answering some questions in storyboard and IRC, it's
obvious that I need to add some FAQs into those docs because I've taken
some of this for gr
[1]
http://lists.openstack.org/pipermail/openstack-dev/2018-September/134972.html
[2] https://review.openstack.org/#/c/603465/
[3] https://review.openstack.org/#/c/604430/
[4] https://docs.openstack.org/nova/latest/reference/upgrade-checks.html
--
Thanks,
Matt
details on each tag.
--
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 9/20/2018 12:08 PM, Elõd Illés wrote:
Hi Matt,
About 1.: I think it is a good idea to cut a final release (especially
as some vendor/operator would be glad even if there would be some
release in Extended Maintenance, too, what most probably won't
happen...) -- saying that without kn
that should do it, thanks!
--
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/lis
use those even if the filter is disabled? In the review I
had suggested that we add a pre-upgrade check which inspects the flavors
and if any of these are found, we report a warning meaning those flavors
need to be updated to use traits rather than capabilities
ing because people assume someone else is going to cover it?
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
h
On 9/19/2018 2:45 PM, Matt Riedemann wrote:
Another one we need to make a decision on is:
https://bugs.launchpad.net/tempest/+bug/1783405
Which I'm suggesting we need to mark more slow tests with the actual
"slow" tag in Tempest so they move to only be run in the tempest-slow
tempest run shouldn't
take over 2 hours (remember when it used to take ~45 minutes?).
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?s
g asked, etc. That's awesome.
Reminds me a lot of gibi when we nominated him.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
On 12/1/2017 2:47 PM, Matt Riedemann wrote:
Andrew Laski also mentioned in IRC that we didn't replace the original
instance.image_ref with the shelved image id because the shelve
operation should be transparent to the end user, they have the same
image (not really), same volumes, same IPs
On 9/18/2018 12:26 PM, Matt Riedemann wrote:
On 9/17/2018 9:41 PM, Ghanshyam Mann wrote:
On Tue, 18 Sep 2018 09:33:30 +0900 Alex Xu
wrote
> That only means after 599276 we only have servers API and
os-instance-action API stopped accepting the undefined query parameter.
>
On 9/18/2018 9:52 PM, Matt Riedemann wrote:
On 9/18/2018 12:28 PM, Doug Hellmann wrote:
What's probably missing is a version of the grenade job that allows us
to control that USE_PYTHON3 variable before and after the upgrade.
I see a few different grenade jobs (neutron-grenade,
neutron-gr
release for the grenade run.
[1]
https://github.com/openstack-infra/devstack-gate/blob/95fa4343104eafa655375cce3546d27139211d13/devstack-vm-gate-wrap.sh#L434
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for u
uot;Received" so does that
mean my non-Forum-at-all submission is now automatically a candidate for
the Forum because that would not be my intended audience (only suits and
big wigs please).
--
Thanks,
Matt
__
Ope
-stable-branch-eol.html#end-of-life
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-
idual
microversions? I'd prefer not to see an explosion of microversions for
cleaning up oddities in the API, but I could see how doing them all in a
single microversion could be complicated.
--
Thanks,
Matt
__
OpenStac
o
my custom API extension that handles GET /servers?bestpet=cats will
continue to work as long as I'm using microversion < 2.66.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscri
ck.org/#/c/599276/
[2]
https://review.openstack.org/#/c/599276/23/nova/api/openstack/compute/schemas/servers.py
[3] https://docs.openstack.org/releasenotes/neutron/rocky.html#upgrade-notes
--
Thanks,
Matt
__
OpenStack D
, or remind them to
translate.
My one cent.
Is there a generic openstack group on wechat? Does one have to be
invited to it? Is there a specific openstack/nova group on wechat? I'm
on wechat anyway so I don't mind being in those groups if someone wants
to reach out.
--
Tha
ommunication between upstream
and downstream teams, I've encouraged the downstream folk to send an
email upstream to start a discussion.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not fo
https://governance.openstack.org/election/results/stein/ptl.html
[2] https://storyboard.openstack.org/#!/story/2003657
[3] https://github.com/cybertron/oslo.upgradecheck
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for
fore I go off and start
writing up a spec?
[1] https://bugs.launchpad.net/openstack-publiccloud-wg/+bug/1791681
[2] https://bugs.launchpad.net/openstack-publiccloud-wg/+bug/1791679
[3] https://blueprints.launchpad.net/nova/+spec/shelve-on-stop
--
Thanks,
Matt
___
On 3/28/2018 4:35 PM, Jay Pipes wrote:
On 03/28/2018 03:35 PM, Matt Riedemann wrote:
On 3/27/2018 10:37 AM, Jay Pipes wrote:
If we want to actually fix the issue once and for all, we need to
make availability zones a real thing that has a permanent identifier
(UUID) and store that permanent
UC is also expected to enlist others and hopefully through our
efforts others are encouraged participate and enlist others.
[1] https://etherpad.openstack.org/p/uc-stein-ptg
[2] https://etherpad.openstack.org/p/UC-Election-Qualifications
Awesome, thank you Melvin and others on the UC.
--
Tha
1 - 100 of 2614 matches
Mail list logo