Howdy all,
We've made a list of cross-project forum sessions and nova-related
sessions/presentations that you might be interested in attending at the
summit and added them to our forum etherpad:
https://etherpad.openstack.org/p/nova-forum-stein
The "Cross-project Forum sessions that should i
On Fri, 2 Nov 2018 09:47:42 +0100, Andreas Scheuring wrote:
Dear Nova Community,
I want to announce the new focal point for Nova s390x libvirt/kvm.
Please welcome "Cathy Zhang” to the Nova team. She and her team will be
responsible for maintaining the s390x libvirt/kvm Thirdparty CI [1] and an
Howdy all,
This is a heads up that we will not hold a nova meeting next week
November 15 because of summit week. And we will also not hold a nova
meeting the following week November 22 because of the US holiday of
Thanksgiving, as we're unlikely to find anyone to run it during the 2100
UTC ti
Hey all,
Here's some notes I took in forum sessions I attended -- feel free to
add notes on sessions I missed.
Etherpad links: https://wiki.openstack.org/wiki/Forum/Berlin2018
Cheers,
-melanie
TUE
---
Cells v2 updates
- Went over the etherpad, no objections to anything
- N
On Mon, 19 Nov 2018 17:19:22 +0100, Surya Seetharaman wrote:
On Mon, Nov 19, 2018 at 2:39 PM Matt Riedemann <mailto:mriede...@gmail.com>> wrote:
On 11/19/2018 3:17 AM, melanie witt wrote:
> - Not directly related to the session, but CERN (hallway track) and
>
On Wed, 21 Nov 2018 12:11:50 -0600, Miguel Lavalle wrote:
One of the key goals of StarlingX during the current cycle is to
converge with the OpenStack projects master branches. In order to
accomplish this goal, the Technical Steering Committee put together a
gap analysis that shows the specs an
On Wed, 21 Nov 2018 21:23:51 +0100, Melanie Witt wrote:
On Wed, 21 Nov 2018 12:11:50 -0600, Miguel Lavalle wrote:
One of the key goals of StarlingX during the current cycle is to
converge with the OpenStack projects master branches. In order to
accomplish this goal, the Technical Steering
On Nov 24, 2013, at 7:37 AM, Thomas Goirand wrote:
> Someone sent a bug report against the python-novaclient package:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728470
>
> Could someone take care of this?
FYI to the thread, this patch is now up for this issue:
https://review.openstack.
On Nov 19, 2014, at 11:38, Everett Toews 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.
> Bizarre.
I see it as blank now too, however I can see all of the previous revision
On Nov 24, 2014, at 13:06, Jay Pipes 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
> slowly over time, event
On Dec 8, 2014, at 13:12, Jeremy Stanley 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 bad to enable
Hi everybody,
At some point, our db archiving functionality got broken because there was a
change to stop ever deleting instance system metadata [1]. For those
unfamiliar, the 'nova-manage db archive_deleted_rows' is the thing that moves
all soft-deleted (deleted=nonzero) rows to the shadow tab
On Apr 23, 2014, at 17:15, Michael Still 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 about improvin
On May 6, 2014, at 15:22, Jamie Lennox wrote:
> If there are concerns with this process please respond here and/or on the
> review.
This sounds like it would be a fix for a bug affecting clients that I was
looking at recently:
https://bugs.launchpad.net/python-novaclient/+bug/1154809
If so,
Hi all,
Recently a nova bug [1] 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 Trov
On Jun 16, 2014, at 13:56, Michael Still wrote:
> It is certainly my belief that the lock functionality for instances is
> about avoiding accidental changes to the instance itself, not the
> contents of the instance. I personally think that snapshots aren't a
> change to the instance and therefo
On Sep 21, 2014, at 23:31, Deepak Shetty 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 list, otherwise it
On Oct 6, 2014, at 15:15, Anne Gentle 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.
signature.asc
Description: Message signed with OpenPG
On Nov 4, 2014, at 0:32, Doug Hellmann 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 same group, and
On Jun 17, 2014, at 13:34, Andrew Laski 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 lock checking methods a
On Jun 19, 2014, at 13:27, Michael Still 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.
signature.asc
Descri
On Jun 20, 2014, at 11:07, Sean Dague 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 really seman
On Jun 29, 2014, at 17:01, Michael Still 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 holiday where I am, s
Hi all,
I noticed in nova/virt/libvirt/driver.py we use domain destroy instead of
domain shutdown in most cases (except for soft reboot). Is there a special
reason we don't use shutdown to do a graceful shutdown of the guest for the
stop, shelve, migrate, etc functions? Using destroy can corrup
On Jul 4, 2014, at 3:11, "Day, Phil" 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 ;-)
Great, I'll review and a
On Jul 9, 2014, at 13:51, Matt Riedemann 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 virtualenv and then ran
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. Thi
On Jul 14, 2014, at 16:53, "Michael Still" 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
OpenStack-dev@lists.openstack.org
http://lists.openst
On Oct 23, 2013, at 5:56 PM, Aaron Rosen wrote:
> I believe he's referring to:
> https://github.com/openstack/nova/blob/master/nova/network/model.py#L335
> https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L1211
I found some more background on the feature (not configurable)
On Oct 24, 2013, at 7:47 AM, "Day, Phil" 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.
Of course. That's what I
Me too, that was sort of awesome.
I also wish we could get rid of XML but that might be primarily because I find
it awkward to work with the way it is now.
As was mentioned before, I think the main thing is making it easier to support.
The autogeneration idea is great.
On Jun 20, 2013, at 4:10
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
> the SecurityGroupActionCon
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
Hi All,
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 a
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 g
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 t
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
removin
Hi everyone,
We have an issue [1] in python-novaclient 2.32.0 where it's not working with
rackspace cloud.
It's caused by a commit [2] that changed the default requested compute API
version from "latest" to "client supported latest", a specific version. We have
some logic in the discover_versi
On Nov 6, 2015, at 7:32, John Garbutt wrote:
> Hi,
>
> I propose we add Alex Xu[1] 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, or objections within on
On Nov 6, 2015, at 7:32, John Garbutt wrote:
> Hi,
>
> I propose we add Sylvain Bauza[1] 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 comments, +1s, or objectio
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 because it's such
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 works.
+1, I think it'
-@openstack
On Dec 1, 2015, at 11:45, Vilobh Meshram
wrote:
> If you can share the details of the bug that Joe mentioned, to reproduce
> quota bugs locally, it would be helpful.
Here's the bug comment I was thinking of, #15 by jogo on the script he used to
make quotas go out of sync while re
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 y
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
microversion work, a
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 ther
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
the http:
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 some
On Dec 10, 2015, at 15:57, Devananda van der Veen
wrote:
> 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 scheduler process in Ironic,
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 want to do the same.
Hi everyone,
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 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:
>
> https://bugs.launchpad.net/os-testr/+bug/1506215
>
> It sounds like that bug proposes a direction so if you could patch os-testr
> to
On Jan 25, 2016, at 17:57, melanie witt 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-blacklisted netw
Hi Everyone,
Recently I have started reviewing the patch series about nested quotas in nova
[1] 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 [2] I think
things mostly "just work" if you configure to run
On Jul 23, 2015, at 7:35, Adam Young 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:
>
> 1. Match the sco
On Aug 19, 2015, at 16:51, Sylvain Bauza wrote:
> Ideas appreciated.
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:
def test_thing(self):
@mock.patch(...)
@mock.patch(...)
@mock.patch(...)
def
On Aug 20, 2015, at 5:40, Alex Xu 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, it's a bug fix
Hi Everyone,
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 [1]:
- There's a Neutron spec [2] for adding the c
Hi All,
With usage of v2.1 picking up (devstack) I find myself going to the API ref
documentation [1] often and find it lacking compared with the similar v2 doc
[2]. 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 req
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:
> http://goo.gl/forms/D2Qk8XGhZ6
>
> If that does not work for you, let me know, and I can see what can be done.
Today I was informed that g
Hi All,
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 v1
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.
+1. I have put up http
On Oct 12, 2015, at 12:14, Kevin L. Mitchell
wrote:
> http://logs.openstack.org/77/232677/1/check/gate-novaclient-dsvm-functional/2de31bc/
> (For review https://review.openstack.org/232677)
>
> http://logs.openstack.org/99/232899/1/check/gate-novaclient-dsvm-functional/6d6dd1d/
> (For review ht
On Oct 14, 2015, at 13:50, Matt Riedemann wrote:
> Well we at least have a bug to track against now:
>
> https://bugs.launchpad.net/python-novaclient/+bug/1506103
Thanks.
I just proposed a possible fix [1] which is hacking the clouds.yaml for only
the functional test job in the post test hook
Hi All,
I have started an etherpad for tracking "low hanging fruit" work in Nova:
https://etherpad.openstack.org/p/nova-low-hanging-fruit
I have linked it on the Nova Mentoring wiki [1] and populated it with a bit of
information about the remaining work that needs to be done to convert the rest
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 with regards to netw
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 [1] or [2]. But no, we
> haven't had UNIQUE constraint on the DB column in these cases, only on IDs.
This is an interesting option.
I
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. However,
> I think the co
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
behavior, what behavior
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 jumping after reading thr
On Mar 23, 2016, at 16:56, melanie witt wrote:
> I may have found a workaround for the scroll jumping after reading through
> the upstream issue comments [1]: use the "Slow" setting in the preferences
> for Render. Click the gear icon in the upper right corner of the diff vi
On Feb 4, 2015, at 16:31, Michael Still 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. :)
melanie (melwitt)
signature.asc
Descrip
On Feb 6, 2015, at 8:17, Matt Riedemann 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 release, specifically to p
On Feb 9, 2015, at 19:55, Michael Still 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 important and
On Feb 19, 2015, at 11:52, Terry Wilson wrote:
> Unfortunately, the new novaclient release ended up completely breaking the
> neutron gate. The v1_1 deprecation broke our (voting) pylint test:
> https://jenkins04.openstack.org/job/gate-neutron-pylint/1383/console
>
> 2015-02-19 18:37:06.932 |
On Feb 19, 2015, at 12:48, Dan Smith 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.
http://pylint-messages.wikidot.com/messages:e0611
melanie (melwitt)
signature.
On Feb 19, 2015, at 13:38, Terry Wilson 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
> novaclient. There'
On Feb 19, 2015, at 17:54, Matt Riedemann 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 problem), or get a
> functional
On Feb 24, 2015, at 9:47, Sean Dague 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 CLI calls i
On Feb 25, 2015, at 10:51, Duncan Thomas 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
A reason I can think of wo
On Mar 9, 2015, at 13:14, Sean Dague 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 things less
On Mar 10, 2015, at 7:32, Chris St. Pierre wrote:
> I've just filed a bug on the confusing wording of help text for the
> secgroup-{add,delete,list}-default-rules? commands:
> https://bugs.launchpad.net/python-novaclient/+bug/1430354
>
> As I note in the bug, though, I'm not sure the best way
On Mar 10, 2015, at 19:28, Chris St. Pierre 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 a patch in
> shortly. T
Thanks all who responded. I have put up a patch to remove the jobs:
https://review.openstack.org/#/c/173547/
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.
On Apr 14, 2015, at 12:03, Jeremy Stanley 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 requirements based on
On May 8, 2015, at 10:15, John Garbutt 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)
signature.asc
Description: Message signed
Hey Folks,
I wanted to give everyone a heads up that we have found and fixed a bug
[1] 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, 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 or need to be refreshed, like if your
ceph
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 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).
+1
___
On Thu, 7 Sep 2017 14:57:24 -0500, Matt Riedemann wrote:
Some more background information is in the ironic spec here:
https://review.openstack.org/#/c/500429/
Also, be aware of these release notes for Pike related to baremetal
scheduling:
http://docs-draft.openstack.org/77/501477/1/check/gat
On Thu, 14 Sep 2017 11:15:26 -0600, Ed Leafe wrote:
On Sep 14, 2017, at 10:30 AM, melanie witt 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 if you have
an od
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 origin
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:
https://review.openstack.org/#/q/I77255c77780f0c2b99d59a9c20adecc85335bb18
And starti
On Fri, 15 Dec 2017 18:38:00 -0800, Arun Sag wrote:
Here are the sequence of actions happen in nova-network
1. allocate_for_instance calls -> allocate_fixed_ips
2. FixedIPs are successfully associated (we can see this in the log)
3. allocate_for_instance calls get_instance_nw_info, which in turn
On Thu, 4 Jan 2018 08:46:38 -0600, Matt Riedemann wrote:
The main issue is for newer jobs like tempest-full, the logs are under
controller/logs/ and we lose the log analyze formatting for color, being
able to filter on log level, and being able to link directly to a line
in the logs.
I also n
On Fri, 05 Jan 2018 10:43:59 -0800, Clark Boylan wrote:
To expand a bit more on that what we are attempting to do is port the log
handling code in devstack-gate [0] to zuul v3 jobs living in tempest [1]. The
new job in tempest itself relies on the ansible process-test-results role
which can b
Hello Stackers,
This is a heads up to any of you using the AggregateCoreFilter,
AggregateRamFilter, and/or AggregateDiskFilter in the filter scheduler.
These filters have effectively allowed operators to set overcommit
ratios per aggregate rather than per compute node in <= Newton.
Beginning
I am working on a POC with this approach and will test all possible
scenarios (boot, resize, reboot, compute service stop/start,
shelved-unshelved etc).
Please let me know your opinion about the same or you have any other
solution in mind.
Hi Abhishek,
FWIW, I'm working on a patch to prop
> On Jan 29, 2018, at 16:45, Arun SAG wrote:
>
> If anyone is running into db race while running database in
> master-slave mode with async replication, The bug has been identified
> and getting fixed here
> https://bugs.launchpad.net/oslo.db/+bug/1746116
Thanks for your persistence in tracking
1 - 100 of 263 matches
Mail list logo
