On Wed, Nov 13, 2013 at 8:39 AM, Mark McLoughlin wrote:
> I think it goes without saying that it makes sense to fix this.
> Personally, I'm annoyed I didn't notice this before now.
Agreed. Thanks for fixing this Anita.
Michael
--
Rackspace Australia
__
On Thu, Nov 14, 2013 at 8:20 AM, Eric Windisch wrote:
> I don't think it is a problem to remove the code in oslo first, as
> long as no other oslo-incubator code uses it. Projects don't have to
> sync the code and could always revert should that they do.
I strongly disagree. It stops projects fr
On Thu, Nov 14, 2013 at 5:18 AM, Mike Spreitzer wrote:
> This is a follow-up to the design summit discussion about DB migrations.
> There was concern about the undo-ability of some migrations. The specific
> example cited was removal of a column. Could that be done with the
> following three mig
On Thu, Nov 14, 2013 at 3:49 PM, Sankarshan Mukhopadhyay
wrote:
> On Thu, Nov 14, 2013 at 10:02 AM, Lana Brindley
> wrote:
>> It looks as though it was decided that no code changes were required, but a
>> doc update was. However, I'm struggling to work out what the user impact is
>> here. On the
+1
On Wed, Jul 3, 2013 at 12:02 PM, Ken'ichi Ohmichi
wrote:
>
> +1
>
> On Tue, 02 Jul 2013 18:40:31 -0400
> Russell Bryant wrote:
>>
>> Greetings,
>>
>> I would like to propose Christopher Yoeh to be added to the nova-core team.
>>
>> Christopher has been prolific in his contributions to nova la
I've been working on testing database migrations against real data
sets for the last few weeks. I haven't had a chance to document it
very well yet though -- there's a blog post being drafted at the
moment.
If you go to http://openstack.stillhq.com/ci you can see the results
of tests run against t
On Wed, Jul 3, 2013 at 3:50 AM, Boris Pavlovic wrote:
> Question:
> Why we should put in oslo slqlalchemy-migrate monkey patches, when we are
> planing to switch to alembic?
>
> Answer:
>If we don’t put in oslo sqlalchemy-migrate monkey patches. We won't be
> able to work on 7 point at all
On Tue, Jul 9, 2013 at 8:11 PM, Mark McLoughlin wrote:
> Hey
>
> The mission statement is what we've been using for a while. The
> "official title" is new.
>
> Official Title: OpenStack Common Libraries
> PTL: Mark McLoughlin
> Mission Statement:
> To produce a set of python libraries c
OpenStack has a system called notifications which does what you're
looking for. I've never used it, but I am sure its documented.
Cheers,
Michael
On Sat, Jul 13, 2013 at 10:12 AM, Qing He wrote:
> All,
>
> Does open stack have pub/sub event service? I would like to be notified of
> the event of
I'm happy to help, although I'm pretty busy...
Michael
On Fri, Jul 12, 2013 at 9:37 PM, Boris Pavlovic wrote:
> Hi Sean,
>
> I agree to help with sqlalchemy-migrate until we remove it.
> But probably there should be one more person mikal
>
> Best regards,
> Boris Pavlovic
>
>
> On Fri, Jul 12, 2
On Tue, Jul 16, 2013 at 1:44 PM, Thomas Goirand wrote:
> In Debian, by policy, any package should be able to be installed using
> DEBIAN_FRONTEND=noninteractive apt-get install. What I do in my postinst
> is calling db_sync, because that isn't something our users should even
> care about, since i
On Tue, Jul 16, 2013 at 4:05 PM, Thomas Goirand wrote:
> On 07/16/2013 12:07 PM, Michael Still wrote:
>> On Tue, Jul 16, 2013 at 1:44 PM, Thomas Goirand wrote:
>>
>>> In Debian, by policy, any package should be able to be installed using
>>> DEBIAN_FRONTEND=nonin
On Tue, Jul 16, 2013 at 4:17 PM, Thomas Goirand wrote:
> Could you explain a bit more what could be done to fix it in an easy
> way, even if it's not efficient? I understand that ALTER doesn't work
> well. Though would we have the possibility to just create a new
> temporary table with the correc
On Tue, Jul 23, 2013 at 5:19 AM, Atwood, Mark wrote:
> Hi!
>
> While I was at the Community Leadership Summit conference this weekend, I met
> the community manager for the Xen hypervisor project. He told me that there
> are *no* OpenStack talks submitted to the upcoming XenCon conference.
>
>
I agree with this, but perhaps we should discuss with
openstack-operators@ as well?
Michael
On Fri, Jul 26, 2013 at 6:33 AM, Davanum Srinivas wrote:
> +1 to turn it off
>
> -- dims
>
> On Thu, Jul 25, 2013 at 12:07 PM, Day, Phil wrote:
>> +1 to turning it off. Having something that doesn’t rea
On Fri, Jul 26, 2013 at 8:30 AM, Russell Bryant wrote:
> If an external proxy (like AWSOME) is what you want, one of those
> already exists (at least for the EC2 API).
>
> http://deltacloud.apache.org/
>
> It supports EC2 on the frontend and the OpenStack compute API on the
> backend. I'm not su
On Fri, Jul 26, 2013 at 7:43 AM, Thierry Carrez wrote:
> I would rather support solution 3: create a single, separate executable
> that does those 20 things that need to be done (can be a shell script
> with some logic in it), and have rootwrap call that *once*. That way you
> increase speed by
+1
On Thu, Aug 1, 2013 at 11:52 PM, Andrew Laski
wrote:
> +1
>
>
> On 07/31/13 at 03:10pm, Russell Bryant wrote:
>>
>> Greetings,
>>
>> I propose that we add Nikola Đipanov to the nova-core team [1].
>>
>> Nikola has been actively contributing to nova for a while now, both in
>> code and reviews.
Hi.
I have increasing levels of concern about Havana database migrations
and I want to beg for help, especially from nova core reviewers.
Specifically, I don't think its possible to land all of the database
migrations people need before the 22 August proposal freeze. At the
moment I see 10 patche
On Sat, Aug 24, 2013 at 4:20 AM, Elizabeth Krumbach Joseph
wrote:
> Hi everyone,
>
> Several months ago the OpenStack Infrastructure team filed a bug to
> "Create a git.openstack.org mirror system"[0]
Does git.openstack.org replace git hub for developers cloning
repositories? Or is it just a mirr
[Concerns over review wait times in the nova project]
I think that we're also seeing the fact that nova-core's are also
developers. nova-core members have the same feature freeze deadline,
and that means that to a certain extent we need to stop reviewing in
order to get our own code ready by the d
On Wed, Aug 28, 2013 at 4:18 AM, Sam Alba wrote:
> Hi all,
>
> We've been working hard during the last couple of weeks with some
> people. Brian Waldon helped a lot designing the Glance integration and
> driver testing. Dean Troyer helped a lot on bringing Docker support in
> Devstack[1]. On top o
On Wed, Sep 4, 2013 at 1:54 AM, Vishvananda Ishaya
wrote:
>
> +1 I think we should be reconstructing data where we can, but keeping track of
> deleted data in a backup table so that we can restore it on a downgrade seems
> like overkill.
I guess it comes down to use case... Do we honestly expect
Hi. This code has been in review since July 29, but a combination of
my focus on code reviews for others and having a baby has resulted in
it not landing. This feature is important to libvirt and closes a
critical bug we've had open way too long. The reviews:
https://review.openstack.org/#/c/39048
Hi,
It has been decided that the Nova Mitaka mid-cycle would be in Bristol, UK
between 26 and 28 January. You can register at:
https://www.eventbrite.com.au/e/openstack-mitaka-nova-mid-cycle-meetup-tickets-19326224257
Details of hotel discounts etc will be added to this thread when they are
kno
I'd be interested in being involved with this, and I know Paul Murray is
interested as well.
I went to make a doodle, but then realised the only non-terrible timeslot
for Australia / UK / US Central is 8pm UTC (7am Australia, 8pm London, 2pm
Central US). So what do people think of that time slot?
+1
Alex does good work.
Michael
On Sat, Nov 7, 2015 at 2:32 AM, 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
+1... Sylvain is an excellent reviewer.
On Sat, Nov 7, 2015 at 2:32 AM, 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.
>
> P
So, its been a week. What time are we picking?
Michael
On Thu, Nov 5, 2015 at 10:46 PM, Murray, Paul (HP Cloud)
wrote:
> > > Most team members expressed they would like a regular IRC meeting for
> > > tracking work and raising blocking issues. Looking at the contributors
> > > here [2], most of
Hey,
I filled in the first part of that page, but when it got to hotels I got
confused. The web site doesn't seem to mention the night rate for the HP
price. Do you know what that is?
Thanks,
Michael
On Sat, Nov 28, 2015 at 3:06 AM, Murray, Paul (HP Cloud)
wrote:
> The Nova Mitaka mid cycle me
On Tue, May 24, 2016 at 11:42 PM, Muneeb Ahmad
wrote:
> If not, can I add it's support? any ideas how can I do that?
>
> On Sat, May 21, 2016 at 10:23 PM, Muneeb Ahmad
> wrote:
>
>> Hey guys,
>>
>> Does OpenStack support Xvisor?
>>
>
So, given I'd never heard of xvisor I think we can say that no
Hi,
I've spent some time today abandoning old reviews from the Nova queue.
Specifically, anything which hadn't been updated before February this year
has been abandoned with a message like this:
"This patch has been idle for a long time, so I am abandoning it to keep
the review clean sane. If you
I've always done it manually by eyeballing the review, but the script is
tempting.
Thanks,
Michael
On 27 May 2016 8:42 PM, "Sean Dague" wrote:
> On 05/27/2016 05:36 AM, Michael Still wrote:
> > Hi,
> >
> > I've spent some time today abandoning old revi
On Tue, Jun 7, 2016 at 7:41 AM, Clif Houck wrote:
> Hello all,
>
> At Rackspace we're running into an interesting problem: Consider a user
> who boots an instance in Nova with an image which only supports SSH
> public-key authentication, but the user doesn't provide a public key in
> the boot req
+Angus
On Thu, Jun 9, 2016 at 7:10 AM, Matt Riedemann
wrote:
> While sitting in Angus' cross-project session on oslo.privsep at the
> Austin summit I believe I had a conversation with myself in my head that
> Nova should stop adding new rootwrap filters and anything new should use
> oslo.privsep
On Fri, Jun 10, 2016 at 7:18 AM, Tony Breeds
wrote:
> On Wed, Jun 08, 2016 at 08:10:47PM -0500, Matt Riedemann wrote:
>
> > Agreed, but it's the worked example part that we don't have yet,
> > chicken/egg. So we can drop the hammer on all new things until someone
> does
> > it, which sucks, or ho
So, https://review.openstack.org/#/c/317739 is basically done I think. I'm
after people's thoughts on:
- I need to do some more things, as described in the commit message. Are
we ok with them being in later patches to get reviews moving on this?
- I'm unsure what level of tempest testing makes
On Wed, Jun 22, 2016 at 11:13 PM, Sean Dague wrote:
> On 06/22/2016 09:03 AM, Matt Riedemann wrote:
> > On 6/21/2016 12:53 AM, Michael Still wrote:
> >> So, https://review.openstack.org/#/c/317739 is basically done I think.
> >> I'm after people's thoughts on
As a recent newcomer to using our client libraries, my only real objection
to this plan is that our client libraries as a mess [1][2]. The interfaces
we expect users to use are quite different for basic things like initial
auth between the various clients, and by introducing another library we
insi
On Wed, Apr 6, 2016 at 7:28 AM, Ian Cordasco wrote:
>
>
> -Original Message-
> From: Michael Still
> Reply: OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> Date: April 5, 2016 at 16:11:05
> To: OpenStack
On Tue, Apr 12, 2016 at 6:49 AM, Matt Riedemann
wrote:
> A few people have been asking about planning for the nova midcycle for
> newton. Looking at the schedule [1] I'm thinking weeks R-15 or R-11 work
> the best. R-14 is close to the US July 4th holiday, R-13 is during the week
> of the US July
On 12 Apr 2016 12:19 AM, "Sean Dague" wrote:
>
> On 04/11/2016 10:08 AM, Ed Leafe wrote:
> > On 04/11/2016 08:38 AM, Julien Danjou wrote:
> >
> >> There's a lot of assumption in oslo.log about Nova, such as talking
> >> about "instance" and "context" in a lot of the code by default. There's
> >> e
either at
San Antonio, Texas or Hillsboro, Oregon during R-15 (June 20-24) or R-11
(July 18-22) as preferred by the Nova community.
Regards
Malini
Forwarded Message
Subject:Re: [openstack-dev] [nova] Newton midcycle planning
Date: Tue, 12 Apr 2016 08:54:17 +1000
From:
On Sun, May 1, 2016 at 10:27 PM, ZhiQiang Fan wrote:
> Hi Nova cores,
>
> There is a spec[1] submitted to Telemetry project for Newton release,
> mentioned that a new feature requires libvirt >= 1.3.4 , I'm not sure if
> this will have bad impact to Nova service, so I open this thread and wait
>
The instance of stackalytics run by the openstack-infra team seems to be
gummed up. It alleges that the last time there was a nova code review was
April 17, which seems... unlikely.
Who looks after this thing so I can ping them gently?
Thanks,
Michael
--
Rackspace Australia
On Wed, May 4, 2016 at 11:03 AM, Davanum Srinivas wrote:
> Michael,
>
> The stackalytics bots do not have access to gerrit at the moment. We
> noticed it last friday and talked to infra folks:
>
> http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2016-04-29.log.html#t20
I can't think of a reason. In fact its a bit warty because we've changed
the way we name the instance directories at least once. Its just how this
code was written back in the day.
Cleaning this up would be a fair bit of work though. Is it really worth the
effort just so people can have different
On Fri, May 6, 2016 at 12:50 AM, Matthew Booth wrote:
> I mentioned in the meeting last Tuesday that there are now 2 of us working
> on the persistent storage metadata patches: myself and Diana Clarke. I've
> also been talking to Paul Carlton today trying to work out how he can get
> moving with
On Tue, May 10, 2016 at 2:12 AM, Markus Zoeller wrote:
> We're close to have all options moved to "nova/conf/". At the bottom
> is a list of the remaining options and their open reviews.
>
> The documentation of the options in "nova/conf/" is done for ~ 150
> options. Which means ~ 450 are missin
I think Tony would be a valuable addition to the team.
+1
Michael
On 14 Jan 2016 7:59 AM, "Matt Riedemann" wrote:
> I'm formally proposing that the nova-stable-maint team [1] adds Tony
> Breeds to the core team.
>
> I don't have a way to track review status on stable branches, but there
> are r
We can give him elocution classes at the mid-cycle. It's like my fair lady,
but nerdier.
Michael
On 16 Jan 2016 4:11 AM, "Dan Smith" wrote:
> > I'm formally proposing that the nova-stable-maint team [1] adds Tony
> > Breeds to the core team.
>
> My major complaint with Tony is that he talks funn
I have just approved that review, as it moves the ball in the right
direction.
Michael
On Sat, Jan 16, 2016 at 3:04 PM, Davanum Srinivas wrote:
> Haha, needs work :)
>
> -- Dims
>
> On Fri, Jan 15, 2016 at 10:53 PM, Thomas Goirand wrote:
> > On 01/16/2016 08:35 AM, Davanum Srinivas wrote:
> >>
Heya,
I am not aware of anyone working on this. That said, its also not clear to
me that this is actually a good idea. Why can't you just loop through the
instances and delete them one at a time?
Michael
On Wed, Jan 20, 2016 at 12:08 AM, vishal yadav
wrote:
> Hey guys,
>
> Would like to know t
I know its late to ask, but what is the parking situation at the office? Is
driving reasonable as a plan or should be walk from the Holiday Inn?
Michael
On 25 Jan 2016 4:58 PM, "Murray, Paul (HP Cloud)" wrote:
> See updated event detail information for the mid-cycle at:
> https://wiki.openstack.
On Sun, Feb 7, 2016 at 8:07 PM, Jay Pipes wrote:
[snip]
> Many contributors submit talks to speak at the conference part of an
> OpenStack Summit because their company says it's the only way they will pay
> for them to attend the design summit. This is, IMHO, a terrible thing. The
> design summ
On Mon, Feb 8, 2016 at 1:51 AM, Monty Taylor wrote:
[snip]
> Fifth - if we do this, the real need for the mid-cycles we currently have
> probably goes away since the summit week can be a legit wall-to-wall work
> week.
>
[snip]
Another reply to a specific point...
I disagree strongly here, a
Havana is very very old and no longer supported. Why are you porting
that release in particular?
Michael
On Tue, Jul 7, 2015 at 3:51 PM, Pradeep kumar
wrote:
> Hi Guys,
>
> I am porting openstack on arm platform, but while running nova-compute
> service on it throws segmentaion fault.
>
> Below
Is this new table as part of a contribution to upstream nova, or for a
private table? If its for a private table, then I'm not really sure
that's a great idea -- for example what happens when we consume the
migration number you use?
If this code isn't private, perhaps it would be easiest to share
b.com/openstack/oslo.db/blob/master/oslo_db/options.py
>
> Actually, we just happened to be discussing this at the Nova meetup this
> morning. And the general consensus was the opposite. It would be better
> to collect all the config options in one file, especially if we are
> going to
On Fri, Jul 24, 2015 at 3:55 AM, Daniel P. Berrange
wrote:
> On Thu, Jul 23, 2015 at 11:57:01AM -0500, Michael Still wrote:
> > In fact, I did an example of what I thought it would look like already:
> >
> > https://review.openstack.org/#/c/205154/
> >
>
On Fri, Jul 24, 2015 at 2:19 PM, Doug Hellmann
wrote:
>
> One idea I've tossed around a bit is having options defined in data
> files that ship with the code, rather than being inside the Python
> code itself. Maybe a first pass at that would be to offload the
> help to a separate file? If that se
On Thu, Aug 13, 2015 at 4:29 AM, Sean Dague wrote:
> On 08/12/2015 02:23 PM, Jay Pipes wrote:
> > On 08/12/2015 01:20 PM, Markus Zoeller wrote:
> >
> >> The three questions I have with every config option:
> >> 1) which service(s) access this option?
> >> 2) what does it do? / what's the impact?
I agree with the rationale here, and will be reviewing
https://review.openstack.org/#/c/215764/ accordingly.
Michael
On Mon, Aug 24, 2015 at 7:56 PM, Daniel P. Berrange
wrote:
> On Mon, Aug 17, 2015 at 01:22:28PM -0600, Chris Friesen wrote:
> >
> > I tried bringing this up on the irc channel, b
I think they should not be marked experimental. For better or for worse,
there are multiple sites deployed, and we will support them if something
goes wrong.
That said, I wouldn't be encouraging new deployments of cells v1 at this
point.
Michael
On Thu, Sep 3, 2015 at 12:55 PM, Lana Brindley
wr
I've +2'ed Tony's Nova patch, but it would be nice to get another core to
take a look as well.
Michael
On Fri, Oct 2, 2015 at 12:34 PM, Robert Collins
wrote:
> On 2 October 2015 at 12:00, Kevin L. Mitchell
> wrote:
> > On Thu, 2015-10-01 at 15:53 -0700, Clark Boylan wrote:
> >> On Thu, Oct 1,
I think I'd rephrase your definition of pre-fetched to be honest --
something more like "images on this hypervisor node without a currently
running instance". So, your operations would become:
- trigger an image prefetching
- list unused base images (and perhaps when they were last used)
- dele
I note that we use instance.name to lookup the libvirt domain a bunch
in the driver. I'm wondering why we don't just use instance.uuid all
the time -- the code for that already exists. Is there a good reason
to not move to always using the uuid?
I ask because instance.name is not guaranteed to be
I am +1 on this.
Michael
On Wed, May 20, 2015 at 2:37 PM, Julien Danjou wrote:
> On Wed, May 20 2015, Davanum Srinivas wrote:
>
>> I'd like to invite Robert Collins (aka lifeless) as an Oslo core.
>> Robert has been a long time contributor to a whole bunch of OpenStack
>> projects and a member o
On Thu, May 21, 2015 at 7:49 AM, Sahid Orentino Ferdjaoui
wrote:
> On Thu, May 21, 2015 at 10:23:35AM +0100, Daniel P. Berrange wrote:
>> On Wed, May 20, 2015 at 03:01:50PM -0700, Michael Still wrote:
>> > I note that we use instance.name to lookup the libvirt domain a bunch
I just did an abandon run for specs that meet this criteria and
haven't been touched since March. Once again, this isn't a kiss of
death, just an attempt at review backlog hygiene.
Cheers,
Michael
On Tue, May 5, 2015 at 1:26 AM, John Garbutt wrote:
> On Monday, May 4, 2015, Michael
Hi,
I'm finding that oslo being in 1,400 different git repos is making it
hard to build a gerrit review dashboard URL. Does anyone have one of
these already built that I can just steal?
Thanks,
Michael
--
Rackspace Australia
_
Oh cool. Thanks!
Michael
On Thu, May 21, 2015 at 10:14 AM, Robert Collins
wrote:
> One is linked from https://wiki.openstack.org/wiki/Oslo#Review_Links
>
> On 22 May 2015 at 05:13, Michael Still wrote:
>> Hi,
>>
>> I'm finding that oslo being in 1,400 differen
Hey,
it would be cool if devs posting changes for nova which depend on us
approving their spec could use Depends-On to make sure their code
doesn't land until the spec does.
Just my random thought for the day.
Michael
--
Rackspace Australia
2015 at 3:10 AM, Michael Still wrote:
> I just did an abandon run for specs that meet this criteria and
> haven't been touched since March. Once again, this isn't a kiss of
> death, just an attempt at review backlog hygiene.
>
> Cheers,
> Michael
>
> On Tue, May 5,
Hi!
On Fri, Jun 12, 2015 at 7:07 AM, Mark Boo wrote:
[snip]
> Now my questions are:
>
> - Is this (file injection using image mounting) likely to be deprecated at
> some point in the future?
Yes, we've been building up to that for a long time and I can't see is
not doing it. Its important beca
I don't think you need a spec for this (its a refactor). That said,
I'd be interested in exploring how you deprecate the old flags. Can
you have more than one deprecated name for a single flag?
Michael
On Wed, Jun 17, 2015 at 7:29 AM, Matt Riedemann
wrote:
>
>
> On 6/16/2015 4:21 PM, Matt Riedem
As an aside, do we think that exposing the exact version of a server
process is safe from a security perspective?
Michael
On Sat, Jun 20, 2015 at 10:14 AM, Devananda van der Veen
wrote:
> Almost all of our discussions so far on this topic have left something out,
> which Monty pointed out to me
Hi,
https://review.openstack.org/#/c/149625 made me think about optional
requirements for nova. Some hypervisor drivers have requirements that
are either only needed for their driver, or are optional to their
driver. Examples include the ironic driver depending on the ironic
client, and the review
uired?
Cheers,
Michael
On Mon, Jun 22, 2015 at 8:45 PM, Sean Dague wrote:
> On 06/22/2015 06:37 AM, Michael Still wrote:
>> Hi,
>>
>> https://review.openstack.org/#/c/149625 made me think about optional
>> requirements for nova. Some hypervisor drivers have requirement
(Noting that its kind of late where I am).
Sean, I totally agree that we should fix uname. Let's get on that.
Michael
On Mon, Jun 22, 2015 at 8:52 PM, Sean Dague wrote:
> On 06/22/2015 05:28 AM, John Garbutt wrote:
>> On 22 June 2015 at 00:14, Michael Still wrote:
>>> A
cycle.
Cheers,
Michael
On Tue, Jun 23, 2015 at 2:04 AM, Jeremy Stanley wrote:
> On 2015-06-22 21:05:11 +1000 (+1000), Michael Still wrote:
>> Sure, except where the thing isn't in pip... I just learned tonight
>> that the libosinfo thing in the review at the start of this thread
I agree. I feel like this is another example of functionality which is
trivially implemented outside nova, and where it works much better if
we don't do it. Couldn't an admin just have a cron job which verifies
hosts, and then adds them to a compromised-hosts host aggregate if
they're owned? I assu
Hi,
I just wanted to let people know that we're setting a deadline of 7
July for mid-cycle meetup signups. So, if you're intending to sign up
but haven't already I'd do it real soon now.
You can sign up at:
https://www.eventbrite.com.au/e/openstack-nova-liberty-mid-cycle-developer-meetup-ti
Just a reminder that the deadline is next week!
Cheers,
Michael
On Fri, Jun 26, 2015 at 8:57 AM, Michael Still wrote:
> Hi,
>
> I just wanted to let people know that we're setting a deadline of 7
> July for mid-cycle meetup signups. So, if you're intending to sign up
>
I normally do this in one big batch, but haven't had a chance yet. I'll do
that later this week.
Michael
On 17 Mar 2016 7:50 AM, "Matt Riedemann" wrote:
> Specs are proposed to the 'approved' subdirectory and when they are
> completely implemented in launchpad (the blueprint status is
> 'Impleme
Today's hangout:
https://plus.google.com/hangouts/_/gwjbog3l3omtk2f4tt5s5v4hn4a
Michael
On Tue, Jan 27, 2015 at 9:11 AM, Michael Still wrote:
> For reference, that's because we were having lunch. It seems to be
> working well again.
>
> Michael
>
> On Tue, Jan
Greetings,
I would like to nominate Melanie Witt for the python-novaclient-core team.
(What is python-novaclient-core? Its a new group which will contain
all of nova-core as well as anyone else we think should have core
reviewer powers on just the python-novaclient code).
Melanie has been involv
And today's:
https://plus.google.com/hangouts/_/gyadkf7bm7wfpsrshlfenb4hiqa
Michael
On Tue, Jan 27, 2015 at 9:06 AM, Michael Still wrote:
> Today's hangout:
>
> https://plus.google.com/hangouts/_/gwjbog3l3omtk2f4tt5s5v4hn4a
>
> Michael
>
> On Tue, Jan 27, 2015 a
Hi,
as you might have read on openstack-dev, the Nova EC2 API
implementation is in a pretty sad state. I wont repeat all of those
details here -- you can read the thread on openstack-dev for detail.
However, we got here because no one is maintaining the code in Nova
for the EC2 API. This is despi
forge project. That seems the best way forward at this
point.
Thanks,
Michael
On 30 Jan 2015 11:11 am, "matt" wrote:
> Is there a blue print or some set of bugs tagged in some way to tackle?
>
> -matt
>
> On Thu, Jan 29, 2015 at 7:01 PM, Michael Still wrote:
>
>&
On Thu, Jan 29, 2015 at 5:15 PM, Michael Still wrote:
> There is an ec2 bug tag in launchpad. I would link to it except I am writing
> this offline. I will fix that later today.
Ok, now that the 40 seater turbo prop has landed, here we go:
https://bugs.launchpad.net/nova/+bugs?field.t
It looks like this was never re-proposed for Kilo. I am open to it
being proposed for L* when that release opens for specs soon, but we
need a developer to be advocating for it.
Michael
On Sun, Feb 1, 2015 at 5:22 PM, Adam Lawson wrote:
> Question, looks like this spec was abandoned , hard to te
t¹s good for these
>>>> APIs to be able to iterate outside of the standard release cycle.
>>>>
>>>>
>>>>
>>>> --Randy
>>>>
>>>> VP, Technology, EMC Corporation
>>>> Formerly Founder & CEO, Cloudscaling
the beginning of a release cycle.
Thanks again to everyone who has volunteered to help out with this.
35% of our users are grateful!
Michael
> On 2/2/15 2:46 AM, Michael Still wrote:
>>
>> So, its exciting to me that we seem to developing more forward
>> momentum here. I per
I agree that the priority at the moment for Nova should be getting our
EC2 implementation working well enough that it buys us time to
transition people to whatever the future may be.
Its unfortunate that we have approved the spec for this work in Kilo,
but I think that's an indication that we didn
Its been a week, so I have now added Melanie to this group. Welcome aboard!
Michael
On Wed, Jan 28, 2015 at 9:41 AM, Michael Still wrote:
> Greetings,
>
> I would like to nominate Melanie Witt for the python-novaclient-core team.
>
> (What is python-novaclient-core? Its a new g
Certainly it was my intent when I created that agenda item to cover
reviews that wouldn't otherwise reach a decision -- either two cores
wedged, or something else that we can't resolve trivially in gerrit.
Now, I can see that people don't like reviews sitting for a long time,
but that's probably t
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.
The reason I didn't do this yesterday is that Joe wanted some time to
pin the stable requirements, which I believe he
next
week instead.
Michael
On Wed, Feb 11, 2015 at 8:51 AM, Joe Gordon wrote:
>
>
> On Mon, Feb 9, 2015 at 7:55 PM, Michael Still wrote:
>>
>> The previous policy is that we do a release "when requested" or when a
>> critical bug fix merges. I don't
Hi,
we had a meeting this morning to try and work through all the FFE
requests for Nova. The meeting was pretty long -- two hours or so --
and we did in in the nova IRC channel in an attempt to be as open as
possible. The agenda for the meeting was the list of FFE requests at
https://etherpad.open
301 - 400 of 510 matches
Mail list logo
