> -Original Message-
> From: Christian Schwede [mailto:christian.schw...@enovance.com]
> Sent: 17 November 2014 14:36
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [swift] LTFS integration with OpenStack Swift for
> scenario like - Data Archival as a Service .
>
>
Perhaps we should re-introduce the auto-expiration of patches, albeit on
a very leisurely timeframe. Before, it was like 1 week to expire a
patch, which was a bit aggressive. Perhaps we could auto-expire patches
that haven't been touched in 4 or 6 weeks, to expire patches that have
truly been aband
On Mon, Nov 17, 2014 at 12:40:12PM -0500, Davanum Srinivas wrote:
> Matt,
>
> Thanks for the help/reviews!. Looks like the sequence seems to be
>
> DevStack / Icehouse - https://review.openstack.org/#/c/134972/
> DevStack / Juno - https://review.openstack.org/#/c/134975/
> Tempest - https://revie
> -Original Message-
> From: Tim Bell [mailto:tim.b...@cern.ch]
> Sent: 17 November 2014 19:44
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [swift] LTFS integration with OpenStack Swift for
> scenario like - Data Archival as a Service .
>
Thanks Matt, will pester Nova-core when the time is right :)
-- dims
On Mon, Nov 17, 2014 at 1:57 PM, Matthew Treinish wrote:
> On Mon, Nov 17, 2014 at 12:40:12PM -0500, Davanum Srinivas wrote:
>> Matt,
>>
>> Thanks for the help/reviews!. Looks like the sequence seems to be
>>
>> DevStack / Iceh
As someone who has spent quite a bit of time triaging bugs, I'd be hugely
in favor of this. I'd probably be willing to pitch in on additional
projects, as well.
Is there already tooling for this built around Launchpad, or do we have to
roll our own?
With storyboard.openstack.org looming on the ho
On Nov 17, 2014, at 12:54 PM, Mehdi Abaakouk wrote:
>
> Signed PGP part
>
> Hi,
>
> Many peoples want to have heartbeat support into the rabbit driver of
> oslo.messaging (https://launchpad.net/bugs/856764)
>
> We have different approaches to add this feature:
>
> - Putting all the heartbea
On Nov 17, 2014, at 10:01 AM, Denis Makogon wrote:
> On Mon, Nov 17, 2014 at 4:26 PM, James Page wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> Hi Denis
>>
>> On 17/11/14 07:43, Denis Makogon wrote:
>>> During Paris Design summit oslo.messaging session was raised good
>
Hi,
I’ve been working with the Poppy project[1] while they are designing their
APIs. Poppy has a concept of a flavor. A single flavor resource has the URI,
{base}/flavors/{flavor_id}.
Poppy APIs refer to a flavor in their request and/or response representations.
Some representations do this b
On Nov 17, 2014, at 12:48 PM, Mehdi Abaakouk wrote:
>
> Signed PGP part
> Le 2014-11-17 15:26, James Page a écrit :
> > This was discussed in the oslo.messaging summit session, and
> > re-enabling zeromq support in devstack is definately on my todo list,
> > but I don't think the should block l
Hi all,
We have experienced a severe hardware failure and the storage for the logs of
the CI runs was also being affected. We have recovered all that could be saved
on the new dedicated server.
If you find any patchset that has the logs missing, please issue a “check
hyper-v” command to gener
On Mon, 2014-11-17 at 19:47 +, Shaunak Kashyap wrote:
> Poppy APIs refer to a flavor in their request and/or response
> representations. Some representations do this by using the flavor ID
> (e.g. 12345) while others use the flavor resource URI (e.g.
> {base}/flavors/12345).
>
> In this contex
Hi all,
The OpenStack Telco Working Group (formerly NFV subteam) will be meeting for
the first time post-summit this Wednesday @ 1400 UTC [1] in
#openstack-meeting-alt on Freenode [2]. I have started to draft the agenda here:
https://etherpad.openstack.org/p/nfv-meeting-agenda
Please add a
On 11/17/2014 02:47 PM, Shaunak Kashyap wrote:
Hi,
I’ve been working with the Poppy project[1] while they are designing their
APIs. Poppy has a concept of a flavor. A single flavor resource has the URI,
{base}/flavors/{flavor_id}.
Please, can we as a community kill the term "flavor" in a fir
This is done.
Thanks,
-Nikhil
From: Nikhil Komawar
Sent: Monday, November 17, 2014 1:23 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [stable] [glance] glance_store scheduled release 0.1.10
Hi all,
Following last week's (mentioned) corrections
Awesome!
On Mon, Nov 10, 2014 at 9:10 AM, Susanne Balle
wrote:
> Works for me. Susanne
>
> On Mon, Nov 10, 2014 at 10:57 AM, Brandon Logan <
> brandon.lo...@rackspace.com> wrote:
>
>> https://wiki.openstack.org/wiki/Meetings#LBaaS_meeting
>>
>> That is updated for lbaas and advanced services wit
It should already be running.
Tooz has been testing with it[1]. Whats running in ubuntu is an older
redis though so don't expect some of the new > 2.2.0 features to work
until the ubuntu version is pushed out to all projects.
https://github.com/stackforge/tooz/blob/master/tooz/drivers/redis.p
Doug Hellmann wrote:
On Nov 17, 2014, at 10:01 AM, Denis Makogon wrote:
On Mon, Nov 17, 2014 at 4:26 PM, James Page wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Denis
On 17/11/14 07:43, Denis Makogon wrote:
During Paris Design summit oslo.messaging session was raised good
qu
On Wed Nov 12 2014 at 2:41:27 PM Chuck Carlino
wrote:
> Hi,
>
> I'm working on the neutron side of a couple of ironic issues, and I need
> some help. Here are the issues.
>
>1. If a nic on an ironic server fails and is replaced by a nic with a
>different mac address, neutron's dhcp serv
On Nov 17, 2014, at 2:18 PM, Jay Pipes wrote:
>
> Please, can we as a community kill the term "flavor" in a fire?
+1
One of the first (but certainly not the last) battle I lost in the early days
of Nova.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
Lucas, Thanks for bringing this up (both in Paris and here). I'm strongly
in favor of these changes as well. We discussed this during the meeting
today [1], to which I offer the following summary:
- move the status reporting to the etherpad [2]
-- take one (1) minute at the start of the meeting fo
Hi guys,
A recent question came up about how do we test better with redis for
tooz. I think this question is also relevant for ceilometer (and other
users of redis) and in general applies to the whole of openstack as the
larger system is what people run (I hope not everyone just runs devstack
On 12 November 2014 11:11, Steve Gordon wrote:
NUMA
>
>
> We still need to identify some hardware to run third party CI for the
> NUMA-related work, and no doubt other things that will come up. It's
> expected that this will be an interim solution until OPNFV resources can be
> used (note cd
This whole thread is made of awesome. Adding a drum kit that's built out of
servers is just piling on more awesome.
Cheers for the great mascot drawings, Lucas!
Deva
On Mon Nov 17 2014 at 8:20:09 AM Jim Rollenhagen
wrote:
> On Sun, Nov 16, 2014 at 01:14:13PM +, Lucas Alvares Gomes wrote:
>
I can see where this makes a lot of sense in API¹s such as Nova¹s where
flavors represent some combination of memory, disk, and cpu performance.
In the case of CDN, the flavor represents a list of CDN providers.
So... you could have a flavor representing a region of the world
(America¹s) consisti
On Nov 17, 2014, at 3:36 PM, Joshua Harlow wrote:
> Doug Hellmann wrote:
>> On Nov 17, 2014, at 10:01 AM, Denis Makogon wrote:
>>
>>> On Mon, Nov 17, 2014 at 4:26 PM, James Page wrote:
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Denis
On 17/11/14 07
On 11/17/2014 12:43 PM, Devananda van der Veen wrote:
Thanks for the reply!
On Wed Nov 12 2014 at 2:41:27 PM Chuck Carlino
mailto:chuckjcarl...@gmail.com>> wrote:
Hi,
I'm working on the neutron side of a couple of ironic issues, and
I need some help. Here are the issues.
1
I am also still seeing issues with 'ERROR: openstack The plugin
token_endpoint could not be found', we can work around it by adding in a
list of all the clients to DEVSTACK_PROJECT_FROM_GIT and things go back to
working, for example:
http://ec2-54-69-107-106.us-west-2.compute.amazonaws.com/puresto
On 11/17/2014 04:46 PM, Amit Gandhi wrote:
I can see where this makes a lot of sense in API¹s such as Nova¹s where
flavors represent some combination of memory, disk, and cpu performance.
In the case of CDN, the flavor represents a list of CDN providers.
In that case, your API is leaking imple
On Mon, Nov 17, 2014 at 3:33 PM, Joshua Harlow wrote:
> It should already be running.
>
> Tooz has been testing with it[1]. Whats running in ubuntu is an older
> redis though so don't expect some of the new > 2.2.0 features to work until
> the ubuntu version is pushed out to all projects.
The r
On Mon, Nov 17, 2014 at 1:06 PM, Joshua Harlow wrote:
> Hi guys,
>
> A recent question came up about how do we test better with redis for tooz.
> I think this question is also relevant for ceilometer (and other users of
> redis) and in general applies to the whole of openstack as the larger
> sys
Ok, it depends on what features are needed in said driver.
Things like http://redis.io/commands/psetex (and others) that might be
used only exist in newer versions > 2.2.0, if these aren't used then it
doesn't matter (basic support/functionality exists in 2.2.0 for all the
common things).
Er
On Nov 17, 2014, at 3:46 PM, Amit Gandhi wrote:
>
> I can see where this makes a lot of sense in API¹s such as Nova¹s where
> flavors represent some combination of memory, disk, and cpu performance.
For Nova, flavors emerged more as a billing convenience than anything technical
regarding creati
Hi all,
I am resuming this thread following the session we had at the summit in
Paris (etherpad here [1])
While there was some sort of consensus regarding what this library should
do, and how it should do it, the session ended with some open questions
which we need to address before finalising th
As we're dealing with the fact that testtools 1.4.0 apparently broke
something with attribute additions to tests (needed by tempest for
filtering), it raises an interesting problem.
Our current policy on requirements is to leave them open ended, this
lets us take upstream fixes. It also breaks us
Agreed it helps with billing. It also allows the customer to make a
choice based on the features offered in a flavor. At the end of the day,
the API works the same way regardless of the flavor selected. The flavor
selection merely gives the customer the experience they are looking for.
I see fl
On Nov 17, 2014, at 5:49 PM, Salvatore Orlando wrote:
> Hi all,
>
> I am resuming this thread following the session we had at the summit in Paris
> (etherpad here [1])
>
> While there was some sort of consensus regarding what this library should do,
> and how it should do it, the session end
On Nov 6, 2014, at 7:56 PM, Ian Wienand wrote:
> On 10/29/2014 12:42 AM, Doug Hellmann wrote:
>> Another way to do this, which has been used in some other projects,
>> is to define one option for a list of “names” of things, and use
>> those names to make groups with each field
>
> I've propose
On 17 November 2014 21:54, Radomir Dopieralski
wrote:
>
> On 17/11/14 09:53, Martin Geisler wrote:
>
> [...]
>
> > As Richard said, npm and bower are not competitors. You use npm to
> > install bower, and you use bower to download Angular, jQuery, Bootstrap
> > and other static files. These are th
On 11/17/2014 06:57 PM, Vishvananda Ishaya wrote:
>
> On Nov 6, 2014, at 7:56 PM, Ian Wienand wrote:
>
>> On 10/29/2014 12:42 AM, Doug Hellmann wrote:
>>> Another way to do this, which has been used in some other projects,
>>> is to define one option for a list of “names” of things, and use
>>>
On Tue, Nov 18, 2014 at 2:31 AM, Pasquale Porreca <
pasquale.porr...@dektech.com.au> wrote:
> Thank you very much Christopher
>
> On 11/17/14 12:15, Christopher Yeoh wrote:
>
>> Yes, sorry documentation has been on our todo list for too long. Could I
>> get you to submit a bug report about the lac
Most production systems I know don't run with open ended dependencies.
One of our contributing issues IMO is that we have the requirements
duplicated everywhere - and then ignore them for many of our test runs
(we deliberately override the in-tree ones with global requirements).
Particularly, since
On Tue, Nov 18, 2014 at 9:32 AM, Sean Dague wrote:
> waiting extra long for valid test results. People don't realize their
> code can't pass and just keep pushing patches up consuming resources
> which means that parts of the project that could pass tests, is backed
> up behind 100% guarunteed fa
On Mon, 2014-11-17 at 18:48 -0500, Doug Hellmann wrote:
> I’ve spent a bit of time thinking about the resource ownership issue.
> The challenge there is we don’t currently have any libraries that
> define tables in the schema of an application. I think that’s a good
> pattern to maintain, since it
+1. I always hesitate to abandon someone's patch because it is so
personal. The auto-expire is impersonal and procedural. I agree that
1 week is too soon. Give it at least a month.
Abandoned patches that have some importance shouldn't ever really be
lost. They should be linked to bug reports
Robert Collins wrote:
Most production systems I know don't run with open ended dependencies.
One of our contributing issues IMO is that we have the requirements
duplicated everywhere - and then ignore them for many of our test runs
(we deliberately override the in-tree ones with global requiremen
Jay-
Good, detailed summary, it pretty much matches with what I heard.
The one thing I want to do is I've setup a wiki page to track our progress (I
find email/etherpads deficient for this task). I've tried to include
everything from the email threads and the summit etherpads at:
http
On Tue, Nov 18, 2014 at 10:46:38AM +1030, Christopher Yeoh wrote:
> Maybe a MOTD at the top of http://review.openstack.org could help here? Have
> a button that the QA/infra people can hit when everything is broken that puts
> up a message there asking people to stop rechecking/submitting patches.
Hi all,
As discussed in Paris and at today's IRC meeting [1] we are going to be
alternating the time of the weekly IRC meetings to accommodate our
contributors in EMEA better. No time will be perfect for everyone, but as
it stands, we rarely (if ever) see our Indian, Chinese, and Japanese
contribu
On 2014-11-17 16:41:02 -0800 (-0800), Joshua Harlow wrote:
> Robert Collins wrote:
> [...]
> >That said, making requirements be capped and auto adjust upwards would
> >be extremely useful IMO, but its a chunk of work;
> > - we need the transitive dependencies listed, not just direct dependencies
>
Sean Dague, thanks for bringing up the subject.
This is highly relevant to my interests. =)
On 2014-11-17 7:10 PM, Robert Collins wrote:
Most production systems I know don't run with open ended dependencies.
One of our contributing issues IMO is that we have the requirements
duplicated everywhe
Good point, we really need a better dependency resolver/installer...
Jeremy Stanley wrote:
On 2014-11-17 16:41:02 -0800 (-0800), Joshua Harlow wrote:
Robert Collins wrote:
[...]
That said, making requirements be capped and auto adjust upwards would
be extremely useful IMO, but its a chunk of w
Hi. This is a reminder mail for the weekly servicevm IRC meeting.
>From Nov 19 2014, the timeslot/channel has been changed.
Please be prepared.
Nov 19, 2014 Wednesday 17:00 UTC-
#openstack-meeting-4 on freenode
https://wiki.openstack.org/wiki/Meetings/ServiceVM
--
Isaku Yamahata
___
Drew,
I would say that it would be good to open a Blueprint for this and push
the code up for review. Even if you don't have CI ready yet you can
post results of a driver cert test [1] and we can start reviewing the
code while you work on finishing up the process of getting your CI running.
On 11/17/2014 9:21 AM, Andrew Laski wrote:
Since there have been no stated conflicts or issues with these times yet
we will go with Wednesdays alternating between 1700 and 2200 UTC in
#openstack-meeting-3 which seems to be open at that time.
This week the meeting will be at 1700. I'll see you
On 11/17/2014 9:36 AM, Victor Sergeyev wrote:
Hello All!
Oslo team is pleased to announce the new release of Oslo database
handling library - oslo.db 1.1.0
List of changes:
$ git log --oneline --no-merges 1.0.2..master
1b0c2b1 Imported Translations from Transifex
9aa02f4 Updated from global
One of the highly reported issues was that when test discovery failed,
testr showed no useful details about the issue.
The root cause of this was an interaction between test *listing*,
which the standard library doesn't formally support (its on my list to
add it there) and discovery, which only kn
Meeting on #openstack-meeting at 1500 UTC (8:00AM MST)
1) Status on cleanup work - https://wiki.openstack.org/wiki/Gantt/kilo
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
Ope
On 11/17/2014 6:57 PM, Louis Taylor wrote:
On Tue, Nov 18, 2014 at 10:46:38AM +1030, Christopher Yeoh wrote:
Maybe a MOTD at the top of http://review.openstack.org could help here? Have
a button that the QA/infra people can hit when everything is broken that puts
up a message there asking peo
From: Devananda van der Veen [mailto:devananda@gmail.com]
Sent: Monday, November 17, 2014 5:00 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Ironic] Proposing new meeting times
Hi all,
As discussed in Paris and at today's IRC meeting [1] we are going to be
alternating
Is the new driver drop-in compatible with the old one? IF not, can existing
systems be upgraded to the new driver via some manual steps, or is it
basically a completely new driver with similar functionality?
On 17 November 2014 07:08, Drew Fisher wrote:
> We (here at Oracle) have a replacement fo
Hi devananda,
I would be comfortable with both the timings, though I like the second
option better. I am from India, so current timing is a little
inconvenient for us!
On 11/18/2014 06:30 AM, Devananda van der Veen wrote:
> Hi all,
>
> As discussed in Paris and at today's IRC meeting [1] we are
On 18 November 2014 10:59, Richard Jones wrote:
> On 17 November 2014 21:54, Radomir Dopieralski
> wrote:
> > - Bower in the development environment,
> > - Bower configuration file in two copies, one for global-requirements,
> > and one for the Horizon's local requirements. Plus a gate job that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Le 2014-11-17 22:53, Doug Hellmann a écrit :
That’s a good goal, but that’s not what I had in mind for in-tree
functional tests.
An interesting idea that might be useful that taskflow implemented/has
done...
The examples @
https://githu
вторник, 18 ноября 2014 г. пользователь Mehdi Abaakouk написал:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>
>
> Le 2014-11-17 22:53, Doug Hellmann a écrit :
>
> That’s a good goal, but that’s not what I had in mind for in-tree
functional tests.
>>> An interesting idea
Ok.
Here’s what I think.
Mostly I like the solution you’re proposing. Some comments/questions:
We discussed this with Dmitry about a couple of months ago and we concluded
that we don’t necessarily need a separate endpoint, CRUD operations etc. (even
though my initial BP had exactly this idea).
101 - 166 of 166 matches
Mail list logo
