Thank you all for the great effort, now only two patches of MUST TO HAVE are on
the way to be merged:
https://review.openstack.org/#/c/372414/ installation update
https://review.openstack.org/#/c/326192/ volume detach
Best Regards
Chaoyi Huang (joehuang)
From: jo
Agenda of Sept.28 weekly meeting, let's continue the topics:
# Newton cycle design summit planning:
https://etherpad.openstack.org/p/ocata-tricircle-sessions-planning
# patch review before freeze date Sept.30
# open discussion
How to join:
# IRC meeting: https://webchat.freenode.net/?chann
Hi Tony,
As you suggest, I find the reason of this problem.
I have removed "API_WORKES=0" in local.conf.
It works.
Thanks very much.
Best Regards,
xiangxinyong
Tony Breeds 于2016年9月28日周三 上午11:28写道：
> On Wed, Sep 28, 2016 at 11:10:52AM +0800, xiangxinyong wrote:
> > Hi guys,
> >
> >
> > When i s
Hello everyone,
A new release candidate for horizon for the end of the Newton cycle was
generated, to catch release-critical fixes and include recent
translations. You can find the source code tarball at:
[...]
Unless new release-critical issues are found that warrant a release
candidate respin,
Hi,
I'm working on adding new tests to the networking scenario tests.
I see that there is a class named "NetworkScenarioTest" in manager.py file.
In that class, there are some helpers functions like '_create_network',
'create_subnet', ...
Is this the place to add more helpers functions like '_up
On 09/27/2016 06:19 PM, Andrew Laski wrote:
>
> I totally understand where you're coming from. I just see it
> differently.
>
> The way it was done did not affect any other projects, and the plumbing
> used is something that could have easily be left in. And as luck would
> have it there's anoth
Hi Zane,
Thanks for pointing this out! My interpretation of the StackForge
Retirement page[1] was wrong on that point. I've updated the blog post to
reflect that (without removing the original interpretation).
The discussion about renaming git repos is a bit of a red herring, because
what we're r
Refloating this thread.
I posted this rfe/bug [1], and I'm planning to come up with an
experimental job that triggers one of the basic neutron/lbaas tests
with octavia.
I wonder if even picking up the scenario one for now could make sense,
it's not very stable at the moment, but may be spreading
On Wed, Sep 28, 2016, at 07:15 AM, Sean Dague wrote:
> On 09/27/2016 06:19 PM, Andrew Laski wrote:
>
> >
> > I totally understand where you're coming from. I just see it
> > differently.
> >
> > The way it was done did not affect any other projects, and the plumbing
> > used is something that
TL;DR networking-cisco IRC meetings will be held bi-weekly on
#openstack-meeting-3 starting from 2016/10/11
With the results of the doodle poll, and some pointers from Steve and Jeremy
(thanks guys for the info) I've successfully organised the time and place for
the networking-cisco IRC meeting
I just found this one created recently, and I will try to build on top of it:
https://review.openstack.org/#/c/371807/12
On Wed, Sep 28, 2016 at 1:52 PM, Miguel Angel Ajo Pelayo
wrote:
> Refloating this thread.
>
> I posted this rfe/bug [1], and I'm planning to come up with an
> experimental j
Excerpts from Andrew Laski's message of 2016-09-27 11:36:07 -0400:
> Hello all,
>
> Recently I noticed that people would look at logs from a Zuul née
> Jenkins CI run and comment something like "there seem to be more
> warnings in here than usual." And so I thought it might be nice to
> quantify t
Hi all,
So the integration tests have started failing all over the place again. Given
the number of failures over the past few weeks I've put up a patch to make them
non-voting [1]. Please stop rechecking patches until this merges.
Reviewers, please be sure to check the test logs when they fail
On Thu, Sep 22, 2016 at 2:30 PM, Devananda van der Veen
wrote:
> Considering I'm the only one currently working on it / bringing up new
> topics, I
> think biweekly is a better match to the pace I'm working on this.
>
> However, I hope that changes after the summit / once we start implementing
>
Hi,
There will be three Vitrage design sessions in Barcelona:
Wednesday 15:05-15:45: workroom
Wednesday 15:55-16:35: fishbowl
Wednesday 17:55-18:35: workroom
I gathered the ideas that were raised in the etherpad below, and created a
draft for the design session discussions. I’ll be happy to ge
Hi team,
I would like to propose Zhu Rong (irc: zhurong) to be included as Solum
core.
Zhu Rong has been very active in different parts of Solum over several
months now.
His primary contribution has been moving Solum to use Oslo libraries,
thereby
making our project satisfy one of the project-wid
Similar to keystone/neutron/nova, I thought it would be healthy for
us to do a post-mortem on the Newton cycle. Here's the etherpad:
https://etherpad.openstack.org/p/ironic-newton-retrospective
Let's try to keep it troll-free (I know it's hard).
Also note I put a poll about having a summit sessio
On 9/28/2016 12:10 AM, Joshua Harlow wrote:
ACTION: we should make sure workarounds are advertised better
ACTION: we should have some document about "when cells"?
This is a difficult question to answer because "it depends." It's akin
to asking "how many nova-api/nova-conductor processes should I
Hi team,
Since all of us are preparing for future summit and there is no specific
topics to cover, I think that we should skip meeting tomorrow at Sept 29.
If there is topic to discuss, please write email to mailing list about your
topic.
PS: Please, continue sharing your ideas about future summi
Matt Riedemann wrote:
On 9/28/2016 12:10 AM, Joshua Harlow wrote:
ACTION: we should make sure workarounds are advertised better
ACTION: we should have some document about "when cells"?
This is a difficult question to answer because "it depends." It's akin
to asking "how many nova-api/nova-condu
Greetings,
We have done incredible work lately to fix a maximum of bugs in such a
short time:
https://review.openstack.org/#/q/topic:tripleo/rc2
At this time, we still have 16 bugs open:
https://launchpad.net/tripleo/+milestone/newton-rc2
While some of them might be fixed by tomorrow (TripleO R
+1
From: Devdatta Kulkarni
Date: Wed, Sep 28, 2016 at 8:32 AM
Subject: [Solum] Nominating Zhu Rong for Solum core
To: [email protected]
Hi team,
I would like to propose Zhu Rong (irc: zhurong) to be included as Solum core.
Zhu Rong has been very active in different parts of Sol
I noticed a good statement, marked it inline.
On 9/28/16 7:24 AM, John Davidge wrote:
> Hi Zane,
>
> Thanks for pointing this out! My interpretation of the StackForge
> Retirement page[1] was wrong on that point. I've updated the blog post to
> reflect that (without removing the original interpre
+1
Look forward to more contributions from you!
On Wed, Sep 28, 2016 at 8:32 AM, Devdatta Kulkarni <
[email protected]> wrote:
> Hi team,
>
> I would like to propose Zhu Rong (irc: zhurong) to be included as Solum
> core.
>
> Zhu Rong has been very active in different parts of Solum o
Until now, we had no specific team for dealing with Puppet OpenStack
CI (aka openstack/puppet-openstack-integration project).
But we have noticed that David was doing consistent work to contribute
to Puppet OpenStack CI by adding more coverage, but also helping when
things are broken.
David is alwa
On 09/28/2016 10:06 AM, Emilien Macchi wrote:
Until now, we had no specific team for dealing with Puppet OpenStack
CI (aka openstack/puppet-openstack-integration project).
But we have noticed that David was doing consistent work to contribute
to Puppet OpenStack CI by adding more coverage, but al
I'd like to throw in my hat to serve the community as a TC member.
My name is Jim Rollenhagen, but I'm better known in the community as jroll.
I've worked in many environments, from 20-person startup to massive
corporations. For the past three years, I've been working on OpenStack at
Rackspace. I
+1 from me, David is doing an awesome job in p-o-i =)
2016-09-28 13:08 GMT-03:00 Rich Megginson :
> On 09/28/2016 10:06 AM, Emilien Macchi wrote:
>
>> Until now, we had no specific team for dealing with Puppet OpenStack
>> CI (aka openstack/puppet-openstack-integration project).
>> But we have no
Hi -
I want to bring up a subject that needs a little more attention. There are
a few ideas floating around but it's important that we get this done right.
UI is unique in the sense that it operates almost entirely in a browser,
talking directly to service API endpoints which it either figures o
Hello! I am announcing my candidacy for a position on the OpenStack Technical
Committee.
For those who do not know me, I have been involved with OpenStack since the
very beginning, working for Rackspace as a core member of the Nova team. An
internal job change took me away from active development
Here you go Flavio, Sergey and team collected some information from
fuel-ccp efforts.
Design for OpenStack Containerized Control Plane :
https://review.openstack.org/#/c/378266/
Design document for clustering services on k8s :
https://review.openstack.org/#/c/378244/
Add test plan/results for fuel
Despite its name, the Technical Committee has become the part of the
OpenStack contributor community that enshrines, defines, and -- in some
rare cases -- enforces what it means to be "OpenStack". Meanwhile,
the community has seen a great deal of growth and change.
Some of these changes have led
Currently the Ironic Grenade gate job is broken. Until the issue is resolved
please don't do recheck on openstack/ironic patch.
Work is ongoing to figure out why it stopped working.
__
OpenStack Development Mailing List (not
But in the lbaas db, all lbaas resources have the provisioning_status and
operating_status fields[1].
[1]
http://git.openstack.org/cgit/openstack/neutron-lbaas/tree/neutron_lbaas/db/loadbalancer/models.py#n352
Also there are apis which allows drivers to maintain them[2].
[2]
http://git.openstack.o
Integration tests are now non-voting, so feel free to recheck failing builds.
Rob
On 28 September 2016 at 14:23, Rob Cresswell
mailto:[email protected]>> wrote:
Hi all,
So the integration tests have started failing all over the place again. Given
the number of failures over the past
On 28/09/2016 12:41 PM, Chris Dent wrote:
>
> * Information is not always clear nor clearly available, despite
> valiant efforts to maintain a transparent environment for the
> discussion of policy and process. There is more that can be done
> to improve engagement and communication. Maybe
Hi there,
I would like to retire the python-keystoneclient-kerberos repo [1]. The
repo was pretty basic, it had a single auth plugin. The logic has since
been copied over to keystoneauth1 and provided you have kerberos libraries
installed the plugin will be available to you. The last release of
py
On Wed, Sep 28, 2016 at 2:49 PM, gordon chung wrote:
>
>
> On 28/09/2016 12:41 PM, Chris Dent wrote:
> >
> > * Information is not always clear nor clearly available, despite
> > valiant efforts to maintain a transparent environment for the
> > discussion of policy and process. There is more t
Hello everyone,
A new release candidate for murano for the end of the Newton cycle
is available! You can find the source code tarballs at:
https://tarballs.openstack.org/murano/murano-3.0.0.0rc2.tar.gz
https://tarballs.openstack.org/murano-agent/murano-agent-3.0.0.0rc2.tar.gz
https://tarballs.op
>> +1 to release notes or something of that like. i was asked to give an
>> update on the TC internally and it seems the only information out there
>> is to read through backlog of meeting logs or track the items that do
>> get raised to ML. even then, it's hard to define what deliverables were
>>
Hello everyone,
A new release candidate for freezer for the end of the Newton cycle
is available! You can find the source code tarball at:
https://tarballs.openstack.org/freezer/freezer-3.0.0.0rc2.tar.gz
Unless release-critical issues are found that warrant a release
candidate respin, these can
On Wed, 28 Sep 2016, Jim Rollenhagen wrote:
+1 to release notes or something of that like. i was asked to give an
update on the TC internally and it seems the only information out there
is to read through backlog of meeting logs or track the items that do
get raised to ML. even then, it's hard t
> On Sep 28, 2016, at 1:59 PM, Chris Dent wrote:
>
> On Wed, 28 Sep 2016, Jim Rollenhagen wrote:
>
+1 to release notes or something of that like. i was asked to give an
update on the TC internally and it seems the only information out there
is to read through backlog of meeting l
On 2016-09-28 20:59:09 +0100 (+0100), Chris Dent wrote:
> Part of the point I was trying to make in the message to which gordc was
> responding is that whereas a git tree can allow someone to dig through
> and acquire details, a thing that is more like release notes[1] is far
> more human oriented
On 28/09/2016 3:59 PM, Chris Dent wrote:
> On Wed, 28 Sep 2016, Jim Rollenhagen wrote:
>
>> And the git tree, with a changelog, is here:
>> http://git.openstack.org/cgit/openstack/governance/
>
> I assume, but I'd prefer if he confirm, that the point gordc was
> trying to make was that there's mo
On 28/09/2016 4:27 PM, Jeremy Stanley wrote:
> As was pointed out elsewhere in the thread, the TC has been trying
> to do something along these lines at
> http://www.openstack.org/blog/category/technical-committee-updates/
> but even with a dedicated communication subteam (see the May 13,
> 2015
Hey ironic-ers,
My team has a patch [1] up for enabling PXE for petitboot [2]. It's been
around for awhile, and we actually use it in our PowerKVM CI ironic job
(as our OpenPOWER target boxes run petitboot). I was hoping to get some
eyes on it as we'd like to eventually get it upstream. I've r
Hello everyone,
A new release candidate for glance for the end of the Newton cycle
is available! You can find the source code tarball at:
https://tarballs.openstack.org/glance/glance-13.0.0.0rc2.tar.gz
Unless release-critical issues are found that warrant a release
candidate respin, this candid
On Tue, Sep 27, 2016, at 02:58 PM, Clark Boylan wrote:
> Once multinode testing has tls-proxy enabled the next thing I think we
> should be talking about is enabling this by default in devstack. As
> mentioned before ironic doesn't work due to IPA images not trusting
> glance's cert. Swift's func
Fantastic!
Quick semi-related question. Will Magnum Newton be using lbaasv2? That is
what we have implemented in Kolla.
Regards
-steve
From: Ton Ngo
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Tuesday, September 27, 2016 at 10:58 PM
To: "OpenStack Develo
A completely secure alternative isn't available in the Python standard library.
Here's a table of various XML libraries and the vulnerabilities they may be
affected by [1]. This is partially reflected in Python's official documentation
as well (version 2.7.12) [2].
There are currently 132 refer
Hello everyone,
A new release candidate for Cinder for the end of the Newton cycle
is available! You can find the source code tarball at:
https://tarballs.openstack.org/cinder/cinder-9.0.0.0rc2.tar.gz
Unless release-critical issues are found that warrant a release
candidate respin, this candida
Hello,
The Newton branch will be created tomorrow, we can start the Tricircle cleaning
in the trunk to make Tricircle dedicated for networking automation. At the same
time Tricircle Newton release will be done in the Newton branch, two more
patches needed for this branch: one patch to update de
Hello,
Trio2o is a new project which is derived from Tricircle:
https://review.openstack.org/#/c/367114/
Please add the initial members (same as that in Tricircle) to the group
trio2o-core (https://review.openstack.org/#/admin/groups/1576,members) and
trio2o-release (https://review.openstack.o
Steve,
In Newton, we upgraded the Heat templates to use lbaasv2 [1]. However, it
seems the k8s external load balancer still work with lbaasv1. If Kolla
doesn't use the external load balancer feature, it should be fine.
[1] https://review.openstack.org/#/c/314060/
Best regards,
Hongbin
On Wed, S
Hi
I am using the SRIOV on mitaka. When I try to launch the VM with SRIOV port
its failed.
When I see the neutrn-server.log I see that below message on controller.
ddf81 - - -] Refusing to bind due to unsupported vnic_type: direct
bind_port
/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/dr
Hello,
As we discussed yesterday, we'll have a short conversation on the Trio2o
cleaning.
Let's discuss Trio2o cleaning on Friday UTC2:00(i.e, beijing time 10:00), 1 hour
It would be better to discuss this in the channel of #openstack-trio2o instead
of #openstack-tricircle(sorry mentioned #ope
Hello Keystone Devs,
Just curious as to the choice to have the project name be only 64
characters:
https://github.com/openstack/keystone/blob/master/keystone/resource/backends/sql.py#L241
Seems short, and an odd choice when the user.name field is 255 characters:
https://github.com/openstack/keyst
We may have to ask Adam or Dolph, or pull out the history textbook for this
one. I imagine that trying to not bloat the token was definitely a concern.
IIRC User name was 64 also, but we had to increase to 255 because we're not
in control of name that comes from external sources (like LDAP).
On We
I think with PKI tokens we had worse to worry about!
At any rate, would be great to know, and if there isn't a strong reason
against it we can make project name 255 for some more flexibility.
Plus although there is no true official standard, most projects in
OpenStack seem to use 255 as the defau
First off, apologies for missing most of the team meeting today. I have read
through the logs and saw a discussion about deprecating heka. We need to
ensure that we follow the deprecation policy. My understanding of the
deprecation policy is as follows (in a nutshell):
1. We must mail
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Actually, the third option is also not an option in the current undercloud
setup, since making the services listen in 0.0.0.0 will break HAProxy. So
when you're deploying with TLS things will break since we use HAProxy to
terminate TLS connections. On the other hand, we also don't want services
to
63 matches
Mail list logo
