Which periodic updates did you have in mind to eliminate? One of the few
remaining ones I can think of is sync_routers but it would be great if you
can enumerate the ones you observed because eliminating overhead in agents
is something I've been working on as well.
One of the most common is the he
Hey,
Host table works fine, and is enabled now. You should be able to pull the
latest commit and use it for appropriate policies.
https://review.openstack.org/#/c/172333/
Regards,
Samta Rangare
On 10 Apr 2015 06:38, "Masahito MUROI" wrote:
> Hi Alex,
>
> Thank you for replying.
>
> I feel easy
Hi all,
The first draft of the spec for Log Message Error Codes (from the Log Working
Group) is out for review:
https://review.openstack.org/#/c/172552/
Please comment, and please look for the way forward so that the different
places, ways and reasons errors get reported provide consistency ac
Hi, Attlia,
Interesting idea. Can you show us your test (or simulation test) result that
Neutron can support up to 100k managed node.
Best Regards
Chaoyi Huang ( joehuang )
From: Attila Fazekas [afaze...@redhat.com]
Sent: 10 April 2015 17:18
To: neil.je
On 2015-04-11 01:28:51 +0300 (+0300), Duncan Thomas wrote:
[...]
> We will not be merging any drivers without stable 3rd party CI in
> future
[...]
For clarity, hopefully this is "stable testing reporting on changes
to the project" in general, and not "3rd party CI" specifically.
After all, the Pr
Hi, Neil,
See inline comments.
Best Regards
Chaoyi Huang
From: Neil Jerram [neil.jer...@metaswitch.com]
Sent: 09 April 2015 23:01
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] Neutron scaling dat
Hello Christopher,
It does seem that configs are being read for another location. Try to remove
that copy in you home directory (so just keep the /etc location). If you see
the same issue, try to rename your /etc/barbican/barbican-api.conf file to
something else. Barbican should crash, probably
On Fri, Apr 10, 2015 at 6:28 PM, Duncan Thomas wrote:
> We will not be merging any drivers without stable 3rd party CI in future, so
> it is a requirement. You can submit the driver for initial review anytime
> now, but it will not get final approval without CI.
Great, we'll get the CI set up AS
Congratulations Emilien,
Looking forward to the progress we can make as a community!
On Apr 10, 2015 4:58 PM, "Colleen Murphy" wrote:
> Just to make it official: since we only had one nominee for PTL, we will
> go ahead and name Emilien Macchi as our new PTL without proceeding with an
> election
Just to make it official: since we only had one nominee for PTL, we will go
ahead and name Emilien Macchi as our new PTL without proceeding with an
election process. Thanks, Emilien, for all your hard work and for taking on
this responsibility!
Colleen (crinkle)
___
On 10 Apr 2015 21:02, "Joshua Huber" wrote:
> A couple questions:
>
> 1) When is it appropriate to submit the driver for review? Is
> 3rd-party CI a prerequisite?
We will not be merging any drivers without stable 3rd party CI in future,
so it is a requirement. You can submit the driver for initi
From: Angus Salkeld mailto:asalk...@mirantis.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, April 9, 2015 6:43 PM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@li
This discussion is actually rather timely. In Kilo, we just added a new
experimental API in Glance called the Catalog Index Service [1].
Basically, it provides multi-tenant elastic search based caching and
indexing for various resources using a plugin mechanism.
We proposed it and built it initial
On 04/07/2015 09:44 AM, Brant Knudson wrote:
On Tue, Apr 7, 2015 at 3:52 AM, Olena Logvinova
mailto:ologvin...@mirantis.com>> wrote:
Good day to everyone!
My name is Olena, I am new in OpenStack (working as a tech
writer). And I'm stuck on a bug
https://launchpad.net/bugs/14
> I'd say events are *more* useful in that workflow, not less, as long as
> they contain enough context. For example, the user creates a volume,
> tries to attach it which fails for some config error, so the user
> deletes it. With an event based model, the admin now has an error event
> in
I like this idea. It leaves specs and implementation details to people
familiar with the code base while providing a good place for users and devs
to discuss feature requests.
On Apr 10, 2015 2:04 PM, "John Kasperski"
wrote:
> On 04/10/2015 01:04 PM, Boris Pavlovic wrote:
>
> Hi,
>
> I believe
True. I was thinking more of the horizon event thing that show for a few
seconds, then vanish. not useful for this case... Maybe something like the way
heat keeps track of events, but more globally then? A list of error events in
the admin tab that admins should look at and clear?
_
On 04/10/2015 01:04 PM, Boris Pavlovic wrote:
> Hi,
>
> I believe that specs are too detailed and too dev oriented for
> managers, operators and devops.
> They actually don't want/have time to write/read all the stuff in
> specs and that's why the communication between dev & operators
> community
Hi,
I'm working on getting our cinder volume driver in shape for
submission for the Liberty release. To that end, I have some questions
about the OpenStack development process.
The associated blueprint is here:
https://blueprints.launchpad.net/cinder/+spec/blockbridge-eps-driver
Our volume drive
On Thu, Apr 09, 2015 at 04:00:39PM -0500, Matt Riedemann wrote:
>
>
> On 4/9/2015 3:14 PM, Kyle Mestery wrote:
> >The Neutron team is proud to announce the release of the latest version
> >of python-neutronclient. This release includes the following bug fixes
> >and improvements:
> >
> >aa1215a M
I'd say events are *more* useful in that workflow, not less, as long as
they contain enough context. For example, the user creates a volume, tries
to attach it which fails for some config error, so the user deletes it.
With an event based model, the admin now has an error event in their queue.
If w
Events shouldnt help much since the workflow is, user does something. It breaks
with "error notify admin" then admin needs to figure out why... ideally there
needs to be a field for why in the db, and the dashboard can show it to admins?
Thanks,
Kevin
From: Dunc
22 matches
Mail list logo
