We didn't discuss it explicitly, but I don't believe the decision has changed.
We can remove it, but last I checked the patches in line to handle testing
after deprecation still needed work. If they've been updated etc. I can look
again.
Rob
On 22 July 2016 at 07:52, Matthias Runge
mailto:mru
Hi all,
> 2. We don't have enough higher-level (integration leve) test coverage for
our newer angular interfaces.
I previously wrote about new horizon integration autotests architecture and
parallel mode: https://github.com/sergeychipiga/horizon_autotests. In this
automated scope there are many t
You're right Joshua.
Tooz HEAD points to 0f4e1198fdcbd6a29d77c67d105d201ed0fbd9e0.
With regards to etcd and zookeeper's versions, they are:
zookeeper-3.4.5+28-1.cdh4.7.1.p0.13.el6.x86_64,
etcd-2.2.5-2.el7.0.1.x86_64.
John.
On Thu, Jul 21, 2016 at 8:14 PM, Joshua Harlow wrote:
> Hi John,
>
> Th
Now that we have switched to oslo.db for test provisioning the
responsibility of choosing a location lands here:
https://github.com/openstack/oslo.db/blob/a79479088029e4fa51def91cb36bc652356462b6/oslo_db/sqlalchemy/provision.py#L505
The problem is that when you specify OS_TEST_DBAPI_ADMIN_CONNECTI
Hi,
What is the discussion result of privsep issue?
When can we release next os-brick?
Best wishes
Lisa
From: Ivan Kolodyazhny [mailto:e...@e0ne.info]
Sent: Wednesday, July 13, 2016 9:55 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [cinder] [
+1
On Fri, Jul 22, 2016 at 2:36 AM, Doug Wiegley
wrote:
> +1
>
> On Jul 21, 2016, at 5:13 PM, Kevin Benton wrote:
>
> +1
>
> On Thu, Jul 21, 2016 at 2:41 PM, Carl Baldwin wrote:
>
>> +1 from me
>>
>> On Thu, Jul 21, 2016 at 1:35 PM, Assaf Muller wrote:
>>
>>> As Neutron's so called testing li
+1
From: Oleg Bondarev
To: "OpenStack Development Mailing List (not for usage questions)"
Date: 22/07/2016 09:13
Subject:Re: [openstack-dev] [Neutron] Proposing Jakub Libosvar for
testing core
+1
On Fri, Jul 22, 2016 at 2:36 AM, Doug Wiegley wr
I think the one use case you missed is the bug for which it was being
developed to fix: https://review.openstack.org/#/c/314054/
Currently we check for overlapping subnets on the same network in a lookup
before creating the subnet, so two requests can race and get overlapping
subnets committed to
Were the backends (zookeeper, etcd) deployed in a cluster configuration? I
can't quite tell from the doc.
On Fri, Jul 22, 2016 at 12:58 AM, John Schwarz wrote:
> You're right Joshua.
>
> Tooz HEAD points to 0f4e1198fdcbd6a29d77c67d105d201ed0fbd9e0.
>
> With regards to etcd and zookeeper's versio
Hi,
Once you solve the issue of getting the baremetal ports to transition to
the ACTIVE state, a notification will automatically be emitted to Nova of
'network-vif-plugged' with the port ID. Will ironic not have access to that
event via Nova?
If not, Ironic could develop a service plugin that jus
Yes, the backends were deployed in cluster configuration (the
configurations are available in the appendix).
I'll make a change to the doc to make sure this is reflected properly.
On Fri, Jul 22, 2016 at 11:29 AM, Kevin Benton wrote:
> Were the backends (zookeeper, etcd) deployed in a cluster con
Hi Hongbin,
This is really a good idea, because it will mitigate much of the job of
implementing loop and conditional branch in Heat ResourceGroup. But as Kevin
pointed out in below mail, it need a careful upgrade/migration path.
Meanwhile, as for the blueprint of supporting multiple flavor
(h
. But
your opinions are more than welcome.
20160722 Agenda
===
1) roll call
2) Agenda bashing
3) Approved Wei (kong.w...@zte.com.cn) as daisycloud core reviewer
4) daisycloud status update
5) daisy4nfv status update and disscussion in daisycloud channel
Log
===
? daisycloud-core
On 22/07/16 09:38, Rob Cresswell wrote:
> We didn't discuss it explicitly, but I don't believe the decision has
> changed. We can remove it, but last I checked the patches in line to
> handle testing after deprecation still needed work. If they've been
> updated etc. I can look again.
>
> Rob
>
P
+1 too
From: Mauricio Lima [mailto:mauricioli...@gmail.com]
Sent: Tuesday, July 19, 2016 5:29 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [kolla][vote] Applying for stable-follows tag
+1
2016-07-19 12:23 GMT-03:00 Vikram Hosakote (vhosakot)
Kevin, thanks for reply,
On Fri, Jul 22, 2016 at 11:50 AM, Kevin Benton wrote:
> Hi,
>
> Once you solve the issue of getting the baremetal ports to transition to
> the ACTIVE state, a notification will automatically be emitted to Nova of
> 'network-vif-plugged' with the port ID. Will ironic not
Hi Aimee,
I think devstack by default configured horizon to use v3 .
For V2 authentication, from the logs , auth_url doesn't seem to be set
explicitly to v2 auth_url .
I have always set explicit v2 auth which worked fine.
For eg:- auth_url = 'http://:5000/v2.0' , for V2 authentication
I have rai
Hi team, I’d like to inform you, that I would be on vacation during next week
and a half and would like to appoint some of my deputies =)
During this cycle I’m acting as a release liaison, so in my absence I would
like Victor Ryzhenkin (freerunner) to act as one and be responsible for
supervis
Thanks for the comments Amitabha.
Please see comments inline
On Fri, Jul 22, 2016 at 5:50 AM, Amitabha Biswas wrote:
> Hi Numan,
>
> Thanks for the proposal. We have also been thinking about this use-case.
>
> If I’m reading this accurately (and I may not be), it seems that the
> proposal is to
Thanks Anusha! I will retest this today. I guess I need to learn more
about Horizon as well - thanks for pointing me in the right direction.
aimee
On Fri, Jul 22, 2016 at 6:30 AM, Anusha Ramineni wrote:
> Hi Aimee,
>
> I think devstack by default configured horizon to use v3 .
> For V2 authent
On 07/21/2016 05:26 PM, Knight, Clinton wrote:
> Nate, you have to press Ctrl-C to see the in-progress test, that’s why you
> don’t
> see it in the logs. The bug report shows this and points to the patch where
> it
> appeared to begin. https://bugs.launchpad.net/cinder/+bug/1578986
>
> Clinto
On Thu, 21 Jul 2016 at 09:27 Sean Dague wrote:
> On 07/12/2016 06:25 AM, Matt Riedemann wrote:
>
> > We probably aren't doing anything while Sean Dague is on vacation. He's
> > back next week and we have the nova/cinder meetups, so I'm planning on
> > talking about the grenade issue in person an
ure, when we move to work with OPNFV world, we
> will still use this channel to discuss not only daisycloud but also
> daisy4nfv. I personaly do not want to maintain two meeting by myself. But
> your opinions are more than welcome.
>
>
>
>
> 20160722 Agenda
> ===
Hey all,
During the midcycle we discussed a few options for a new logo mascot. I've
taken a few of the top choices and created a survey to get more input:
https://www.surveymonkey.com/r/G7JRNQB
Please vote as soon as possible. These are first come, first served, so we
should decide soon and get
Hi, nova and neutron teams,
While booting new instance nova requests port for that instance in the
neutron.
It's possible to have a situation when neutron doesn't response due timeout
or connection break and nova retries port creation. It definitely results in
ports duplication for instance [1].
On 07/21/2016 02:43 PM, Carl Baldwin wrote:
None of these operations are expected to be very contentious and
performance hasn't really been a concern yet. If it were a big concern,
I'd be very interested in the GiST index solution because, as I
understand it, detecting overlap without that cap
Hi All!
Today we are going to update the 'fuel-devops' framework on our product CI
to the version 2.9.22.
It's the FINAL version in 2.9 thread, new active development will be
produced in 3.x thread only, and 3.0.1 is released as first of it's.
Changes sinse 2.9.21:
* For devops:
- paramiko 2.0
I’m not a core, so treat this as +0 but I think Jakub will be good addition to
core team.
So +1
> On Jul 22, 2016, at 3:20 AM, Martin Hickey wrote:
>
> +1
>
> Oleg Bondarev ---22/07/2016 09:13:16---+1 On Fri, Jul 22, 2016
> at 2:36 AM, Doug Wiegley
>
> From: Oleg Bondarev
> To: "OpenStack
This series is part of the priority feature libvirt-instance-storage[1]. At
first glance it may not be immediately apparent why, so I'll work backwards
for
context.
The purpose of the feature is to create an unambiguous, canonical source of
metadata about 'local' storage. 'Local' here is defined t
On Thu, Jul 21 2016, gordon chung wrote:
> meerkat is a good option too. i think we have something to vote on :)
I've started a poll (sent to core reviewers, it's the easiest), go ahead
and vote. I'll stop the vote Tuesday (or before if everyone voted by
then!).
--
Julien Danjou
# Free Software
On 7/14/2016 4:40 PM, Matt Riedemann wrote:
On 7/14/2016 3:11 AM, GHANSHYAM MANN wrote:
1. Always add a schema change to Tempest if a microversion changes a
response.
The problem with this is we shouldn't land a schema change by itself
in tempest.
Until we have something using the schema we ha
On 07/22/2016 04:02 AM, Kevin Benton wrote:
Now that we have switched to oslo.db for test provisioning the
responsibility of choosing a location lands
here:
https://github.com/openstack/oslo.db/blob/a79479088029e4fa51def91cb36bc652356462b6/oslo_db/sqlalchemy/provision.py#L505
The problem is t
On 07/22/2016 04:02 AM, Kevin Benton wrote:
Now that we have switched to oslo.db for test provisioning the
responsibility of choosing a location lands
here:
https://github.com/openstack/oslo.db/blob/a79479088029e4fa51def91cb36bc652356462b6/oslo_db/sqlalchemy/provision.py#L505
The problem is t
On 7/22/2016 8:20 AM, Angus Lees wrote:
On Thu, 21 Jul 2016 at 09:27 Sean Dague mailto:s...@dague.net>> wrote:
On 07/12/2016 06:25 AM, Matt Riedemann wrote:
> We probably aren't doing anything while Sean Dague is on vacation.
He's
> back next week and we have the nova/cinder
hope can help you.
http://www.chenshake.com/openstack-project-series-3-devstack/
On Fri, Jul 22, 2016 at 9:35 AM, wrote:
>
> Hi all,
>
> When i use devstack to deploy a OS env, it raise the error.
> The log is as follows.
> Does anybody know how to resolve this problem? Thank you!~
>
> 12 stati
On Wed, Jul 20, 2016 at 12:29 PM, Rob Crittenden
wrote:
> Rob Crittenden wrote:
>
>> Andrey Pavlov wrote:
>>
>>> Hi,
>>>
>>> When I ran devstack with SSL I found a bug and tried to fix it -
>>> https://review.openstack.org/#/c/242812/
>>> But no one agree with me.
>>> Try to apply this patch - it
On Thu, Jul 21, 2016 at 07:03:53AM -0700, Matt Riedemann wrote:
> On 7/21/2016 2:03 AM, Bhor, Dinesh wrote:
> > Hi Nova Devs,
> >
> >
> >
> > Many times, there are a number of data sets that we have to run the same
> > tests on.
> >
> > And, to create a different test for each data set values i
Brant Knudson wrote:
On Wed, Jul 20, 2016 at 12:29 PM, Rob Crittenden mailto:rcrit...@redhat.com>> wrote:
Fixing Keystone is easy. An Apache VirtualHost for 443 needs to be
added.
But I found another, deeper problem: cinder won't listen on SSL.
When they switched to using oslo_
All - I made the change to the auth_url that Anusha suggested.
Same problem as before " Cannot authorize API client"
2016-07-22 14:13:50.835861 * calling policies_list =
client.list_policy()*
2016-07-22 14:13:50.836062 Unable to get policies list: Cannot
authorize API client.
I used the t
Hello All,
We came out of the Midcycle with a lot of things on a lot of people’s
plates. Here is a summary of what everyone signed up for and what things
need owners.
scottda:
-
Pick a time to meet weekly to discuss and push ahead with Active-Active
HA (day1)
-
Find out the p
Excerpts from Jamie Lennox's message of 2016-07-20 10:28:29 +1000:
> On 20 July 2016 at 00:06, Joshua Harlow wrote:
>
> > Hayes, Graham wrote:
> >
> >> On 18/07/16 22:27, Ronald Bradford wrote:
> >>
> >>> Hi All,
> >>>
> >>> For Oslo libraries we ensure that API's are backward compatible for 1+
>
Eric, you're right.
I've disabled all such tests using '@unittest.skip("Skip until bug #1578986
is fixed")' decorator in my patch:
$ grep -r '1578986' cinder/tests/unit/ | grep -v 'pyc' | wc -l
37
Next step is to fix them.
[1] https://review.openstack.org/#/c/320148/
Regards,
Ivan Kolodyazhny
+1
On Fri, 2016-07-22 at 09:19 -0500, Darek Śmigiel wrote:
> I’m not a core, so treat this as +0 but I think Jakub will be good
> addition to core team.
>
>
> So +1
>
> > On Jul 22, 2016, at 3:20 AM, Martin Hickey
> > wrote:
> >
> > +1
> >
> > Oleg Bondarev ---22/07/2016 09:13:16---+1 On Fri
On Wed, Jul 20, 2016, at 07:01 AM, Rob Crittenden wrote:
> Andrey Pavlov wrote:
> > Hi,
> >
> > When I ran devstack with SSL I found a bug and tried to fix it -
> > https://review.openstack.org/#/c/242812/
> > But no one agree with me.
> > Try to apply this patch - it may help.
> > Also there is
I just approved the revert.
I think we need to step back and re-evaluate the work that we are doing
in neutron-legacy. It's very fragile - and really any change to that
piece of logic ends up breaking networking-generic-switch,
ironic-multitenant-network, midonet, or the gate.
Which is why I'm re
Also I was the one who approved the original patch, so the fault rests
on my shoulders. My apologies.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@list
Ofcourse insightful reviewers will make development fast.
So ++
From: Darek Śmigiel [mailto:smigiel.dari...@gmail.com]
Sent: Friday, July 22, 2016 7:20 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] Proposing Jakub Libosvar for testing
Hi all,
Spyros has consistently contributed to Magnum for a while. In my opinion, what
differentiate him from others is the significance of his contribution, which
adds concrete value to the project. For example, the operator-oriented install
guide he delivered attracts a significant number of
Hey folks,
I know it doesn't make a lot of sense to break up containers from ansible
changes to people outside the core review team, but for anything with backport
potential, please do so. We are considering in Occata splitting the kolla repo
into two (kolla = containers & build, kolla-ansible
Hi,
I started some work to have a CI job that will only deploy an undercloud.
We'll save time and resources.
I used storyboard: https://storyboard.openstack.org/#!/story/2000682
and I invite our contributors to use it too when working in TripleO
CI, it helps us to track our current work.
So far
On 21/07/2016 16:49, Doug Hellmann wrote:
> Excerpts from Hayes, Graham's message of 2016-07-19 16:59:20 +:
>> On 19/07/2016 16:39, Doug Hellmann wrote:
>>> Excerpts from Hayes, Graham's message of 2016-07-18 17:13:09 +:
On 18/07/2016 17:57, Thierry Carrez wrote:
> Hayes, Graham wr
Hi all,
Based on Dims's request, I removed him from the Magnum core reviewer team.
Dims's contribution started from the first commit of the Magnum tree, and he
was served as a Magnum core reviewer for a long time. I am sorry to hear that
Dims want to leave the team, but thanks for his contribut
Thanks Hongbin!
On Fri, Jul 22, 2016 at 5:13 PM, Hongbin Lu wrote:
> Hi all,
>
>
>
> Based on Dims’s request, I removed him from the Magnum core reviewer team.
> Dims’s contribution started from the first commit of the Magnum tree, and he
> was served as a Magnum core reviewer for a long time. I
On 22 July 2016 at 21:35, Steven Dake (stdake) wrote:
>
> Hey folks,
>
> I know it doesn't make a lot of sense to break up containers from ansible
changes to people outside the core review team, but for anything with
backport potential, please do so. We are considering in Occata splitting
the kol
On Fri, Jul 22, 2016 at 4:53 PM, Emilien Macchi wrote:
> Hi,
>
> I started some work to have a CI job that will only deploy an undercloud.
> We'll save time and resources.
>
> I used storyboard: https://storyboard.openstack.org/#!/story/2000682
> and I invite our contributors to use it too when wo
On Fri, Jul 22, 2016 at 2:08 PM, Hayes, Graham wrote:
> * OpenStack Client
>
> OpenStack CLI privileged projects have access to more commands, as
> plugins cannot hook in to them (e.g. quotas)
>
It's been OSC's intention to allow for command hooking, we just don't
really know how to do that
From: Dave Walker mailto:em...@daviey.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Friday, July 22, 2016 at 2:19 PM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.op
I think its an interesting idea. If nothing else, it will show what it would be
like to have a split set of repo's before it actually is a thing and can't be
undone.
Thanks,
Kevin
From: Dave Walker [em...@daviey.com]
Sent: Friday, July 22, 2016 2:19 PM
To: OpenSt
Hi folks,
At the midcycle we decided to push off implementing Monitoring until post
Newton. The rationale for this decision was that the core review team has
enough on their plates and nobody was super keen to implement any monitoring
solution given our other priorities.
Like all good things,
Precisely!
From: "Fox, Kevin M" mailto:kevin@pnnl.gov>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Friday, July 22, 2016 at 3:03 PM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:opensta
Your a class act Dims. It was good working with you on Magnum :)
Regards
-steve
On 7/22/16, 2:15 PM, "Davanum Srinivas" wrote:
>Thanks Hongbin!
>
>On Fri, Jul 22, 2016 at 5:13 PM, Hongbin Lu wrote:
>> Hi all,
>>
>>
>>
>> Based on Dims¹s request, I removed him from the Magnum core reviewer
>>t
Don't forget mewalds implementation as well - we now have 2 monitoring
options for kolla :-)
On Fri, Jul 22, 2016 at 3:15 PM, Steven Dake (stdake) wrote:
> Hi folks,
>
> At the midcycle we decided to push off implementing Monitoring until post
> Newton. The rationale for this decision was that t
Thanks for pointing that out. Brain out to lunch today it appears :(
I think choices are a good thing even though they increase our
implementation footprint. Anyone opposed to implementing both with
something in globals.yml like
monitoring: grafana or
monitoring: sensu
Comments questions or con
Hi,
I saw in specs of kilo that ssl re-encryption will be introduced in later
phase. Is the ssl re-encryption feature available in the mitaka release? I
understand ssl offload is available, but I want to try the ssl
re-encryption on octavia lbaas.
This link refers to v1 probably
https://wiki.openst
I think those are two different, complementary things.
One's metrics and the other is monitoring. You probably want both at the same
time.
Thanks,
Kevin
From: Steven Dake (stdake) [std...@cisco.com]
Sent: Friday, July 22, 2016 3:52 PM
To: OpenStack Develo
Yes, this is my thought.
The scope of the Sensu work is: "Is this thing working?" (with the
reference being up/down)
But the scope of the Grafana and friends is, "How hard is this working?"
(but no alerting)
They are certainly complementary However, Sensu can throw data at a
Grafana stack (ai
Thanks Numan & Amitabha, this may be the right direction to solve the bug [1].
It basically implements Neutron API as async call, and queuing the request
within DB transaction, and the ordering is preserved by the journal thread
"lock" that is implemented with state PROCESSING plus DB transactio
Hi Aimee,
Thanks for the investigation.
I remember testing congress client with V3 password based authentication ,
which worked fine .. but never tested with token based .
Please go ahead and fix it , if you think there is any issue .
On 22-Jul-2016 9:38 PM, "Aimee Ukasick" wrote:
> All - I m
I do not believe it is in it and I don't know if anyone is working on
it. I believe it has pushed down the priority stack, but someone might
correct me if I'm wrong.
Thanks,
Brandon
On Fri, 2016-07-22 at 16:00 -0700, Akshay Kumar Sanghai wrote:
> Hi,
> I saw in specs of kilo that ssl re-encryptio
One of the things that seems to happen now and then is that an update to
requirements breaks gate for other projects in some way. One thing that
helps is cross project testing, though we do that on a one off basis I'd
like to see this testing become more codified. I have a review out that
does a
70 matches
Mail list logo
