I am not even sure what is the intent, but some of the behavior looks like
it is clearly unintended and not useful (i.e., buggy).
IMHO, the API and CLI documentation should explain these calls/commands in
enough detail that the reader can tell the difference. And the difference
should be
Dmitri, this is a true statement. Mistral is fully abstracted out from a
concrete transport.
Renat Akhmerov
@ Mirantis Inc.
On 17 Jun 2014, at 00:52, Dmitry Borodaenko dborodae...@mirantis.com wrote:
Mistral doesn't have to be married to RabbitMQ, there's a ZeroMQ
driver in oslo.messaging,
I don't think that a common area as being proposed is a silver bullet for
solving packaging issues, such as this one. Knowing that the right source
tree bits are dropped onto the file system is not enough to guarantee that
the end-to-end solution will work on a specific distro. Other issues may
On 15 June 2014 02:45, Sukhdev Kapur sukhdevka...@gmail.com wrote:
I thought I send out this message in case other CI maintainers are
investigating this issue.
I have a problem that appeared at the same time and may be related? testr
list-tests in the tempest directory is failing with an
Hello all.
I am trying to sign the New Contributor Agreement to be able to
submit a new blueprint for review.
For several weeks now, I just always get an error message included below.
I even suspected browser compatibility problems, but trying with Google
Chrome, Opera or Firefox dit not help
Hi. I'm going to let this sit for another 24 hours, and then we'll
declare it closed.
Cheers,
Michael
On Tue, Jun 17, 2014 at 6:16 AM, Mark McLoughlin mar...@redhat.com wrote:
On Sat, 2014-06-14 at 08:40 +1000, Michael Still wrote:
Greetings,
I would like to nominate Ken'ichi Ohmichi for the
On 17/06/14 00:28, Joshua Harlow wrote:
So this is a reader/write lock then?
I have seen https://github.com/python-zk/kazoo/pull/141 come up in the
kazoo (zookeeper python library) but there was a lack of a maintainer for
that 'recipe', perhaps if we really find this needed we can help get
Hi Ihar,
What is the reason to breakup neutron into so many packages? A quick disk
usage stat shows the plugins directory is currently 3.4M.
Is that considered to be too much space for a package, or was it for
another reason?
Thanks,
Kevin Benton
On Mon, Jun 16, 2014 at 3:37 PM, Ihar
Hi all,
I would like to remind you to sign up for mid-cycle meetup which is
happening July 21-25 in Raleigh:
* https://etherpad.openstack.org/p/juno-midcycle-meetup
We need number of participants as soon as possible so that we can ask
for group discount at the hotel. Also if we don't get
On Thu, May 29, 2014 at 6:57 AM, Nachi Ueno na...@ntti3.com wrote:
Hi Zang
Since, SSL-VPN for Juno bp is approved in neturon-spec,
I would like to restart this work.
Could you share your code if it is possible?
Also, Let's discuss how we can collaborate in here.
Currently We are running
On 06/14/2014 12:40 AM, Michael Still wrote:
Greetings,
I would like to nominate Ken'ichi Ohmichi for the nova-core team.
Ken'ichi has been involved with nova for a long time now. His reviews
on API changes are excellent, and he's been part of the team that has
driven the new API work
Folks,
A question for the taskflow ninjas.
Any thoughts on best practice WRT $subject?
Specifically I have in mind this ceilometer review[1] which adopts
the approach of using very fine-grained tasks (at the level of an
individual alarm evaluation) combined with short-term assignments
to
We all know that review can be a bottleneck for Nova patches.Not only
that, but a patch lingering in review, no matter how trivial, will
eventually accrue rebases which sap gate resources, developer time, and
will to live.
It occurs to me that there are a significant class of patches which
simply
A far more effective way to reduce the load of trivial review issues
on core reviewers is for none-core reviewers to get in there first,
spot the problems and add a -1 - the trivial issues are then hopefully
fixed up before a core reviewer even looks at the patch.
The fundamental problem with
Hi
As the lbass mid cycle sprint starts today, is there any way to track and
understand the progress (without flying to Texas... )
Thanks
Avishay
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
On Tue, Jun 17, 2014 at 11:04:17AM +0100, Matthew Booth wrote:
We all know that review can be a bottleneck for Nova patches.Not only
that, but a patch lingering in review, no matter how trivial, will
eventually accrue rebases which sap gate resources, developer time, and
will to live.
It
Hi:
Awesome! Currently we are suffering lots of bugs in ovs-agent, also
intent to rebuild a more stable flexible agent.
Taking the experience of ovs-agent bugs, I think the concurrency
problem is also a very important problem, the agent gets lots of event
from different greenlets, the rpc, the
On 06/17/2014 07:23 AM, Daniel P. Berrange wrote:
On Tue, Jun 17, 2014 at 11:04:17AM +0100, Matthew Booth wrote:
We all know that review can be a bottleneck for Nova patches.Not only
that, but a patch lingering in review, no matter how trivial, will
eventually accrue rebases which sap gate
On 6/17/14, 1:56 PM, Duncan Thomas duncan.tho...@gmail.com wrote:
A far more effective way to reduce the load of trivial review issues
on core reviewers is for none-core reviewers to get in there first,
spot the problems and add a -1 - the trivial issues are then hopefully
fixed up before a
On Tue, Jun 17 2014, Eoghan Glynn wrote:
Any thoughts on best practice WRT $subject?
First thing on my mind is that having smaller task can allow to have a
better repartition of the work load. :)
--
Julien Danjou
# Free Software hacker
# http://julien.danjou.info
signature.asc
Description:
On 16/06/14 18:51, Clint Byrum wrote:
Excerpts from Tomas Sedovic's message of 2014-06-16 09:19:40 -0700:
All,
After having proposed some changes[1][2] to tripleo-heat-templates[3],
reviewers suggested adding a deprecation period for the merge.py script.
While TripleO is an official
Hello,
Just a quick note to mention that I just updated the subteam wiki page with
a proposed definition of what NFV means. Comments and updates are of
course welcome.
https://wiki.openstack.org/wiki/Teams/NFV#What_is_NFV.3F
Cheers,
--
Nicolas Barcet nico...@barcet.com
a.k.a. nijaba, nick
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/06/14 12:36, Sean Dague wrote:
On 06/17/2014 07:23 AM, Daniel P. Berrange wrote:
On Tue, Jun 17, 2014 at 11:04:17AM +0100, Matthew Booth wrote:
We all know that review can be a bottleneck for Nova
patches.Not only that, but a patch lingering
On Tue, Jun 17, 2014 at 01:12:45PM +0100, Matthew Booth wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/06/14 12:36, Sean Dague wrote:
On 06/17/2014 07:23 AM, Daniel P. Berrange wrote:
If would be nice if gerrit had simple keyword tagging so any
reviewer can tag an existing
On 06/17/2014 08:00 AM, Nicolas Barcet wrote:
Hello,
Just a quick note to mention that I just updated the subteam wiki page
with a proposed definition of what NFV means. Comments and updates are
of course welcome.
https://wiki.openstack.org/wiki/Teams/NFV#What_is_NFV.3F
Overview
Hi,
There is an action for creating a Gerrit dashboard to show all
NFV-related specs and patches.
As it requires to have a specific label for discriminating them, I'm
adding NFVImpact in all the patches proposed in [1].
The side effect is that it creates another patchset and so runs another
On 06/17/2014 08:20 AM, Daniel P. Berrange wrote:
On Tue, Jun 17, 2014 at 01:12:45PM +0100, Matthew Booth wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/06/14 12:36, Sean Dague wrote:
On 06/17/2014 07:23 AM, Daniel P. Berrange wrote:
If would be nice if gerrit had simple keyword
On 6/17/2014 7:04 AM, Eoghan Glynn wrote:
Folks,
A question for the taskflow ninjas.
Any thoughts on best practice WRT $subject?
Specifically I have in mind this ceilometer review[1] which adopts
the approach of using very fine-grained tasks (at the level of an
individual alarm
On 12 June 2014 17:10, Sean Dague s...@dague.net wrote:
On 06/12/2014 12:02 PM, Matt Riedemann wrote:
On 6/12/2014 10:51 AM, Matthew Treinish wrote:
On Fri, Jun 13, 2014 at 12:41:19AM +0930, Christopher Yeoh wrote:
On Fri, Jun 13, 2014 at 12:25 AM, Dan Smith d...@danplanet.com wrote:
I
On 06/14/2014 12:40 AM, Michael Still wrote:
Greetings,
I would like to nominate Ken'ichi Ohmichi for the nova-core team.
Ken'ichi has been involved with nova for a long time now. His reviews
on API changes are excellent, and he's been part of the team that has
driven the new API work
I wonder what the turnaround of trivial patches actually is, I bet you it's
very very small, and as Daniel said, the human burden is rather minimal (I
would be more concerned about slowing them down in the gate, but I digress).
I think that introducing a two-tier level for patch approval can only
On 14 June 2014 00:48, Michael Still mi...@stillhq.com wrote:
On Fri, Jun 13, 2014 at 1:00 PM, Christopher Yeoh cbky...@gmail.com wrote:
On Fri, Jun 13, 2014 at 11:28 AM, Matt Riedemann
mrie...@linux.vnet.ibm.com wrote:
On 6/12/2014 5:58 PM, Christopher Yeoh wrote:
On Fri, Jun 13, 2014 at
So I am +1 deprecating resize down, mostly for consistency reasons.
On 16 June 2014 10:34, Day, Phil philip@hp.com wrote:
Beyond what is and isn’t technically possible at the file system level there
is always the problem that the user may have more data than can fit into the
reduced disk.
I have seem some work and specs around this here:
https://blueprints.launchpad.net/nova/+spec/hot-resize
Hope that helps,
John
On 8 April 2014 17:45, Trump.Zhang zhangleiqi...@gmail.com wrote:
Such as QoS attributes of vCPU, Memory and Disk, including IOPS limit,
Bandwidth limit, etc.
Hello,
I confirm ... one of my college has the same trouble.
On Tue, Jun 17, 2014 at 9:57 AM, Sami J. Mäkinen sjm+osde...@hard.ware.fi
wrote:
Hello all.
I am trying to sign the New Contributor Agreement to be able to
submit a new blueprint for review.
For several weeks now, I just
On 06/17/2014 09:13 AM, ZZelle wrote:
Hello,
I confirm ... one of my college has the same trouble.
Make sure you're a member of the foundation first using the same email
address you're using in gerrit:
https://www.openstack.org/join/register/
For some more commentary, see comments on:
Hello,
We went through a similar exercise for Marconi.
At that point of time, there was not any documentation on the series of steps
to go through.
Below are some of the high level steps we went through.
1. Complete devstack integration (Make sure you run devstack with same
local.conf as in
Hi guys,
So I've started to look at the configuration file used by Glance and I
want to switch to one configuration file only.
I stumbled upon this blueprint:
https://blueprints.launchpad.net/glance/+spec/use-oslo-config
which fits.
Does not look like I can assign myself to it, but if
On Tue, Jun 17, 2014 at 4:36 AM, Matthew Booth mbo...@redhat.com wrote:
On 17/06/14 00:28, Joshua Harlow wrote:
So this is a reader/write lock then?
I have seen https://github.com/python-zk/kazoo/pull/141 come up in the
kazoo (zookeeper python library) but there was a lack of a maintainer for
We have an Etherpad going here:
https://etherpad.openstack.org/p/juno-lbaas-mid-cycle-hackathon
Dustin
On Tue, Jun 17, 2014 at 4:05 AM, Avishay Balderman avish...@radware.com
wrote:
Hi
As the lbass mid cycle sprint starts today, is there any way to track and
understand the progress
2014-06-17 21:39 GMT+09:00 John Garbutt j...@johngarbutt.com:
On 12 June 2014 17:10, Sean Dague s...@dague.net wrote:
On 06/12/2014 12:02 PM, Matt Riedemann wrote:
On 6/12/2014 10:51 AM, Matthew Treinish wrote:
On Fri, Jun 13, 2014 at 12:41:19AM +0930, Christopher Yeoh wrote:
On Fri, Jun
Hi UXers,
this is a reminder that our next regular IRC meeting is happening
tomorrow (Wednesday) June 18th at 14:30 UTC at #openstack-meeting-3.
Agenda: https://wiki.openstack.org/wiki/Meetings/UX
Feel free to add topics which you are interested in.
See you all tomorrow
-- Jarda
On 17/06/14 15:59 +0200, Julien Danjou wrote:
Hi guys,
So I've started to look at the configuration file used by Glance and I
want to switch to one configuration file only.
I stumbled upon this blueprint:
https://blueprints.launchpad.net/glance/+spec/use-oslo-config
w.r.t using
On Fri, Jun 13, 2014 at 03:06:25PM +0530, abhishek jain wrote:
Hi Rich
Can you help me regarding the possible cause for VM stucking at spawning
state on ubuntu powerpc compute node in openstack using devstack.
Did you solve this one? It's impossible to debug unless you collect
the full
On Mon, 2014-06-16 at 23:06 +0530, Deepak Shetty wrote:
I am trying devstack on F20 setup with Manila sources.
When i am trying to do
manila create --name cinder_vol_share_using_nfs2 --share-network-id
36ec5a17-cef6-44a8-a518-457a6f36faa0 NFS 2
I see the below error in c-vol due to which
I do not like this idea. As now we are on 5 different config files (+ policy
and schema). One for each (API and Registry) would still be ok, but putting all
together would just become messy.
If the *-paste.ini will be migrated to .conf files that would bring it down,
but please do not try to
On Fri, Jun 13, 2014 at 06:12:16AM -0400, Aryeh Friedman wrote:
Theoretically impossible to reduce disk unless you have some really nasty
guest additions.
True for live resizing.
For dead resizing, libguestfs + virt-resize can do it. Although I
wouldn't necessarily recommend it. In almost
I agree with Erno. I think that the glance registry service being optional is
a good argument for keeping its config separate rather than munging it into the
API config.
rosmaita
From: Kuvaja, Erno [kuv...@hp.com]
Sent: Tuesday, June 17, 2014 10:29 AM
Hi Sami,
sorry for this. I suspect there is something going on with gerrit which
throws the inappropriate error message (more below).
On 06/17/2014 12:57 AM, Sami J. Mäkinen wrote:
For several weeks now, I just always get an error message included below.
In these cases and in general, don't
Frankly I don't like the idea of using single configuration for all
service too, I think it will be cool if we can generate separated
configuration template files automatically for each Glance service. So
besides https://review.openstack.org/#/c/83327/ , actually I'm working
on that idea as well,
On 6/16/2014 11:58 PM, Joshua Hesketh wrote:
Hi there,
Very sorry for the mishap. I manually enqueued our zuul to run tests on
changes that turbo-hipster had recently missed and did not pay attention
to the branch they were for.
Turbo-Hipster doesn't run tests on stable or non-master
On Tue, Jun 17, 2014 at 6:51 AM, Armando M. arma...@gmail.com wrote:
I wonder what the turnaround of trivial patches actually is, I bet you
it's very very small, and as Daniel said, the human burden is rather
minimal (I would be more concerned about slowing them down in the gate, but
I
+1
-Original Message-
From: Michael Still [mailto:mi...@stillhq.com]
Sent: Saturday, June 14, 2014 6:41 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Nova] Nominating Ken'ichi Ohmichi for nova-core
Greetings,
I would like to nominate Ken'ichi Ohmichi for the
Also, pop into #openstack-lbaas on Freenode, we have people there
monitoring the channel.
On Tue, Jun 17, 2014 at 9:19 AM, Dustin Lundquist dus...@null-ptr.net wrote:
We have an Etherpad going here:
https://etherpad.openstack.org/p/juno-lbaas-mid-cycle-hackathon
Dustin
On Tue, Jun 17,
On Tue, Jun 17, 2014 at 10:56:36AM -0400, Russell Bryant wrote:
On 06/17/2014 10:43 AM, Richard W.M. Jones wrote:
On Fri, Jun 13, 2014 at 06:12:16AM -0400, Aryeh Friedman wrote:
Theoretically impossible to reduce disk unless you have some really nasty
guest additions.
True for live
On 06/17/2014 10:43 AM, Richard W.M. Jones wrote:
On Fri, Jun 13, 2014 at 06:12:16AM -0400, Aryeh Friedman wrote:
Theoretically impossible to reduce disk unless you have some really nasty
guest additions.
True for live resizing.
For dead resizing, libguestfs + virt-resize can do it.
Actually the channel name is #neutron-lbaas.
On Tue, Jun 17, 2014 at 8:03 AM, Kyle Mestery mest...@noironetworks.com
wrote:
Also, pop into #openstack-lbaas on Freenode, we have people there
monitoring the channel.
On Tue, Jun 17, 2014 at 9:19 AM, Dustin Lundquist dus...@null-ptr.net
wrote:
On Tue, Jun 17, 2014 at 10:10:26AM EDT, Shixiong Shang wrote:
Trying to join the weekly meeting, but my IRC client kept complaining…Is it
just me?
If you have problems, you can always use the web client:
http://webchat.freenode.net/
--
Sean M. Collins
On 06/13/2014 02:22 PM, Day, Phil wrote:
I guess the question I’m really asking here is: “Since we know resize down
won’t work in all cases,
and the failure if it does occur will be hard for the user to detect,
should we just block it at the API layer and be consistent across all
@ZhiYan: I don't like the idea of removing the sample configuration file(s)
from the git repository. Many people do not want to have to checkout the entire
codebase and tox every time they have to verify a variable name in a
configuration file. I know many people who were really frustrated
Hi,
I'm trying to figure out what we'll be able to support in the near/far term
with regards to packaging applications. My understanding of the DSL is
incomplete and I'm trying to fix that :) This isn't so much a usage question
as for assistance writing documentation.
Taking Wordpress as the
On 17/06/14 23:30, Arnaud Legendre wrote:
@ZhiYan: I don't like the idea of removing the sample configuration file(s)
from the git repository. Many people do not want to have to checkout the entire
codebase and tox every time they have to verify a variable name in a
configuration file. I know
The Manila core team welcomes Xing Yang! She has been a very active
reviewer and has been consistently involved with the project.
Xing, thank you for all your effort and keep up the great work!
-Ben Swartzlander
___
OpenStack-dev mailing list
On Tue, Jun 17 2014, Arnaud Legendre wrote:
@ZhiYan: I don't like the idea of removing the sample configuration file(s)
from the git repository. Many people do not want to have to checkout the
entire codebase and tox every time they have to verify a variable name in a
configuration file. I
[trimming reply-to to OpenStack Development since I don't think that
infra is the right venue to discuss this]
On 06/13/2014 10:08 AM, trinath.soman...@freescale.com wrote:
I have two scenarios to deal with.
[1] A change takes two months or more to get merged into the master
branch.
Here,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/17/2014 09:52 AM, John Griffith wrote:
On Tue, Jun 17, 2014 at 6:51 AM, Armando M. arma...@gmail.com
wrote:
I wonder what the turnaround of trivial patches actually is, I
bet you it's very very small, and as Daniel said, the human
burden
All the things that you mention here seem to be technical difficulties.
I don't think technical difficulties should drive the experience of the user.
Also, Zhi Yan seems to be able to make that happen :)
Thanks,
Arnaud
- Original Message -
From: Julien Danjou jul...@danjou.info
To:
On 06/17/2014 10:43 AM, Stefano Maffulli wrote:
[trimming reply-to to OpenStack Development since I don't think that
infra is the right venue to discuss this]
On 06/13/2014 10:08 AM, trinath.soman...@freescale.com wrote:
I have two scenarios to deal with.
[1] A change takes two months or
Thanks Ben! It's my pleasure to join the Manila core team!
Xing
-Original Message-
From: Swartzlander, Ben [mailto:ben.swartzlan...@netapp.com]
Sent: Tuesday, June 17, 2014 11:46 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Manila] Welcome Xing Yang to the
On 6/10/2014 3:56 PM, Matt Riedemann wrote:
On 6/4/2014 11:02 AM, Day, Phil wrote:
Matt and I chatted on IRC and have come up with an outlined plan, if
we missed anything please don't hesitate to comment or ask.
https://etherpad.openstack.org/p/quota-classes-goof-up
I added a few
We are now on: #openstack-lbaas
The #neutron-lbaas is now deprecated.
On Tue, Jun 17, 2014 at 11:10 AM, Dustin Lundquist dus...@null-ptr.net
wrote:
Actually the channel name is #neutron-lbaas.
On Tue, Jun 17, 2014 at 8:03 AM, Kyle Mestery mest...@noironetworks.com
wrote:
Also, pop into
So, we've now moved to #openstack-lbaas, my email was slightly ahead. :)
On Tue, Jun 17, 2014 at 10:10 AM, Dustin Lundquist dus...@null-ptr.net wrote:
Actually the channel name is #neutron-lbaas.
On Tue, Jun 17, 2014 at 8:03 AM, Kyle Mestery mest...@noironetworks.com
wrote:
Also, pop into
Congratulations Xing!
-Original Message-
From: yang, xing [mailto:xing.y...@emc.com]
Sent: Tuesday, June 17, 2014 10:11 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Manila] Welcome Xing Yang to the Manila core team!
Thanks Ben! It's
On Tue, Jun 17, 2014 at 3:56 AM, Duncan Thomas duncan.tho...@gmail.com
wrote:
A far more effective way to reduce the load of trivial review issues
on core reviewers is for none-core reviewers to get in there first,
spot the problems and add a -1 - the trivial issues are then hopefully
fixed
We've started doing this in a slightly more reasonable way for icehouse.
What we've done is:
- remove unnecessary notification from the server
- process all port-related events, either trigger via RPC or via monitor in
one place
Obviously there is always a lot of room for improvement, and I agree
Everyone is migrating to the new channel #openstack-lbaas
From: Dustin Lundquist dus...@null-ptr.netmailto:dus...@null-ptr.net
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Tuesday, June 17,
Meetup webex:
https://a10networks.webex.com/a10networks/e.php?MTID=m3351a8eb388c2ade866bac44cc272c5b
From: Susanne Balle sleipnir...@gmail.commailto:sleipnir...@gmail.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
On 06/10/2014 09:18 PM, Radomir Dopieralski wrote:
The name poll is now officially over, and the winner is:
horizon_lib
You can view the results here:
http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_ea99af9511f3f255
I think we won't need to check for trademark issues with this name, so
we
WebEx is here:
https://a10networks.webex.com/a10networks/e.php?MTID=m3351a8eb388c2ade866bac44cc272c5b
On Tue, Jun 17, 2014 at 12:13 PM, Susanne Balle sleipnir...@gmail.com
wrote:
We are now on: #openstack-lbaas
The #neutron-lbaas is now deprecated.
On Tue, Jun 17, 2014 at 11:10 AM, Dustin
Another area of improvement for the agent would be to move away from
executing CLIs for port commands and instead use OVSDB. Terry Wilson
and I talked about this, and re-writing ovs_lib to use an OVSDB
connection instead of the CLI methods would be a huge improvement
here. I'm not sure if Terry
Hi, I have posted a preliminary agenda for today. I will be unable to
attend the meeting, Kevin Benton will be chairing the meeting today.
Please do add items to the agenda that you wish to discuss!
https://wiki.openstack.org/wiki/Meetings/NeutronQoS
--
Sean M. Collins
On 06/17/2014 12:22 PM, Joe Gordon wrote:
On Tue, Jun 17, 2014 at 3:56 AM, Duncan Thomas duncan.tho...@gmail.com
mailto:duncan.tho...@gmail.com wrote:
A far more effective way to reduce the load of trivial review issues
on core reviewers is for none-core reviewers to get in
just a provocative thought: If we used the ovsdb connection instead, do we
really need an L2 agent :P?
On 17 June 2014 18:38, Kyle Mestery mest...@noironetworks.com wrote:
Another area of improvement for the agent would be to move away from
executing CLIs for port commands and instead use
Excerpts from Matthew Booth's message of 2014-06-17 01:36:11 -0700:
On 17/06/14 00:28, Joshua Harlow wrote:
So this is a reader/write lock then?
I have seen https://github.com/python-zk/kazoo/pull/141 come up in the
kazoo (zookeeper python library) but there was a lack of a maintainer
Hi,
+1 for Paris, since a mid-cycle sprint is already being hosted and organised by
eNovance :)
Sylvain
- Original Message -
From: Dmitry mey...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Sunday, June 15, 2014
Excerpts from Tomas Sedovic's message of 2014-06-17 04:56:24 -0700:
On 16/06/14 18:51, Clint Byrum wrote:
Excerpts from Tomas Sedovic's message of 2014-06-16 09:19:40 -0700:
All,
After having proposed some changes[1][2] to tripleo-heat-templates[3],
reviewers suggested adding a
Not if you use ODL, and we don't want to reinvent that wheel. But by
skipping CLI commands and instead using OVSDB programmatically from
agent to ovs-vswitchd, that's a decent improvement.
On Tue, Jun 17, 2014 at 11:56 AM, Armando M. arma...@gmail.com wrote:
just a provocative thought: If we
Howdy,
Sandy is correct, we aren't doing automatic load-balancing of tasks/jobs
(currently).
Though there is nothing stopping this from being implemented (and I of
course would recommend adding it to taskflow rather than jumping to
gearman, but I am obviously biased),
A feature that appeared
Managing the ports and plumbing logic is today driven by L2 Agent, with little
assistance
from controller.
If we plan to move that functionality to the controller, the controller has to
be more
heavy weight (both hardware and software) since it has to do the job of L2
Agent for all
Eoghan Glynn egl...@redhat.com writes:
TL;DR: how about we adopt a soft enforcement model, relying
on sound judgement and good faith within the community?
Thank you very much for bringing this up and proposing it to the TC. As
others have suggested, having a concrete alternative is
Back on the distributed subject (since this deserves a different email),
In the newest taskflow release (0.3.x) we have 2 mechanisms for
distribution outside of a process.
One is the job/jobboard[1] conductor[2] concepts,
These concepts allow for atomic ownership of a 'job' and conductors act
On 17/06/14 17:40, Stefano Maffulli wrote:
Hi Sami,
sorry for this. I suspect there is something going on with gerrit which
throws the inappropriate error message (more below).
Yay. I really just had to become a new OpenStack Foundation Member.
The error message I got is just not too
Hi,
Does it make sense also to have the choice between ovs-ofctl CLI and a
direct OF1.3 connection too in the ovs-agent?
Best Regards,
Racha
On Tue, Jun 17, 2014 at 10:25 AM, Narasimhan, Vivekanandan
vivekanandan.narasim...@hp.com wrote:
Managing the ports and plumbing logic is today
On 06/17/2014 10:45 AM, Sami J. Mäkinen wrote:
Yay. I really just had to become a new OpenStack Foundation Member.
The error message I got is just not too informative, I could not
help thinking there is something really broken.
Right, unfortunately the error message from gerrit cannot be
https://wiki.openstack.org/wiki/Meetings/HeatAgenda
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Heat+Chatiso=20140618T20p1=211ah=1
Agenda (2014-06-18 2000 UTC)
Review last meeting's actions
Adding items to the agenda
Mid-cycle meetup
Critical issues sync
Regards,
We have some projects which are dynamically creating VMs up to their quota.
Under some circumstances, as cloud administrators, we would like these projects
to shrink and make room for other higher priority work.
We had investigated setting the project quota below the current utilisation
(i.e.
I figured. I implemented it in https://review.openstack.org/#/c/97684/.
On Mon, Jun 16, 2014 at 9:35 PM, Renat Akhmerov rakhme...@mirantis.com
wrote:
I don’t think we have them. You can write them I think as a part of what
you’re doing.
Renat Akhmerov
@ Mirantis Inc.
On 31 May 2014,
I don't think so. Once we implement the OVSDB support, we will
deprecate using the CLI commands in ovs_lib.
On Tue, Jun 17, 2014 at 12:50 PM, racha ben...@gmail.com wrote:
Hi,
Does it make sense also to have the choice between ovs-ofctl CLI and a
direct OF1.3 connection too in the ovs-agent?
Makes sense to me
On 18 Jun 2014 06:18, Tim Bell tim.b...@cern.ch wrote:
We have some projects which are dynamically creating VMs up to their
quota. Under some circumstances, as cloud administrators, we would like
these projects to shrink and make room for other higher priority work.
We
so some questions
- how can we decide ( identify ) if the VM to delete can indeed be deleted
- Can we better enforce quota per app / cluster level
- This delete from older VM can only work if these are individual VM
operating only to support work loads ( and not as standalone apps ) ?
On Tue,
1 - 100 of 169 matches
Mail list logo
