On 14 Nov 2017, at 16:08, Davanum Srinivas wrote:
> On Wed, Nov 15, 2017 at 10:44 AM, John Dickinson wrote:
>>
>>
>> On 14 Nov 2017, at 15:18, Mathieu Gagné wrote:
>>
>>> On Tue, Nov 14, 2017 at 6:00 PM, Fox, Kevin M wrote:
>>>> The pressure
On 15 Nov 2017, at 7:40, Jay Pipes wrote:
> On 11/15/2017 06:28 AM, Duncan Thomas wrote:
>> On 15 November 2017 at 11:15, Matt Keenan wrote:
>>> On 13/11/17 22:51, Nikhil Komawar wrote:
>>>
>>> I think it will a rather hard problem to solve. As swift store can be
>>> configured to store objects
On 22 Nov 2017, at 22:08, Adrian Turjak wrote:
> Hello fellow openstackers,
>
> I'm trying to figure something out that confuses me around how Swift
> handles roles from Keystone, and what the ACLs allow.
>
> In the Swift config you can specify roles which can manage the
> containers for their p
Swift has now used 4 feature branches and landed 3 of them:
* feature/sp -- for storage policy functionality (landed)
* feature/ec -- for erasure codes (landed)
* feature/hummingbird -- for golang WIP
* feature/crypto -- for at-rest encryption (landed)
Overall, using long-lived upstream featu
I've been trying to follow this thread, but I'll admit I'm confused about what
is being asked about or proposed. I'm not sure what "plugins for all" means.
Is "plugins for all" a way to make every plugin in an OpenStack project work
the same way? How would that work? There's a huge set of divers
On 19 Jul 2016, at 11:56, Dean Troyer wrote:
> On Tue, Jul 19, 2016 at 12:27 PM, John Dickinson wrote:
>
>> Overall, using long-lived upstream feature branches has been very helpful
>> for us and overall a positive experience.
>>
>> I've seen some other teams
On 8 Aug 2016, at 9:50, Jay Pipes wrote:
> Tempest devs,
>
> Let me please draw your attention to a LP bug that may not seem particularly
> high priority, but I believe could be resolved easily with a patch already
> proposed.
>
> LP bug 1536251 [1] accurately states that Tempest is actively v
I'd like to advocate for *not* raising minimum versions very often. Every time
some OpenStack project raises minimum versions, this change is propagated to
all projects, and that puts extra burden on anyone who is maintaining packages
and dependencies in their own deployment. If one project need
On 9 Aug 2016, at 11:33, Ian Cordasco wrote:
>
>
> -Original Message-
> From: John Dickinson
> Reply: OpenStack Development Mailing List (not for usage questions)
>
> Date: August 9, 2016 at 13:17:08
> To: OpenStack Development Mailing List
> S
On 11 Aug 2016, at 10:03, Andreas Jaeger wrote:
> TL;DR: upper-constraints can be used now for all tox based jobs
>
> With any software package, you will need additional packages to run it.
> Often, there's a tight coupling: The software package will only run with
> specific other package versio
On 3 Aug 2016, at 16:47, Jay Pipes wrote:
> Hi Novas and anyone interested in how to represent capabilities in a
> consistent fashion.
>
> I spent an hour creating a new os-capabilities Python library this evening:
>
> http://github.com/jaypipes/os-capabilities
>
> Please see the README for exa
On 10 Aug 2016, at 8:29, Doug Hellmann wrote:
> Excerpts from Doug Hellmann's message of 2016-07-29 16:55:22 -0400:
>> One of the outcomes of the discussion at the leadership training
>> session earlier this year was the idea that the TC should set some
>> community-wide goals for accomplishing
On 11 Aug 2016, at 15:02, Brian Rosmaita wrote:
> I have a question about the api-ref. Right now, for example, the new
> images v1/v2 api-refs are accurate for Mitaka. But DocImpact bugs are
> being generated as we speak for changes in master that won't be
> available to consumers until Newton
On 11 Aug 2016, at 15:14, Ed Leafe wrote:
> On Aug 11, 2016, at 4:50 PM, John Dickinson wrote:
>
>> Is this intended to be a cross-project thing? The message is tagged
>> "[nova]", so I'm kinda surprised I saw it, but the library seems to be
>> calle
bindep is great, and we've been using it in Swift for a while now. I'd
definitely recommend it to other projects.
Andreas, I didn't see a patch proposed to Swift to move the file. I don't want
to get in the way of your tool, though. Is there a patch that will be proposed,
or should I do that my
On 12 Aug 2016, at 7:28, Doug Hellmann wrote:
> Excerpts from John Dickinson's message of 2016-08-11 15:00:56 -0700:
>>
>> On 10 Aug 2016, at 8:29, Doug Hellmann wrote:
>>
>>> Excerpts from Doug Hellmann's message of 2016-07-29 16:55:22 -0400:
One of the outcomes of the discussion at the le
On 12 Aug 2016, at 13:31, Doug Hellmann wrote:
> Excerpts from John Dickinson's message of 2016-08-12 13:02:59 -0700:
>>
>> On 12 Aug 2016, at 7:28, Doug Hellmann wrote:
>>
>>> Excerpts from John Dickinson's message of 2016-08-11 15:00:56 -0700:
On 10 Aug 2016, at 8:29, Doug Hellmann w
On 15 Aug 2016, at 1:37, Thierry Carrez wrote:
> Doug Hellmann wrote:
>> [...]
>> Choosing to be a part of a community comes with obligations as well
>> as benefits. If, after a lengthy discussion of a community-wide
>> goal, involving everyone in the community, a project team is
>> resolutely
I don't know of people running Swift in production with mod_wsgi. The original
doc you referenced and the related work done upstream was done several years
ago, IIRC by IBM. Personally, I've never deployed Swift that way.
However, I too am really interested in the general answers to your questio
On 17 Aug 2016, at 15:27, Nick Papadonis wrote:
> comments
>
> On Wed, Aug 17, 2016 at 4:53 PM, Matthew Thode
> wrote:
>
>> On 08/17/2016 03:52 PM, Nick Papadonis wrote:
>>
>>> Thanks for the quick response!
>>>
>>> Glance worked for me in Mitaka. I had to specify 'chunked transfers'
>>> and i
no
On 2 Apr 2018, at 11:46, Jialin Liu wrote:
> Hi,
> Can a container name in openstack swift contains / ?
> e.g.,
> abc/111/mycontainer
>
>
> Best,
> Jialin
> __
> OpenStack Development Mailing List (not for usage questions)
I've discovered that eventlet 0.23.0 (released April 6) does break
things for Swift. I'm not sure about other projects yet.
https://bugs.launchpad.net/swift/+bug/1769749
--John
On 7 May 2018, at 13:50, Doug Hellmann wrote:
Excerpts from Michel Peterson's message of 2018-05-07 17:54:02 +03
On 14 May 2018, at 13:43, Pete Zaitcev wrote:
On Thu, 10 May 2018 20:07:03 +0800
Yuxin Wang wrote:
I'm working on a swift project. Our customer cares about S3
compatibility very much. I tested our swift cluster with
ceph/s3-tests and analyzed the failed cases. It turns out that lots
of th
On 20 May 2018, at 17:19, Thomas Goirand wrote:
On 05/20/2018 06:24 PM, Matthew Treinish wrote:
On Sun, May 20, 2018 at 03:05:34PM +0200, Thomas Goirand wrote:
Thanks for these details. What exactly is the trouble with the Swift
backend? Do you know? Is anyone working on fixing it? At my com
During today's Swift team meeting[1], we discussed the idea of
relaxing review guidelines. We agreed the normal case is "one core
reviewer's approval is sufficient to land code".
We've long had a "one +2" policy for trivial and obviously correct
patches. Put simply, the old policy was one of "nor
On 2 Jan 2017, at 13:06, Davanum Srinivas wrote:
> Folks,
>
> Short Story :
> [1] has merged in devstack, it adds support for a python 3.5 based
> up/down devstack test that just starts services and brings them down.
> see [2] for a test run.
>
> Need help from swift folks:
> Swift still needs w
On 3 Jan 2017, at 10:38, Doug Hellmann wrote:
> Excerpts from John Dickinson's message of 2017-01-03 09:02:19 -0800:
>>
>> On 2 Jan 2017, at 13:06, Davanum Srinivas wrote:
>>
>>> Folks,
>>>
>>> Short Story :
>>> [1] has merged in devstack, it adds support for a python 3.5 based
>>> up/down devst
On 10 Feb 2017, at 7:07, Denis Makogon wrote:
> Greetings.
>
> I've been developing Swift middleware that depends on specific HTTP headers
> and figured out that there's only one way to specify them on client side -
> only in programmatically i can add HTTP headers to each Swift HTTP API
> metho
On 13 Feb 2017, at 20:17, Mahati C wrote:
> Hello everyone,
>
> An update on the Outreachy program, including a request for volunteer
> mentors and funding. For those of you who are not aware, Outreachy helps
> people from underrepresented groups get involved in free and open source
> software
On 16 Feb 2017, at 15:01, Chris Dent wrote:
> On Thu, 16 Feb 2017, Dan Prince wrote:
>
>> And yes. We are all OpenStack developers in a sense. We want to align
>> things in the technical arena. But I think you'll also find that most
>> people more closely associate themselves to a team within Op
On 28 Aug 2018, at 9:59, Jeremy Stanley wrote:
[Obligatory disclaimer: I am not a lawyer, this is not legal advice,
and I am not representing the OpenStack Foundation in any legal
capacity here.]
TL;DR: You should not be putting "Copyright OpenStack Foundation" on
content in Git repositories,
On 4 Sep 2018, at 12:16, Julia Kreger wrote:
Greetings Stackers!
I hereby announce my candidacy for a position on the OpenStack
Technical
Committee.
In many respects I consider myself a maverick, except reality is
sometimes
entirely different than my own self perception, upon reflection.
That's a great question.
A quick google search shows a few like Swift Explorer, Cyberduck, and
Gladinet. But since Swift supports the S3 API (check with your cluster
operator to see if this is enabled, or examine the results of a `GET
/info` request), you can use any available S3 GUI client as
I'd be honored to continue to serve as your PTL for OpenStack Swift.
## Looking back at the Newton cycle
During the Newton cycle, the Swift community has delivered at-rest
encryption. This feature is the culmination of a more than year of
work, and it enables Swift to be deployed in places where
I am throwing my hat into the ring for the TC election.
I've been a part of OpenStack since it started. I've seen it grow from
a few dozen people into the very large community we have today. During
the past 6 years, I've seen controversial topics come and go and the
community grow and adapt. I've
On 29 Sep 2016, at 16:00, gordon chung wrote:
>
> On 29/09/16 04:35 PM, John Dickinson wrote:
>>
>> I am concerned that there is a current focus on preserving the status
>> quo. There's focus on policies and rules instead of use cases; there's
>> f
On 27 Sep 2016, at 9:21, Sean McGinnis wrote:
> I would like to announce my candidacy for a position on the Technical
> Committee.
>
> I work for Dell EMC with over a decade (quite a bit over, but I don't want to
> think about that) in storage and software development. I have been involved in
>
On 3 Oct 2016, at 12:31, Doug Hellmann wrote:
>
> I think that's the balance we want to
> have: listen to input, collect information, then clearly set the
> direction without over-prescribing the implementation.
In light of this statement, would you reevaluate previous decisions you've made
reg
The Swift team has been doing midcycles for a while now, and as the new PTG
gets closer, I want to write down our experience with what has worked for us. I
hope it is beneficial to other teams, too.
## Logistics of the event
- 2 rooms is ideal, but can make due with one larger room
- move table
On 1 Nov 2016, at 14:46, Zane Bitter wrote:
> On 01/11/16 15:13, James Slagle wrote:
>> On Tue, Nov 1, 2016 at 7:21 PM, Emilien Macchi wrote:
>>> Hi,
>>>
>>> TripleO (like some other projects in OpenStack) have not always done
>>> good job in merging specs on time during a cycle.
>>> I would li
gt;>> OSIC
>>>
>>
>> Right I don't think the intention would be to implement it from scratch, but
>> to do some basic analysis of what exists (and think about and document the
>> patterns), and try to find the common parts (which likely involves renaming
&
On 7 Nov 2016, at 10:31, Ash wrote:
> On Mon, Nov 7, 2016 at 9:58 AM, Hayes, Graham wrote:
>
>> On 07/11/2016 17:14, Flavio Percoco wrote:
>>> Greetings,
>>>
>>> I literally just posted a thing on my blog with some thoughts of what
>> I'd expect
>>> any new language being proposed for OpenStack
I've been fielding questions about the upcoming PTG, but one has come
up that I don't know how to answer.
How will cross-project sessions at the PTG be scheduled?
>From looking at the "Event Layout" section on
https://www.openstack.org/ptg, it seems to imply that each team in the
left column will
On 14 Nov 2016, at 13:57, gordon chung wrote:
> hi,
>
> one issue i've noticed with our 'backlog' scheduling is that we register
> all our new measures in a single folder/filestore object. this folder or
> object in most production cases can grow quite large (tens/hundreds of
> thousands). so we
On 18 Nov 2016, at 8:14, Dean Troyer wrote:
>> -Original Message-
>> From: Luke Hinds
> [...]
>>> for non security related functions, but when it comes to government
>>> compliance and running OpenStack on public clouds (and even private for the
>>> Telcos / NFV), not meeting FIPS will
On 22 Nov 2016, at 10:47, Andreas Jaeger wrote:
> When we (infra) changed the unit test jobs to not set up databases by
> default, we created special python-db and tox-db jobs that set up both
> MySQL and PostgreSQL databases. And that complicated the setup of those
> projects and lead to proble
201 - 246 of 246 matches
Mail list logo
