On Tue, Dec 10, 2013 at 11:48 PM, Gary Kotton gkot...@vmware.com wrote:
On 12/11/13 12:43 AM, Matt Riedemann mrie...@linux.vnet.ibm.com wrote:
On Tuesday, December 10, 2013 4:17:45 PM, Maithem Munshed 71510 wrote:
Hello,
I was wondering, what is the reason behind having nova audit
+1
http://logs.openstack.org/10/61310/2/check/gate-nova-docs/e4ca63f/console.html
2013-12-11
Wangpan
发件人：Gary Kotton gkot...@vmware.com
发送时间：2013-12-11 15:22
主题：[openstack-dev] [Gating-Failures] Docs creation is failing
收件人：OpenStack Development Mailing List (not for usage
On 12/06/2013 03:18 PM, Adalberto Medeiros wrote:
Hello all!
Yesterday, during the QA meeting, I volunteer myself to help the team
handling bugs and defining a better process to triage them.
which is great!
To accomplish that, I would like to suggest a Bug Triage Day for next
week on
On 2013/10/12 21:24, Lyle, David wrote:
I would like to nominate Tatiana Mazur to Horizon Core. Tatiana has been a
significant code contributor in the last two releases, understands the code
base well and has been doing a significant number of reviews for the last to
milestones.
+1
Ok, Russell, if we do go this way creating a separate project what would
be the correct naming for it in openstack?
gce-api, gce-compat, gce or some cryptic name like GraCE or GraCEful,
for example? :)
Alex
10.12.2013 22:14, Russell Bryant пишет:
On 12/10/2013 11:13 AM, Alexandre Levine
I generally tend to agree that once the distributed router is available,
nobody would probably want to use a centralized one.
Nevertheless, I think it is correct that, at least for the moment, some
advanced services would only work with a centralized router.
There might also be unforeseen
Hi Yoshihiro,
In my opinion the use of filters on changes is allowed by the smoketesting
policy we defined.
Notwithstanding that the approach of testing every patch is definitely the
safest, I understand in some cases the volume of patchsets uploaded to
gerrit might overwhelm the plugin-specific
Thanks Miguel!
I will pick up a few tests from the list you put together, and I encourage
too every neutron developer to do the same.
At the end of the day, it's not really different from scripting what you do
everyday to test the code you develop.
I am also available to help new contributors
Thanks Kyle for organizing this. I am attending too!
On Wed, Dec 11, 2013 at 7:50 AM, Irena Berezovsky ire...@mellanox.comwrote:
Please take guys and girls from Israel into account J.
*From:* Yongsheng Gong [mailto:gong...@unitedstack.com]
*Sent:* Wednesday, December 11, 2013 5:20 AM
Hello Peter,
Here are the tests I have done. Already have 240 instances active across all
the 16 compute nodes. To make the tests and data collection easy,
I have done the tests on single compute node
First Test -
* 240 instances already active, 16 instances on the compute node where
Thanks for the detailed write-up Evg.
What is the use of SSLPolicy.PassInfo?
Managing as individual ciphers is a pain, Can we introduce an entity called
cipher groups? This enables to provide built-in cipher groups (HIGH, LOW, DES
etc) as well. At the least we can provide this in the UI+CLI
+1 for Tatiana Mazur to Horizon Core
On 12/10/2013 09:24 PM, Lyle, David wrote:
I would like to nominate Tatiana Mazur to Horizon Core. Tatiana has been a
significant code contributor in the last two releases, understands the code
base well and has been doing a significant number of
On 2013/10/12 23:09, Robert Collins wrote:
On 11 December 2013 05:42, Jaromir Coufal jcou...@redhat.com wrote:
On 2013/09/12 23:38, Tzu-Mainn Chen wrote:
The disagreement comes from whether we need manual node assignment or not.
I would argue that we
need to step back and take a look at the
On 2013/10/12 19:39, Tzu-Mainn Chen wrote:
Ideally, we don't. But with this approach we would take out the
possibility to change something or decide something from the user.
The 'easiest' way is to support bigger companies with huge deployments,
tailored infrastructure, everything connected
Hi all,
TL;DR: I believe that As an infrastructure administrator, Anna wants a
CLI for managing the deployment providing the same fundamental features
as UI. With the planned architecture changes (making tuskar-api thinner
and getting rid of proxying to other services), there's not an obvious
Hi Salvatore,
Thank you for your reply.
2013/12/11 Salvatore Orlando sorla...@nicira.com:
Hi Yoshihiro,
In my opinion the use of filters on changes is allowed by the smoketesting
policy we defined.
Notwithstanding that the approach of testing every patch is definitely the
safest, I
On 12/10/2013 05:57 PM, James E. Blair wrote:
Hi,
Sphinx 1.2 was just released and it is incompatible with distutils in
python 2.7. See these links for more info:
https://bitbucket.org/birkenfeld/sphinx/pull-request/193/builddoc-shouldnt-fail-on-unicode-paths/diff
hi,
I'm attempting to rationalize on the status of tempest blueprints. I
need your help so I organized questions in a few open points.
* (1) I'm looking for input here on the actual status of the following
blueprints, which are already approved or in a good progress state:
+1 for Tatiana Mazur to Horizon Core
not sure if only cores should do the vote, but Tatiana has been very
active, so it will be well deserved. :-)
On 12/11/2013 01:09 PM, Jiri Tomasek wrote:
+1 for Tatiana Mazur to Horizon Core
On 12/10/2013 09:24 PM, Lyle, David wrote:
I would like to
A few clarifications added, next time i'll need to triple-read after
myself :)
On 11.12.2013 13:33, Jiří Stránský wrote:
Hi all,
TL;DR: I believe that As an infrastructure administrator, Anna wants a
CLI for managing the deployment providing the same fundamental features
as UI. With the
Hey,
doc jobs fails because sphinx 1.2 used, all project are now applying 1.2
rule for sphinx to fix it.
Here is a thread with additional info:
http://lists.openstack.org/pipermail/openstack-dev/2013-December/021863.html
Thanks.
On Wed, Dec 11, 2013 at 1:30 PM, Wangpan
Hi,
The 1.2 rule for Sphinx doesn't help, as pointed out by Sean Dague here:
http://lists.openstack.org/pipermail/openstack-dev/2013-December/021921.html
The 1.1.99 rule he proposes works for me (on python-swiftclient):
https://review.openstack.org/#/c/61378/
Regards,
Florent Flament
On 12/10/13 at 11:09am, Flavio Percoco wrote:
On 09/12/13 17:37 -0500, Russell Bryant wrote:
On 12/09/2013 05:16 PM, Gordon Sim wrote:
On 12/09/2013 07:15 PM, Russell Bryant wrote:
[...]
One other pattern that can benefit from intermediated message flow is in
load balancing. If the
Disclaimer: I swear I'll stop posting this sort of thing soon, but I'm
new to the project. I only mention it again because it's relevant in
that I missed any of the discussion on why proxying from tuskar API to
other APIs is looked down upon. Jiri and I had been talking yesterday
and he
On 12/10/2013 05:57 PM, Paul McMillan wrote:
+1 on Tatiana Mazur, she's been doing a bunch of good work lately.
I'm fine with me being removed from core provided you have someone else
qualified to address security issues as they come up. My contributions have
lately been reviewing and
Hi lbaas folks,
Let's meet as usual at #openstack-meeting on Thursday, 12 at 14-00 UTC.
The primary discussion points should be:
1) Third party testing
2) L7 rules
3) Loadbalancer instance
4) HA for agents and HA for HAProxy
Thanks,
Eugene.
___
UTC 22:00 works for me. Really appreciated.
On Wed, Dec 11, 2013 at 12:13 PM, Yongsheng Gong
gong...@unitedstack.com wrote:
UTC 22:00+, which is 6:am beijing time，but if there are guys from Israel
alike, I can get up one hour earlier, just like what I do for neutron
meeting.
On Wed, Dec 11,
On Wed, Dec 11, 2013 at 7:33 AM, Jiří Stránský ji...@redhat.com wrote:
Hi all,
TL;DR: I believe that As an infrastructure administrator, Anna wants a CLI
for managing the deployment providing the same fundamental features as UI.
With the planned architecture changes (making tuskar-api thinner
Thanks for writing this all out!
- Original Message -
Disclaimer: I swear I'll stop posting this sort of thing soon, but I'm
new to the project. I only mention it again because it's relevant in
that I missed any of the discussion on why proxying from tuskar API to
other APIs is looked
On 2013/10/12 19:39, Tzu-Mainn Chen wrote:
Ideally, we don't. But with this approach we would take out the
possibility to change something or decide something from the user.
The 'easiest' way is to support bigger companies with huge deployments,
tailored infrastructure, everything
On Wed, Dec 11, 2013 at 10:35 AM, James Slagle james.sla...@gmail.com wrote:
On Wed, Dec 11, 2013 at 7:33 AM, Jiří Stránský ji...@redhat.com wrote:
1) Make a thicker python-tuskarclient and put the business logic there. Make
it consume other python-*clients. (This is an unusual approach though,
On Wed, Dec 11, 2013 at 9:35 AM, James Slagle james.sla...@gmail.comwrote:
On Wed, Dec 11, 2013 at 7:33 AM, Jiří Stránský ji...@redhat.com wrote:
Previously, we had planned Tuskar arcitecture like this:
tuskar-ui - tuskarclient - tuskar-api - heat-api|ironic-api|etc.
To be clear,
On Tue, Dec 10, 2013 at 10:49 PM, Jamie Lennox jamielen...@redhat.comwrote:
Using the default policies it will simply check for the admin role and not
care about the domain that admin is limited to. This is partially a left
over from the V2 api when there wasn't domains to worry about.
A
Hi,
thanks for starting this conversation.
I will take it little side ways. I think we should be asking why have we
needed the tuskar-api. It has done some more complex logic (e.g.
building a heat template) or storing additional info, not supported by
the services we use (like rack
+1 on moving the domain admin role rules to the default policy.json
-David Lyle
From: Dolph Mathews [mailto:dolph.math...@gmail.com]
Sent: Wednesday, December 11, 2013 9:04 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [keystone] domain admin
I will take it little side ways. I think we should be asking why have
we needed the tuskar-api. It has done some more complex logic (e.g.
building a heat template) or storing additional info, not supported
by the services we use (like rack associations).
That is a perfectly fine
On 12/11/2013 04:35 PM, James Slagle wrote:
On Wed, Dec 11, 2013 at 7:33 AM, Jiří Stránský ji...@redhat.com wrote:
Hi all,
TL;DR: I believe that As an infrastructure administrator, Anna wants a CLI
for managing the deployment providing the same fundamental features as UI.
With the planned
On 11.12.2013 16:43, Tzu-Mainn Chen wrote:
Thanks for writing this all out!
- Original Message -
Disclaimer: I swear I'll stop posting this sort of thing soon, but I'm
new to the project. I only mention it again because it's relevant in
that I missed any of the discussion on why
Configuration Groups is currently developed to associate the datastore
version with a configuration that is created. If a datastore version is not
presented it will use the default similar to the way instances are created
now. This looks like a way of associating the configuration with a
datastore
On Wed, Dec 11, 2013 at 10:41 AM, Jay Dobies jason.dob...@redhat.comwrote:
I'm still fuzzy on what OpenStack means when it says *client. Is that just
a bindings library that invokes a remote API or does it also contain the
CLI bits?
For the older python-*client projects they are both Python
On Dec 10, 2013, at 3:46 PM, Zane Bitter zbit...@redhat.com wrote:
On 10/12/13 15:10, Randall Burt wrote:
On Dec 10, 2013, at 1:27 PM, Zane Bitter zbit...@redhat.com
wrote:
On 10/12/13 12:46, Richard Lee wrote:
Hey all,
We're working on a blueprint
On 12/10/2013 08:41 PM, Devananda van der Veen wrote:
Tue, Dec 10, 2013 at 12:43 PM, David Kranz dkr...@redhat.com
mailto:dkr...@redhat.com wrote:
On 12/09/2013 01:37 PM, Devananda van der Veen wrote:
On Fri, Dec 6, 2013 at 2:13 PM, Clark Boylan
clark.boy...@gmail.com
Hello, guys!
We faced with Glance notifications issue during Tempest tests for
Ceilometer. We tried to send notification by ourselves (during
investigation we've found that Glance uses almost the same code):
from oslo.config import cfg
from oslo import messaging
CONF.rabbit_host = 'localhost'
On 12/11/2013 03:51 PM, Russell Bryant wrote:
On 12/10/2013 05:57 PM, Paul McMillan wrote:
+1 on Tatiana Mazur, she's been doing a bunch of good work lately.
I'm fine with me being removed from core provided you have someone else
qualified to address security issues as they come up. My
It looks to me this schedule as a service is not a service, and it more like an
function with some changeable parameters. It needs many nova and cinder
functions done first.
-原始邮件-
发件人: Qiu Yu unic...@gmail.com
发送时间: 2013/12/11 14:41
收件人: OpenStack Development Mailing List (not for
Greetings Stackers!
The VMwareAPI subteam is still working out a few priorities, but we should
have these mostly ironed out by next week's IRC meeting. If you need to
comment or adjust expectations be sure to show up and let us know. We had a
very active discussion in this week's IRC meeting. I
Hi,
I'm trying to clarify the terminology being used for Tuskar, which may be
helpful so that we're sure
that we're all talking about the same thing :) I'm copying responses from the
requirements thread
and combining them with current requirements to try and create a unified view.
Hopefully,
To that end, I would like to nominate Sandy Walsh from Rackspace to
ceilometer-core. Sandy is one of the original authors of StackTach, and
spearheaded the original stacktach-ceilometer integration. He has been
instrumental in many of my codes reviews, and has contributed much of
the
https://blueprints.launchpad.net/keystone/+spec/update-policy-to-cloud
On 12/11/2013 11:18 AM, Lyle, David wrote:
+1 on moving the domain admin role rules to the default policy.json
-David Lyle
From: Dolph Mathews [mailto:dolph.math...@gmail.com]
Sent: Wednesday, December 11, 2013 9:04 AM
To:
On Wed, Dec 11, 2013 at 01:44:19PM +0100, Giulio Fidente wrote:
hi,
I'm attempting to rationalize on the status of tempest blueprints. I
need your help so I organized questions in a few open points.
* (1) I'm looking for input here on the actual status of the
following blueprints, which
Hi!
This list is for discussion of ongoing bugs and features in Heat. For
user-centric discussions, please use the main openstack mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Thanks!
Excerpts from Haiming Yang's message of 2013-12-11 09:40:32 -0800:
I think it
On 11/12/13 14:15 -0500, Tzu-Mainn Chen wrote:
Hi,
I'm trying to clarify the terminology being used for Tuskar, which may be
helpful so that we're sure
that we're all talking about the same thing :) I'm copying responses from the
requirements thread
and combining them with current
Hi,
I'm trying to clarify the terminology being used for Tuskar, which may be
helpful so that we're sure
that we're all talking about the same thing :) I'm copying responses from
the requirements thread
and combining them with current requirements to try and create a unified
view.
So glad we're hashing this out now. This will save a bunch of headaches
in the future. Good call pushing this forward.
On 12/11/2013 02:15 PM, Tzu-Mainn Chen wrote:
Hi,
I'm trying to clarify the terminology being used for Tuskar, which may be
helpful so that we're sure
that we're all
The weekly OpenStack QA team IRC meeting will be tomorrow, December 12th at
22:00 UTC in the #openstack-meeting channel.
The meeting agenda can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to add an item to the agenda.
Also, a quick reminder that
This is really helpful, thanks for pulling it together.
comment inline...
On Wed, Dec 11, 2013 at 2:15 PM, Tzu-Mainn Chen tzuma...@redhat.com wrote:
* NODE a physical general purpose machine capable of running in many roles.
Some nodes may have hardware layout that is particularly
On 11/12/13 23:43 +0800, Jay Lau wrote:
Greetings,
Here come a question related to heat auto scale down.
The scenario is as following:
I was trying to deploy hadoop cluster with heat Auto Scaling template.
When scale up a slave node, I can use user-data to do some post work for
configuration
Hello,
I’ve spent the past week experimenting with using Pecan for Nova’s API, and
have opened an experimental review:
https://review.openstack.org/#/c/61303/6
…which implements the `versions` v3 endpoint using pecan (and paves the way for
other extensions to use pecan). This is a
On Wed Dec 11 14:15:22 2013, Tzu-Mainn Chen wrote:
Hi,
I'm trying to clarify the terminology being used for Tuskar, which
may be helpful so that we're sure that we're all talking about the
same thing :) I'm copying responses from the requirements thread and
combining them with current
On 12/06/2013 02:19 AM, Jaromir Coufal wrote:
We are growing. At the moment we are 4 core members and others are
coming in. But honestly, contributors are not coming to specific
projects - they go to reach UX community in a sense - OK this is awesome
effort, how can I help? What can I work on?
On Wed, Dec 11, 2013 at 3:41 PM, Ryan Petrello
ryan.petre...@dreamhost.comwrote:
Hello,
I’ve spent the past week experimenting with using Pecan for Nova’s API,
and have opened an experimental review:
https://review.openstack.org/#/c/61303/6
…which implements the `versions` v3 endpoint
- Original Message -
Devdatta,
On Dec 10, 2013, at 12:37 PM, devdatta kulkarni
devdatta.kulka...@rackspace.com wrote:
Hi Adrian,
Thanks for creating https://etherpad.openstack.org/p/solum-demystified
I am really excited to see the examples. Especially cool is how
Dear Glance core,
Until this review is sorted - https://review.openstack.org/#/c/60971/2
You won't be able to merge any changes, because of the docs issue with
sphinx.
http://lists.openstack.org/pipermail/openstack-dev/2013-December/021863.html
Which means right now every glance patch that goes
Hi Neutron team,
I haven't been involved in neutron meetings for quite some time so I'm not
sure where we are on this at this point. It is often recommended in
OpenStack guides and other operational materials to run multiple
neutron-servers to deal with the API load from Nova. Things like the
Hey everyone!
So the summit was a month back, but on the TripleO side we've kindof
slumped: there is great design work on the console side happening
(yay), but the CD side - where Nova rebuild support is the current
blocker - is basically stalled.
Folk are doing good work on related bits of
On Thu, Dec 12, 2013 at 7:11 AM, Ryan Petrello
ryan.petre...@dreamhost.comwrote:
Hello,
I’ve spent the past week experimenting with using Pecan for Nova’s API,
and have opened an experimental review:
https://review.openstack.org/#/c/61303/6
…which implements the `versions` v3 endpoint
Thanks to new doc patchers Shilla Saebi and Thomas Herve for their clean up
work, especially for the Identity API docs and Heat install!
Be ready for 12/20/13 Doc Bug Day! Looking forward to it.
1. In review and merged this past week:
The Install Guide is still the most worked-on document. I'd
On Thu, Dec 12, 2013 at 8:59 AM, Doug Hellmann
doug.hellm...@dreamhost.comwrote:
On Wed, Dec 11, 2013 at 3:41 PM, Ryan Petrello
ryan.petre...@dreamhost.com wrote:
Hello,
I’ve spent the past week experimenting with using Pecan for Nova’s API,
and have opened an experimental review:
Hi,
To keep this thread alive I would like to share the small screencast I've
recorded for Murano Metadata repository. I would like to share with you
what we have in Murano and start a conversation about metadata repository
development in OpenStack. Here is a link to screencast
On Dec 11, 2013, at 5:44 PM, Georgy Okrokvertskhov
gokrokvertsk...@mirantis.com
wrote:
Hi,
To keep this thread alive I would like to share the small screencast I've
recorded for Murano Metadata repository. I would like to share with you what
we have in Murano and start a conversation
-Original Message-
From: Monty Taylor [mailto:mord...@inaugust.com]
Sent: Wednesday, December 11, 2013 10:28 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Horizon] Nominations to Horizon Core
On 12/11/2013 03:51 PM, Russell Bryant wrote:
On
Hi,
I think BP is a right way to organize this. I will submit BP for metadata
service from our side too.
Thanks
Georgy
On Wed, Dec 11, 2013 at 3:53 PM, Randall Burt randall.b...@rackspace.comwrote:
On Dec 11, 2013, at 5:44 PM, Georgy Okrokvertskhov
gokrokvertsk...@mirantis.com
wrote:
On 12 December 2013 08:15, Tzu-Mainn Chen tzuma...@redhat.com wrote:
Hi,
I'm trying to clarify the terminology being used for Tuskar, which may be
helpful so that we're sure
that we're all talking about the same thing :) I'm copying responses from
the requirements thread
and combining
On Wed, Dec 11, 2013 at 3:05 PM, Sean Dague s...@dague.net wrote:
Dear Glance core,
Until this review is sorted - https://review.openstack.org/#/c/60971/2
Or this one https://review.openstack.org/#/c/61600/ rather
You won't be able to merge any changes, because of the docs issue with
On 2013年12月12日 04:41, Ryan Petrello wrote:
Hello,
I’ve spent the past week experimenting with using Pecan for Nova’s API, and
have opened an experimental review:
https://review.openstack.org/#/c/61303/6
…which implements the `versions` v3 endpoint using pecan (and paves the way for
other
On 12/11/2013 04:17 PM, Chris Buccella wrote:
On 12/02/2013 10:18 AM, Joe Gordon wrote:
Thanks for bringing this up, and I'd welcome a patch in Swift that
would use a common library to generate the transaction id, if it
were installed. I can see that there would be huge
+1 for both Tatiana and cleaning up the core list.
On Wed, Dec 11, 2013 at 5:24 AM, Lyle, David david.l...@hp.com wrote:
I would like to nominate Tatiana Mazur to Horizon Core. Tatiana has been a
significant code contributor in the last two releases, understands the code
base well and has
+1 for Tatiana and the clean-up.
On 11 December 2013 07:24, Lyle, David david.l...@hp.com wrote:
I would like to nominate Tatiana Mazur to Horizon Core. Tatiana has been a
significant code contributor in the last two releases, understands the code
base well and has been doing a significant
On 2013-12-11 18:28:14 +0100 (+0100), Monty Taylor wrote:
On 12/11/2013 03:51 PM, Russell Bryant wrote:
On 12/10/2013 05:57 PM, Paul McMillan wrote:
[...]
If you don't have anyone else who is a web security specialist
on the core team, I'd like to stay. Since I'm also a member of
the
Hi all!
I realize it's been a while since I've posted an update about the project
-- it's high time I do so! And there are several things to report...
We tagged an Icehouse-1 milestone, though we did not publish a tarball just
yet. That should happen at the Icehouse-2 milestone.
Are these NSX routers *functionally* different?
What we're talking about here is a router which, whether it's distributed
or not, behaves *exactly the same*. So as I say, maybe it's an SLA thing,
but 'distributed' isn't really user meaningful if the user can't actually
prove he's received a
Re: Removing Paul McMillan from core
I would argue that it is critical that each project have 1-2 people on core
that are security experts. The VMT is an intentionally small team. They
are moving to having specifically appointed security sub-teams on each
project (I believe this is what I heard
Hello folks
I wrote a blog post today after noticing again that reporters take the
data published on Activity Board and Stackalytics as true, without
asking questions to the protagonists. The problem is that at the moment
none of the systems we have can guarantee that the data is presenting at
So, I've dug into the bug list in the past few days, and want to share what
I've observed.
Over the Havana cycle, we all used the bug list as a way to earmark work we
needed to come back to. Some of those earmarks are stale. Perhaps the
status is incorrect, or we fixed it but didn't close the
Hi all,
The [state-management] project team holds a weekly meeting in
#openstack-meeting on thursdays, 2000 UTC. The next meeting is tomorrow,
2013-12-12!!!
As usual, everyone is welcome :-)
Link: https://wiki.openstack.org/wiki/Meetings/StateManagement
Taskflow:
On 12/11/2013 08:14 PM, Bryan D. Payne wrote:
Re: Removing Paul McMillan from core
I would argue that it is critical that each project have 1-2 people on
core that are security experts. The VMT is an intentionally small team.
They are moving to having specifically appointed security
+1
On Thu, Dec 12, 2013 at 9:14 AM, Bryan D. Payne bdpa...@acm.org wrote:
Re: Removing Paul McMillan from core
I would argue that it is critical that each project have 1-2 people on
core that are security experts. The VMT is an intentionally small team.
They are moving to having
On 13-12-11 11:18 AM, Lyle, David wrote:
+1 on moving the domain admin role rules to the default policy.json
-David Lyle
From: Dolph Mathews [mailto:dolph.math...@gmail.com]
Sent: Wednesday, December 11, 2013 9:04 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Glance allows sharing of images between projects without consumer
project approval
- ---
### Summary ###
Glance allows images to be shared between projects. In certain API
versions, images can be shared without the consumer project's
approval. This
In commit:
https://review.openstack.org/#/c/58814/
There is an assumption that all plugins creates the
plumgrid_neutron.agents which is not the case. I just tested big switch and
plumgrid and they are failing:
INFO [alembic.migration] Running upgrade havana - e197124d4b9, add unique
constraint
On Dec 11, 2013, at 4:45 PM, Clayton Coleman ccole...@redhat.com wrote:
- Original Message -
Devdatta,
On Dec 10, 2013, at 12:37 PM, devdatta kulkarni
devdatta.kulka...@rackspace.com wrote:
Hi Adrian,
Thanks for creating https://etherpad.openstack.org/p/solum-demystified
I
We can involve people in security reviews without having them on the
core review team. They are separate concerns.
Yes, but those people can't ultimately approve the patch. So you'd need to
have a security reviewer do their review, and then someone who isn't a
security person be able to
On 12/11/2013 08:08 PM, Bryan D. Payne wrote:
We can involve people in security reviews without having them on the
core review team. They are separate concerns.
Yes, but those people can't ultimately approve the patch. So you'd need
to have a security reviewer do their review,
On 10:06 Thu 12 Dec , Christopher Yeoh wrote:
On Thu, Dec 12, 2013 at 8:59 AM, Doug Hellmann
doug.hellm...@dreamhost.comwrote:
On Wed, Dec 11, 2013 at 3:41 PM, Ryan Petrello
ryan.petre...@dreamhost.com wrote:
Hello,
I’ve spent the past week experimenting with using Pecan
So again, nothing prevents a non-core security reviewer from reviewing
blueprints and doing code reviews. Believe me any security minded input is
always welcome and weighed carefully.
Although the principle of having a minimum number of security reviewers in core
is certainly a fair point of
95 matches
Mail list logo
