Your config file looks fine Sudhakar (included below, sent offline).
Have you checked your syslog (/var/log/syslog) for errors?
[DEFAULT]
#cert_file = /etc/swift/cert.crt
#key_file = /etc/swift/cert.key
bind_port = 8080
bind_ip = 10.30.91.80
workers = 8
user = swift
[pipeline:main]
pipeline =
andi abes wrote:
Essex-4 is almost here, and once it comes out, you’d probably want to
install it.
Good idea ! Don't forget to feed back the bugs you encounter, so that we
can fix them in the release candidates we'll have up to final release of
Essex (2012.1) planned on April 5.
Cheers,
--
attached the log file.
i stop all firewall services.
please let me know what can be done
regards
Sudhakar
On Thu, Feb 23, 2012 at 2:08 PM, Adrian Smith adr...@17od.com wrote:
Your config file looks fine Sudhakar (included below, sent offline).
Have you checked your syslog (/var/log/syslog)
We have recently updated the XenServer/XCP code so the storage is configurable,
if you want a pattern to copy.
https://github.com/citrix-openstack/nova/blob/everett/nova/virt/xenapi/vm_utils.py
If I remember correctly, they assumed standalone ESX hosts with local storage,
so never got around to
On Thu, Feb 23, 2012 at 1:10 AM, andi abes andi.a...@gmail.com wrote:
If you're going to be hacking at the same time, let's connect!
Excellent timing, we plan Fedora OpenStack Test Day on the same day:
https://fedoraproject.org/wiki/Test_Day:2012-03-08_OpenStack_Test_Day
Cheers,
Alan
OK - I'll put a description into lanchpad along with our notes on how we're
proposing to fix this on our Diablo branch (as there is a performance related
change in here as well)
As with the previous performance change it will take us some time to get an
Essex compatible fix - but if I provide
On Thu, Feb 23, 2012 at 9:53 AM, Sudhakar Maiya sma...@gmail.com wrote:
attached the log file.
packages/swauth/middleware.py, line 510, in handle_prep#012(path,
resp.status))#012Exception: Could not create the main auth account:
/v1/AUTH_.auth 503 Internal Server Error#012:
Have you
what is the permission do i need to give
i have given like this
/dev/sdb6 5.0G 33M 5.0G 1% /srv/node/sdb6
/dev/sdb7 5.0G 33M 5.0G 1% /srv/node/sdb7
/dev/sdb8 5.0G 33M 5.0G 1% /srv/node/sdb8
/dev/sdb9 5.0G 33M 5.0G 1%
Try adding the following line to the [app:proxy-server] section of
your proxy config file, i.e. just below allow_account_management =
true
account_autocreate = true
On 23 February 2012 09:53, Sudhakar Maiya sma...@gmail.com wrote:
attached the log file.
i stop all firewall services.
please
No luck :(
On Thu, Feb 23, 2012 at 4:14 PM, Adrian Smith adrian_f_sm...@dell.comwrote:
Try adding the following line to the [app:proxy-server] section of
your proxy config file, i.e. just below allow_account_management =
true
account_autocreate = true
On 23 February 2012 09:53, Sudhakar
2012/2/22 McNally, Dave (HP Cloud Services) dave.mcna...@hp.com:
Currently I’m trying to track how a refresh of the security groups is
handled (upon creation or deletion of a vm). Following through the
code I get to ‘do_refresh_security_group_rules’ in
libvirt/firewall.py. Up to this point the
Also, on http://nova.openstack.org/vmwareapi_readme.html it mentions
nova.network.vmwareapi_net for vlan networking support, but it doesn't
appear to actually exist in the code - am I missing something?
You are correct, vmwareapi_net.py is removed sometime back when hypervisor
driver api
This week, we switched Smokestack over to use a Fedora/puppet configuration
that Derek Higgins and I have been working on. You can see those results in
gerrit now. It seems very stable and supports running Nova smoke tests and
Torpedo.
We plan on focussing our trunk chasing on
Hi Soren,
Thanks for the insight, a few questions / comments:
1 deal with the situation where a refresh call to one of the compute
nodes got lost. If that happened, at least it would all get sorted
out on the next refresh.
Can see the advantage of this, but on an active system this can
I've put my name on the ballot for Nova PTL, and I'd like to explain
what I expect to do (my platform, if you will).
Nova is facing many separate, but related problems.
* Nova is too big.
Very few (if any) core developers are comfortable reviewing every
part of the code base. In itself,
Hi all,
My co-worker built swift e3 environment (thank you Eguchi-san), so I checked
my patch and fix it. Then, I checked the last s3_token.py and swift3.py. I found
two problems.
a) swift3 sets HTTP_X_AUTH_TOKEN (= X-Auth-Token?) in constructors
of ServiceController, BucketController and
Hi all,
I'd like to understand how things go with ephemeral and persistant volumes.
For instance, say that my gold images are stored in a Swift storage
network, connected to Glance.
When I ask Nova to boot the VM,
- will the disk image stay in Swift storage?
- will the physical compute node
On Thu, Feb 23, 2012 at 6:06 AM, Dan Prince dpri...@redhat.com wrote:
This week, we switched Smokestack over to use a Fedora/puppet
configuration that Derek Higgins and I have been working on.
that is great news
You can see those results in gerrit now. It seems very stable and supports
On Thu, Feb 23, 2012 at 9:17 AM, Soren Hansen so...@linux2go.dk wrote:
I've put my name on the ballot for Nova PTL, and I'd like to explain
what I expect to do (my platform, if you will).
Nova is facing many separate, but related problems.
* Nova is too big.
Very few (if any) core
One important (and apparently often overlooked) part of your email is this:
*How to register to vote for Project Policy Board *
Any registered member of the OpenStack Launchpad group is eligible to
vote for the Project Policy Board. If you want to vote you need to
register to Launchpad and
On Thu, 2012-02-23 at 18:07 +0100, Thierry Carrez wrote:
One important (and apparently often overlooked) part of your email is this:
Indeed, thank you Thierry.
Let me try to be even clearer about this:
**
REGISTER HERE OR YOU WON'T VOTE
I'd love to hear more specifics about what needs more focus. These
issues are large and have been the major focus of the core team for a
while.
* Nova is too big.
Very few (if any) core developers are comfortable reviewing every
part of the code base. In itself, this isn't necessarily a
The OpenStack community is electing its Project Technical Leads and two
members of the Project Policy Board. Details are at
http://www.openstack.org/blog/2012/02/openstack-governance-elections-spring-2012/.
On February 26 the nominations will close and the voting process will start on
February
Run 'euca-describe-images' it should tell you what your missing in your
environment, or perhaps the error. ( It looks like you have all the
environment variables )
The euca-describe-images needs the following
EC2_SECRET_KEY
EC2_ACCESS_KEY
EC2_URL
On a side note, uec-publish-tarball didn't work
On Thu, 23 Feb 2012 10:09:07 +0530
Sudhakar Maiya sma...@gmail.com wrote:
please check and let me know what needs to be done
You have to decide if you run with SSL or without. These two clauses
obviously contradict to each other:
[DEFAULT]
#cert_file = /etc/swift/cert.crt
#key_file =
Hello all,
During the last few days I've been struggling to get Swift to use Keystone
middleware. Problem is that even if Keystone works fine when trying to
access the Swift configured with Keystone middleware I keep getting 401s,
no matter how I try i.e. which Swift url I try to access
Hi Derrick,
Thanks a lot for your answer!
Well, the euca-describe-images command gave me the following output:
root@nova-controller:~# euca-describe-availability-zones verbose
Warning: failed to parse error message from AWS: unknown:1:0: syntax error
BotoServerError: 500 Internal
2012/2/23 Duncan McGreggor dun...@dreamhost.com:
Soren, if elected, by what processes/policies etc. would you
accomplish these goals?
Well, there are limits to what a PTL really can do :)
However, in practical terms there are a number of things I'd like us to
do:
* I'd like us to look at the
OK.
Reading through the swiftkeystone2 (module that I'm using to support v2
authentication in swift's proxy configuration) source and documentation, I've
figured out the necessary roles that need to be applied to user's accounts and
ACLs to project containers to allow all combinations of
I'm setting up Swift storage for an internal project. For the project's use of
Swift, I want all members of the project to be able to see what's stored in
Swift. Applying suitable ACLs, it's possible for user's to see the contents of
the projects container. However, is there any way to allow
hi,
st/swift worked well.
But how curl works when swift is configured with keystone.
With non keystone,I run this to get the token
curl -v -H 'X-Storage-User: admin:admin' -H 'X-Storage-Pass: admin'
http:// 127.0.0.1:8080/auth/v1.0
Now I have keystone configured at
It all depends on the auth system you are using.
Below is for swauth and tempauth:
Are the users using the same shared storage? If so, set them up as .admin users
with the same storage endpoint. If they are not using the same shared storage,
then you may be stuck. The ACL support in swauth and
On Thu, Feb 23, 2012 at 10:25 PM, John Dickinson m...@not.mn wrote:
It all depends on the auth system you are using.
This is about the same for keystone but to be a .admin like in
tempauth or swauth for keystone middleware you need to have one of the
role specified in the configuration variable
On Thu, Feb 23, 2012 at 11:23 PM, Paras pradhan pradhanpa...@gmail.com wrote:
Now I have keystone configured at http://192.168.122.14:5000/v2.0 how
to use curl in this case to get a token?
Example from devstack:
TOKEN=`curl -s -d {\auth\:{\passwordCredentials\:
{\username\: \$ADMIN_USER\,
2012/2/23 Day, Phil philip@hp.com:
1 deal with the situation where a refresh call to one of the compute
nodes got lost. If that happened, at least it would all get sorted
out on the next refresh.
Can see the advantage of this, but on an active system this can be
quite an overhead
On Thu, Feb 23, 2012 at 10:57 PM, Alan Pevec ape...@gmail.com wrote:
On Thu, Feb 23, 2012 at 11:23 PM, Paras pradhan pradhanpa...@gmail.com
wrote:
Now I have keystone configured at http://192.168.122.14:5000/v2.0 how
to use curl in this case to get a token?
Example from devstack:
By the
I'm trying to use OpenStack in what I think to be the typical
non-public-cloud deployment, and my experience is not what it
could/should be. I'm hoping someone can point me to the right way,
or we can figure out what needs to change.
My wishlist:
* I want my instances to be on my network e.g.
I'd assume FlatDHCPManager works much like FlatManager, but maybe I'm wrong. I
use FlatManager and I always end up having to modify the fixed_ips table
manually after running nova-manage because I think I'm trying to do something
similar as you. I have a /23... and I want to give nova a /25
Thanks for chipping in.
I have contributed a patch (which has merged) which should allow you
to stop editing the SQL: https://review.openstack.org/#change,3816
With that, you should be able to pass the full range, with an
additional argument specifying the subset that nova controls:
On Feb 23, 2012, at 3:55 PM, Justin Santa Barbara wrote:
Thanks for chipping in.
I have contributed a patch (which has merged) which should allow you
to stop editing the SQL: https://review.openstack.org/#change,3816
With that, you should be able to pass the full range, with an
Sorry, I should have mentioned my setup. I'm using Keystone from the managedit
repository combined with a swift keystone plugin to allow the proxy to use
version 2 authentication.
Ross
(finger tapped on my iPhone)
On Feb 23, 2012, at 4:38 PM, Chmouel Boudjnah chmo...@chmouel.com wrote:
On
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
If you're going to go the cloud-init route... you wouldn't need DHCP, right?
There should be iptables rules to allow you to talk to the metadata service
over 169.254.* (And linux should give you a default link-local address that
allows you to talk to the MD service magically)
Do you
On Feb 23, 2012, at 5:42 PM, Justin Santa Barbara wrote:
If you're going to go the cloud-init route... you wouldn't need DHCP, right?
There should be iptables rules to allow you to talk to the metadata
service over 169.254.* (And linux should give you a default link-local
address that
Current way makes it difficult to see which openstack packages are
installed in a single list, and find what's lacking...
--
-Alexey Eromenko Technologov
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
45 matches
Mail list logo
