Ask Your Question

mfischer's profile - activity

2014-06-09 10:17:05 -0500 received badge  Famous Question (source)
2014-05-23 08:51:18 -0500 received badge  Notable Question (source)
2014-05-07 17:18:01 -0500 commented question Resizing Instances on NFS Shared Storage

You can solve the host key issue by creating a key for the nova user and propagating it to all your compute nodes. Basically passwordless ssh needs to work, however, that won't solve the issue of why it's trying to copy at all when it's shared storage. That's where I'm at, did you ever solve it?

2014-03-30 23:07:00 -0500 received badge  Popular Question (source)
2014-03-20 12:50:34 -0500 commented question Does glance-replicator work ?

Same for me, no matter what I try for the fromserver/toserver. The issue is that you apparently can't use IPs:

2014-03-04 16:52:39 -0500 received badge  Notable Question (source)
2014-02-27 12:31:27 -0500 received badge  Famous Question (source)
2014-02-20 03:19:40 -0500 received badge  Popular Question (source)
2014-01-31 17:37:20 -0500 received badge  Enthusiast
2014-01-30 08:00:07 -0500 commented answer What is the purpose of LDAP groups to Keystone?

Using groups to assign roles makes a lot of sense but how do you do the assignment? Do you pass the groupid in place of user id in the CLI?

2014-01-29 22:16:35 -0500 asked a question What is the purpose of LDAP groups to Keystone?

For keystone I understand the purpose of users, tenants, and roles, but when I use LDAP as a backend, what is the purpose of the LDAP groups? Are they supposed to replace tenants or roles or instead can I use the groups to assign roles to? For example, assign the Admin role to everyone in a certain group? (If so, I'd like to know how to do this with the CLI tool since the option is either missing or non-obvious).

2014-01-09 21:11:42 -0500 commented answer How to ensure nova-compute nodes work before they get added to the scheduler?

Perfect! I didn't think of that (now obvious) option.

2014-01-08 15:04:49 -0500 asked a question How to ensure nova-compute nodes work before they get added to the scheduler?

If I bring up a new nova-compute node or bring one back-up that's been having some maintenance done, I'd like to be able to prove to myself that the node could successfully run guests before adding it back into the pool for scheduling. As I understand it, as soon as nova-compute starts, when properly configured, the nova-scheduler (on another node) will see it and it will be available for the scheduler to use. Ideally, I'd boot my node and run some nova commands to prove that I could, for example, start a VM with functional and correct network settings before people start using it. In the case of maintenance, I could simply disable the node with nova-manage and re-enable it later, but for a new node, what's the solution?

As a follow-up, can I run nova commands on a compute node without a scheduler? One idea was to bring up the compute node in an isolated network and test nova, but perhaps this is not possible. Could I temporarily run a local nova-schedule?

2014-01-03 13:26:44 -0500 received badge  Notable Question (source)
2014-01-02 14:27:57 -0500 commented answer remove nova-compute node from inventory

If I have multiple control nodes, do I need to remove it from the DB on each system or are they synchronized?

2014-01-01 01:31:52 -0500 received badge  Popular Question (source)
2013-12-31 13:59:10 -0500 commented answer error: Could not find binary nova-compute on host ... when disabling nova-compute

That was it. nova service list did NOT have the FQDN, so just listing compute02 solved it!

2013-12-31 13:58:48 -0500 received badge  Scholar (source)
2013-12-30 20:29:09 -0500 asked a question error: Could not find binary nova-compute on host ... when disabling nova-compute

I'm trying to disable a compute node and I keep getting this error. I'm on Ubuntu server 12.04 + grizzly. Here's the syntax and error:

admin@control02:~$ sudo nova-manage --debug service disable --service=nova-compute
error: Could not find binary nova-compute on host

I've tried disabling several nodes just to be sure it wasn't the one offline one causing issues.

As far as I see I don't have any path issues on the compute nodes, nova-compute is in the path (/usr/bin)

2013-12-30 19:59:04 -0500 received badge  Supporter (source)