GRE tunnels are created between all the openstack nodes for the private
networks
I'm not sure what decides which IP's should be in the GRE mesh network but
ip's from the Quantum bridge mapped networks are also added.
Problem solved,
The local_ip in ovs_quantum_plugin.ini is used.
Puppet was
Hi,
I am new to openstack and looking for the metering tools.
I read about the ceilometer, but not found any proper documentation for
this.
Please help me understand regarding the available metering tools.
Regards,
Arumon
___
Mailing list:
Hi folks,
I get the following error message while running nova image-list.
[root@RLD1OPST01 ~]# nova image-list
ERROR: Malformed request url (HTTP 400) (Request-ID:
req-96acb3fd-3fbe-4f71-ba5f-8d143f1da502)
But #glance index works fine.
[root@RLD1OPST01 ~]# glance index
ID
Hi,
Here is a detailed overview of my setup.
Two machines(each 4G RAM and one 2TB disk)
1. Configured as proxy + storage
2. Configured as storage
I followed the folsom object storage administrator guide and created ring
partitions using the following commands.
# swift-ring-builder
Services nova-compute, nova-api, nova-scheduler, nova-network are running
fine.
Still am facing this issue. I can't proceed from here. Please help
On Fri, Mar 8, 2013 at 4:46 PM, Ashutosh Narayan aashutoshnara...@gmail.com
wrote:
Hi folks,
I get the following error message while running nova
Could you please tell us :
- your credentials (except password of course)
- 'keystone endpoint-list'
- 'keystone service-list'
It seems like you're requesting a wrong API.
Is 'nova list' working btw ?
-Sylvain
Le 08/03/2013 12:56, Ashutosh Narayan a écrit :
Services nova-compute,
Hi Sylvain,
Here is the content of ketstonerc file :
[root@RLD1OPST01 ~]# cat keystonerc
export OS_USERNAME=admin
export OS_PASSWORD=x
export OS_TENANT_NAME=demo
export OS_AUTH_URL=http://192.168.105.61:35357/v2.0
keystone endpoint-list throws :
[root@RLD1OPST01 ~]# keystone endpoint-list
Hi Guys,
I've upgraded my swift setup (2 Storage Nodes and 2 Proxy Nodes) from
1.4.6 to 1.7.6. It was upgraded without errors and i've followed this
guides:
https://lists.launchpad.net/openstack/msg16188.html
Hi, Arumon,
You will find the ceilometer documentation at
http://docs.openstack.org/developer/ceilometer/
There are some basic installation and configuration instructions, as well
as an architectural overview. Please do not hesitate to ask questions, so
we can expand and improve what is
https://answers.launchpad.net/nova/+faq/2004
Make sure auth_strategy = keystone is defined in nova.conf
-Sylvain
Le 08/03/2013 13:21, Ashutosh Narayan a écrit :
Hi Sylvain,
Here is the content of ketstonerc file :
[root@RLD1OPST01 ~]# cat keystonerc
export OS_USERNAME=admin
export
I have auth_strategy = keystone defined in nova.conf.
Tenant ID is also set for the same. Any changes I need to do here ?
What else should I see ?
On Fri, Mar 8, 2013 at 6:30 PM, Sylvain Bauza sylvain.ba...@digimind.comwrote:
https://answers.launchpad.net/nova/+faq/2004
Make sure
2013/3/8 Olivier Archer olivier.arc...@ifremer.fr:
2013/3/7 Kieran Spear kisp...@gmail.com:
I've seen this before. My problem was an out of date
/etc/glance/glance-api-paste.ini:
[filter:authtoken]
paste.filter_factory = keystone.middleware.auth_token:filter_factory
Changing it to:
As per point number '2'
2) Check that the tenant ID in the request matches the tenant you are
authenticated under
mentioned in the link you sent where can I verify this ?
On Fri, Mar 8, 2013 at 6:45 PM, Ashutosh Narayan aashutoshnara...@gmail.com
wrote:
I have auth_strategy = keystone defined
Hi,
From the documentation here :
http://docs.openstack.org/trunk/openstack-compute/install/apt/content/ap_installinggrizzlyubuntuprecise.html
I've got problems with 'glance index' :
# glance index
Authorization Failed: Unable to communicate with identity service:
{error: {message: An
Hi Oliver,
think this will solve your problem
In /etc/keystone/keystone.conf
[signing]
token_format = UUID
#certfile = /etc/keystone/ssl/certs/signing_cert.pem
#keyfile = /etc/keystone/ssl/private/signing_key.pem
#ca_certs = /etc/keystone/ssl/certs/ca.pem
#key_size = 1024
#valid_days = 3650
Hi Sylvain,
I followed this
linkhttp://docs.openstack.org/trunk/openstack-compute/install/yum/content/keystone-service-endpoint-create.htmlto
set Nova Compute service
Here is the command I ran earlier to set it :
[root@RLD1OPST01 ~]# keystone --token 58e7c511e8e6ad09be56 --endpoint
Hi Heiko,
So i removed /etc/keystone/ssl created by 'keystone-manage
pki-setup', because using UUID seem easiest to me. But the probem is
still the same for me (Request returned failure status).
Greeting,
2013/3/8 Heiko Krämer krae...@avarteq.de:
Hi Oliver,
think this will solve your
Hi All,
I have two nodes (test1 and test2) that I am trying to set up in a highly
available configuration.
During the setup process I tried running nova-manage service list on both
nodes. It worked fine on test2, but fails on test1 even though I can
connect to the database with the mysql
On 03/08/2013 12:19 PM, Samuel Winchenbach wrote:
Hi All,
I have two nodes (test1 and test2) that I am trying to set up in a
highly available configuration.
During the setup process I tried running nova-manage service list on
both nodes. It worked fine on test2, but fails on test1 even
Excerpts from 蒋闻天's message of 2013-03-06 17:09:57 -0800:
Hi everyone, I have a problem when i use devstack to test heat and quantum.
This is my localrc
DATABASE_PASSWORD=nova
RABBIT_PASSWORD=nova
SERVICE_TOKEN=nova
SERVICE_PASSWORD=nova
ADMIN_PASSWORD=nova
Hello,
I have been testing the new Policy APIs and looking at the policy table in the
Keystone database. When I consider the OpenStack services including Keystone,
I find that they all use a policy.json file stored on the file system. So my
question is how is this new Keystone policy feature
Hi Sylvain,
This seems very odd to me. The reason this should happen is if your
client is sending packets with the DF (don't fragment) bit set in the
TCP header of the packets you are sending. I'd confirm that your
version of 'curl' is doing this (which it should definitely not do!).
What
What does your keystone.conf file have for the following sections?
[signing]
#token_format = UUID
token_format = PKI
certfile = /etc/keystone/ssl/certs/signing_cert.pem
keyfile = /etc/keystone/ssl/private/signing_key.pem
ca_certs = /etc/keystone/ssl/certs/ca.pemkey_size = 1024
valid_days = 3650
Sorry, that must have been a copy and paste error. Here is what I actually
ran:
http://paste2.org/p/3084996
On Fri, Mar 8, 2013 at 12:40 PM, Jay Pipes jaypi...@gmail.com wrote:
On 03/08/2013 12:19 PM, Samuel Winchenbach wrote:
Hi All,
I have two nodes (test1 and test2) that I am trying
Hi all,
I am trying to install openstack and I can't log into dashboard.
In fact, to be accurate, this problem surfaced after I updated openstack
packages for debian from http://33.apt-proxy.gplhost.com/debian. It was
working before.
I don't what went wrong with this upgrade. nova, keystone,
Hi Rick,
You are right. I just ran curl to test for myself and it does set the
DF bit. Why is this? Any ideas why it specifies that the packet cannot
be fragmented?
Thanks,
Aaron
On Fri, Mar 8, 2013 at 11:27 AM, Rick Jones rick.jon...@hp.com wrote:
On 03/08/2013 09:55 AM, Aaron Rosen wrote:
On Mar 8, 2013, at 1:49 PM, Aaron Rosen aro...@nicira.com wrote:
You are right. I just ran curl to test for myself and it does set the
DF bit. Why is this? Any ideas why it specifies that the packet cannot
be fragmented?
http://lmgtfy.com/?q=don%27t+fragment+bit+path+mtu
--
Brad Knowles
On Mar 8, 2013, at 1:54 PM, Brad Knowles bknow...@momentumsi.com
wrote:
On Mar 8, 2013, at 1:49 PM, Aaron Rosen aro...@nicira.com wrote:
You are right. I just ran curl to test for myself and it does set the
DF bit. Why is this? Any ideas why it specifies that the packet cannot
be
On 03/08/2013 11:49 AM, Aaron Rosen wrote:
Hi Rick,
You are right. I just ran curl to test for myself and it does set the
DF bit. Why is this? Any ideas why it specifies that the packet cannot
be fragmented?
Because most, if not virtually all TCP stacks going back to the mid
1990s (RFC 1191
oops. guess I need to change the root password now :P
On Fri, Mar 8, 2013 at 3:09 PM, Samuel Winchenbach swinc...@gmail.comwrote:
http://paste2.org/p/3085807
On Fri, Mar 8, 2013 at 2:46 PM, Jay Pipes jaypi...@gmail.com wrote:
Please paste the results of SELECT User, Host, Password FROM
http://paste2.org/p/3085807
On Fri, Mar 8, 2013 at 2:46 PM, Jay Pipes jaypi...@gmail.com wrote:
Please paste the results of SELECT User, Host, Password FROM mysql.user
when running as root...
Thanks!
-jay
On 03/08/2013 02:25 PM, Samuel Winchenbach wrote:
Here are my grants. I don't
A little more information, or a completely different problem...I just
realized my network node can't ping its public gateway. (Instead of
7.7.7.0/24, I am using 10.42.36.0/23. My gateway is .1 (and has
non-redundant IP of .10), and my Network Node IP is .130). This did work
at one time.
I'm stumped :( Looks like everything is set up correctly to me. What is
interested is that your nova user access works from test2, but there is
no nova@test2 user in the mysql.user table. What about doing a DROP USER
nova@test1; FLUSH PRIVILEGES; and then see if that fixes things... since
the
I dropped those users and no change.
I also set up general logging in mysql but it really doesn't provide any
additional information. Any idea for a next step I could take?
I am almost at the point of taking a tcpdump and trying to recreate the
salted password. :/
Thanks for the help
Sam
Sorry, I really can't think of anything :(
On 03/08/2013 03:52 PM, Samuel Winchenbach wrote:
I dropped those users and no change.
I also set up general logging in mysql but it really doesn't provide any
additional information. Any idea for a next step I could take?
I am almost at the
If you are an ATC for a keystone, nova or ceilometer, you should have
now received in the mail your link to vote in the PTL election for that
project be sure to vote! The elections end March 14.
For the other projects, there was only one person standing for election,
so congratulations guys, you
In designing the API, the goal was to simply store policy.json files (or
any future iterations of it) in any format as a blob in a centralized
location (keystone) that could be retrieved by remote services. While
discussing the design, it spawned a lot of great questions about how to map
policies
Highlights of the week
We
Wrote an OpenStack Operations Guide in 5 Days!
And here it isthe OpenStack
Operations Guide. You can read it in EPUB, MOBI, PDF, or print. The electronic formats are free to
download so click away. The print version costs $29.90
After many hours investigating sign in error in horizon, I found the last
line responsible for this issue in /var/log/apache2/error.log :
[Sat Mar 09 01:12:18 2013] [error] File
/usr/lib/python2.7/dist-packages/novaclient/client.py, line 195, in
request
[Sat Mar 09 01:12:18 2013] [error]
Title: precise_grizzly_ceilometer_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_ceilometer_trunk/127/Project:precise_grizzly_ceilometer_trunkDate of build:Fri, 08 Mar 2013 03:01:09 -0500Build duration:2 min 24 secBuild cause:Started by an SCM
Title: raring_grizzly_ceilometer_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_ceilometer_trunk/129/Project:raring_grizzly_ceilometer_trunkDate of build:Fri, 08 Mar 2013 03:01:08 -0500Build duration:3 min 21 secBuild cause:Started by an SCM
at 20130308-0314Build needed 00:00:00, 0k disc spaceE: Package build dependencies not satisfied; skippingERROR:root:Error occurred during package creation/build
at 20130308
at 20130308
Title: precise_grizzly_python-glanceclient_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-glanceclient_trunk/46/Project:precise_grizzly_python-glanceclient_trunkDate of build:Fri, 08 Mar 2013 04:13:42 -0500Build duration:1 min 56 secBuild
Title: precise_grizzly_python-quantumclient_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-quantumclient_trunk/52/Project:precise_grizzly_python-quantumclient_trunkDate of build:Fri, 08 Mar 2013 04:17:25 -0500Build duration:2 min 30
Title: precise_grizzly_nova_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/769/Project:precise_grizzly_nova_trunkDate of build:Fri, 08 Mar 2013 04:16:11 -0500Build duration:12 minBuild cause:Started by user James PageBuilt
Title: raring_grizzly_ceilometer_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_ceilometer_trunk/130/Project:raring_grizzly_ceilometer_trunkDate of build:Fri, 08 Mar 2013 14:01:09 -0500Build duration:3 min 38 secBuild cause:Started by an SCM
Title: raring_grizzly_ceilometer_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_ceilometer_trunk/132/Project:raring_grizzly_ceilometer_trunkDate of build:Fri, 08 Mar 2013 15:01:11 -0500Build duration:2 min 47 secBuild cause:Started by an SCM
Title: precise_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_keystone_trunk/186/Project:precise_grizzly_keystone_trunkDate of build:Fri, 08 Mar 2013 16:01:10 -0500Build duration:8 min 26 secBuild cause:Started by an SCM
Title: raring_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_keystone_trunk/199/Project:raring_grizzly_keystone_trunkDate of build:Fri, 08 Mar 2013 16:02:05 -0500Build duration:9 min 39 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_keystone_trunk/187/Project:precise_grizzly_keystone_trunkDate of build:Fri, 08 Mar 2013 17:37:03 -0500Build duration:5 min 34 secBuild cause:Started by an SCM
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/855/Project:raring_grizzly_nova_trunkDate of build:Fri, 08 Mar 2013 18:03:24 -0500Build duration:2 min 58 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_keystone_trunk/188/Project:precise_grizzly_keystone_trunkDate of build:Fri, 08 Mar 2013 18:01:10 -0500Build duration:7 min 41 secBuild cause:Started by an SCM
Title: precise_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_keystone_trunk/189/Project:precise_grizzly_keystone_trunkDate of build:Fri, 08 Mar 2013 19:31:14 -0500Build duration:6 min 18 secBuild cause:Started by an SCM
Title: raring_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_keystone_trunk/202/Project:raring_grizzly_keystone_trunkDate of build:Fri, 08 Mar 2013 19:31:09 -0500Build duration:7 min 30 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/858/Project:raring_grizzly_nova_trunkDate of build:Fri, 08 Mar 2013 21:31:10 -0500Build duration:15 minBuild cause:Started by an SCM changeBuilt
57 matches
Mail list logo
