makes sense to me. thanks for concise update and tracking this.
On 10/02/2016 7:59 AM, Davanum Srinivas wrote:
> +1 from me
>
> On Wed, Feb 10, 2016 at 7:56 AM, Jay Pipes wrote:
>> On 02/10/2016 07:33 AM, Sean Dague wrote:
>>>
>>> The largeops tests at this point are mostly
Summary: Liberty OVS agent restarts are better, but still need work.
See: https://bugs.launchpad.net/neutron/+bug/1514056
As many of you know, Liberty has a fix for OVS agent restarts such
that it doesn’t dump all flows when starting, resulting in a loss of
traffic. Unfortunately, Liberty
Hi Basavaraj:
The most common way to install an application at deployment time is to
run a shell script that uses wget/curl/apt-get/yum to retrieve the
binary from a repository and then installs the software and
configures/runs it.
We don't have any examples of this in the Tacker repo yet
Hello,
We're in the process of adding IGMP and multicast support to Dragonflow[1]. The
added feature will route multicast packets only to relevant and registered VMs,
compute nodes, and handle IGMP packets.
This feature has some configuration parameters for subnets and router
interfaces.
Some
I would be happy if resize is going to smaller flavor, nova just change
CPU and RAM, didn't try to change disk to smaller. But it doesn't work.
In search I found that it should work like that, resize with KVM just
change CPU and RAM, but disk stay same, if flavor have smaller disk.
Maybe this
The gate-manila-tempest-dsvm-hdfs jenkins job has been failing for a
long time now. It appears to be a config issue that's probably not hard
to fix, but nobody is actively maintaining this code.
Since it's a waste of resources to continue running this broken job, I
plan to disable it, and if
Hi,
I'm doing a university project in OpenStack. The aim is to monitor virtual
routers per tenant with Monasca(which according to my knowledge hasn't been
implemented yet). The initial features would include monitoring of in/out
traffic per interface. I'm writing a plugin in Monasca for that
We stopped running tests under python 2.6 a while back, and I submitted
a bunch of patches to projects that still had the python package
classifier indicating support for python 2.6. Most of those merged, but
quite a few are still open [1]. Please take a look at the list and if
you find any for
Thanks Neil, very helpful.
From: neil.jer...@metaswitch.com
Subject: Re: [Openstack-operators] Anyone using Project Calico for tenant
networking?
Hi Ned,
Sorry for the delay in following up here.
On 06/02/16 14:40, Ned Rhudy (BLOOMBERG/ 731 LEX) wrote:
> Thanks. Having read the
This is a work we are doing in Dragonflow and is relatively simple to
implement leveraging
Dragonflow current infrastructure and reactive local controller.
This will significantly reduce duplicating packets for IGMP aware VMs. and
hence
reduce multicast load.
We would love to help and bring this
Lots of questions, I'm sorry.
Are you planning to drop them indefinitely or is it temporary ? Is it to
help alleviate the gate from it's current misery ?
Why were these tests introduced in the first place ? To find issues or
bottenecks relative to scale or amount of operations ? Was it a request
+1, although I would like to keep them to find scale bottlenecks. Maybe when
the new infra-cloud is up (we'll have full control over it, includind hw
access), we can pin these tests just to it.
Ghe Rivero
Quoting Sean Dague (2016-02-10 13:33:44)
> The largeops tests at this point are mostly
On 02/10/2016 08:42 AM, David Moreau Simard wrote:
> Lots of questions, I'm sorry.
>
> Are you planning to drop them indefinitely or is it temporary ? Is it to
> help alleviate the gate from it's current misery ?
>
> Why were these tests introduced in the first place ? To find issues or
>
Yes, with Cinder resize works, and volume resize is separated function.
But my issue is when I use VM boot from image, without using cinder,
using CEPH directly in nova.
On 2016.02.10. 16:49, Alberto Molina Coballes wrote:
Sorry Mārtiņš, my previous comment wasn't completely correct.
I'm
On 10/02/16 07:33 -0500, Sean Dague wrote:
The largeops tests at this point are mostly finding out that some of our
new cloud providers are slow - http://tinyurl.com/j5u4nf5
This is fundamentally a performance test, with timings having been tuned
to pass 98% of the time on two clouds that were
Hello All,
I just want to integrate my sample application which has to run
automatically upon VNF instantaiation. And I am using Tacker service as
well.
Can someone please give me pointers on it.
Regards,
Basavaraj
___
Mailing list:
We are delighted to announce the release of:
reno 1.5.0: RElease NOtes manager
With source available at:
http://git.openstack.org/cgit/openstack/reno
With package available at:
https://pypi.python.org/pypi/reno
Please report issues through launchpad:
On mié, feb 10, 2016 at 12:41:42 +0200, Mārtiņš Jakubovičs wrote:
> Hello,
>
> Looks like it is not working, when I try to resize instance I receive:
> Server disk was unable to be resized because: Resize to zero disk flavor is
> not allowed.
>
Sorry Mārtiņš, my previous comment wasn't
On Fri, Feb 5, 2016 at 4:46 PM, Eric LEMOINE wrote:
> Hi Kolla devs
>
> The other day inc0 said that we would like "central logging" to be
> optional in Mitaka, and still use Rsyslog and keep the current
> behavior if "central logging" is disabled.
>
> I would like to
There could be situations where resizing (up or down) an instance could be an
option (like critical non-ha services although this is a real bad policy) but
the proper way to operate a cloud is to spin up and kill as many instances as
needed. But if you really need to shrink an instance, it's
Thanks Robert for the update.
Regards,
Basavaraj
On Wed, Feb 10, 2016 at 8:15 PM, HADDLETON, Robert W (Bob) <
bob.haddle...@nokia.com> wrote:
> Hi Basavaraj:
>
> The most common way to install an application at deployment time is to run
> a shell script that uses wget/curl/apt-get/yum to
Sean Dague wrote:
The largeops tests at this point are mostly finding out that some of our
new cloud providers are slow - http://tinyurl.com/j5u4nf5
This is fundamentally a performance test, with timings having been tuned
to pass 98% of the time on two clouds that were very
Hi,
I'm doing a university project in OpenStack. The aim is to monitor virtual
routers per tenant with Monasca(which according to my knowledge hasn't been
implemented yet). The initial features would include monitoring of in/out
traffic per interface. I'm writing a plugin in Monasca for that
We are happy to announce the release of:
neutron 7.0.3: OpenStack Networking
This release is part of the liberty stable release series.
With package available at:
https://pypi.python.org/pypi/neutron
For more details, please see below.
7.0.3
^
An OVS agent configured to run in DVR
We are amped to announce the release of:
neutron-vpnaas 7.0.3: OpenStack Networking VPN as a Service
This release is part of the liberty stable release series.
With package available at:
https://pypi.python.org/pypi/neutron-vpnaas
For more details, please see below.
Changes in
> - Message from Remo Mattei on Tue, 9 Feb 2016
> 07:21:17 -0800 -
>
> To:
>
> Ludwig Tirazona
>
> cc:
>
> openstack@lists.openstack.org
>
> Subject:
>
> Re: [Openstack] I can't get nova-novncproxy to listen on the specified
address
>
>
On 1/29/2016 12:08 AM, Renat Akhmerov wrote:
On 28 Jan 2016, at 17:40, Matt Riedemann wrote:
With regards to the trove 'plugin' stuff, it adds a new dependency on
python-troveclient which was not in sahara 1.0.0 in liberty GA, so IMO it's not
valid to release
Excerpts from Thierry Carrez's message of 2016-02-10 08:35:19 -0800:
> Chris Dent wrote:
> > [...]
> > Observing this thread and "the trouble with names"[1] one I get
> > concerned that we're trending in the direction of expecting
> > projects/servers/APIs to be done and perfect before they will
We are eager to announce the release of:
neutron-lbaas 7.0.3: OpenStack Networking Load Balancing as a Service
This release is part of the liberty stable release series.
With package available at:
https://pypi.python.org/pypi/neutron-lbaas
For more details, please see below.
Changes in
Chris Dent wrote:
[...]
Observing this thread and "the trouble with names"[1] one I get
concerned that we're trending in the direction of expecting
projects/servers/APIs to be done and perfect before they will ever
be OpenStack. This, of course, runs entirely contrary to the spirit
of open
Michael Still writes:
> On Tue, Feb 9, 2016 at 4:59 AM, Joshua Hesketh
> wrote:
>
>> On Thu, Feb 4, 2016 at 2:44 AM, James E. Blair
>> wrote:
>>>
>>> On the subject of clearing the cache more often, I think we may not want
>>>
It changes mostly nothing for case of furious plugin development when big
parts of code changed from one release to another.
You will have 6 different deployment_tasks directories and 30 a little bit
different files in root directory of plugin. Also you forgot about
repositories directory (+6 at
Colleagues,
Centos bootstrap image (that we used to build together with the ISO) code
has been removed from fuel-main. Now the only available option is the
Ubuntu based bootstrap image that is built on the master node in run time.
>From this moment we are ready to get rid of building Fuel
Ihar Hrachyshka wrote:
> UPD: seems like enforcing instance mtu to 1400 indeed makes us pass forward
> into tempest:
>
> http://logs.openstack.org/59/265759/3/experimental/gate-grenade-dsvm-neutron-multinode/a167a59/console.html
>
> And there are only three failures there:
>
>
ick! yes Ghe, agree but I would not advice this process, even though I have
done this many time and works a huge % of the time, it’s not a save solution.
parted then will be better if he really needs to address this resize and yes to
keep in mind that XFS does not resize down at all. So the
Sean M. Collins wrote:
Ihar Hrachyshka wrote:
UPD: seems like enforcing instance mtu to 1400 indeed makes us pass
forward
into tempest:
http://logs.openstack.org/59/265759/3/experimental/gate-grenade-dsvm-neutron-multinode/a167a59/console.html
And there are only three
Excerpts from Sean Dague's message of 2016-02-10 04:33:44 -0800:
> The largeops tests at this point are mostly finding out that some of our
> new cloud providers are slow - http://tinyurl.com/j5u4nf5
>
> This is fundamentally a performance test, with timings having been tuned
> to pass 98% of the
Ihar Hrachyshka wrote:
> Actually, we already have 1450 for network_device_mtu for the job since:
>
> https://review.openstack.org/#/c/267847/4/devstack-vm-gate.sh
>
Ah! Forgot about that one. Cool.
> Also, I added some interface state dump for worlddump, and here is how the
> main node
On Wed, Feb 10, 2016 at 4:57 PM, Steven Hardy wrote:
> Hi all,
>
> We discussed this in our meeting[1] this week, and agreed a ML discussion
> to gain consensus and give folks visibility of the outcome would be a good
> idea.
>
> In summary, we adopted a more permissive
Hello, John
Note, that digit "4" defines amount of "python code blocks", not "python
code lines". So, you can have uncovered some log message that consists of
100 lines. But it will be counted as just 1.
Who "we" have requirement that new drivers have 90% unit test coverage?
And, Manila CI
Hi,
I noticed that the coverage script is enforcing a hard limit of 4 on
the number of extra missing lines introduced. We have a requirement
that new drivers have 90% unit test coverage, which the ceph driver
meets[1], but it's tripping up on that absolute 4 line limit.
What do folks think
On 10/02/16 18:48, "Clint Byrum" wrote:
>Excerpts from Sean Dague's message of 2016-02-10 04:33:44 -0800:
>> The largeops tests at this point are mostly finding out that some of our
>> new cloud providers are slow - http://tinyurl.com/j5u4nf5
>>
>> This is fundamentally a
Hi,
I'm doing a university project in OpenStack. The aim is to monitor virtual
routers per tenant with Monasca(which according to my knowledge hasn't been
implemented yet). The initial features would include monitoring of in/out
traffic per interface. I'm writing a plugin in Monasca for that
Hi, John. This is but one reason the coverage job doesn¹t vote; it has
other known issues. It is primarily a convenience tool that lets core
reviewers know if they should look more deeply into unit test coverage.
For a new driver such as yours, I typically pull the code and check
coverage for
Devstack has some half baked support for keystone templated service
catalog. In an effort to clean up parts of devstack, we're dropping that
- https://review.openstack.org/#/c/278333
However... this unfortunately led to some cargo culting, and everyone's
devstack plugin is going to fail if we
Hi,
I accidentally ran the meeting early, due to not having re-downloaded a
fresh iCal export. So I had the wrong time.
For background:
https://github.com/openstack-infra/yaml2ical/commit/4def663a8d5259962d5c2239266ebfaa19082bf6
So anyway, please ensure that your calendar is updated with a
Hi,
the pep8 target is our usual target to include style and lint checks and
thus is used besides pep8 also for doc8, bashate, bandit, etc as
documented in the PTI (=Python Test Interface,
http://governance.openstack.org/reference/cti/python_cti.html).
We've had some discussions to introduce a
On Tue, Feb 9, 2016 at 1:21 PM, Kevin Benton wrote:
> If you see any issues, either propose a patch directly or file a bug against
> https://bugs.launchpad.net/openstack-manuals/+filebug with the tag
> 'seg-guide'
Did you want 'sec-guide'? That would seem more intuitive to me.
On 10/02/2016 11:35 AM, Thierry Carrez wrote:
> Chris Dent wrote:
>> [...]
>> Observing this thread and "the trouble with names"[1] one I get
>> concerned that we're trending in the direction of expecting
>> projects/servers/APIs to be done and perfect before they will ever
>> be OpenStack.
On 10/02/16 21:53, "gordon chung" wrote:
>
>
>On 10/02/2016 11:35 AM, Thierry Carrez wrote:
>> Chris Dent wrote:
>>> [...]
>>> Observing this thread and "the trouble with names"[1] one I get
>>> concerned that we're trending in the direction of expecting
>>> projects/servers/APIs
On 02/04/2016 06:38 AM, Sean Dague wrote:
> 2) Have a registry of "common" names.
>
> Upside, we can safely use common names everywhere and not fear collision
> down the road.
>
> Downside, yet another contention point.
>
> A registry would clearly be under TC administration, though all the
>
On Mon, Feb 8, 2016 at 9:40 AM, Assaf Muller wrote:
> As for DVR, I'm searching for someone to pick up the gauntlet and
> contribute some L3 fullstack tests. I'd be more than happy to review
> it! I even have an abandoned patch that gets the ball rolling (The
> idea is to test
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/05/2016 01:16 PM, Sean Dague wrote:
> Whether or not it is, I'm not sure how it is part of a Ubiquitous
> Open Source Cloud Platform. Because it only enables the use of
> commerical services.
>
> It's fine that it's open source software. I
Yes, sorry.
On Feb 10, 2016 12:52, "Carl Baldwin" wrote:
> On Tue, Feb 9, 2016 at 1:21 PM, Kevin Benton wrote:
> > If you see any issues, either propose a patch directly or file a bug
> against
> > https://bugs.launchpad.net/openstack-manuals/+filebug with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/05/2016 01:27 PM, Mike Perez wrote:
>>> So while Poppy may not fully qualify for the open core label,
>>> it still fails some of the tests that we want to see, such as a
>>> usable open source implementation.
>> From a QA perspective in
There's two main types of services in openstack. Those that are a multitenant
aware implementation of some kind of data plane protocol with an "openstack"
api. Swift/radosgw, Zaqar, MagnetoDB, etc. I think we can ignore these in this
discussion.
Then there's what I consider the more "Operating
Georgios, Martin, and others:
Once this rework of Fuel build process is done, we'll definitely
announce it on openstack-dev ML (using [fuel] tag in the subject, hint
hint :). You can also track the progress of this work in the blueprint:
Hi Dilip,
Can you please clarify your question? If a driver reports both
thin_provisioning and thick_provisioning to True and reports free_capacity
based on thin provisioning , and you want to provision a thick volume, the
scheduler won’t block it and it fail when the driver tries to create
Clayton,
This is really good information.
I’m wondering how we can help support you and get the necessary dev support to
get this resolved sooner than later. I totally agree with you that this should
be backported to at least Liberty.
Please let me know how I and other can help!
—Joe
On Tue, Feb 9, 2016 at 3:23 PM, Ildikó Váncsa
wrote:
> Hi Walt,
>
> > -Original Message-
> > From: Walter A. Boring IV [mailto:walter.bor...@hpe.com]
> > Sent: February 09, 2016 23:15
> > To: openstack-dev@lists.openstack.org
> > Subject: Re: [openstack-dev]
On 02/10/2016 03:03 PM, Sean Dague wrote:
On 02/04/2016 06:38 AM, Sean Dague wrote:
2) Have a registry of "common" names.
Upside, we can safely use common names everywhere and not fear collision
down the road.
Downside, yet another contention point.
A registry would clearly be under TC
+1 to Stas, supplanting VCS branches with code duplication is a path to
madness and despair. The dubious benefits of a cross-release backwards
compatible plugin binary are not worth the code and infra technical debt
that such approach would accrue over time.
On Wed, Feb 10, 2016 at 07:36:30PM
On Wed, Feb 10, 2016 at 5:06 AM, Neil Jerram wrote:
> In terms of how floating IPs are represented in the Neutron data model:
> currently they require a relationship between an external Network, a
> Router and a tenant Network. The floating IP pool is defined as a
>
On Wed, Feb 10, 2016 at 03:30:42PM -0700, John Griffith wrote:
> On Tue, Feb 9, 2016 at 3:23 PM, Ildikó Váncsa
> wrote:
>
> >
> This may still be in fact the easiest way to handle this. The only other
> thing I am still somewhat torn on here is that maybe Nova
On 2016-02-09 01:32:12 +0800 (+0800), Thomas Goirand wrote:
> While it is a good idea to enhance the current Ubuntu image, at the same
> time, I'd like to draw your attention that we need review for adding the
> Debian image too:
> https://review.openstack.org/#/c/264726
>
> Igor Belikov did an
Hi Heat team,
As mentioned in IRC, magnum gate broke with bug 1544227 . Rabi submitted on a
fix (https://review.openstack.org/#/c/278576/), but it doesn't seem to be
enough to unlock the broken gate. In particular, it seems templates with
SoftwareDeploymentGroup resource failed to complete (I
On 10/02/16 18:05, James Slagle wrote:
On Wed, Feb 10, 2016 at 4:57 PM, Steven Hardy > wrote:
Hi all,
We discussed this in our meeting[1] this week, and agreed a ML
discussion
to gain consensus and give folks visibility of the
Hey everybody,
tl;dr - We have new AFS-based consistent per-region mirrors of PyPI and
APT repos with additional wheel repos containing pre-built wheels for
all the modules in global-requirements
We've just rolled out a new change that you should mostly never notice -
except that jobs
I started noticing more of the Trove gate jobs failing in the last 24 hours
and I think i've tracked it down to this mirror specifically.
http://mirror.bhs1.ovh.openstack.org/ubuntu/pool/main/p/
It looks like its missing the python-software-properties package and
causing our gate job to fail. I
Sean Dague wrote:
[...]
3) This be a dedicated repository 'openstack/service-registry'. The API
WG will have votes on it (I would also suggest the folks that have been
working on Service Catalog TNG - myself, Anne Gentle, Brant Knudson, and
Chris Dent be added to this). The actual registry will
On Wed, Feb 10, 2016 at 5:12 PM, Fox, Kevin M wrote:
> But the issue is, when told to detach, some of the drivers do bad things.
> then, is it the driver's issue to refcount to fix the issue, or is it
> nova's to refcount so that it doesn't call the release before all users
On 2016-02-11 14:41:03 +1100 (+1100), Tony Breeds wrote:
[...]
> Okay We'll need to think about that one as the contrainst in
> stable/kilo can be bogus, sometime we have a version in contraints
> that isn't valid compared to g-r
[...]
Oh, right since there's an upper-constraints.txt in
I think Sean and John are in the right direction. Nova and Cinder need to
be more decoupled in the area of volume attachments.
I think some of the mess here is due to different Cinder backend behavior -
with some Cinder backends you actually attach volumes to a host (e.g., FC,
iSCSI), with some
Hi,
We did some analysis of the issue you are facing.
One of the issues from heat side is, we convert None(singleton) resource
references
to 'None'(string) and the translation logic is not ignoring them. Though we
don't
apply translation rules to resource references[1].We don't see this issue
I agree with Stas, one rpm - one version.
But plugin builder allows to specify several releases as compatible. The
deployment tasks and repositories can be specified per release, at the same
time the deployment graph is one for all releases.
Currently it looks like half-implemented feature.
On 11/02/16 00:33, "gordon chung" wrote:
>
>
>On 10/02/2016 4:28 PM, Tim Bell wrote:
>>
>> On 10/02/16 21:53, "gordon chung" wrote:
>>
>>> apologies if this was asked somewhere else in thread, but should we try
>>> to define "production" scale or can we even? based
On Wed, Feb 10, 2016 at 07:07:22PM -0800, Clark Boylan wrote:
> On Wed, Feb 10, 2016, at 06:02 PM, Tony Breeds wrote:
> > On Wed, Feb 10, 2016 at 06:45:25PM -0600, Monty Taylor wrote:
> > > Hey everybody,
> > >
> > > tl;dr - We have new AFS-based consistent per-region mirrors of PyPI and
> > >
Right now master (targeting 9.0) is still deploying liberty and there is
active work going on to support both Kilo and Mitaka. On the review queue
are changes that would make fuel-library in-compatible with the prior
(liberty) openstack release. However I think if we extend a little bit of
effort
On Thu, Feb 11, 2016 at 04:46:39AM +, Jeremy Stanley wrote:
> On 2016-02-11 14:41:03 +1100 (+1100), Tony Breeds wrote:
> [...]
> > Okay We'll need to think about that one as the contrainst in
> > stable/kilo can be bogus, sometime we have a version in contraints
> > that isn't valid compared
Thanks Lenny.
So I think I should clean up this dir from time to time.
From: Lenny Verkhovsky [len...@mellanox.com]
Sent: Wednesday, February 10, 2016 2:49 AM
To: Wan, Sam
Cc: OpenStack Infra
Subject: RE: [OpenStack-Infra] weird 'Merge Failed.' message
Thanks,
But how at least I can setup that if I change offering to lower it
change just CPU and RAM and if root disk size in offering is smaller
than actually in instance, nova don't try to change it to smaller?
Best regards,
Martins
On 2016.02.10. 03:23, Remo Mattei wrote:
Resize down on
I prefer waiting for infra team response.
-Original Message-
From: Wan, Sam [mailto:sam@emc.com]
Sent: Wednesday, February 10, 2016 9:56 AM
To: Lenny Verkhovsky
Cc: OpenStack Infra
Subject: RE: [OpenStack-Infra] weird 'Merge
Seems like it found a host to schedule it on (ODL-CN-1-2GB)
Selected host: WeighedHost [host: (ODL-CN-1-2GB, ODL-CN-1-2GB) ram:1481
disk:9216 io_ops:0 instances:0, weight: 0.0231877250665]
_schedule /opt/stack/nova/nova/scheduler/filter_scheduler.py:158
But launching that instance on this host
Good morning,
I was reading the Fuel documentation and I am interested in the eighth point
from https://wiki.openstack.org/wiki/Fuel#What_is_Fuel.3F
And I was thinking if it's possible to build a SUSE Linux image using the SUSE
ISO images. Could I build it?
P.S. I read this too
victor.martinalo...@altran.com
De: openstack-requ...@lists.openstack.org
[openstack-requ...@lists.openstack.org]
Enviado: miércoles, 10 de febrero de 2016 11:08
Para: Martin Alonso Victor
Asunto: Welcome to the "Openstack" mailing list (Digest mode)
Hello,
Looks like it is not working, when I try to resize instance I receive:
Server disk was unable to be resized because: Resize to zero disk flavor
is not allowed.
Maybe there is some nova configuration which allow to scale down
instance without shrinking root disk?
Best regards,
On Tue, 9 Feb 2016, Chris Dent wrote:
eventlet 0.18.2 has broken the nova unit tests at
'nova.tests.unit.test_wsgi.TestWSGIServerWithSSL' so the gate is
blocked.
sdague et al are working on it. Please hold off approving patches
in nova until they get it resolved.
Just in case it's not
Hi all,
Unfortunately today's meeting of the Telco Working Group [1] is canceled, my
apologies for the late notice!
Thanks,
Steve
[1] https://wiki.openstack.org/wiki/TelcoWorkingGroup
__
OpenStack Development Mailing
Hi all,
Unfortunately today's meeting of the Telco Working Group [1] is canceled, my
apologies for the late notice!
Thanks,
Steve
[1] https://wiki.openstack.org/wiki/TelcoWorkingGroup
___
OpenStack-operators mailing list
Folks
I think the easiest and the best option here is to boot iPXE or pxelinux
with NFS and put master node image onto an NFS mount. This one should work
seamlessly.
On Wed, Feb 10, 2016 at 1:36 AM, Andrew Woodward
wrote:
> Unless we hope to gain some insight and
On 02/10/2016 05:54 AM, Chris Dent wrote:
> On Tue, 9 Feb 2016, Chris Dent wrote:
>
>> eventlet 0.18.2 has broken the nova unit tests at
>> 'nova.tests.unit.test_wsgi.TestWSGIServerWithSSL' so the gate is
>> blocked.
>>
>> sdague et al are working on it. Please hold off approving patches
>> in
Matt Riedemann wrote:
While reviewing the neutron 7.0.2 stable/liberty point release, I noticed
there were a lot of changes since 7.0.1. [1]
There are 48 non-merge commits by my count.
While there is no rule about how many backports should land before we cut
a
Hi All,
I was trying to bring up a VM as a compute node (using devstack
kilo version and ODL version lithium) . The VM is running Ubuntu 14.04 version
and it is spawned on a ESXI box and the hypervisor used is kvm. The
virtualization is enabled in this VM.
> On 09 Feb 2016, at 21:43, Sean M. Collins wrote:
>
> Kevin Benton wrote:
>> I agree with the mtu setting because there isn't much of a downside to
>> enabling it. However, the others do have reasons to be disabled.
>>
>> csum - requires runtime detection of support for a
I like the idea of moving it to use the OpenStack infrastructure.
On Wed, Feb 10, 2016 at 12:13 AM, Ben Nemec wrote:
> On 02/09/2016 08:05 AM, Emilien Macchi wrote:
> > Hi,
> >
> > TripleO is currently using puppet-pacemaker [1] which is a module hosted
> > & managed by
On 02/09/2016 07:31 PM, Elizabeth K. Joseph wrote:
On Mon, Feb 8, 2016 at 4:58 AM, Imre Farkas wrote:
Hi,
As python-wsmanclient has been registered under openstack, could you please
add me to both python-wsmanclient-core and python-wsmanclient-release
groups.
Reference:
Hello.
I've noticed once again that job
"gate-tempest-dsvm-neutron-src-oslo.concurrency-liberty" is always failing.
After looking at the failure I found that the core issue is
ContextualVersionConflict [0]. It seems that we have conflicting
requirements for oslo.utils here, and we do: in Liberty
Hi Ned,
Sorry for the delay in following up here.
On 06/02/16 14:40, Ned Rhudy (BLOOMBERG/ 731 LEX) wrote:
> Thanks. Having read the documentation, I have one question about the
> network design. Basically, our use case specifies that instances be able
> to have a stable IP across terminations;
The largeops tests at this point are mostly finding out that some of our
new cloud providers are slow - http://tinyurl.com/j5u4nf5
This is fundamentally a performance test, with timings having been tuned
to pass 98% of the time on two clouds that were very predictable in
performance. We're now
Could anyone (and especially Dan, Hans, or Ryan) check my changes?
There is no new code ) only removing old code and dependency to 'boto' library.
https://review.openstack.org/#/c/266425/
--
Kind regards,
Andrey Pavlov.
__
1 - 100 of 125 matches
Mail list logo