Hi!
This is the weekly summary of Technical Committee initiatives. You can
find the full list of all open topics (updated twice a week) at:
https://wiki.openstack.org/wiki/Technical_Committee_Tracker
If you are working on something (or plan to work on something) that is
not on the tracker, feel
Dims,
This was just a fella in the kolla community experimenting without attempting
to cause harm. IOW he didn’t know exactly what he was doing which is helpful
when messing with the meeting bots (.
No harm done anyway, so no need to take any corrective action in implementation.
Cheers
Hi Idan Kinory,
I deploy Vitrage with devstack using master branch.
Currently I found a error in Aodh datasource when I change the Aodh alarm
state(alarm_state_transition notification).
The error log is as follows:
Oct 27 07:30:50 dwj-vitrage vitrage-collector[9880]: 2017-10-27
Hello,
(Can I still use this thread?)
Excuse me, I'm trying to run Zuul v3 in my environment, and I have three
question about it.
I'd appreciate it if anyone helps.
My environment)
I use feature/zuulv3 branch, and version is 2.5.3.dev1374.
Q1)
"Unknown option --die-with-parent" error was
On Fri, Oct 27, 2017 at 12:19 AM, Jay Pipes wrote:
> On 10/25/2017 12:55 PM, Mathieu Gagné wrote:
>
>> Hi,
>>
>> On Wed, Oct 25, 2017 at 10:17 AM, Loo, Ruby wrote:
>>
>>> Hello ironic'ers,
>>>
>>> A while ago, we approved a spec to add node tag support to
Hello,
py35 unit tests of masakari are failed by same errors on gerrit.
e.g.
* https://review.openstack.org/#/c/441796/
=>http://logs.openstack.org/96/441796/3/check/openstack-tox-py35/d958f3f/testr_results.html.gz
* https://review.openstack.org/#/c/509782/
Hello,
I test ceilometer agent notification workload partition. I found it is too
fragile.
The load is 1k cirrors vm. I make processing queue to 4 and workers to 1.
I can sure the network is ok. But in the ceilometer agent notification log
i see this
On Wed, Oct 25, 2017 at 3:07 PM, Dmitry Tantsur wrote:
> Hi!
>
> Thanks for raising this.
>
> On 10/19/2017 01:11 PM, Vladyslav Drok wrote:
>
>> Hi!
>>
>> I'd like to discuss the usage of the new noauth plugin to keystoneauth,
>> which was introduced in [1]. The docstring of
Update 40 will be the last one before a short gap unless someone else
wants to fill the gap. Next week I'll be travelling to Sydney. The
week after that I'll be taking a break in Sydney after the summit. The
week after that I'll be lost in a fog of jetlag and travel fatigue.
So, the next one of
Hi everyone,
Once upon a time we only had one governance construct to recognize
activity in OpenStack, and that was the upstream project teams. As a
result, we created teams for everything.
However with the introduction of SIGs, we have a new construct for
activities that are not mainly about
On Tue, 17 Oct 2017 17:27:10 +0200
Petr Kovar wrote:
> Thanks for your feedback, everybody. I made some more edits to the
> document and tried to address the remaining comments left in the etherpad.
>
> I think the current revision of the doc provides enough details on
> the
Thanks for voting, everybody. There is a strong preference to move the
meeting time to 16:00 UTC Mon or Wed, which seems to work for everybody
who voted.
http://whenisgood.net/qtqbz52/results/ptgfrap
Let's have our next week's docs meeting on Wednesday, 1st November, 16:00
UTC and see how that
On Fri, Oct 27, 2017 at 6:08 PM, Jeremy Stanley wrote:
> On 2017-10-27 15:30:34 +0200 (+0200), Thierry Carrez wrote:
> [...]
> > I think the Security project team would benefit from becoming a
> > proper SIG.
> [...]
>
> I tend to agree, though it's worth also considering what
On 2017-10-27 14:26:06 -0400 (-0400), Mohammed Naser wrote:
[...]
> in our experience, malicious VMs are not short lived but they are
> long lived. We'll generally find them running before we received
> the report which means that the abuse report came for that user
> indeed.
[...]
I guess the
On Fri, Oct 27, 2017 at 12:48 PM, Jeremy Stanley wrote:
> On 2017-10-26 22:26:59 -0400 (-0400), Mohammed Naser wrote:
> [...]
> > The use-case for us is that it helps us easily identify or find VMs which
> > we get any abuse reports for (or anything we see malicious traffic
Hello All ,
I found some blueprint about supporting Docker Swarm Mode
https://blueprints.launchpad.net/magnum/+spec/swarm-mode-support
I understood that related development is not over yet and no any Openstack
version or Magnum version to test it also looks like some more thing to do.
On 10/26/2017 10:56 PM, Joshua Harlow wrote:
Just the paranoid person in me, but is it safe to say that the filter
that you are showing here does not come from user text?
Ie these two lines don't come from a user input directly (without going
through some filter) do they?
Hi folks!
We plan to add a new no-OS option [1] for users who wants to run a
proprietary, externally licensed, or customized operating system on a bare
metal server.
A bare metal server with no operating system can be set up to boot and load
the OS from a PXE setup. For this to work properly,
Hi,
I'd like to draw your attention to some things that we're changing in
Zuul v3 that affect stable branches.
We found a couple of interrelated issues where Zuul's behavior did not
match our expectations, and we also had some incorrect advice in the
migration doc.
We're rolling out a new
Hi all,
As you may or may not have noticed all ovb jobs on rh1 started failing
sometime last night. After some investigation today I found a few issues.
First, our nova db archiving wasn't working. This was due to the
auto-increment counter issue described by melwitt in
Hey all,
Here is the recap of what we worked on during office hours [0] this week:
Bug #1726736 in OpenStack Identity (keystone): ""no auth token" debug
logs are confusing"
https://bugs.launchpad.net/keystone/+bug/1726736
discussed, proposed fix, reviewed, and merged
Outside of that, we spent
21 matches
Mail list logo