Turn on debug setting in config file and post compute and volume logs'
contents somewhere (e.g. http://paste.openstack.org/ )
Kind regards, Yuriy.
On Thu, Jul 5, 2012 at 12:18 PM, romi zhang romizhang1...@163.com wrote:
I did it just like your ideas,right now, dashboard status was in always
Try to remove that quotes from nexenta_target_prefix flag. They seem
to be the source of this problem.
Kind regards, Yuriy.
On Tue, Jul 3, 2012 at 12:45 PM, romi zhang romizhang1...@163.com wrote:
My nexenta configuration in nova.conf on nova-volume server is:
#nova-volume
Sorry, my bad.
The more free RAM is better (cost is smaller) thanks to this -1.0. So
the default behavior is spread-first indeed. To make it fill-first,
you can add flag --compute_fill_first_cost_fn_weight=1.0 to scheduler
node.
Kind regards, Yuriy.
On Thu, May 3, 2012 at 8:15 PM, Yuriy Taraday
Yes.
By default, once in two minutes host's capabilities are refreshed in
nova-scheduler. These capabilities are then used along with data from
DB to form current host capabilities. After that, resources used by
each instance on the host are subtracted from it. The result
containing the actual
Please post to http://paste.openstack.org error text and backtrace
from nova-api.log.
Kind regards, Yuriy.
On Fri, May 4, 2012 at 6:13 PM, Leander Bessa leande...@gmail.com wrote:
Hello,
I seem to be unable to list the images available in glance. I'm not sure why
this is happening. I've
Just note that since Essex release Nova by default use fill-first cost
function, meaning that nodes with less free RAM will be preferred for
new instances.
Kind regards, Yuriy.
On Sun, Apr 29, 2012 at 8:28 PM, Szymon Grzybowski semy...@gmail.com wrote:
Hi,
Me and my colleague are doing
We can do #includedir /etc/nova/sudoers.d from sudoers as well.
I think, a solution with a separate conf/dir for rootwrap is a step
back to sudo.
Kind regards, Yuriy.
On Wed, May 2, 2012 at 1:54 PM, Thierry Carrez thie...@openstack.org wrote:
Andrew Bogott wrote:
As part of the plugin
, 2012 at 8:05 PM, Lorin Hochstein
lo...@nimbisservices.com wrote:
Yuriy:
On May 3, 2012, at 4:46 AM, Yuriy Taraday wrote:
Just note that since Essex release Nova by default use fill-first cost
function, meaning that nodes with less free RAM will be preferred for
new instances.
Kind regards
Hi!
1. Is your locale anything different from C or en? If so, you're most
likely getting an exception on nova-compute when it tries to start,
exception gets lost (my fault, forgot to file a bug) and nova-compute
dies. The exception is most likely occur because of
So we have to require either developer or user to specify every option.
My change follows exactly this logic.
The separate issue I see with this '/etc' defaults. But even if we keep
them, we should enforce developers to provide default values or require
user to do it.
--
You received this bug
I still think it's a bad idea to inject such values in code. Even with
typical distutils install, you have to respect the prefix which was
provided with code, and if you'll have several installations in your
system, this can lead to some problems. For example, you can install
Keystone with
Now I had no luck trying to reproduce problem that appeared with
db_pool. Maybe it's gone?
Who can walk me through the way to that bug? I think, we should fix it
if it's not fixed already, bring back db_pool and then eventlet will
be all good again, am I right?
Kind regards, Yuriy.
On Fri, Mar
Hello!
I am to start writing documentation on Nexenta driver, but I don't see
any place where I should add it. Am I missing something? Are there any
documentation on nova-volume?
Kind regards, Yuriy.
On Sat, Mar 3, 2012 at 02:30, Anne Gentle a...@openstack.org wrote:
Hi all -
Please
To land Nexenta volume driver, we need review and approval on two changes:
- SnapshotIsBusy: https://review.openstack.org/1416
- driver itself: https://review.openstack.org/4204
I hope, there is some number of kind people who can give me some +1s or
comments on them.
Vish had already reviewed the
a feature freeze
exception request or wait for the Folsom branch to be active (early March?)
Anyone, feel free to correct me!
Brian
-Original Message-
From: Yuriy Taraday yorik@gmail.com
Sent: Wednesday, February 22, 2012 10:55am
To: openstack@lists.launchpad.net
Subject: [Openstack
Hello again, everyone.
We finally got our pass to integrate the driver with Essex release. What
should we do to target our blueprint to Essex release to pass through
feature freeze at essex-3?
We're going to provide code no later than Feb 15, so we'll have enough time
to be ready before code
Since we're clear about how changes should be included in stable branches,
are there any expectations on how often packages (e.g. Ubuntu ones) should
be updated?
Kind regards, Yuriy.
On Fri, Nov 18, 2011 at 10:42, Mark McLoughlin mar...@redhat.com wrote:
Hi James,
On Fri, 2011-11-11 at
prohibited by law.
2011/11/14 Yuriy Taraday yorik@gmail.com
We already noted this version of Nexenta driver.
We found out number of points which proof that this version of driver is
better that modified Solaris driver:
1). it connects to Nexenta through Nexenta API, not SSH.
It's faster
I wonder if we should keep Change ID consistent in stable and master
branches so that if one merged something into master, reviewers
and archaeologists can easily find both related changes in master and all
backports of specific change.
The simple scenario is: push change into master, then
Hello.
So, I'm still trying to understand how to work with Gerrit.
I've uploaded series of commits to Gerrit. One of them is
https://review.openstack.org/159. Patchset has been changed several times
then merged then reverted, but change is still in Merged status. Who should
set it to any other
Thanks to he fix, invalid author problem vanished.
Now I'm getting missing Change-Id in commit message error.
What is the best way to provide Change-Id to existing commits?
Kind regards, Yuriy.
On Wed, Aug 3, 2011 at 18:58, James E. Blair cor...@inaugust.com wrote:
Yuriy Taraday yorik
-msg hook in place and executable. (See here for more details:
http://wiki.openstack.org/GerritWorkflow) This page doesn't mention
it but you need to chmod +x the hook if it isn't already.
Thanks,
Brad
On Thu, Aug 4, 2011 at 2:44 AM, Yuriy Taraday yorik@gmail.com
wrote:
Thanks
Did you consider to implement changes to eliminate rolerefs that I proposed
a week ago?
I think, major version change is good reason to clear some old drawbacks.
Kind regards, Yuriy.
On Fri, Jul 29, 2011 at 00:44, Ziad Sawalha ziad.sawa...@rackspace.comwrote:
Hi -
We're working on the
In process of creating separate backend, I found out several obstacles that
I believe should be removed.
One of them is RoleRefs.
As I suggest, there should no such thing at all. At least they should be
isolated in sql backend which implements relation between tenants, roles and
users through
(Cloud Services); Yuriy Taraday;
openstack@lists.launchpad.net
*Subject:* Re: [Openstack] Keystone tenants vs. Nova projects
** **
In the example I gave below they are not members of any group and have no
roles assigned to them. Should they still be authenticated?
** **
*From
always make sure that the user is authenticated.
** **
Regards,
Liem
** **
*From:* Yuriy Taraday [mailto:yorik@gmail.com]
*Sent:* Thursday, July 14, 2011 10:37 PM
*To:* openstack@lists.launchpad.net
*Cc:* Ziad Sawalha; Rouault, Jason (Cloud Services); Nguyen, Liem Manh
, 2011 at 1:37 AM, Yuriy Taraday yorik@gmail.comwrote:
I think, there should not be such thing as default tenant.
If user does not specify tenant in authentication data, ones token should
not be bound to any tenant, and user should have access to resources based
on global role assignments
There is blueprint
https://blueprints.launchpad.net/keystone/+spec/pluggable-identity-store with
Beta Available.
How can I put my hands on this beta? Where is this code? Are there any
design decisions made on this topic?
I'm specifically interested in LDAP storage backend.
Kind regards, Yuriy.
28 matches
Mail list logo
