On Thu, Aug 7, 2014 at 11:20 PM, Russell Bryant rbry...@redhat.com 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
It seems to me that the tension here is that there are groups who
would really like to use features in newer libvirts that we don't CI
on in the gate. Is it naive to think that a possible solution here is
to do the following:
- revert the libvirt version_cap flag
- instead implement a third
Maybe we should change how we wait?
I get that we don't want to sit around forever, but perhaps we should
specify a total maximum time to wait instead of a number of iterations
of a loop? Something like 15 minutes should be long enough for
anyone!. Eventlet sleeps are also pretty cheap, so having
On Wed, Aug 6, 2014 at 2:03 AM, Thierry Carrez thie...@openstack.org wrote:
We seem to be unable to address some key issues in the software we
produce, and part of it is due to strategic contributors (and core
reviewers) being overwhelmed just trying to stay afloat of what's
happening. For
On Thu, Aug 7, 2014 at 10:05 AM, Stefano Maffulli stef...@openstack.org wrote:
On Wed 06 Aug 2014 02:10:23 PM PDT, Michael Still wrote:
- we rate limit the total number of blueprints under code review at
any one time to a fixed number of slots. I secretly prefer the term
runway, so I am going
Jay has now been added to the nova-core group in gerrit.
Cheers,
Michael
On Thu, Jul 31, 2014 at 7:02 AM, Michael Still mi...@stillhq.com 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
On Thu, Jul 31, 2014 at 9:57 PM, Russell Bryant rbry...@redhat.com wrote:
Further, I'd like to propose that we treat all of existing +1 reviews as
+2 (once he's officially added to the team). Does anyone have a problem
with doing that? I think some folks would have done that anyway, but I
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 other types of core status I have
missed.
Please
the point of contention - which
I'ev done
Yes, I will sponsor this one as well. This is more a bug fix than a feature
IMO and would be really nice to get into Juno.
-Original Message-
From: Michael Still [mailto:mi...@stillhq.com]
Sent: 24 July 2014 00:50
To: Daniel P. Berrange
In that case this exception is approved. The exception is in the form
of another week to get the spec merged, so quick iterations are the
key.
Cheers,
Michael
On Wed, Jul 23, 2014 at 5:31 PM, Sylvain Bauza sba...@redhat.com wrote:
Le 23/07/2014 01:11, Michael Still a écrit :
This spec freeze
I think this sounds risky to me... I'd rather we landed _something_ in
terms of an ironic driver in juno, rather than adding features to what
we have now. In fact, I thought Devananda had frozen the ironic nova
driver to make this easier?
Michael
On Tue, Jul 22, 2014 at 4:45 PM, Faizan Barmawer
Fair enough. Let's roll with that then.
Michael
On Tue, Jul 22, 2014 at 6:33 AM, Sean Dague s...@dague.net wrote:
On 07/21/2014 03:35 PM, Dan Smith wrote:
We've already approved many other blueprints for Juno that involve features
from new libvirt, so I don't think it is credible to reject
Ok, this one has two cores, so the exception is approved. The
exception is in the form of another week to get the spec merged, so
quick iterations are the key.
Cheers,
Michael
On Tue, Jul 22, 2014 at 1:55 PM, Kenichi Oomichi
oomi...@mxs.nes.nec.co.jp wrote:
-Original Message-
From:
, Michael Still mi...@stillhq.com wrote:
Fair enough. Let's roll with that then.
Michael
On Tue, Jul 22, 2014 at 6:33 AM, Sean Dague s...@dague.net wrote:
On 07/21/2014 03:35 PM, Dan Smith wrote:
We've already approved many other blueprints for Juno that involve features
from new libvirt, so I
Ok, this one has two cores, so the exception is approved. The
exception is in the form of another week to get the spec merged, so
quick iterations are the key.
Cheers,
Michael
On Tue, Jul 22, 2014 at 2:02 AM, Kevin L. Mitchell
kevin.mitch...@rackspace.com wrote:
On Mon, 2014-07-21 at 10:55
This spec freeze exception only has one core signed up. Are there any
other cores interested in working with Sylvain on this one?
Michael
On Mon, Jul 21, 2014 at 7:59 PM, John Garbutt j...@johngarbutt.com wrote:
On 18 July 2014 09:10, Sylvain Bauza sba...@redhat.com wrote:
Hi team,
I would
I just want to check my understanding -- it seems to me that this
depends on a feature that's very new to libvirt (merged there 22 May
2014). Is that right?
http://libvirt.org/git/?p=libvirt.git;a=commit;h=d950494129513558a303387e26a2bab057012c5e
We've had some concerns about adding features to
cc'ed the
main protagonists into my email on this thread.
Michael
On Mon, Jul 21, 2014 at 10:55 AM, Mike Perez thin...@gmail.com wrote:
On 10:21 Mon 21 Jul , Michael Still wrote:
I just want to check my understanding -- it seems to me that this
depends on a feature that's very new to libvirt
At our weekly nova meeting just now I promised that I'd send an email
here explaining our intentions with the spec freeze for juno.
The proposed process works like this, but is subject to change:
- you request a spec freeze exception on the openstack-dev mailing
list. Please do this in the next
Those who have replied to this thread are now registered.
Michael
On Wed, Jul 16, 2014 at 6:56 AM, Michael Still mi...@stillhq.com wrote:
Hi.
We've now hit our room capacity, so I have closed registrations for
the nova mid cycle meetup. Please reply to this thread if that's a
significant
That time is around 1am for me. I'm ok with that as long as someone on
the nova side can attend in my place.
Michael
On Thu, Jul 17, 2014 at 12:22 PM, Kyle Mestery mest...@mestery.com wrote:
As we're getting down to the wire in Juno, I'd like to propose we have
a weekly meeting on the
Ok, I just released 2.18.1 to address this issue.
https://launchpad.net/python-novaclient/+milestone/2.18.1
Cheers,
Michael
On Sat, Jul 12, 2014 at 7:18 AM, Michael Still mi...@stillhq.com wrote:
I can do another release once https://review.openstack.org/#/c/106447/ merges.
Michael
On Sat
Hi.
We've now hit our room capacity, so I have closed registrations for
the nova mid cycle meetup. Please reply to this thread if that's a
significant problem for someone.
Thanks,
Michael
--
Rackspace Australia
___
OpenStack-dev mailing list
The containers meetup is in a different room with different space
constraints, so containers focussed people should do whatever Adrian
is doing for registration.
Michael
On Wed, Jul 16, 2014 at 12:53 PM, Eric Windisch ewindi...@docker.com wrote:
On Tue, Jul 15, 2014 at 6:42 PM, Rick Harris
I can't see a way to add the hudson user to that group, I'm hoping
fungi might have come advice there.
Michael
On Tue, Jul 15, 2014 at 6:55 AM, melanie witt melw...@outlook.com wrote:
Hi Nova Bug Wranglers,
There have been some issues where the gerrit hook script is unable to link a
review
Jeremy helped me with this on IRC, and the hudson bot is now a member
of that group.
Cheers,
Michael
On Tue, Jul 15, 2014 at 9:34 AM, Michael Still mi...@stillhq.com wrote:
I can't see a way to add the hudson user to that group, I'm hoping
fungi might have come advice there.
Michael
On Tue
, Michael Still wrote:
Sorry for the delay here. This email got lost in my inbox while I was
travelling.
This release is now tagged. Additionally, I have created a milestone
for this release in launchpad, which is the keystone process for
client releases. This means that users of launchpad can
You should probably add these details to the wiki page for the event
at https://wiki.openstack.org/wiki/Sprints/BeavertonJunoSprint
Unfortunately my travel is booked already, so I wont be there for the Thursday.
Michael
On Sat, Jul 12, 2014 at 8:31 AM, Adrian Otto adrian.o...@rackspace.com
Sorry for the delay here. This email got lost in my inbox while I was
travelling.
This release is now tagged. Additionally, I have created a milestone
for this release in launchpad, which is the keystone process for
client releases. This means that users of launchpad can now see what
release a
, Michael Still wrote:
On Wed, Jul 9, 2014 at 8:21 AM, Sean Dague s...@dague.net wrote:
This is also why I find it unlikely to be a qemu bug, because that's not
shared state between guests. If qemu just randomly wedges itself, that
would be detectable much easier outside of the gate
The associated bug says this is probably a qemu bug, so I think we
should rephrase that to we need to start thinking about how to make
sure upstream changes don't break nova.
Michael
On Wed, Jul 9, 2014 at 7:50 AM, Joe Gordon joe.gord...@gmail.com wrote:
On Thu, Jun 26, 2014 at 4:12 AM, Daniel
On Wed, Jul 9, 2014 at 8:21 AM, Sean Dague s...@dague.net wrote:
This is also why I find it unlikely to be a qemu bug, because that's not
shared state between guests. If qemu just randomly wedges itself, that
would be detectable much easier outside of the gate. And there have been
attempts by
I think you'd be better of requesting an exception for your spec than
splitting the scheduler immediately. These refactorings need to happen
anyways, and if your scheduler work diverges too far from nova then
we're going to have a painful time getting things back in sync later.
Michael
On Mon,
Joe has a good answer, but you should also be aware of the hypervisor
support matrix (https://wiki.openstack.org/wiki/HypervisorSupportMatrix),
which hopefully comes some way to explaining what we expect of a nova
driver.
Cheers,
Michael
On Tue, Jul 8, 2014 at 9:11 AM, Joe Gordon
Adrian, is there any news on this? I want to start booking my ops
meetup travel, but I don't know if I should include this meetup or
not.
Thanks,
Michael
On Wed, Jul 2, 2014 at 8:12 AM, Russell Bryant rbry...@redhat.com wrote:
On 07/01/2014 05:59 PM, Adrian Otto wrote:
Team,
Please help us
On Thu, Jul 3, 2014 at 4:33 AM, Luke Gorrie l...@snabb.co wrote:
On 30 June 2014 21:04, Kevin Benton blak...@gmail.com wrote:
As a maintainer of a small CI system that tends to get backed up during
milestone rush hours, it would be nice if we were allowed up to 12 hours.
However, as a
We were talking about doing something with google+ for Chris Yeoh, but
haven't really progressed the plan. Does someone want to pick up the
ball with that or shall I?
Michael
On Tue, Jul 1, 2014 at 11:50 PM, Dugger, Donald D
donald.d.dug...@intel.com wrote:
At minimum I can arrange for a phone
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?
Thanks,
Michael
--
Rackspace Australia
___
This sounds like something which should be reported as a bug. You do
that at https://bugs.launchpad.net/nova/+filebug
Cheers,
Michael
On Thu, Jun 26, 2014 at 1:43 AM, Agrawal, Ankit
ankit11.agra...@nttdata.com wrote:
Hi All,
When I boot an instance from volume and the take snapshot of that
- but I don't see the harm in letting specs be submitted to
the K directory for early review / feedback during that period ?
Phil
-Original Message-
From: Michael Still [mailto:mi...@stillhq.com]
Sent: 24 June 2014 09:59
To: OpenStack Development Mailing List
Subject: [openstack-dev
, Michael Still wrote:
Phil -- I really want people to focus their efforts on fixing bugs in
that period was the main thing. The theory was if we encouraged people
to work on specs for the next release, then they'd be distracted from
fixing the bugs we need fixed in J.
Cheers,
Michael
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.
Cheers,
Michael
On Fri, Jun 20, 2014 at 5:06 AM, melanie witt melw...@outlook.com wrote:
On Jun 17, 2014, at 13:34,
Kenichi has now been added to the nova-core group in gerrit. Welcome aboard!
Michael
On Tue, Jun 17, 2014 at 6:18 PM, Michael Still mi...@stillhq.com wrote:
Hi. I'm going to let this sit for another 24 hours, and then we'll
declare it closed.
Cheers,
Michael
On Tue, Jun 17, 2014 at 6:16
Hi. I'm going to let this sit for another 24 hours, and then we'll
declare it closed.
Cheers,
Michael
On Tue, Jun 17, 2014 at 6:16 AM, Mark McLoughlin mar...@redhat.com wrote:
On Sat, 2014-06-14 at 08:40 +1000, Michael Still wrote:
Greetings,
I would like to nominate Ken'ichi Ohmichi
On Wed, Jun 18, 2014 at 10:21 AM, Ahmed RAHAL ara...@iweb.com wrote:
Le 2014-06-16 15:28, melanie witt a écrit :
The more I think about it, the more I get to think that locking is just
there to avoid mistakes, not voluntary misbehaviour.
I agree. You have a really important instance, so you
On Tue, Jun 17, 2014 at 5:28 AM, melanie witt melw...@outlook.com wrote:
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
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 we've seen in recent cycles forward. Ken'ichi
has also
On Fri, Jun 13, 2014 at 1:00 PM, Christopher Yeoh cbky...@gmail.com wrote:
On Fri, Jun 13, 2014 at 11:28 AM, Matt Riedemann
mrie...@linux.vnet.ibm.com wrote:
On 6/12/2014 5:58 PM, Christopher Yeoh wrote:
On Fri, Jun 13, 2014 at 8:06 AM, Michael Still mi...@stillhq.com
mailto:mi...@stillhq.com
In light of the recent excitement around quota classes and the
floating ip pollster, I think we should have a conversation about the
review guidelines we'd like to see for API changes proposed against
nova. My initial proposal is:
- API changes should have an associated spec
- API changes
Sorry, didn't notice the list changed.
On Fri, Jun 13, 2014 at 8:40 AM, Michael Still mi...@stillhq.com wrote:
On Thu, Jun 12, 2014 at 10:05 PM, Tom Cammann tom.camm...@hp.com wrote:
Hello,
I'm addressing https://bugs.launchpad.net/oslo/+bug/1326020 which is
dealing with periodic tasks
I'll add this bug (and thread) to the agenda for the nova meeting tomorrow.
Michael
On Wed, Jun 11, 2014 at 7:43 AM, Kyle Mestery mest...@noironetworks.com wrote:
I wanted to update people on this bug [1], which until the weekend was
affecting the gate. After spending a week and a half
https://review.openstack.org/99002 adds more logging to
nova/network/manager.py, but I think you're not going to love the
debug log level. Was this the sort of thing you were looking for
though?
Michael
On Mon, Jun 9, 2014 at 11:45 PM, Sean Dague s...@dague.net wrote:
Based on some back of
Hi.
This is a reminder that we will have a meeting today at 21:00 UTC. The agenda is
at https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
Cheers,
Michael
--
Rackspace Australia
___
OpenStack-dev mailing list
Thierry, you couldn't find the nova midcycle meetup because the final
details haven't been announced yet. I hope to fix that tomorrow.
Cheers,
Michael
On Thu, Jun 5, 2014 at 7:48 PM, Thierry Carrez thie...@openstack.org wrote:
Hey everyone,
With all those mid-cycle sprints being proposed I
Hi!
Nova will hold its Juno mid cycle meetup between July 28 and 30, at an
Intel campus in Beaverton, OR (near Portland). There is a wiki page
with more details here:
https://wiki.openstack.org/wiki/Sprints/BeavertonJunoSprint
I'll update that wiki page as we nail down more details. There's
Thanks for chasing the specs / blueprints process John -- its much appreciated.
Michael
On Sat, May 31, 2014 at 3:41 AM, John Garbutt j...@johngarbutt.com wrote:
Hi,
Juno-1 release date is now less than two weeks away:
https://wiki.openstack.org/wiki/Juno_Release_Schedule
In this weeks
Hi.
I've been looking at the current state of the vmware driver spawn
refactor work, and as best as I can tell phase one is now complete.
However, I can only find one phase two patch, and it is based on an
outdated commit. That patch is:
https://review.openstack.org/#/c/87002/
There also
Heya!
This is just a gentle reminder that there will be a nova meeting on
Thursday at 21:00 UTC.
The agenda is at
https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
-- feel free to add things I've missed. As a new value add, if you add
your IRC nick to the list on that page
On Mon, May 19, 2014 at 10:35 PM, Joe Gordon joe.gord...@gmail.com wrote:
On Wed, May 14, 2014 at 6:58 AM, Matt Riedemann mrie...@linux.vnet.ibm.com
wrote:
I'd like to get some more discussion going for the nova-spec on adding DB2
support [1] especially since we didn't get to the topic for
Hi, so we should have a meeting today week at 21:00 UTC. The agenda is
at https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
Cheers,
Michael
--
Rackspace Australia
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
The way to go is probably to put them into the etherpad for that
session, which is at
https://etherpad.openstack.org/p/juno-nova-vmware-driver-roadmap
Cheers,
Michael
On Mon, May 5, 2014 at 11:32 PM, Sheng Bo Hou sb...@cn.ibm.com wrote:
Hi VMware folks,
How can I put my proposals for VMware
Additionally, if there are any blueprints / specs related to your
session please include them in a list at the start of the etherpad.
That will help people to have read up on the specs before the session.
Thanks for creating these etherpads Daniel!
Michael
On Sat, May 3, 2014 at 2:43 AM, Daniel
This is now done. Sorry for the delay.
Michael
On Mon, Apr 28, 2014 at 12:13 PM, Ken'ichi Ohmichi
ken1ohmi...@gmail.com wrote:
2014-04-28 11:00 GMT+09:00 Michael Still mi...@stillhq.com:
On Mon, Apr 28, 2014 at 11:24 AM, Kenichi Oomichi
oomi...@mxs.nes.nec.co.jp wrote:
Hi Michael,
Thanks
Fixed. I've swapped the image precaching and live upgrade sessions.
Hopefully this hasn't caused problems for any image precaching
peoples.
Michael
On Mon, Apr 28, 2014 at 4:00 PM, Tom Fifield t...@openstack.org wrote:
On 28/04/14 05:02, Michael Still wrote:
Hi.
I've just pushed a draft
Hi.
I was intending to run a nova meeting this week, but I don't think its
worth a mutiny over the off week that the rest of the project is
respecting. The only agenda items I can think of are:
- please prepare your summit sessions
- I've attempted to fix the clashes in scheduling that are
Yeah, I feel bad that we haven't had one in three weeks now -- its
definitely a thing I am not happy with. Next week for sure.
Michael
On Fri, May 2, 2014 at 12:15 AM, Matt Riedemann
mrie...@linux.vnet.ibm.com wrote:
On 5/1/2014 1:58 AM, Michael Still wrote:
Hi.
I was intending to run
Yes, exactly. Don't write a presentation, come with a plan in bullet
points in an etherpad, and be prepared to have an active discussion
about how that plan might change...
If you'd like I am sure people here would be happy to pre-review an
etherpad to make sure you're on the right track.
Hi.
I've just pushed a draft summit schedule to sched.org. I'd be
interested in people who proposed a session that was accepted checking
if their session time clashes with other commitments that they have,
as well as people who are passionate about a given proposal ensuring
that they're available
On Mon, Apr 28, 2014 at 11:24 AM, Kenichi Oomichi
oomi...@mxs.nes.nec.co.jp wrote:
Hi Michael,
Thanks for the schedule draft.
I'd like to pick one comment about it.
Now sessions related to Nova v3 API are scheduled like:
- 5:20pm May 14: Nova V3 API
- 5:00pm May 15: Nova V2 on V3 API
Hi.
Given no one has volunteered to run the meeting and I can't make it
because of travel, let's skip this weeks meeting. We'll have one next
week for sure!
Michael
--
Rackspace Australia
___
OpenStack-dev mailing list
, 2014 at 2:05 AM, Michael Still mi...@stillhq.com wrote:
Hi.
Given no one has volunteered to run the meeting and I can't make it
because of travel, let's skip this weeks meeting. We'll have one next
week for sure!
Michael
--
Rackspace Australia
Hi.
I just want to be honest here and set expectations. The entire nova
track has 27 slots this summit. We need to cover all of the drivers,
the transition from nova-network to neutron, the v3 API, and a bunch
of other stuff. I can't see a quarter of our slots being used for
scheduler topics. At
On Thu, Apr 24, 2014 at 4:47 AM, Randy Bias ran...@cloudscaling.com wrote:
... I’d like to recommend we move
them into Stackforge as we did with the GCE APIs. That way these can become
optional components installed by those who want to use them. The other
advantage is that they can be
On Thu, Apr 24, 2014 at 7:39 AM, Joe Gordon joe.gord...@gmail.com wrote:
So no one is seriously discussing moving EC2 out of nova right now. The
issue is that the EC2 code and tempest tests aren't being maintained are
slowly code rotting. The goal of this thread is to get some volunteers to
On Wed, Apr 23, 2014 at 11:34 PM, Russell Bryant rbry...@redhat.com wrote:
John originally mentioned this on the review, but Phil and I both seem
to agree.
Most novaclient work can just be a work item of a nova blueprint. How
about we just handle it that way?
For those cases where that's
My biggest concern with your proof of concept is that it would require
all outstanding blueprints to do a rebase, which sounds painful. Could
we perhaps create a subdirectory for novaclient, and keep the nova
stuff at the top level until most things have landed?
Michael
On Wed, Apr 23, 2014 at
If you'd like to have a go at implementing this in nova's Juno
release, then you need to create a new-style blueprint in the
nova-specs repository. You can find more details about that process at
https://wiki.openstack.org/wiki/Blueprints#Nova
Some initial thoughts though, some of which have
It looks to me like this was removed in oslo in commit
a33989e7a2737af757648099cc1af6c642b6e016, which was synced with nova
in 605749ca12af969ac122008b4fa14904df68caf7 (however, I can't see the
change being listed in the commit message for nova, which I assume is
a process failure). That change
Hi.
I'd also like to announce my TC candidacy. I am currently a member of
the TC, and I would like to continue to serve.
I first started hacking on Nova during the Diablo release, with my
first code contributions appearing in the Essex release. Since then
I've hacked mostly on Nova and Oslo,
On Mon, Apr 14, 2014 at 7:06 PM, Stefano Maffulli stef...@openstack.org wrote:
On 04/14/2014 06:58 AM, Michael Still wrote:
First off, thanks for electing me as the Nova PTL for Juno.
Congratulations Michael.
* I promised to look at mentoring newcomers. The first step there is
working out
Hi.
Easter is this coming weekend for many countries, so many people are
going to be away or at least winding down for the long weekend.
Let's skip the nova meeting this week and let people have a bit of a break.
Thanks,
Michael
--
Rackspace Australia
On Wed, Apr 16, 2014 at 7:31 AM, Russell Bryant rbry...@redhat.com wrote:
On 04/15/2014 05:14 PM, Kyle Mestery wrote:
2. Nova has a subset of the core-team which can actually approve BPs,
is this correct?
Correct. The team is nova-drivers [1]. This is the team that assisted
me with the
On Wed, Apr 16, 2014 at 7:57 AM, Hugh O. Brock hbr...@redhat.com wrote:
On Wed, Apr 16, 2014 at 09:30:45AM +1200, Robert Collins wrote:
Redhat offered to host the next TripleO midcycle meetup in Raleigh, I
don't know if they have space for Nova TripleO at once, but I'd love
to get more
On Wed, Apr 16, 2014 at 10:01 AM, Robert Collins
robe...@robertcollins.net wrote:
On 16 April 2014 11:28, Michael Still mi...@stillhq.com wrote:
On Wed, Apr 16, 2014 at 7:57 AM, Hugh O. Brock hbr...@redhat.com wrote:
On Wed, Apr 16, 2014 at 09:30:45AM +1200, Robert Collins wrote:
Redhat
On Mon, Apr 14, 2014 at 4:58 PM, Chris Behrens cbehr...@codestud.com 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!
Thanks!
* a mid cycle meetup. I think the Icehouse
On Mon, Apr 14, 2014 at 2:58 PM, Michael Still mi...@stillhq.com wrote:
Thanks for taking the time to read this email, and please do let me
know if you think this sort of communication is useful.
Hi. I just want to thank the ten or so people who've privately replied
to this email
First off, thanks for electing me as the Nova PTL for Juno. I find the
outcome of the election both flattering and daunting. I'd like to
thank Dan and John for running as PTL candidates as well -- I strongly
believe that a solid democratic process is part of what makes
OpenStack so successful, and
On Sat, Apr 12, 2014 at 7:37 AM, Russell Bryant rbry...@redhat.com wrote:
On 04/11/2014 04:58 PM, Sean Dague wrote:
[snip]
If we think it's staying in 3rd party, people are free to use
whatever they would like.
I guess we should be clear on this point.
I *really* think the best way
It might be that this is happening because there is no clear incumbent
for the Nova PTL position. Is it ok to hold off on this until after
the outcome of the election is known?
Michael
On Mon, Apr 7, 2014 at 2:23 PM, Tom Fifield t...@openstack.org wrote:
So far, there's been no comment from
Hi.
I would like to run for the OpenStack Compute PTL position as well.
I have been an active nova developer since late 2011, and have been a
core reviewer for quite a while. I am currently serving on the
Technical Committee, where I have recently been spending my time
liaising with the board
Hi.
So I've written a blueprint for nova for Juno, and uploaded it to
nova-specs (https://review.openstack.org/#/c/80865/). That got me
thinking about what this process might look like, and this is what I
came up with:
* create a launchpad blueprint
* you write a proposal in the nova-specs repo
On Mon, Mar 17, 2014 at 3:00 PM, Chris Behrens cbehr...@codestud.com wrote:
On Mar 16, 2014, at 7:58 PM, Michael Still mi...@stillhq.com wrote:
Hi.
So I've written a blueprint for nova for Juno, and uploaded it to
nova-specs (https://review.openstack.org/#/c/80865/). That got me
thinking
On Mon, Mar 17, 2014 at 3:21 PM, Christopher Yeoh cbky...@gmail.com wrote:
To accommodate those who happen to find the blueprint first, I think we
need a link from the blueprint to the nova-specs review or when its
approved into the nova-specs repository. I kind of expected the link
from the
Wasn't the conclusion last time that it would be best to add bhyve support
to libvirt?
Michael
On 10/03/2014 6:09 PM, Robert Norton rnor...@gmail.com wrote:
I'm curious to see if any progress has been made on supporting FreeBSD
and/or the bhyve hypervisor? I haven't seen any updates on this on
I see many examples in nova of where we still read rows with
read_deleted=yes. I think we need to see a plan for how to remove
all of those before we can progress this.
Michael
On Tue, Mar 11, 2014 at 9:06 AM, Johannes Erdfelt johan...@erdfelt.com wrote:
On Mon, Mar 10, 2014, Joshua Harlow
On Thu, Mar 6, 2014 at 12:26 PM, Tian, Shuangtai
shuangtai.t...@intel.com wrote:
Hi，
I would like to make a request for FFE for one patch in novaclient for PCI
V3 API : https://review.openstack.org/#/c/75324/
[snip]
BTW the PCI Patches in V2 will defer to Juno.
I'm confused. If this isn't
Hi.
You might have noticed that the nova gate is currently broken. I
believe this is related to an oslo.messaging release today, and have
proposed a fix at https://review.openstack.org/#/c/77844/
Cheers,
Michael
--
Rackspace Australia
___
On Wed, Mar 5, 2014 at 11:09 AM, Dan Smith d...@danplanet.com wrote:
What I'd like to do next is work through a new proposal that includes
keeping both v2 and v3, but with a new added focus of minimizing the
cost. This should include a path away from the dual code bases and to
something like
I think its also pretty unfair on the people who put a lot of work
into the v3 API. We're seriously going to delete their code after they
put a year into it?
To me OpenStack isn't just the users, its also the development
community. I think we do measurable harm to that development community
by
On Tue, Mar 4, 2014 at 4:32 AM, Russell Bryant rbry...@redhat.com 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
301 - 400 of 467 matches
Mail list logo
