Hi,
I am running the "client.hosts.list()" command in Vitrage to get all the hosts
in the system (we also run similar commands for availability zones and
instances). Vitrage does this to gain a holistic view of system resources[1].
As part of our performance checks we noticed that when calling
On 06/08/16 01:45, Emilien Macchi wrote:
> On Fri, Aug 5, 2016 at 4:19 PM, Wesley Hayutin wrote:
>>
>>
>> On Fri, Aug 5, 2016 at 4:08 PM, Emilien Macchi wrote:
>>>
>>> On Fri, Aug 5, 2016 at 1:58 PM, Steven Hardy wrote:
On Thu, Aug 04, 2016 at 09:46:20PM -0400, Emilien Macchi wrote:
> H
On 07/29/2016 10:55 PM, Doug Hellmann wrote:
> One of the outcomes of the discussion at the leadership training
> session earlier this year was the idea that the TC should set some
> community-wide goals for accomplishing specific technical tasks to
> get the projects synced up and moving in the sa
I can do this for EMEA
-Paul
On 05/08/16 17:11, Steven Dake (stdake) wrote:
Typo is subject tag – please see inside :)
From: Steven Dake mailto:std...@cisco.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Friday, A
I'm on the same page as Doug here.
On 08/01/2016 04:23 PM, Jay Pipes wrote:
> Likewise, what if the Manila project team decides they aren't interested
> in supporting Python 3.5
Any project that is actively deciding to not support the current version
of Python must indeed be kicked out, as it bec
On Wed, Aug 3, 2016 at 4:49 PM, Joe Talerico wrote:
> On Wed, Jul 27, 2016 at 2:04 AM, Hugh Brock wrote:
>> On Jul 26, 2016 8:08 PM, "Gordon, Kent"
>> wrote:
>>>
>>>
>>>
>>>
>>>
>>>
>>> > -Original Message-
>>> > From: Gonéri Le Bouder [mailto:gon...@lebouder.net]
>>> > Sent: Tuesday, Ju
Hi Carl
On Thu, 19 May 2016 at 21:51 Carl Baldwin wrote:
> On Thu, May 19, 2016 at 7:09 AM, Doug Hellmann
> wrote:
> > We have the same issue with version numbers regressing no matter when we
> > cut the next release, so it's up to the team. It might be easier to deal
> > with now while it's fr
Hi Networking SFC team
I'm trying to get a view on a few Neutron related projects with the
objective of lining up a release in Ubuntu and Debian alongside OpenStack
Newton of vmware-nsx, networking-l2gw, networking-sfc and tap-as-a-service.
What are your plans for Newton? I can push snapshots int
Hi, folks
I uploaded a new project to gerrit, but test-requirement.txt had duplicate
entries by mistake. That
makes jenkins fail whatever I
commit(http://logs.openstack.org/58/351458/7/check/gate-python-bileanclient-requirements/017cd3a/console.html).
Anybody have some idea to fix that?
Hi Chris,
We have tried to reproduce it in two blades that have the same configs.
They are all empty of instance from very beginning. What we see that the
scenario happens in one blade, another works as expect. Of course we use
qcow image.
If i use the below calculation, it can explain the s
The problem with the other projects image builds is that they are
based for bigger systems, while cirros is an embedded-device-like
image which boots in a couple of seconds.
Couldn't we contribute to cirros to have such module load by default [1]?
Or may be it's time for Openstack to build their
Awesome Sean!,
Keep us posted!! :)
On Sat, Aug 6, 2016 at 8:16 PM, Mooney, Sean K wrote:
> Hi just a quick fyi,
>
> About 2 weeks ago I did some light testing with the conntrack security group
> driver and the newly
>
> Merged upserspace conntrack support in ovs.
>
>
>
> I can confirm that a
James Page wrote:
Hi Carl
On Thu, 19 May 2016 at 21:51 Carl Baldwin wrote:
On Thu, May 19, 2016 at 7:09 AM, Doug Hellmann
wrote:
> We have the same issue with version numbers regressing no matter when we
> cut the next release, so it's up to the team. It might be easier to deal
> with now
Hi Ihar
On Mon, 8 Aug 2016 at 10:37 Ihar Hrachyshka wrote:
[...]
> Any update on re-tagging the mitaka release of networking-l2gw with the
> > correct semantic version? I'm working on packaging updates for Debian
> > and Ubuntu, and don't really want to push in 2016.1.0, only to have to
> > the
Folks,
Since the end of last week
master.python-fuelclient.pkgs.ubuntu.review_fuel_client [1] blocks all patches
to python-fuelclient. As logs suggest this issue is caused by the Xenial merge
party.
Please resolve the issue ASAP because some folks are blocked and cannot finish
their jobs in t
Hi.
On Mon, Aug 8, 2016 at 1:52 AM, Clint Byrum wrote:
> Excerpts from Steve Baker's message of 2016-08-08 10:11:29 +1200:
>> On 05/08/16 21:48, Ricardo Rocha wrote:
>> > Hi.
>> >
>> > Quick update is 1000 nodes and 7 million reqs/sec :) - and the number
>> > of requests should be higher but we h
If it’s not possible to fix this job during next few hours, let’s mark in as
non-voting until the bug(s) are fixed.
> 8 серп. 2016 р. о 11:48 Roman Prykhodchenko написав(ла):
>
> Folks,
>
> Since the end of last week
> master.python-fuelclient.pkgs.ubuntu.review_fuel_client [1] blocks all
>
Hi Hossein,
hossein zabolzadeh wrote:
> Hi there.
> I am dealing with large amount of legacy application(MediaWiki, Joomla,
> ...) running on openstack. I am looking for the best way to improve high
> availability of my instances. All applications are not designed for
> fail(Non-Cloud-Ready Apps)
We are working on this. Will fix soon.
Vladimir Kozhukalov
On Mon, Aug 8, 2016 at 12:52 PM, Roman Prykhodchenko wrote:
> If it’s not possible to fix this job during next few hours, let’s mark in
> as non-voting until the bug(s) are fixed.
>
> > 8 серп. 2016 р. о 11:48 Roman Prykhodchenko напис
On Mon, Aug 8, 2016 at 11:51 AM, Ricardo Rocha wrote:
> Hi.
>
> On Mon, Aug 8, 2016 at 1:52 AM, Clint Byrum wrote:
>> Excerpts from Steve Baker's message of 2016-08-08 10:11:29 +1200:
>>> On 05/08/16 21:48, Ricardo Rocha wrote:
>>> > Hi.
>>> >
>>> > Quick update is 1000 nodes and 7 million reqs/s
Hello,
For using DPDK, CPUs on compute host has to be isolated between Host,
DPDK PMD and Guests. In order, to configure the host to use only
specified CPUs, the CPUAffinity [1] configuration in
/etc/systemd/system.conf needs to be used. Along with CPUAffinity, IRQ
repining[2] needs to be done, to
Hello Steven!
Our plans for Glare in Newton are: 1. Implement beta version of
App-Catalog, based on Glare v1; 2. Develop an experimental support (POC)
for Murano, Heat and probably Tacker. It means that all big updates will be
in Ocata, and despite the fact that the code will be ready in this cycle
On Mon, 8 Aug 2016, Alex Xu wrote:
Chris, thanks for the blog to explain your idea! It helps me understand
your idea better.
Thanks for reading it. As I think I've mentioned a few times I'm not
really trying to sell the idea, just make sure it is clear enough to
be evaluated.
I agree the goa
Hello team,
I just acquired the openstackmagnum account [1] on docker Hub. It's an
organization
account so all core team members can be owners. Cores, please share with me
your
docker Hub ID or registered e-mail and I'll add you. I already added Adrian
and Egor.
In organization accounts we can ha
On 08 Aug 2016, at 11:51, Ricardo Rocha
mailto:rocha.po...@gmail.com>> wrote:
Hi.
On Mon, Aug 8, 2016 at 1:52 AM, Clint Byrum
mailto:cl...@fewbar.com>> wrote:
Excerpts from Steve Baker's message of 2016-08-08 10:11:29 +1200:
On 05/08/16 21:48, Ricardo Rocha wrote:
Hi.
Quick update is 1000 nod
Vladimir,
Thanks you for the update on this. Is there any ETA available?
On Mon, Aug 8, 2016 at 12:09 PM Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:
> We are working on this. Will fix soon.
>
> Vladimir Kozhukalov
>
> On Mon, Aug 8, 2016 at 12:52 PM, Roman Prykhodchenko
> wrote:
>
>>
I have originally brought this on IRC, but though this place might be
better adequate.
As part of the storlets functional tests Jenkins job, we do a docker
pull from docker hub.
This operation fails many times, and requires many "recheck"s (we run
this with every 'git review').
One solution w
Hi,
On 08/07/2016 09:24 PM, Hongbin Lu wrote:
Added to the agenda of next team meeting:
https://wiki.openstack.org/wiki/Meetings/Containers#Agenda_for_2016-08-09_1600_UTC
.
Thank you, I will join tomorrow (09.08.2016) Magnum team meeting,
Have a nice day,
Best regards,
Hongbin
-Ori
Sean McGinnis wrote:
This may mostly be a Cinder concern, but putting it out there to get
wider input.
For some time now there has been some debate about moving third party
drivers in Cinder to be out of tree. I won't go into that too much,
other than to point out one of the major drivers for
I propose the ant, known for discovering probabilistic graph traversal
algorithms.
My other thought, the bee, has already been taken by refstack.
lxsli
__
OpenStack Development Mailing List (not for usage questions)
Unsubsc
Jeremy Stanley wrote:
On 2016-08-06 17:51:02 -0400 (-0400), Ben Swartzlander wrote:
[...]
when it's no longer to run dsvm jobs on them (because those jobs
WILL eventually break as infra stops maintaining support for very
old releases) then we simply remove those jobs and rely on vendor
CI + mi
Thanks for you comments Stuart!
I also have some thoughts on this matter: first of all, I never liked how
locations are implemented in glance v2, and not just because of
inconsistencies in multiple locations per one image, but for the reason
that there are no differences between internal and exter
zhi wrote:
hi,
Recently, I saw a patch which fixed the listener's admin_state_up
status[1]. This patch is already merged in master branch. But it is not merged
into stable/liberty.
So I upload a new patch[2] to merge that patch into stable/liberty.
[1]: https://review.openstack.or
On 05/08/2016 19:15, Doug Hellmann wrote:
> Excerpts from Hayes, Graham's message of 2016-08-05 17:04:35 +:
>> Hey,
>>
>> We look like we are getting close to merging the os-api-ref integration
>> with openstackdocstheme.
>>
>> Unfortunately, there is no "phased" approach available - the versio
On 08.08.2016 13:07, Alexis Lee wrote:
> I propose the ant, known for discovering probabilistic graph traversal
> algorithms.
>
> My other thought, the bee, has already been taken by refstack.
>
>
> lxsli
>
> __
> OpenStack
Cool thanks for the response. Appreciate it. I think the big take away is all
the ODMs are free from churn in Newton and have a full cycle to adapt to the
changes which is great news!
Thanks!
-steve
From: Mikhail Fedosin mailto:mfedo...@mirantis.com>>
Reply-To: "OpenStack Development Mailing
Recently, I sent a series of patches [1] to make it easier for
developers to deploy a multi node octavia controller with
n_controllers x [api, cw, hm, hk] with an haproxy in front of the API.
Since this is the way the service is designed to work (with horizontal
scalability in mind), and we want t
Hi,
The next notification subteam meeting will be held on 2016.08.09 17:00 UTC [1]
on #openstack-meeting-4.
Cheers,
Gibi
[1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160809T17
__
OpenStack Developme
Is the data transfer compressed?
If there are lots of repeated pattern in the payload, compressing the
content may result in great improvement in performance.
--
Yujun
On Mon, Aug 8, 2016 at 3:19 PM Weyl, Alexey (Nokia - IL) <
alexey.w...@nokia.com> wrote:
> Hi,
>
> I am running the "client.host
I need to check if the data transferred is compressed, but in either way I
don’t want to get more than 99% (that the manager object takes) of the data
sent for the instance / host / availablility zone, so I would like to get the
data without that property.
From: Yujun Zhang [mailto:zhangyujun+.
On Wed, 3 Aug 2016, Andrew Laski wrote:
I am a fan of microversions. I think they work wonderfully to express
when a resource representation changes, or when different data is
required in a request. This allows clients to make the same request
across multiple clouds and expect the exact same res
Hi,
I was looking at grafana today, and spotted another weirdness.
See the periodic jobs dashboard:
http://grafana.openstack.org/dashboard/db/neutron-failure-rate?panelId=4&fullscreen
Currently it shows for me 100% failure rate for py34/oslo-master job,
starting from ~Aug 3. But when I go to
Hi all,
To reduce complexity in configuring SR-IOV I want to deprecate the
supported_pci_vendor_devs option [1] in the neutron-server ml2 config.
This option is doing extra validation that pci vendor id and product id
provided by nova in the neutron port binding profile is matching to the vendor
Excerpts from Hayes, Graham's message of 2016-08-08 11:28:35 +:
> On 05/08/2016 19:15, Doug Hellmann wrote:
> > Excerpts from Hayes, Graham's message of 2016-08-05 17:04:35 +:
> >> Hey,
> >>
> >> We look like we are getting close to merging the os-api-ref integration
> >> with openstackdocs
Thank you for sending the corrected link Mathieu! I thought I fixed it
before I sent the email, but... *shrug*
Anyway! Looking at the doodle, the mutually available time is 4 PM UTC on
this Wednesday (8/10/16). If there are no objections, I guess we will hear
those seeking to discuss defaults o
Dear Sridhar,
Can we also discuss the NSD?
Thanks & Regards
Dharmendra Kushwaha
From: Sridhar Ramaswamy [sric...@gmail.com]
Sent: Monday, August 08, 2016 8:49 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [tac
On 08/08/2016 13:47, Doug Hellmann wrote:
> Excerpts from Hayes, Graham's message of 2016-08-08 11:28:35 +:
>> On 05/08/2016 19:15, Doug Hellmann wrote:
>>> Excerpts from Hayes, Graham's message of 2016-08-05 17:04:35 +:
Hey,
We look like we are getting close to merging the o
On 08/08/2016 08:44 AM, Doug Hellmann wrote:
> Excerpts from Hayes, Graham's message of 2016-08-08 11:28:35 +:
>> On 05/08/2016 19:15, Doug Hellmann wrote:
>>> Excerpts from Hayes, Graham's message of 2016-08-05 17:04:35 +:
Hey,
We look like we are getting close to merging th
+1
This validation in neutron is redundant.
/ludovic
-Original Message-
From: Moshe Levi [mailto:mosh...@mellanox.com]
Sent: August-08-16 8:43 AM
To: OpenStack Development Mailing List (not for usage questions)
(openstack-dev@lists.openstack.org)
Subject: [openstack-dev] [neutron][nova
Hi,
This is a reminder that we’ll have a team meeting today at #openstack-meeting
at 16.00 UTC.
Agenda:
Review action items
Current status (progress, issues, roadblocks, further plans)
Open discussion
Renat Akhmerov
@Nokia
__
On 03.08.2016 22:02, Znoinski, Waldemar wrote:
> Thanks
> Much appreciated
>
> Making use of the opportunity here... what's the next big thing a CI (like
> one testing NFV) should be doing? (multinode or there's something else more
> important?)
Two tiny nits on the comment the CI is giving a c
Markus Zoeller said on Mon, Aug 08, 2016 at 01:29:49PM +0200:
> On 08.08.2016 13:07, Alexis Lee wrote:
> > I propose the ant, known for discovering probabilistic graph traversal
> > algorithms.
> >
> > My other thought, the bee, has already been taken by refstack.
>
> AFAIK #infra is going to cho
On 08/08/2016 05:07 AM, Alexis Lee wrote:
I propose the ant, known for discovering probabilistic graph traversal
algorithms.
My other thought, the bee, has already been taken by refstack.
How about the octopus, since nova has tentacles reaching into many parts of the
system...
Chris
_
On 08/08/2016 11:05 AM, Hugh Brock wrote:
On Wed, Aug 3, 2016 at 4:49 PM, Joe Talerico wrote:
On Wed, Jul 27, 2016 at 2:04 AM, Hugh Brock wrote:
On Jul 26, 2016 8:08 PM, "Gordon, Kent"
wrote:
-Original Message-
From: Gonéri Le Bouder [mailto:gon...@lebouder.net]
Sent: Tuesday
On Mon, Aug 08, 2016 at 02:40:31PM +0200, Ihar Hrachyshka wrote:
> Hi,
>
> I was looking at grafana today, and spotted another weirdness.
>
> See the periodic jobs dashboard:
>
> http://grafana.openstack.org/dashboard/db/neutron-failure-rate?panelId=4&fullscreen
>
> Currently it shows for me 10
On Sat, Aug 06, 2016 at 08:00:06PM -0400, Ben Swartzlander wrote:
> On 08/06/2016 06:11 PM, Jeremy Stanley wrote:
> >On 2016-08-06 17:51:02 -0400 (-0400), Ben Swartzlander wrote:
> >[...]
> >>when it's no longer to run dsvm jobs on them (because those jobs
> >>WILL eventually break as infra stops m
On 08/08/2016 06:14 AM, Chris Dent wrote:
On Mon, 8 Aug 2016, Alex Xu wrote:
Chris, thanks for the blog to explain your idea! It helps me understand
your idea better.
Thanks for reading it. As I think I've mentioned a few times I'm not
really trying to sell the idea, just make sure it is clea
In accordance with the spec[1], I started a patch[2] to port security
related items from mistral to mistral-lib. This may not be the right way
to approach this task and I'm hoping the patch provides a means to
illustrate the problem and starts a discussion on the right solution.
A custom action t
On Mon, Aug 8, 2016 at 4:02 PM, Tomas Sedovic wrote:
> On 08/08/2016 11:05 AM, Hugh Brock wrote:
>>
>> On Wed, Aug 3, 2016 at 4:49 PM, Joe Talerico wrote:
>>>
>>> On Wed, Jul 27, 2016 at 2:04 AM, Hugh Brock wrote:
On Jul 26, 2016 8:08 PM, "Gordon, Kent"
wrote:
>
>
>>
Matthew Treinish wrote:
On Mon, Aug 08, 2016 at 02:40:31PM +0200, Ihar Hrachyshka wrote:
Hi,
I was looking at grafana today, and spotted another weirdness.
See the periodic jobs dashboard:
http://grafana.openstack.org/dashboard/db/neutron-failure-rate?panelId=4&fullscreen
Currently it show
>
> Unless you manage to get it approved for the global policy, I think
> you will effectively make your stable:follows-policy tag obsolete,
> and then it should be removed from your project. Read the
> requirements:
>
> https://governance.openstack.org/reference/tags/stable_follows-policy.html#r
Great work with that multi-node setup Miguel.
About that multinode Infra is supporting two nodes setup used currently by
grenade jobs but in my opinion we don’t have any tests which can cover that
type of testing. We’re still struggling with selecting proper tool to test
Octavia from integration
In summary, it turns out we learned a few things:
1) neutron guests in our gate runs don't have the ability to route
outwards. For instance, if they tried to do a package update, it would fail.
2) adding the ability for them to route outwards (as would be expected
for things like package updates)
On 08/08/2016 07:48 AM, Steven Dake (stdake) wrote:
Cool thanks for the response. Appreciate it. I think the big take away
is all the ODMs are free from churn in Newton and have a full cycle to
adapt to the changes which is great news!
Yes, that is absolutely the case.
Best,
-jay
__
We are enthusiastic to announce the release of:
django_openstack_auth 2.4.0: Django authentication backend for use
with OpenStack Identity
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/django_openstack_auth/
With packag
Change deployed,
Thanks for your comments,
Michal
-Original Message-
From: Markus Zoeller [mailto:mzoel...@linux.vnet.ibm.com]
Sent: Monday, August 08, 2016 3:15 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission
On 03.08.
On 08/07/2016 11:16 PM, Adam Young wrote:
On 08/06/2016 08:44 AM, John Dennis wrote:
On 08/05/2016 06:06 PM, Adam Young wrote:
Ah...just noticed the redirect is to :5000, not port :13000 which is
the HA Proxy port.
OK, this is due to the SAML request:
https://identity.ayoung-dell-t1700.test
On Mon, Aug 08, 2016 at 09:47:53AM -0500, Sean McGinnis wrote:
> >
> > Unless you manage to get it approved for the global policy, I think
> > you will effectively make your stable:follows-policy tag obsolete,
> > and then it should be removed from your project. Read the
> > requirements:
> >
> >
On 08/06/2016 07:17 PM, Paul Belanger wrote:
> Greetings,
>
> 5 months ago fungi posted:
>
> [tripleo] becoming third party CI (was: enabling third party CI)[1]
>
> About having the discussion whether the existing TripleO CI should itself
> follow
> our third-party integration model instead o
On Sat, Aug 6, 2016 at 8:17 PM, Paul Belanger wrote:
> Greetings,
>
> 5 months ago fungi posted:
>
> [tripleo] becoming third party CI (was: enabling third party CI)[1]
>
> About having the discussion whether the existing TripleO CI should itself
> follow
> our third-party integration model ins
Miguel,
Thank you for your work here. I would support an effort to setup a
multi-node gate job.
Michael
On Mon, Aug 8, 2016 at 5:04 AM, Miguel Angel Ajo Pelayo
wrote:
> Recently, I sent a series of patches [1] to make it easier for
> developers to deploy a multi node octavia controller with
>
Hi Akshay,
Currently we are only allowing one VIP per amphora.
You can log into the amphora if you specify a ssh keypair loaded into
nova in the octavia.conf file. When that is specified you can log
into the amphora via SSH on the management network interface.
Michael
On Mon, Aug 1, 2016 at 5:
On 2016-08-08 17:09:33 +0800 (+0800), 吕冬兵 wrote:
> I uploaded a new project to gerrit, but test-requirement.txt had
> duplicate entries by mistake. That makes jenkins fail whatever I
> commit
> (http://logs.openstack.org/58/351458/7/check/gate-python-bileanclient-requirements/017cd3a/console.html).
On my brief participation on Manila team I've find Tom contributions to be
very helpful. I think he will be a great addition!
2016-08-04 11:16 GMT-03:00 Sean McGinnis :
> I have zero say here, but just want to say Tom is always a great guy to
> have around and knows his stuff. +1 from me that he
On 2016-08-08 11:20:54 +0200 (+0200), Miguel Angel Ajo Pelayo wrote:
> The problem with the other projects image builds is that they are
> based for bigger systems, while cirros is an embedded-device-like
> image which boots in a couple of seconds.
Yep, smaller is certainly better when it comes to
On 05/08/16 12:01, Hongbin Lu wrote:
Add [heat] to the title to get more feedback.
Best regards,
Hongbin
*From:*Ricardo Rocha [mailto:rocha.po...@gmail.com]
*Sent:* August-05-16 5:48 AM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [magnu
On Mon, Aug 8, 2016 at 11:47 AM, James Slagle wrote:
> On Sat, Aug 6, 2016 at 8:17 PM, Paul Belanger wrote:
>> Greetings,
>>
>> 5 months ago fungi posted:
>>
>> [tripleo] becoming third party CI (was: enabling third party CI)[1]
>>
>> About having the discussion whether the existing TripleO CI
On 2016-08-08 06:00:14 -0500 (-0500), e...@itsonlyme.name wrote:
[...]
> One solution we were thinking of is having a VM image that
> contains the Docker image we need (e.g. saved using docker save),
> thus bypassing the need to do "docker pull". Is that possible? I
> realise that so far probably d
On 2016-08-08 13:03:51 +0200 (+0200), Ihar Hrachyshka wrote:
> Sean McGinnis wrote:
[...]
> > The suggestion was to just change our stable policy in regards to driver
> > bugfix backports. No need to create and maintain more branches. No need
> > to set up gate jobs and things like that.
>
> Unle
Has the use case been considered where the compute nodes have no nat to the
internet?
The glare api server might have to pass the data through to the requesting
client in that case or download/cache an internal copy.
Thanks,
Kevin
From: Mikhail Fedosin [mfedo...
I'd like to nominate Luke for a CoreSec position as part of the Security
Project.
CoreSec team members support the VMT with extended consultation on
externally reported vulnerabilities.
Luke has been an active member of the Security project for quite some time.
He's done significant recent work o
On 8 August 2016 at 18:31, Matthew Treinish wrote:
>
> This argument comes up at least once a cycle and there is a reason we
> don't do
> this. When we EOL a branch all of the infrastructure for running any ci
> against
> it goes away. This means devstack support, job definitions, tempest skip
>
Mike was kind enough to drop by the IRC channel today to help the
operational deployment managers (ODMs) understand the impact of Glare for
technical planning purposes.
The log of the discussion is here:
http://eavesdrop.openstack.org/irclogs/%23openstack-kolla/%23openstack-koll
a.2016-08-08.log.h
On 2016-08-08 14:26:18 +0100 (+0100), Alexis Lee wrote:
> Markus Zoeller said on Mon, Aug 08, 2016 at 01:29:49PM +0200:
> > On 08.08.2016 13:07, Alexis Lee wrote:
> > > I propose the ant, known for discovering probabilistic graph traversal
> > > algorithms.
> > >
> > > My other thought, the bee, h
Tempest devs,
Let me please draw your attention to a LP bug that may not seem
particularly high priority, but I believe could be resolved easily with
a patch already proposed.
LP bug 1536251 [1] accurately states that Tempest is actively verifying
that an OpenStack API call violates RFC 7230
On 2016-08-08 09:33:20 -0700 (-0700), Rob C wrote:
> I'd like to nominate Luke for a CoreSec position as part of the Security
> Project.
[...]
Sounds good to me. Luke's feedback on security bugs so far has been
quite helpful, so I'm all for encouraging more of the same.
This would bring the "OSSG
On 2016-08-08 11:47:56 -0400 (-0400), James Slagle wrote:
[...]
> I suppose it's also possible that we might be pushing too strongly
> down the multinode path? Is the general concensus in infra that they'd
> like to help enable project teams to eventually add 3 and 4 (and maybe
> more) node multino
Greetings,
I would like to nominate David Ames for addition to the
charms-release team, as he has played a valuable role in the charm release
processes. This change will grant privileges such as new stable branch
creation, among other things necessary to facilitate the charm release
process.
Ch
http://www.openstack.org/blog/2016/08/openstack-developer-mailing-list-digest-20160805/
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?sub
On 8 August 2016 at 08:01, Sean Dague wrote:
> In summary, it turns out we learned a few things:
>
> 1) neutron guests in our gate runs don't have the ability to route
> outwards. For instance, if they tried to do a package update, it would
> fail.
>
> 2) adding the ability for them to route outw
> Ok, to turn the question around, we (the cinder team) have recognised a
> definite and strong need to have somewhere for vendors to share patches on
> versions of Cinder older than the stable branch policy allows.
>
> Given this need, what are our options?
>
> 1. We could do all this outside Op
On Mon, Aug 8, 2016 at 1:06 PM, Jeremy Stanley wrote:
> On 2016-08-08 11:47:56 -0400 (-0400), James Slagle wrote:
> [...]
>> I suppose it's also possible that we might be pushing too strongly
>> down the multinode path? Is the general concensus in infra that they'd
>> like to help enable project t
On 08/08/2016 12:40 PM, Duncan Thomas wrote:
On 8 August 2016 at 18:31, Matthew Treinish mailto:mtrein...@kortar.org>> wrote:
This argument comes up at least once a cycle and there is a reason
we don't do
this. When we EOL a branch all of the infrastructure for running any
ci ag
On 08/08/2016 12:36 PM, Jeremy Stanley wrote:
On 2016-08-08 13:03:51 +0200 (+0200), Ihar Hrachyshka wrote:
Sean McGinnis wrote:
[...]
The suggestion was to just change our stable policy in regards to driver
bugfix backports. No need to create and maintain more branches. No need
to set up gate
On Mon, Aug 08, 2016 at 07:40:56PM +0300, Duncan Thomas wrote:
> On 8 August 2016 at 18:31, Matthew Treinish wrote:
>
> >
> > This argument comes up at least once a cycle and there is a reason we
> > don't do
> > this. When we EOL a branch all of the infrastructure for running any ci
> > against
+1 on this plan too, if the +2's I've been slinging haven't made it
obvious :)
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
Hi James,
Networking-sfc will release Newton version after Neutron pull the stable/Newton
branch (around late Oct. and Early Nov time frame).
Basically after the branch is pulled, we will make sure all unit, functional,
tempest tests including multi-node end-to-end tests against stable/Newton
b
I second the supernova concept. I'm just not a huge fan of an animal.
Unless it's a Tardigrade.
I found some cartoonish things that show a supernova could be
graphically stylized:
* https://heasarc.gsfc.nasa.gov/Images/objects/snrs/SNR_cartoon2.gif
*
http://coffeeshopphysics.com/articles/2011-10/1
If you have any topic for our weekly meeting, please add it here:
https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160809
See you tomorrow,
On Tue, Aug 2, 2016 at 11:06 AM, Emilien Macchi wrote:
> no item in our agenda, we cancelled the meeting, see you next week!
>
> On Mon, A
On 8/8/2016 6:07 AM, Alexis Lee wrote:
I propose the ant, known for discovering probabilistic graph traversal
algorithms.
My other thought, the bee, has already been taken by refstack.
lxsli
__
OpenStack Development Maili
1 - 100 of 121 matches
Mail list logo
