Re: [Openstack] profiling nova-api

Great work! About a year ago I found out than config was in the very top of profiling table. It is there again. That time there was a small misprint that led to constant config reloading. This time i tried to add caching since our config became so dynamic. My efforts can be found here: https://rev

Re: [Openstack] Error in scheduler when create a new instance.

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 https://bugs.launchpad.net/nova/+b

Re: [Openstack] Energy efficiency

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 wrote: > Hi, > > Me and my colleague are doing research about opens

Re: [Openstack] extending rootwrap securely

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 wrote: > Andrew Bogott wrote: >>     As part of the plugin framework, I'm think

Re: [Openstack] Energy efficiency

, 2012 at 8:05 PM, Lorin Hochstein 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.

Re: [Openstack] Energy efficiency

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

Re: [Openstack] [nova-scheduler] Question

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 amo

Re: [Openstack] [Glance][Nova] Can't list images

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 wrote: > Hello, > > I seem to be unable to list the images available in glance. I'm not sure why > this is happening. I've check the logs for

Re: [Openstack] 答复: Is there special setting to attach volume to instance on Nexenta server?

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 wrote: > My nexenta configuration in nova.conf on nova-volume server is: > > > > #nova-volume > > --routing_source_ip=$my_ip >

Re: [Openstack] 答复: 答复: Is there special setting to attach volume to instance on Nexenta server?

nd in dashboard,it was failing into "attaching" status. > > Romi > > -邮件原件- > 发件人: romi zhang [mailto:romizhang1...@163.com] > 发送时间: 2012年7月4日 星期三 11:11 > 收件人: 'openstack@lists.launchpad.net' > 抄送: 'Yuriy Taraday' > 主题: 答复: [Openstac

Re: [Openstack] 答复: 答复: 答复: Is there special setting to attach volume to instance on Nexenta server?

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 wrote: > > I did it just like your ideas,right now, dashboard status was in always > "attaching". > In

Re: [Openstack] [Gerrit] Getting "invalid author"

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 wrote: > Yuriy

Re: [Openstack] Nova D3 Milestone and the skipped tests

Hello. I'm probably prying out of my area of expertise, but anyway. I think that to prevent confusion when it comes to global parts of Nova, this project should be separated to couple of subprojects, including one for the core and e.g. one for every hypervisor supported. When someone wants to crea

Re: [Openstack] [Gerrit] Getting "invalid author"

d message you can add one by > >> amending the commit (git commit --amend) as long as you have the > >> commit-msg hook in place and executable. (See here for more details: > >> http://wiki.openstack.org/GerritWorkflow) This page doesn't mention > >> it but

[Openstack] [Gerrit] More problems

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 sta

Re: [Openstack] Default ports for services

Shouldn't it be a sysadmin's headache? I think, it should be secure enough to run both APIs on one port and let sysadmin decide to allow or deny access to them on some conditions. Kind regards, Yuriy. On Tue, Aug 23, 2011 at 19:00, Ziad Sawalha wrote: > Admin and Service start on different por

Re: [Openstack] Stable branch reviews

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 cherry-

[Openstack] Nexenta Driver proposal

Hello. The Openstack block volume storage demands high reliability and management automation. This can be achieved with specialized storage solutions, but Openstack still lacks integration with this type of storage back-ends. We have created a blueprint

Re: [Openstack] Nexenta Driver proposal

ify the sender by reply e-mail. In such case, > you are hereby notified that any dissemination, distribution, copying or > use of this message or any attachments, for any purpose, is strictly > prohibited by law. > > > > > > 2011/11/14 Yuriy Taraday > >> We already no

Re: [Openstack] Stable branch reviews

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 wrote: > Hi James, > > On Fri, 2011-11-11 at 07:03 +, Mark

Re: [Openstack] [nova-testing] Efforts for Essex

Forgot to CC maillist again. Kind regards, Yuriy. On Thu, Nov 24, 2011 at 14:13, Yuriy Taraday wrote: > > 2011-11-24T00:12:57 I guess eventually we need to push > that to all nova..api layers > > I think, there should be some common package that should allow do this > with

Re: [Openstack] Nexenta Driver proposal

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 freez

Re: [Openstack] Capture of the Keystone/LDAP Role discussion

We have a project running that will definitely verify if current LDAP backend can work with legacy AD. Are you going to change a lot of things in backends? I believe that current model (tree for global roles definitions and all tenant roles as groups in tenant's subtree) is very flexible and repres

Re: [Openstack] Capture of the Keystone/LDAP Role discussion

In fact, my concern is that we are going to adapt essex release for new big installation, but it can become very painful to move to new ksl afterwards for update. I hope it'll not. Kind regards, Yuriy. On Thu, Feb 2, 2012 at 12:12, Yuriy Taraday wrote: > We have a project running t

[Openstack] Call for review: Nexenta volume driver

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

Re: [Openstack] Call for review: Nexenta volume driver

e 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" > Sent: Wednesday, February 22, 2012 10:55am > To: openstack@lists.l

Re: [Openstack] Doc Day March 6th - the plan the plan

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 wrote: > Hi all - > > Please consider this your in

Re: [Openstack] cfg usage - option registration, global objects

How about decorators? For example: @cfg.used_here( cfg.IntOpt('one_opt', default=1), cfg.StrOpt('other_opt', default="www")) def func([self, ]conf, arg1, arg2): do_smth_with(conf.one_opt, conf.other_opt) Of course, this used_here should be able to receive a list of opts and to be appl

Re: [Openstack] Problem nova-network failed on ubuntu 12.04

I think, the best way is to use nova-rootwrap to prevent such problems. Kind regards, Yuriy. On Tue, Mar 6, 2012 at 17:59, Leandro Reox wrote: > Its not , its a requirement actually, and we ask to add this to the docs, > the same happens with nova-volumes > > Regards > > On Tue, Mar 6, 2012 at

Re: [Openstack] Memory leaks from greenthreads

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

[Openstack] [Keystone] Pluggable identity store status

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. _

[Openstack] Keystone tenants vs. Nova projects

Currently Keystone model assumes that user is bound to exactly one tenant. It conflicts with the fact that in Nova user can have access to several projects. Which way will it be? Kind regards, Yuriy. ___ Mailing list: https://launchpad.net/~openstack Pos

Re: [Openstack] Keystone tenants vs. Nova projects

nt:* Thursday, July 14, 2011 12:22 PM > > *To:* Rouault, Jason (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

Re: [Openstack] Keystone tenants vs. Nova projects

user instead. > With a default role, we can 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 > > *T

Re: [Openstack] Keystone tenants vs. Nova projects

mers? > > > On Fri, Jul 15, 2011 at 1:37 AM, Yuriy Taraday wrote: > >> 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 res

Re: [Openstack] Keystone tenants vs. Nova projects

r services - as a @dell user, you can login with > the same email/password to internal resources as well as sfdc ones. ( in > case it's not obvious - you also update your password in one location - the > Dell AD directory) > > On Jul 15, 2011, at 14:14, Yuriy Taraday <

[Openstack] [KeyStone] Should there by any RoleRefs?

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 separ

Re: [Openstack] Service Registration in Keystone (roles, endpoints)

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 wrote: > Hi - > > We're working on the blueprint to allow service

[Openstack] [Gerrit] Getting "invalid author"

Hello. I'm trying to use Gerrit to propose changes to Keystone. I'm using instructions from http://wiki.openstack.org/GerritWorkflow to push my changes. I'm getting "invalid author" error but my settings/contacts page looks fine and the e-mail listed there and in the error message are the same. Wh