Got the environment up and went to the Dashboard's entry page by
pointing my browser to http://localhost:80/
(http://localhost:8000/ doesn't work).
Logged successfully with 'admin' user name;
entered the System Panel page;
got error in the Overview page:
"Unable to get service info: User does not have admin privileges"
got error in the Instances page:
"Unable to get instance list: (InterfaceError) Error binding
parameter 6 - probably unsupported type......"
got error in the System Panel Services page:
"Unable to get service info: User does not have admin privileges"
it does display glance, identity , nova-compat, nova as up.
got error in User Dashboard Image when launching the only listed
image (id=3, ami-tty):
"Unable to launch instance: (InterfaceError) Error binding
parameter 0 - probably unsupported type. ....."
I didn't see any of the nova processes running with 'nova-*'
names. What names do they have?
I wasn't able to run either the nova-manage nor the euca tools.
How can I do this? It is very helpful to have both access to the
command line tools in nova as well as the Dashboard.
Thanks,
Mauricio
On Mon, Aug 8, 2011 at 8:55 PM, Mark Gius <mark@xxxxxxxxxxxx
<mailto:mark@xxxxxxxxxxxx>> wrote:
$ sudo ./nova.sh branch
$ sudo ./nova.sh install
$ sudo ./nova.sh run
This starts up everything in a screen session. When you
detach the screen with Ctrl-A, D all of the openstack
components will shut down.
The nova.sh script generally sets up a clean environment
every time it is run. This makes it mostly useful for demo
and test environments.
Hopefully this helps.
Mark
On Mon, Aug 8, 2011 at 5:40 PM, Mauricio Arango
<arango.mauricio@xxxxxxxxx
<mailto:arango.mauricio@xxxxxxxxx>> wrote:
Thanks Mark,
I'm trying your nova.sh script. I run it in a clean
Ubuntu instance as 'nova.sh install'. However it didn't
start the nova processes.
Please let me know what is the correct way of runnig the
scrpt to get everything running.
Mauricio
On Mon, Aug 8, 2011 at 5:28 PM, Mark Gius
<mark@xxxxxxxxxxxx <mailto:mark@xxxxxxxxxxxx>> wrote:
Have you set up and configured a keystone instance
for authentication? The dashboard only supports
Keystone based authentication right now, and it looks
like you're trying to connect to nova using Nova's
builtin auth. That howto you are following is quite
old. If you're looking to get openstack up and
running on a single box, you might want to try this
script
(https://github.com/4P/deployscripts/blob/master/nova.sh)
which sets up nova+keystone+glance+dashboard on a
single host.
If you'd like to modify your existing setup, take a
look at https://github.com/openstack/keystone, which
talks about how to set up keystone and integrate it
into your nova installation.
Mark
On Mon, Aug 8, 2011 at 10:15 AM, Mauricio Arango
<arango.mauricio@xxxxxxxxx
<mailto:arango.mauricio@xxxxxxxxx>> wrote:
Hi,
I installed Nova and Dashboard on a single
VirtualBox Ubuntu guest, following the
instructions in:
http://uksysadmin.wordpress.com/2011/02/17/running-openstack-under-virtualbox-a-complete-guide/
and
http://wiki.openstack.org/OpenStackDashboard
I added the following lines in Dahsboard's
local_settings.py, based on information
extracted from the novarc file in Nova:
[
EC2_ACCESS_KEY="afa00c4d-7c1f-4a26-8986-1e291abb4e9d:myproject"
EC2_SECRET_KEY="e77a7fd0-bd94-4e67-9dc1-75a9ee2da45c"
EC2_URL="http://172.241.0.101:8773/services/Cloud";
NOVA_API_KEY="afa00c4d-7c1f-4a26-8986-1e291abb4e9d"
NOVA_USERNAME="mauricio"
NOVA_URL="http://172.241.0.101:8774/v1.0/";
NOVA_CERT="/home/mauricio/ostack/cloud/creds/cacert.pem"
]
The nova install, runs well, tested it using euca
tools.
The GUI part of Dashboard works but fails
connecting to Nova, generating the this error on
any connection attempt:
[
DEBUG:django_openstack.api:extras_api connection
created using token
"e1d4b8ca-9386-4f8e-b194-de6e504d6fa5" and url
"http://localhost:8774/v1.1";
ERROR:django_openstack.dash:ApiException in
instance usage
Traceback (most recent call last):
File
"/home/mauricio/ostack/openstack-dashboard/django-openstack/django_openstack/dash/views/instances.py",
line 167, in usage
usage = api.usage_get(request, tenant_id,
datetime_start, datetime_end)
File
"/home/mauricio/ostack/openstack-dashboard/django-openstack/django_openstack/api.py",
line 270, in inner
return f(*args, **kwargs)
File
"/home/mauricio/ostack/openstack-dashboard/django-openstack/django_openstack/api.py",
line 520, in usage_get
return
Usage(extras_api(request).usage.get(tenant_id,
start, end))
File
"/home/mauricio/ostack/openstack-dashboard/openstack-dashboard/.dashboard-venv/src/openstackx/openstackx/extras/usage.py",
line 15, in get
return
self._get("/extras/usage/%s?start=%s&end=%s" %
(tenant_id, start.isoformat(), end.isoformat()),
"usage")
File
"/home/mauricio/ostack/openstack-dashboard/openstack-dashboard/.dashboard-venv/src/openstackx/openstackx/api/base.py",
line 36, in _get
resp, body = self.api.connection.get(url)
File
"/home/mauricio/ostack/openstack-dashboard/openstack-dashboard/.dashboard-venv/src/openstackx/openstackx/api/connection.py",
line 78, in get
return self._cs_request(url, 'GET', **kwargs)
File
"/home/mauricio/ostack/openstack-dashboard/openstack-dashboard/.dashboard-venv/src/openstackx/openstackx/api/connection.py",
line 66, in _cs_request
raise ex
Unauthorized: This server could not verify that
you are authorized to access the document you
requested. Either you supplied the wrong
credentials (e.g., bad password), or your browser
does not understand how to supply the credentials
required. (HTTP 401)
]
I'm including the contents of the novarc file:
[
NOVA_KEY_DIR=$(pushd $(dirname
$BASH_SOURCE)>/dev/null; pwd; popd>/dev/null)
export
EC2_ACCESS_KEY="afa00c4d-7c1f-4a26-8986-1e291abb4e9d:myproject"
export
EC2_SECRET_KEY="e77a7fd0-bd94-4e67-9dc1-75a9ee2da45c"
export
EC2_URL="http://172.241.0.101:8773/services/Cloud";
export S3_URL="http://172.241.0.101:3333";
export EC2_USER_ID=42 # nova does not use user
id, but bundling requires it
export EC2_PRIVATE_KEY=${NOVA_KEY_DIR}/pk.pem
export EC2_CERT=${NOVA_KEY_DIR}/cert.pem
export NOVA_CERT=${NOVA_KEY_DIR}/cacert.pem
export EUCALYPTUS_CERT=${NOVA_CERT} #
euca-bundle-image seems to require this set
alias ec2-bundle-image="ec2-bundle-image --cert
${EC2_CERT} --privatekey ${EC2_PRIVATE_KEY}
--user 42 --ec2cert ${NOVA_CERT}"
alias ec2-upload-bundle="ec2-upload-bundle -a
${EC2_ACCESS_KEY} -s ${EC2_SECRET_KEY} --url
${S3_URL} --ec2cert ${NOVA_CERT}"
export
NOVA_API_KEY="afa00c4d-7c1f-4a26-8986-1e291abb4e9d"
export NOVA_USERNAME="mauricio"
export NOVA_URL="http://172.241.0.101:8774/v1.0/";
]
Thanks in advance for your help,
Mauricio
_______________________________________________
Mailing list: https://launchpad.net/~openstack
<https://launchpad.net/%7Eopenstack>
Post to : openstack@xxxxxxxxxxxxxxxxxxx
<mailto:openstack@xxxxxxxxxxxxxxxxxxx>
Unsubscribe : https://launchpad.net/~openstack
<https://launchpad.net/%7Eopenstack>
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list:https://launchpad.net/~openstack <https://launchpad.net/%7Eopenstack>
Post to :openstack@xxxxxxxxxxxxxxxxxxx <mailto:openstack@xxxxxxxxxxxxxxxxxxx>
Unsubscribe :https://launchpad.net/~openstack <https://launchpad.net/%7Eopenstack>
More help :https://help.launchpad.net/ListHelp
