Hi,
This is a reminder that we’ll have a team meeting today at #openstack-mistral
at 16.00 UTC.
Agenda:
Review action items
Current status (progress, issues, roadblocks, further plans)
Dashboard progress
Liberty-2 progress
Open discussion
Add your topics either by replying to this email or
Hi Dolph
Thanks for idea. Is this approach used somewhere for similar use-case I
described? If so please point it out. Thanks
Filip
On 07/10/2015 04:57 PM, Dolph Mathews wrote:
How about using domain-based role assignments in keystone and
requiring domain-level authorization in policy, and
Updating jobs using sudo jenkins-jobs --flush-cache update
/etc/jenkins_jobs/config/. Also update the myvendor in examples.yaml
On Mon, Jul 13, 2015 at 1:45 PM, Tang Chen tangc...@cn.fujitsu.com wrote:
On 07/13/2015 03:50 PM, Abhishek Shrivastava wrote:
Use tester or something, also are
Miguel Angel Ajo wrote:
I've been working on assembling a QoS[1] POC since last day of the
coding sprint in Israel [2],
Ihar has reported to the list our plan to get into master [3].
I've been able to validate and integrate lots of the patches, and find
the gaps, while still
finishing the
Rob,
Please see:
https://etherpad.openstack.org/p/juno-cross-project-future-of-python
-- dims
On Mon, Jul 13, 2015 at 5:39 AM, Robert Collins
robe...@robertcollins.net wrote:
On 13 July 2015 at 20:08, Ihar Hrachyshka ihrac...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/12/2015 11:29 PM, Matt Fischer wrote:
We used Tempest for a time against our production environment. It was a
pain to clean up but ephemeral test jobs solves that for you. A few
questions:
What version of tempest will be using?
master for now. We will see if new tags are created
Oleg
The problem here is that you have this code released and it is running in
production - how are you going to fix this? Pin requirements and deal with
dependency hell?
Seriously, it is much easier to deal with explicitly frozen mirror which is
created by one 'pip install ' run than to play
On 2015-07-13 10:08:16 +0200 (+0200), Ihar Hrachyshka wrote:
clients and oslo libraries still maintain their py26 for a reason:
decision to drop py26 was for server projects only.
Yes, that decision was made at a time when our server projects had
stable branches, but our clients and shared
On 13/07/2015 13:57, Jeremy Stanley wrote:
people on 2.6-only platforms who want to install and run
python-novaclient from PyPI can use the stable/juno version (though
I'll admit that finding which version works with 2.6 may be a tricky
proposition for a consumer who is unaware of this
Hello, Warren.
Yes, we use properly filled file on a single splining drive. All tests
are done with fio, here is a link on full test report -
http://koder-ua.github.io/6.1GA/ephemeral_drive.html.
Here is a link on report for same test, executed directly on HDD, used
for ephemeral storage -
Hi,
Thanks for your replies.
Got back to the team and tried to get more input:
- the volume is created correctly (i misunderstood that part)
- the problem is that (sometimes) the instance gets spawned on the 3rd node
(which doesn't have the driver configured).
This might be because of the
On 13 July 2015 at 20:08, Ihar Hrachyshka ihrac...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/13/2015 03:29 AM, Robert Collins wrote:
So, we've got constraints support for tox coming together nicely.
The rollout for that will be per project (because tox.ini
On 07/13/2015 04:35 PM, Abhishek Shrivastava wrote:
Updating jobs using sudo jenkins-jobs --flush-cache update
/etc/jenkins_jobs/config/. Also update the myvendor in examples.yaml
Sorry, I updated the jobs, restart the whole machine. But it still
doesn't work.
By the way, there is no
The problem is, if you reject the request to lower quota unless the usage
is under the new quota, you've got an inherently racy process where the
admin needs to communicate with the tenant to say 'Stop using some of your
quota while I reduce it', which is no less complicated than 'I've reduced
On 2015-07-13 06:03:56 -0400 (-0400), Davanum Srinivas wrote:
Please see:
https://etherpad.openstack.org/p/juno-cross-project-future-of-python
That decision happened at a time when there were no stable branches
of clients/libs and no expectation of their existence. Since then
the situation has
Hi, Mike
I'm not sure we really don't need any change about this feature. At least,
some end users I faced to think there should be changed
IMHO, there is a main problem that some users whom I faced to can't
understand: What's the purpose that admin reduce quota lowner than existing
usage?
Ian Cordasco wrote:
On 7/10/15, 03:44, Thierry Carrez thie...@openstack.org wrote:
Also you'll find that the various distros use different epoch values for
the same software, because epoch are also used to cover local blunders
in packaging and historical artifacts. That is why epochs should be
Hi, Paul!
This messages is OK. May be you can put a change on review in WIP status,
that I will be able to check what is going on? I never have such problems
with migrations in neutron-vpnaas repo. May be the problem is that database
is already upgraded, was database cleaned before you run
Hi Gosha,
Supporting versioning in existing backend will require us to re-implement
the significant part of Artifact Repository in Murano API: we'll need to
add versions and dependencies concepts into our model (which is already
complicated and dirty enough), extend appropriate API calls etc. And
Vladimir,
The failures you are referring to is purely test-related failures. They
don't affect the code in production in any way, as far as I can see. All
the same, production code won't be affected by pinning versions of
test-requirements in the stable/* branches of the product and test suits.
Hi,
here is the commit on review:
https://review.openstack.org/#/c/200433
We already added non-voting job in infra repository, need to merge this
script.
On Fri, Jul 3, 2015 at 1:29 PM, Anastasia Kuznetsova
akuznets...@mirantis.com wrote:
Boris,
thanks for an explanation! I will take a
Some comments inline.
On Mon, Jul 13, 2015 at 9:24 AM, Bartlomiej Piotrowski
bpiotrow...@mirantis.com wrote:
Freezing every moving part is complete overkill and puts a heavy burden on
devops
team as well as infra itself. The fix couldn't be more simple: just put
upper
bounds in
Dima
You have a very valid point, but the is a problem here - by doing it this
way we are breaking developers' workflow which is based on using such
repositories as pypi, rubygem, etc.
If you convince developers (and I guess not only Fuel ones as we are moving
towards community engagement) to
Brandon, thank you.
I’ve pushed a fix for this issue https://review.openstack.org/#/c/201044
Evg
From: Brandon Logan [mailto:brandon.lo...@rackspace.com]
Sent: Friday, July 10, 2015 7:43 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev]
Hi all,
The device:owner the port is defined as a 255 byte string, and is widely used
now, indicating the use of the port.
Seems we can fill it freely, and user also could update/set it from cmd
line(port-update $PORT_ID --device_owner), and I don't find the guideline for
using.
What is its
We have proposing the blueprint about exposing new API for monitoring in
https://blueprints.launchpad.net/trove/+spec/expose-new-api-for-monitoring
Looking forward to any discussion :)
-- tobe from UnitedStack__
OpenStack
Hi Neil
On 07/10/2015 12:49 PM, Neil Jerram wrote:
A pragmatic fix appears to be to explicitly requery the IPAllocation
table, as you can see in the two commits here:
https://github.com/Metaswitch/calico/commit/5512ce7dd50db414f161bddcef17b0846a1466ac
Hi, all.
Currently magnum-conductor can communicates with k8s master which has a
floating ip in all-in-one deployment. But if magnum-conductor is not
deployed on the neutron network node which has the br-ex, how can
magnum-conductor communicate with k8s master. The magnum-conductor node
then
Instead of it use reusable_node option.
On Tue, Jul 14, 2015 at 9:12 AM, Tang Chen tangc...@cn.fujitsu.com wrote:
Hi Abhishek, All,
I found the problem.
My /etc/zuul/layout/layout.yaml has the following config:
jobs:
- name: ^dsvm-tempest.*$
parameter-function: single_use_node
+1 from me.
Paul reviews are always helpful and easily in the same number with the
other Core members (108 reviews this cycle!). Additionally he has been
helpful in testing the new Ansible pieces as well as pushing forward the
source installation, both areas we need help in currently.
Sam Yaple
hi,
what's the status of patches like this?
https://review.openstack.org/#/c/173834/
we still haven't decided how to handle that?
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Hi all,
Recently I want to have a try of the feature security-port, but these is
very few introduction. Could you give some help?
Thank you.
__
OpenStack Development Mailing List (not for usage questions)
Hi Abhishek,
I printed the self.layout.projects in zuul/scheduler.py, it is empty.
So the project was not found.
But I did do the jenkins-jobs --flush-cache update /etc/jenkins_jobs/config/
And I did configure openstack-dev/sandbox in layout.yaml.
Do you have any idea what's wrong here ?
Hi, Wanghua
Currently magnum-conductor can communicates with k8s master which has a
floating ip in all-in-one deployment. But if magnum-conductor is not deployed
on the neutron network node which has the br-ex, how can magnum-conductor
communicate with k8s master. The magnum-conductor
Hi Abhishek, All,
I found the problem.
My /etc/zuul/layout/layout.yaml has the following config:
jobs:
- name: ^dsvm-tempest.*$
parameter-function: single_use_node
But in _parseConfig() in zuul/scheduler.py, it failed to find
single_use_node().
fname =
On Tue, Jul 14, 2015 at 11:40 AM, Steven Dake (stdake) std...@cisco.com
wrote:
Hey folks,
I am proposing Paul Bourke for the Kolla core team. He did a fantastic
job getting Kolla into shape to support multiple distros and from
source/from binary installation. His statistics are fantastic
Thanks Adrian!
Hi, all,
Let me recap what is hyper and the idea of hyperstack.
Hyper is a single-host runtime engine. Technically,
Docker = LXC + AUFS
Hyper = Hypervisor + AUFS
where AUFS is the Docker image. Due to the shared-kernel nature of LXC, Docker
lacks of the necessary isolation
Dear PTLs, cross-project liaisons and anyone else interested,
We'll have a cross-project meeting today at 21:00 UTC, with the
following agenda:
* Team announcements (horizontal, vertical, diagonal)
* (OpenStack spec) Replace eventlet + monkey-patching with ?? [1]
* (OpenStack spec)
Hi Keystone team,
Now the test of ec2 credentials[1] is been proposed to Tempest, and
I'd like to know current situation of ec2 api on Keystone as a Tempest
reviewer.
On Nova instead, ec2 api is deprecated in Nova and the standalone
service of ec2 api is separated from Nova to
Inline reply (I've added to CC relevant people for ml2/plugin.py
port_update extension
handing -via git blame-) as they probably have an opinion here
(specially the last
two options).
Kevin Benton wrote:
This sounds like a lot of overlap with the dict extend functions. Why
weren't they
On 07/13/2015 09:40 PM, Li, Chen wrote:
Hi mike,
Thanks, this is very helpful.
Summary:
1. The purpose of admin user proxy user are the same = to work without user's
own username password.
sort of, the proxy user is to work without the user's credentials,
whereas the admin user needs a
Well FWIW I think that that should go ahead: we have no constraints
mechanism to keep to known-good versions for kilo, and the minimum
version bump was explains in the requirements repo when it was
proposed.
On 14 July 2015 at 17:10, Takashi Yamamoto yamam...@midokura.com wrote:
hi,
what's the
From: OTSUKA, Motohiro yuany...@oeilvert.orgmailto:yuany...@oeilvert.org
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Monday, July 13, 2015 at 8:11 PM
To: OpenStack Development Mailing List
Hi Tim,
The change was already merged to master. Withe next release of
python-muranoclient it can be used in Congress.
Regards
Filip
On 07/08/2015 03:57 PM, Tim Hinrichs wrote:
There are two things to remember here.
1) When you configure the Congress datasource driver to talk to
Murano,
Hello Puppet masters!
Here's an initial agenda for our weekly meeting, tomorrow at 1500 UTC
in #openstack-meeting-4:
https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20150714
Please add additional items you'd like to discuss.
If our schedule allows it, we'll make bug triage
Excerpts from Jeremy Stanley's message of 2015-07-13 11:57:35 +:
On 2015-07-13 10:08:16 +0200 (+0200), Ihar Hrachyshka wrote:
clients and oslo libraries still maintain their py26 for a reason:
decision to drop py26 was for server projects only.
Yes, that decision was made at a time
Hi,
I sent a simple patch to check the possibility to add results to callbacks:
https://review.openstack.org/#/c/201127/
This will allow us to decouple the callback logic from the ML2 plugin in the
QoS scenario where we need to update the agents in case the profile_id on a
port/network
On 07/13/2015 04:09 AM, Kevin Benton wrote:
because you won't have to run Neutron agents on compute nodes anymore.
How will upgrades work for OVN?
We haven't written anything down yet, but here's what I expect.
Right now we're still changing the db schema however is needed without
messing
On 7/13/2015 6:57 AM, Jeremy Stanley wrote:
On 2015-07-13 10:08:16 +0200 (+0200), Ihar Hrachyshka wrote:
clients and oslo libraries still maintain their py26 for a reason:
decision to drop py26 was for server projects only.
Yes, that decision was made at a time when our server projects had
On Mon, Jul 13, 2015 at 2:19 AM, Alexander Tivelkov ativel...@mirantis.com
wrote:
Hi Gosha,
Supporting versioning in existing backend will require us to re-implement
the significant part of Artifact Repository in Murano API: we'll need to
add versions and dependencies concepts into our model
From what I can tell, nova never got a global-requirements sync update
for this change on stable/kilo:
https://review.openstack.org/#/c/200493/
We need that so we don't have to try and do it manually:
https://review.openstack.org/#/c/200880/
Which is apparently busted in the
On 2015-07-13 09:39:36 -0400 (-0400), Doug Hellmann wrote:
[...]
On the other hand, how much longer will we be supporting Juno? A
matter of months, right?
The reason it's being brought up again at this point is to ask
whether it's more important that we keep master clients/libs working
with 2.6
On 7/12/2015 1:50 AM, Joshua Hesketh wrote:
Hey,
Yes, sorry, I only discovered this yesterday. I should have updated the
wiki page sooner but I've placed some details there now:
https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/kilo+topic:fix-th,n,z
Basically
At the moment everything is ready for moving fuel-web/bin/agent to a
separate git repository.
Please, be informed that all patches changing fuel-web/bin/agent that will
be merged after this moment will need to be ported into the new
nailgun-agent repository.
Current source repository which will
On Jul 10, 2015, at 4:19 AM, Thierry Carrez thie...@openstack.org wrote:
I think growing up is accepting the pain that comes with picking a
good name, rather than sidestepping the issue.
I’ve heard the phrase that there are only two hard problems in computer
science, and naming is one of
On 7/13/2015 9:01 AM, Matt Riedemann wrote:
From what I can tell, nova never got a global-requirements sync update
for this change on stable/kilo:
https://review.openstack.org/#/c/200493/
We need that so we don't have to try and do it manually:
https://review.openstack.org/#/c/200880/
I just closed the poll after one week.
It will happen on Wed 9/2 – Fri 9/4.
We'll work on the agenda during the following weeks.
Best,
On 07/06/2015 10:26 PM, Matt Fischer wrote:
Operators mid-cycle is Aug 17-21 at a TBD location, I voted accordingly.
Thanks.
On Mon, Jul 6, 2015 at 12:09
On 2015-07-14 00:33:52 +0200 (+0200), Thomas Goirand wrote:
[...]
I believe I asked you about 10 times to keep these branches alive, so
that distributions could work together on a longer support, even without
a CI behind it.
And the project consensus has seemed to disagree with this after
Thanks Kevin and everybody for the positive feedback! :)
It's a pleasure to work with so many awesome people.
Best,
Miguel Ángel,
Kevin Benton wrote:
It's been a week with no negative feedback. Welcome to the team Miguel!
On Jul 7, 2015 5:22 AM, Ihar Hrachyshkaihrac...@redhat.com wrote:
Last year I put together a virtualenv patch for the Designate puppet
module, but the patch was too invasive of a change and too opinionated to
be practical to merge. I've taken another shot at this with the approach
of implementing well defined hooks for various phases of the module. This
should
Hey folks,
I am proposing Paul Bourke for the Kolla core team. He did a fantastic job
getting Kolla into shape to support multiple distros and from source/from
binary installation. His statistics are fantastic including both code and
reviews. His reviews are not only voluminous, but
On 07/03/2015 08:36 AM, Samuel de Medeiros Queiroz wrote:
Hi Thierry,
Thanks for clarifying. A Spec Freeze Exception is what I was supposed
to ask for.
Rectifying:
On behalf of the team working on the Dynamic Policies subject, I would
like to ask for a *Spec Freeze Exception* in Liberty
On Mon, Jul 13, 2015 at 06:41:55PM +, Devananda van der Veen wrote:
This is a much-overdue follow up to this poll, which got 17 responses.
snip
So, though it saddens me, I would like to propose that we change back to a
single meeting time effective the week following our midcycle (Aug
I am a +1 on this as well. I agree with Guang
Brad Topol, Ph.D.
IBM Distinguished Engineer
OpenStack
(919) 543-0646
Internet: bto...@us.ibm.com
Assistant: Kendra Witherspoon (919) 254-0680
From: Yee, Guang guang@hp.com
To: OpenStack Development Mailing List (not for usage
On 16:28 Jul 10, Ivan Kolodyazhny wrote:
Hi Mike,
Unfortunately, we don't get a lot of stats [1] because we don't run it
often. I've added 'check experimental' comment to latest
python-cinderclient review request to get more stats.
Review request to make this voting:
On 7/9/15, 13:37, Flavio Percoco fla...@redhat.com wrote:
Greetings,
I'd like to propose Stuart Mclaren for the glance-drivers team. Stuart
has a huge amount of knowledge about Glance's history, he knows the
Glance codebase well and he also has experience in deploying and
maintaning Glance
This is a much-overdue follow up to this poll, which got 17 responses.
TL;DR:
The poll indicated that most responders did not personally find the 0500
meeting helpful. Reviewing the meeting logs for the last six months shows
significantly lower core attendance in those meetings. Informal
Hi,
Following is the subteam report for Ironic. As usual, this is pulled
directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
As of Mon, Jul 13 (diff with Jun 29)
Open: 147 (-3). 6 new (+1), 52 in progress, 1 critical (+1), 10 high (-1)
and 8 incomplete (-1)
Nova
Hi all!
Just dropping a reminder out here -- our midcycle is one month away! We're
starting to jot down informal notes and plans on an etherpad here:
https://etherpad.openstack.org/p/ironic-liberty-midcycle
Please continue to use that to coordinate all the things. If you plan to
attend, please
A quick reminder that we will be reconvening tomorrow at 16:00UTC in
#openstack-meeting-4 to continue the API discussion.
Thanks,
Graham
On 06/07/15 15:27, Hayes, Graham wrote:
Hi All,
I have put up an agenda for the meeting tomorrow:
https://wiki.openstack.org/wiki/Meetings/GSLB
It
On 07/13/2015 02:21 PM, Emilien Macchi wrote:
It comes up some people are interested to help with Puppet OpenStack CI
work, so here is an etherpad:
https://etherpad.openstack.org/p/puppet-openstack-CI
Before working on any task, please make sure to chat with us on IRC or
ML, and put your name
Hi everyone,
The OpenStack Infrastructure (Infra) team is having our next weekly
meeting on Tuesday July 14th, at 19:00 UTC in #openstack-meeting
Meeting agenda available here:
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is
welcome to to add agenda items)
Everyone
On 7/3/15, 05:35, Kuvaja, Erno kuv...@hp.com wrote:
First of all, Thanks Flavio for bring this open to the daylight!
I agree. More of these discussions need to happen on the mailing list.
I have been really frustrated about the Glance spec process since the
beginning and as glance core tried
Excerpts from Matt Riedemann's message of 2015-07-13 08:52:37 -0500:
On 7/13/2015 6:57 AM, Jeremy Stanley wrote:
On 2015-07-13 10:08:16 +0200 (+0200), Ihar Hrachyshka wrote:
clients and oslo libraries still maintain their py26 for a reason:
decision to drop py26 was for server projects
I noticed in Kilo there’s a validation check in the console web socket proxies
to ensure the hostnames from the Origin and Host headers match. This was as a
result of CVE-2015-0259 (https://bugs.launchpad.net/nova/+bug/1409142).
Effectively it disabled cross-site web socket connections.
This
On Mon, Jul 13, 2015 at 12:04:05PM -0700, Mike Perez wrote:
On 16:28 Jul 10, Ivan Kolodyazhny wrote:
Hi Mike,
Unfortunately, we don't get a lot of stats [1] because we don't run it
often. I've added 'check experimental' comment to latest
python-cinderclient review request to get more
I'm trying to get my arms around how to develop ceilometer support for
networking related data/counters. Seems like there might be a couple of ways to
go about this.
On the one hand, there are the OpenDaylight and opencontrail contributions in
It comes up some people are interested to help with Puppet OpenStack CI
work, so here is an etherpad:
https://etherpad.openstack.org/p/puppet-openstack-CI
Before working on any task, please make sure to chat with us on IRC or
ML, and put your name in the etherpad.
Also, any new topics are
++!
Per my understanding, the work, and therefore the risks, are fairly
compartmentalized. The upside is this will pave the way for a much richer
authorization management system.
Guang
From: Adam Young [mailto:ayo...@redhat.com]
Sent: Monday, July 13, 2015 10:15 AM
To:
July 14 IRC Meeting is cancelled due to proximity to the Keystone MidCycle
(Wed, Thurs, and Fri) of this week. Meetings will resume normal schedule as
of July 21.
See everyone either at the MidCycle or at the next IRC meeting.
Does anyone have recent experience getting the Kubernetes/Redis example to work
in the Magnum developer Quick-Start guide?:
https://github.com/openstack/magnum/blob/master/doc/source/dev/dev-quickstart.rst#exercising-the-services-using-devstack
I can get everything in the Kubernetes/Redis
On Fri, Jul 10, 2015 at 5:34 PM, Gurucharan Shetty shet...@nicira.com wrote:
On Fri, Jul 10, 2015 at 8:16 AM, Gurucharan Shetty shet...@nicira.com wrote:
From a 2 min look, this seems to wrap docker commands instead of using
the new plugin
The plugin is here:
Thanks for joining us today and making a good meeting!
As usually,
Meeting minutes:
http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-07-13-16.00.html
http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-07-13-16.00.html
Meeting log:
Hi German,
We integrated UI with LBaaS v2 GET APIs. We have created all panels for
CREATE and UPDATE as well.
Plan is to share our code with community on stackforge for more
collaboration from the community.
So far Ganesh from cisco has shown interest in helping with some work. It
will be great
On 14 July 2015 at 02:10, Jeremy Stanley fu...@yuggoth.org wrote:
On 2015-07-13 09:39:36 -0400 (-0400), Doug Hellmann wrote:
[...]
On the other hand, how much longer will we be supporting Juno? A
matter of months, right?
The reason it's being brought up again at this point is to ask
whether
On Mon, Jul 13, 2015 at 07:50:59AM -0400, Emilien Macchi wrote:
On 07/12/2015 11:29 PM, Matt Fischer wrote:
We used Tempest for a time against our production environment. It was a
pain to clean up but ephemeral test jobs solves that for you. A few
questions:
What version of
I would appreciate if you could all leave your comments and thoughts on
the following patch [1].
Please be advised this is an initial version and your feedback is very
much appreciated.
[1] https://review.openstack.org/#/c/200128/1
--
Best Regards,
Maish Saidel-Keesing
Hello everyone.
During the Liberty summit in Vancouver, the idea to maintain OpenStack
packages for Debian and Ubuntu on upstream infra sparked. As part of the
Openstack and Debian community we still want to push for it. Instead of
trying to directly go for the /openstack namespace, we currently
On 13 Jul 2015 8:52 pm, Ian Cordasco ian.corda...@rackspace.com wrote:
On 7/13/15, 03:38, Thierry Carrez thie...@openstack.org wrote:
SNIP
By counter-productive, I meant: likely to generate more confusion than
clarity. If you provide an epoch in the version and it doesn't match
downstream
This sounds like a lot of overlap with the dict extend functions. Why
weren't they adequate for the QoS use case?
On Mon, Jul 13, 2015 at 7:58 AM, Mike Kolesnik mkole...@redhat.com wrote:
Hi,
I sent a simple patch to check the possibility to add results to callbacks:
Thanks for the info. So the equivalent in neutron would be if we just
ensure backward compatible AMQP APIs, right?
On Mon, Jul 13, 2015 at 7:33 AM, Russell Bryant rbry...@redhat.com wrote:
On 07/13/2015 04:09 AM, Kevin Benton wrote:
because you won't have to run Neutron agents on compute nodes
On 13 July 2015 at 21:58, Ian Cordasco ian.corda...@rackspace.com wrote:
On 7/13/15, 15:09, Dave Walker em...@daviey.com wrote:
SNIP
Therefore, these distro's would need to increment the distro epoch if the
upstream version (without the upstream epoch) is lower than the version
currently in
On 7/13/15, 03:38, Thierry Carrez thie...@openstack.org wrote:
Ian Cordasco wrote:
On 7/10/15, 03:44, Thierry Carrez thie...@openstack.org wrote:
Also you'll find that the various distros use different epoch values
for
the same software, because epoch are also used to cover local blunders
Since this is post-commit, can you try using a new admin context for the
get_port call and see if it suffers from the same problem? So instead of
passing context._plugin_context, pass in ctx.get_admin_context().
On Fri, Jul 10, 2015 at 4:49 AM, Neil Jerram neil.jer...@metaswitch.com
wrote:
On Sun, Jul 12, 2015 at 09:29:57PM -0600, Matt Fischer wrote:
We used Tempest for a time against our production environment. It was a
pain to clean up but ephemeral test jobs solves that for you. A few
questions
Just curious how long ago was this? Because resource leaks have always been
My tempest experience is dated to Havana, so I'll consider it to be
completely out of date. Glad to he about all these improvements.
On Jul 13, 2015 2:12 PM, Matthew Treinish mtrein...@kortar.org wrote:
On Sun, Jul 12, 2015 at 09:29:57PM -0600, Matt Fischer wrote:
We used Tempest for a time
For those involved in Magnum networking, I suggest attending the upcoming
Docker Meetup:
http://www.meetup.com/Docker-Online-Meetup/events/223796871/
Regards,
Daneyon Hansen
__
OpenStack Development Mailing List (not for
On 7/13/15, 15:09, Dave Walker em...@daviey.com wrote:
On 13 Jul 2015 8:52 pm, Ian Cordasco ian.corda...@rackspace.com wrote:
On 7/13/15, 03:38, Thierry Carrez thie...@openstack.org wrote:
SNIP
By counter-productive, I meant: likely to generate more confusion
than
clarity. If you provide an
Ian Cordasco wrote:
On 7/13/15, 15:09, Dave Walkerem...@daviey.com wrote:
On 13 Jul 2015 8:52 pm, Ian Cordascoian.corda...@rackspace.com wrote:
On 7/13/15, 03:38, Thierry Carrezthie...@openstack.org wrote:
SNIP
By counter-productive, I meant: likely to generate more confusion
than
Team,
I woud like to ask for your input about adding support for Hyper in Magnum:
https://blueprints.launchpad.net/magnum/+spec/hyperstack
We touched on this in our last team meeting, and it was apparent that achieving
a higher level of understanding of the technology before weighing in about
1 - 100 of 128 matches
Mail list logo
