instance attain rate
limiting. I guess:)
and belowed[1][2] is some fragments of my env.
So, Can someone please explain this situation for me, and, your help is a
highly appreciated.
Thanks.
Joe
--[1]: source compute node
# virsh list
112 instance-0331 paused
[This was originally posted to openst...@lists.openstack.org by accident.
Reposting it to openstack-dev.]
Calling all Heat neophytes, aficionados, and everyone in between ...
I've often thought it would be helpful to add a Heat Template Cookbook to the
developer documentation.
Like any helping
7dfd158458e3dd59f223a6e5#.VUOcRq1VhBc
jd
—
Joe D’Andrea
AT&T Labs - Research
Cloud Technologies & Services
Bedminster, NJ
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-req
Tim,
> On Jun 9, 2015, at 10:04 AM, Tim Hinrichs wrote:
>
> Hi Joe,
>
> The telco slides are powerpoint, but are hosted on google drive ...
Thanks very much for the OpEx slides (and corresponding design doc)!
Is there a deck link for "Congress: Introduction, Status,
> On Jun 15, 2015, at 11:06 AM, Tim Hinrichs wrote:
>
> Hi Joe,
>
> Here's the link to the Intro to Congress slide deck.
Thank you! I should have re-checked the wiki. :)
jd
__
OpenStack Development M
ble. I imagine there are others I haven't thought of.
Questions/feedback welcomed and appreciated, especially if it can help me draw
a better bead on the scope of this change and what would need altering. I will
then use that to help inform an initial blueprint and shepherd it forward
On Tue, Aug 5, 2014 at 4:17 PM, Robert Collins
wrote:
> Hi!
>
> James has run into an issue implementing the multi-hypervisor spec
> (
> http://git.openstack.org/cgit/openstack/tripleo-specs/tree/specs/juno/tripleo-juno-deploy-cloud-hypervisor-type.rst
> )
> which we're hoping to use to reduce in
On Sat, Aug 9, 2014 at 6:29 AM, Eoghan Glynn wrote:
>
>
> > > Hi Folks,
> > >
> > > Dina Belova has recently landed some infra patches[1,2] to create
> > > an experimental mongodb-based Tempest job. This effectively just
> > > overrides the ceilometer storage backend config so that mongodb
> > >
On Sun, Aug 10, 2014 at 11:59 PM, Mark McLoughlin wrote:
> On Fri, 2014-08-08 at 09:06 -0400, Russell Bryant wrote:
> > On 08/07/2014 08:06 PM, Michael Still wrote:
> > > It seems to me that the tension here is that there are groups who
> > > would really like to use features in newer libvirts th
dition gate variant to all
> projects.
> > With the effort to reduce the number of gate variants we have [0] I would
> > prefer to see just ceilometer gate on both mongodb and sqlalchemy and the
> > main integrated gate [1] pick just one.
>
> Just checking to see t
On Mon, Aug 11, 2014 at 3:53 PM, Devananda van der Veen <
devananda@gmail.com> wrote:
> On Mon, Aug 11, 2014 at 3:27 PM, Joe Gordon wrote:
> >
> >
> >
> > On Mon, Aug 11, 2014 at 3:07 PM, Eoghan Glynn wrote:
> >>
> >>
> >>
> &g
On Fri, Aug 8, 2014 at 6:58 AM, Kyle Mestery wrote:
> On Thu, Aug 7, 2014 at 1:26 PM, Joe Gordon wrote:
> >
> >
> >
> > On Tue, Aug 5, 2014 at 9:03 AM, Thierry Carrez
> > wrote:
> >>
> >> Hi everyone,
> >>
> >> With the inc
On Tue, Aug 12, 2014 at 8:46 AM, Jay Pipes wrote:
> On 08/12/2014 10:56 AM, Mark McLoughlin wrote:
>
>> Hey
>>
>> (Terrible name for a policy, I know)
>>
>> From the version_cap saga here:
>>
>>https://review.openstack.org/110754
>>
>> I think we need a better understanding of how to approac
On Tue, Aug 12, 2014 at 11:08 AM, Doug Hellmann
wrote:
>
> On Aug 12, 2014, at 1:44 PM, Dolph Mathews
> wrote:
>
>
> On Tue, Aug 12, 2014 at 12:30 AM, Joe Gordon
> wrote:
>
>>
>>
>>
>> On Fri, Aug 8, 2014 at 6:58 AM, Kyle Mestery wrote:
&
On Tue, Aug 12, 2014 at 12:23 AM, Mark McLoughlin wrote:
> On Mon, 2014-08-11 at 15:25 -0700, Joe Gordon wrote:
> >
> >
> >
> > On Sun, Aug 10, 2014 at 11:59 PM, Mark McLoughlin
> > wrote:
> > On Fri, 2014-08-08 at 09:06 -0400, Russell Bryant wrot
On Wed, Aug 13, 2014 at 2:01 AM, Nikola Đipanov wrote:
> On 08/13/2014 04:05 AM, Michael Still wrote:
> > On Wed, Aug 13, 2014 at 4:26 AM, Eoghan Glynn wrote:
> >>
> >>> It seems like this is exactly what the slots give us, though. The core
> review
> >>> team picks a number of slots indicating
On Wed, Aug 13, 2014 at 5:13 AM, Mark McLoughlin wrote:
> On Thu, 2014-08-07 at 09:30 -0400, Sean Dague wrote:
>
> > While I definitely think re-balancing our quality responsibilities back
> > into the projects will provide an overall better release, I think it's
> > going to take a long time bef
On Wed, Aug 13, 2014 at 2:48 PM, Duncan Thomas
wrote:
> On 13 August 2014 13:57, Matthew Treinish wrote:
> > On Tue, Aug 12, 2014 at 01:45:17AM +0400, Boris Pavlovic wrote:
> >> Keystone, Glance, Cinder, Neutron and Heat are running rally performance
> >> jobs, that can be used for performance t
On Wed, Aug 13, 2014 at 8:31 PM, Michael Still wrote:
> On Thu, Aug 14, 2014 at 1:24 PM, Jay Pipes wrote:
>
> > Just wanted to quickly weigh in with my thoughts on this important
> topic. I
> > very much valued the face-to-face interaction that came from the
> mid-cycle
> > meetup in Beaverton (
On Thu, Aug 14, 2014 at 1:47 AM, Daniel P. Berrange
wrote:
> On Thu, Aug 14, 2014 at 09:24:36AM +1000, Michael Still wrote:
> > On Thu, Aug 14, 2014 at 3:09 AM, Dan Smith wrote:
> > >> I'm not questioning the value of f2f - I'm questioning the idea of
> > >> doing f2f meetings sooo many times a
On Wed, Aug 13, 2014 at 12:24 PM, Doug Hellmann
wrote:
>
> On Aug 13, 2014, at 3:05 PM, Eoghan Glynn wrote:
>
> >
> >>> At the end of the day, that's probably going to mean saying No to more
> >>> things. Everytime I turn around everyone wants the TC to say No to
> >>> things, just not to their
Running a silent check on
> >> changes to Nova is the first step in establishing that history.
> >>
> >> Joe Gordon suggests we need a spec to bring the driver back into Nova.
> >> Besides the fact that specs are closed and there is no intention of
> >>
On Fri, Aug 15, 2014 at 8:17 AM, Sandy Walsh
wrote:
> On 8/14/2014 6:42 PM, Doug Hellmann wrote:
>
>
> On Aug 14, 2014, at 4:41 PM, Joe Gordon wrote:
>
>
>
>
> On Wed, Aug 13, 2014 at 12:24 PM, Doug Hellmann
> wrote:
>
>>
>> On Aug 13, 2014, at 3:
On Thu, Aug 14, 2014 at 4:02 PM, Eoghan Glynn wrote:
>
> > > Additional cross-project resources can be ponied up by the large
> > > contributor companies, and existing cross-project resources are not
> > > necessarily divertable on command.
> >
> > Sure additional cross-project resources can and
On Thu, Aug 14, 2014 at 4:02 PM, Eoghan Glynn wrote:
>
> > > Additional cross-project resources can be ponied up by the large
> > > contributor companies, and existing cross-project resources are not
> > > necessarily divertable on command.
> >
> > Sure additional cross-project resources can and
On Aug 16, 2014 10:37 AM, "Jeremy Stanley" wrote:
>
> On 2014-08-16 04:01:25 +0200 (+0200), Chmouel Boudjnah wrote:
> > If like me you find it difficult to read a large text file like
> > the rst specs inside gerrit diff interface viewer, I have created
> > a script that gets rst files in a review
On Mon, Aug 18, 2014 at 3:18 AM, Thierry Carrez
wrote:
> Doug Hellmann wrote:
> > On Aug 13, 2014, at 4:42 PM, Russell Bryant wrote:
> >> Let me try to say it another way. You seemed to say that it wasn't much
> >> to ask given the rate at which things happen in OpenStack. I would
> >> argue t
On Mon, Aug 18, 2014 at 8:18 AM, Russell Bryant wrote:
> On 08/18/2014 06:18 AM, Thierry Carrez wrote:
> > Doug Hellmann wrote:
> >> On Aug 13, 2014, at 4:42 PM, Russell Bryant wrote:
> >>> Let me try to say it another way. You seemed to say that it wasn't
> much
> >>> to ask given the rate at
On Mon, Aug 18, 2014 at 5:22 AM, Daniel P. Berrange
wrote:
> On Mon, Aug 18, 2014 at 12:18:16PM +0200, Thierry Carrez wrote:
> > Doug Hellmann wrote:
> > > On Aug 13, 2014, at 4:42 PM, Russell Bryant
> wrote:
> > >> Let me try to say it another way. You seemed to say that it wasn't
> much
> > >
On Sun, Aug 17, 2014 at 9:24 AM, Jay Bryant
wrote:
> +2
>
> I prefer the LOG.warning format and support that given the documentation
> you shared.
>
> If there is agreement I would create a hacking check.
>
I think a better approach is to just not care which i used here. IMHO
mixing up LOG.warn
On Tue, Aug 19, 2014 at 4:22 AM, Gary Kotton wrote:
> Hi,
> Minesweeper is back up and running – this is now called “Vmware NSX CI”.
> A patch for the deprecation of the ESX driver resulted in endless
> Minesweeper failures (https://review.openstack.org/#/c/108854/). These
> were resolved by a n
On Tue, Aug 19, 2014 at 8:47 AM, Daniel P. Berrange
wrote:
> On Tue, Aug 19, 2014 at 09:31:48PM +1200, Robert Collins wrote:
> > Hey everybody - https://wiki.openstack.org/wiki/TripleO/SpecReviews
> > seems pretty sane as we discussed at the last TripleO IRC meeting.
> >
> > I'd like to propose t
On Tue, Aug 19, 2014 at 8:23 AM, Russell Bryant wrote:
> On 08/19/2014 05:31 AM, Robert Collins wrote:
> > Hey everybody - https://wiki.openstack.org/wiki/TripleO/SpecReviews
> > seems pretty sane as we discussed at the last TripleO IRC meeting.
> >
> > I'd like to propose that we adopt it with t
On Aug 19, 2014 10:45 AM, "Day, Phil" wrote:
>
> > -Original Message-
> > From: Nikola Đipanov [mailto:ndipa...@redhat.com]
> > Sent: 19 August 2014 17:50
> > To: openstack-dev@lists.openstack.org
> > Subject: Re: [openstack-dev] [Nova] Scheduler split wrt Extensible
Resource
> > Tracking
On Aug 20, 2014 10:56 AM, "John Garbutt" wrote:
>
> On 18 August 2014 11:18, Thierry Carrez wrote:
> > Doug Hellmann wrote:
> >> On Aug 13, 2014, at 4:42 PM, Russell Bryant wrote:
> >>> Let me try to say it another way. You seemed to say that it wasn't
much
> >>> to ask given the rate at which
ot sure if
we'd treat this as a 'bug' or whether there is a blueprint under which
this could be done?
Thanks,
Joe
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Fri, Aug 22, 2014 at 2:11 AM, Daniel P. Berrange
wrote:
> On Thu, Aug 21, 2014 at 09:02:17AM -0700, Armando M. wrote:
> > Hi folks,
> >
> > According to [1], we have ways to introduce external references to commit
> > messages.
> >
> > These are useful to mark certain patches and their relevan
point, or merely an approach at a
staged implementation [that might welcome some additions]? :)
Thanks,
Joe
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
onger want this VM to have an anti-affinity policy
relative to the others, etc.).
- Joe
On Mon, Aug 25, 2014 at 10:16 AM, Jay Pipes wrote:
> On 08/25/2014 11:10 AM, Joe Cropper wrote:
>>
>> Hello,
>>
>> Is our long-term vision to allow a VMs to be dynamically added/r
this queued up as a discussion point for Paris? If so, count me in!
Thanks,
Joe
On Mon, Aug 25, 2014 at 11:08 AM, Jay Pipes wrote:
> On 08/25/2014 11:31 AM, Joe Cropper wrote:
>>
>> Thanks Jay. Those are the same types of questions I was pondering as
>> well when debating how
to be checked.
Thoughts?
Thanks,
Joe
> On Aug 25, 2014, at 12:10 PM, Russell Bryant wrote:
>
>> On 08/25/2014 12:56 PM, Joe Cropper wrote:
>> That was indeed a rather long (and insightful) thread on the topic.
>> It sounds like there are still some healthy discussions w
IT administrator to use them--hence why I'm
exploring adding some additional functionality; I'm even happy to help
implement this, if we can get any type of concurrence on the subject.
:-)
- Joe
On Mon, Aug 25, 2014 at 12:58 PM, Russell Bryant wrote:
> On 08/25/2014 01:25 PM, Joe C
On Aug 24, 2014 9:04 AM, "Morgan Fainberg"
wrote:
>
>
>
> On Sunday, August 24, 2014, Anne Gentle wrote:
>>
>> I'm following this as well since I have the exact same problem in a
docstring patch for heat.
>>
>
> Keystone saw an oddity with the new sample config generator (changing how
options are
On Mon, Aug 4, 2014 at 3:29 AM, Chris Dent wrote:
>
> In the "Thoughts on the patch test failure rate and moving forward"
> thread[1] there's discussion of moving some of the burden for
> functional testing to the individual projects. This seems like a good
> idea to me, but also seems like it co
On Mon, Aug 25, 2014 at 2:50 PM, Chris Dent wrote:
> On Mon, 25 Aug 2014, Joe Gordon wrote:
>
> [Other stuff snipped, thanks for that, good to have some pointers.]
>
>
> Why can't you run devstack locally? Maybe there are some changes we can
>> make so its easier
You're always welcome to submit a patch for a valid bug. Just put:
Closes-Bug: #
At the bottom of the commit message to link the change set to the bug. :)
- Joe
> On Aug 25, 2014, at 9:44 PM, Jae Sang Lee wrote:
>
> Hi, all.
>
> Diskfilter based on host disk usage, it
On Tue, Aug 19, 2014 at 11:57 AM, James Slagle
wrote:
> On Tue, Aug 19, 2014 at 1:58 PM, Joe Gordon wrote:
> >
> > While I cannot speak for the dynamics of the tripleo team, if this were
> to
> > be adopted in nova I would not +2 any blueprints as I don't think I ca
On Tue, Aug 26, 2014 at 5:36 AM, Wang Shen wrote:
> Hi, All
> I have done some work to test the performance of LUN scanning, use
> "iscsiadm" with "--rescan" like what Nova dose. In my test, a host
> connected with a lot of LUNs , more than 1000 LUNs. Because "--rescan"
> will cause kernel to sca
On Mon, Aug 25, 2014 at 6:36 AM, Sean Dague wrote:
> On 08/20/2014 12:37 PM, Zane Bitter wrote:
> > On 11/08/14 05:24, Thierry Carrez wrote:
> >> So the idea that being (and remaining) in the integrated release should
> >> also be judged on technical merit is a slightly different effort. It's
> >
resources, or the level of domain-
> > expertise that they can be realistically be expected bring to the
> > table, or the period of time to on-board them, or something else?
> >
> >
> > Yes, all of the above.
>
> Hi Joe,
>
> In coming to that conclusion,
On Tue, Aug 26, 2014 at 5:31 AM, Boris Pavlovic wrote:
> Hi stackers,
>
>
> It goes without saying that end users, that are actually using your
> tool/project/service, usually don't have enough time to join community,
> understand all technical details and road map of project and after that
> con
On Wed, Aug 27, 2014 at 12:30 PM, James E. Blair
wrote:
> Kevin Benton writes:
>
> > From what I understand, the intended projects for the incubator can't
> > operate without neutron because they are just extensions/plugins/drivers.
>
> I could have phrased that better. What I meant was that th
On Thu, Aug 28, 2014 at 10:17 AM, Sean Dague wrote:
> On 08/28/2014 12:48 PM, Doug Hellmann wrote:
> >
> > On Aug 27, 2014, at 5:56 PM, Sean Dague wrote:
> >
> >> On 08/27/2014 05:27 PM, Doug Hellmann wrote:
> >>>
> >>> On Aug 27, 2014, at 2:54 PM, Sean Dague wrote:
> >>>
> Note: thread in
learning in simpler times.
>
> I think we could develop tools and visualizations that would help the
> debugging tasks. We could make those tasks more visible, and therefore
> more appealing to the brave souls that step up to tackle them. Sean and
> Joe did a ton of work improving the
On Thu, Aug 28, 2014 at 2:40 AM, Daniel P. Berrange
wrote:
> On Thu, Aug 28, 2014 at 01:04:57AM +, Dugger, Donald D wrote:
> > I'll try and not whine about my pet project but I do think there
> > is a problem here. For the Gantt project to split out the scheduler
> > there is a crucial BP th
On Thu, Aug 28, 2014 at 2:43 PM, Alan Kavanagh
wrote:
> I share Donald's points here, I believe what would help is to clearly
> describe in the Wiki the process and workflow for the BP approval process
> and build in this process how to deal with discrepancies/disagreements and
> build timeframes
.2014-08-28-21.01.log.html
[1] https://wiki.openstack.org/wiki/Juno_Release_Schedule
[2] https://blueprints.launchpad.net/nova/juno
[3] http://54.201.139.117/nova-bugs.html
best,
Joe
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
On Thu, Aug 28, 2014 at 3:27 PM, Chris Friesen
wrote:
> On 08/28/2014 04:01 PM, Joe Gordon wrote:
>
>>
>>
>>
>> On Thu, Aug 28, 2014 at 2:43 PM, Alan Kavanagh
>> mailto:alan.kavan...@ericsson.com>> wrote:
>>
>> I share Donald's
change the policy on nova-api during this migration
to only allow access to a special "migration" role or the like? This
would disable services or users from accessing Nova's api when a
special policy is applied for the migration, but
On Aug 29, 2014 10:42 AM, "Dugger, Donald D"
wrote:
>
> Well, I think that there is a sign of a broken (or at least bent) process
and that's what I'm trying to expose. Especially given the ongoing
conversations over Gantt it seems wrong that ultimately it was rejected due
to silence. Maybe rejec
goal of this exercise is to help us see if our individual world views
align with the greater community, and to get the ball rolling on a larger
discussion of where as a project we should be focusing more time.
best,
Joe Gordon
[0]
http://lists.openstack.org/pipermail/openstack-dev/2014-August
On Tue, Aug 26, 2014 at 4:47 PM, Salvatore Orlando
wrote:
> TL; DR
> A few folks are proposing to stop running tests for neutron advanced
> services [ie: (lb|vpn|fw)aas] in the integrated gate, and run them only on
> the neutron gate.
>
> Reason: projects like nova are 100% orthogonal to neutron
t; https://review.openstack.org/102643
>
> where upgrading to Ubuntu Trusty meant the libvirt version in use in the
> gate went from 0.9.8 to 1.2.2, which caused the "live snapshot" code
> paths in Nova for the first time, which appeared to be related to some
> serious
On Wed, Sep 3, 2014 at 2:50 AM, Nikola Đipanov wrote:
> On 09/02/2014 09:23 PM, Michael Still wrote:
> > On Tue, Sep 2, 2014 at 1:40 PM, Nikola Đipanov
> wrote:
> >> On 09/02/2014 08:16 PM, Michael Still wrote:
> >>> Hi.
> >>>
> >>> We're soon to hit feature freeze, as discussed in Thierry's rec
On Wed, Sep 3, 2014 at 8:57 AM, Solly Ross wrote:
> > I will follow up with a more detailed email about what I believe we are
> > missing, once the FF settles and I have applied some soothing creme to
> > my burnout wounds, but currently my sentiment is:
> >
> > Contributing features to Nova nowa
being requested for the initial deployment
(unless I'm missing something, which could be the case).
This patch aims to 'fix' that. Comments are welcomed.
Thanks,
Joe
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http:/
On Wed, Sep 3, 2014 at 11:30 PM, Michael Still wrote:
> I'm good with this one too, so that makes three if Joe is ok with this.
>
I am ok with this, I hope the move to oslo.db will fix a few bugs for us
and the nova patch to review isn't too bad.
>
> @Josh -- can you ple
On Thu, Sep 4, 2014 at 2:23 AM, John Garbutt wrote:
> Sorry for another top post, but I like how Nikola has pulled this
> problem apart, and wanted to respond directly to his response.
>
> On 3 September 2014 10:50, Nikola Đipanov wrote:
> > The reason many features including my own may not make
On Thu, Sep 4, 2014 at 3:24 AM, Daniel P. Berrange
wrote:
> Position statement
> ==
>
> Over the past year I've increasingly come to the conclusion that
> Nova is heading for (or probably already at) a major crisis. If
> steps are not taken to avert this, the project is likely to
On Fri, Sep 5, 2014 at 4:05 AM, Nikola Đipanov wrote:
> On 09/04/2014 10:25 PM, Solly Ross wrote:
> > Anyway, I think it would be useful to have some sort of page where people
> > could say "I'm an SME in X, ask me for reviews" and then patch
> submitters could go
> > and say, "oh, I need an some
On Fri, Sep 5, 2014 at 9:11 AM, Mike Wilson wrote:
> Hi all,
>
> I am requesting an exception for the juno-slaveification blueprint. There
> is a single outstanding patch [1] which has already been approved before,
> but needed to be re-spun due to gate failures which then necessitated a
> rebase
. :-)
- Joe
On Sep 5, 2014, at 3:41 PM, Jay Bryant wrote:
> Matt,
>
> I don't think that is the right solution.
>
> If the string changes I think the only problem is it won't be translated if
> it is thrown. That is better than breaking the coding standard imho.
>
&g
Thanks, ttx.
If there’s anyone that can do a final review on
https://review.openstack.org/#/c/118535/ — would be much appreciated and I’m
happy to llet the i18n folks know once it merges.
- Joe
On Sep 6, 2014, at 9:36 AM, Thierry Carrez wrote:
> In that precise case, given how early it
rried that some OpenStack services such as nova-api,
nova-conductor and cinder-api take up so much memory? Does there memory
usage keep growing over time, does anyone have any numbers to answer this?
Why do these processes take up so much memory?
best,
Joe
[0]
http://logstash.openstac
On Wed, Sep 3, 2014 at 8:37 AM, Joe Gordon wrote:
> As you all know, there has recently been several very active discussions
> around how to improve assorted aspects of our development process. One idea
> that was brought up is to come up with a list of cycle goals/project
> priorit
wouldn’t be violated by the addition of
the VM
2. Removing a VM from a server group
Just allow it
I think this would round out the support that’s there and really allow us to
capitalize on the hard work everyone’s already put into them.
- Joe
On Aug 26, 2014, at 6:39 PM, Chris Friesen wrote
what’s
already there [1].
[1] Sure, the to-be-added VM could be in the midst of a migration or something,
but that would be pretty simple to check make sure its task state is None or
some such.
- Joe
On Sep 10, 2014, at 5:16 PM, Russell Bryant wrote:
>
>
>> On Sep 10, 2014, at
think that’s necessary.
Overall, this seems like a feasible, fairly minor enhancement--that wouldn’t
make us any worse off than we are today (perhaps address some existing race
conditions), all whilst providing a large improvement to the overall usability
of the server groups. :-)
- Joe
On Sep 10
Agreed - I’ll draft up a formal proposal in the next week or two and we can
focus the discussion there. Thanks for the feedback - this provides a good
framework for implementation considerations.
- Joe
On Sep 10, 2014, at 6:00 PM, Russell Bryant wrote:
> On 09/10/2014 06:46 PM, Joe Crop
Hi Folks,
Just wondering if the nova-specs master branch will have a ‘kilo’ directory
created soon for Kilo proposals? I have a few things I’d like to submit, just
looking for the proper home.
Thanks,
Joe
___
OpenStack-dev mailing list
OpenStack-dev
Thanks! Exactly what I was looking for.
On Sep 11, 2014, at 12:38 AM, Russell Bryant wrote:
> On 09/11/2014 01:32 AM, Joe Cropper wrote:
>> Hi Folks,
>>
>> Just wondering if the nova-specs master branch will have a ‘kilo’
>> directory created soon for Kilo proposa
Great to hear. I started a blueprint for this [1]. More detail can be added
once the kilo nova-specs directory is created… for now, I’ve tried to put some
fairly detailed notes on the blueprint’s description.
[1] https://blueprints.launchpad.net/nova/+spec/dynamic-server-groups
- Joe
On Sep
.
In any case, I’ve started a blueprint on this [1] and we can continue iterating
in the nova-spec once kilo opens up. Thanks all for the good discussion on
this thus far.
[1] https://blueprints.launchpad.net/nova/+spec/dynamic-server-groups
- Joe
On Sep 11, 2014, at 5:04 PM, Chris Friesen
On Tue, Sep 9, 2014 at 12:19 PM, Kurt Griffiths <
kurt.griffi...@rackspace.com> wrote:
> Hi folks,
>
> In this second round of performance testing, I benchmarked the new Redis
> driver. I used the same setup and tests as in Round 1 to make it easier to
> compare the two drivers. I did not test Red
On Thu, Sep 11, 2014 at 2:18 AM, Daniel P. Berrange
wrote:
> On Thu, Sep 11, 2014 at 09:23:34AM +1000, Michael Still wrote:
> > On Thu, Sep 11, 2014 at 8:11 AM, Jay Pipes wrote:
> >
> > > a) Sorting out the common code is already accounted for in Dan B's
> original
> > > proposal -- it's a prere
On Sep 15, 2014 8:31 PM, "Jay Pipes" wrote:
>
> On 09/15/2014 08:07 PM, Jeremy Stanley wrote:
>>
>> On 2014-09-15 17:59:10 -0400 (-0400), Jay Pipes wrote:
>> [...]
>>>
>>> Sometimes it's pretty hard to determine whether something in the
>>> E-R check page is due to something in the infra scripts,
hough not graphed), but in the
> former case only one “project” was used.
>
multiple Tenant/Project-IDs
>
> From: Joe Gordon
> Reply-To: OpenStack Dev
> Date: Friday, September 12, 2014 at 1:45 PM
> To: OpenStack Dev
> Subject: Re: [openstack-dev] [zaqar] Juno Performance T
Hi All,
My understanding of Zaqar is that it's like SQS. SQS uses distributed
queues, which have a few unusual properties [0]:
Message Order
Amazon SQS makes a best effort to preserve order in messages, but due to
the distributed nature of the queue, we cannot guarantee you will receive
messages
Postgres is also logging a lot of errors:
http://logs.openstack.org/63/122263/1/check/check-tempest-dsvm-postgres-full/2f27252/logs/postgres.txt.gz
On Wed, Sep 17, 2014 at 4:49 PM, Clark Boylan wrote:
> Hello,
>
> Recent sampling of test run times shows that our tempest jobs run
> against clouds
On Tue, Sep 16, 2014 at 2:58 AM, Michael Still wrote:
> Hi.
>
> Is time to start identifying (and working on) release critical bugs in
> nova before we ship RC1.
>
> My initial position is that any critical bug is release critical.
> There are currently critical bugs not targeted to rc1, but that
On Thu, Sep 18, 2014 at 9:02 AM, Devananda van der Veen <
devananda@gmail.com> wrote:
> On Thu, Sep 18, 2014 at 7:55 AM, Flavio Percoco wrote:
> > On 09/18/2014 04:24 PM, Clint Byrum wrote:
> >> Great job highlighting what our friends over at Amazon are doing.
> >>
> >> It's clear from these
On Thu, Sep 18, 2014 at 7:45 AM, Flavio Percoco wrote:
> On 09/18/2014 04:09 PM, Gordon Sim wrote:
> > On 09/18/2014 12:31 PM, Flavio Percoco wrote:
> >> On 09/17/2014 10:36 PM, Joe Gordon wrote:
> >>> My understanding of Zaqar is that it's like SQS. SQS uses d
ename:"console.html" Title: test_network_basic_ops
fails waiting for network to become available Project: Status neutron: In
Progress swift: Invalid tempest: Invalid Hits FAILURE: 42 Bug:
https://bugs.launchpad.net/bugs/1218391 => message:"Cannot 'createImage'"
AND filename:&qu
Dims, we think https://review.openstack.org/#/c/57509/ will fix
125178<https://launchpad.net/bugs/1251784>
.
On Wed, Nov 20, 2013 at 3:58 PM, Davanum Srinivas wrote:
> Anita, Joe,
>
> I need help with adding debug message in:
> https://review.openstack.org/#/c/56316/
>
&
this BP, but I
will properly respond to that tommorow.
Also I am not sure what you mean with the subject line.
> >>
> >> And made patch that makes this work.
> >> But only because our BP wasn't approved we got -2 from Joe Gordon.
> >> (https://review.openstac
moment we don't have any working
>> way to purge DB... so admins should make it by hand.
>>
>>
>> And we made this BP (in october)
>> https://blueprints.launchpad.net/nova/+spec/db-purge-engine
>>
>> And made patch that makes this work.
+1
On Fri, Nov 22, 2013 at 2:41 PM, Christopher Yeoh wrote:
>
>
> +1
>
>
> On Sat, Nov 23, 2013 at 7:23 AM, Russell Bryant wrote:
>
>> Greetings,
>>
>> I would like to propose adding Matt Riedemann to the nova-core review
>> team.
>>
>> Matt has been involved with nova for a long time, taking o
sent on the go
On Nov 23, 2013 9:02 AM, "Davanum Srinivas" wrote:
>
> Gary,
>
> There's a blow-by-blow account in this etherpad -
> https://etherpad.openstack.org/p/critical-patches-gatecrash-November-2013
>
> On Sat, Nov 23, 2013 at 11:12 AM, Gary Kotton wrote:
> > Hi,
> > To whoever fixed the g
e are working on the
next steps to prevent this from happening again. The two most immediate
changes are:
- Doing a better job of triaging gate bugs (
http://lists.openstack.org/pipermail/openstack-dev/2013-November/020048.html
).
- In the next few days we will remove '
known set of nondeterministic issues down to 0 and keep it
> there.
>
Yes! In fact we are already working towards that. See
http://lists.openstack.org/pipermail/openstack-dev/2013-November/020048.html
>
> -Rob
>
> On 25 November 2013 18:00, Joe Gordon wrote:
> > Hi All,
> &g
1 - 100 of 1002 matches
Mail list logo
