Gabriel Hurley gabriel.hur...@nebula.com writes:
Hi Gabriel,
As the former Horizon PTL, I have a great respect for the importance
of the contributions the distro maintainers/developers make to Horizon
and OpenStack as a whole. From how many bugs the distros manage to
find, to their diligence
1. *make a minor concession to proportionality* - while keeping the
focus on consensus, e.g. by adopting the proportional Condorcet
variant.
It would be interesting to see the analysis again, but in the past this
proved to not make much difference.
For the record, I
It's certainly not a fun thing to do (trying to guide a
community of disjoint folks) and it likely comes with little
recognition when successful, but IMHO we surely need more of
this active technical leadership vs. blessing of projects; of
course the boundary between being a engaging
Testtools 1.2.0 release apparently broke subunit.run discover --list
which breaks the way that tempest calls the test chain. No tempest runs
have passed since it's release.
https://review.openstack.org/#/c/134705/ is a requirements pin, though I
think because of grenade this is actually going to
Sean,
I can baby sit these 3
thanks,
dims
On Sat, Nov 15, 2014 at 9:25 AM, Sean Dague s...@dague.net wrote:
Testtools 1.2.0 release apparently broke subunit.run discover --list
which breaks the way that tempest calls the test chain. No tempest runs
have passed since it's release.
On 11/14/2014 09:11 PM, Jeremy Stanley wrote:
Categories emerge automatically as you tag pages into them. No
separate category creation step is required.
True although incomplete. Categories are just pages, like almost
anything in mediawiki, so if you add text [[Category: New_Category]] in
a
On 2014-11-15 09:25:54 -0500 (-0500), Sean Dague wrote:
Testtools 1.2.0 release apparently broke subunit.run discover --list
[...]
Also... lets try not to release libraries on Fridays before disappearing
for the weekend... please. Pretty please.
Also reported upstream as
On 2014-11-15 16:37:50 +0100 (+0100), Stefano Maffulli wrote:
[...]
If you don't create the New_Category page, it will end up in the
'wantedCategories' special page:
https://wiki.openstack.org/wiki/Special:WantedCategories
[...]
Oh, neat! This is a new feature. In older* versions it just
On 15 November 2014 14:25, Sean Dague s...@dague.net wrote:
Testtools 1.2.0 release apparently broke subunit.run discover --list
which breaks the way that tempest calls the test chain. No tempest runs
have passed since it's release.
https://review.openstack.org/#/c/134705/ is a requirements
It probably needs to be backed out of stable/icehouse. The issue is
that we were installing unittest2 via distro packages *and* testtools
new dependency on unittest2 did not express a minimum version.
We're just about to issue 1.2.1 which will have such a minimum version.
And for the record,
On 15 November 2014 19:51, Robert Collins robe...@robertcollins.net wrote:
It probably needs to be backed out of stable/icehouse. The issue is
that we were installing unittest2 via distro packages *and* testtools
new dependency on unittest2 did not express a minimum version.
We're just about
On 2014-11-16 08:51:34 +1300 (+1300), Robert Collins wrote:
[...]
The issue is that we were installing unittest2 via distro packages
*and* testtools new dependency on unittest2 did not express a
minimum version.
[...]
BTW, patches to stop installing unittest2 from distro packages in
devstack:
On 16 November 2014 03:25, Sean Dague s...@dague.net wrote:
Testtools 1.2.0 release apparently broke subunit.run discover --list
which breaks the way that tempest calls the test chain. No tempest runs
have passed since it's release.
https://review.openstack.org/#/c/134705/ is a requirements
On 16 November 2014 09:03, Dave Walker em...@daviey.com wrote:
On 15 November 2014 19:51, Robert Collins robe...@robertcollins.net wrote:
It probably needs to be backed out of stable/icehouse. The issue is
that we were installing unittest2 via distro packages *and* testtools
new dependency on
On 15 November 2014 20:23, Robert Collins robe...@robertcollins.net wrote:
On 16 November 2014 09:03, Dave Walker em...@daviey.com wrote:
On 15 November 2014 19:51, Robert Collins robe...@robertcollins.net wrote:
It probably needs to be backed out of stable/icehouse. The issue is
that we were
On 16 November 2014 09:38, Dave Walker em...@daviey.com wrote:
On 15 November 2014 20:23, Robert Collins robe...@robertcollins.net wrote:
On 16 November 2014 09:03, Dave Walker em...@daviey.com wrote:
On 15 November 2014 19:51, Robert Collins robe...@robertcollins.net wrote:
It probably needs
On 2014-11-15 20:38:02 + (+), Dave Walker wrote:
You are right, I accidently folded two issues into 1. However, I do
not understand how we can resolve this issue the way you have outlined
without introducing a new minimum version on unittest2, which was not
previously a requirement on
Doug,
I can help with oslo library releases this cycle.
thanks,
dims
On Fri, Nov 14, 2014 at 10:23 AM, Doug Hellmann d...@doughellmann.com wrote:
Last cycle Thierry put together a tool to make releasing Oslo libraries
easier for us. Using the tool will ensure that all of our releases are
On 15 November 2014 21:22, Jeremy Stanley fu...@yuggoth.org wrote:
On 2014-11-15 20:38:02 + (+), Dave Walker wrote:
You are right, I accidently folded two issues into 1. However, I do
not understand how we can resolve this issue the way you have outlined
without introducing a new
On 16 November 2014 09:06, Robert Collins robe...@robertcollins.net wrote:
On 16 November 2014 03:25, Sean Dague s...@dague.net wrote:
Testtools 1.2.0 release apparently broke subunit.run discover --list
which breaks the way that tempest calls the test chain. No tempest runs
have passed since
During the Kilo design summit session on Oslo versioning changes, we
mostly resolved to switch to semver without alphas and pin stable
branch libs to less than the next nontrivial version number
(allowing for backports to fix bugs with subsequent point releases
on a stable branch when needed).
Thanks Xin,i will try for a separate license for snapshot and see how it
goes.
Can you help me understand this better.
in my existing cinder volume which is a single server that act as iscsi
target , i use LVM in qcow2 disk format and it has thin provisioning and
snapshot capability.
With VNX
Hi all, I just set up keystone with apache(2.2.15) and mod_wsgi. It runs
perfectly.
But when I tested my own application, it threw an exception of 404 Not
Found, because it accessed the url: http://192.168.242.10:/35357/v2.0
And I curl to get keystone versions, the result is weird.
Here's
On Saturday 15 November 2014 12:25:23 Li Ma wrote:
Hi all, I just set up keystone with apache(2.2.15) and mod_wsgi. It runs
perfectly.
But when I tested my own application, it threw an exception of 404 Not
Found, because it accessed the url: http://192.168.242.10:/35357/v2.0
And I curl to
Li Ma skywalker.n...@gmail.com wrote on 11/15/2014 04:25:23 AM:
From: Li Ma skywalker.n...@gmail.com
To: openstack@lists.openstack.org openstack@lists.openstack.org
Date: 11/15/2014 04:32 AM
Subject: [Openstack] weird behavior of keystone+apache+mod_wsgi
Hi all, I just set up keystone with
HelloOo Nicolas
Its very nice, congrats!
I'm not a front-end developer, but I think if we are able Pin some of
components and make them static, we can use it in our conferences. I
suggest double click or Ctrl + Left Click to force a circle to be
static and not moving. You can also add the online
On 2014/11/15 17:40, Boris Bobrov wrote:
On Saturday 15 November 2014 12:25:23 Li Ma wrote:
Hi all, I just set up keystone with apache(2.2.15) and mod_wsgi. It runs
perfectly.
But when I tested my own application, it threw an exception of 404 Not
Found, because it accessed the url:
On Saturday 15 November 2014 14:42:56 Li Ma wrote:
On 2014/11/15 17:40, Boris Bobrov wrote:
On Saturday 15 November 2014 12:25:23 Li Ma wrote:
Hi all, I just set up keystone with apache(2.2.15) and mod_wsgi. It runs
perfectly.
But when I tested my own application, it threw an exception of
Hi,
If all your application needs is a connection between the instances, just
connect all three instances on same virtual network.
Then check nova security group rules (think of it like you would of a firewall)
add rules for needed ports and that's it.
Instances should be able to access one
29 matches
Mail list logo
