+1
-Original Message-
From: Brandon Logan [mailto:[email protected]]
Sent: Tuesday, September 02, 2014 8:13 AM
To: [email protected]
Subject: Re: [openstack-dev] [neutron][lbaas][octavia]
Hi Susanne and everyone,
My opinions are that keeping it in stackforge un
Following last week IRC, please find below a suggestion to improve the
description and the messaging to the wider community about NFV.
I think this group is a great initiative and very important to explain NFV to
the wider developers community of OpenStack.
While NFV is becoming a more known ter
I am unable to create a back up of the volume using the cinder command even
if all the conditions required are satisfied. I am getting a HTTP 500
error. I am not sure what could be the problem here. Really appreciate if
some one can give me some pointers to where i can look.
I am using Openstack H
Hello, Vinod.
Sorry but dev. mailing list is not for usage questions. But it seems that
you don't have launched cindre-backup service (see Service cinder-backup
could not be found.). Take a look at
https://github.com/openstack/cinder/blob/master/bin/cinder-backup.
Best regards,
Denis Makogon
O
On Wed, Aug 27, 2014 at 2:11 AM, David Easter wrote:
> What’s New in Fuel 5.1?
>
> The primary new features of Fuel 5.1 are:
>
* Compute, cinder, ceph nodes has no external (public) network interface
and don't get public IP addresses if it's not necessary.
/sv
Hi everyone,
As you probably know, the Juno-3 milestone should be published Thursday
this week, and with it comes the Juno feature freeze. The general
schedule is as follows:
Tuesday:
Defer/-2 blueprints that will obviously not get the required approvals
in the next 20 hours. Review and approve a
Hayes, Graham wrote:
> On Fri, 2014-08-29 at 17:56 +0200, Thierry Carrez wrote:
>> Hayes, Graham wrote:
>>> Would the programs for those projects not get design summit time? I
>>> thought the Programs got Design summit time, not projects... If not, can
>>> the Programs get design summit time?
>>
>
I also agree with most of what Brandon said, though I am slightly
concerned by the talk of merging Octavia and [Neutron-]LBaaS-v2 codebases.
[blogan] "I think the best course of action is to get Octavia itself into
the same codebase as LBaaS (Neutron or spun out)."
[sballe] "What I am trying to no
Hi,
At NTT Data, we work on system development projects with Swift.
Recently we have big interest in the metadata search feature of Swift, and now
we're planning to construct a search function into Swift.
I checked some materials on wiki page
http://wiki.openstack.org/wiki/MetadataSearch to con
Hi Emma,
I do not claim to be an OpenStack guru, but might know something about
backing up a vCloud.
What proposal did you have in mind? A link would be helpful.
Backing up a step (ha), the existing cinder-backup API is very close to
useless. Backup needs to apply to an active instance. The Nova
Following the last PCI pass-through meeting , we want to start thinking about
features/add-ons that need to be addressed in the Kilo Release.
I created an etherpad (reused Doug's template) for topics related to PCI
pass-through, mostly focused on SR-IOV networking:
https://etherpad.openstack.org
On 2 September 2014 04:56, Emma Lin wrote:
> Hi Gurus,
> I saw the wiki page for Cinder Brick proposal for Havana, but I didn’t see
> any follow up on that idea. Is there any real progress on that idea?
>
> As this proposal is to address the local storage issue, I’d like to know the
> status, and
On 11 August 2014 19:26, Jay Pipes wrote:
> The above does not really make sense for MySQL Galera/PXC clusters *if only
> Galera nodes are used in the cluster*. Since Galera is synchronously
> replicated, there's no real point in segregating writers from readers, IMO.
> Better to just spread the
>Adding in such case more bureaucracy (specs) is not the best way to resolve
>team throughput issues...
I’d argue that if fundamental design disagreements can be surfaced and debated
at the design stage rather than first emerging on patch set XXX of an
implementation, and be used to then prior
On 09/01/2014 01:38 AM, Ian Wienand wrote:
> On 08/29/2014 10:42 PM, Sean Dague wrote:
>> I'm actually kind of convinced now that none of these approaches are
>> what we need, and that we should instead have a .bashateignore file in
>> the root dir for the project instead, which would be regex that
Hi,
Great to see some renewed interest in metadata search for Swift. We are
working on this, and would be glad if there is renewed interest from the
community.
I saw your comments on thew wiki discussion page and they look good to me.
I just added some additional comments about Data Types and
I think we finally got to a largely consensus agreement at the mid-cycle
on the path forward for Nova v2.1 and microversioning. Summary for
others: Nova v2.1 will be Nova v2 built on the v3 infrastructure (which
is much cleaner), with json schema based request validation (to further
clean up and ma
On Mon, Sep 1, 2014 at 10:47 PM, Kevin Benton wrote:
> Thank you YAMAMOTO. I didn't think to look at stackalytics.
>
> Kyle, can you list yourself on the wiki? I don't want to do it in case there
> is someone else doing that job full time.
> Also, is there a re-trigger phrase that you can document
Some more comments from me inline.
Salvatore
On 2 September 2014 11:06, Adam Harwell wrote:
> I also agree with most of what Brandon said, though I am slightly
> concerned by the talk of merging Octavia and [Neutron-]LBaaS-v2 codebases.
>
Beyond all the reasons listed in this thread - merging
Oslo team,
We need to consider how we are going to handle the approaching feature freeze
deadline (4 Sept). We should, at this point, be focusing reviews on changes
associated with blueprints. We will have time to finish graduation work and
handle bugs between the freeze and the release candida
Doug,
plan is good. Same criteria will mean exception for oslo.log as well
-- dims
On Tue, Sep 2, 2014 at 9:20 AM, Doug Hellmann wrote:
> Oslo team,
>
> We need to consider how we are going to handle the approaching feature freeze
> deadline (4 Sept). We should, at this point, be focusing revi
Hi Mirantis guys,
I have set up two Cassandra backups:
The first backup procedure was similar to the one you want to achieve.
The second backup used SAN features (EMC VNX snapshots) so it was very specific
to the environment.
Backup an entire cluster (therefore all replicas) is challenging w
Hi All,
I'd like to ask for a feature freeze exception for using oslo-incubator service
framework in glance, based on the following blueprint:
https://blueprints.launchpad.net/glance/+spec/use-common-service-framework
The code to implement this feature is under review at present.
1. Sync oslo
On Tue, Sep 02, 2014 at 08:54:31AM -0400, Sean Dague wrote:
> I think we finally got to a largely consensus agreement at the mid-cycle
> on the path forward for Nova v2.1 and microversioning. Summary for
> others: Nova v2.1 will be Nova v2 built on the v3 infrastructure (which
> is much cleaner), w
We've been playing a game recently between oslo.vmware and the refactor
series where a patch from the refactor series goes in, requiring a
rebase of oslo.vmware daily. After a brief discussion with garyk earlier
I decided to head that off by rebasing the refactor series on top of
oslo.vmware, which
Hi Romain!
Thank you for useful info about your Cassandra backuping.
We have not tried to tune Cassandra compaction properties yet.
MagnetoDB is DynamoDB-like REST API and it means that it is key-value
storage itself and it should be able to work for different kind of load,
because it depends on
Salvatore
Thanks for your clarification below around the blueprint.
> For LBaaS v2 therefore the relationship between it and Octavia should be
the same as with any other
> backend. I see Octavia has a blueprint for a "network driver" - and the
derivable of that should definitely be
> part of the
Oslo team,
Thierry and I discussed some changes in how we manage milestones in launchpad
during our 1:1 today. We settled on something close to what I think Mark has
been doing for oslo.messaging. The idea is to use milestones named “next” in
each library, and then rename those milestones when
I 100% agree with what Brandon wrote below and that is why IMHO they go
together and should be part of the same codebase.
Susanne
On Tue, Sep 2, 2014 at 1:12 AM, Brandon Logan
wrote:
I think the best course of action is to get Octavia itself into the same
codebase as LBaaS (Neutron or spun out
Yes, you’re right, I missed oslo.log.
Doug
On Sep 2, 2014, at 9:28 AM, Davanum Srinivas wrote:
> Doug,
>
> plan is good. Same criteria will mean exception for oslo.log as well
>
> -- dims
>
> On Tue, Sep 2, 2014 at 9:20 AM, Doug Hellmann wrote:
>> Oslo team,
>>
>> We need to consider how w
Hi Susanne,
I'm just trying to gain a good understanding of the situation here.
More comments and questions inline.
Salvatore
On 2 September 2014 16:34, Susanne Balle wrote:
> Salvatore
>
> Thanks for your clarification below around the blueprint.
>
> > For LBaaS v2 therefore the relationship
On 2014-09-02 15:18:14 +0100 (+0100), Daniel P. Berrange wrote:
> Do we have any historic precedent of using feature branches in this kind
> of way in the past, either in Nova or other projects ? If so, I'd be
> interested in how successful it was.
[...]
The new Keystone API used a feature branch,
On 2 September 2014 15:27, Matthew Booth wrote:
> We've been playing a game recently between oslo.vmware and the refactor
> series where a patch from the refactor series goes in, requiring a
> rebase of oslo.vmware daily. After a brief discussion with garyk earlier
> I decided to head that off by
Hello guys,
As you know, the heat-translator project was started early this year with
an aim to create a tool to translate non-Heat templates to HOT. It is a
StackForge project licensed under Apache 2. We have made good progress
with its development and a demo was given at the OpenStack 2014 A
On Tue, 2014-09-02 at 17:34 +0300, Dmitriy Ukhlov wrote:
> Hi Romain!
>
>
> Thank you for useful info about your Cassandra backuping.
It's always a pleasure to talk about Cassandra :)
>
> We have not tried to tune Cassandra compaction properties yet.
>
> MagnetoDB is DynamoDB-like REST API an
Doug
I agree with you but I need to understand the options. Susanne
>> And I agree with Brandon’s sentiments. We need to get something built
before I’m going to worry too
>> much about where it should live. Is this a candidate to get sucked into
LBaaS? Sure. Could the reverse
>> happen? Sure
Thanks everyone for your feedback. I think we have a consensus that this
sort of change would be best left to v2 of the API. We can start planning
v2 of the API at the Paris summit, and target some kind of “community
preview” of it to be released as part of Kilo.
On 8/29/14, 11:02 AM, "Everett Toe
By which John means "generally trying to avoid filling".
Michael
On Tue, Sep 2, 2014 at 10:52 AM, John Garbutt wrote:
> On 2 September 2014 15:27, Matthew Booth wrote:
>> We've been playing a game recently between oslo.vmware and the refactor
>> series where a patch from the refactor series goe
Yeah I've been worried about the term "driver" being overused here.
However, it might not be too bad if we get the other terminology correct
(network driver, vm/container/appliance driver, etc).
I was thinking of ML2 when I said Octavia living in the LBaaS tree might
be best. I was also thinking
On Tue, Sep 2, 2014 at 9:18 AM, Daniel P. Berrange wrote:
> I think it is reasonable to assume that our Juno work is easily capable
> of keeping the entire core team 100% busy until Kilo opens. So having
> people review v2.1 stuff on a feature branch is definitely going to
> impact the work we ge
Hi all,
Emma,
thanks for raising this topic, I've added it for the next Cinder weekly
meeting [1].
Duncan,
I absolutely agree with you that if any code could be located in a one
place, it must be there.
I'm not sure which place is the best for Brick: oslo or stackforge. Let's
discuss it. I want
Hi Susanne,
I believe the options for Octavia are:
1) Merge into the LBaaS tree (wherever LBaaS is)
2) Become its own openstack project
3) Remains in stackforge for eternity
#1 Is dependent on these options
1) LBaaS V2 graduates from the incubator into Neutron. V1 is deprecated.
2) LBaaS V2 remai
Sounds good to me too.
On 09/02/2014 08:20 AM, Doug Hellmann wrote:
> Oslo team,
>
> We need to consider how we are going to handle the approaching feature freeze
> deadline (4 Sept). We should, at this point, be focusing reviews on changes
> associated with blueprints. We will have time to fin
Hi,
I'll be on a long haul flight tonight from about 21:00 UTC. So... Once
feature freeze happens I'm not ignoring any freeze exceptions, it will
just take me a little while to get to them.
Michael
--
Rackspace Australia
___
OpenStack-dev mailing lis
On Fri 29 Aug 2014 03:03:34 PM PDT, James E. Blair wrote:
> It's the best way we have right now, until we have time to make it more
> self-service. We received one third-party CI request in 2 years, then
> we received 88 more in 6 months. Our current process is built around
> the old conditions.
Hi.
We're soon to hit feature freeze, as discussed in Thierry's recent
email. I'd like to outline the process for requesting a freeze
exception:
* your code must already be up for review
* your blueprint must have an approved spec
* you need three (3) sponsoring cores for an exception
Sure thing, I’ll add that to my list of things to try in “Round 2” (coming
later this week).
On 8/28/14, 9:05 AM, "Jay Pipes" wrote:
>On 08/26/2014 05:41 PM, Kurt Griffiths wrote:
>> * uWSGI + gevent
>> * config: http://paste.openstack.org/show/100592/
>> * app
Hello.
Currently for alpha releases of oslo libraries we generate either universal
or Python 2.x-only wheels. This presents a problem: we can't adopt alpha
releases in projects where Python 3.x is supported and verified in the
gate. I've ran into this in change request [1] generated after
global-r
On 09/02/2014 08:16 PM, Michael Still wrote:
> Hi.
>
> We're soon to hit feature freeze, as discussed in Thierry's recent
> email. I'd like to outline the process for requesting a freeze
> exception:
>
> * your code must already be up for review
> * your blueprint must have an approved sp
On 08/29/2014 11:17 AM, John Garbutt wrote:
> After moving to use ZNC, I find IRC works much better for me now, but
> I am still learning really.
There! this sentence has two very important points worth highlighting:
1- when people say IRC they mean IRC + a hack to overcome its limitation
2- IRC+
On Tue, Sep 2, 2014, at 11:30 AM, Yuriy Taraday wrote:
> Hello.
>
> Currently for alpha releases of oslo libraries we generate either
> universal
> or Python 2.x-only wheels. This presents a problem: we can't adopt alpha
> releases in projects where Python 3.x is supported and verified in the
> ga
Needing 3 out of 19 instead of 3 out of 20 isn't an order of magnatude
according to my calculator. Its much closer/fairer than making it 2/19 vs
3/20.
If a change is borderline in that it can only get 2 other cores maybe it
doesn't have a strong enough case for an exception.
Phil
Sent from
On Tue, Sep 2, 2014 at 1:40 PM, Nikola Đipanov wrote:
> On 09/02/2014 08:16 PM, Michael Still wrote:
>> Hi.
>>
>> We're soon to hit feature freeze, as discussed in Thierry's recent
>> email. I'd like to outline the process for requesting a freeze
>> exception:
>>
>> * your code must already be
On Tue, Sep 2, 2014 at 1:28 PM, Salvatore Orlando wrote:
> Inline.
> Salvatore
>
> On 2 September 2014 19:46, Stephen Balukoff wrote:
>>
>> For what it's worth in this discussion, I agree that the possible futures
>> of Octavia already discussed (where it lives, how it relates to Neutron
>> LBaaS
On 09/02/2014 02:50 PM, Stefano Maffulli wrote:
> On 08/29/2014 11:17 AM, John Garbutt wrote:
>> After moving to use ZNC, I find IRC works much better for me now, but
>> I am still learning really.
>
> There! this sentence has two very important points worth highlighting:
>
> 1- when people say I
On Mon, Sep 1, 2014 at 11:59 AM, Elizabeth K. Joseph
wrote:
> Hi everyone,
>
> The OpenStack Infrastructure (Infra) team is hosting our weekly
> meeting on Tuesday September 2nd, at 19:00 UTC in #openstack-meeting
Had quite the busy meeting! Thanks to everyone who participated.
Minutes and log no
It's been a while since we had a bug day. We now have 121 NEW bugs:
https://bugs.launchpad.net/tempest/+bugs?field.searchtext=&field.status%3Alist=NEW&orderby=-importance
The first order of business is to triage these bugs. This is a large
enough number that I hesitate to
mention anything else,
Just out of curiosity, what is the rational behind upping the number of
core sponsors for feature freeze exception to 3 if only two +2 are
required to merge? In Icehouse, IIRC, two core sponsors was deemed
sufficient.
Dan
On 09/02/2014 02:16 PM, Michael Still wrote:
Hi.
We're soon to hit fe
+1
On Sep 2, 2014 12:59 PM, Kyle Mestery wrote:
On Tue, Sep 2, 2014 at 1:28 PM, Salvatore Orlando wrote:
> Inline.
> Salvatore
>
> On 2 September 2014 19:46, Stephen Balukoff wrote:
>>
>> For what it's worth in this discussion, I agree that the possible futures
>> of Octavia already discussed (
Hi Kyle,
IMO, that depends entirely on how the incubator project is run. For now,
I'm in favor of remaining separate and letting someone else be the guinea
pig. :/ I think we'll (all) be more productive this way.
Also keep in mind that the LBaaS v2 code is mostly there (just waiting on
reviews),
Hi folks!
The preliminary agenda items are here:
https://wiki.openstack.org/wiki/Octavia/Weekly_Meeting_Agenda#Agenda
Please feel free to add agenda items as necessary.
Also, we're going to start keeping a weekly stand-up etherpad, so that
those working on the Octavia project know what other peo
Any objection? We need to move the time since the main meeting conflicts
with our current time slot.
Discussion from today's meeting:
http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-09-02-13.59.log.html
--
Sean M. Collins
_
I am not for this if Octavia is merged into the incubator when LBaaS V2
is, assuming LBaaS V2 will be merged into it before the summit. I'd
rather Octavia get merged into whatever repository it is destined to
whenever it is much more mature. If Octavia is merged into the
incubator too soon, I thi
Excerpts from Nejc Saje's message of 2014-09-01 07:48:46 +:
> Hey guys,
>
> in Ceilometer we're using consistent hash rings to do workload
> partitioning[1]. We've considered generalizing your hash ring
> implementation and moving it up to oslo, but unfortunately your
> implementation is no
The implementation in ceilometer is very different to the Ironic one -
are you saying the test you linked fails with Ironic, or that it fails
with the ceilometer code today?
The Ironic hash_ring implementation uses a hash:
def _get_partition(self, data):
try:
return (struct
On Tue, Sep 2, 2014 at 4:05 PM, Collins, Sean
wrote:
> Any objection? We need to move the time since the main meeting conflicts
> with our current time slot.
>
If you do that, I'll take over #openstack-meeting from you for the
Neutron meeting, so let me know once this meeting moves and I'll
update
Thanks Flavio, I added a few thoughts.
On 8/28/14, 3:27 AM, "Flavio Percoco" wrote:
>Greetings,
>
>I'd like to join the early coordination effort for design sessions. I've
>shamelessly copied Doug's template for Oslo into a new etherpad so we
>can start proposing sessions there.
>
>https://ether
Just wanted to let you know that sahara has move to server groups for
anti-affinity. This is IMHO the way we should so it as well.
Susanne
Jenkins (Code Review)
5:46 PM (0 minutes ago)
to Andrew, Sahara, Alexander, Sergey, Michael, Sergey, Vitaly, Dmitry,
Trevor
Jenkins has posted comments on th
Hi Guys
For the throughput tests I need to be able to install iperf on the cloud image.
For this DNS server needs to be set. But the current network context should
also support DNS name server setting
Should we add that into network context?
Ajay
From: Boris Pavlovic mailto:[email protected]>>
On 16 August 2014 02:43, Jeremy Stanley wrote:
> On 2014-08-13 19:51:52 -0500 (-0500), Ben Nemec wrote:
> [...]
>> make the check-tripleo job leave an actual vote rather than just a
>> comment.
> [...]
>
> That, as previously discussed, will require some design work in
> Zuul. Gerrit uses a single
Hi,
I have done some SQLite footgun elimination at Mozilla, was curious if
swift ran into similar issues.
>From blog posts like
http://blog.maginatics.com/2014/05/13/multi-container-sharding-making-openstack-swift-swifter/
and http://engineering.spilgames.com/openstack-swift-lots-small-files/ it
s
One recurring topic in our weekly meetings over the last few months has
been the fact that it's taking us longer and longer to review and land
patches. Right now, http://www.nemebean.com/reviewstats/tripleo-open.html
has the following stats:
- Stats since the latest revision:
1. Average w
Thank you all for the prompt response. And I'm glad to see the progress on this
topic.
Basically, what I'm thinking is the local storage support for big data and
large scale computing is specially useful.
I'll monitor the meeting progress actively.
Duncan,
And I'm interested to know the details
Preston,
Thanks for your support. What I mentioned Cinder Brick is described in this
wiki page: https://wiki.openstack.org/wiki/CinderBrick
Regards.
Emma
From: "Preston L. Bannister" mailto:[email protected]>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:op
On 2014-09-03 11:51:13 +1200 (+1200), Robert Collins wrote:
> I thought there was now a thung where zuul can use a different account
> per pipeline?
That was the most likely solution we discussed at the summit, but I
don't believe we've implemented it yet (or if we have then it isn't
yet being use
On 14 August 2014 11:03, James Polley wrote:
> In recent history, we've been looking each week at stats from
> http://russellbryant.net/openstack-stats/tripleo-openreviews.html to get a
> gauge on how our review pipeline is tracking.
>
> The main stats we've been tracking have been the "since the
Hey all,
I published a patch to add an Ironic API wrapper in Horizon. Having code up
for Horizon is a graduation requirement for Ironic, so I'd like some
eyeballs on it to at least tell us we're going in the right direction. I
understand this code won't land until after Ironic is integrated.
Anot
On 09/02/2014 10:13 PM, Sean Dague wrote:
One of the things that could make it better is to add file extensions to
all shell files in devstack. This would also solve the issue of gerrit
not syntax highlighting most of the files. If people are up for that,
I'll propose a rename patch to get us the
Well, git knows all the files in-tree, right? Or am I missing something here?
if-has-bash-hashbang-and-is-versioned-then-bashate-it?
-Rob
On 3 September 2014 13:26, Ian Wienand wrote:
> On 09/02/2014 10:13 PM, Sean Dague wrote:
>>
>> One of the things that could make it better is to add file ex
Hi Stackers,
Network TOPO like this: VM1(net1)--Router1---IPSec VPN
tunnel---Router2--VM2(net2)
If left and right side deploy on different OpenStack environments, it works
well. But in the same environment, Router1 and Router2 are namespace
implement in the same network node. I cannot ping
Hi,
Our CI system is disabled due to a running bug and wrong log link. I have
manually verified the system with sandbox and two Neutron testing patches.
However, with CI disabled, I am not able to see its review comment on any
patch.
Is there a way that I can see what the comment will look like w
On 08/25/2014 10:49 AM, Zane Bitter wrote:
On 24/08/14 23:17, Adam Young wrote:
On 08/23/2014 02:01 AM, Clint Byrum wrote:
I don't know how Zaqar does its magic, but I'd love to see simple
signed
URLs rather than users/passwords. This would work for Heat as well.
That
way we only have to pass
On Tue, Sep 2, 2014 at 8:32 PM, Robert Collins
wrote:
> Well, git knows all the files in-tree, right? Or am I missing something
> here?
>
> if-has-bash-hashbang-and-is-versioned-then-bashate-it?
It's not quote that simple, none of the include files have a shebang line;
I've always felt that hav
On 09/03/2014 11:32 AM, Robert Collins wrote:
if-has-bash-hashbang-and-is-versioned-then-bashate-it?
That misses library files that aren't execed and have no #!
This might be an appropriate rule for test infrastructure to generate a
list for their particular project, but IMO I don't think we
Hi, so as everyone knows I've been on an arc to teach pbr a lot more
about the semantic versioning we say we use (for all things) - with
the API servers being different, but a common set of code driving it.
We realised there's one quirky interaction today: since we fixed the
bug where pbr would cr
Hi,
Good to know we will have Ironic support. I can help the integration.
Let me clarify the situation as Horizon core team. I wonder why it is ASAP.
Horizon is released with integrated projects and it is true in Juno release
too.
Ironic is still incubated even if it is graduated for Kilo release
It seems -dev list is not an appropriate place to discuss it.
please use the general list. I replies to the general list.
2014年9月3日水曜日、Germy Lureさんは書きました:
> Hi Stackers,
>
> Network TOPO like this: VM1(net1)--Router1---IPSec VPN
> tunnel---Router2--VM2(net2)
> If left and right side deplo
On September 2, 2014 9:28:15 PM PDT, Akihiro Motoki wrote:
>Hi,
>
>Good to know we will have Ironic support. I can help the integration.
>
>Let me clarify the situation as Horizon core team. I wonder why it is
>ASAP.
>Horizon is released with integrated projects and it is true in Juno
>release
>
Right, the ASAP part is just to have a working Horizon for Ironic
(proposed, not merged) with most of the features we want as we move towards
the vote for graduation. We definitely understand the end-of-cycle crunch,
as we're dealing with the same in Ironic. I'm just looking for a general
"This cod
Thanks for the clarification. This input is really useful to Horizon team too.
I understand the goal is to know the beta implementation has the right
direction.
It is a good startline to discuss what it should be.
Thanks,
Akihiro
On Wed, Sep 3, 2014 at 2:02 PM, Josh Gachnang wrote:
> Right, the
Hi all:
currently oslo provides lock utility, but unlike other languages, it is
class lock, which prevent all instances call the function. IMO, oslo should
provide an instance lock, only lock current instance to gain better
concurrency.
I have written a lock in a patch[1], please consider pick it
Hi Ajay,
We are testing the same scenario that you are working one, but getting the
follow error:
http://paste.openstack.org/show/105029/
Could you be of any help here?
Thanks
On Wed, Sep 3, 2014 at 4:16 AM, Ajay Kalambur (akalambu) wrote:
> Hi Guys
> For the throughput tests I need to b
On Wed, 2014-09-03 at 12:58 +1200, Robert Collins wrote:
> On 14 August 2014 11:03, James Polley wrote:
> > In recent history, we've been looking each week at stats from
> > http://russellbryant.net/openstack-stats/tripleo-openreviews.html to get a
> > gauge on how our review pipeline is tracking.
93 matches
Mail list logo
