Hi rezoo,
This is a known bug for HAavana, which has been fixed (but was not
backported), please see:
https://bugs.launchpad.net/neutron/+bug/1254555
Thanks,
Eugene.
On Sun, Jan 5, 2014 at 1:25 AM, rezroo r...@dslextreme.com wrote:
Hi all,
I'm testing the Havana devstack and I noticed that
You missed the pound sign. It is '/join #openstack-cinder' and not '/join
openstack-cinder' :)
Regards,
Rushi Agrawal
Ph: (+91) 99 4518 4519
On Thu, Jan 2, 2014 at 1:15 PM, Swapnil Kulkarni
swapnilkulkarni2...@gmail.com wrote:
Just got connected!!! Strange :|
Thanks :)
Best Regards,
Greetings,
Here come a question related to AvailabilityZoneFilter.
A new project Gantt which is a common scheduler for OpenStack is now under
incubation, and now most of the code are get from nova scheduler.
I'm planning to make Gantt use common scheduler from oslo, and I think that
this is the
Excerpts from Rushi Agrawal's message of 2014-01-05 05:41:58 -0800:
I can see people arguing in future over which top IDE's/editor's trashfiles
should or shouldn't be included in the gitignores. Also, I believe the
concept of global gitignore is a fantastic one.
Has it ever actually
On Sun, 2014-01-05 at 10:47 -0500, Sean Dague wrote:
While waiting some inordinate amount of time to compile lxml for a
tempest pep8 test, I started to wonder why is it that we are using -U on
all our pip install commands in tox (it's a pretty common pattern across
projects).
It seems
Hi Jay,
I have 3 points:
First of all:
https://github.com/openstack/gantt/
Why this project has all history of Nova? It seems very odd way to create
new project aka clone Nova remove all from Nova..
Second:
This blueprint https://blueprints.launchpad.net/nova/+spec/no-db-schedulershould
be
With regards to the futures module it should just work fine with the packaging
of https://pypi.python.org/pypi/futures which is a backport of the 3.2
concurrent futures package into 2.6,2.7, so that's the package there.
Feel free to bug me on irc if u want any other help with dependencies, the
Excerpts from Sean Dague's message of 2014-01-05 07:47:22 -0800:
While waiting some inordinate amount of time to compile lxml for a
tempest pep8 test, I started to wonder why is it that we are using -U on
all our pip install commands in tox (it's a pretty common pattern across
projects).
I've skimmed the rest of the thread and not seen something mentioned
that seems like it matters a lot. If I missed this suggestion buried
deep in the ensuing discussion, I apologize for that.
Since TaskFlow wants to be generally consumable and not only driven as
an OpenStack component, it should
On 2014-01-05 07:40:52 -0800 (-0800), Clint Byrum wrote:
[...]
We have Oslo for algorithms, not configurations. We have global
requirements to control external _dependencies_. This is about
neither. Leave them in, add them when people submit them. How is
this at all hard or controversial to
On 2014-01-05 10:47:22 -0500 (-0500), Sean Dague wrote:
[...]
It seems like requirements should be sufficient. Forcing -U to the
latest all the time seems like it would actually mask a ton of
problems, and makes sitepackages = True to be largely useless.
[...]
In fact, I believe it was mostly
Thanks Jay Pipes and Boris for the comments.
@Jay Pipes, agree, I can name it as AvailabilityZoneAggregateFilter.
@Boris,
For your first question, we may want to get some answer from @Robert
Collins.
For second question, perhaps you can refer to
Agreed, we are going to expand it and work on figuring out how to test against
multiple versions. It does work with 0.8 and it seems even like 0.9 works fine
also. But all compatible also means I can't guarantee 0.10 (if it comes out)
will work since afaik semver means sqlalchemy could still
Excerpts from Herndon, John Luke's message of 2014-01-03 08:17:15 -0800:
On 1/2/14, 7:06 PM, Sean Dague s...@dague.net wrote:
On 01/02/2014 08:36 PM, Robert Collins wrote:
On 3 January 2014 14:34, Robert Collins robe...@robertcollins.net
wrote:
On 3 January 2014 12:40, Herndon, John
On 01/05/2014 11:25 AM, Jeremy Stanley wrote:
On 2014-01-05 10:47:22 -0500 (-0500), Sean Dague wrote:
[...]
It seems like requirements should be sufficient. Forcing -U to the
latest all the time seems like it would actually mask a ton of
problems, and makes sitepackages = True to be largely
On 2014-01-05 12:17:41 -0500 (-0500), Sean Dague wrote:
Well that's really unfortunate.
So if I understand that correctly there is *no* way to configure tox
+ pip to:
* use site packages if they are sufficient to requirements.txt
* install packages into venv if they are not (i.e. only
Hi folks,
thank you all for participating elections (80% participation).
Here are the results of the PTL election process [0].
Congratulations to the Climate PTL for Icehouse release: *Dina Belova*!
Elections process has been recorded in [1].
[0]
As a follow-up, I've filed this bug:
https://bugs.launchpad.net/nova/+bug/1266262
We'll be working around this in TripleO by setting
default_ephemeral_format for our baremetal clouds, but I feel we should
document in Icehouse's release notes that the default will be changed
to ext4 in Juno, so
Well done Climate electorate, 80% participation is a great rate.
Thank you to both candidates for running.
Congratulations Dina, I look forward to working with you as PTL.
Nicely run election, Sergey.
Good work,
Anita.
On 01/06/2014 02:15 AM, Sergey Lukjanov wrote:
Hi folks,
thank you all
Joshua Harlow harlo...@yahoo-inc.com writes:
It seems simple to have variations of venvs (or something similar)
that taskflow tox.ini can have that specify the different 0.7, 0.8,
0.9, when sqlalchemy 1.0 comes out then this should become a nonissue
(hopefully). I will bug the infra folks to
On 01/05/2014 03:42 AM, Sukhdev Kapur wrote:
Folks,
I finally got over my fear of weather and booked my flight and hotel for
this sprint.
I am relatively new to OpenStack community with a strong desire to learn
and contribute.
Having a strong desire to participate effectively is great.
Sean Dague s...@dague.net writes:
I think the main user-visible aspect of this decision is the delay
before unprocessed bugs are made visible. If a bug starts affecting a
number of jobs, it might be nice to see what bug numbers people are
using for rechecks without waiting for the next cron
Kudos to Dina for the PTL position. 3 vs. 5 with 80% participation means
it's a good thing for Climate : this is not a Stackforge project pushed by
only one sponsor and having a benevolent dictator, but rather a mix of
various experiences and subprojects with people having various ideas.
Now,
On 01/05/2014 05:49 PM, James E. Blair wrote:
Sean Dague s...@dague.net writes:
I think the main user-visible aspect of this decision is the delay
before unprocessed bugs are made visible. If a bug starts affecting a
number of jobs, it might be nice to see what bug numbers people are
using
Thank you guys :)
Climate really has good community and it's a great opportunity for us to
present our ideas to the world :)
Anita, I believe we'll do the great job all together.
Sylvain, I remember about 0.1 ;) Although in Russia we still have Christmas
holidays, I'll find some day this week
25 matches
Mail list logo
