Hi Vish,
Thanks. I just have a weird thought. Based on the stack.sh logs I
understand that when I run stack.sh second time it simply spawns all the
services.
Ex: I saw the below in stack.sh log
' screen -S stack -p n-net -X stuff 'cd /opt/stack/nova &&
/opt/stack/nova/bin/nova-network
+ screen_it
In the spirit of essex-3 devstack v2 should be pretty functional (+- bugs, and
some missing pieces, haha).
It seems to run horizon, keystone, nova, glance (and clients), db, rabbitmq,
all correctly.
We are only missing the swift component (TBD - working on it) and minus the
networking config (
>> http://bogott.net/misc/osmpuppet.png
>>
>> That's what it looks like when you configure an instance using Open Stack
>> Manager, which is WikiMedia's VM management interface. My main priority for
>> adding puppet support to Nova is to facilitate the creation and control of a
>> GUI much like th
Why not just use
Cache-Control: no-cache
?
That way, intervening caches will do the right thing too...
Cheers,
On 21/01/2012, at 4:33 AM, Stephen Broeker wrote:
> The X-Newest header can be used by a GET Operation to ensure that all of the
> Storage Nodes (3 by default) are queried for the l
On Thu, Jan 26, 2012 at 8:56 PM, Andrew Bogott wrote:
> Andrew --
>
> Thanks for your comments. I'm going to start with a screenshot for
> context:
>
> http://bogott.net/misc/osmpuppet.png
>
> That's what it looks like when you configure an instance using Open Stack
> Manager, which is WikiMedia
Sorry to bring back a rather quiet thread from 3 days ago.
How fast do we need to queueing component to be? My observation from
Amazon EC2 us-east-1 is about 2 VMs provisioned per second on average.
Let's say there are 100 messages exchanged for the workload per second
per VM (which I believe is o
Hey Andrew,
Sorry for the slow response on this. There has been a lot to do for e-3. In
any case, here are my thoughts on the subject. I am really not convinced that
configuration management needs to be part of nova at all. This is stuff that
should be built on top of nova. We have a bit of
OpenStack Community Newsletter –January 27, 2012
HIGHLIGHTS
* OpenStack Bug Squashing Day Is Coming On Feb 2nd
http://www.openstack.org/blog/2012/01/the-first-openstack-bug-squashing-day-is-coming-on-feb-2nd/
and you can follow its evolution on http://wiki.openstack.org/bugstats
Great,
I was going to ask for a way to disable that! I've got the update check
patched out in my packaging already ;)
I'll let you know how I get on with Ubuntu..
Thanks,
Kiall
On Fri, Jan 27, 2012 at 9:07 PM, Monty Taylor wrote:
>
>
> On 01/27/2012 03:49 PM, Kiall Mac Innes wrote:
> > Hey M
On 01/27/2012 03:49 PM, Kiall Mac Innes wrote:
> Hey Monty,
>
> Packaging sources are
> at http://review.managedit.ie/p/openstack/packaging/git-review.git if
> they are of any interest.
>
> Otherwise I'll just keep my eye out for updates and keep the PPA
> updated.. I might even use this simple
Hey Monty,
Packaging sources are at
http://review.managedit.ie/p/openstack/packaging/git-review.git if they are
of any interest.
Otherwise I'll just keep my eye out for updates and keep the PPA updated..
I might even use this simple repo as a learning experience for getting
packages into Ubuntu i
On 01/27/2012 08:48 AM, Kiall Mac Innes wrote:
> Hiya,
>
> For those of you who prefer to avoid "pip" installing as much as
> possible in favor of native packages, I've packaged up the git-review
> tool for Ubuntu (Just oneiric for now, if there is interest I'll package
> for lucid too).
>
> PP
On 01/27/2012 04:59 AM, Thierry Carrez wrote:
> Robbie Williamson wrote:
>> http://jenkins.qa.ubuntu.com/view/Precise%20OpenStack%20Testing/
>
> Great work!
>
> Would be cool to syndicate those Jenkins instances into a general health
> dashboard that we could use to get at a glance the health o
There is a hack on top of devstack for you to restart those services
easily across reboot.
https://blueprints.launchpad.net/devstack/+spec/upstart
Yun
On Fri, Jan 27, 2012 at 1:18 AM, nandakumar raghavan
wrote:
> Hi,
>
> I have similar query. I had installed open stack using devstack on a fresh
On 1/27/12 4:49 AM, Belmiro Moreira wrote:
The idea of integrating nova with "configuration management tools"
(puppet, chef, ...) is very interesting. But in my opinion we
shouldn't have a specific implementation to a single tool or a small
set of tools.
Yep, I'm increasingly convinced of this.
The documentation seems to say that the user "system_tester" does not have
auto permissions on its account.
The headers X-Container-Read and/or X-Container-Write have to be set.
The question is, how can a reseller_admin user see other accounts?
A .reseller_admin account can touch all accounts.
A .a
devstack provides a file to source called openrc with all the necessary
variables. You don't need to create your own novarc file, just source openrc
instead.
Vish
On Jan 27, 2012, at 9:51 AM, Joe Smithian wrote:
> Hi Christian,
>
> Thanks for your suggestion. I logged in as stack and tried i
Hi all -
I thought you'd want to know these three things about docs going on lately.
1. The new installation guide for Diablo that includes Compute,
Identity, Image, and the Dashboard is now published. Find it
here:http://docs.openstack.org/diablo/openstack-compute/install/content/.
2. The PDF li
But on storage servers, what's kind of error it can be??
I followed the link below to configure them
http://swift.openstack.org/howto_installmultinode.html
Best regards
Khaled
From: chmo...@openstack.org
Date: Fri, 27 Jan 2012 10:05:01 -0800
Subject: Re: [Openstack] Creating account and user in
Well your proxy configuration looks correct, the probably may lie somewhere
else on the storage servers.
Chmouel.
On Fri, Jan 27, 2012 at 10:01 AM, Khaled Ben Bahri
wrote:
> Hi Chmouel
>
> Yes of course,
> I have it there
> this is th file proxy-server.conf
>
> _
Hi Chmouel
Yes of course,
I have it there
this is th file proxy-server.conf
__
[DEFAULT]
cert_file = /etc/swift/cert.crt
key_file = /etc/swift/cert.key
bind_ip = 157.159.103.228
bind_port = 8080
workers = 8
user = swift
[pipeline:main
It's not really a Glance thing, but a Swift thing, though. You'd have
to talk to the Swift guys about removing Rackspace-specific stuff from
the Swift client class, which is what Glance needs the configuration
option for...
-jay
On Wed, Jan 25, 2012 at 6:39 PM, Joshua Harlow wrote:
> Thx Jay,
>
Hi Christian,
Thanks for your suggestion. I logged in as stack and tried it again;
it failed with the same error:
stack@k:/home/localadmin/creds$ source novarc
stack@k:/home/localadmin/creds$ euca-describe-availability-zones
Warning: failed to parse error message from AWS: :1:0: syntax error
None
I'm using the swift utility
swift -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U system:root -K testpass
with tis first user it works perfectly
but with the second user
I got that error
Date: Fri, 27 Jan 2012 09:04:26 -0800
Subject: Re: [Openstack] Creating account and user in swift
From: sbro
did you have account_autocreate in there ? for example that's my config
with tempauth :
[app:proxy-server]
use = egg:swift#proxy
allow_account_management = true
account_autocreate = true
Khaled Ben Bahri writes:
> Hi Adrian,
>
> When i add user in the same account of the admin,
> I got this e
Are you using the "swift" utility or are you using REST?
How are you performing the GET Authorization?
On Fri, Jan 27, 2012 at 9:00 AM, Khaled Ben Bahri wrote:
> Hi,
>
> I added an entry like this one but it doesn't work
> I got this error
> Account HEAD failed: https://x.x.x.x:8080/v1/AUTH_syst
Hi,
I added an entry like this one but it doesn't work
I got this error
Account HEAD failed: https://x.x.x.x:8080/v1/AUTH_system 403 Forbidden
Date: Fri, 27 Jan 2012 08:56:59 -0800
Subject: Re: [Openstack] Creating account and user in swift
From: sbroe...@internap.com
To: khaled-...@hotmail.com
Try adding an entry like the following:
user_test_tester3 = testing3
On Fri, Jan 27, 2012 at 2:44 AM, Khaled Ben Bahri wrote:
> Hi folks,
>
> I installed swift with "tempauth" authentication subsystem
> To create a user I have to write a new line in the proxy-server.conf on
> the section
Hi,
I've lunched an instance using OpenStack dashboard but cann't start a
VNC session. It displays this error message:
Error: Unable to get vnc console for instance
40c098b8-1c92-4b16-9c33-964ef6c5b950: The server could not comply with
the request since it is either malformed or otherwise incorre
Hi joe.
> euca-describe-availability-zones but it failed as you can see below.
Try using the "stack" user. This is working fine for me one a fresh
devstack installation:
cstack@devstack001:~$ cd devstack/
stack@devstack001:~/devstack$ source openrc
stack@devstack001:~/devstack$ euca-describe-av
I've modified novarc file as suggested in the OpenStack Compute
Starter Guide. You can see I've added ":proj" to EC2_ACCESS_KEY and
EC2_SECRET_KEY
NOVARC=$(readlink -f "${BASH_SOURCE:-${0}}" 2>/dev/null) ||
NOVARC=$(python -c 'import os,sys; print
os.path.abspath(os.path.realpath(sys.argv[1]))
Hi All,
I've installed devstack using the stack.sh script on Ubuntu 11.10 - 64 bit.
I've started all the service and tried
euca-describe-availability-zones but it failed as you can see below.
localadmin@k:/opt/stack/devstack$ source /home/localadmin/creds/novarc
localadmin@k:/opt/stack/devstack
I'll be taking the existing Zones code out of API and Distributed Scheduler.
The new Zones infrastructure is an optional component.
-S
From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net
[openstack-bounces+sandy.walsh=rackspace@lists
Hi Adrian,
When i add user in the same account of the admin,
I got this error when i tried to test the second user:
Account HEAD failed: https://127.0.0.1:8080/v1/AUTH_system 403 Forbidden
Khaled
From: adrian_f_sm...@dell.com
To: khaled-...@hotmail.com
CC: openstack@lists.launchpad.net
Date: Fri
Just as Nova enters feature freeze, it sounds like a good moment to
consider removing deprecated, known-buggy-and-unmaintained or useless
feature code from the Essex tree.
Here are my suggestions for removal:
- Ajaxterm (unmaintained, security issues, replaced by VNC console)
- Hyper-V support (k
Here's the documentation I was referring to,
https://github.com/openstack/swift/blob/master/etc/proxy-server.conf-sample#L79
It states,
# There are special groups of:
# .reseller_admin = can do anything to any account for this auth
# .admin = can do anything within the account
# If neither of
Hey Everyone,
As you may be well aware, the existing Keystone implementation has been a
source of some consternation for deployers and various members of our
community. In response to this, over the last few months, there has been an
effort between our team and members of the community to re-a
Hi,
.admin is not indicated to mention that the user is an admin for swift??
I think that we can create users who are not from the admin group
I changed that line to mention the name of account at the end of line but it
still the same error
user_newaccount_user1 = passuser1 https://PROXY_IP:808
Hiya,
For those of you who prefer to avoid "pip" installing as much as possible
in favor of native packages, I've packaged up the git-review tool for
Ubuntu (Just oneiric for now, if there is interest I'll package for lucid
too).
PPA @ https://launchpad.net/~managedit/+archive/git-review
$ apt-a
Hi
Now the Qautum E3 whether work with Horizon E3?
whether I can manage the Qauntum in Horizon Dashboard?
On Fri, Jan 27, 2012 at 7:57 PM, Leandro Reox wrote:
> Excellent job guys ! Well definitely try it next week, the last release
> worked out pretty good so far for us.
>
> Keep up the good
Hi Andrew and others,
first of all sorry for my previous email. (seems I sent a unfinished email)
The idea of integrating nova with "configuration management tools"
(puppet, chef, ...) is very interesting. But in my opinion we
shouldn't have a specific implementation to a single tool or a small
se
Excellent job guys ! Well definitely try it next week, the last release
worked out pretty good so far for us.
Keep up the good work!
Cheers
Lean
On Thu, Jan 26, 2012 at 8:36 PM, Dan Wendlandt wrote:
> Congrats to the Quantum team!
>
> The latest + greatest version of Quantum was release this
I'm guessing the problem is that the user isn't a member of the ".admin" group.
This is a requirement to perform operations on the root URL.
To include the user in this group add .admin like this,
user_newaccount_user1 = passuser1 .swift .admin
https://PROXY_IP:8080/v1/AUTH_system
Adrian
From
Hi folks,
I installed swift with "tempauth" authentication subsystem
To create a user I have to write a new line in the proxy-server.conf on the
section [filter:temauth] like this :
user_system_root = testpass .admin https://PROXY_IP:8080/v1/AUTH_system
as i inderstood, the format is actually
Robbie Williamson wrote:
> http://jenkins.qa.ubuntu.com/view/Precise%20OpenStack%20Testing/
Great work!
Would be cool to syndicate those Jenkins instances into a general health
dashboard that we could use to get at a glance the health of openstack
downstreams...
Would there be a feature in Jenki
Alejandro Comisario wrote:
> PS: Is the plan to commit the new Zones code into Milestone 3 ? that
> would be fantastic news !
Essex-3 being out, that sounds unlikely. And Essex being feature-frozen,
it also sounds unlikely that such a far-reaching change would land in Essex.
New features and arch
Hi Nati
On 26/01/12 20:49, Nachi Ueno wrote:
Can I ask some questions?
1. Is there any document or opensource of your juju-based ci-deployment?
There will be :-); all of the bits and pieces are under
http://launchpad.net/~openstack-ubuntu-testing code branches but we will
be pulling togeth
47 matches
Mail list logo
