On Jul 19, 2017 1:58 PM, "Jeremy Stanley" wrote:
On 2017-07-19 13:42:43 -0700 (-0700), Emilien Macchi wrote:
[...]
> We also want to remove #openstack-puppet. Not sure who created it
> but it causes confusion.
I don't see any evidence we ever logged it anyway:
On Jul 19, 2017 2:36 PM, "Antoine Cabot" wrote:
Hey guys,
It's been a long time since the last summit and our last discussions !
I hope Watcher is going well and you are getting more traction
everyday in the OpenStack community !
As you may guess, my last 2 months
Hi all,
This is a day late, but here is the summary for what we worked on during
office hours yesterday. The full log can be found below [0].
Bug #1689888 in OpenStack Identity (keystone): "/v3/users is
unproportionally slow"
https://bugs.launchpad.net/keystone/+bug/1689888
participants:
I was able to automate some of this report. I figured a follow up
containing data about what was worked on would be nice.
Bug #1703467 in OpenStack Identity (keystone): "assert_admin is checking
default policy rule not admin_required"
https://bugs.launchpad.net/keystone/+bug/1703467
On 07/19/2017 12:11 AM, Zane Bitter wrote:
On 17/07/17 23:12, Lance Bragstad wrote:
Would Keystone folks be happy to allow persistent credentials once
we have a way to hand out only the minimum required privileges?
If I'm understanding correctly, this would make application
On 07/19/2017 12:18 AM, Zane Bitter wrote:
On 18/07/17 10:55, Lance Bragstad wrote:
Would Keystone folks be happy to allow persistent credentials once
we have a way to hand out only the minimum required privileges?
If I'm understanding correctly, this would make application
ruby and Wan-Yan,
Thanks for your reply, I have already send the steps and logs to ilo
driver group
保密:本函仅供收件人使用,如阁下并非抬头标明的收件人,请您即刻删除本函,勿以任何方式使用及传播,并请您能将此误发情形通知发件人,谢谢!
__
OpenStack Development Mailing List (not for
On 7/19/2017 6:16 AM, Sean Dague wrote:
I was just starting to look through some logs to see if I could line up
request ids (part of global request id efforts), when I realized that in
the process to uwsgi by default, we've entirely lost the INFO wsgi
request logs. :(
Instead of the old format
Yeah, if one clearly belongs to a single vendor moving is definitely the
way to go.
OVS itself is a good example of one that is used by lots of drivers. Since
it's in os-vif maybe we should do the same for any others without a clear
association (e.g. vif_type='tap' is about as vendor agnostic as
On 7/19/2017 6:16 AM, Sean Dague wrote:
We hit a similar issue with placement, and added custom
paste middleware for that. Maybe we need to consider a similar thing
here, that would only emit if running under uwsgi/apache?
For example, this:
On 7/19/17, 1:11 PM, "Clark Boylan" wrote:
>On Tue, Jul 18, 2017, at 12:47 PM, Eric K wrote:
>> Hi all, looking for some hints/tips. Thanks so much in advance.
>>
>> My local python3 devstack setup [2] succeeds, but in check-job a
>> similarly
>> configured devstack
Thanks a lot Jeremy. I'm now running the reproduce.sh to see what happens.
> [3] Check-job devstack log:
>
>http://logs.openstack.org/49/484049/1/check/gate-congress-dsvm-py35-api-my
>sql-ubuntu-xenial-nv/7ae2814/logs/devstacklog.txt.gz
And oops, I linked to and older run of the check-job
Hey guys,
It's been a long time since the last summit and our last discussions !
I hope Watcher is going well and you are getting more traction
everyday in the OpenStack community !
As you may guess, my last 2 months have been very busy with my
relocation in Vancouver with my family. After 8
+1
On Wed, Jul 12, 2017 at 7:31 AM, Susanne Balle wrote:
> +1
>
> On Fri, Jun 30, 2017 at 4:31 AM, Hidekazu Nakamura
> wrote:
>>
>> +1
>>
>> > -Original Message-
>> > From: Чадин Александр (Alexander Chadin)
>> >
Hi Wangjun,
Can you provide more info?
What driver did you use?
What's your target_raid_config?
What do the logical drives look like after the configuration?
Any log, server and storage hardware and firmware version info you can
share?
You are welcome to contact
On 2017-07-19 13:42:43 -0700 (-0700), Emilien Macchi wrote:
[...]
> We also want to remove #openstack-puppet. Not sure who created it
> but it causes confusion.
I don't see any evidence we ever logged it anyway:
http://eavesdrop.openstack.org/irclogs/
So... er... done!
> The real one is
On Wed, Jul 19, 2017 at 12:24 PM, Jeremy Stanley wrote:
> For those who are unaware, Freenode doesn't allow any one user to
> /join more than 120 channels concurrently. This has become a
> challenge for some of the community's IRC bots in the past year,
> most recently the
Yeah I'd say stop logging it and we'll request being added back in should
we get going.
Amy(spotz)
On Wed, Jul 19, 2017 at 3:22 PM, Jeremy Stanley wrote:
> On 2017-07-19 15:15:51 -0500 (-0500), Amy Marrich wrote:
> > Sorry to see the Diversity channel go as we really need to
On 2017-07-19 15:15:51 -0500 (-0500), Amy Marrich wrote:
> Sorry to see the Diversity channel go as we really need to get the
> Working Group back up and running but it never was really high
> volume.
[...]
If you anticipate activity picking up soon in that channel we can
certainly keep logging
Sorry to see the Diversity channel go as we really need to get the Working
Group back up and running but it never was really high volume.
Amy(spotz)
On Wed, Jul 19, 2017 at 2:24 PM, Jeremy Stanley wrote:
> For those who are unaware, Freenode doesn't allow any one user to
>
Excerpts from Jeremy Stanley's message of 2017-07-19 19:24:00 +:
> For those who are unaware, Freenode doesn't allow any one user to
> /join more than 120 channels concurrently. This has become a
> challenge for some of the community's IRC bots in the past year,
> most recently the "openstack"
On Tue, Jul 18, 2017, at 12:47 PM, Eric K wrote:
> Hi all, looking for some hints/tips. Thanks so much in advance.
>
> My local python3 devstack setup [2] succeeds, but in check-job a
> similarly
> configured devstack setup [1] fails for not installing congress client.
>
>
For those who are unaware, Freenode doesn't allow any one user to
/join more than 120 channels concurrently. This has become a
challenge for some of the community's IRC bots in the past year,
most recently the "openstack" meetbot (which not only handles
meetings but also takes care of channel
On 07/18/2017 04:33 PM, Ravi, Goutham wrote:
Hello Manila reviewers,
It has been a few days past the feature proposal freeze, but I would
like to request an extension for an enhancement to the NetApp driver in
Manila. [1] implements a low-impact blueprint [2] that was approved for
the Pike
Welcome to the following new members of the manila-stable-maint team:
Goutham Pacha Ravi
Rodrigo Barbieri
Thomas Bechtold
Tom Barron
Valeriy Ponomaryov
Xing Yang
All of you are of course familiar with the stable-maint guidelines, and
have a good history of enforcing the rules. Please continue
On Wed, Jul 19, 2017 at 9:15 AM, Alex Schultz wrote:
>
>
> On Wed, Jul 19, 2017 at 9:58 AM, Ricardo Noriega De Soto <
> rnori...@redhat.com> wrote:
>
>> Thanks Gary for the opportunity! We'll keep fighting! :-)
>>
>>
> Congrats. Your efforts in the puppet openstack repos to
On 2017-07-18 12:47:07 -0700 (-0700), Eric K wrote:
> Hi all, looking for some hints/tips. Thanks so much in advance.
>
> My local python3 devstack setup [2] succeeds, but in check-job a similarly
> configured devstack setup [1] fails for not installing congress client.
>
>
On 07/18/2017 08:18 AM, Numan Siddique wrote:
On Thu, Jul 13, 2017 at 3:02 PM, Saravanan KR > wrote:
On Tue, Jul 11, 2017 at 11:40 PM, Ben Nemec > wrote:
>
>
> On
+1 Awesome work on the suse support, but also on improving the nuts
and bolts of our tests and everything else during that process.
On Tue, Jul 18, 2017 at 7:57 AM, Major Hayden wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 07/18/2017 04:23 AM, Andy McCrae
FYI, in kolla-kubernes, I've been playing with fluent-bit as a log shipper.
Works very similar to fluentd but is much lighter weight. I used this:
https://github.com/kubernetes/charts/tree/master/stable/fluent-bit
I fought with getting log rolling working properly with log files and its kind
On Wed, Jul 19, 2017 at 9:58 AM, Ricardo Noriega De Soto <
rnori...@redhat.com> wrote:
> Thanks Gary for the opportunity! We'll keep fighting! :-)
>
>
Congrats. Your efforts in the puppet openstack repos to also get this
properly supported and tested have also been very appreciated.
Thanks,
On 17 July 2017 at 15:56, Derek Higgins wrote:
> On 17 July 2017 at 15:37, Emilien Macchi wrote:
>> On Thu, Jul 13, 2017 at 6:01 AM, Emilien Macchi wrote:
>>> On Thu, Jul 13, 2017 at 1:55 AM, Derek Higgins wrote:
Thanks Gary for the opportunity! We'll keep fighting! :-)
On Wed, Jul 19, 2017 at 8:52 AM, Gary Kotton wrote:
> Hi,
>
> Over the last few months Ricardo Noriega has been making many
> contributions to the project and has actually helped get it to the stage
> where it’s a lot
On Wed, Jul 19, 2017 at 5:38 PM, McLellan, Steven
wrote:
Thanks Balazs for noticing and replying to my message!
The Status field is quite important to us since it's the indicator of
VM state that Horizon displays most prominently and the most simple
description of
Excerpts from Alexandra Settle's message of 2017-07-19 15:42:42 +:
> Hi everyone,
>
> As you all know, we have been changing the way the documentation team
> operates. Chief among those
> changes are reducing the workload on the shrinking team. The migration to
> move installation, admin,
Hi everyone,
As you all know, we have been changing the way the documentation team operates.
Chief among those
changes are reducing the workload on the shrinking team. The migration to move
installation, admin, and
configuration documentation to project-team repositories is the first phase of
Thanks Balazs for noticing and replying to my message!
The Status field is quite important to us since it's the indicator of VM state
that Horizon displays most prominently and the most simple description of
whether a VM is currently usable or not without having to parse the various
_state
Hi,
Steve asked the following question on IRC [1]
< sjmc7> hi gibi. sorry, meant to bring this up in the notifications
meeting but i had to step away for a bit. we were having a discussion
last week about the field that the API returns as 'status' - do the
notifications have an equivalent?
Hi, I suggest either providing more information so someone may be able to help
you here, or go onto irc, #openstack-ironic, and ask for help there.
--ruby
From: 王俊
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
On 07/07/2017 07:38 PM, Giulio Fidente wrote:
> On 07/04/2017 08:00 PM, Emilien Macchi wrote:
>> On Wed, Jun 28, 2017 at 9:37 PM, Giulio Fidente wrote:
>>> On 06/28/2017 04:35 PM, Emilien Macchi wrote:
Hey folks,
Let's start to prepare the next PTG in Denver.
Kind reminder for the team meeting, as NOW :)
Join us on #openstack-cyborg if you are bored of regular stuff :P
--
Zhipeng (Howard) Huang
Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang,
Hi everyone,
Django 1.11 support has landed for Django OpenStack Auth [1], which was
released shortly after [2]. Horizon's Django 1.11 support is just merging [3],
at which point we will raise the global requirement [4] and make the Horizon /
DOA tests voting [5].
At that point, we should be
On Wed, 19 Jul 2017, Balazs Gibizer wrote:
I added more info to the bug report and the review as it seems the test is
fluctuating.
(Reflecting some conversation gibi and I have had in IRC)
I've made a gabbi-based replication of the desired functionality. It
also flaps, with a >50% failure
On 07/18/2017 04:33 PM, Ravi, Goutham wrote:
> Hello Manila reviewers,
>
>
>
> It has been a few days past the feature proposal freeze, but I would
> like to request an extension for an enhancement to the NetApp driver in
> Manila. [1] implements a low-impact blueprint [2] that was approved
Hi all!
With the driver composition implemented in Ocata and polished in Pike, we would
like to eventually get rid of the old-style drivers. I believe the new hardware
types are much easier to understand, create and use.
We have landed a spec laying down the deprecation plan [1]. In essence,
Hi team!
As discussed on the IRC meeting, I would like to propose a soft feature freeze
for ironic, starting with Aug 1st. I hope this proposal will help us better
concentrate on the priorities and finally be able to finish most of the things
we've committed to.
Between this day and the
On Wed, Jul 19, 2017 at 1:13 PM, Chris Dent
wrote:
On Wed, 19 Jul 2017, Balazs Gibizer wrote:
We are trying to get some help from the related functional test [5]
but
honestly we still need some time to digest that LOCs. So any direct
help is appreciated.
I
On Wed, Jul 19, 2017 at 3:11 AM, Dnyaneshwar Pawar
wrote:
> Hi tripleo/rdo experts,
>
>
>
> puppet-veritas_hyperscale is added to RDO trunk via [1].
>
> Also patched tripleo-puppet-elements to include puppet-veirtas_hyperscale
> [2].
>
>
>
> When I create overcloud
I wanted to give a quick heads up on some breaking changes that started
landing last week with regards to how container images are specified
with Heat parameters in TripleO. There are a few patches associated
with converting over to the new changes but the primary patches are
listed below here [1]
(Blog version at https://anticdent.org/tc-report-29.html )
This TC Report is a bit late. Yesterday I was attacked by an oyster.
This week had no meeting, so what follows is a summary of various
other TC related (sometimes only vaguely related) activity.
# Vision
The [TC
Hi,
May I ask a question about RAID?I set target_raid_config before I set
the node state to ‘provide’, but when I make the node to available, the
server’s logical drive does not like my configures.I don’t know why.who can
give some help?
I was just starting to look through some logs to see if I could line up
request ids (part of global request id efforts), when I realized that in
the process to uwsgi by default, we've entirely lost the INFO wsgi
request logs. :(
Instead of the old format (which was coming out of oslo.service) we
On Wed, 19 Jul 2017, Balazs Gibizer wrote:
We are trying to get some help from the related functional test [5] but
honestly we still need some time to digest that LOCs. So any direct
help is appreciated.
I managed to create a functional test case that reproduces the above problem
Hi everyone,
Don't forget todays meeting for the PublicCloudWorkingGroup.
1400 UTC in IRC channel #openstack-meeting-3
Etherpad: https://etherpad.openstack.org/p/publiccloud-wg
Regards,
Tobias__
OpenStack Development
On Thu, 2017-07-13 at 07:54 -0600, Kevin Benton wrote:
> On Thu, Jul 13, 2017 at 7:26 AM, Stephen Finucane
wrote:
>
> > os-vif has been integrated into nova since the newton cycle. With the
> > integration of os-vif, the expectation is that all the old, non-os-vif
> >
You are right but adding [os-vif] lands it in my os-vif folder os
I guess [openstack-dev][os-vif][nova][neutron] 1.6.1 release for pike
Would have made it work for everyone :)
> -Original Message-
> From: Matt Riedemann [mailto:mriede...@gmail.com]
> Sent: Tuesday, July 18, 2017 10:35 PM
On Tue, Jul 18, 2017 at 2:39 PM, Balazs Gibizer
wrote:
On Mon, Jul 17, 2017 at 6:40 PM, Jay Pipes wrote:
> On 07/17/2017 11:31 AM, Balazs Gibizer wrote:
> > On Thu, Jul 13, 2017 at 11:37 AM, Chris Dent
>
> > wrote:
>
Hi tripleo/rdo experts,
puppet-veritas_hyperscale is added to RDO trunk via [1].
Also patched tripleo-puppet-elements to include puppet-veirtas_hyperscale [2].
When I create overcloud using quickstart.sh + latest RDO trunk,
puppet-veritas_hyperscale modules do not get installed on any of
On Tue, Jul 18, 2017 at 5:54 PM, Mooney, Sean K wrote:
> Should have:
>
> Improve OVS Representor Lookup https://review.openstack.org/#/c/484051/
I've split out the review into two portions, here is the second one:
Improve OVS Representor VF Lookup
On 17/07/17 14:05 +0200, Flavio Percoco wrote:
Thanks for all the feedback so far. This is one of the things I appreciate the
most about this community, Open conversations, honest feedback and will to
collaborate.
I'm top-posting to announce that we'll have a joint meeting with the Kolla team
Hey folks,
Based on the outcome of this thread, I've submitted this resolution to allow
teams to host meetings outside meeting channels. Please, comment and review :)
https://review.openstack.org/#/c/485117/
Flavio
On 26/06/17 10:37 +0200, Flavio Percoco wrote:
Hey Y'all,
Not so long ago
Hi,
Kolla-ansible went through this process a few years ago, and ended up with
a solution involving heka pulling logs from files in a shared docker volume
(kolla_logs). Heka was recently switched for fluentd due to the
disappearance of upstream support. I suspect kolla-kubernetes has been
through
On 18.07.2017 21:27, Lars Kellogg-Stedman wrote:
> Our current model for logging in a containerized deployment has pretty
> much everything logging to files in a directory that has been
> bind-mounted from the host. This has some advantages: primarily, it
> makes it easy for an operator on the
On 07/18/2017 11:22 PM, Emilien Macchi wrote:
> On Mon, Jul 17, 2017 at 12:10 PM, Emilien Macchi wrote:
>> Since we have mixed feelings but generally agree that we should give
>> it a try, let's give it a try and see how it goes, at least one time,
>> tomorrow.
> So we tried
Hi,
Over the last few months Ricardo Noriega has been making many contributions to
the project and has actually helped get it to the stage where it’s a lot
healthier than before ☺. I am adding him to the core team.
Congratulations!
A luta continua
Gary
Hi all,
In the process of making it possible to make external subnets visible via a
policy.json entry[1] I ran into a limitation of our DB pagination in
conjunction with the policy engine.
The queries to the DB do not take into account policy.json entries so users
may get fewer subnets than
66 matches
Mail list logo