openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #24829
Re: Availability Zones in Grizzly are not recognized
Hi,
Please find the below Grizzly link that I have followed to install separate Network, compute and Openstack.
http://docs.openstack.org/grizzly/basic-install/apt/openstack-basic-install-apt-grizzly.pdf
At page 8 I find that the bash script for keystone may not be correctly pasted (any help..!1)
At page 11 unable to I can wget glance but cannot save I get the below error.
Unable to communicate with identity service: {"error": {"message": "Invalid project", " code": 401, "title": "Not Authorized"}}. (HTTP 401)
glance image-create --is-public true --disk-format qcow2 --container-format bare --name "Ubuntu" < ubuntu-12.04-server-cloudimg-amd64-disk1.img
Unable to communicate with identity service: {"error": {"message": "Invalid project", "code": 401, "title": "Not Authorized"}}. (HTTP 401)
My source file is below:
export OS_TENANT_NAME=admin
export OS_USERNAME=admin
export OS_PASSWORD=password
export OS_AUTH_URL="http://localhost:5000/v2.0/";
export SERVICE_ENDPOINT="http://localhost:35357/v2.0";
export SERVICE_TOKEN=password
The Grizzly install setup, I am stuck at glance and get the above error message.
Regards,
Raghavendra
From: Openstack [mailto:openstack-bounces+raghavendra.lad=accenture.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Vogl, Yves
Sent: Tuesday, July 02, 2013 1:51 PM
To: openstack
Cc: Papaspyrou, Alexander
Subject: [Openstack] Availability Zones in Grizzly are not recognized
Hi,
I want to segregate my installation into "Availability Zones".
I've configured a working multi-host installation with following hosts:
[FIGURE 1]
# nova availability-zone-list
+-----------------------+----------------------------------------+
| Name | Status |
+-----------------------+----------------------------------------+
| internal | available |
| |- Controller | |
| | |- nova-conductor | enabled :-) 2013-07-02T08:05:57.000000 |
| | |- nova-scheduler | enabled :-) 2013-07-02T08:05:59.000000 |
| | |- nova-consoleauth | enabled :-) 2013-07-02T08:06:02.000000 |
| |- hvm-A | |
| | |- nova-network | enabled :-) 2013-07-02T08:05:58.000000 |
| |- hvm-B | |
| | |- nova-network | enabled :-) 2013-07-02T08:05:56.000000 |
| |- hvm-C | |
| | |- nova-network | enabled :-) 2013-07-02T08:05:57.000000 |
| |- hvm-D | |
| | |- nova-network | enabled :-) 2013-07-02T08:06:01.000000 |
| nova | available |
| |- hvm-A | |
| | |- nova-compute | enabled :-) 2013-07-02T08:06:03.000000 |
| |- hvm-B | |
| | |- nova-compute | enabled :-) 2013-07-02T08:05:55.000000 |
| |- hvm-C | |
| | |- nova-compute | enabled :-) 2013-07-02T08:06:00.000000 |
| |- hvm-D | |
| | |- nova-compute | enabled :-) 2013-07-02T08:06:00.000000 |
+-----------------------+----------------------------------------+
Now I want to introduce another "Availability Zone" to get something like this:
[FIGURE 2]
# nova availability-zone-list
+-----------------------+----------------------------------------+
| Name | Status |
+-----------------------+----------------------------------------+
| internal | available |
| |- Controller
| |
| | |- nova-conductor | enabled :-) 2013-07-02T08:05:57.000000 |
| | |- nova-scheduler | enabled :-) 2013-07-02T08:05:59.000000 |
| | |- nova-consoleauth | enabled :-) 2013-07-02T08:06:02.000000 |
| |- hvm-A
| |
| | |- nova-network | enabled :-) 2013-07-02T08:05:58.000000 |
| |- hvm-B
| |
| | |- nova-network | enabled :-) 2013-07-02T08:05:56.000000 |
| |- hvm-C
| |
| | |- nova-network | enabled :-) 2013-07-02T08:05:57.000000 |
| |- hvm-D
| |
| | |- nova-network | enabled :-) 2013-07-02T08:06:01.000000 |
| zone_1 | available |
| |- hvm-A
| |
| | |- nova-compute | enabled :-) 2013-07-02T08:06:03.000000 |
| |- hvm-B
| |
| | |- nova-compute | enabled :-) 2013-07-02T08:05:55.000000 |
| |- hvm-C
| |
| | |- nova-compute | enabled :-) 2013-07-02T08:06:00.000000 |
| zone_2 | available |
| |- hvm-D
| |
| | |- nova-compute | enabled :-) 2013-07-02T08:06:00.000000 |
+-----------------------+----------------------------------------+
So I configured on the Controller:
# Scheduler
default_schedule_zone=zone_1
default_availability_zone=zone_1
And on the compute nodes:
# Scheduler
default_availability_zone=zone_1
resp.
# Scheduler
default_availability_zone=zone_2
It seems that those values are ignored because no availability zones are shown up. It still looks like [FIGURE 1].
Am I missing something?
--
Mit freundlichen Grüßen
Yves Vogl
adesso mobile solutions GmbH
Yves Vogl
Leiter IT Operations
Stockholmer Allee 24 | 44269 Dortmund
T +49 231 930 9379 | F +49 231 930 9317 |
Mail: vogl@xxxxxxxxxxxxxxxx<mailto:vogl@xxxxxxxxxxxxxxxx> | Web: www.adesso-mobile.de<http://www.adesso-mobile.de/> | Mobil-Web: adesso-mobile.mobi
Vertretungsberechtigte Geschäftsführer: Dr. Josef Brewing, Frank Dobelmann
Registergericht: Amtsgericht Dortmund
Registernummer: HRB 13763
Umsatzsteuer-Identifikationsnummer gemäß § 27 a Umsatzsteuergesetz: DE201541832
________________________________
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited.
Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.
______________________________________________________________________________________
www.accenture.com
References
