On Sat, 2013-09-21 at 09:16 -0400, Doug Hellmann wrote:
> I am running for PTL for the OpenStack Common Libraries (Oslo) project.
Excellent!
Doug has been a superb contributor to Oslo and I've particularly
appreciated his keen eye for Python API design. I've no doubt that Doug
would make a wonder
Hey
I meant to send this as soon as nominations opened - I figure that
incumbent PTLs should make it clear if they don't intend to nominate
themselves for re-election.
To that end - I'm not going to put myself forward for election as Oslo
PTL this time around. This is purely based on a gut instin
Thanks for a very complete answer.
While I agree that it's OK if there is only going to be one secret to use
the Accept type (it is actually a nice idea), it doesn't seem that MIME
types are really suitable if there are multiple secrets per URI.
So I don't think that fixing this should be punted
On 09/23/2013 01:36 PM, Thomas Goirand wrote:
> On 09/23/2013 11:04 AM, Pádraig Brady wrote:
>> OpenStack should be compatible with sqlalchemy 0.8.x at this stage,
>> or should be easily tweaked to be so.
>
> My view as well.
>
>> sqlalchemy-migrate will be a bit awkward though as upstream
>> see
On 09/23/2013 11:04 AM, Pádraig Brady wrote:
> OpenStack should be compatible with sqlalchemy 0.8.x at this stage,
> or should be easily tweaked to be so.
My view as well.
> sqlalchemy-migrate will be a bit awkward though as upstream
> seems to have moved to alembic and is no longer that interest
Hello Justin,
First off, the current implementation of Barbican only supports one encrypted
payload per secret record. We plan to revisit this once we begin work on the
SSL certificate processing features.
As for the Barbican API, please note that the latest Barbican API is located
here:
http
Looks like this problem happens in systems that use pip<1.4 but upgraded
tox to 1.6.1
http://tox.readthedocs.org/en/latest/config.html#confval-install_command=ARGV
On Fri, Sep 20, 2013 at 12:47 AM, Jeremy Stanley wrote:
> On 2013-09-19 09:24:08 +0800 (+0800), Yongsheng Gong wrote:
> [...]
> >
On 09/23/2013 03:36 AM, Thomas Goirand wrote:
> On 09/23/2013 05:43 AM, Monty Taylor wrote:
Since we now have at least some integration testing on our global
requirements list, I uploaded https://review.openstack.org/47745 to
see what breaks (though unit tests for individual projects
On 09/23/2013 05:43 AM, Monty Taylor wrote:
>>> Since we now have at least some integration testing on our global
>>> requirements list, I uploaded https://review.openstack.org/47745 to
>>> see what breaks (though unit tests for individual projects are not
>>> covered by this test and may also need
I am running for DevStack PTL. I have been the acting PTL since DevStack
became a program and have been working on DevStack since its first public
demo in a lightning talk at the Essex Design Summit. In addition I have
also contributed to Grenade and python-openstackclient.
Over the last develop
于 2013年09月17日 05:07, David Kang 写道:
Hi, David
this should be fixed.
Hi,
I'm testing PCI passthrough features on Havana (single node installation).
I've installed OpenStack on CentOS 6.4 using EPEL.
The pci_passthrough_filter doesn't seem to be able to get the object
'host_state.pci_stats'.
于 2013年09月21日 05:05, David Kang 写道:
- Original Message -
From: "Russell Bryant"
To: openstack-dev@lists.openstack.org
Sent: Friday, September 20, 2013 1:28:13 PM
Subject: Re: [openstack-dev] [nova] [pci passthrough] Is "extra_info" broken?
https://bugs.launchpad.net/nova/+bug/1223559
T
On 09/22/2013 01:47 PM, Thomas Goirand wrote:
> On 09/22/2013 11:36 PM, Jeremy Stanley wrote:
>> On 2013-09-22 23:00:26 +0800 (+0800), Thomas Goirand wrote:
>>> I already mentioned in this list that we need to be compatible with
>>> SQLAlchemy 0.8.x. However, I've seen both regressions happening
As part of my project to add a second implementation of the OpenStack API,
I'm implementing Barbican, and I'm struggling to understand the motivations
behind the API spec.
The API supports storing multiple secrets under a given key, the canonical
example for that being SSL keys which comprise a ce
Hi all,
I'm writing to declare my intention to run for OpenStack documentation
program technical lead. [1]
I've been working on OpenStack docs since September 2010, and it has been
an honor and a privilege to serve in this position informally prior to
having documentation declared a program. I've
On 09/22/2013 11:36 PM, Jeremy Stanley wrote:
> On 2013-09-22 23:00:26 +0800 (+0800), Thomas Goirand wrote:
>> I already mentioned in this list that we need to be compatible with
>> SQLAlchemy 0.8.x. However, I've seen both regressions happening in the
>> global-requirements.txt and in Ceilometer:
Thanks!
On 9/22/13 6:41 PM, "Sean Dague" wrote:
>On 09/22/2013 11:10 AM, Gary Kotton wrote:
>> Hi,
>> Anyone know why the devstack gating is broken?
>> Thanks
>> Gary
>
>I was just looking over logs, especially the last merge on integrated
>projects before things went funny (at about midnight la
Hello Neutron Folk:
Please stop +1'ing candidate announcements.
Thank you,
Anita.
Reference:
http://lists.openstack.org/pipermail/openstack-dev/2013-September/015381.html
http://lists.openstack.org/pipermail/openstack-dev/2013-September/015441.html
On 09/21/2013 11:31 PM, P Balaji-B37839 wrote
On 09/22/2013 11:10 AM, Gary Kotton wrote:
Hi,
Anyone know why the devstack gating is broken?
Thanks
Gary
I was just looking over logs, especially the last merge on integrated
projects before things went funny (at about midnight last night).
The root cause is guests not spawning, and going i
On 2013-09-22 23:00:26 +0800 (+0800), Thomas Goirand wrote:
> I already mentioned in this list that we need to be compatible with
> SQLAlchemy 0.8.x. However, I've seen both regressions happening in the
> global-requirements.txt and in Ceilometer:
>
> SQLAlchemy>=0.7.8,<=0.7.99
>
> Please, do not
Hi,
Anyone know why the devstack gating is broken?
Thanks
Gary
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi,
I already mentioned in this list that we need to be compatible with
SQLAlchemy 0.8.x. However, I've seen both regressions happening in the
global-requirements.txt and in Ceilometer:
SQLAlchemy>=0.7.8,<=0.7.99
Please, do not add <=0.7.99, this breaks badly, and all of OpenStack
really needs t
Hi,
At the moment the only driver that supports the PCI stats is libvirt. I think
that we need to ensure that that if the PCI stats are not reported by the
driver then the data structure is not accessed and the data base will not have
any unnecessary updates.
I have added the following fix for t
On Sun, Sep 22, 2013 at 10:35 AM, Thomas Goirand wrote:
> On 09/22/2013 10:10 PM, Doug Hellmann wrote:
> > I am working with the primary author on having a cmd2 release that uses
> > pyparsing 2.0.1. That will allow us to be consistent in specifying our
> > requirements.
>
> Oh! Is this related t
On 09/22/2013 10:10 PM, Doug Hellmann wrote:
> I am working with the primary author on having a cmd2 release that uses
> pyparsing 2.0.1. That will allow us to be consistent in specifying our
> requirements.
Oh! Is this related to cmd2?
> I'm not aware of any specific test failures though.
Just
On Sun, Sep 22, 2013 at 1:54 AM, Thomas Goirand wrote:
> Hi,
>
> Previously, upstream decided to use >= 1.5.7 for Python 2.x, then the
> 2.x branch for Python 3.x. Then later on, Python 2.x was added to the
> Pyparsing 2.x branch, and upstream released version 2.0.1, which has
> support for both
I would like to run for the OpenStack QA Program PTL position.
I'm the current/interim PTL for OpenStack QA, chosen when QA was
promoted to an official program mid cycle for Havana.
I started working on OpenStack just before the Essex release, and am
currently a core reviewer on Tempest, Devstack
Hi,
Although not a voting member, I would like to thank Mark for a phenomenal job
on Neutron and LBaaS and would like to see him continue to lead Neutron forward.
Regards,
-Sam.
-Original Message-
From: Mark McClain [mailto:mark.mccl...@dreamhost.com]
Sent: Friday, September 2
Hi all,
I think that TaskFlow is an interesting initiative that could provide us
some benefits like good encapsulation of logical code blocks, better
exception handling and management of actions taking place in Climate core,
rollbacks and replays management.
It looks like that we should initially
Big Plus 1 for Mark!
Great PTL and Excellent Job in Neutron!
Edgar
On Fri, Sep 20, 2013 at 1:44 PM, Mark McClain wrote:
>
> Hi-
>
> I writing to announce my candidacy for the OpenStack Networking (Neutron)
> PTL.
>
> I am the current Neutron PTL. Our team continued to grow during the
> Havana
30 matches
Mail list logo
