On Oct 23, 2013, at 5:56 PM, Aaron Rosen aro...@nicira.com wrote:
I believe he's referring to:
I found some more background on the feature (not
On Oct 24, 2013, at 7:47 AM, Day, Phil email@example.com wrote:
Yep, that was the feature I was referring to.
As I said I don't have anything defiant that shows this to be not working
(and the code looks fine) - just wanted to try and simplify the world a bit
for a while.
On Nov 24, 2013, at 7:37 AM, Thomas Goirand z...@debian.org wrote:
Someone sent a bug report against the python-novaclient package:
Could someone take care of this?
FYI to the thread, this patch is now up for this issue:
Recently a nova bug  was opened where the user describes a scenario where an
instance that is locked is still able to be snapshotted (create image and
backup). In the case of Trove, instances are locked ...to ensure integrity and
protect secrets which are needed by the resident
On Jun 17, 2014, at 13:34, Andrew Laski andrew.la...@rackspace.com wrote:
It appears that locking was added in 2010
(8aea573bd2e44e152fb4ef1627640bab1818dede), at which time commit messages
weren't nearly as clear and helpful as they now are so there's not much
insight from that. But the
On Jun 19, 2014, at 13:27, Michael Still mi...@stillhq.com wrote:
It might be a good idea to add a comment to the RPC layer for the
snapshot call explaining why we haven't implemented a lock check. That
would reduce future confusion as well.
I think that's a good idea -- will do that.
On Jun 20, 2014, at 11:07, Sean Dague s...@dague.net wrote:
H402 - 1 line doc strings should end in punctuation. The real statement
is this should be a summary sentence. A sentence is not just a set of
words that end in a period. Squirel fast bob. It's something deeper.
This rule thus isn't
On Jun 29, 2014, at 17:01, Michael Still mi...@stillhq.com wrote:
Hi. The meeting this week would be on the 3rd of July, which I assume
means that many people will be out of the office. Do people think its
worth running the meeting or shall we give this week a miss?
July 3 is a company
On Jul 4, 2014, at 3:11, Day, Phil firstname.lastname@example.org wrote:
I have a BP (https://review.openstack.org/#/c/89650) and the first couple of
bits of implementation (https://review.openstack.org/#/c/68942/
https://review.openstack.org/#/c/99916/) out for review on this very topic ;-)
On Jul 9, 2014, at 13:51, Matt Riedemann mrie...@linux.vnet.ibm.com wrote:
I've been beating my head against the wall a bit on unit tests too this week,
and here is another tip that just uncovered something for me when python -m
testtools.run and nosetests didn't help.
I sourced the tox
Hi Nova Bug Wranglers,
There have been some issues where the gerrit hook script is unable to link a
review to a launchpad bug e.g. no comment is posted to launchpad when a fix has
been proposed, even when the submitter has included the appropriate text
Closes-Bug: # in the commit message. This
On Jul 14, 2014, at 16:53, Michael Still mi...@stillhq.com wrote:
Jeremy helped me with this on IRC, and the hudson bot is now a member
of that group.
Wonderful -- thank you both!
OpenStack-dev mailing list
On Apr 23, 2014, at 17:15, Michael Still mi...@stillhq.com wrote:
I don't think we should block the possibility of there being a
novaclient specific BP sometime in the future. When we think of a good
reason for one, let's just put it in a subdirectory.
I agree. For example, this blueprint is
On May 6, 2014, at 15:22, Jamie Lennox jamielen...@redhat.com wrote:
If there are concerns with this process please respond here and/or on the
This sounds like it would be a fix for a bug affecting clients that I was
looking at recently:
On Sep 21, 2014, at 23:31, Deepak Shetty dpkshe...@gmail.com wrote:
Even better, whenever ./run_tests fail... maybe put a msg stating the
following C libs needs to be installed, have the user check the
same..something like that would help too.
I don't think it should be a human-maintained
On Oct 6, 2014, at 15:15, Anne Gentle a...@openstack.org wrote:
You got it Mike! Donating now!
This is awe-inspiring. Male allies are what we need, and you are delivering.
+1, and thank you Mike for sharing information about the Ada Initiative with us.
On Nov 4, 2014, at 0:32, Doug Hellmann d...@doughellmann.com wrote:
I think this is reasonable, though do we actually support setting
the same key twice ?
Yes, if it is registered in different groups.
I have found that for a MultiStrOpt, the same key can be set multiple times
even in the
On Nov 19, 2014, at 11:38, Everett Toews everett.to...@rackspace.com wrote:
Does anybody know what happened to the Etherpad? It’s completely blank now!!!
If you check the Timeslider, it appears that it only ever existed on Nov. 15.
I see it as blank now too, however I can see all
On Nov 24, 2014, at 13:06, Jay Pipes jaypi...@gmail.com wrote:
That said, I don't think it's wise to make oslo-versionedobjects be a totally
new thing. I think we should use nova.objects as the base of a new
oslo-versionedobjects library, and we should evolve oslo-versionedobjects
On Jun 20, 2013, at 5:36 PM, Christopher Yeoh wrote:
The management of security groups can be handled through the
project-formerly-known-as-quantum, but the (dis)association of security
groups to instances does I think need to be handled by Nova. So we'll need
On Jun 24, 2013, at 2:50 PM, Mark McLoughlin wrote:
Unlike other nitpicking I tend to do with commit messages, I previously
never thought this was worth even mentioning to committers but if some
reviewers were going to start -1ing people for the *correct* style then
I figured it was best to
I did the initial port of the security_groups api extension to v3 and have been
testing it out in devstack while adding the expected_errors decorator to it.
The guidance so far on network-related extensions in v3 is not to duplicate
actions that can be accomplished through the neutron
On Aug 13, 2013, at 2:11 AM, Day, Phil wrote:
If we really want to get clean separation between Nova and Neutron in the V3
API should we consider making the Nov aV3 API only accept lists o port ids in
the server create command ?
That way there would be no need to every pass security group
On Aug 13, 2013, at 3:35 PM, Melanie Witt wrote:
On Aug 13, 2013, at 2:11 AM, Day, Phil wrote:
If we really want to get clean separation between Nova and Neutron in the V3
API should we consider making the Nov aV3 API only accept lists o port ids
in the server create command ?
On Aug 15, 2013, at 1:13 PM, Joe Gordon wrote:
+1 from me as long as this wouldn't change anything for the EC2 API's
security groups support, which I assume it won't.
Correct, it's unrelated to the ec2 api.
We discussed briefly in the nova meeting today and there was consensus that
On Dec 8, 2014, at 13:12, Jeremy Stanley fu...@yuggoth.org wrote:
I'm dubious of this as it basically says we know this breaks
sometimes, so we're going to stop testing that it works at all and
possibly let it get even more broken, but you should be safe to rely
on it anyway.
+1, it seems
At some point, our db archiving functionality got broken because there was a
change to stop ever deleting instance system metadata . For those
unfamiliar, the 'nova-manage db archive_deleted_rows' is the thing that moves
all soft-deleted (deleted=nonzero) rows to the shadow
On Feb 4, 2015, at 16:31, Michael Still mi...@stillhq.com wrote:
Its been a week, so I have now added Melanie to this group. Welcome aboard!
Thank you! I am honored by the nomination and all of your votes.
It is my great pleasure to join python-novaclient-core. :)
On Feb 19, 2015, at 11:52, Terry Wilson twil...@redhat.com wrote:
Unfortunately, the new novaclient release ended up completely breaking the
neutron gate. The v1_1 deprecation broke our (voting) pylint test:
On Feb 19, 2015, at 12:48, Dan Smith d...@danplanet.com wrote:
Either convince neutron pylint not to care, or just convert the
uses in neutron to v2.
In pylint, E0611 is the check which could be disabled to ignore this case.
On Feb 19, 2015, at 13:38, Terry Wilson twil...@redhat.com wrote:
We've currently just disabled the pylint gate tests, and I've posted a patch
for neutron to resolve the issue. Looks like there was a similar patch
already up for review as well, though it only catches one of our uses of
On Feb 19, 2015, at 17:54, Matt Riedemann mrie...@linux.vnet.ibm.com wrote:
Regarding the novaclient change, the plan is to get either the devstack cells
exercise job voting on novaclient changes again (which it was at some point
prior to the 2.21 release and should have caught this
On Feb 6, 2015, at 8:17, Matt Riedemann mrie...@linux.vnet.ibm.com wrote:
We haven't done a release of python-novaclient in awhile (2.20.0 was released
on 2014-9-20 before the Juno release).
It looks like there are some important feature adds and bug fixes on master
so we should do a
On Feb 9, 2015, at 19:55, Michael Still mi...@stillhq.com wrote:
The previous policy is that we do a release when requested or when a
critical bug fix merges. I don't see any critical fixes awaiting
release, but I am not opposed to a release.
That's right. I think the keystone v3 support is
On Mar 9, 2015, at 13:14, Sean Dague s...@dague.net wrote:
So possibly another way to think about this is our prior signaling of
what was supported by Nova was signaled by the extension list. Our code
was refactored into a way that supported optional loading by that unit.
As we're making
On Mar 10, 2015, at 19:28, Chris St. Pierre chris.a.st.pie...@gmail.com wrote:
Ah, look at that! In some other projects, flake8 complains about a docstring
whose first line doesn't end in a period, so I didn't think it'd be possible.
If you don't think that's excessively verbose, there'll be
On Mar 10, 2015, at 7:32, Chris St. Pierre chris.a.st.pie...@gmail.com wrote:
I've just filed a bug on the confusing wording of help text for the
As I note in the bug, though, I'm
On Feb 24, 2015, at 9:47, Sean Dague s...@dague.net wrote:
I'm happy if there are other theories about how we do these things,
being the first functional test in the python-novaclient tree that
creates and destroys real resources, there isn't an established pattern
yet. But I think doing all
On Feb 25, 2015, at 10:51, Duncan Thomas duncan.tho...@gmail.com wrote:
Is there anybody who'd like to step forward in defence of this rule and
explain why it is an improvement? I don't discount for a moment the
possibility I'm missing something, and welcome the education in that case
On May 8, 2015, at 10:15, John Garbutt j...@johngarbutt.com wrote:
Melanie, welcome to nova-core :)
Thank you everyone, for your generous support. I am truly humbled.
I am thrilled to join nova-core and excited to work with all of you. :)
-melanie (irc: melwitt)
On Apr 14, 2015, at 12:03, Jeremy Stanley fu...@yuggoth.org wrote:
Our regular integration testing jobs do this by default. When a
change is proposed to a stable branch of a project, devstack-gate
checks out the same branch name for the other projects being tested
with it and updates
Thanks all who responded. I have put up a patch to remove the jobs:
And then next we need to get some stable branches cut and get some guidance
from infra on how we can run stable-compat-jobs only on changes proposed to
stable branches for novaclient.
I have started an etherpad for tracking low hanging fruit work in Nova:
I have linked it on the Nova Mentoring wiki  and populated it with a bit of
information about the remaining work that needs to be done to convert the rest
On Aug 19, 2015, at 16:51, Sylvain Bauza sba...@redhat.com wrote:
Instead of using the nested context managers, a way I like is to decorate a
nested function in the test and call it, for example:
I attended the ops mid cycle summit on Tuesday and Wednesday and here are brief
notes on the feedback I heard related to nova. Please feel free to add your
comments or correct me if I got anything wrong.
Large Deployments Session :
- There's a Neutron spec  for adding the
On Aug 20, 2015, at 5:40, Alex Xu hejie...@intel.com wrote:
So user may wrote client like this:
if response.status == 500 and ‘OverQuota’ in response.message:
I thought we're not supporting that type of case. My understanding is that we
should never be returning 500 and if we are,
On Jul 23, 2015, at 7:35, Adam Young ayo...@redhat.com wrote:
What this means is the if a user is assigned admin on any project, they are
assigned admin for everything.
Fixing this is going to require a change to how we write policy.
Each policy rule needs to have two parts:
Recently I have started reviewing the patch series about nested quotas in nova
 and I'm having trouble understanding where we currently are with identity
