Hi everybody,
voting for discussion tool for OpenStack UX has ended. First of all I
want to give huge thanks to all interested and participated people. All
your votes and activities around were very helpful for us to back our
decision up.
The winner of voting is:
** Askbot (60.9 %)*
with
Silly pip, trix are for kids.
Ok, well:
sudo pip install -I oslo.config==1.1.1
then pip uninstall oslo.config
On 08/09/2013 06:58 PM, Roman Gorodeckij wrote:
stack@hp:~/devstack$ sudo pip install oslo.config
Requirement already satisfied (use --upgrade to upgrade): oslo.config in
I've been seeing some flakiness lately with launchpad not tracking Gerrit
status when a patch is proposed (changing the bug to 'In Progress') or
merged (changing the bug to 'Fix Committed'). Has anyone else experienced
this? Note that the bugs even show when a patch is proposed, change the
Here is one I saw today that was in progress but status was New:
https://bugs.launchpad.net/nova/+bug/1209134
This is another one I saw today in nova bug triage that was New but had
actually already been merged: https://bugs.launchpad.net/nova/+bug/1206330
A bit older but the first
On 2013-08-10 13:20:41 -0500 (-0500), Matt Riedemann wrote:
I've been seeing some flakiness lately with launchpad not tracking
Gerrit status when a patch is proposed (changing the bug to 'In
Progress') or merged (changing the bug to 'Fix Committed'). Has
anyone else experienced this? Note that
ok.. nothing changes..
stack@hp:~/devstack$ sudo pip install -I oslo.config==1.1.1
Downloading/unpacking oslo.config==1.1.1
Downloading oslo.config-1.1.1.tar.gz (75kB): 75kB downloaded
Running setup.py egg_info for package oslo.config
warning: no previously-included files found matching
Maybe sudo the 2nd cmd?
Sent from my digital shackles
On Aug 10, 2013, at 10:57 AM, Roman Gorodeckij ho...@holms.lt wrote:
ok.. nothing changes..
stack@hp:~/devstack$ sudo pip install -I oslo.config==1.1.1
Downloading/unpacking oslo.config==1.1.1
Downloading oslo.config-1.1.1.tar.gz
OK, I have the post on the new tags bookmarked so I've been sure to use
them in my latest commits but looking back at the ones I pointed out, they
were using something different so I suppose that's the issue (although the
hyper-v one of mine was before those changes went into effect, I think -
On 2013-08-10 21:04:01 -0500 (-0500), Matt Riedemann wrote:
[...]
the hyper-v one of mine was before those changes went into effect,
I think - it was merged back on 7/9).
[...]
It's entirely possible the hyper-v change you mention fell victim to
a temporary network connectivity or API
Since we can't guarantee that a volume, when attached, will become a
specified device name, we would like to be able to create a filesystem and
label it (so that we can programmatically interact with it when
provisioning systems, services, etc).
What we are trying to decide is whether this should
10 matches
Mail list logo
