Openstack user admin commands removed from nova-manage

Lately I have been trying to get an openstack node up and running on an Ubuntu VM. For which, I was following a couple of the many guides available online. Everything went well until I found out that I was not able to create a user with an admin role using the nova-manage command. I was trying to run,

nova-manage user admin openstack

Much to my disappointment, I got the following error, 

nova-manage: error: argument category: invalid choice: 'user' (choose from 'version', 'bash-completion', 'project', 'account', 'shell', 'logs', 'service', 'db', 'vm', 'agent', 'cell', 'instance_type', 'host', 'flavor', 'fixed', 'vpn', 'floating', 'network')

I was a bit frustrated after going through the wiki for the nova-manage command which said that nova-manage was going away in the Folsom release of openstack, but never said anything about what is going to replace it. That's when I bothered to find out which version of openstack I was using! I know, I should've done it earlier, probably checked the "System requirements" section in the installation/setup tutorials, but then it is when you ignore parts like these that you get a feeling of having finished reading the whole bible in a couple of hours!

Anyway, I figured that I was running Ubuntu 13.04 with Openstack Grizzly. Even though the nova-manage wiki (which I guess was written somewhere around Essex) said that it was supposed to go away in Folsom, I found that it was still available in Grizzly but with some of the subcommands stripped off. I also came across the commit which removed the "user" and a couple of other subcommands from nova-manage which is here: Remove auth-related nova-manage commands · f953091 · openstack/nova · GitHub

Some more time with the codebase, and I came across this file  openstack/nova/nova/auth/manager.py  whose docstring clearly stated that I should be using Keystone going forward. Keystone which is documented here: Keystone - Openstack; seems to be a bit more complex than the simpler but obsolete "nova-manage user" command.

I haven't yet got Keystone fully setup, so that's it for now. But I should be back with an update to this post as to how it goes!

UPDATE:
It turns out that usage of keystone is as simple as:

keystone user-create --name=openstack --pass=openstack --email=admin@example.com

Of course, with a couple of other commands to create an admin role and add the user to that role, but the best part is that the documentation here: Adding Users, Tenants and Roles, is very clear on the usage of it.
Location: Rahul Hsg. Soc., D Lane, Sham Sharan Society, Koregaon Park, Pune, Maharashtra 411001, India

Comments

  1. Anonymous8 December 2022 at 08:50

    At the most effective roulette websites UK gamers can discover, many of these promotions come in the type of deposit-match cash bonuses. You will 로스트아크 all the time discover several of} websites that provide free spins on sure slot games, but phrases of|when it comes to|by method of} the most effective roulette bonuses, you need to} search out the most generous cash bonus. On this page, we’ll provide advice on {how to|the method to|tips on how to} find a secure on-line roulette actual cash casino.

    ReplyDelete

Post a Comment

Popular posts from this blog

Errors while trying to monitor Asterisk through Nagios

Today, I was trying to configure nagios to monitor an asterisk setup. I installed the nagios-plugins-check_sip plugin available for CentOS. I also had check_asterisk downloaded from here just to try out both. Now, check_asterisk and check_sip are perl scipts which can be used to monitor an asterisk setup. When run through the command line, they seem to work fine, i.e: given that asterisk or any other sip server is listening and your command is correct, you should get output similar to this: ;SIP/2.0 200 OK, 0.000585 seconds response time, cnt=1 Although, that's exactly what I got, it didn't work the same way through nagios, I was getting the following as the output from the plugin. (Service check did not exit properly) After enabling debug info for nagios, I found this in the logs, HOST: remotehost, SERVICE: Asterisk, CHECK TYPE: Active, OPTIONS: 1, SCHEDULED: Yes, RESCHEDULE: Yes, EXITED OK: No, RETURN CODE: 3, OUTPUT: **ePN failed to compile /usr/lib64/nagios/plugins/chec...
Read more

Configuring remote access for couchdb

By default, CouchDb is configured to be access only from a local port, i.e: you can connect to a couchdb instance as long as it is on the same host. Also, it is necessary that the HTTP request be made using the loopback IP address (127.0.0.1). In case you want to be able to access a couchdb instance from an external machine, you need to make some changes to the couchdb configuration. Note that you would need to have superuser access in order to make changes to these files. Usually couchdb will have two configuration (ini) files in /etc/couchdb depending on your installation. Both these files (default.ini and local.ini) can be used to enable remote hosts to access couchdb. The configuration required for this is: [httpd] port = 5984 bind_address = 0.0.0.0 By default the configuration would be: [httpd] port = 5984 bind_address = 127.0.0.1 This means that the Http server is bound only to the loopback IP address, which is why we change it to 0.0.0.0 to make it bind to any IP address. If...
Read more

Proxy Error 502 “Reason: Error reading from remote server” with Apache 2.2.3

I had a setup of tomcat running on port 8080 and Apache proxying for tomcat on port 80. If I tried to access webapps directly from tomcat on port 8080,. they were accessible, while on port 80, I would get the followig error: Proxy Error 502 “Reason: Error reading from remote server” with Apache 2.2.3 following fix worked: adding retry=1 acquire=3000 timeout=600 Keepalive=On after the Proxy directive in the http configuration.
Read more