On 08/20/2014 08:27 AM, Joe Gordon wrote:
On Aug 19, 2014 10:45 AM, Day, Phil philip@hp.com
mailto:philip@hp.com wrote:
-Original Message-
From: Nikola Đipanov [mailto:ndipa...@redhat.com
mailto:ndipa...@redhat.com]
Sent: 19 August 2014 17:50
To: openstack-dev
On 08/20/2014 02:33 PM, Jay Pipes wrote:
On 08/20/2014 04:48 AM, Nikola Đipanov wrote:
Fair enough - I will WIP the revert until Phil is back. It's the right
thing to do seeing that he is away.
Well, it's as much (or more?) Paul Murray and Andrea Rosa :)
Yes sorry - meant to say Paul
Since after a week of discussing it I see no compelling argument against
reverting it - here's the proposal:
https://review.openstack.org/115218
Thanks,
N.
On 08/12/2014 12:21 PM, Nikola Đipanov wrote:
Hey Nova-istas,
While I was hacking on [1] I was considering how to approach the fact
On 08/19/2014 06:39 PM, Sylvain Bauza wrote:
On the other hand, ERT discussion is decoupled from the scheduler split
discussion and will be delayed until Extensible Resource Tracker owner
(Paul Murray) is back from vacation.
In the mean time, we're considering new patches using ERT as
On 08/14/2014 10:25 PM, Sylvain Bauza wrote:
Hi mikal,
Le 14 août 2014 01:49, Michael Still mi...@stillhq.com
mailto:mi...@stillhq.com a écrit :
So, there's been a lot of email in the last few days and I feel I am
not keeping up.
Sylvain, can you summarise for me what the plan is here?
On 08/13/2014 06:05 PM, Sylvain Bauza wrote:
Le 13/08/2014 12:21, Sylvain Bauza a écrit :
Le 12/08/2014 22:06, Sylvain Bauza a écrit :
Le 12/08/2014 18:54, Nikola Đipanov a écrit :
On 08/12/2014 04:49 PM, Sylvain Bauza wrote:
(sorry for reposting, missed 2 links...)
Hi Nikola,
Le 12
On 08/13/2014 04:05 AM, Michael Still wrote:
On Wed, Aug 13, 2014 at 4:26 AM, Eoghan Glynn egl...@redhat.com wrote:
It seems like this is exactly what the slots give us, though. The core
review
team picks a number of slots indicating how much work they think they can
actually do (less than
Hey Nova-istas,
While I was hacking on [1] I was considering how to approach the fact
that we now need to track one more thing (NUMA node utilization) in our
resources. I went with - I'll add it to compute nodes table thinking
it's a fundamental enough property of a compute host that it deserves
On 08/12/2014 04:49 PM, Sylvain Bauza wrote:
(sorry for reposting, missed 2 links...)
Hi Nikola,
Le 12/08/2014 12:21, Nikola Đipanov a écrit :
Hey Nova-istas,
While I was hacking on [1] I was considering how to approach the fact
that we now need to track one more thing (NUMA node
On 08/08/2014 12:12 AM, Stefano Maffulli wrote:
On 08/07/2014 01:41 PM, Eoghan Glynn wrote:
My point was simply that we don't have direct control over the
contributors' activities
This is not correct and I've seen it repeated too often to let it go
uncorrected: we (the OpenStack project as
On 08/08/2014 11:37 AM, Thierry Carrez wrote:
Personally I think we just need to get better at communicating the
downstream expectations, so that if we create waste, it's clearly
upstream fault rather than downstream. Currently it's the lack of
communication that makes developers produce more
On 08/06/2014 07:54 PM, Jay Pipes wrote:
I bring this up on the mailing list because I think Liyi's patch offers
an interesting future direction to the way that we think about our retry
approach in Nova. Instead of having hard-coded or configurable interval
times, I think Liyi's approach of
On 08/07/2014 03:20 PM, Russell Bryant wrote:
On 08/07/2014 09:07 AM, Sean Dague wrote: I think the difference is
slot selection would just be Nova drivers. I
think there is an assumption in the old system that everyone in Nova
core wants to prioritize the blueprints. I think there are a bunch
On 07/30/2014 11:02 PM, Michael Still wrote:
Greetings,
I would like to nominate Jay Pipes for the nova-core team.
Jay has been involved with nova for a long time now. He's previously
been a nova core, as well as a glance core (and PTL). He's been around
so long that there are probably
On 07/29/2014 11:03 AM, Daniel P. Berrange wrote:
On Mon, Jul 28, 2014 at 09:30:24AM -0700, Vishvananda Ishaya wrote:
I think we should discuss adding/changing this functionality. I have had
many new users assume that booting from an iso image would give them a
root drive which they could
On 07/09/2014 10:51 PM, Matt Riedemann wrote:
On 6/12/2014 6:17 AM, Daniel P. Berrange wrote:
On Thu, Jun 12, 2014 at 07:07:37AM -0400, Sean Dague wrote:
On 06/12/2014 06:59 AM, Daniel P. Berrange wrote:
Does anyone have any tip on how to actually run individual tests in an
efficient
On 07/03/2014 05:27 PM, Mark McLoughlin wrote:
Hey
This is an attempt to summarize a really useful discussion that Victor,
Flavio and I have been having today. At the bottom are some background
links - basically what I have open in my browser right now thinking
through all of this.
We're
On 07/07/2014 02:58 PM, Victor Stinner wrote:
Hi,
Le lundi 7 juillet 2014, 12:48:59 Nikola Đipanov a écrit :
When I read all of this stuff and got my head around it (took some time
:) ), a glaring drawback of such an approach, and as I mentioned on the
spec proposing it [1] is that we would
On 07/01/2014 03:40 PM, Sylvain Bauza wrote:
Hi,
I won't be able to attend the mid-cycle sprint due to a good family
reason (a new baby 2.0 release expected to land by these dates), so I'm
wondering if it's possible to webcast some of the sessions so people who
are not there can still share
On 06/14/2014 12:40 AM, Michael Still wrote:
Greetings,
I would like to nominate Ken'ichi Ohmichi for the nova-core team.
Ken'ichi has been involved with nova for a long time now. His reviews
on API changes are excellent, and he's been part of the team that has
driven the new API work
assistance.
Thanks,
Nikola Đipanov, SSE - OpenStack @ Red Hat
[1] http://openstack.redhat.com/Upgrading_RDO_To_Icehouse
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe
On 04/14/2014 08:58 AM, Chris Behrens wrote:
On Apr 13, 2014, at 9:58 PM, Michael Still mi...@stillhq.com wrote:
First off, thanks for electing me as the Nova PTL for Juno. I find the
First off, congrats!
Congrats Michael. And good luck!
* a mid cycle meetup. I think the Icehouse
On 04/10/2014 04:01 PM, Lingxian Kong wrote:
2014-04-10 15:06 GMT+08:00 sxmatch sxmatch1...@gmail.com
mailto:sxmatch1...@gmail.com:
hi guys:
I have registered a bp for this issue from Cinder side.
On 04/09/2014 03:54 AM, Lingxian Kong wrote:
yes, the bp also make sense to nova-cinder interaction, may I submmit
a blueprint about that?
Any comments?
I was going to propose that same thing for Nova as well, as well as a
summit session for Atlanta. Would be good to coordinate the
On 03/27/2014 03:52 AM, Wanghao (S) wrote:
Hi, all,
There is a use case: we have two nova components (call them nova A and
nova B) and one cinder component. Attach a volume to an instance in nova
A and then services of nova A become abnormal.
Because the volume also want to be used
On 03/05/2014 07:59 PM, Russell Bryant wrote:
On 03/05/2014 12:27 PM, Andrew Laski wrote:
On 03/05/14 at 07:37am, Tracy Jones wrote:
Hi - Please consider the image cache aging BP for FFE
(https://review.openstack.org/#/c/56416/)
This is the last of several patches (already merged) that
On 03/05/2014 08:00 PM, Russell Bryant wrote:
On 03/05/2014 10:34 AM, Gary Kotton wrote:
Hi,
Unfortunately we did not get the ISO support approved by the deadline.
If possible can we please get the FFE.
The feature is completed and has been tested extensively internally. The
feature is very
Hi folks,
This did not make it in fully. Outstanding patches are:
https://review.openstack.org/#/c/71064/
https://review.openstack.org/#/c/71065/
https://review.openstack.org/#/c/71067/
https://review.openstack.org/#/c/71067/
https://review.openstack.org/#/c/71479/
On 03/03/2014 06:32 PM, Russell Bryant wrote:
There has been quite a bit of discussion about the future of the v3 API
recently. There has been growing support for the idea that we should
change course and focus on evolving the existing v2 API instead of
putting out a new major revision. This
On 02/27/2014 11:22 AM, Thierry Carrez wrote:
Solly Ross wrote:
We (the websockify/noVNC team) have released a new version of websockify
(0.6.0). It contains several fixes and features relating to OpenStack (a
couple of bugs were fixed, and native support for the `logging` module was
On 12/18/2013 03:29 PM, Russell Bryant wrote:
Greetings,
The weekly Nova meeting [1] has been held on Thursdays at 2100 UTC.
I've been getting some requests to offer an alternative meeting time.
I'd like to try out alternating the meeting time between two different
times to allow more
On 12/18/2013 06:17 PM, Matt Riedemann wrote:
On 12/18/2013 9:42 AM, Matt Riedemann wrote:
The question came up in this patch [1], how do we deprecate and remove
keys in the notification payload? In this case I need to deprecate and
replace the 'instance_type' key with 'flavor' per the
On 11/19/2013 05:52 PM, Peter Feiner wrote:
On Tue, Nov 19, 2013 at 11:19 AM, Chuck Short chuck.sh...@canonical.com
wrote:
Hi
On Tue, Nov 19, 2013 at 10:43 AM, Peter Feiner pe...@gridcentric.ca wrote:
A substantive reason for switching from mox to mock is the derelict
state of mox
On 12/04/2013 06:15 PM, Peter Feiner wrote:
On Wed, Dec 4, 2013 at 11:16 AM, Nikola Đipanov ndipa...@redhat.com wrote:
1) Figure out what is the deal with mox3 and decide if owning it will
really be less trouble than porting nova. To be hones - I was unable to
even find the code repo
+1
On 26/11/13 20:32, Russell Bryant wrote:
Greetings,
I would like to propose that we re-add Dan Prince to the nova-core
review team.
Dan Prince has been involved with Nova since early in OpenStack's
history (Bexar timeframe). He was a member of the nova-core review team
from May 2011
On 13/11/13 18:49, Doug Hellmann wrote:
On Mon, Nov 11, 2013 at 6:08 PM, Mark McLoughlin mar...@redhat.com
mailto:mar...@redhat.com wrote:
Hi Nikola,
On Mon, 2013-11-11 at 12:44 +0100, Nikola Đipanov wrote:
Hey all,
During the summit session
Dear OpenStack devs,
A recent review [1] dragged into spotlight how damaging improper use of
external code inside migrations can be.
Basically in my mind the incident raises 2 issues that I think we should
look into:
1) How can we make reviewing changes with db migrations more robust
Since we
On 18/11/13 18:46, Nikola Đipanov wrote:
1) How can we make reviewing changes with db migrations more robust
Since we use sqlalchemy-migrate to version our database, the package's
documentation [2] states how care needs to be taken when importing code
inside a db migration script. It seems
Hey all,
During the summit session on the the VMWare driver roadmap, a topic of
validating the passed configuration prior to starting services came up
(see [1] for more detail on how it's connected to that specific topic).
Several ideas were thrown around during the session mostly documented in
their configuration. But maybe its so fast I don't care, but
I just felt I should raise that.
Thanks John,
This is a valid point that makes me think that there might be some
upgrade implications to such an approach that we might want to consider
also.
N.
John
On 11 November 2013 11:44, Nikola Đipanov
On 23/10/13 17:33, Russell Bryant wrote:
4) Blueprint Prioritization
I would like to do a better job of using priorities in Icehouse. The
priority field services a couple of purposes:
- helps reviewers prioritize their time
- helps set expectations for the submitter for how
On 08/10/13 01:01, Russell Bryant wrote:
On 10/07/2013 06:34 PM, Vishvananda Ishaya wrote:
There is a configuration option stating what to do with instances that are
still in the hypervisor but have been deleted from the database. I think you
want:
running_deleted_instance_action=reap
On 24/09/13 10:15, Gary Kotton wrote:
Hi,
Anyone know the root cause of:
2013-09-24 06:47:01.670 | Cleaning up...
2013-09-24 06:47:01.670 | No distributions matching the version for
pyparsing=2.0.1 (from cliff=1.4.3-python-neutronclient=2.3.0,3--r
On 09/09/13 11:25, Roman Podolyaka wrote:
Hi,
There is a patch on review (https://review.openstack.org/#/c/45422/)
fixing https://bugs.launchpad.net/tripleo/+bug/1221620 which has
importance 'Critical' in Nova and TripleO (long story short: currently
Nova Baremetal deployments with more
, TripleO-CI found this regression. Maybe we should consider
adding its job to Nova check/gate pipelines?
Thanks,
Roman
On Mon, Sep 9, 2013 at 1:59 PM, Nikola Đipanov ndipa...@redhat.com
mailto:ndipa...@redhat.com wrote:
On 09/09/13 11:25, Roman Podolyaka wrote:
Hi
only in special cases like this
(maybe, let's see :)), and not be something we do as a rule.
If we want to be serious about performance - we can't keep on doing this
- IMHO.
N.
Best regards,
Boris Pavlovic
On Mon, Sep 9, 2013 at 4:10 PM, Nikola Đipanov ndipa...@redhat.com
mailto:ndipa
On 06/09/13 11:28, Thierry Carrez wrote:
Wang, Shane wrote:
Hi core developers and everyone,
Please allow me to make an FFE request for adding utilization aware
scheduling support in Havana.
The blueprint:
https://blueprints.launchpad.net/nova/+spec/utilization-aware-scheduling.
[...]
On 06/09/13 14:12, Gary Kotton wrote:
Hi,
The following patch was approved but failed as it required a rebase
- https://review.openstack.org/#/c/41058/. Would it be possible that a
core reviewer takes a look.
Re-approved.
Cheers,
N.
Thanks in advance
Gary
On 18/07/13 11:34, Boris Pavlovic wrote:
Hi all,
I have some question about fixing old DB migrations.
If we are now in havana. And some broken migration was added in Havana.
Why we are not able to fix it directly?
Instead of chaining few lines, we should add new migration that do some
and shadow tables
are synces is required here.
As is probably clear from all above - I respectfully disagree on all
points except 2 for db migrations in the current state.
Thanks,
N.
Best regards,
Boris Pavlovic
On Fri, Jul 5, 2013 at 3:41 PM, Nikola Đipanov ndipa...@redhat.com
101 - 150 of 150 matches
Mail list logo
