Hi Doug
thanks. We will test this next week
regards
David
On 19/09/2014 18:43, Doug Hellmann wrote:
>
> On Sep 19, 2014, at 6:56 AM, David Chadwick wrote:
>
>>
>>
>> On 18/09/2014 22:14, Doug Hellmann wrote:
>>>
>>> On Sep 18, 2014, at 4:34 PM, David Chadwick
>>> wrote:
>>>
O
On Tue, Sep 23, 2014 at 8:40 AM, Doug Hellmann wrote:
>
> On Sep 22, 2014, at 8:05 PM, Devananda van der Veen
> wrote:
>
>> On Mon, Sep 22, 2014 at 2:27 PM, Doug Hellmann wrote:
>>>
>>> On Sep 22, 2014, at 5:10 PM, Devananda van der Veen
>>> wrote:
>>>
One of the primary effects of integ
Agree with all the comments made - Dolph, you really did a great job as PTL -
keeping the balanced view is a crucial part of the role. Keystone is the
better for it.
Henry
On 23 Sep 2014, at 17:08, Yee, Guang wrote:
> ++ Amen, brother!
>
> From: Lance Bragstad [mailto:lbrags...@gmail.com]
On Sep 23, 2014, at 7:53 AM, Daniel P. Berrange wrote:
> On Tue, Sep 23, 2014 at 07:42:30AM -0400, Sean Dague wrote:
>> On 09/23/2014 02:56 AM, Thierry Carrez wrote:
>>> Hi everyone,
>>>
>>> Rather than waste a design summit session about it, I propose we review
>>> the proposed Kilo release cy
On 23 September 2014 15:57, John Griffith wrote:
> Hey Everyone,
>
> I've been kinda mixed on this one, but I think it's a good time for me to
> not run for Cinder PTL. I've been filling the role since we started the
> idea back at the Folsom Summit, and it's been an absolute pleasure and honor
>
On 22 September 2014 23:14, Robert Collins wrote:
> I am not at all sure we've prevented other flowers blooming -
> and I hate the idea that we have done that.
I've certainly sat around at discussions which shut down hard with
somebody making the statement that 'that is TripleO's field and they
d
On 22/09/14 22:04, Joe Gordon wrote:
To me this is less about valid or invalid choices. The Zaqar team is
comparing Zaqar to SQS, but after digging into the two of them, zaqar
barely looks like SQS. Zaqar doesn't guarantee what IMHO is the most
important parts of SQS: the message will be delivere
++ Amen, brother!
From: Lance Bragstad [mailto:lbrags...@gmail.com]
Sent: Tuesday, September 23, 2014 7:52 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [keystone] Stepping down as PTL
On Tue, Sep 23, 2014 at 3:51 AM, Thierry Carrez wrot
On 09/22/2014 05:29 AM, Kenichi Oomichi wrote:
-Original Message-
From: Alex Xu [mailto:x...@linux.vnet.ibm.com]
Sent: Friday, September 19, 2014 3:40 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Nova] Some ideas for micro-version implementation
Close to Kilo, it i
On 09/22/2014 04:27 PM, Brant Knudson wrote:
On Fri, Sep 19, 2014 at 1:39 AM, Alex Xu mailto:x...@linux.vnet.ibm.com>> wrote:
Close to Kilo, it is time to think about what's next for nova API.
In Kilo, we
will continue develop the important feature micro-version.
In previous v2
Since there are no major updates and some folks will not be able to
join Murano weekly meeting, we've decided to skip it for today.
Short update:
1. The only remaining major item left for juno is documentation and
everyone is pretty aware about items we need to have in our docs:
https://etherpad.o
On 2014-09-23 15:26:20 + (+), Amir Sadoughi wrote:
> Instead of moving the Kilo cycle a week later (April 23 -> April
> 30), would it be possible to move the "L" design summit a week
> ahead (May 18-22 -> May 11-15). This would extend the L-cycle a
> week. Additionally, this would also help
On Sep 22, 2014, at 8:05 PM, Devananda van der Veen
wrote:
> On Mon, Sep 22, 2014 at 2:27 PM, Doug Hellmann wrote:
>>
>> On Sep 22, 2014, at 5:10 PM, Devananda van der Veen
>> wrote:
>>
>>> One of the primary effects of integration, as far as the release
>>> process is concerned, is being
Instead of moving the Kilo cycle a week later (April 23 -> April 30), would it
be possible to move the "L" design summit a week ahead (May 18-22 -> May
11-15). This would extend the L-cycle a week. Additionally, this would also
help with return travel as the following Monday is Memorial Day; I'd
On Sep 23, 2014, at 5:18 AM, Thierry Carrez wrote:
> Devananda van der Veen wrote:
>> On Mon, Sep 22, 2014 at 2:27 PM, Doug Hellmann wrote:
>>> On Sep 22, 2014, at 5:10 PM, Devananda van der Veen
>>> wrote:
>>>
One of the primary effects of integration, as far as the release
proces
On Sep 23, 2014, at 4:35 AM, Thomas Goirand wrote:
> On 09/18/2014 10:04 PM, Doug Hellmann wrote:
>> All of the final releases for the Oslo libraries for the Juno cycle are
>> available on PyPI. I’m working on a couple of patches to the global
>> requirements list to update the baseline in the
On 23/09/14 08:58, Flavio Percoco wrote:
I believe the guarantee is still useful and it currently does not
represent an issue for the service nor the user. 2 things could happen
to FIFO in the future:
1. It's made optional and we allow users to opt-in in a per flavor
basis. (I personally don't l
Hey Everyone,
I've been kinda mixed on this one, but I think it's a good time for me to
not run for Cinder PTL. I've been filling the role since we started the
idea back at the Folsom Summit, and it's been an absolute pleasure and
honor for me.
I don't plan on going anywhere and will still be in
Sean Dague wrote:
> On 09/23/2014 02:56 AM, Thierry Carrez wrote:
>> Hi everyone,
>>
>> Rather than waste a design summit session about it, I propose we review
>> the proposed Kilo release cycle schedule on the mailing-list. See
>> attached PDF for a picture of the proposal.
>>
>> The hard date the
On Tue, Sep 23, 2014 at 3:51 AM, Thierry Carrez
wrote:
> Adam Young wrote:
> > OpenStack owes you more than most people realize.
>
> +1
>
> Dolph did a great job of keeping the fundamental piece that is Keystone
> safe from a release management perspective, by consistently hitting all
> the deadl
confirmed
On 23/09/14 10:19 AM, Duncan Thomas wrote:
> This is an announcement of my standing for PTL of the Cinder project.
>
> I've been an active member of the Cinder core team from day one, and
> I've had the pleasure of working closely with John Griffith, the
> incumbent PTL, and a large and
This is an announcement of my standing for PTL of the Cinder project.
I've been an active member of the Cinder core team from day one, and
I've had the pleasure of working closely with John Griffith, the
incumbent PTL, and a large and varied collection of contributors for
that period.
My job is r
I am really sorry to see you step down, but congratulations!
cheers,
brian
From: Mark Washenberger [mark.washenber...@markwash.net]
Sent: Monday, September 22, 2014 12:22 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Glance] PTL Non-Candidacy
On 09/23/2014 05:11 AM, Mac Innes, Kiall wrote:
Hi all,
I'd like to announce my candidacy for the DNS Services Program PTL
position.
I’ve been involved in Designate since day one, as the both original
author and as pseudo-PTL pre-incubation. Designate and the DNS
Services program have come
On 2014-09-23 12:53:42 +0100 (+0100), Daniel P. Berrange wrote:
> I didn't really notice anyone stop working in the last off-week we
> had. Changes kept being submitted at normal rate, people kept talking
> on IRC, etc, etc. An off-week is a nice idea in theory but it didn't
> seem to have much eff
confirmed
On 23/09/14 07:11 AM, Mac Innes, Kiall wrote:
> Hi all,
>
>
> I'd like to announce my candidacy for the DNS Services Program PTL position.
>
>
> I've been involved in Designate since day one, as the both original author
> and as pseudo-PTL pre-incubation. Designate and the DNS Servi
On 23-Sep-14 09:42, Clint Byrum wrote:
> Excerpts from Angus Salkeld's message of 2014-09-22 20:15:43 -0700:
>> On Tue, Sep 23, 2014 at 1:09 AM, Anant Patil wrote:
>>
>>> Hi,
>>>
>>> One of the steps in the direction of convergence is to enable Heat
>>> engine to handle concurrent stack operations
confirmed
On 23/09/14 12:58 AM, Mike Perez wrote:
> Hello all,
>
> My name is Mike Perez, and I would like to be your next PTL for the OpenStack
> block storage project Cinder.
>
> I've been involved with the OpenStack community since October 2010. I'm
> a senior developer for Datera, which cont
confirmed
On 23/09/14 05:10 AM, Eoghan Glynn wrote:
>
> Folks,
>
> I'd like to continue serving as Telemetry PTL for a second cycle.
>
> When I took on the role for Juno, I saw some challenges facing the
> project that would take multi-cycle efforts to resolve, so I'd like to
> have the opportu
On 22 September 2014 21:49, Mark McClain wrote:
> Ideally, I think something that provides proper sync support should exist in
> Keystone or a Keystone related project vs multiple implementations in
> Neutron, Cinder or any other multi-tenant service that wants to provide more
> human friendly na
On 09/23/2014 10:58 AM, Gordon Sim wrote:
> On 09/22/2014 05:58 PM, Zane Bitter wrote:
>> On 22/09/14 10:11, Gordon Sim wrote:
>>> As I understand it, pools don't help scaling a given queue since all the
>>> messages for that queue must be in the same pool. At present traffic
>>> through different
On 2014年09月23日 17:12, Christopher Yeoh wrote:
On Mon, 22 Sep 2014 09:29:26 +
Kenichi Oomichi wrote:
Before discussing how to implement, I'd like to consider what we
should implement. IIUC, the purpose of v3 API is to make consistent
API with the backwards incompatible changes. Through huge
Hi stackers,
I have an idea about service provider framework. Anyone interested in this
topic can give me some suggestions.
My idea is that providers report their services capability dynamically not
configured in neutron.conf. See details by the link below.
https://docs.google.com/presentation/d/
On 23/09/2014 12:58 PM, "Clint Byrum" wrote:
>
> Excerpts from Geoff O'Callaghan's message of 2014-09-22 17:30:47 -0700:
> > On 23/09/2014 1:59 AM, "Clint Byrum" wrote:
> > >
> > > Geoff, do you expect all of our users to write all of their messaging
> > > code in Python?
> > >
> > > oslo.messagi
Zigo,
Ouch! Can you please open a bug in oslo.messaging, i'll mark it critical
thanks,
dims
On Tue, Sep 23, 2014 at 4:35 AM, Thomas Goirand wrote:
> On 09/18/2014 10:04 PM, Doug Hellmann wrote:
>> All of the final releases for the Oslo libraries for the Juno cycle are
>> available on PyPI. I’m
On Tue, Sep 23, 2014 at 07:42:30AM -0400, Sean Dague wrote:
> On 09/23/2014 02:56 AM, Thierry Carrez wrote:
> > Hi everyone,
> >
> > Rather than waste a design summit session about it, I propose we review
> > the proposed Kilo release cycle schedule on the mailing-list. See
> > attached PDF for a
On 09/23/2014 02:56 AM, Thierry Carrez wrote:
> Hi everyone,
>
> Rather than waste a design summit session about it, I propose we review
> the proposed Kilo release cycle schedule on the mailing-list. See
> attached PDF for a picture of the proposal.
>
> The hard date the proposal is built around
Hi all,
I'd like to announce my candidacy for the DNS Services Program PTL position.
I've been involved in Designate since day one, as the both original author and
as pseudo-PTL pre-incubation. Designate and the DNS Services program have come
a long way since the project was first introduced
Hi Mark,
Many thanks for your leadership, and keeping glance so enjoyable to work on
over the last few cycles.
-Stuart
From: Mark Washenberger
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Glance] PTL Non-Candidacy
Message-ID:
Content-Type: text/plain; charset="utf-8"
G
On Tue, Sep 23, 2014 at 02:27:52PM +0400, Roman Bogorodskiy wrote:
> Michael Still wrote:
>
> > Hi.
> >
> > I know we've been talking about deprecating nova.virt.disk.vfs.localfs
> > for a long time, in favour of wanting people to use libguestfs
> > instead. However, I can't immediately find an
On Tue, 23 Sep 2014 09:00:26 +0900
"Ken'ichi Ohmichi" wrote:
\>
> So how about just using HTTP 200(OK) only for status codes?
> That would give up providing accurate internal status to clients but
> backwards backwards incompatibilities never happen.
>
No I think that we should where possible re
On Mon, 22 Sep 2014 15:27:47 -0500
Brant Knudson wrote:
> >
> >
> Did you consider JSON Home[1] for this? For Juno we've got JSON Home
> support in Keystone for Identity v3 (Zaqar was using it already). We
> weren't planning to use it for microversioning since we weren't
> planning on doing micro
On Mon, 22 Sep 2014 09:47:50 -0500
Anne Gentle wrote:
> >
> > (1) Input/Output attribute names
> > (1.1) These names should be snake_case.
> > eg: imageRef -> image_ref, flavorRef -> flavor_ref, hostId ->
> > host_id (1.2) These names should contain extension names if they
> > are provided in ca
Sorry for the delay. django-openstack-auth 1.1.7 was released last Friday and
it seems David forgot to update global requirements.
Now let me clarify how to handle this kind of bugs which requires a
fix in a library after the release.
What is the appropriate way to fix a bug depending on libraries
Michael Still wrote:
> Hi.
>
> I know we've been talking about deprecating nova.virt.disk.vfs.localfs
> for a long time, in favour of wanting people to use libguestfs
> instead. However, I can't immediately find any written documentation
> for when we said we'd do that thing.
>
> Additionally,
I am ok with a staged approach, although I do think its something we
should start in Kilo. That said though, we emit a warning if the
installation doesn't have a working libguestfs in juno.
Michael
On Tue, Sep 23, 2014 at 8:09 PM, Daniel P. Berrange wrote:
> On Tue, Sep 23, 2014 at 09:53:36AM +1
Excerpts from Steven Hardy's message on 23/09/2014 11:37:42:
> >
> > On the other hand, there is a big downside to having it (only) in Heat
also
> > - you're dependent on the operator deciding to provide it.
> >
> > >- You prempt the decision about integration with any higher
levelservices,
> > >
On Tue, Sep 23, 2014 at 09:53:36AM +1000, Michael Still wrote:
> Hi.
>
> I know we've been talking about deprecating nova.virt.disk.vfs.localfs
> for a long time, in favour of wanting people to use libguestfs
> instead. However, I can't immediately find any written documentation
> for when we said
Greetings,
I recently published a post[0] about Zaqar's path going forward with the
hope to clarify a bit the project's vision and guarantees as a service -
I didn't mention API features.
Since we've been talking about this lately, I thought to share the post
here to ease the discussion and to ki
On Tue, Sep 23, 2014 at 12:40 PM, Nikesh Kumar Mahalka <
nikeshmaha...@vedams.com> wrote:
> Hi,
> I am able to do all volume operations through dashboard and cli commands.
> But when i am running tempest tests,some tests are getting failed.
> For contributing cinder volume driver for my client in
Akihiro Motoki wrote:
> I would like to request dependency freeze exceptions for
> django-openstack-auth.
> https://review.openstack.org/#/c/123101/
This arguably counts as an internal library. We are freezing those now
(well, last Friday was the deadline), so +1 on this one.
--
Thierry Carrez
On 09/23/2014 05:13 AM, Clint Byrum wrote:
> Excerpts from Joe Gordon's message of 2014-09-22 19:04:03 -0700:
[snip]
>>
>> To me this is less about valid or invalid choices. The Zaqar team is
>> comparing Zaqar to SQS, but after digging into the two of them, zaqar
>> barely looks like SQS. Zaqar
Hi,
I am able to do all volume operations through dashboard and cli commands.
But when i am running tempest tests,some tests are getting failed.
For contributing cinder volume driver for my client in cinder,do all
tempest tests should passed?
Ex:
1)
./run_tempest.sh tempest.api.volume.test_volumes
On Fri, Sep 19, 2014 at 06:54:27PM -0400, Zane Bitter wrote:
> On 09/09/14 05:52, Steven Hardy wrote:
> >Hi Sahdev,
> >
> >On Tue, Sep 02, 2014 at 11:52:30AM -0400, Sahdev P Zala wrote:
> >>Hello guys,
> >>
> >>As you know, the heat-translator project was started early this year
> >> with
Robert Collins wrote:
> On 19 September 2014 22:29, Thierry Carrez wrote:
> ...
>> current Heat team is not really interested in maintaining them. What's
>> the point of being under the same program then ? And TripleO is not the
>> only way to deploy OpenStack, but its mere existence (and name)
>>
Devananda van der Veen wrote:
> On Mon, Sep 22, 2014 at 2:27 PM, Doug Hellmann wrote:
>> On Sep 22, 2014, at 5:10 PM, Devananda van der Veen
>> wrote:
>>
>>> One of the primary effects of integration, as far as the release
>>> process is concerned, is being allowed to co-gate with other
>>> inte
On Mon, 22 Sep 2014 09:29:26 +
Kenichi Oomichi wrote:
>
> Before discussing how to implement, I'd like to consider what we
> should implement. IIUC, the purpose of v3 API is to make consistent
> API with the backwards incompatible changes. Through huge discussion
> in Juno cycle, we knew that
Folks,
I'd like to continue serving as Telemetry PTL for a second cycle.
When I took on the role for Juno, I saw some challenges facing the
project that would take multi-cycle efforts to resolve, so I'd like to
have the opportunity to see that move closer to completion.
Over Juno, our focus as
Hi,
I would like to request dependency freeze exceptions for django-openstack-auth.
https://review.openstack.org/#/c/123101/
django-openstack-auth is developped along with Horizon and the recent
release 1.1.7 of django-openstack-auth has good fixes which affect
Juno Horizon, especially from the f
On 09/22/2014 05:58 PM, Zane Bitter wrote:
On 22/09/14 10:11, Gordon Sim wrote:
As I understand it, pools don't help scaling a given queue since all the
messages for that queue must be in the same pool. At present traffic
through different Zaqar queues are essentially entirely orthogonal
streams
On Tue, Sep 23, 2014 at 09:53:36AM +1000, Michael Still wrote:
> Hi.
>
> I know we've been talking about deprecating nova.virt.disk.vfs.localfs
> for a long time, in favour of wanting people to use libguestfs
> instead. However, I can't immediately find any written documentation
> for when we said
Adam Young wrote:
> OpenStack owes you more than most people realize.
+1
Dolph did a great job of keeping the fundamental piece that is Keystone
safe from a release management perspective, by consistently hitting all
the deadlines, giving time for other projects to safely build on it.
> Don't yo
On 09/18/2014 10:04 PM, Doug Hellmann wrote:
> All of the final releases for the Oslo libraries for the Juno cycle are
> available on PyPI. I’m working on a couple of patches to the global
> requirements list to update the baseline in the applications. In all cases,
> the final release is a seco
Hi,
I think that this variable is useful for me
cfg.IntOpt("reboot_timeout",
default=0,
help="Automatically hard reboot an instance if it has been "
"stuck in a rebooting state longer than N seconds. "
"Set to 0 to disable."),
cfg.Int
101 - 164 of 164 matches
Mail list logo
