On Tue, Apr 29, 2014 at 12:23 PM, Dan Smith d...@danplanet.com wrote:
Yeah, we've already got plans in place to get Cinder to use the
interface to provide us more detailed information and eliminate some
polling. We also have a very purpose-built notification scheme between
nova and cinder
Hi all!
I can attend, but since is the recomended 'Off Week'
(https://wiki.openstack.org/wiki/Icehouse_Release_Schedule) (Yeah. It's
weird a week start on Thursday) we could skip it.
Ghe Rivero
On 05/01/2014 04:07 PM, Matt Wagner wrote:
On 30/04/14 15:37 -0700, Devananda van der Veen wrote:
Hi Neutron advanced service folks,
As you may have noticed, there is a session slot for virtual resource
for service chaining. Please check the following etherpad.
https://etherpad.openstack.org/p/juno-virtual-resource-for-service-chaining
I'd like to have some preliminary discussion on the
At Thu, 24 Apr 2014 15:24:53 +0900,
IWAMOTO Toshihiro wrote:
At Thu, 24 Apr 2014 00:34:36 +0200,
ZZelle wrote:
[1 multipart/alternative (7bit)]
[1.1 text/plain; ISO-8859-1 (7bit)]
Hi Carl,
A clear l3 agent manager interface with hookable methods would clearly
simplify the
Dear all
Hi my name is Saki Iwata
I'm working on this bug fix.
https://bugs.launchpad.net/nova/+bug/1239952
https://review.openstack.org/#/c/86213/
This patch change response code from 400 to 503.
This patch got many reviewed but we can't make a decision.
To put it simply, which code (500 or
So taking a moment to look at ...
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
500 is a general fault... implying something bad happened and we don't
know how to handle it
503 is a fault implying that the responding server has a problem ...
close but not quite what's happening ...
Thanks for the exception explanation - now I understand better what is going on
there. Yuriy’s mention about looking in .testrepository gave me the needed
piece on how to find out where the failure occurred.
Regards,
PCM (Paul Michali)
MAIL …..…. p...@cisco.com
IRC ……..… pcm_
It was in init code for a device driver, which (currently, as a short term PoC
solution) reads a config file for settings of statically configured VPN
devices. If there are no devices at all, it will report the issue and the agent
will exit. In the future, will be dynamically obtaining the
On May 1, 2014, at 1:23 PM, Yuriy Taraday yorik@gmail.com wrote:
Coming back to topic, I'd prefer using standard library call because it can
be mocked for testing.
Yeah that’s probably the open question I still have. Does the community prefer
raising a SystemError exception or use the
Some non insignificant number of devstack changes related to neutron
seem to be neutron plugins having to do all kinds of manipulation of
extra config files. The grenade upgrade issue in neutron was because of
some placement change on config files. Neutron seems to have *a ton* of
config files and
I think that associating a VIP subnet and list of member subnets is a good
choice.
This is declaratively saying to where is the configuration expecting layer 2
proximity.
The minimal would be the VIP subnet which in essence means the VIP and members
are expected on the same subnet.
Any member
Adam, you are correct to show why order matters in policies.
It is a good point to consider AND between rules.
If you really want to OR rules you can use different policies.
Stephen, the need for order contradicts using content modification with the
same API since for modification you would
Agree with Sam here,
Moreover, i think it makes sense to leave subnet an attribute of the pool.
Which would mean that members reside in that subnet or are available
(routable) from this subnet, and LB should have a port on this subnet.
Thanks,
Eugene.
On Fri, May 2, 2014 at 3:51 PM, Samuel
On Fri, May 2, 2014 at 6:39 AM, Sean Dague s...@dague.net wrote:
Some non insignificant number of devstack changes related to neutron
seem to be neutron plugins having to do all kinds of manipulation of
extra config files. The grenade upgrade issue in neutron was because of
some placement
On 04/07/2014 12:06 PM, Nathan Kinder wrote:
Hi,
We don't currently collect high-level security related information about
the projects for OpenStack releases. Things like the crypto algorithms
that are used or how we handle sensitive data aren't documented anywhere
that I could see. I did
This topic has already been discussed last year and a use-case was described
(see [1]).
Here's a Heat blueprint for a new OS::Nova::Flavor resource: [2].
Several issues have been brought up after posting my implementation for review
[3], all related to how flavors are defined/implemented in
WSME 0.6.1 was tagged and uploaded to PyPI a few minutes ago. It
should appear in our CI mirror soon.
What's New In This Release?
* Fix error: variable 'kw' referenced before assignment
* Fix default handling for zero values
* Fixing spelling mistakes
* A proper check of
On Wed, Apr 30, 2014 at 06:10:20PM EDT, Martinx - ジェームズ wrote:
Since IPv6 is all public, don't you think that we (might) need a new
blueprint for IPv6-Only, like just dns-resolution?
Yes - I think IPv6 only Neutron is at least one separate blueprint,
possibly more. Robert Li is currently
On Thu, May 1, 2014 at 6:11 PM, Ben Nemec openst...@nemebean.com wrote:
On 04/29/2014 02:48 PM, Doug Hellmann wrote:
I have exported the gettextutils code and related files to a new git
repository, ready to be imported as oslo.i18n. Please take a few
minutes to look over the files and give it
On May 2, 2014, at 7:39 AM, Sean Dague s...@dague.net wrote:
Some non insignificant number of devstack changes related to neutron
seem to be neutron plugins having to do all kinds of manipulation of
extra config files. The grenade upgrade issue in neutron was because of
some placement change
-Original Message-
From: John Dennis [mailto:jden...@redhat.com]
Sent: 02 May 2014 14:23
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Security audit of OpenStack projects
On 04/07/2014 12:06 PM, Nathan Kinder wrote:
Hi,
We
On Thu, May 1, 2014 at 6:33 PM, Ben Nemec openst...@nemebean.com wrote:
On 04/09/2014 11:11 AM, Doug Hellmann wrote:
I have started writing up some general steps for adding oslo libs to
projects, and I would like some feedback about the results. They can't
go into too much detail about
It seems to me that there are two aspects being discussed in this thread:
style and practicality.
From a style perspective, it is important to give a uniform experience to
Neutron API users.
Obviously this does not mean the Load Balancing API must adhere to some
strict criteria.
For instance, 2nd
As Robert said, libraries should not be calling sys.exit() or raising
SystemExit directly, ever.
Throwing SystemExit from a library bypasses other exception handling
cleanup code higher in the stack that is unlikely to be looking for
fatal exceptions like SystemExit (because well-behaved
On Thu, 2014-05-01 at 17:17 -0400, Alexandre Viau wrote:
Hello Everyone!
My name is Alexandre Viau from Savoir-Faire Linux.
We have submited a Monitoring as a Service blueprint and need feedback.
Problem to solve: Ceilometer's purpose is to track and *measure/meter* usage
information
+1
And since most of the monitoring systems have standardized on supporting Nagios
plug ins, it would be great if it supported them too.
Thanks,
Kevin
From: Alexandre Viau [alexandre.v...@savoirfairelinux.com]
Sent: Thursday, May 01, 2014 2:17 PM
To:
Here are the calls in Neutron:
neutron/agent/l3_agent.py:raise SystemExit(msg)
neutron/agent/l3_agent.py:raise SystemExit(msg)
neutron/agent/l3_agent.py:raise SystemExit(msg)
neutron/agent/linux/dhcp.py:raise SystemExit(msg)
I need to rearrange a few sessions in the Oslo track to accommodate
Mark's schedule on Friday. I've tried to anticipate any conflicts
while making as few changes as possible, but please let me know if
your new slot conflicts with something else you need to attend and I
will try to work with you.
Hello!
I have moved the blueprint to ceilometer.
It is now available here:
https://blueprints.launchpad.net/ceilometer/+spec/monitoring-as-a-service
We have also created an Etherpad. Feel free to come contribute:
https://etherpad.openstack.org/p/MaaS
And since most of the monitoring systems
If you are leading a session in the Oslo track, please add a link to
the ether pad you have created with notes to the list at
https://wiki.openstack.org/wiki/Summit/Juno/Etherpads#Oslo
Thanks!
Doug
___
OpenStack-dev mailing list
My guess is the rootwrap and oslo service stuff is OK, the daemon
module may be OK, but all of the plugins should be changed. That's
just a guess after a cursory review, though, and someone who knows the
neutron code better than I do will have to make the call. Some of
those plugin modules may
Hi Rob,
We quickly discussed your ephemeral CA idea this morning and like it. We also
realize that it will take a lot of work to make it happen. At this point in
time we are attempting to simply add some form of SSL to a cloud installed with
TripleO. We lost all of our previous installation
FYI to any Nova people who are leading and/or planning on attending summit
sessions in Atlanta, while creating an etherpad for the libvirt session, I
also took the time out to create link to etherpads for all of the Nova
summit sessions. You can find them linked from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1 for making single config the norm
I think it's not just devstack/grenade that would benefit from this.
Variance in the plugin configuration patterns is a fairly common
complaint I hear from folks deploying OpenStack, and going to a single
config
TL;DR
Work is happening on a unified client library. This provides the
opportunity to rework the way SSL options are handled. Can we discuss
this in one of the sessions at the Atlanta Summit in a few weeks?
https://blueprints.launchpad.net/oslo/+spec/common-client-library-2
outlines a path
An easy way to get started identifying accessibility problems is to test
using the keyboard. I've made a small update to the wiki describing what
to do: https://wiki.openstack.org/wiki/Horizon/WebAccessibility
I've open our first accessibility bug, and it's related to keyboard
testing:
On 05/02/2014 03:06 PM, Rob Crittenden wrote:
TL;DR
Work is happening on a unified client library. This provides the
opportunity to rework the way SSL options are handled. Can we discuss
this in one of the sessions at the Atlanta Summit in a few weeks?
Good survey, thanks.
Ken'ichi, thanks for the detail. I just added that summit session to my
list to attend. I'm looking forward to it.
On Thu, May 1, 2014 at 12:34 AM, Ken'ichi Ohmichi ken1ohmi...@gmail.comwrote:
Hi,
2014-04-29 10:28 GMT+09:00 Matthew Farina m...@mattfarina.com:
*3. Where would JSON
On Fri, May 2, 2014 at 2:14 PM, Adam Young ayo...@redhat.com wrote:
Did swift leave this behind when they switched to Requests?
Swift and Glance clients were not changed to requests when I did the
initial work in the fall of 2012 due to their use of chunked transfers.
I've not really looked
On Fri, May 2, 2014 at 2:06 PM, Rob Crittenden rcrit...@redhat.com wrote:
I'm trying to get devstack to the point where it can configure all the
services with SSL so it can be be part of the acceptance process. This is
for client communication, there is no expectation that anyone would deploy
Problem to solve: Ceilometer's purpose is to track and *measure/
meter* usage information collected from OpenStack components
(originally for billing). While Ceilometer is usefull for the cloud
operators and infrastructure metering, it is not a *monitoring*
solution for the tenants and
Dean Troyer wrote:
On Fri, May 2, 2014 at 2:14 PM, Adam Young ayo...@redhat.com
mailto:ayo...@redhat.com wrote:
Did swift leave this behind when they switched to Requests?
Swift and Glance clients were not changed to requests when I did the
initial work in the fall of 2012 due to their
Hi,
I've submitted a patch (https://review.openstack.org/#/c/91663/) that updates
Nova to use the latest version
of websockify. It would appear that the CI now pulls websockify from
pypi.openstack.org, which appears not to
have websockify 0.6 on it yet. What is the process for getting
Dean Troyer wrote:
On Fri, May 2, 2014 at 2:06 PM, Rob Crittenden rcrit...@redhat.com
mailto:rcrit...@redhat.com wrote:
I'm trying to get devstack to the point where it can configure all
the services with SSL so it can be be part of the acceptance
process. This is for client
Hi all,
At Yahoo, load balancing is heavily used throughout our stack for both HA and
load distribution, even within the OpenStack control plane itself. This
involves a
variety of technologies, depending on scale and other requirements. For large
scale + L7 we use Apache Traffic Server, while
On Fri, May 2, 2014 at 1:39 PM, Solly Ross sr...@redhat.com wrote:
Hi,
I've submitted a patch (https://review.openstack.org/#/c/91663/) that
updates Nova to use the latest version
of websockify. It would appear that the CI now pulls websockify from
pypi.openstack.org, which appears not to
Hi Adam,
My comments inline:
On Fri, May 2, 2014 at 1:33 AM, Adam Harwell adam.harw...@rackspace.comwrote:
I am sending this now to gauge interest and get feedback on what I see
as an impending necessity — updating the existing haproxy driver,
replacing it, or both.
I agree with Stephen's
Hi Adam and Samuel!
Thanks for the questions / comments! Reactions in-line:
On Thu, May 1, 2014 at 8:14 PM, Adam Harwell adam.harw...@rackspace.comwrote:
Stephen, the way I understood your API proposal, I thought you could
essentially combine L7Rules in an L7Policy, and have multiple
On Wed, 2014-04-30 at 10:20 -0700, Mike Perez wrote:
On 06:49 Wed 30 Apr , Zhangleiqiang (Trump) wrote:
Hi stackers:
I found when a instance status become error, I will see the detailed
fault info at times when I show the detail of Instance. And it is very
convenient for me
Thanks for the input Duncan.
The removal of the debug logs is really a separate issue. I was just
hoping to reduce the number of patches that would touch a large number
of files. As we are thinking through this though, it really is a
separate change so it is best to do separate patches.
On a
On Wed, Apr 30, 2014 at 11:30 PM, Ken'ichi Ohmichi ken1ohmi...@gmail.comwrote:
Hi,
After huge discussion related to v3 API[1], we started to implement v2.1
API.
I'd like to share the current status and get feedback before the summit.
Now we are implementing for two items:
1. Add response
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
Hi all,
(I'm resending this from home to avoid the DMARC-SPAM issue)
At Yahoo, load balancing is heavily used throughout our stack for both HA and
load distribution, even within the OpenStack control plane itself. This
involves a
variety of technologies, depending on scale and other
Hi guys,
Yep, so what I'm hearing is that we should be able to assume that either
all members in a single pool are adjacent (ie. layer-2 connected), or are
routable from that subnet.
Adam-- I could see it going either way with regard to how to communicate
with members: If the particular device
54 matches
Mail list logo
