Single Node: EC2_ACCESS_KEY environment variable must be set?

Asked by Longshanks

Hello,

I was able to install the nova on single node (Ubuntu 10.04 LTS i686 ). When I tried to make it run following the instructions "http://docs.openstack.org/openstack-compute/admin/content/ch05s07.html". Tried to execute the command `euca-create-volume`. It threw an error "EC2_ACCESS_KEY environment variable must be set". When I looked for the help on search, it said a novarc file shall be created which does not exist.

How do I get this key?

Thank You
Longshanks

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Solved by:
Masanori Itoh
Solved:
Last query:
Last reply:
Revision history for this message
Best Masanori Itoh (itohm) said :
#1

Hi,

Yes, You have to set EC2_ACCESS_KEY and EC2_SECRET_KEY to your environment variables.

As for generation of 'novarc', please see:

http://docs.openstack.org/openstack-compute/admin/content/ch03s03.html#d5e314

Regards,
Masanori

Revision history for this message
Longshanks (samurai-dj-py) said :
#2

Thanks Masanori Itoh, that solved my question.

Revision history for this message
Chuck Scott (connaryscott) said :
#3

I was hoping for a quick start...

http://nova.openstack.org/2011.2/quickstart.html

says nothing about needed variables beginning with EC2....
is there anything authoritative which covers things that are missing that doc?

E.g., i never heard of a command beginning with "euca" although trying to get up to speed with it.

Revision history for this message
Anne Gentle (annegentle) said :
#4

Hi Chuck, that quick start is specifically intended for developers to start quickly, not for actual proof of concepts for administrators. I'd suggest you start with the Starter Guide instead - see http://docs.openstack.org/cactus/openstack-compute/starter/content/.

Revision history for this message
Ashokkumar c (ashokcse) said :
#5

Hi

I am getting similar error when I run this during server1(CC) setup

euca-describe-availability-zones verbose
EC2_ACCESS_KEY environment variable must be set.
Connection failed

Should I have to set EC2_ACCESS_KEY and EC2_SECRET_KEY?
If yes, plz tell me how to do it.

I followed http://docs.openstack.org/cactus/openstack-compute/starter/content/Nova_Components-d1e718.html and I got stuck up in this command .
My nova.conf

--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--lock_path=/var/lock/nova
--state_path=/var/lib/nova
--verbose
--s3_host=192.168.21.171
--rabbit_host=192.168.21.171
--cc_host=192.168.21.171
--ec2_url=http://192.168.21.171:8773/services/Cloud
--fixed_range=192.168.0.0/16
--network_size=8
--FAKE_subdomain=ec2
--routing_source_ip=192.168.21.171
--sql_connection=mysql://root:mygreatsecret@192.168.21.171/nova
--glance_host=192.168.21.171
--image_service=nova.image.glance.GlanceImageService
--iscsi_ip_prefix=192.168.

Revision history for this message
Sateesh (sateesh-chodapuneedi) said :
#6

Hi Ahok,

You need to generate the credentials and source the file novarc to environment variable EC2_ACCESS_KEY and EC2_SECRET_KEY, whether it's single node or multi node installation.

You can find the instructions here,
http://docs.openstack.org/openstack-compute/admin/content/ch03s03.html#d5e314

Revision history for this message
Ashokkumar c (ashokcse) said :
#7

Hi Sateesh

Thanks for ur help.

I executed these comments without error

mkdir –p /root/creds
/usr/bin/python /usr/bin/nova-manage project zipfile $NOVA_PROJECT $NOVA_PROJECT_USER /root/creds/novacreds.zip

unzip /root/creds/novacreds.zip -d /root/creds/
cat /root/creds/novarc >> ~/.bashrc
source ~/.bashrc

But when i execute the below it gives

euca-describe-availability-zones verbose

EC2_ACCESS_KEY environment variable must be set.
Connection failed

I logged in http://open.eucalyptus.com but i am not sure how to get EC2_ACCESS_KEY and EC2_SECRET_KEY ....
and how to add it...

Revision history for this message
Ashokkumar c (ashokcse) said :
#8

Hi

Thank for all help..
Problem solved...
 No need to get EC2_ACCESS_KEY and EC2_SECRET_KEY from anywhere...I just redone the previous steps with little care...

Revision history for this message
Sateesh (sateesh-chodapuneedi) said :
#9

Cool :-)