v3 support in nova. From what I read in a semi recent proposal  I think
things mostly just work if you configure to run
On Nov 6, 2015, at 7:32, John Garbutt wrote:
> I propose we add Alex Xu to nova-core.
> Over the last few cycles he has consistently been doing great work,
> including some quality reviews, particularly around the API.
> Please respond with comments, +1s,
On Nov 6, 2015, at 7:32, John Garbutt wrote:
> I propose we add Sylvain Bauza to nova-core.
> Over the last few cycles he has consistently been doing great work,
> including some quality reviews, particularly around the Scheduler.
> Please respond with
We have an issue  in python-novaclient 2.32.0 where it's not working with
It's caused by a commit  that changed the default requested compute API
version from "latest" to "client supported latest", a specific version. We have
some logic in the
On Oct 14, 2015, at 13:50, Matt Riedemann wrote:
> Well we at least have a bug to track against now:
I just proposed a possible fix  which is hacking the clouds.yaml for only
On Oct 12, 2015, at 12:14, Kevin L. Mitchell
> (For review https://review.openstack.org/232677)
With usage of v2.1 picking up (devstack) I find myself going to the API ref
documentation  often and find it lacking compared with the similar v2 doc
. I refer to this doc whenever I see a novaclient bug where something broke
with v2.1 and I'm trying to find out what the valid
On Sep 11, 2015, at 10:15, John Garbutt wrote:
> To make it easier to know who submitted what, we are going to try out
> google forms for the submissions:
> If that does not work for you, let me know, and I can see what can be done.
On Sep 30, 2015, at 14:45, Andrew Laski wrote:
> I have a slight preference for #1. Nova is not buggy here novaclient is so I
> think we should contain the fix there.
> Is using the v2 API an option? That should also allow the 3 extra parameters
> mentioned in #2.
I have been looking and haven't yet located documentation about how to upgrade
from glance v1 to glance v2.
From what I understand, images and snapshots created with v1 can't be
listed/accessed through the v2 api. Are there instructions about how to migrate
images and snapshots from
On Dec 10, 2015, at 15:57, Devananda van der Veen
> So, at this point, I think we need to accept that the scheduling of
> virtualized and bare metal workloads are two different problem domains that
> are equally complex.
> Either, we:
> * build a separate
On Jan 6, 2016, at 11:41, Andrew Laski wrote:
> As explained in
> http://lists.openstack.org/pipermail/openstack-dev/2016-January/083216.html a
> recurring calendar event based on alternating weeks will now be incorrect. I
> had to fix my calendar and I expect others will
On Nov 26, 2015, at 9:36, John Garbutt wrote:
> A suggestion in the past, that I like, is creating a nova functional
> test that stress tests the quota code.
> Hopefully that will be able to help reproduce the error.
> That should help prove if any proposed fix actually
On Nov 20, 2015, at 6:18, Sean Dague wrote:
> instance_actions seems extremely useful, and at the ops meetups I've
> been to has been one of the favorite features because it allows and easy
> interface for "going back in time" to figure out what happened.
Agreed, we're using it
On Jan 25, 2016, at 17:57, melanie witt <melwi...@gmail.com> wrote:
> Thanks!! That's indeed the same problem and removing the '$' from the
> exclude_regex worked for me. (ostestr --blacklist_file tests-py3.txt --regex
> "nova.tests.unit.network" ran all non-blackliste
On Feb 25, 2016, at 8:35, Michał Dulko wrote:
> We've faced similar issues in Cinder and as solution we've moved
> filtering to Python code. Like in for example  or . But no, we
> haven't had UNIQUE constraint on the DB column in these cases, only on IDs.
On Jan 22, 2016, at 19:14, Matthew Treinish wrote:
> Although, now that I look at the list it definitely looks like this one,
> which I had forgotten about:
> It sounds like that bug proposes a direction so if you
I noticed because of the way we run the py34 tests in tox.ini, I'm not able to
specify a filter regex the way I normally do as a positional arg, for example:
'tox -epy34 nova.tests.unit.network' doesn't filter and it runs everything.
('tox -epy27 nova.tests.unit.network' will only
On Feb 12, 2016, at 14:49, Jay Pipes wrote:
> This would be my preference as well, even though it's technically a
> backwards-incompatible API change.
> The idea behind get-me-a-network was specifically to remove the current
> required complexity of the nova boot command
On Mar 15, 2016, at 10:59, Tim Bell wrote:
> The risk I see is that we are missing input to the development process in
> view of the complexity of submitting those requirements. Clearly, setting the
> bar too low means that there is no clear requirement statement etc.
On Mar 17, 2016, at 9:41, Markus Zoeller wrote:
> What are the various reasons which block you to work on bug reports?
The number one reason for me is lack of information. The main things I want to
know are, what version, what commands/API calls did you do, what was the
On Mar 18, 2016, at 9:50, Andrew Laski wrote:
> I've adapted to the new interface and really like some of the new
> capabilities it provides, but having the page jump around while I'm
> commenting has been a huge annoyance.
I may have found a workaround for the scroll
On Mar 23, 2016, at 16:56, melanie witt <melwi...@gmail.com> wrote:
> I may have found a workaround for the scroll jumping after reading through
> the upstream issue comments : use the "Slow" setting in the preferences
> for Render. Click the gear icon in the upper
On Wed, 18 May 2016 14:30:00 -0500, Matt Riedemann wrote:
While convenient as a workaround, I'm not in favor of the idea of adding
something to the REST API so a user can force refresh the connection
info - this is a bug and leaks information out of the API about how the
cloud is configured. If
On Thu, 14 Apr 2016 13:17:48 -0500, Dean Troyer wrote:
My only real concern is you've implied a structure that will potentially
have many combinations of configurations and those will bitrot. How
different are x86 and s390 arch in local.conf? (I've never seen an s390
local.conf!) I do know
On Tue, 19 Apr 2016 19:31:04 +0800, Kenny Ji-work wrote:
I have installed openstack mitaka, when I execute any nova's commands
with the result displayed below:
[root@devstack scripts]# nova list
*ERROR (AttributeError): 'unicode' object has no attribute 'get'*
I installed openstack as
On Tue, 19 Apr 2016 10:02:46 -0400, Sean Dague wrote:
Right, I think in the Havana timeframe, things were very different. Part
of the rationale for full parity was that applications would be written
against nova-network, and smoothly transition to neutron. But with over
90% neutron, assuming
On Wed, 13 Apr 2016 12:53:12 -0500, Matt Riedemann wrote:
I'd like to propose that we make Andrey Kurilin core on python-novaclient.
He's been doing a lot of the maintenance the last several months and a
lot of times is the first to jump on any major issue, does a lot of the
I am working on a POC with this approach and will test all possible
scenarios (boot, resize, reboot, compute service stop/start,
Please let me know your opinion about the same or you have any other
solution in mind.
FWIW, I'm working on a patch to
On Wed, 1 Feb 2017 08:06:41 -0500, Davanum Srinivas wrote:
Three more from this morning, at least the first one looks new:
Apologies for the late notice, but there won't be a cells meeting this
afternoon being that everyone is busy scrambling for the feature freeze
deadline this week. Let's catch up after FF.
On Wed, 15 Feb 2017 16:12:14 -0500, Corey Bryant wrote:
This works but you have to specify all of the args (--cell_uuid, --name,
--transport-url and --database_connection). Otherwise you'll hit
Thanks for pointing that out.
It looks like the
On Wed, 15 Feb 2017 16:34:57 -0500, Corey Bryant wrote:
I think I figured it out. I'll submit a patch in a little bit.
Great, post a link to the patch after you upload it and we'll review.
Also note earlier I forgot to mention --name should also be optional for
the command (everything
On Tue, 8 Nov 2016 14:25:08 -0600, Matt Riedemann wrote:
While talking about that in the session, there was some brainstorming on
doing limit checks differently in the API. Basically, do away with
reservations, do a quick DB query to check quota before an operation
begins, and if it's OK go
On Mon, 14 Nov 2016 22:48:01 +0100, Sławek Kapłoński wrote:
Are You sure that but
https://bugs.launchpad.net/nova/+bug/1458122 is still valid? I tried to
spawn instances with min=3 and max=11 when quota was set to 10 and I had
spawned 10 instances properly (no any in error state). I also checked
On Mon, 14 Nov 2016 17:34:28 -0600, Matt Riedemann wrote:
Why do we want to return a list of uuids for servers created? I thought
that's why we have the 'return_reservation_id' request parameter for the
server multiple-create scenario so that you can get a single reservation
ID back and all of
On Tue, 22 Nov 2016 19:42:32 -0500, Emilien Macchi wrote:
On Tue, Nov 22, 2016 at 6:36 PM, melanie witt <melwi...@gmail.com> wrote:
In the Nova configuration, the 'my_ip' setting is the IP address the host
uses to connect to the management network . This is the IP Nova uses to
On Tue, 22 Nov 2016 11:39:54 -0500, Andrew Laski wrote:
It has been a true pleasure working with you all these past few years
and I'm thankful to have had the opportunity. As I've told people many
times when they ask me what it's like to work on an open source project
like this: working on
In the Nova configuration, the 'my_ip' setting is the IP address the
host uses to connect to the management network . This is the IP Nova
uses to set up iptables rules for the metadata service listening on port
By default, 'my_ip' is set to the result of
On Tue, 15 Nov 2016 18:10:40 -0600, Chris Friesen wrote:
I'm in favor of your change, since the existing behaviour doesn't make
But at some point I guess consistency trumps correctness, and if a new
microversion is necessary to mark the new behaviour then a spec is
required, and at that
On Tue, 6 Dec 2016 16:04:14 -0500, Jay Pipes wrote:
We're discussing only doing:
Once we start doing claims in the scheduler, we'll have the ability to do:
Thanks. FWIW, I'm not against simple non-JSON query params.
The last time we
On Fri, 13 Jan 2017 14:04:27 -0700, Alex Schultz wrote:
Just from the puppet standpoint, it's much easier to create the cell
and populate it after the fact and run some command to sync stuff
after the nodes have been added. This also would be easier to consume
for scale up/scale down actions.
On Fri, 6 Jan 2017 12:15:34 -0500, William M Edmonds wrote:
Why would someone need to change the defaults via REST API calls? I
agree that we should plan for that now if we think that will eventually
be needed, but I'm not seeing why it would be needed.
The REST API already allows people to
On Tue, 6 Dec 2016 15:42:18 -0500, Jay Pipes wrote:
On 12/06/2016 03:28 PM, Ed Leafe wrote:
On Dec 6, 2016, at 2:16 PM, Jay Pipes wrote:
I would prefer:
to "group" the resources parameter together. When
On Tue, 18 Jul 2017 09:22:31 +0900, Ghanshyam Mann wrote:
Yes, this is same case when we do fetch patch set using git checkout,
i do not think its something to do with gite review -d.
Doing that shouldn't change the author, at least in my experience. I
constantly 'git fetch' or 'git review -d
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
This data can get out of whack or need to be refreshed, like if your
I wanted to give everyone a heads up that we have found and fixed a bug
 on master where the number of database connections had increased so
much that we were starting to hit a "OperationalError
(pymysql.err.OperationalError) (1040, u'Too many connections')" in the
gate on some
On Thu, 7 Sep 2017 14:57:24 -0500, Matt Riedemann wrote:
Some more background information is in the ironic spec here:
Also, be aware of these release notes for Pike related to baremetal
On Wed, 20 Sep 2017 13:47:18 -0500, Matt Riedemann wrote:
Presumably there was a good reason why the instance failed to build on a
host originally, but that could be for any number of reasons: resource
claim failed during a race, configuration issues, etc. Since we don't
really know what
On Thu, 14 Sep 2017 11:15:26 -0600, Ed Leafe wrote:
On Sep 14, 2017, at 10:30 AM, melanie witt <melwi...@gmail.com> wrote:
I was thinking, if it's possible to assign more than one resource class to an Ironic
node, maybe you could get similar behavior to the old non-exact filters. So
On Fri, 29 Sep 2017 13:49:55 -0500, Matt Riedemann wrote:
For awhile now actually.
Someone was asking about when archive_deleted_rows would actually work,
and the answer is, it should since at least mitaka:
On Tue, 22 Aug 2017 20:18:18 -0500, Matt Riedemann wrote:
So to the existing core team members, please respond with a yay/nay and
after about a week or so we should have a decision (knowing a few cores
are on vacation right now).
This is just a brief status about the blueprints currently occupying
review runways  and an ask for the nova-core team to give these
reviews priority for their code review focus.
* XenAPI: Support a new image handler for non-FS based SRs
1 - 100 of 259 matches
Mail list logo