that it's not available yet and anything to do with
alternatives is future work.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
is
needed that tells the admin how to configure the transport_url for the not
ifications.
This was done as part of the cells v2 layout docs here:
https://docs.openstack.org/nova/latest/user/cellsv2_layout.html#notifications
--
Thanks,
Matt
this config
option and reply to this thread, since the change to deprecate the
option in nova just merged:
https://review.openstack.org/498113
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions
.
I mean, if we thought hooks were bad, this is pretty terrible.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs
and
tag it with pike-rc-potential.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi
and
after about a week or so we should have a decision (knowing a few cores
are on vacation right now).
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
any custom resource class from an ironic node
in the Placement service if it does not already exist so it can be used
later for scheduling with flavors that have the resource class set.
--
Thanks,
Matt
__
OpenStack
.
If this is all transitional code, we should really document the hell out
of this in the RequestSpec class itself for anyone trying to write new
client side code with it, like me.
[1] https://bugs.launchpad.net/nova/+bug/1712008
--
Thanks,
Matt
need to be though, so could you split
this out and we could just merge it on it's own?
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
,
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
to search for stuff?
Because when I'm in nova docs looking for rbd stuff, I don't want to
sift through forum questions or glance docs or cinder docs, etc.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage
.
--
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
first - not that anyone has to talk to me about it to nominate
themselves.
Also, I've been kind of sort of distracted by this whole release
candidate thing going on right now...
--
Thanks,
Matt
__
OpenStack Development
sure why Nova should be
involved here. We dropped all support for extending the API via
stevedore extension loading in Pike [1]. The virt drivers don't extend
the REST API either.
[1] https://blueprints.launchpad.net/nova/+spec/api-no-more-extensions-pik
wanted to upstream this.
For information on contributing features to Nova, you can start here:
https://docs.openstack.org/nova/latest/contributor/blueprints.html
--
Thanks,
Matt
__
OpenStack Development Mailing List
/tree/master/nova/api/openstack/compute
I seem to remember a team in China at IBM working on VMware snapshots
years ago, or something like this, for a product, so maybe you stumbled
upon that.
--
Thanks,
Matt
maintaining these jobs? If not, they should be moved to the
experimental queue so they can be run on demand, not in the check queue
for every patch set proposed to Trove. These are also single and
multi-node jobs, so they are needlessly eating up node pool resources.
--
Thanks,
Matt
On 8/2/2017 10:04 AM, Matt Riedemann wrote:
and we're not going
to use it in multinode scenarios.
Why would you not run this in multinode scenarios? That's the only time
this is really a problem, because in the single node case we're
discovering and mapping the compute node late enough
RC1 on 8/10 before doing this? We already
broke the gate and lost at least 6-10 hours last week on the day of
feature freeze because of this.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions
/source/cli-delete-an-instance.rst
--
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
Now that we're past feature freeze for Pike, I've started an etherpad
for tracking items needed to get done before the first release candidate
here:
https://etherpad.openstack.org/p/nova-pike-release-candidate-todo
Just a reminder but Pike RC1 is Thursday August 10th.
--
Thanks,
Matt
volume extend stuff, which isn't related to
Glance, so does having the minimum bump in glance* matter?
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
that the libvirt volume driver would also have to be added back to
Nova, since we dropped that after Cinder dropped the volume driver.
https://review.openstack.org/#/c/463992/
--
Thanks,
Matt
__
OpenStack Development Mailing List
with this. Please create a blueprint in nova so we can track it as a
feature since that's what it is.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
On 7/26/2017 11:34 AM, Matt Riedemann wrote:
On 7/26/2017 11:23 AM, Matt Riedemann wrote:
Given this, what else do you need? Please be clear about what your use
case is and how it is not solved using the 2.53 microversion. There
may need to be changes to the CLI but let's separate
On 7/26/2017 11:23 AM, Matt Riedemann wrote:
Given this, what else do you need? Please be clear about what your use
case is and how it is not solved using the 2.53 microversion. There may
need to be changes to the CLI but let's separate that concern from the
REST API changes.
I think your
eview.openstack.org/#/c/485435/
Given this, what else do you need? Please be clear about what your use
case is and how it is not solved using the 2.53 microversion. There may
need to be changes to the CLI but let's separate that concern from the
REST API chang
y easy enough to do that.
--
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/li
as a result, please reply to this thread or
yell at us (mriedem/dansmith/melwitt) in the openstack-nova channel.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
://review.openstack.org/#/c/484935/
--
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
I wanted to get some things documented for the Queens PTG so I've
started an etherpad:
https://etherpad.openstack.org/p/nova-ptg-queens
Feel free to put down things you'd like to discuss. We'll shape it up later.
--
Thanks,
Matt
-4de3-9da7-8eb3de9e305e,vcpu_model=VirtCPUModel,vcpus=1,vm_mode=None,vm_state='active'),
'a4eba582-075a-4200-ae6f-9fc7797c95dd':
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
/cinder/neutron/keystone and whoever else is
logging request IDs in the API?
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
On 7/18/2017 12:07 PM, Mooney, Sean K wrote:
Resending with correct subject line
The real correct subject line tag would be [nova] or [nova][neutron]. :P
--
Thanks,
Matt
__
OpenStack Development Mailing List
somehow?
I've deferred the blueprint to Queens. We can re-assess at the PTG.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
: git-review
Version: 1.25.0
--
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
-versioned-notifications
I don't know if all of the dependencies are done, and it looks like the
Nova changes are pretty stale. Should we just defer this to Queens?
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage
r usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Thanks for bringing this up. Your fix is in the wrong place, s
://eavesdrop.openstack.org/meetings/nova/2017/nova.2017-07-13-14.00.html
[2] https://etherpad.openstack.org/p/nova-pike-feature-freeze-status
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
not be an error condition if you're
trying to update the state of a resource and it's already at that state.
I don't have a PhD in REST though so would like broader discussion on this.
[1] http://www.restapitutorial.com/lessons/idempotency.html
--
Thanks,
Matt
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
Done.
--
Thanks,
Matt
__
OpenStack
__
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
n each, and used the max/min
versions for the behavior differences for when they are optional or not,
but I can see where it's still a bit confusing.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage quest
missing some details:
https://review.openstack.org/#/c/481748/
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http:/
active since he was laid
off from OSIC, which was back in May.
We also need to add some upgrade testing in the Grenade project so that
we can be sure a volume attached in Ocata is properly detached in Pike.
Steve Noyes was investigating this.
--
Thanks,
Matt
On 7/6/2017 9:50 AM, Matt Riedemann wrote:
Another alternative is we should be able to test evacuate with the
in-tree functional tests using fixtures. That kind of testing only gives
us so much coverage since we have to stub some things out, but it would
at least test the mechanics
e
in-tree functional tests using fixtures. That kind of testing only gives
us so much coverage since we have to stub some things out, but it would
at least test the mechanics of an evacuate through all of the services.
--
Tha
t security group(s) and then attach that port to the server
instance in nova.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subjec
to be
done by the end of the Pike release, so time is a factor.
[1] https://review.openstack.org/#/c/472275/
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
On 6/21/2017 4:28 PM, Rochelle Grober wrote:
From: Matt
On 6/21/2017 7:04 AM, Shewale, Bhagyashri wrote:
I would like to write functional tests to check the exact req/resp
for each placement API for all supported versions similar
to what is already done for other APIs under
nova/tests
n't know how you solve that one. People are going to
work on what they are paid to work on.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.opens
Gs fix that in a way that work groups haven't?
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack
with placement.
He's talked about building something into the gabbi library for this,
but I don't know if that's being worked on or not.
Chris is also on vacation for a couple of weeks, just FYI.
--
Thanks,
Matt
rsion.
I'm posting this in the mailing list for wider discussion/input.
[1] https://review.openstack.org/#/c/435141/
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
cells v2 cells in Pike.
[1] https://review.openstack.org/#/c/436094/
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
Amrith,
Some good thoughts in your email. I've replied to a few specific pieces
below. Overall I think it's a good start to a plan.
On Sun, Jun 18, 2017 at 5:35 AM, Amrith Kumar
wrote:
> Trove has evolved rapidly over the past several years, since integration
> in
budget decisions at a
company determining what to invest in. I think Doug has tried to explain
that perspective a bit elsewhere in this thread, and it sounds like
that's the key issue, the outside perspective from people making budget
decisi
nt 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 Developme
ded=delete-an-image-detail#delete-an-image
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.o
for what they support
and then work on reducing the number of things they don't support. We've
been doing that for ages now.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack
On 6/16/2017 8:13 PM, Matt Riedemann wrote:
Yeah there is a distinction between the ceph nv job that runs on
nova/cinder/glance changes and the ceph job that runs on os-brick and
glance_store changes. When we made the tempest dsvm ceph job non-voting
we failed to mirror that in the os-brick
to mirror that in the os-brick/glance-store jobs. We should do
that.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
fix it on their end.
--
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
to be demoralizing to the development community.
I'm not trying to offend or troll so much as vent some frustration.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
on #openstack-dev and we'll try to work through it.
-Sean
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
g and just fix it that way for #2? :) Because (1) it
doesn't make sense, as far as we know, and (2) it forces the operator to
have to use the API to enable them later just to fix their nova
service-list output.
--
Tha
On 6/13/2017 12:19 PM, Matt Riedemann wrote:
With this change in Pike:
https://review.openstack.org/#/c/442162/
The PUT /os-services/* APIs to enable/disable/force-down a service will
now only work with nova-compute services. If you're using those to try
and disable a non-compute service
ade the
nova/ironic interaction for users and operators, and developers by
bridging the gap on both sides.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-r
://review.openstack.org/#/c/464280/11/nova/api/openstack/compute/services.py@288
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Good luck with the new position Roman. You've always been a great help
not only in Oslo land but also helping us out in Nova. You'll be missed.
--
Thanks,
Matt
ame. I use
Stackalytics the same way.
Note, however, that reviewstats is also published from a site that
russellb has running, e.g.:
http://russellbryant.net/openstack-stats/nova-reviewers-30.txt
--
Thanks,
Matt
__
we'd work on that in Queens.
I definitely want to use new shiny things at some point, we just have to
handle the old crufty things too.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions
On 6/8/2017 1:39 PM, melanie witt wrote:
On Thu, 8 Jun 2017 08:58:20 -0500, Matt Riedemann wrote:
Nova stores the output of the Cinder os-initialize_connection info API
in the Nova block_device_mappings table, and uses that later for
making volume connections.
This data can get out of whack
On 6/8/2017 10:17 AM, Arne Wiebalck wrote:
On 08 Jun 2017, at 15:58, Matt Riedemann <mriede...@gmail.com
<mailto:mriede...@gmail.com>> wrote:
Nova stores the output of the Cinder os-initialize_connection info API
in the Nova block_device_mappings table, and uses that later
eventually said no to that, and stated why here:
https://docs.openstack.org/developer/nova/policies.html#metrics-gathering
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 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
are not a substitute for
documenting how to use a feature. Specs aren't really either, or
shouldn't be, but sometimes that's the only thing we have since we don't
get things into the manuals or in-tree devref.
That's my way of saying I think a spec is a good idea.
--
Thanks,
Matt
1/check/gate-tempest-dsvm-multinode-live-migration-ubuntu-xenial/546935b/logs/screen-n-cpu.txt.gz?level=TRACE#_Jun_05_15_56_42_184587
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: o
Regards
Chaoyi Huang (joehuang)
__
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/opens
similar and I'm happy to say they said the same things.
Just wish I'd seen this earlier. :)
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
+1, especially because now I don't have to write the governance patch
for this which was a TODO of mine from the summit.
--
Thanks,
Matt
code, like
default policy and privsep, the better.
--
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
discussion here:
http://lists.openstack.org/pipermail/openstack-dev/2017-May/117242.html
Which turned into a discussion about porcelain APIs.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions
ave to run it serially.
So do you plan on leaving those tests in Tempest or moving them into the
Cinder repo and making them run under a separate tox serial environment?
[1] https://bugs.launchpad.net/nova/+bug/1547142
[2] https://bugs.launchpad.net/cinder/+bug/1527278
--
Tha
On 4/13/2017 11:45 AM, Matt Riedemann wrote:
This came up in the nova/cinder meeting today, but I can't for the life
of me think of why we don't unbind ports or terminate the connection
volumes when we shelve offload an instance from a compute host.
When you unshelve, if the instance
I've reported a bug here:
https://bugs.launchpad.net/nova/+bug/1694543
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
Fix is proposed here:
https://review.openstack.org/#/c/468585/
This is just FYI so people aren't needlessly rechecking.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
://docs.openstack.org/releasenotes/nova/ocata.html
[1] http://lists.openstack.org/pipermail/openstack-dev/2017-May/117132.html
[2] https://review.openstack.org/#/c/468388/
[3] https://review.openstack.org/#/c/468387/
--
Thanks,
Matt
applications then OpenStack will
be relevant for a very long time indeed.
I enjoyed this, thank you.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
ame server,
and in this case you'd have to detach the port(s) that were previously
created?
I don't know how Heat works, but if that's the case, then yeah that
doesn't sound fun, but I think Nova provides the APIs to be able to do this.
--
Thanks,
M
On 5/24/2017 2:46 PM, Doug Hellmann wrote:
Please take a look at
the results and let me know if that's doing what you all expect.
Tested this out locally and it fixes my issue. Thanks Doug!
--
Thanks,
Matt
__
OpenStack
On 5/24/2017 9:59 AM, Matt Riedemann wrote:
I started going down a path the other night of trying to see if we could
bulk query floating IPs when building the internal instance network info
cache [1] but it looks like that's not supported. The REST API docs for
Neutron say that you can't
/2017-May/117096.html
--
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
vertical is hard to follow though, it would
be nice if the graph could be expanded horizontally.
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
[5]
https://specs.openstack.org/openstack/nova-specs/specs/liberty/implemented/metadata-service-network-info.html#rest-api-impact
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstac
in
the glueteus maximus. I asked Matt for help to find out what API's had been
deprecated, he almost immediately helped me with a list and I'm working
through getting them fixed (Thanks Matt).
I'm merely raising the generic question of whether or not planned
deprecations should be done before Milestone
ctually do that upstream. So it's always funny (in
a sad way) how much people clamor for stable branch support upstream,
and for a long time period, but people aren't even proposing backports
upstream en masse. Anyway, there is my dig since you brought it back up. :)
--
Tha
this for volumes, when are we going to
start seeing people asking for passing more detailed information about
Neutron ports when creating a server?
--
Thanks,
Matt
__
OpenStack Development Mailing List (not for usage
601 - 700 of 2548 matches
Mail list logo