Hey,
FWIW - we're going to be doing a bunch of Fedora 16 OpenStack testing on
#fedora-test-day today
Cheers,
Mark.
Forwarded Message
From: Tim Flink tfl...@redhat.com
Reply-to: Fedora Cloud SIG cl...@lists.fedoraproject.org
To: test-annou...@lists.fedoraproject.org,
Hi,
I've found my way through https://github.com/openstack, and I'm happy to
see that mostly everything is there now. However, I've found still missing:
- python-novaclient
- the debian folder for packaging files (there's no branch for that either)
Is there any plan to fix this?
Also, I've
On 20 paź 2011, at 05:46, aliex_liu wrote:
/var/log/syslog
Oct 20 11:16:17 ubuntu10 libvirtd: 11:16:17.081: 9765: error :
virCommandWait:1229 : internal error Child process (/sbin/iptables --table
mangle --delete POSTROUTING --out-interface virbr0 --protocol udp
--destination-port 68
Hi
in order to work with curl :
curl -v -H X-Auth-User: user -H X-Auth-key: KEY http://IP:PORT/API_VERSION/
-v : verbose
-H : headers
http : ip to request.
I myself use that awesome tool to debug and work on my environments :
http://code.google.com/p/rest-client/
Razique
Le 20 oct. 2011 à
On Thu, Oct 20, 2011 at 03:06:53PM +0800, Thomas Goirand wrote:
Hi,
I've found my way through https://github.com/openstack, and I'm happy to
see that mostly everything is there now. However, I've found still missing:
- python-novaclient
- the debian folder for packaging files (there's no
Cool !
Le 20 oct. 2011 à 12:10, Roman Sokolkov a écrit :
I ve solved. in last commit of python-novaclient
http://bazaar.launchpad.net/~jk0/python-novaclient/master/revision/124
i saw that when service compute it will use publicURL
service_type='compute', endpoint_type='publicURL'):
I have already read that CHECKSUM parameter is not acceptable for some
versions of kernel (distros). I think it's your case.
- May need to update iptables package kernel to support CHECKSUM rule.
[]'s
On Thu, Oct 20, 2011 at 1:46 AM, aliex_liu aliex_...@hotmail.com wrote:
**
/var/log/syslog
I don't remember when the change to log attempts to grab locks landed.
Maybe your version doesn't have that. In that case, my guess is that
it's attempting to grab a lock to fiddle with iptables, but something
is already holding that lock. There should be a nova directory in
/var/lock. Can you
Hi Aaron and all -
Just wanted to make you aware of testing wiki pages that exist already:
http://wiki.openstack.org/SmallTestingGuide
http://wiki.openstack.org/TestGuide
If you look at the info for these pages you can see who has worked on them,
for example see
We need to add these codes to maintain compliance.
https://tools.ietf.org/html/draft-nottingham-http-new-status-02
--andy
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe :
The “Pre-condition Required” status is definitely a good idea, but at least for
Swift it is a band-aid. Full S3-style versioning would be a better solution.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
On Wed, 19 Oct 2011, aliex_liu wrote:
/NOVA-INIT/instances/instacnes-002a/console.log
when i run a instance,the default route has been deleted, and why?
can i add the default route?
only one network interface eth0
A more complete console log would be useful. The instance can't seem
We had extend discussions about the HTTP error code that we retuned for rate
limiting while discussing the compute API. The issue is that we allow users to
discover and query their rate limits. So an over-limit response should be in
the 400 range because we see it as a client error. None of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Do I need to mention the container?
# swift-bench -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U
system:root -K pass -c 10 -s 2 -n 100 -g 10
Traceback (most recent call last):
File /usr/bin/swift-bench, line 134, in module
controller.run()
With some very minor re-wording the “429 Too Many Requests” response could just
as easily apply when the user
has been limited to a specific number of outstanding requests. Essentially the
server tells the user that it will queue
at most N requests from the User and that the N+1st will be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I found some more details in the system log:
http://paste.openstack.org/show/2800/
not sure if this is helpful:
python: abrt: detected unhandled Python exception in /usr/bin/swift-bench
- --sharif
On 10/20/2011 02:42 PM, Sharif Islam wrote:
Do
Hi-
Hishaharu - yes, we are working on the documentation during this milestone.
Razique - thank you for helping out :-)
Ziad
On 10/20/11 4:38 PM, Hisaharu Ishii
ishii.hisah...@nttdata-agilenet.com wrote:
Hi folks,
The auth. scheme has changed recently. Here is a working set with the
last
Np. Let me know if you guys need a hand. We have a lauchpad team 'openstack
nova-doc team' which deals with the doc.
Regards
Le 20 oct. 2011 à 23:50, Ziad Sawalha ziad.sawa...@rackspace.com a écrit :
Hi-
Hishaharu - yes, we are working on the documentation during this milestone.
Razique
Hi Ziad,
Cool! I'm glad to hear it.
Hisaharu
2011/10/20 Ziad Sawalha ziad.sawa...@rackspace.com:
Hi-
Hishaharu - yes, we are working on the documentation during this milestone.
Razique - thank you for helping out :-)
Ziad
On 10/20/11 4:38 PM, Hisaharu Ishii
For those of you not on the Orchestration team mailing list, you can sign up
here:
https://launchpad.net/~nova-orchestration
Cheers,
Sandy
Sent: Thursday, October 20, 2011 8:46 AM
To: nova-orchestrat...@lists.launchpad.net
Subject: [Nova-orchestration]
20 matches
Mail list logo
