Hi everyone,
New release of cmd2 0.9.0 seems to break cliff and python-tackerclient.
The cmd2 library changed the way it handles parsing input commands. It now
uses a different library, which means the values passed to the commands are
no longer PyParsing objects and are instead Statement objects
Hello,
I'm trying to run ceilometer with panko publishers in pike release and when I
run the ceilometer-agent-notification I get a trace complaining about
NoSuchOptError, but without the actual parameter that is missing (see trace
below).
I have configured panko.conf with the following:
[dat
Hi Team,
Weekly meeting as usual starting UTC1400 at #openstack-cyborg
Initial agenda:
1. Rocky task assignment confirmation
2. os-acc discussion
--
Zhipeng (Howard) Huang
Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office
On 19/06/18 01:59, Alex Schultz wrote:
On Mon, Jun 18, 2018 at 9:13 AM, Lars Kellogg-Stedman wrote:
Hey folks,
I'm trying to patch puppet-keystone to support multi-valued
configuration options (like trusted_dashboard). I have a patch that
works, mostly, but I've run into a frustrating probl
On Tue, Jun 19, 2018 at 11:15 AM, 李健 wrote:
>> So, my question is, why does the network service not use the
>> python2-neutronclient to get the client like other core projects, but
>> instead uses another separate project(openstacksdk)?
> There were multiple reasons to not use neutron client lib
On Jun 19, 2018, at 12:48 PM, Chris Dent wrote:
>
> Many of the things that get written will start off wrong but the
> only way they have a chance of becoming right is if they are written
> in the first place.
This.
Too many people are afraid of doing anything that might turn out to be the
"wr
Hi Boden！
I am song, I have discussed with the ptl zhiyuan.
we all think it is not a simple work to finish this.
we will plan this as a bp, but maybe can not finished it
in the R release, we promise must be finish it in the next openstack version.
At 2018-06-19 10:13:47, "linghucong
Could someone from the Neutron release group rebase feature/graphql
branch against master/HEAD branch please?
Regards,
Gilles
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
I'd like to help it. : )
Regards,
Yikun
Jiang Yikun（Kero）
Mail: yikunk...@gmail.com
Matt Riedemann 于2018年6月20日周三 上午1:07写道：
> On 6/18/2018 10:10 AM, Balázs Gibizer wrote:
> > * Introduce instance.lock and instance.unlock notifications
> >
> https://bluep
On Tue, Jun 19, 2018 at 1:45 PM, Wesley Hayutin wrote:
> Check and gate jobs look clear.
> More details on a bit.
>
So for a recap of the last 24 hours or so...
Mistral auth problems - https://bugs.launchpad.net/tripleo/+bug/1777541
- caused by https://review.openstack.org/#/c/574878/
- fixed
On 06/19/2018 01:59 PM, Artom Lifshitz wrote:
Adding
claims support later on wouldn't change any on-the-wire messaging, it would
just make things work more robustly.
I'm not even sure about that. Assuming [1] has at least the right
idea, it looks like it's an either-or kind of thing: either we
On 06/19/2018 03:51 PM, Dean Troyer wrote:
On Tue, Jun 19, 2018 at 11:15 AM, 李健 wrote:
So, my question is, why does the network service not use the
python2-neutronclient to get the client like other core projects, but
instead uses another separate project(openstacksdk)?
There were multiple re
Hi there,
For people who maybe still interested in this issue. I have proposed a
patch, see https://review.openstack.org/576029 And I have verified with
Sonobuoy for both multi masters (3 master nodes) and single master
clusters, all worked. Any comments will be appreciated. Thanks.
On 21/05/18
On Tue, Jun 19, 2018 at 11:15 AM, 李健 wrote:
> So, my question is, why does the network service not use the
> python2-neutronclient to get the client like other core projects, but
> instead uses another separate project(openstacksdk)?
There were multiple reasons to not use neutron client lib for O
All (but especially out-of-tree compute driver maintainers)-
ComputeDriver.get_traits() was introduced mere months ago [1] for
initial implementation by Ironic [2] mainly because the whole
update_provider_tree framework [3] wasn't fully baked yet. Now that
update_provider_tree is a thing,
> Adding
> claims support later on wouldn't change any on-the-wire messaging, it would
> just make things work more robustly.
I'm not even sure about that. Assuming [1] has at least the right
idea, it looks like it's an either-or kind of thing: either we use
resource tracker claims and get the new
Check and gate jobs look clear.
More details on a bit.
Thanks
Sent from my mobile
On Tue, Jun 19, 2018, 07:33 Felix Enrique Llorente Pastora <
ellor...@redhat.com> wrote:
> Hi,
>
>We have the following bugs with fixes that need to land to unblock
> check/gate jobs:
>
>https://bugs.launc
Excerpts from Chris Dent's message of 2018-06-19 20:06:15 +0100:
>
> Every now and again I keep working on my experiments to containerize
> placement in a useful way [1]. At the moment I have it down to using
> a very small oslo_config-style conf file. I'd like to take it the
> rest of the way and
Every now and again I keep working on my experiments to containerize
placement in a useful way [1]. At the moment I have it down to using
a very small oslo_config-style conf file. I'd like to take it the
rest of the way and have no file at all so that my container can be
an immutable black box th
Hi all,
Keystone recently took a big step in implementing the default roles work
that's been a hot topic over the past year [0][1][2][3][4], and a big
piece in making RBAC more robust across OpenStack. We merged a patch [5]
that ensures the roles described in the specification [6] exist. This
was
HTML: https://anticdent.org/tc-report-18-25.html
Over the time that I've been observing the TC, there's been quite a
lot of indecision about how and when to exercise power. The rules
and regulations of OpenStack governance have it that the TC has
pretty broad powers in terms of allowing and disa
On 6/18/2018 10:10 AM, Balázs Gibizer wrote:
* Introduce instance.lock and instance.unlock notifications
https://blueprints.launchpad.net/nova/+spec/trigger-notifications-when-lock-unlock-instances
This hasn't been updated in quite awhile. I wonder if someone else wants
to pick that up now?
On 18/06/18 13:39, Jay Pipes wrote:
+openstack-dev since I believe this is an issue with the Heat source code.
On 06/18/2018 11:19 AM, Spyros Trigazis wrote:
Hello list,
I'm hitting quite easily this [1] exception with heat. The db server
is configured to have 1000
max_connnections and 1000 m
Hi,
No. Not right. Idea is to unify CLI for all projects inside of the
python-openstackclient and obsolete all individual python-XXXclients. This
can be achieved by using the openstacksdk. Network module was just first in
the row, where the progress stucked a bit.
Regards,
On Tue, Jun 19, 2018
Hello everyone
---
CentOS Linux release 7.3.1611
OpenStack Version: Newton
# rpm -qa | egrep "(openstacksdk|openstackclient)"
python-openstackclient-3.2.1-1.el7.noarch
python2-openstacksdk-0.9.5-1.el7.noarch
The openstack CLI is implemented by python-openstackclient.
I
On Tue, Jun 19, 2018 at 9:17 AM, Jiří Stránský wrote:
> On 19.6.2018 16:29, Lars Kellogg-Stedman wrote:
>>
>> On Tue, Jun 19, 2018 at 02:18:38PM +0100, Steven Hardy wrote:
>>>
>>> Is this the same issue Carlos is trying to fix via
>>> https://review.openstack.org/#/c/494517/ ?
>>
>>
>> That solves
On 19.6.2018 16:29, Lars Kellogg-Stedman wrote:
On Tue, Jun 19, 2018 at 02:18:38PM +0100, Steven Hardy wrote:
Is this the same issue Carlos is trying to fix via
https://review.openstack.org/#/c/494517/ ?
That solves part of the problem, but it's not a complete solution.
In particular, it doesn
On Wed, Jun 13, 2018 at 9:50 AM, Emilien Macchi wrote:
> Alan Bishop has been highly involved in the Storage backends integration in
> TripleO and Puppet modules, always here to update with new features, fix
> (nasty and untestable third-party backends) bugs and manage all the
> backports for stab
On Tue, Jun 19, 2018 at 02:18:38PM +0100, Steven Hardy wrote:
> Is this the same issue Carlos is trying to fix via
> https://review.openstack.org/#/c/494517/ ?
That solves part of the problem, but it's not a complete solution.
In particular, it doesn't solve the problem that bit me: if you're
chan
Hi,
We have the following bugs with fixes that need to land to unblock
check/gate jobs:
https://bugs.launchpad.net/tripleo/+bug/1777451
https://bugs.launchpad.net/tripleo/+bug/1777616
You can check them out at #tripleo ooolpbot.
Please stop workflowing temporally until they get m
Hi,
Last week I was on bug deputy and I basically forgot about it. So I went
through bugs from last week yesterday. Below is summary of those bugs:
Neutron-vpnaas bug:
* libreswan ipsec driver doesn't work with libreswan versions 3.23+ -
https://bugs.launchpad.net/neutron/+bug/1776840
CI rela
On Wed, Jun 13, 2018 at 4:50 PM, Emilien Macchi wrote:
> Alan Bishop has been highly involved in the Storage backends integration in
> TripleO and Puppet modules, always here to update with new features, fix
> (nasty and untestable third-party backends) bugs and manage all the
> backports for stab
On 19 June 2018 at 10:27, Renat Akhmerov wrote:
> Hi,
>
> I’d like to promote Vitalii Solodilov to the core team of Mistral. In my
> opinion, Vitalii is a very talented engineer who has been demonstrating it
> by providing very high quality code and reviews in the last 6-7 months.
> He’s one of
+1 well deserved!
Renat Akhmerov ezt írta (időpont: 2018. jún.
19., K, 11:28):
> Hi,
>
> I’d like to promote Vitalii Solodilov to the core team of Mistral. In my
> opinion, Vitalii is a very talented engineer who has been demonstrating it
> by providing very high quality code and reviews in the
Hi,
I’d like to promote Vitalii Solodilov to the core team of Mistral. In my
opinion, Vitalii is a very talented engineer who has been demonstrating it by
providing very high quality code and reviews in the last 6-7 months. He’s one
of the people who doesn’t hesitate taking responsibility for
Hello lists,
With heat's team help I figured it out. Thanks Jay for looking into it.
The issue is coming from [1], where the max_overflow is set to
executor_thread_pool_size if it is set to a lower value to address
another issue. In my case, I had a lot of RAM and CPU so I could
push for threads
Hello,
Thanks Alex, I should probably improve my search-fu.
Is that commit in the RPM packages then I assume, so we need to ship a
metrics.yaml (which is kind of opinionated unless CloudKitty supplies a
default one) and set the fetcher in the config file.
Perhaps somebody can confirm the above
Thanks for response.
We will go with options 2 which is to cancel the meeting and continue on nova
channel. We will start API office hour on every Wednesday (27th June onwards)
06:00 UTC on #openstack-nova channel.
I pushed the patch to free the current slot of API meeting[1] and will update
38 matches
Mail list logo
