that will cause
significant issues down the road.
--Morgan
Sent via mobile
On May 7, 2015, at 09:37, Chris St. Pierre chris.a.st.pie...@gmail.com
wrote:
This bug recently came to my attention:
https://bugs.launchpad.net/nova/+bug/1241587
I've reopened it, because it is an actual problem
to tackle the problem altogether?
Thanks!
--
Chris St. Pierre
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org
that the default security
group is, in fact, not the 'default' security group or the security
group which is default, but rather another beast entirely which isn't even
actually a security group?
Naming: still the hardest problem in computer science. :(
--
Chris St. Pierre
on what network
traffic is allowed between guests; it only affects new tenants created
afterwards.
--
Chris St. Pierre
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
:19 AM, Flavio Percoco fla...@redhat.com wrote:
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
at 12:59 AM, Flavio Percoco fla...@redhat.com wrote:
On 11/02/15 13:42 -0800, Chris St. Pierre wrote:
I recently proposed a change to glance to turn the file-backed scrubber
queue
files into JSON: https://review.openstack.org/#/c/145223/
As I looked into it more, though, it turns out
is reachable again, and I'll
resurrect my blueprint to make the queue files suck less.
Either way I'm happy to make the changes, I'm just not sure what the goal
of these changes was, and how to properly proceed.
Thanks for any clarification anyone can offer.
--
Chris St. Pierre
] [glance] Option to skip deleting images in
use?
Guess that's a implementation detail. Depends on the way you go about
using what's available now, I suppose.
Thanks,
-Nikhil
--
*From:* Chris St. Pierre [chris.a.st.pie...@gmail.com]
*Sent:* Wednesday
installation. I do not consider it a solution to the problem that images
can be deleted in use to take the protected flag away from arbitrary,
bespoke use.
On Thu, Dec 18, 2014 at 6:44 PM, Jay Pipes jaypi...@gmail.com wrote:
On 12/18/2014 02:08 PM, Chris St. Pierre wrote:
I wasn't suggesting that we
that wouldn’t require modification of glance would be a
cron job
that lists images and snapshots and marks them protected while they are in
use.
Vish
On Dec 16, 2014, at 3:19 PM, Collins, Sean
sean_colli...@cable.comcast.com wrote:
On Tue, Dec 16, 2014 at 05:12:31PM EST, Chris St. Pierre
be
too racy unless we we implement a test-and-set for such properties or there
is a different job which queues up these requests and perform sequentially
for each tenant.
Thanks,
-Nikhil
--
*From:* Chris St. Pierre [chris.a.st.pie...@gmail.com]
*Sent
to the trouble of writing a spec
for it, particularly since it doesn't appear that glance currently talks to
Nova as a client at all. Is this something that folks would be interested
in having? Thanks!
--
Chris St. Pierre
___
OpenStack-dev mailing list
, but most of
us take backups anyway. Same deal.
On Tue, Dec 16, 2014 at 2:30 PM, Jay Pipes jaypi...@gmail.com wrote:
Just set the images to is_public=False as an admin and they'll disappear
from everyone except the admin.
-jay
On 12/16/2014 03:09 PM, Chris St. Pierre wrote:
Currently
, then the image can't be deleted by accidentally.
On 17/12/14 10:23, Chris St. Pierre wrote:
The goal here is protection against deletion of in-use images, not a
workaround that can be executed by an admin. For instance, someone without
admin still can't do that, and someone with a fat finger
restrictions
Kilo (?): Use anything you want
At any rate, if accepting Unicode is an issue, then it's been an issue for
a while.
--
Chris St. Pierre
Senior Software Engineer
metacloud.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
consensus on whether or not I need to go through the
interminable blueprint process to get this accepted.
So since everyone seems to think that this is at least not a bad idea, and
since no one seems to know why it was originally changed, what stands
between me and a +2?
Thanks.
--
Chris St. Pierre
that. :)
My review is at https://review.openstack.org/#/c/119421/ if anyone does
find time to +N it. Thanks all!
--
Chris St. Pierre
Senior Software Engineer
metacloud.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
Linking clearly isn't my strong suit:
https://review.openstack.org/#/c/119741/
On Mon, Sep 15, 2014 at 1:58 PM, Chris St. Pierre stpie...@metacloud.com
wrote:
On Mon, Sep 15, 2014 at 11:16 AM, Jay Pipes jaypi...@gmail.com wrote:
I believe I did:
http://lists.openstack.org/pipermail
these printable characters should
not be joined in holy resource naming, speak now or forever hold your peace.
Thanks!
--
Chris St. Pierre
Senior Software Engineer
metacloud.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
19 matches
Mail list logo
