Just check oslo messaging doc, don't know if it's out of date.
"Each notification listener is associated with an executor which controls how
incoming notification messages will be received and dispatched. By default, the
most simple executor is used - the blocking executor. This executor proces
Hi Novaers and Cinders:
Quite often application requirements would demand using locally attached
disks (or direct attached disks) for OpenStack compute instances. One such
example is running virtual hadoop clusters via OpenStack.
We can now achieve this by using BlockDeviceDriver as Cinder driver
> On 22 Sep 2016, at 17:16, Ryan Hallisey wrote:
>
> I agree with Michal and Martin. I was a little reluctant to respond here
> because the Debian additions are new, while Fedora has been around since the
> beginning and never got a ton of testing.
>
> Berendt what's your take here?
It is fin
On Thu, Sep 22, 2016 at 01:54:21PM -0500, Matt Riedemann wrote:
> Sergey is working on a spec to use the standardized virt driver instance
> diagnostics in the os-diagnostics API. A question came up during review of
> the spec about how to define a disk 'id':
>
> https://review.openstack.org/#/c/3
Minutes:
http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-09-23-07.59.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-09-23-07.59.txt
Log:
http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisyclou
-- Forwarded message --
From:
Date: Fri, Sep 23, 2016 at 11:50 AM
Subject: [neutron][lbaas][barbican] Listener create fails
To: [email protected]
You have to be a subscriber to post to this mailing list, so your
message has been automatically rejected. You can subscribe at:
On 2016/09/20 23:42, Matt Riedemann wrote:
On 9/20/2016 4:25 AM, Rikimaru Honjo wrote:
Hi All,
I requested to review my patch in the last Weekly Nova team meeting.[1]
In this meeting, Mr. Dan Smith said following things about my patch.
* This patch is too large to merge in rc2.[2]
* Fix after
2016-09-21 16:34 GMT+02:00 Steven Dake (stdake) :
>
>
>
> On 9/20/16, 11:18 AM, "Haïkel" wrote:
>
> 2016-09-19 19:40 GMT+02:00 Jeffrey Zhang :
> > Kolla core reviewer team,
> >
> > Kolla supports multiple Linux distros now, including
> >
> > * Ubuntu
> > * CentOS
>
On 22/09/16 20:55 +, Steven Dake (stdake) wrote:
Flavio,
Apologies for delay in response – my backlog is large.
Forgive me if I parsed your message incorrectly.
It's probably me failing to communicate my intent or just the intent not being
good enough or worth it at all.
It came across
On 22/09/16 10:49 -0500, Michał Jastrzębski wrote:
So issue is, I know of few other openstacks on k8s and everyone does
that slightly differently. So far we lack proof points and real world
data to determine best approaches to stuff. This is still not-to-well
researched field. Right now it's most
I agree that sometimes simply filtering for "security" can get a bit noisy
because only very occasionally is an email mentioning it or even using the
[security] tag actually trying to get the attention of the OSSP. Most of
the time (from my filters anyway) it's either a Neutron Security Groups
issu
Hi folks!
We've found out that we're not testing creating of config drives in our CI. It
ended up in one combination being actually broken (pxe_* + wholedisk +
configdrive). I would like to cover this testing gap. Is there any benefit in
NOT using config drives in all jobs? I assume we should
Dear all
The Massively Distributed Cloud Working Group [1] will meet on Thursday morning
during the next summit in Barcelona.
We have three slots. The current proposal is to discuss distributed
clouds/Fog/Edge use-cases and requirements during the two first ones and to use
the last one to defi
Hi horizoners,
As you may have noticed, the main fixes have been merged and the horizon
gate failure rate seems to be recovered.
There are still some remaining issues around the integration tests, but top
failure rate problems now have been fixed or have a workaround.
Thanks for your patience.
2
On 9/23/2016 3:54 AM, Daniel P. Berrange wrote:
On Thu, Sep 22, 2016 at 01:54:21PM -0500, Matt Riedemann wrote:
Sergey is working on a spec to use the standardized virt driver instance
diagnostics in the os-diagnostics API. A question came up during review of
the spec about how to define a disk
On Fri, Sep 23, 2016 at 07:32:36AM -0500, Matt Riedemann wrote:
> On 9/23/2016 3:54 AM, Daniel P. Berrange wrote:
> > On Thu, Sep 22, 2016 at 01:54:21PM -0500, Matt Riedemann wrote:
> > > Sergey is working on a spec to use the standardized virt driver instance
> > > diagnostics in the os-diagnostic
On 23/09/2016 3:19 AM, Zhai, Edwin wrote:
> "Each notification listener is associated with an executor which
> controls how incoming notification messages will be received and
> dispatched. By default, the most simple executor is used - the blocking
> executor. This executor processes inbound not
This makes sense to me. Another approach is here -
https://review.openstack.org/375467
Thanks,
Vlad
On Fri, Sep 23, 2016 at 2:37 PM, Dmitry Tantsur wrote:
> Hi folks!
>
> We've found out that we're not testing creating of config drives in our
> CI. It ended up in one combination being actually
On 23/09/2016 2:18 AM, Zhai, Edwin wrote:
>
> There are many targets(topics)/endpoints in above ceilometer code. But
> in AODH, we just have one topic, 'alarm.all', and one endpoint. If it is
> still multi-threaded, there is already potential race condition here,
> but event-alarm tiemout make i
On Thu, Sep 22, 2016, at 01:34 PM, Alexander Makarov wrote:
> Andrew,
>
> the idea is to shift existing RBAC implementation:
> currently policy is enforced in the service (Nova, for instance)
> against the result of token validation, which is, in general, an access
> check;
> I'm thinking about
Steven Dake (stdake) wrote:
> [...]
> The session we would like to return to the foundation is the *_Kolla
> Workroom Session Wednesday 3:05-3:45 session_*. We have no conflicts in
> this time slot and aren’t returning it as a result of some conflict in
> the core team’s schedule that I am aware o
[email protected] wrote:
> Also if you don't plan to use all of your
>> allocated slots, let us know so that we can propose them to other teams.
>>
> Just so that we are not forgotten (in case there is some space left),
> the storlets dev team would greatly appreciate 2fb and 2-3wr.
Would you be
Hi all,
A few weeks ago, there was a controversy in which a patch had been
-2'd until other concerns were resolved and then the core who used
their -2 powers disappeared and could not lift it after those concerns
had been resolved. This lead to a situation where the -2'd patch was
abandoned and th
The next meeting of the Nova scheduler subteam will be on Monday, September 26
at 1400 UTC in #openstack-meeting-alt
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160926T14
The agenda is here: https://wiki.openstack.org/wiki/Meetings/NovaScheduler
Please add any issues you would
thanks Ian, this is great info.
Just a side question, do you have example for -Workflow , say in cases
when I'd +2ed but to keep a check on process and approve after the
freeze -W'ed it?
Nonetheless, I have been using the labels and owner/reviewer/project
field to good advantage so would like to
-Original Message-
From: Nikhil Komawar
Reply: Nikhil Komawar
Date: September 23, 2016 at 10:04:51
To: OpenStack Development Mailing List (not for usage questions)
Cc: Ian Cordasco
Subject: Re: [openstack-dev] [Glance] Cores using -2 votes
> thanks Ian, this is great info.
>
> J
Kevin,
This is functionality that has been requested in the past but has never
been implemented.
The best way to proceed would likely be to propose a blueprint/spec for
this and start working this through that.
-Jay
On 09/23/2016 02:51 AM, Zhenyu Zheng wrote:
Hi Novaers and Cinders:
Qui
On Thu, 2016-09-15 at 10:20 +0100, Steven Hardy wrote:
> Hi all,
>
> As we work to finish the last remaining tasks for Newton, it's a good
> time
> to look back over the cycle, and recognize the excellent work done by
> several new contributors.
>
> We've seen a different contributor pattern deve
Hello everyone,
The release candidates for trove and trove-dashboard for the end
of the Newton cycle is available! You can find the RC2 source code
tarballs at:
https://tarballs.openstack.org/trove/trove-6.0.0.0rc2.tar.gz
https://tarballs.openstack.org/trove-dashboard/trove-dashboard-7.0.0.0rc2.
Hi neutrinos,
The idea of this email is to summarize the effort that we're making during the
implemetation of Rolling upgrades in Neutron, as well as
sharing the upcoming changes.
Announcements
Neutron Newton RC1 has been created and this contains the following changes
related to
Yeah, would be very nice to have/reuse a place for highest level and
projects independent specs to outline key architecture decisions like
(WARN [tl;dr]: biased examples from a non existent prototype go below):
* Shared nothing for stateful DB/MQ components (this means no shared
storage for state
Flavio Percoco wrote:
Greetings,
I've recently started looking into the container technologies around
OpenStack.
More specifically, I've been looking into the tools that allow for
deploying
OpenStack on containers, which is what I'm the most interested in right
now as
part of the TripleO efforts
These queries might be a good addition to the Glance dashboard in
https://github.com/openstack/gerrit-dash-creator under the "Patches I -2'd"
section:
https://github.com/openstack/gerrit-dash-creator/blob/master/dashboards/glance.dash#L33
> -Original Message-
> From: Ian Cordasco [mailt
On Fri, Sep 23, 2016 at 3:42 PM, Ian Cordasco wrote:
> Hi all,
>
> A few weeks ago, there was a controversy in which a patch had been
> -2'd until other concerns were resolved and then the core who used
> their -2 powers disappeared and could not lift it after those concerns
> had been resolved. T
Thanks for starting the discussion Fabio.
> As someone that started looking into this topic just recently, I'd love to see
> our communities collaborate more wherever possible. For example, it'd be great
> to see us working on a reference architecture for deploying OpenStack on
> kubernetes, letti
-Original Message-
From: Bashmakov, Alexander
Reply: OpenStack Development Mailing List (not for usage questions)
Date: September 23, 2016 at 11:08:55
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Glance] Cores using -2 votes
> Thes
-Original Message-
From: Erno Kuvaja
Reply: OpenStack Development Mailing List (not for usage questions)
Date: September 23, 2016 at 11:33:46
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Glance] Cores using -2 votes
> Ok, as it's b
I empathize with you Erno. I think this is a case of sheer
mis-understanding and probably (I think) the mention of that instance /
situation in this email is only for referential purposes.
There are some critical deadlines one sub-set of people have to met and
there are other priorities other sub
Hi Stackers,
In Newton, we had a major goal of having Nova sending inventory and
allocation records from the nova-compute daemon to the new placement API
service over HTTP (i.e. not RPC). I'm happy to say we achieved this
goal. We had a stretch goal from the mid-cycle of implementing the
cust
I wanted to provide a quick update from Security.
We had our weekly IRC meeting yesterday, dhellman was kind enough to attend
to help broker some of the discussion. In advance of the meeting I prepared
a blog post where I tried to articulate my position and where I think
things need to go next [1]
Hi,
Continuing the topic on the need for integration style tests for Nova
(brought up earlier during the weekly meeting at #openstack-meeting, Sep
22). The proposal is for a project to hold integration tests that
includes low-level testing and runs against a devstack backend. I have
included more
Bogdan,
I recognize English isn’t your first language, so forgive me if I have
mis-parsed your message. I think the question you are asking is “Can we have
cooperation to standardize on how best to do OpenStack on Kubernetes”. We
tried an analog of that with Mirantis around Mesos, and that re
On 13:17 Sep 21, Rob C wrote:
> For my part, I missed the elections, that's my bad. I normally put a
> calendar item in for that issue. I don't think that my missing the election
> date should result in the group being treated in this way. Members of the
> TC have contacted me about unrelated thing
Adding the project to email subject.
Thanks
Prasanth Anbalagan
On Fri, 2016-09-23 at 12:56 -0400, Prasanth Anbalagan wrote:
> Hi,
>
> Continuing the topic on the need for integration style tests for Nova
> (brought up earlier during the weekly meeting at #openstack-meeting,
> Sep 22). The propos
Excerpts from Rob C's message of 2016-09-23 17:46:46 +0100:
> I wanted to provide a quick update from Security.
>
> We had our weekly IRC meeting yesterday, dhellman was kind enough to attend
> to help broker some of the discussion. In advance of the meeting I prepared
> a blog post where I tried
On 11:03 Sep 21, Doug Hellmann wrote:
>
> > On Sep 21, 2016, at 8:58 AM, Filip Pytloun
> > wrote:
> >
> > Hello,
> >
> > it's definately our bad that we missed elections in OpenStackSalt
> > project. Reason is similar to Rob's - we are active on different
> > channels (mostly IRC as we keep re
Just a reminder for any folks interested in oslo and the summit,
I'd be great to have any or or other ideas on:
https://etherpad.openstack.org/p/ocata-oslo-summit-planning
So just wanted to make sure people are aware of that URL/etherpad and
have been thinking about what to add to it (I have
Flavio,
Forgive the top post and lack of responding inline – I am dealing with lookout
2016 which apparently has a bug here [0].
Your question:
I can contribute to kolla-kubernetes all you want but that won't give me what I
asked for in my original email and I'm pretty sure there are opinions a
Since I've heard this a few times over the years (the ML is to hard to
read, to much volume, to hard to keep track, to hard/this or that and
so-on),
I thought it would make sense to start to document what folks that have
been able to keep track of the ML have been doing and perhaps we can
the
Not sure exactly what you mean, but in Cinder using the
InstanceLocalityFilter[1], you can schedule a volume to the same compute
node the instance is located. Is this what you need?
[1]
http://docs.openstack.org/developer/cinder/scheduler-filters.html#instancelocalityfilter
On Fri, Sep 23, 2016
On Fri, Sep 23, 2016 at 7:37 AM, Dmitry Tantsur wrote:
> Hi folks!
>
> We've found out that we're not testing creating of config drives in our CI.
> It ended up in one combination being actually broken (pxe_* + wholedisk +
> configdrive). I would like to cover this testing gap. Is there any benefi
On 09/23/2016 01:04 PM, Steven Dake (stdake) wrote:
I also fail to see how training the Fuel team with the choices Kolla
has made in implementation puts OpenStack first.
Sorry, could you elaborate on what exactly you mean above? What do you
mean by "training the Fuel team with the choices Koll
There's a bit of why documentation here (though somewhat dated now):
https://review.openstack.org/#/c/361186/
And here:
https://github.com/openstack/kolla-kubernetes/blob/master/specs/ansible-deployment.rst
But there is still a bunch of stuff that we're still figuring out via the
review process.
Jay apologies.
That was an overgeneralization. The fuel team was not part of the kolla-mesos
team to my knowledge. To my knowledge the kolla-mesos team has moved on to
kubernetes upstream work and isn’t all that involved in fuel work.
Cheers
-steve
From: Jay Pipes
Reply-To: "OpenStack Deve
We're going to need to cut rc-2 for Glance to accommodate some new
translations, so there is an opportunity to include some conservative
bugfixes. Any such must be merged before 16:00 UTC on Wed 28 Sept, so I
am setting a deadline of 12:00 UTC on Tue 27 Sept for approval. If you
have a bugfix tha
Excerpts from Joshua Harlow's message of 2016-09-23 11:03:24 -0700:
> Since I've heard this a few times over the years (the ML is to hard to
> read, to much volume, to hard to keep track, to hard/this or that and
> so-on),
>
> I thought it would make sense to start to document what folks that ha
On 08/11/2016 06:25 AM, Steven Hardy wrote:
On Wed, Aug 10, 2016 at 11:31:29AM -0400, Zane Bitter wrote:
On 09/08/16 21:21, Adam Young wrote:
On 08/09/2016 06:00 PM, Zane Bitter wrote:
In either case a good mechanism might be to use a Heat Software
Deployment via the Heat API directly (i.e. no
Le 23/09/2016 18:41, Jay Pipes a écrit :
Hi Stackers,
In Newton, we had a major goal of having Nova sending inventory and
allocation records from the nova-compute daemon to the new placement
API service over HTTP (i.e. not RPC). I'm happy to say we achieved
this goal. We had a stretch goal
https://bugs.launchpad.net/glance/+bug/1620833
Would be my suggestion for a conservative / quick-hit / high impact bug to
consider for inclusion. Especially since this cycle is when the
documentation for using db.simple was added, it seems like it¹d be nice if
this were also fixed.
Tim
On 9/2
This seems to also be a connection issue to Firefox, but just in a
different place:
http://logs.openstack.org/69/375669/1/check/gate-horizon-dsvm-integration-deprecated-ubuntu-xenial/468d333/console.html#_2016-09-23_19_38_05_221999
Richard
On 23 September 2016 at 22:18, Akihiro Motoki wro
Earlier this month there was a thread on replacing stud in devstack for
the tls-proxy service [0]. Over the last week or so a bunch of work has
happened around this so I figured I would send an update.
Tempest passes against devstack with some edits to one of the object
tests to properly handle 30
On 22 September 2016 at 22:36, Takashi Yamamoto
wrote:
> hi,
>
> On Fri, Sep 23, 2016 at 4:20 AM, Armando M. wrote:
> >
> >
> > On 22 September 2016 at 00:46, reedip banerjee
> wrote:
> >>
> >> Dear Neutron Core members,
> >>
> >> I have a query regarding the procedure for inclusion in the Neut
Added some more object patches for reviews
> -Original Message-
> From: Morales, Victor [mailto:[email protected]]
> Sent: Friday, September 23, 2016 8:28 AM
> To: [email protected]
> Subject: [openstack-dev] [neutron][upgrades] Bi-weekly upgrades work status.
> 9/1
+1! The security project adds tremendous value to OpenStack.
Regards
-steve
From: Doug Hellmann
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Friday, September 23, 2016 at 10:35 AM
To: openstack-dev
Subject: Re: [openstack-dev] [security] [salt] Removal of S
Hi,
Thanks all for the information, as for the filter Erlon(
InstanceLocalityFilter) mentioned, this only solves a part of the problem,
we can create new volumes for existing instances using this filter and then
attach to it, but the root volume still cannot
be guranteed to be on the same host as
2016-09-24 5:07 GMT+08:00 Sylvain Bauza :
>
>
> Le 23/09/2016 18:41, Jay Pipes a écrit :
>
>> Hi Stackers,
>>
>> In Newton, we had a major goal of having Nova sending inventory and
>> allocation records from the nova-compute daemon to the new placement API
>> service over HTTP (i.e. not RPC). I'm
Jay--
If this is a production install, it's very unlikely that the admin user's
password is "password". The neutron_lbaas.conf file will need to be
updated with the admin user's actual password, and the neutron services
daemon restarted.
Stephen
On Fri, Sep 23, 2016 at 2:29 AM, Jayanthi Jeyakum
67 matches
Mail list logo
