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 c
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 Lukjanov
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 itsel
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
for
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
+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,
>
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 places
On Fri Feb 13 2015 at 5:45:36 PM Eric Windisch 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', pe
+1.
On Fri, Feb 13, 2015 at 11:41 AM, Sebastian Kalinowski
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 really nice thing 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 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 wou
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 the
LXC container. Since 1.0.6, libvirt is able todo this itself and it
would simplify the codepaths in Nova if we can rely on that
In general, without use of user n
On Thu, 12 Feb 2015, Ian Cordasco wrote:
So that particular problem you mention is an issue with the Routes
package. It assumes you will define very (method, route) that you wish to
handle and it’ll 404 everything else (because no definition was found). If
we used better (slightly higher level)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi neutroners,
we** had several conversations recently with our Red Hat fellows who
work on openvswitch (Jiri Benc and Jiri Pirko) regarding the way
neutron utilizes their software. Those were beneficial to both sides
to understand what we do right an
On 02/12/2015 01:37 PM, Daniel P. Berrange wrote:
> On Thu, Feb 12, 2015 at 01:17:55PM -0500, Sean Dague wrote:
>> On 02/12/2015 01:09 PM, Daniel P. Berrange wrote:
>>> On Thu, Feb 12, 2015 at 12:32:10PM -0500, Sean Dague wrote:
Looking recently at the following failure -
http://logs.open
On Thu, 2015-02-12 at 16:01 +, Amrith Kumar wrote:
> How is a private IRC channel any different from a culture of private
> discussions? Having a chat over lunch, in the hallway, on the
> telephone, etc.,
I will articulate again why I think that a group of leaders of OpenStack
*should not* es
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 merge. Here I want to build a good amount of benchmarks to be
able to compare
the current network
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 forwardin
On 02/12/2015 09:59 PM, Robert Collins wrote:
On 5 February 2015 at 13:20, Rochelle Grober 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
likely to stick in the mem
On 13 February 2015 at 12:40, Rossella Sblendido
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 would prev
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 https://etherpad.openstac
-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
> eventu
-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 unders
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
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 possiblilit
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 h
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 clarif
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:
http://boris-42.me/thoughts-on-making-openstack-community-more-user-friendly
On 12 February 2015 at 19:57, John Belamaric
wrote:
>
>
> From: Salvatore Orlando
> 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 Development Mailing List
> Subject
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 sl
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 indivi
Do you have the log of the discussion as well?
On Fri, Feb 13, 2015 at 7:09 AM, Danny Al-Gaaf
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 the
> > cur
Erlon Cruz wrote on 02/13/2015 07:51:34 AM:
> From: Erlon Cruz
> To: Danny Al-Gaaf , "OpenStack Development
> Mailing List (not for usage questions)"
> Date: 02/13/2015 07:53 AM
> Subject: Re: [openstack-dev] [cinder] Etherpad for volume
> replication created ...
>
> Do you have the log of the
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 her
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. Conn
On Fri, Feb 13, 2015 at 6:14 AM, Thierry Carrez
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 away and won't
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)
> Uns
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 commun
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 the
> >LXC container. Since 1.0.6, libvirt is abl
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
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 specified
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
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
Content-Length:
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 blue
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 the
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 http://server1/myL
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 pro
Erno,
> 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 community should
> use the resources to do some work that has actual momentum.
Based on my experience, one of the most common situation in OpenStack is
n
>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
+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 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 but rsync prot
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
> @
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 a
From: Salvatore Orlando mailto:sorla...@nicira.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Friday, February 13, 2015 at 8:26 AM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack
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 e
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
wrote:
> +1 to Andrew
>
> This is actually what we want to do with SSL keys.
>
> On Wed, Feb 11, 2015 at 3:26 AM, Andrew W
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 wrote:
> Greetings all,
>
> During the last two cycles, I've had the feeling that some of the
> things I love the most about this community are degra
-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
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.
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 model
Humm this doesn't have to be complicated, for a start.
>- Figuring out the http method the server expects (POST/PUT)
Yeah, I agree. There"s 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 r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for the write-up! See inline.
On 02/13/2015 04:34 PM, Robert Li (baoli) wrote:
> 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 ro
On 13 February 2015 at 16:22, John Belamaric
wrote:
>
>
> From: Salvatore Orlando
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Date: Friday, February 13, 2015 at 8:26 AM
> To: "OpenStack Development Mailing List (not for us
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 ad
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
"AnyAdd
Hi Ruby
Good point. If you assume congress to be present, then scheduling and most
actions are a result of a policy decision and might not impact the
scheduler. The results of the LP/CVP would allow you to spawn resources at
end points.
However if you assume that there is congress + other entitie
Thierry Carrez 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 (which
> lead to the accidental approval of the previous spec).
I think that was in
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 inter
"Kuvaja, Erno" 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 experience
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
On 13 February 2015 at 17:16, John Belamaric
wrote:
>
>
> 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 perspec
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 recei
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 rev
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 we
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
put
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 prefix
> -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" writes:
On 23:30 Mon 09 Feb , Jay S. Bryant wrote:
> Mike,
>
> A FFE for this has been submitted to Nova and is being sponsored by
> Matt Riedemann: [1]
>
> Assuming that goes through soon, can we please re-address?
>
> Thanks!
> Jay
>
> [1]
> http://www.mail-archive.com/openstack-dev@lists.opens
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…
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
Congrats Marek, well deserved!
On Fri, Feb 13, 2015 at 2:35 PM, Morgan Fainberg
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, Morgan Fainberg
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
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
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 one
> On Feb 13, 2015, at 09:42, 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 indiv
> -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
>
> -
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 chang
Thank you, everyone! :)
Dnia 13 lutego 2015 18:35:09 CET, Morgan Fainberg
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 Fainberg
>(morga
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 wrote:
> On 02/12/2015 10:40 AM, Alexander Makarov wrote:
>
> A trust token cannot be used to get another token:
>
> https://github.com/openstack/keystone/blob/master/key
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
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 wit
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 A
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] Te
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 rev
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 S
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, in
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 hav
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" wrote:
>
>1.
> A few months back we started the process to remove the tempest CLI
> tests from tempest [0]. Now that we have s
Argh. Wrong thread. Sorry. I was aiming for one about logging :(
On 14 Feb 2015 01:48, "Jay Pipes" wrote:
> On 02/12/2015 09:59 PM, Robert Collins wrote:
>
>> On 5 February 2015 at 13:20, Rochelle Grober
>> wrote:
>>
>>> Duncan Thomas [mailto:duncan.tho...@gmail.com] on Wednesday, February
>>> 0
1 - 100 of 126 matches
Mail list logo
