Hi folks,
we have a new python-saharaclient release with SSL and indirect access
support, as well as bunch of bug fixes.
https://launchpad.net/python-saharaclient/+milestone/0.7.7
Bump in global requirements: https://review.openstack.org/#/c/155428/
Thanks.
--
Sincerely yours,
Sergey
Hi,
Since fuel plugins are going to be moved [1] from fuel-plugins repository
[2],
the only project which will be there is fuel plugin builder and plugins
examples
which are related to fuel plugin builder testing.
Currently fuel plugin builder has its own release cycle, but we don't have
tags
+1 for the whole idea, I really waited for it until first release of
fuel-plugin-builder.
Without tags it's hard to say which commit is included in PyPI release.
Also automation of release process is a really nice thing and make it more
transparent.
2015-02-13 9:59 GMT+01:00 Evgeniy L
Hi folks,
In the spirit of stepping down considerately [1], I'd like to ask to be
removed from the core and drivers team for Horizon and associated
projects. I'm embarking on some fun adventures far far away and won't
have any time to spare for OpenStack for a while.
I removed my name from
Hi Andrey,
I agree that it's useful to know compatibility between releases and
previous versions
of plugins, but I'm not 100% sure that tag comments is the best place to
keep such
information, does it make sense to use Changelog.txt file for such
information instead?
Regarding to versioning
Hi Jay,
do you have a link to the etherpad?
Danny
Am 13.02.2015 um 05:54 schrieb Jay S. Bryant:
All,
Several members of the Cinder team and I were discussing the
current state of volume replication while trying to figure out the
best way to resolve bug 1383524 [1]. The outcome of the
On Fri Feb 13 2015 at 5:45:36 PM Eric Windisch e...@windisch.us wrote:
ᐧ
from neutron.agent.privileged.commands import ip_lib as priv_ip
def foo():
# Need to create a new veth interface pair - that usually
requires root/NET_ADMIN
priv_ip.CreateLink('veth', 'veth0',
+1.
On Fri, Feb 13, 2015 at 11:41 AM, Sebastian Kalinowski
skalinow...@mirantis.com wrote:
+1 for the whole idea, I really waited for it until first release of
fuel-plugin-builder.
Without tags it's hard to say which commit is included in PyPI release.
Also automation of release process is a
Hi all,
We have almost year old (from last update) reviews still in the queue for
glance. The discussion was initiated on yesterday's meeting for adopting
abandon policy for stale changes.
The documentation can be found from
https://etherpad.openstack.org/p/glance-cleanout-of-inactive-PS and
On 28/01/15 14:25 +0100, Thierry Carrez wrote:
Hi everyone,
When we first introduced the cross-project specs (specs for things that
may potentially affect all OpenStack projects, or where more convergence
is desirable), we defaulted to rather simple rules for approval:
- discuss the spec in a
We have an ongoing effort in neutron to move to rootwrap-daemon.
https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/rootwrap-daemon-mode,n,z
To speed up multiple system calls, and be able to spawn daemons inside
namespaces.
I have to read a bit what
On 02/12/2015 02:36 PM, Salvatore Orlando wrote:
- I promised a non blocking algorithm for IP allocation. The one I was
developing was based on specifying the primary key on the ip_requests
table in a way that it would prevent two concurrent requests from
getting the same address, and would
On 12/02/15 09:34 -0800, Chris St. Pierre wrote:
Yeah, that commit definitely disables the file-backed queue -- it certainly
*looks* like we want to be rid of it, but all of the code is left in place and
even updated to support the new format. So my confusion remains. Hopefully Zhi
Yan can
Hi,
I believe that keeping review queue clean is the great idea.
But I am not sure that set of these rules is enough to abandon patches.
Recently I wrote blogpost related to making OpenStack community more user
friendly:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/13/2015 01:42 PM, Miguel Ángel Ajo wrote:
Hi, Ihar Jiri, thank you for pointing this out.
I’m working on the following items:
1) Doing Openflow traffic filtering (stateful firewall) based on
OVS+CT[1] patch, which may
eventually
On 13/02/15 16:01 +0100, Jordan Pittier wrote:
What is the difference between just calling the Glance API to upload an image,
versus adding add() functionality to the HTTP image store?
You mean using glance image-create --location http://server1/myLinuxImage [..]
? If so, I guess adding the
Tim
Wanted to clarify a bit. As I have mentioned before: Solver scheduler is
work done before this work (Datalog-constraints) but we had kept it
very generic to be integrated with something like congress. In fact Ramki
(who was one of the members of the original thread when you reached out to
On 13/02/15 11:06 +, Kuvaja, Erno wrote:
Hi all,
We have almost year old (from last update) reviews still in the queue for
glance. The discussion was initiated on yesterday’s meeting for adopting
abandon policy for stale changes.
The documentation can be found from
On 13 February 2015 at 12:40, Rossella Sblendido rsblend...@suse.com
wrote:
On 02/12/2015 02:36 PM, Salvatore Orlando wrote:
- I promised a non blocking algorithm for IP allocation. The one I was
developing was based on specifying the primary key on the ip_requests
table in a way that it
Erlon Cruz sombra...@gmail.com wrote on 02/13/2015 07:51:34 AM:
From: Erlon Cruz sombra...@gmail.com
To: Danny Al-Gaaf danny.al-g...@bisect.de, OpenStack Development
Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: 02/13/2015 07:53 AM
Subject: Re:
Angus Lees wrote:
So inspired by the Rootwrap on root-intensive nodes thread, I went and
wrote a proof-of-concept privsep daemon for
neutron: https://review.openstack.org/#/c/155631
Nice work! Trying to check where the security model is actually weaker
than the one provided by rootwrap here...
On 02/12/2015 02:20 PM, Ryan Brown wrote:
+1 I think the way to go would be:
We suggest (pretty please) that you comply with RFCs 7230-5 and if you
have any questions ask us. Also here are some examples of usage that
is/isn't RFC compliant for clarity
+1, i like the idea of pointing readers
On 02/13/2015 09:47 AM, Jordan Pittier wrote:
Hi list,
I would like to add the 'add' capability to the HTTP glance store.
Let's say I (as an operator or cloud admin) provide an HTTP server where
(authenticated/trusted) users/clients can make the following HTTP request :
POST
In short term, we use veth pairs with namespace to fix the issue if performance
is not impacted (Hopefully:)
If performance downgrade too much, we may consider the following:
1) DHCP agent: use veth pairs with namespace since it is not critical path.
2) L3 agent: don't create port in OSV.
On Fri, Feb 13, 2015 at 6:14 AM, Thierry Carrez thie...@openstack.org
wrote:
Julie Pichon wrote:
In the spirit of stepping down considerately [1], I'd like to ask to be
removed from the core and drivers team for Horizon and associated
projects. I'm embarking on some fun adventures far far
On 02/12/2015 05:15 PM, Trevor McKay wrote:
Hi folks,
Here is another way to do this. Lu had mentioned Oozie shell actions
previously.
Sahara doesn't support them, but I played with it from the Oozie command
line
to verify that it solves our hbase problem, too.
We can potentially create a
On 02/12/2015 09:59 PM, Robert Collins wrote:
On 5 February 2015 at 13:20, Rochelle Grober rochelle.gro...@huawei.com wrote:
Duncan Thomas [mailto:duncan.tho...@gmail.com] on Wednesday, February 04,
2015 8:34 AM wrote:
The downside of numbers rather than camel-case text is that they are less
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/13/2015 01:47 PM, Miguel Ángel Ajo wrote:
Sorry, I forgot about
5) If we put all our OVS/OF bridge logic in just one bridge
(instead of N: br-tun, br-int, br-ex, br-xxx), the performance
should be yet higher, since, as far as I
On 12 February 2015 at 19:57, John Belamaric jbelama...@infoblox.com
wrote:
From: Salvatore Orlando sorla...@nicira.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: Thursday, February 12, 2015 at 8:36 AM
To: OpenStack
Hello Everyone
It is time for us to apply for slots for the annual Google Summer of Code
event https://developers.google.com/open-source/soc/?csw=1
Last year, we got a bunch of slots and had awesome projects
https://wiki.openstack.org/wiki/GSoC2014
We are hoping this year we will get even more
Hi!
Important chagesets are supposed to have bugs (or blueprints) assigned
to them, so, even if the CS is abandoned, its description still
remains on Launchpad in one form or another, so we will not loose it
from general project's backlog. And if the changeset didn't have a
bug/blueprint
On 02/13/2015 09:20 AM, Daniel P. Berrange wrote:
On Fri, Feb 13, 2015 at 08:49:26AM -0500, Jay Pipes wrote:
On 02/13/2015 07:04 AM, Daniel P. Berrange wrote:
Historically Nova has had a bunch of code which mounted images on the
host OS using qemu-nbd before passing them to libvirt to setup
What is the difference between just calling the Glance API to upload an
image, versus adding add() functionality to the HTTP image store?
You mean using glance image-create --location http://server1/myLinuxImage
[..] ? If so, I guess adding the add() functionality will save the user
from having to
Adding tags on the subject line to attract the attention of the OSSG
(OpenStack Security group) which regroups people working on improving
the state of security in OpenStack in general.
Patrick Lismore wrote:
Hi all,
I am a software developer working at HP, I do not work with OpenStack
@HP
Chris Hoge wrote:
We're proposing to host the repository at openstack/defcore, as this is work
being done by a board-backed committee with cross cutting concerns for all
OpenStack projects. All projects are owned by some parent organization within
the OpenStack community. One possiblility
Julie Pichon wrote:
In the spirit of stepping down considerately [1], I'd like to ask to be
removed from the core and drivers team for Horizon and associated
projects. I'm embarking on some fun adventures far far away and won't
have any time to spare for OpenStack for a while.
Aw. Sad to hear
Do you have the log of the discussion as well?
On Fri, Feb 13, 2015 at 7:09 AM, Danny Al-Gaaf danny.al-g...@bisect.de
wrote:
Hi Jay,
do you have a link to the etherpad?
Danny
Am 13.02.2015 um 05:54 schrieb Jay S. Bryant:
All,
Several members of the Cinder team and I were discussing
On 02/13/2015 01:56 AM, YAMAMOTO Takashi wrote:
Ryu/ofagent CI will be offline during this weekend.
sorry for inconvenience.
YAMAMOTO Takashi
__
OpenStack Development Mailing List (not for usage questions)
Hi Boris,
Thanks for your input. I do like the idea of picking up the changes that have
not been active. Do you have resources in mind to dedicate for this?
My personal take is that if some piece of work has not been touched for a
month, it’s probably not that important after all and the
Stefano Maffulli wrote:
And so far, no real indication of why IRC is worse than a private
phone call or a water-cooler conversation on a regular basis.
Multiple people have explained why already and you're choosing to ignore
their words: permanent private IRC channels are a bad habit that
Hi list,
I would like to add the 'add' capability to the HTTP glance store.
Let's say I (as an operator or cloud admin) provide an HTTP server where
(authenticated/trusted) users/clients can make the following HTTP request :
POST http://server1/myLinuxImage HTTP/1.1
Host: server1
+1 to Andrew
This is actually what we want to do with SSL keys.
On Wed, Feb 11, 2015 at 3:26 AM, Andrew Woodward xar...@gmail.com wrote:
We need to be highly security conscious here doing this in an insecure
manner is a HUGE risk so rsync over ssh from the master node is usually (or
scp) OK
Sorry, I forgot about
5) If we put all our OVS/OF bridge logic in just one bridge (instead of N:
br-tun, br-int, br-ex, br-xxx),
the performance should be yet higher, since, as far as I understood, flow
rule lookup could be more
optimized into the kernel megaflows without
James E. Blair wrote:
[...]
I think in general though, it boils down to the fact that we need to
answer these questions for each of the repos:
A) Should the broader community register ±1 or simply comments? (Now
that we may distinguish them from TC member votes.)
B) Should individual
On 13/02/15 14:17 +, Kuvaja, Erno wrote:
Hi Boris,
Thanks for your input. I do like the idea of picking up the changes that have
not been active. Do you have resources in mind to dedicate for this?
My personal take is that if some piece of work has not been touched for a
month, it’s
Dan,
One of the technical guys here at Cisco asked me a really good technical
question about libvirt upgrades in containers which I was unable to answer. My
suspicion is the linux VM system just sorts it out, but I wanted to get your
input.
Assume libvirt version 1 is running in a container.
On 02/13/2015 10:01 AM, Jordan Pittier wrote:
What is the difference between just calling the Glance API to upload
an image, versus adding add() functionality to the HTTP image store?
You mean using glance image-create --location
http://server1/myLinuxImage [..] ? If so, I guess adding the
Put it in this way, it also makes sense. But I think I need to see it
translated in code to figure it out properly. Anyway, this is something which
pertains the base classes rather than the reference driver.
I think from the perspective of the reference driver we should just raise if a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/13/2015 02:33 AM, Kevin Benton wrote:
Why did the services fail with the stdlib patched? Are they
incompatible with eventlet?
It's not like *service entry points* are not ready for neutron.* to be
monkey patched, but tools around it (flake8
Hi,
Getting so mixed that I’ll jump to the inline commenting as well.
From: Boris Pavlovic [mailto:bo...@pavlovic.me]
Sent: 13 February 2015 15:01
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [glance] Cleanout of inactive change proposals
from
Hi,
while trying to integrate dibbler client with neutron to support PD, we
countered a few issues with the dibbler client (and server). With a neutron
router, we have the qg-xxx interface that is connected to the public network,
on which a dhcp server is running on the delegating router. For
Humm this doesn't have to be complicated, for a start.
- Figuring out the http method the server expects (POST/PUT)
Yeah, I agree. Theres no definitive answer to this but I think PUT makes
sense here. I googled 'post vs put' and I found that the idempotent and
who is in charge of the actual
Kuvaja, Erno kuv...@hp.com writes:
Hi all,
We have almost year old (from last update) reviews still in the queue
for glance. The discussion was initiated on yesterday's meeting for
adopting abandon policy for stale changes.
Hi,
Abandoning changes submitted by other people is not a good
I was traveling for two days, and I miss a great thread like this. Go
figure! One comment in-line.
On Wed, Feb 11, 2015 at 3:55 AM, Flavio Percoco fla...@redhat.com wrote:
Greetings all,
During the last two cycles, I've had the feeling that some of the
things I love the most about this
Hello Debo/Tim
My understanding is that with Congress things like filters (e.g. anti-affinity
or other aggregates) will be replaced to be written as policies with Datalog.
Goals (a Policy), Constraints (policies in Congress) will also get translated
to (for example) linear programs in some
Jay, I am afraid I didn't understand your point.
Could you rephrase/elaborate on What is the difference between just
calling the Glance API to upload an image, versus adding add() please ?
Currently, you can't call the Glance API to upload an image if the
default_store is the HTTP store.
On Fri,
Folks, next Monday is Presidents Day [1] here in the US, so given we'll
likely have a very low turnout at the meeting, I'm going to cancel the
weekly Neutron meeting [2].
However, I encourage people to continue reviewing specs for Kilo-3 [3]. We
have a lot of patches out for review, so the more
From: Salvatore Orlando sorla...@nicira.commailto:sorla...@nicira.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Friday, February 13, 2015 at 8:26 AM
To: OpenStack Development Mailing
Andrew,
It looks like what you've described is already done for ssh keys [1].
[1] https://review.openstack.org/#/c/149543/
On Fri, Feb 13, 2015 at 6:12 PM, Vladimir Kuklin vkuk...@mirantis.com
wrote:
+1 to Andrew
This is actually what we want to do with SSL keys.
On Wed, Feb 11, 2015 at
I'm happy to sponsor this.
On 02/12/2015 01:32 PM, Jay Faulkner wrote:
Hi Nova cores,
We’d like to request an FFE for this added nova feature. It gives a real
interface - a JSON file - to network data inside the instance. This is a
patch Rackspace carries downstream, and we’ve had lots of
Hi Ihar,
To answer your questions in order:
1. Yes, you are understanding the intention correctly. Dibbler doesn¹t
currently support client restart, as doing so causes all existing
delegated prefixes to be released back to the PD server. All subnets
belonging to the router would potentially
Based upon the feedback from this thread, I want to welcome Marek as the newest
member of keystone core.
Cheers,
Morgan
--
Morgan Fainberg
On February 10, 2015 at 9:51:16 AM, Morgan Fainberg (morgan.fainb...@gmail.com)
wrote:
Hi everyone!
I wanted to propose Marek Denis (marekd on IRC) as a
On 02/13/2015 11:42 AM, Jeremy Stanley wrote:
For a few months, some project core teams (including Nova's) have
been running with an ACL granting access to the rebase button in
Gerrit for all the projects they manage, a permission usually only
exposed to the owner of an individual change. This
Adam, Nova client does it for some reason during a call to
nova.servers.list()
On Thu, Feb 12, 2015 at 10:03 PM, Adam Young ayo...@redhat.com wrote:
On 02/12/2015 10:40 AM, Alexander Makarov wrote:
A trust token cannot be used to get another token:
On Fri, Feb 13, 2015 at 10:57 AM, John Davidge (jodavidg)
jodav...@cisco.com wrote:
Hi Ihar,
To answer your questions in order:
1. Yes, you are understanding the intention correctly. Dibbler doesn¹t
currently support client restart, as doing so causes all existing
delegated prefixes to be
-Original Message-
From: James E. Blair [mailto:cor...@inaugust.com]
Sent: 13 February 2015 16:44
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [glance] Cleanout of inactive change proposals
from review
Kuvaja, Erno kuv...@hp.com
Hi Debo and Yathi,
We’re completely on the same page here. We’ve known about the solver-scheduler
for a while now (I even attended your Atlanta talk), and I always expected
Congress would integrate with it. As you say, now it’s a matter of getting
down to the details.
A bit on the context…
For a few months, some project core teams (including Nova's) have
been running with an ACL granting access to the rebase button in
Gerrit for all the projects they manage, a permission usually only
exposed to the owner of an individual change. This has been
generally useful for them, especially
Thank you, everyone! :)
Dnia 13 lutego 2015 18:35:09 CET, Morgan Fainberg morgan.fainb...@gmail.com
napisał(a):
Based upon the feedback from this thread, I want to welcome Marek as
the newest member of keystone core.
Cheers,
Morgan
--
Morgan Fainberg
On February 10, 2015 at 9:51:16 AM, Morgan
On 02/12/2015 04:10 PM, Chris Friesen wrote:
On 02/12/2015 03:44 AM, Sylvain Bauza wrote:
Any action done by the operator is always more important than what the
Scheduler
could decide. So, in an emergency situation, the operator wants to
force a
migration to an host, we need to accept it
Congrats Marek, well deserved!
On Fri, Feb 13, 2015 at 2:35 PM, Morgan Fainberg morgan.fainb...@gmail.com
wrote:
Based upon the feedback from this thread, I want to welcome Marek as the
newest member of keystone core.
Cheers,
Morgan
--
Morgan Fainberg
On February 10, 2015 at 9:51:16 AM,
On Feb 13, 2015, at 09:42, Jeremy Stanley fu...@yuggoth.org wrote:
For a few months, some project core teams (including Nova's) have
been running with an ACL granting access to the rebase button in
Gerrit for all the projects they manage, a permission usually only
exposed to the owner of
-Original Message-
From: Steve Gordon [mailto:sgor...@redhat.com]
Sent: Wednesday, February 11, 2015 8:49 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Znoinski, Waldemar
Subject: Re: [openstack-dev] Testing NUMA, CPU pinning and large pages
-
We have a approximately 10 BPs for Kilo-3 [1] which do not have any code
proposed for review yet. If you're assigned to a BP in this category, I
encourage you to work to submit your code in the coming week. Waiting until
the Feature Proposal Freeze (FPF) on March 5 [2] to propose your code will
Erno Kuvaja wrote:
We have almost year old (from last update) reviews still in the queue
for glance. The discussion was initiated on yesterday's meeting for
adopting abandon policy for stale changes.
I'm okay with abandoning old some old reviews which are obviously going
nowhere, such as ones
On 02/13/2015 11:55 AM, Jordan Pittier wrote:
Jay, I am afraid I didn't understand your point.
Could you rephrase/elaborate on What is the difference between just
calling the Glance API to upload an image, versus adding add() please ?
Currently, you can't call the Glance API to upload an image
Hi all,
I would like to invite you to review my proposal on tagging guidelines for
the API-WG. The proposal is heavily based on the recent nova tagging spec,
but I decided to deviate from it in a couple of places (I noted in the
document my reasons).
Feedback welcome.
Thanks,
Miguel
I'm sure it would be helpful if I give you the link to the document :)
https://review.openstack.org/#/c/155620/
On Fri, Feb 13, 2015 at 11:01 AM, Miguel Grinberg
miguel.s.grinb...@gmail.com wrote:
Hi all,
I would like to invite you to review my proposal on tagging guidelines for
the
Cool, You guys read my mind o.O
RE: the review. We need to avoid copying the secrets to nodes that don't
require them. I think it might be too soon to be able to make granular
tasks based for this, but we need to move that way.
Also, how are the astute tasks read into the environment? Same as
On 02/13/2015 01:02 PM, Hoban, Adrian wrote:
-Original Message-
From: Steve Gordon [mailto:sgor...@redhat.com]
Sent: Wednesday, February 11, 2015 8:49 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Znoinski, Waldemar
Subject: Re: [openstack-dev] Testing NUMA,
Hi Tim,
Glad to collaborate and work towards nailing down the details. Yeah in terms
of policy enforcement from Congress, it makes sense to delegate to
domain-specific policy engines. It will be good to go through this PoC and to
start thinking about the integration points of Congress with
1.
A few months back we started the process to remove the tempest CLI
tests from tempest [0]. Now that we have successfully pulled
novaclient CLI
tests out of tempest, we have the process sorted out. We now
have a process
that should be easy to follow for each project,
Hi,
this might be a dumb question, is it possible to have a stand-alone Manila
service that could be used by clients outside of a specific OpenStack
cloud? For example, a shared Manila service that VMs in two clouds could
both use?
I am guessing that there would be two drawbacks to this
Hello all,
I'm proposing the Authenticated Encryption (AE) Token specification [1] as
an SPFE. AE tokens increases scalability of Keystone by removing token
persistence. This provider has been discussed prior to, and at the Paris
summit [2]. There is an implementation that is currently up for
No, really. What's up? :) I'm off Monday so starting a 3-day weekend, but
will see you all next week.
__In review and merged this past week__
I'm super pleased with the way that people are responding to our
suggestions and conventions. We are averaging over 60 reviews a day, keep
up the good
Big +1 from me if we can land something solid.
On Fri, Feb 13, 2015 at 3:12 PM, Yee, Guang guang@hp.com wrote:
++
As for the unbound groups concern, our initial internal Federation POCs
worked well with a single group so far. The proposed hierarchical role
groups, or perhaps even
On Fri, Feb 13, 2015, at 11:33 AM, James E. Blair wrote:
Thierry Carrez thie...@openstack.org writes:
Current Cross-Project Repo Rules
...
* Only the TC chair may vote Workflow +1.
My understanding is that currently, any TC member can Workflow+1
On Feb 12, 2015, at 9:29 AM, Ryan Brown
rybr...@redhat.commailto:rybr...@redhat.com wrote:
On 02/10/2015 08:01 AM, Everett Toews wrote:
On Feb 9, 2015, at 9:28 PM, Jay Pipes
jaypi...@gmail.commailto:jaypi...@gmail.com
mailto:jaypi...@gmail.com wrote:
On 02/02/2015 02:51 PM, Stefano Maffulli
On Thu, Feb 12, 2015, at 07:19 AM, Joshua Zhang wrote:
Hi Doug,
Thank you very much for your reply. I don't have any codes, so no any
special codes as well.
Only thing I did is that:
1, use devstack to install a fresh openstack env, all are ok.
2, import neutron-vpnaas
All it does is create a temporary lock directory and then set an env var
to that path so external locks work properly in tests. If you don't
have any external locks or you use
https://github.com/openstack/oslo.concurrency/blob/master/oslo_concurrency/fixture/lockutils.py#L55
for any tests that do
On Fri, Feb 13, 2015 at 2:15 PM, David Kranz dkr...@redhat.com wrote:
Swift is different in that most interesting data is in the headers except
for GET methods, and applying the same methodology as the others does not
make sense to me. There are various ways the swift client could be changed
We get a lot of complaints about problems caused by persistent tokens, so
this would be great to see in K. Given the amount of work required to get
it done, which includes taking care of some other issues, like getting
revocation events working and refactoring the token code (things which
could
I see that in tox.ini, several commands have lockutils-wrapper prefix on
them in the neutron-vpnaas repo. Seems like this was added as part of
commit 88e2d801 for Migration to oslo.concurrency.
Is this needed on the functional, cover, and dsvm-functional targets? I
don't see it in the neutron
What's the test path thing for? Testr should be able to filter out unit
tests or vice versa without altering discovery.
On 14 Feb 2015 08:57, Joe Gordon joe.gord...@gmail.com wrote:
1.
A few months back we started the process to remove the tempest CLI
tests from tempest [0].
Argh. Wrong thread. Sorry. I was aiming for one about logging :(
On 14 Feb 2015 01:48, Jay Pipes jaypi...@gmail.com wrote:
On 02/12/2015 09:59 PM, Robert Collins wrote:
On 5 February 2015 at 13:20, Rochelle Grober rochelle.gro...@huawei.com
wrote:
Duncan Thomas
++
As for the unbound groups concern, our initial internal Federation POCs worked
well with a single group so far. The proposed hierarchical role groups, or
perhaps even supporting nested user groups down the road should offer us more
flexibility in terms user and permission management. For
Digging through the logs this originated from this bug:
https://bugs.launchpad.net/tempest/+bug/1260710
Its probably not needed everywhere and in all the clients.
On Fri, Feb 13, 2015 at 1:06 PM, Robert Collins robe...@robertcollins.net
wrote:
What's the test path thing for? Testr should be
Almost all of the OpenStack REST apis return little of user value in the
response headers, with json bodies containing the returned data. The
tempest client methods had been returning two values with one always
being ignored. To clean that up before moving the service clients to
tempest-lib,
I am a vote of Yes for the Authenticated Encryption (AE) Token
specification receiving a Spec Freeze exception. This approach has
tremendous potential to significantly improve Keystone and POC code
already exists. I feel there is enough runway that it is worth trying to
move forward with
On February 13, 2015 at 11:51:10 AM, Lance Bragstad (lbrags...@gmail.com) wrote:
Hello all,
I'm proposing the Authenticated Encryption (AE) Token specification [1] as an
SPFE. AE tokens increases scalability of Keystone by removing token
persistence. This provider has been discussed prior to,
1 - 100 of 117 matches
Mail list logo
