image-list" because glance-api barfs on a single image and gives up
on the entire API request...and there are no non-INFO/DEBUG messages in
glance logs for this. >:-/
~ Scott
[1] https://bugs.launchpad.net/glance/+bug/1346648
[2] https://bugs.launchpad.net/glance/+bug/1336958
On Fri, Ju
t both these fields to be
> maintained ([0])
>
> [0]
> https://review.openstack.org/#/c/100968/4/specs/juno/artifact-repository.rst
>
> --
> Regards,
> Alexander Tivelkov
>
>
> On Thu, Jul 3, 2014 at 3:44 AM, Scott Devoid wrote:
>
>> Hi folks,
>>
>
Hi Folks,
I have a situation where I previously granted a tenant access to flavor X.
At which point users launched instances based on that flavor. Now I am
removing the tenant from the flavor-access-list since I do not want users
to create any more instances using that flavor.
However, in Horizon
Hi folks,
Background:
Among all services, I think glance is unique in only having a single
'owner' field for each image. Most other services include a 'user_id' and a
'tenant_id' for things that are scoped this way. Glance provides a way to
change this behavior by setting "owner_is_tenant" to fal
gt;
Sorry, this is a bit fastidious, but I think "nova live-migrate" is what
you mean here. "nova migrate", I think, is still a completely separate
code-path. live-migrate needs to talk to both the source and destination
nova-compute services to coordinate and confirm the
?
-- Forwarded message --
From: Michael Hearn
Date: Fri, May 2, 2014 at 9:21 AM
Subject: [Openstack] Glance - and the use of the "project_id:%(project_id)"
rule
To: "openst...@lists.openstack.org"
Having played with the policies and rules within glance's policy.json file
I have
I agree with Amit on this. There needs to be a way for the driver to
indicate that an operation is not currently possible and include some
descriptive message to indicate why. Right now the volume manager assumes
certain behavioral constraints (e.g. that snapshots are completely
decoupled from clon
>
> Not only live upgrades but also dynamic reconfiguration.
>
> Overcommitting affects the quality of service delivered to the cloud user.
> In this situation in particular, as in many situations in general, I think
> we want to enable the service provider to offer multiple qualities of
> service
>
> It may be useful to have an API query which tells you all the numbers you
> may need - real hardware values, values after using the configured
> overcommit ratios and currently used values.
>
+1 to an exposed admin-API for host resource state and calculations,
especially if this allowed you to
Also I would prefer that we not add "special" tenant names. Roles already
had/has problems with "admin", "Member" and "_member_" having special
meaning in some projects.
~ Scott
On Tue, May 27, 2014 at 1:20 PM, Vishvananda Ishaya
wrote:
> Are you aware that there is already a way to do this thr
I would run the meeting if I knew how to. :-)
And isn't next week the "recommended off week"?
~ Scott
On Thu, Apr 24, 2014 at 2:05 AM, Michael Still wrote:
> Hi.
>
> Given no one has volunteered to run the meeting and I can't make it
> because of travel, let's skip this weeks meeting. We'll hav
Hi folks!
I am working to add Sheepdog as a disk backend for the libvirt driver. I
have a blueprint started and an early version of the code. However I am
having trouble working my way thorough the code in the libvirt driver. The
storage code doesn't feel vary modular to start with and my changes
On Fri, Apr 18, 2014 at 11:41 AM, Dean Troyer wrote:
> On Fri, Apr 18, 2014 at 10:51 AM, Scott Devoid wrote:
>
>> The issue is that it is very easy to suggest new features and refactoring
>> when you are very familiar with the codebase. To a newcomer, though, you
>> ar
On Fri, Apr 18, 2014 at 5:32 AM, Sean Dague wrote:
> On 04/18/2014 12:03 AM, Scott Devoid wrote:
> > So I have had a chance to look over the whole review history again. I
> > agree with Sean Dague and Dean Troyer's concerns that the current patch
> > affects code
So I have had a chance to look over the whole review history again. I agree
with Sean Dague and Dean Troyer's concerns that the current patch affects
code outside of lib/storage and extras.d. We should make the Devstack
extension system more flexible to allow for more extensions. Although I am
not
Sergio J Cazzolato wrote:
> I would to see the operators opinion in this blueprint, we need to
> understand if it is useful or it is confusing for you.
>
> https://review.openstack.org/#/c/84432/9
Sergio, I'm reposting this in a new thread since this isn't about quota
templates. Also I'm postin
Adding the Operators list to this since I think they will have some useful
comments.
My experience is that the current Nova quotas are not entirely useful. In
our environment we have a limited number of machines with 32 cores and 1TB
of ram (tens), and a large number with 8 cores and 32GB of ram (
Is it possible to include a link to the original LP Answers page as a
comment on the question? Or are the LP Answers sections getting wiped
completely after the move?
Also perhaps all imported questions should be tagged "lp-answers" or
something? This would help manual curators to vote and further
hort comings on the EC2 logging, and figuring out
> normalizing those would be good as well.
Most of our users work through Horizon or the nova CLI. Good to know about
the EC2 issues though.
On Tue, Jan 28, 2014 at 1:46 PM, Sean Dague wrote:
> On 01/28/2014 12:41 PM, Scott Devoid wrote:
&g
>
> For the uses I've seen of it in the nova api code INFO would be perfectly
> fine in place of AUDIT.
>
We've found the AUDIT logs in nova useful for tracking which user initiated
a particular request (e.g. delete this instance). AUDIT had a much better
signal to noise ratio than INFO or DEBUG.
Related question: Why does resize get called (and the VM put in "RESIZE
VERIFY" state) when migrating from one machine to another, keeping the same
flavor?
On Thu, Jan 16, 2014 at 9:54 AM, Brian Elliott wrote:
>
> On Jan 15, 2014, at 4:34 PM, Clint Byrum wrote:
>
> > Hi Chris. Your thread may
>
> Migrations from Essex to Grizzly/Havana
...
I would find it entirely suitable to upgrade from Essex to Folsom, then
> migrate from nova-volume to cinder and from nova-network to quantum, then
> only to upgrade to Grizzly.
We're in the same spot, upgrading an Essex deployment to Havana. We d
+1 for an answer to this.
The reference documentation suggests running Neutron OVS with a total of 6
software switches between the VM and public NAT addresses. [1]
What are the performances differences folks see with this configuration vs.
the 2 software switch configuration for linux bridge?
[1]
Hi Nikolay and Patrick, thanks for your replies.
Virtual vs. Physical Resources
Ok, now I realize what you meant by "virtual resources," e.g. instances,
volumes, networks...resources provided by existing OpenStack schedulers. In
this case "physical resources" are actually more "removed" since ther
Some thoughts:
0. Should Climate also address the need for an eviction service? That is, a
service that can weight incoming requests and existing resource allocations
using some set of policies and evict an existing resource allocations to
make room for the higher weighted request. Eviction is nec
The only snapshot functions in the volume driver are create_snapshot,
delete_shapshot and create_volume_from_snapshot. That row should probably
be deleted from the wiki since listing snapshots occurs entirely via the
db/api.
I've added the current set of supported features for the Solaris ISCSI
dri
26 matches
Mail list logo
