misconfiguration of the rings
Could you tell something about this? Maybe it'll help me avoid some future
failures.
On Wed, Mar 13, 2013 at 5:58 PM, Adam Huffman adam.huff...@gmail.comwrote:
Thanks for looking. With lots of help from tongli on #openstack, I
realised that there had been a
thanks for your cases
On Wed, Mar 13, 2013 at 10:48 PM, Wyllys Ingersoll
wyllys.ingers...@evault.com wrote:
On Mar 12, 2013, at 6:56 PM, Kieran Spear kisp...@gmail.com wrote:
Hi Wyllys,
On 13 March 2013 04:19, Wyllys Ingersoll wyllys.ingers...@evault.com
wrote:
Can someone point me
Yes， you are right， the problem is caused by both exist of n-net and
quantum.
I just add one line, disable_service n-net. It works.
Thank all of you. I will do more test and develop on heat.
2013/3/11 Steven Hardy sha...@redhat.com
On Thu, Mar 07, 2013 at 09:09:57AM +0800, 蒋闻天 wrote:
Hi
Sergey,
Thanks for the detailed project info. We are currently deploying openstack
and being hadoop people for the past few years, we were missing this
functionality. Openstack itself already has most of the required tools to
maintain a cloud infrastructure and as we all know it is a lot learn to
Hi,it depends basically on what you are looking for - you can store the images in both, but Swift is more of an project aimed to propose and high-available and high-tolerant object store. Not saying that Glance doesn't do that - but Glance is more of a repository actuallyRegards,
Razique
Hello everyone,
The first project to publish a release candidate in preparation for the
Grizzly release is OpenStack Networking (code named Quantum)! The RC1 is
available for download at:
https://launchpad.net/quantum/grizzly/grizzly-rc1
Congratulations to the Quantum development team for
I did a mistake in the link follow this instead -
https://github.com/cloud-rack
Regards,
Pranav
On Thu, Mar 14, 2013 at 9:34 AM, Pranav pps.pra...@gmail.com wrote:
Hi,
I don't know weather I'm qualified for being a mentor (ill be graduating
this summer). But I have my project which Ill be
Hi Logan,
Thanks for the reply. I have one more question.
How we will check whether the tunneling is established or not?
I have gone through lot of documents of gre setup and all are says that the
ovs-vsctl show command will show the tunnel info.
Also is there a doc to understand how the magic
Hi,
I am getting the below error while starting the quantum agent. Please help.
ERROR:quantum.agent.linux.ovs_lib:Unable to execute ['ovs-vsctl',
'--timeout=2', 'list-ports', 'br-int']
Regards,
Arumon
___
Mailing list:
The logs should provide also the reason for the failure you are reporting.
If you're using rootwrap, one thing I'd very is that ovs-vsctl is in
your filter list.
You should have something like the following:
ovs-vsctl: CommandFilter, /bin/ovs-vsctl, root
ovs-vsctl_usr: CommandFilter,
Amazing!will follow that :)
Razique Mahroua-Nuage Corazique.mahr...@gmail.comTel: +33 9 72 37 94 15
Le 14 mars 2013 à 00:24, JuanFra Rodriguez Cardoso juanfra.rodriguez.card...@gmail.com a écrit :Great fusion of strong IT buzzwords!!JuanFra
2013/3/13 Sergey Lukjanov slukja...@mirantis.com
Hello
Greetings,
I'm setting up openstack on some machines using
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst.
I'm using 3 nodes: a controller, network node and compute node. All the
network interfaces are VLAN tagged use the
Resolvido, era só instalar os pacotes cloud-init e
cloud-initramfs-growroot. A configuração default deles já ajusta isso
Alex Vitola
@alexvitola
Em 13 de março de 2013 16:57, Alex Vitola alex.vit...@gmail.com escreveu:
Estou instalando algumas maquinas a partir de templates do ubuntu, e
This sounds awesome.
Regards,
Pranav
On Thu, Mar 14, 2013 at 3:37 PM, Razique Mahroua
razique.mahr...@gmail.comwrote:
Amazing!
will follow that :)
*Razique Mahroua** - **Nuage Co*
razique.mahr...@gmail.com
Tel : +33 9 72 37 94 15
Le 14 mars 2013 à 00:24, JuanFra Rodriguez Cardoso
I install folsom as the guide ( basic-install-folsom.pdf ), when I go to
section Glance, and execute : #glance image-list and #glance
image-create, I always get the error like below:
root@controller:~# glance image-create --location
Have you followed a devstack install? Have you verified credentials
(tenant, user, pass, auth_url) in glance-*.conf/.ini are ok?
Regards!
---
JuanFra
2013/3/14 杨峰 hoking.y...@gmail.com
I install folsom as the guide ( basic-install-folsom.pdf ), when I go to
section Glance, and execute :
Hi Brad,
First of all, thank you for the question.
EHO is not just a Hadoop deployment or management tool, but complete
fully-integrated native OpenStack component. EHO will provide an ability to
apply different deployment and provisioning tools using extension mechanism.
So, deployment
Mentors need to fill out specific projects on an Ideas page on the
OpenStack wiki. Here are specifics from their FAQ about what OpenStack as a
project needs to do to apply. Applications open Monday 3/18 and are due
3/29.
1. How does a mentoring organization apply?
The organization should choose
I'm not sure about verifying the GRE tunnels, so I can't be much help there.
As far as understanding how the tunneling happens, GRE is an open protocol,
not specific to OpenStack, or any vendor, and googling GRE should give you
plenty of information about it.
On Mar 14, 2013 5:21 AM, Aru s
Thanks for the reply. I have one more question.
How we will check whether the tunneling is established or not?
tcpdump can show you the GRE traffic:
tcpdump -i ethX proto gre
Cheers,
Robert
___
Mailing list: https://launchpad.net/~openstack
Post to
I have EC2 configured correctly as far as I can tell because I am able to view
my containers using the S3 APIs and S3 tools such as CyberDuck or s3curl.pl,
using ec2 credentials returned by the keystone command line tool.
However, when I use the Horizon user settings interface and select
I figured it out - nova-cert was not installed and running. I need to add this
to my setup when EC2 is enabled, I wasn't aware of the dependency.
-Wyllys
On Mar 14, 2013, at 10:35 AM, Wyllys Ingersoll wyllys.ingers...@evault.com
wrote:
I have EC2 configured correctly as far as I can
On Thu, Mar 14, 2013 at 1:40 AM, Razique Mahroua
razique.mahr...@gmail.comwrote:
Hi,
it depends basically on what you are looking for - you can store the
images in both, but Swift is more of an project aimed to propose and
high-available and high-tolerant object store. Not saying that Glance
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenStack Security Advisory: 2013-007
CVE: CVE-2013-1840
Date: March 14, 2013
Title: Backend credentials leak in Glance v1 API
Reporter: Stuart McLaren (HP)
Products: Glance
Affects: All versions
Description:
Stuart McLaren from HP reported a
Hi!
My Quantum Single Flat is almost working!
My Instance get an IPv4 without any problem but, the metadata isn't
working...
What can I do?
My compute node have the `nova-api-metadata' package, nova.conf have
`metadata_host = 10.32.14.234', the iptables `169.254.169.254' NAT rule is
there
Take a look at the limitations section of the Quantum docs. You will need to
set allow overlapping IP's to false and make sure you have bidirectional
network connectivity between the metadata ip and the tenant private network(s).
The L3 agent.ini also should be configured with the metadata
It doesn't look like you include iscsi_ip_address in cinder.conf. Try setting
this to the IP address of your cinder service.
In the cinder database, the entry for the volume should have the correct IP
address in the provider_location column. If this is defaulted to localhost,
then VMs on your
Hi,
We have deployed OpenStack using the guide provided at the OpenStack
webpage:
Host A : controller node
Host B : network node
Host C : compute node
Everything went fine during the installation process, but when we try to
instantiate a VM, the logs show that the VMs are unable to
Daneyon,
Thanks! But, I'm not using L3, or GRE, or namespaces...
I read the
http://docs.openstack.org/trunk/openstack-network/admin/content/ch_limitations.htmland
I don't think my setup (Single Flat, no GRE, no L3) fits that case...
From my understandings, I'm not using overlapping IP's,
That's the best way I found to see if GRE is up, just watching for two way
proto gre traffic.
Here's how you can match the IP addresses *inside* the GRE packet, which
you probably will want. Note that 0x0a050505 is hexadecimal for my desired
IP address of 10.5.5.5:
root@os-network:~# tcpdump -i
I really appreciate the work from this community!!! :-D
Installing Ubuntu Raring right now to try Grizzly...
Thank you guys!!!
Best,
Thiago
On 14 March 2013 06:01, Thierry Carrez thie...@openstack.org wrote:
Hello everyone,
The first project to publish a release candidate in preparation
Is there a method to do a basic service status check for OpenStack
components ?
I'd like to able to validate that the daemons are able to handle an
unauthenticated request from a monitoring script. This is somewhat
equivalent to a network level ping or nagios probe, i.e. validate that there
On Thu, Mar 14, 2013 at 3:40 PM, Tim Bell tim.b...@cern.ch wrote:
Currently, curl to the service URL just gives 401 error.
Check the exit code, it should be 0 because that 401 error is
generated by the api server. It's alive and responding, just not with
200 codes. If the server doesn't
Make sure that the metadata server has a route back to the VM. Traffic
hitting that NAT rule ensures that data is flowing properly in one
direction, but you need to make sure bits can flow back to establish a
tcp connection. We had this problem running multiple nova-network
servers.
-nld
On Thu,
Hello,
I was able to setup a Grizzly-2 Keystone server with PKI and SSL enabled on an
Ubuntu 12.04 server. I updated to Grizzly-3 and am able to enable PKI but not
SSL. I get Connection refused. Has anyone else run into this problem? Does
anyone else have SSL working with Grizzly-3 Keystone?
Is there a listing of the summint conference (not the design part at [1])
available somewhere? (there used to be the vote for speakers list, but that
now is gone).
[1] http://summit.openstack.org/
___
Mailing list: https://launchpad.net/~openstack
Post
Looks like there's a bug in pki_setup. It didn't generate the SSL certs, only
the signing certs. Workaround is to make ssl using the signing certs for now.
[ssl]
enable = True
certfile = /etc/keystone/ssl/certs/signing_cert.pem
keyfile = /etc/keystone/ssl/private/signing_key.pem
ca_certs =
We are seeing lot of this error when we do load/ stress testing on our swift
cluster..
Our assumption connection time between proxy and object server is timeing
out.
We increase client time out option. Still no luck..
Anybody else has seen this erro..
ERROR __call__ error with PUT
Guys,
I'm about to test Grizzly but, I'm seeing two alternatives:
1- Install Ubuntu 12.04 and add
http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/grizzly
main /etc/apt/sources.list.d/grizzly.list (
I have a question on service endpoints.
I've read that Horizon depends quite heavily on them, and a
misconfiguration there can really mess things up. My question is, does the
endpoint need to be compatible with Horizon?
For instance, as of Grizzly, Keystone will support /v2.0 and /v3
Nova will
On 2013-03-14 17:41:26 -0400 (-0400), andi abes wrote:
Is there a listing of the summint conference (not the design part
at [1]) available somewhere? (there used to be the vote for
speakers list, but that now is gone).
I expect it should be up in a day or two. The chairs have just
finished
Glad you got it resolved, but can you file a bug on pki_setup not
generating SSL certs? I don't believe I've seen that issue.
https://bugs.launchpad.net/keystone
Thanks!
-Dolph
On Thu, Mar 14, 2013 at 4:58 PM, Miller, Mark M (EB SW Cloud - RD -
Corvallis) mark.m.mil...@hp.com wrote:
Looks
On 2013-03-14 22:49:07 + (+), Jeremy Stanley wrote:
I expect it should be up in a day or two. The chairs have just
finished notifying the speakers and are putting polish on the final
schedule.
Or not. The announcement just went out and has the URL to the
preliminary agenda:
**Ideally** you would provide unversioned endpoints for all services, e.g.:
http://keystone:35357/ instead of http://keystone:35357/v2.0/
... and the client would work out what versions are supported and select a
preferred version automatically.
However, we're not quite there yet. I can't
Hello Suchi,
We are doing some similar stress testing for Swift and its working fine for a
normal 100 user (1sec ramp-up)/1MB object size.
Can you please give some more details on your set-up like,
- Object size
- Load/concurrent users
- Size of cluster
-
Hi all,
I'm trying to recover from a mass renaming of our hardware nodes and have
been having a bit of trouble.
After changing the hostname on all of them nova-manage service list show
all the old hostname (in the dead state) and all the new host names. My
first question is how do I remove old
Well, I'm giving it up.
It is almost impossible to enable metadata with Folsom / Quantum / Single
Flat...
I tried everything...
Even this do not help me:
Folsom-Quantum-metadata server issue:
https://answers.launchpad.net/quantum/+question/218237
Since I have now a working Quantum (without
Title: precise_folsom_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_deploy/402/Project:precise_folsom_deployDate of build:Thu, 14 Mar 2013 05:16:12 -0400Build duration:1 min 56 secBuild cause:Started by command line by jenkinsBuilt
Title: raring_grizzly_glance_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_glance_trunk/186/Project:raring_grizzly_glance_trunkDate of build:Thu, 14 Mar 2013 03:33:58 -0400Build duration:2 hr 43 minBuild cause:Started by user James PageBuilt
at 20130314
Title: quantal_folsom_glance_stable
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_glance_stable/207/Project:quantal_folsom_glance_stableDate of build:Thu, 14 Mar 2013 14:01:41 -0400Build duration:1 min 38 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/821/Project:precise_grizzly_nova_trunkDate of build:Thu, 14 Mar 2013 15:01:42 -0400Build duration:6 min 56 secBuild cause:Started by an SCM changeBuilt
Title: precise_folsom_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_deploy/403/Project:precise_folsom_deployDate of build:Thu, 14 Mar 2013 15:23:14 -0400Build duration:1 min 40 secBuild cause:Started by command line by jenkinsBuilt
See http://10.189.74.7:8080/job/folsom_coverage/507/
--
Started by command line by jenkins
Building on master in workspace
http://10.189.74.7:8080/job/folsom_coverage/ws/
No emails were triggered.
[workspace] $ /bin/bash -x
Title: precise_grizzly_nova_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/822/Project:precise_grizzly_nova_trunkDate of build:Thu, 14 Mar 2013 15:31:38 -0400Build duration:12 minBuild cause:Started by an SCM changeBuilt
Title: precise_essex_test
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_test/601/Project:precise_essex_testDate of build:Thu, 14 Mar 2013 16:27:26 -0400Build duration:23 secBuild cause:Started by command line by jenkinsBuilt on:masterHealth
at 20130314
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10711/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10712/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10713/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10714/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10715/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10716/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10717/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10718/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10719/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10720/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10721/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10722/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10724/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
at 20130314
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10725/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10726/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10727/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10730/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
Title: test_juju
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/test_juju/1/Project:test_jujuDate of build:Thu, 14 Mar 2013 22:36:11 -0400Build duration:5.8 secBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability:
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10731/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10732/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10733/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10734/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10736/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10737/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10738/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10739/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10740/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10741/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10742/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10743/
--
Started by timer
Building remotely on pkg-builder in workspace
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash
88 matches
Mail list logo
