hi zhang hua,
This configuration of LANGUAGE_CODE in settings.py is a global setting
which won't take much effect. that means it mostly likedly will be
overrided by user preferences such as Brower, Session. the latter is
probably done on the GUI of dashboard settings. If the horizon can't get
any
Hi All
I try to install openstack on multi-node .
I can boot instance and use vnc console to visit the instance .
But , I cannot access outside in instance .
I found the fixed ip range didn’t put on the br100 at compute-node only on
compute-controller. The compute-node only install
Hi,
On running 'service openstack-nova-api restart' I am getting error such as
'AttributeError : 'module' object has no attribute 'pipeline_factory''. Can
anyone help me with this??
Thanks in advance.
--Udit Agarwal
___
Mailing list:
Hi,
Can you try :
*echo 1 /proc/sys/net/ipv4/ip_forward* on the nova-network node.
And also modify */etc/sysctl.conf* to uncomment the ip_forward parameter :
*net.ipv4.ip_forward = 1*
Is it ok now ?
Regards
On Thu, Jun 14, 2012 at 10:24 AM, David yuezhou...@hisoft.com wrote:
Hi
Hi All,
Recently I came across the tool called Tempest to perform he integration
tests on a live cluster running openstack.
Can we use this tool to test Quantum networks also?
Are there any tools which do the end-to end testing of openstack components
(including Quantum) like creating multiple
On Tue, Jun 12, 2012 at 9:16 AM, adrian_f_sm...@dell.com wrote:
For anyone interested in documentation I've posted two changes in relation to
the Swift API docs,
Describe the end_marker parameter (https://review.openstack.org/#/c/8375/)
Added section on metadata at account level
On Tue, Jun 12, 2012 at 3:09 AM, Brian Waldon
brian.wal...@rackspace.com wrote:
So it sounds like we're going with case-insensitive string comparison for
role names. There's already a patch in review for Glance, but it sounds like
we'll need to get something up for Swift. Thanks for the input,
On Wed, Jun 13, 2012 at 07:59:59AM -0700, Brian Waldon wrote:
There hasn't been much process around choosing what metadata keys to
use from Nova, and the best way to figure out what we do use is to
trace through the code. Doing that, I found instance_uuid, user_id,
image_type, backup_type,
Thanks Chmouel for reviewing. I am reviewing (and patching as needed) also.
Adrian, the API will not version upwards until the API itself is
redesigned, so the doc will remain an API 1.0 document.
Generally speaking, the documents stored in object-api, compute-api,
identity-api, netconn-api and
- Original Message -
From: Brian Waldon brian.wal...@rackspace.com
To: openstack@lists.launchpad.net (openstack@lists.launchpad.net)
openstack@lists.launchpad.net
Sent: Friday, June 8, 2012 5:50:45 PM
Subject: [Openstack] Comparing roles - case (in)sensitivity
tl;dr - Should we
IMHO, a well-documented WADL + XSD would say a thousand words (maybe more)...
And can serve as a basis for automated testing as well. I understand that the
v3 API draft is perhaps not at that stage yet; but, would like to see a WADL +
XSD set as soon as the concepts are solidified.
Liem
Hi, have any updates there?
Can anybody clarify what happens if controller nodes just going hard shutdown?
I thinking about solution with two hypervisors and putting controller
node in VM shared storage, which can be relaunched when active
hypervisor will die.
Any ideas, advise?
On Tue, Jun 12,
On Jun 14, 2012, at 10:16 AM, Glen Campbell wrote:
My team is working on a set of language bindings for OpenStack and Rackspace
services. The first language we're working on is Python, and I'm trying to
come up with a simple, generic way to handle API extensions.
The first question that
While I understand the reasons for which the RequestExtensions scheme might
be preferred over the resource extension one, I was wondering whether
assigning namespaces to attributes could be a solution to the XML
issue. This would clearly separate core attributes from extended ones.
Bob, can you
On 06/13/2012 12:39 PM, Nick Barcet wrote:
Hi,
The metering project team holds a weekly meeting in #openstack-meeting,
Thursdays at 1600 UTC. Everyone is welcome.
http://wiki.openstack.org/Meetings/MeteringAgenda
Topics for this week:
* Review last week's actions
* dhellmann:
Oops, realized that I didn't include the list…
Glen Campbell • Developer Relations Group
glen.campb...@rackspace.commailto:glen.campb...@rackspace.com • (210)
446-9990 • @glenc
On Jun 14, 2012, at 12:26 PM, Brian Waldon wrote:
My team is working on a set of language bindings for OpenStack and
On Jun 14, 2012, at 1:09 PM, Glen Campbell glen.campb...@rackspace.com wrote:
Two reasons:
1. Because there's existing bindings :) None of us are very strong Python
developers, and it gives us a chance to get through the existing code and
learn from the pros
2. Because there's only
Hey all,
I feel really sad with saying this, now, that we have quite a few instances
in producgtion
since about 5 days at least, I now have encountered the second instance
loosing its
IP address due to No DHCPOFFER (as of syslog in the instance).
I checked the logs in the central nova-network
Has nova-network been restarted? There was an issue where nova-network was
signalling dnsmasq which would cause dnsmasq to stop responding to requests
yet appear to be running fine.
You can see if killing dnsmasq, restarting nova-network, and rebooting an
instance allows it to get a dhcp address
Hey Jim,
Any updates or new ideas on the cause of the intermittent hangs?
I mentioned these on IRC with regards to one of the Essex failures one
thing I've seen with Glance recently is that both the glance-api and
glance-registry now use (and try to auto create) the database by default.
In recent devstack builds, I've seen g-api fail intermittently, too, and
couldn't figure out why it failed (nothing in logs).
This might have been the reason.
-jay
On 06/14/2012 05:48 PM, Dan Prince wrote:
Hey Jim,
Any updates or new ideas on the cause of the intermittent hangs?
I
I don't think putting the controller node completely into a VM is a good
advice,
at least when speaking of nova-scheduler and nova-api (if central).
I may be wrong, and if so, please correct me.
Christian.
On Thu, Jun 14, 2012 at 7:20 PM, Igor Laskovy igor.lask...@gmail.comwrote:
Hi, have any
Hey,
thanks for your reply. Unfortunately there was no process restart in
nova-network nor in dnsmasq,
both processes seem to have been up for about 2 and 3 days.
However, why is the default dhcp_lease_time value equal 120s? Not having
this one overridden
causes the clients to actually
Are you running in VLAN mode? If so, you probably need to update to a new
version of dnsmasq. See this message for reference:
http://osdir.com/ml/openstack-cloud-computing/2012-05/msg00785.html
Vish
On Jun 14, 2012, at 1:41 PM, Christian Parpart wrote:
Hey all,
I feel really sad with
There's a flag 'dhcp_lease_time' (in secs) that can be set in nova.conf.
DHCP clients typically re-up every (dhcp_lease_time/2) seconds, but this
varies based on client. Additionally some dhcp clients are not persistent,
meaning if there's ever a network hiccup and they don't get a dhcp ACK they
+111 from me.
This would make a lot easier extracting info from logs and correlating
events in different logs. In the long run these association might also be
used by metering/billing applications.
This is probably out of scope, but I was wondering whether we can also add
a concept of parent
I vaguely recall Vish mentioning a bug in dnsmasq that had a somewhat
similar problem. (it had to do with lease renewal problems on ip
aliases or something like that).
This issue was particularly pronounced with windows VMs, apparently.
-nld
On Thu, Jun 14, 2012 at 6:02 PM, Christian Parpart
Interesting idea! Do you think we could get this by just logging the request
ID in the service that initiated the request? It does require one extra lookup
when trying to figure it out, but I bet a log analyzer could be written to take
care of that no problem.
Gabe
From: Salvatore Orlando
Hey all,
many many thanks for all your replies, and while already having raised the
dhcp timeouts
just by now, I'll have now enough time to sleep to actually apply the
dnsmasq fix
tomorrow then.
Yes, I am running in VLAN-mode, since this is also the propagated way.
Maybe OpenStack
Hi Liem,
I'm one of the folks who helped Marc get WADL off of the ground. At the time,
my use cases were exactly as you describe: documentation (e.g.,
https://github.com/mnot/wadl_stylesheets) and testing.
Even back then, there was a lot of discussion in the community; e.g., see:
FWIW I haven't run across the dnsmasq bug in our environment using EPEL
packages.
Nate
On Jun 14, 2012 7:20 PM, Vishvananda Ishaya vishvana...@gmail.com wrote:
Are you running in VLAN mode? If so, you probably need to update to a new
version of dnsmasq. See this message for reference:
Udit,
What setup are you using ? devstack ?
Did you start this getting error recently ? Did anything change on your system?
This (https://lists.launchpad.net/openstack/msg11123.html) thread suggests code
was updated without updating api-paste.ini (Not sure if it applies to you since
you
32 matches
Mail list logo
