Hi,
As many Vitrage developers will be on vacation next week, the IRC meeting on
April 12 will be SKIPPED.
We will meet again on April 19.
Thanks,
Ifat.
__
OpenStack Development Mailing List (not for usage questions)
Hello everyone,
Please reminder that the weekly OpenStack QA team IRC meeting will be
Thursday, April 6th at 9:00 UTC in the #openstack-meeting channel.
The agenda for the meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_April_6th_2017_.280900_UTC.29
Hi Jeremy,
I did ignore the impact of code review. Thank you for reminding.
Zoey Lin
> -原始邮件-
> 发件人: "Jeremy Stanley"
> 发送时间: 2017-04-05 22:00:28 (星期三)
> 收件人: "OpenStack Development Mailing List (not for usage questions)"
>
> 抄送:
For example, detail of the messages of topics.L3_AGENT
2017-04-06 9:38 GMT+08:00 Sam :
> Thank you all.
>
> For 'context', I got it.
> For RPCs, is there some document or blog or some debug method to get its
> detal contains in neutron L3 Agent?
>
> 2017-04-06 9:33
Thank you all.
For 'context', I got it.
For RPCs, is there some document or blog or some debug method to get its
detal contains in neutron L3 Agent?
2017-04-06 9:33 GMT+08:00 김기석 [Kiseok Kim] :
> Hi Sam,
>
>
>
> that 'context' is olso_context and neutron use it with
Hi Sam,
that 'context' is olso_context and neutron use it with addition attributes.
oslo.context has to_dict method,
so you could add debug log in 'agent_updated' method like:
LOG.debug("context in agent_updated: %s", context.to_dict())
and you can find out the attributes of context
On 4/5/2017 3:09 PM, Sean Dague wrote:
At the PTG clayg brought up an excellent question about what the
expected flow was to restart a bunch of services in devstack after a
code changes that impacts many of them (be it common code, or a
library). People had created a bunch of various screen
On Wed, Apr 5, 2017 at 4:49 PM, Emilien Macchi wrote:
> Greetings dear owls,
>
> I would like to bring back an old topic: running tempest in the gate.
>
> == Context
>
> Right now, TripleO gate is running something called pingtest to
> validate that the OpenStack cloud is
We are excited to announce the September Project Teams Gathering in Denver, CO
at the Denver Renaissance Stapleton Hotel this September 11th-15th.
As mentioned at the Atlanta PTG feedback session in February, we had narrowed
down our PTG location options to Denver and Montreal. Based on
Welcome!
And, of course, writing tests that demonstrate some of those more difficult
open bugs would help make sure they don't resurface once fixed ;-) so, if you
can't get a handle yet on the intricacies of the the code that contains the
issue, you still might be able to demonstrate the
We ended up cancelling today's policy meeting, but policy discussions
carried on throughout the day in #openstack-keystone [0]. We have several
specs up for review [1][2][3][4]. Some are nova specs and a couple are
proposed to keystone. With keystone's spec proposal freeze coming up next
week [5],
On Wed, Apr 5, 2017 at 1:30 PM, Andrea Frittoli
wrote:
>
>
> I just want to say thank you! to you clarkb clayg and everyone involved :)
> This is so much better!
>
> andreaf
>
>
Sean is throwing credit at me where none is due. IIRC I was both in the
room and in a
Greetings dear owls,
I would like to bring back an old topic: running tempest in the gate.
== Context
Right now, TripleO gate is running something called pingtest to
validate that the OpenStack cloud is working. It's an Heat stack, that
deploys a Nova server, some volumes, a glance image, a
On Wed, Apr 5, 2017 at 9:14 PM Sean Dague wrote:
> At the PTG clayg brought up an excellent question about what the
> expected flow was to restart a bunch of services in devstack after a
> code changes that impacts many of them (be it common code, or a
> library). People had
Hi,
As you might know, the TC introduced new tags [1] for upgrade processes
quite some time ago, which reflect the level of maturity of an upgrade.
Therefore there is the growing need of test tools which help to exercise
and validate the upgrade approaches defined by the community.
During the
At the PTG clayg brought up an excellent question about what the
expected flow was to restart a bunch of services in devstack after a
code changes that impacts many of them (be it common code, or a
library). People had created a bunch of various screen hacks over the
years, but screen is flakey,
The tone of this in inappropriate and not in keeping with our community
code of conduct:
https://www.openstack.org/legal/community-code-of-conduct/
It is neither friendly, patient, welcoming, considerate or respectful.
No attempt has been made to collaborate openly on a solution, or to
We deprecated a bunch of proxy APIs and CLIs with the 2.36 microversion
in the Newton release. We bent over backward to make the CLI fall back
to 2.35 if using a deprecated proxy in novaclient but that code is all
removed now, and will be gone in the upcoming novaclient 8.0.0 release [1].
[1]
Hi, I'm Chris Dent, cdent on IRC.
I'm once again nominating myself to be your representative on the
Technical Committee. I've been around OpenStack for about three
years, most recently visible as the guy who writes those weekly
updates about the placement API service and talks about the
API-WG.
I am Dean Troyer and would like to nominate myself as a candidate for
re-election to the Technical Committee.
I have been around OpenStack for a long time, primarily working on
DevStack, Grenade and OpenStackClient.
OpenStack has been going through the maturation process in the last
year or two
Hi,
I suggested to add few pci devices related attributes to ironic
inspection(out-of-band as well inband).
https://review.openstack.org/#/c/338138.
I got the suggestion to convert them to standard pci device format which
nova understands. For example( as given in Nova code):
[{"count": 5,
There's nothing to discuss on the agenda today so I'm canceling the meeting
for today.
-amrith
--
Amrith Kumar
amrith.ku...@gmail.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Clay,
So the moral of the story is to "pay attention to what's happening
around you"? or something else?
Thanks,
Dims
On Wed, Apr 5, 2017 at 12:55 PM, Clay Gerrard wrote:
> I hate this stuff.
>
> Not just pbr (tho I do have a long history of being kicked in the nuts by
I hate this stuff.
Not just pbr (tho I do have a long history of being kicked in the nuts by
pbr for no good reason I can ascertain). But when suddenly some process
OpenStack invented I've never *heard of in two years* breaks - and
overnight me and 100's of other folks have to stop what their
Looks like CNCF is setting up work groups around CNI and CSI, in case
anyone is interested
https://github.com/cncf/toc#working-groups
https://github.com/cncf/wg-storage/blob/master/README.md#members
https://github.com/cncf/wg-networking/blob/master/README.md#members
On 04/05/2017 05:46 AM, Thierry Carrez wrote:
> Hi everyone,
>
> Last year in Ann Arbor, a group of OpenStack community members
> (including 6 current TC members) attended a Servant Leadership training
> at ZingTrain organized by Colette Alexander and funded by the OpenStack
> Foundation. We
Hi Sam,
'context' is an object of neutron.context.Context which inherits
oslo_context.RequestContext.
When you see 'context' as a method signature like
router_added_to_agent(self, context, payload),
'context' is Context object.
oslo_messaging serializes the context object and sends to RPC
Hi,
Peng, thank you for looking into how we might be able to provide
translations for the THT content in TripleO UI! I think this would be
helpful for users, and we have a couple of translators interested in
helping as well.
On 23 March 2017 at 09:07, Thomas Herve wrote:
> On
I see Emilien proposed a number of patches to individual projects with
"Sem-Ver: api-break" in the commit message.
As far as I understand the pbr documentation [1] correctly (see the
forth paragraph in the section) which is pointed by Emilien,
the change looks reasonable.
Honestly it would be
On Tue, Apr 04, 2017 at 04:01:48PM -0400, Emilien Macchi wrote:
> After our weekly meeting of today, I found useful to share and discuss
> our roadmap for Container CI jobs in TripleO.
> They are ordered by priority from the highest to lowest:
>
> 1. Swap ovb-nonha job with ovb-containers, enable
On Thu, Mar 30, 2017 at 12:40 PM, Armando M. wrote:
> On 30 March 2017 at 08:47, Saverio Proto wrote:
>
>> Hello,
>>
>> I am trying to use the neutron l2gw plugin, but I am not using a bare
>> metal switch to bridge.
>>
>> I am using a server with
On 4/5/2017 9:00 AM, Jeremy Stanley wrote:
On 2017-04-05 14:00:59 +0800 (+0800), 林泽燕 wrote:
[...]
I wonder if I could show you my study, including some metrics for
the prediction model and a visualization tool.
[...]
I want to start out thanking you for your research and interest in
Hey Saharans and interested folks,
On the intent to move our API version to v2 there has been a lot of work
going on this cycle following
https://wiki.openstack.org/wiki/Sahara/api-v2 defined
a while back.
One of the new features defined on the document is the addition of
microversion support.
+1 from me, they've both been very helpful and have been doing good work :).
-Nate
_
From: Yang, Lin A
Sent: Monday, April 3, 2017 3:04 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject:
On 04/05/2017 09:39 AM, Akihiro Motoki wrote:
I noticed this thread by Monty's reply. Sorry for my late :(
I think we need to think 'id' separately for API modeling and DB modeling.
In the API perspective, one of the important things is that 'id' is
not predictable
and it rarely conflict. From
On 05/04/17 09:00 AM, Monty Taylor wrote:
>
> Please do NOT use uuid as a primary key in MySQL:
>
> * UUID has 36 characters which makes it bulky.
you can store it as a binary if space is a concern.
> * InnoDB stores data in the PRIMARY KEY order and all the secondary keys
> also contain
On 4/4/2017 10:07 PM, Feodor Tersin wrote:
I raised the question though, could we move forward with removing the
device field from the "POST /servers/{server_id}/os-volume_attachments"
API since that doesn't do anything with image BDM overrides.
Will this affect detaching/attaching of root
I noticed this thread by Monty's reply. Sorry for my late :(
I think we need to think 'id' separately for API modeling and DB modeling.
In the API perspective, one of the important things is that 'id' is
not predictable
and it rarely conflict. From this perspective, UUID works.
In the DB
FWIW, from my perspective on the Project Navigator side, this format
works great. We can actually derive the age of the project from this
information as well by identifying the first release that has API data
for a particular project. I'm indifferent about where it lives, so I'd
defer to you
On 2017-04-05 14:00:59 +0800 (+0800), 林泽燕 wrote:
[...]
> I wonder if I could show you my study, including some metrics for
> the prediction model and a visualization tool.
[...]
I want to start out thanking you for your research and interest in
OpenStack's development practices. I love that our
Just in case any Murano developers are also on the Kubernetes users
list, this came up. Might be good to reach out to our Kubernetes friends
here if we have some insights that could help them.
Here's a list to the Google Groups message if it's easier to read than
the mangled email below:
On 02/21/2017 07:28 AM, gordon chung wrote:
On 21/02/17 01:28 AM, Qiming Teng wrote:
in mysql[2].
Can someone remind me the benefits we get from Integer over UUID as
primary key? UUID, as its name implies, is meant to be an identifier for
a resource. Why are we generating integer key values?
Hi Team,
Just a kind reminder for the team meeting today on EST 11:00am on
#openstack-cyborg .
--
Zhipeng (Howard) Huang
Standard Engineer
IT Standard & Patent/IT Prooduct Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen
On 03/30/2017 05:13 AM, Julian Edwards wrote:
Hi all
Hi and welcome!
I'm looking to start contributing to Ironic, and in fact I did a
couple of small patches already which are still waiting to be
landed/reviewed. [1]
I'm finding it a little hard to find some more reasonable bugs to get
On 03/30/2017 08:36 PM, Doug Hellmann wrote:
Excerpts from Sean McGinnis's message of 2017-03-22 10:44:05 -0500:
On Wed, Mar 22, 2017 at 08:42:42AM -0500, Kevin L. Mitchell wrote:
On Tue, 2017-03-21 at 22:10 +, Taryma, Joanna wrote:
However, pep8 does not accept passing variable to
Monty Taylor wrote:
> As per our discussion in today's TC meeting, I have made a document
> format for reporting versions to the project navigator. I stuck it in
> the releases repo:
>
> https://review.openstack.org/453361
>
> Because there was already per-release information there, and the
>
Hi all,
I'm working on neutron L3 Agent and some other Agent. I found that there
are lots of RPCs including RPC call and notification and lots of 'context'
as bellow. But I don't know its detail context, can I get these from some
docs?
If there are no docs, could I get these using some debug
Hi everyone,
Last year in Ann Arbor, a group of OpenStack community members
(including 6 current TC members) attended a Servant Leadership training
at ZingTrain organized by Colette Alexander and funded by the OpenStack
Foundation. We found that these concepts adapted quite well to our
unique
Hey,
My two cents.
JP
On 04/04/2017, 13:39, "Monty Taylor" wrote:
Hey all!
I woke up early this morning and found myself thinking "I clearly don't
have enough work on my plate, why don't I add some more?"
I'd love to make a gate job that:
- Deploys
Hello, team,
Agenda of Apr.5 weekly meeting:
1. feature implementation review
2. Pike-2 planning
3. Open Discussion
How to join:
# IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on
every Wednesday starting from UTC 14:00.
If you have other topics to be
Hi Clark
On Tue, 4 Apr 2017 at 00:08 Clark Boylan wrote:
> One of the major sets of issues currently affecting gate testing is
> Libvirt stability. Elastic-recheck is tracking Libvirt crashes for us
> and they happen frequently [0][1][2]. These issues appear to only affect
On Tue, 4 Apr 2017 at 14:38 Daniel P. Berrange wrote:
> On Mon, Apr 03, 2017 at 04:06:53PM -0700, Clark Boylan wrote:
> > Hello,
> >
> > One of the major sets of issues currently affecting gate testing is
> > Libvirt stability. Elastic-recheck is tracking Libvirt crashes for
Thank you Matt for all your work and help :) Good luck!
2017-04-05 4:20 GMT+04:00 Emilien Macchi :
> On Tue, Apr 4, 2017 at 5:23 PM, Matt Fischer wrote:
> > I am stepping down as core in the puppet openstack project. This is the
> > culmination of a long
Hello,
I am testing the neutron l2gw plugin for production use.
I found a bug, that I think is either a design problem or feature that
is not implemented.
When we configure the l2gateways with the Openstack API, some state is
stored in the mysql database, and the neutron-l2gateway-agent
Hi everyone,
It's update time and we need to start raising the upper bounds on Django in
global-requirements. We're currently capped at <1.9, which will shortly be
raised to <1.10. This will raise the upper-constraint to 1.9.13. See
https://review.openstack.org/#/c/453482/
Following a couple
hi,
On Tue, Apr 4, 2017 at 4:09 PM, Gary Kotton wrote:
> Hi,
>
> The problem that we have is that any foreign key usage under transactions is
> now broken. An example of an exception that is raised is:
>
>
>
> DBReferenceError: (sqlite3.IntegrityError) FOREIGN KEY
Mike,
Thank you for your service.
Regards
-steve
-Original Message-
From: Mike Perez
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Tuesday, April 4, 2017 at 1:20 PM
To:
57 matches
Mail list logo