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
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
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 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
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
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
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
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
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
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)
>>
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
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 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
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 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
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 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
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,
> > >
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
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,
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
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
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 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 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
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
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
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
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
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 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
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 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
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 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
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 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 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 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
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
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
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
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
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
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
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
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
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 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
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 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
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
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 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
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
++ 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 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
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 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 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
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 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
Doug Hellmann wrote:
> 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,
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 Sep 23, 2014, at 8:40 AM, Doug Hellmann wrote:
> If we are no longer incubating *programs*, which are the teams of people who
> we would like to ensure are involved in OpenStack governance, then how do we
> make that decision? From a practical standpoint, how do we make a list of
> eligibl
Devananda van der Veen wrote:
> On Tue, Sep 23, 2014 at 8:40 AM, Doug Hellmann wrote:
>> One is a technical discussion that has nothing at all to do with governance.
>> The other is entirely about governance.
>>
>> If we are no longer incubating *programs*, which are the teams of people who
>> w
Keystone team has released 0.11.1 of python-keystoneclient. Due to some delays
getting things through the gate this took a few extra days.
https://pypi.python.org/pypi/python-keystoneclient/0.11.1
—Morgan
—
Morgan Fainberg
-Original Message-
From: John Dickinson
Reply: OpenStack De
On Fri, 2014-09-19 at 09:13 -0400, Sean Dague wrote:
> I've spent the better part of the last 2 weeks in the Nova bug tracker
> to try to turn it into something that doesn't cause people to run away
> screaming. I don't remember exactly where we started at open bug count 2
> weeks ago (it was north
The Keystone team has released python-keystoneclient 0.11.1 [1]. This version
is meant to be the release coinciding with the Juno release of OpenStack.
The release includes two fixes [2] on top of the 0.11.0 [3] version.
Cheers,
Morgan Fainberg
[1] https://pypi.python.org/pypi/python-keystonec
On Tue, 2014-09-23 at 12:09 -0400, Jay Pipes wrote:
> I'd like to say finally that I think there should be an OpenStack API
> working group whose job it is to both pull together a set of OpenStack
> API practices as well as evaluate new REST APIs proposed in the
> OpenStack ecosystem to provide
On Sep 19, 2014, at 9:13 AM, Sean Dague wrote:
> Cross interaction with Neutron and Cinder remains racey. We are pretty
> optimistic on when resources will be available. Even the event interface
> with Neutron hasn't fully addressed this. I think a really great Design
> Summit session would be N
On 09/23/2014 01:15 PM, Kevin L. Mitchell wrote:
On Tue, 2014-09-23 at 12:09 -0400, Jay Pipes wrote:
I'd like to say finally that I think there should be an OpenStack API
working group whose job it is to both pull together a set of OpenStack
API practices as well as evaluate new REST APIs propo
On Tue, Sep 23, 2014 at 01:32:50PM -0400, Andrew Laski wrote:
> I've been thinking along very similar lines, but I don't think each current
> API needs to be replaced. I would very much like to see a unified API
> project that could be responsible for managing requests to "boot an instance
> with
On 08:57 Tue 23 Sep , 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 f
I am running for PTL for Oslo for the Kilo release cycle.
I have served 2 terms now, and my tl;dr platform for Kilo is, “More of the
same!”
I have already posted the retrospective the team put together for Juno [1], so
I won’t go over those items in depth here. From my perspective, the team is
-Original Message-
From: John Griffith
Reply: OpenStack Development Mailing List (not for usage questions)
>
Date: September 23, 2014 at 08:02:23
To: OpenStack Development Mailing List (openstack-dev@lists.openstack.org)
>
Subject: [openstack-dev] [cinder] Not seeking another term as
On Tue, 2014-09-23 at 18:39 +0100, Louis Taylor wrote:
> On Tue, Sep 23, 2014 at 01:32:50PM -0400, Andrew Laski wrote:
> > I've been thinking along very similar lines, but I don't think each current
> > API needs to be replaced. I would very much like to see a unified API
> > project that could be
On 09/23/2014 02:10 PM, Kevin L. Mitchell wrote:
> On Tue, 2014-09-23 at 18:39 +0100, Louis Taylor wrote:
>> On Tue, Sep 23, 2014 at 01:32:50PM -0400, Andrew Laski wrote:
>>> I've been thinking along very similar lines, but I don't think each current
>>> API needs to be replaced. I would very much
confirmed
On 23/09/14 01:54 PM, Doug Hellmann wrote:
> I am running for PTL for Oslo for the Kilo release cycle.
>
> I have served 2 terms now, and my tl;dr platform for Kilo is, “More of the
> same!”
>
> I have already posted the retrospective the team put together for Juno [1],
> so I won’t
On 23/09/14 09:44, Anant Patil wrote:
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 concur
On 09/23/2014 12:19 PM, Sean Dague wrote:
On 09/23/2014 02:10 PM, Kevin L. Mitchell wrote:
On Tue, 2014-09-23 at 18:39 +0100, Louis Taylor wrote:
On Tue, Sep 23, 2014 at 01:32:50PM -0400, Andrew Laski wrote:
I've been thinking along very similar lines, but I don't think each current
API needs
Hi, I suppose this question is directed at the VMware-API team, Gary,
Tracy, Arnaud and Vui in particular?
I work at IBM in the Software group working with Dims (Davanum Srinivas)
and Radu Mateescu and am particularly interested in ova support with
VMware. I've looked at the blueprint (
https:
On Tue, Sep 23, 2014 at 9:50 AM, Vishvananda Ishaya
wrote:
>
> On Sep 23, 2014, at 8:40 AM, Doug Hellmann wrote:
>
> > If we are no longer incubating *programs*, which are the teams of people
> who we would like to ensure are involved in OpenStack governance, then how
> do we make that decision?
On 09/23/2014 02:18 AM, Thierry Carrez wrote:
> The main goal of incubation, as we did it in the past cycles, is a
> learning period where the new project aligns enough with the existing
> ones so that it integrates with them (Horizon shows Sahara dashboard)
> and won't break them around release ti
I believe heat has its own dependency graph implementation but if that was
switched to networkx[1] that library has a bunch of nice read/write
capabilities.
See: https://github.com/networkx/networkx/tree/master/networkx/readwrite
And one made for sqlalchemy @ https://pypi.python.org/pypi/graph-
Hi Devs,
I have the new license, but it has some new restrictions on it's use. I am
still waiting on some clarification, but I do know some situations in which I
can distribute the license.
I cannot distribute the license to any commercial developers. This means if as
part of your job, you are
John,
Thanks for the term as PTL since Cinder got it's start. Without your
encouragement when Kurt and I started working on Cinder back during
Grizzly. We wouldn't have been successful, and might not even be
working on the project to this day. I can't say enough about how
helpful you hav
On Tue, Sep 23, 2014 at 12:15 PM, Kevin L. Mitchell <
kevin.mitch...@rackspace.com> wrote:
> One of the things that's been bothering me about OpenStack for a while
> now is the fact that we have all these different APIs on different
> endpoints. What I've been wondering about is if we should crea
Flavio wrote> "The reasoning, as explained in an other
email, is that from a use-case perspective, strict ordering won't hurt
you if you don't need it whereas having to implement it in the client
side because the service doesn't provide it can be a PITA."
The reasoning is flawed though. If perform
On Tue, Sep 23, 2014 at 1:19 PM, Sean Dague wrote:
> So today we have a proxy API in Nova which does some of this. I guess
> the question is is it better to do this in Nova in the future or divorce
> it from there.
>
A stand-alone, production-quality configurable proxy would be useful to
take ov
On Sep 19, 2014, at 1:16 PM, Doug Hellmann wrote:
> The Oslo team is starting to remove deprecated code from the incubator for
> libraries that graduated this cycle, in preparation for the work we will be
> doing in Kilo.
>
> Any fixes for those modules needed before the final releases for th
On Sep 23, 2014, at 1:24 PM, Mark McClain wrote:
>
> On Sep 19, 2014, at 9:13 AM, Sean Dague wrote:
>
>> Cross interaction with Neutron and Cinder remains racey. We are pretty
>> optimistic on when resources will be available. Even the event interface
>> with Neutron hasn't fully addressed th
On Tue, Sep 23, 2014 at 1:40 PM, Chris Friesen
>
> Why not do something like what is done for the userspace/kernel syscall
> API? Userspace code tries to use the most recent one it knows about, if
> that comes back as "not a valid syscall" then it tries the next older
> version. As long as trying
The ceilometer team released python-ceilometerclient vesion 1.0.11 yesterday:
https://pypi.python.org/pypi/python-ceilometerclient/1.0.11
Cheers,
Eoghan
> Keystone team has released 0.11.1 of python-keystoneclient. Due to some
> delays getting things through the gate this took a few extra day
On Mon, Sep 22, 2014 at 7:51 AM, Jay S. Bryant
wrote:
>
> On 09/21/2014 07:37 PM, Matt Riedemann wrote:
>>
>> When I'm essentially +2 on a change but for a small issue like typos in
>> the commit message, the need for a note in the code or a test (or change to
>> a test), I've been doing those mys
On 09/23/2014 09:29 PM, Fox, Kevin M wrote:
> Flavio wrote> "The reasoning, as explained in an other
> email, is that from a use-case perspective, strict ordering won't hurt
> you if you don't need it whereas having to implement it in the client
> side because the service doesn't provide it can be
+1 You will be missed Mark. Thank you for your leadership and mentorship.
Iccha
On 9/23/14, 5:59 AM, "stuart.mcla...@hp.com" wrote:
>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: O
Hi sahara folks,
I've prepared all new images for Sahara (using diskimage-builder) for
Juno release.
Vanilla plugin:
http://sahara-files.mirantis.com/sahara-juno-vanilla-1.2.1-centos-6.5.qcow2
http://sahara-files.mirantis.com/sahara-juno-vanilla-1.2.1-ubuntu-14.04.qcow2
http://sahara-files.mirant
On Mon, Sep 22, 2014 at 11:45 AM, Elizabeth K. Joseph
wrote:
> Hi everyone,
>
> The OpenStack Infrastructure (Infra) team is hosting our weekly
> meeting on Tuesday September 23rd, at 19:00 UTC in #openstack-meeting
Meeting minutes and log:
Minutes:
http://eavesdrop.openstack.org/meetings/infra
1 - 100 of 164 matches
Mail list logo
