Hi,
Below is my view, Mike and Jon are welcome to correct me if needed.
On 03/14/2012 06:27 AM, Todd Deshane wrote:
Looks like the Debian repos on Xen.org are out of date. I'm not sure
if the intention was to drop them once the packages got into SID or if
they would be staging/unstable
I have updated the wiki at:
http://wiki.xen.org/wiki/XCP_toolstack_on_a_Debian-based_distribution
:)
Thomas
On 03/13/2012 10:55 PM, Todd Deshane wrote:
On Mon, Mar 12, 2012 at 2:10 PM, Eduardo Nunes eduardo.ke...@gmail.com
wrote:
I read all the docs about it but i dont get it, what release
Hello all,
Can someone help me understand what options need to be in glance-api.conf
and what options can be left to glance-cache.conf , resp
glance-cache-paste.ini ?
Case in point: If I wanted to use the xattr driver, I need to specify
that in glance-api.conf -- specifying that in
Shep,
Those steps are great. I'll be running through them, the devstack and any
other info I've collated and update the bug I originally raised that caused
me the pain that tipped me over the edge (
https://bugs.launchpad.net/glance/+bug/953989)
Adam, the other bugs raised in the last day
Hi,
we are thinking to contribute to increase the types of notifications
(events) through the rabbit server. We are thinking to notify from each
Openstack component (nova, glance, quantum in the future ...)
We think that unify the code on the openstack-common stuff is a great idea.
We are
Florian,
The key point in the split between glance-api.conf, glance-registry.conf,
glance-cache.conf etc. is the glance application intended to consume that
config.
This follows directly from the naming:
bin/glance-api by default consumes glance-api.conf
bin/glance-registry by default
Eoghan,
Yes, it does make perfect sense. Kind thanks for the explanation.
However, what is still unclear is what config iteems that pertain to other
apps must still be present (ie. duplicated in) glance-api.conf (e.g.
image_cache_driver , etc )
Thanks again,
Florian
On Mar 14, 2012 10:45
Yes, it does make perfect sense. Kind thanks for the explanation.
However, what is still unclear is what config iteems that pertain to
other apps must still be present (ie. duplicated in) glance-api.conf
(e.g. image_cache_driver , etc )
This is probably something we should document more
To make the notifiers common, the QAL / RPC will also have to be made common.
The Glance code for notifications currently implements queue/rpc-implementation
specific notifiers, so this might not be a bad thing…
If there is an effort to move the RPC into openstack.common, then I would like
to
Hi,
I have signed the agreement but I'm not sure how to make my git review
command realize that. Right now I got:
$ git review
fatal: A Contributor Agreement must be completed before uploading:
http://wiki.openstack.org/HowToContribute
fatal: The remote end hung up unexpectedly
Thanks,
Hi, folks!
nova client couldn't delete images in error state, but it could delete
errored instances. I think we need this feature.
# nova volume-delete 3
ERROR: Invalid volume: Volume status must be available (HTTP 400)
--
Regards, Roman Sokolkov
___
On 03/14/2012 09:59 AM, Yun Mao wrote:
Hi,
I have signed the agreement but I'm not sure how to make my git review
command realize that. Right now I got:
$ git review
fatal: A Contributor Agreement must be completed before uploading:
http://wiki.openstack.org/HowToContribute
i'e installed the xcp with this notes,
http://wiki.xen.org/wiki/XAPI_on_Ubuntu
and instaled the compute, but it's now working with the xen, i've change
the flag of the hypervisor on the nova.conf.
what do i do now?
___
Mailing list:
On Wed, Mar 14, 2012 at 10:29 AM, Eduardo Nunes eduardo.ke...@gmail.com wrote:
i'e installed the xcp with this notes,
http://wiki.xen.org/wiki/XAPI_on_Ubuntu
and instaled the compute, but it's now working with the xen, i've change the
flag of the hypervisor on the nova.conf.
what do i do now?
On Mar 14, 2012, at 9:13 AM, Roman Sokolkov wrote:
nova client couldn't delete images in error state, but it could delete
errored instances. I think we need this feature.
# nova volume-delete 3
ERROR: Invalid volume: Volume status must be available (HTTP 400)
+1 to the feature request.
Those were great bugs too - sorry you hit them, but thanks to you and Jay for
reporting them in! We're working on them now!
-joe
On Mar 14, 2012, at 1:45 AM, Kevin Jackson wrote:
Shep,
Those steps are great. I'll be running through them, the devstack and any
other info I've collated and
Surprisingly nova-manage works very cool!
2012/3/14 Jason Hedden jhed...@mcs.anl.gov
On Mar 14, 2012, at 9:13 AM, Roman Sokolkov wrote:
nova client couldn't delete images in error state, but it could delete
errored instances. I think we need this feature.
# nova volume-delete 3
Hi Todd,
I did some work on the devstack port for xapi on Debian.
Unfortunately I have not yet pushed it back, as it is not completed. I was
trying to use devstack to run Openstack with Quantum on XCP.
I will get back at you as soon as it is done.
Eduardo, the devstack port linked by Todd
This is an annoying operational concern, so I have targeted it and proposed a
fix.
https://review.openstack.org/5342
Please verify that it works for you.
Vish
On Mar 14, 2012, at 9:03 AM, Jason Hedden wrote:
On Mar 14, 2012, at 9:13 AM, Roman Sokolkov wrote:
nova client couldn't delete
In case any one runs into this, there is a bug in the Precise upstart
package that causes a reboot after installing essex to result in a
kernel panic. I don't know exactly what in the openstack install process
triggers it but there is a PPA mentioned in comment #11 of this bug
ticket that
The image caching configuration is somewhat unique within Glance, as it is
needed by multiple wsgi apps. As you point out, that means you need to
duplicate your cache configuration in glance-api.conf and glance-cache.conf to
get everything to play well together. I'm going to update the docs to
Hi Shep and others -
A couple of questions to enhance my understanding while I walk through this
for the install doc.
Service Tenant - do you create just one service tenant to enclose all the
service users?
Glance Service User - do you create a Nova Service User and a Swift Service
User also?
On Mar 14, 2012, at 11:57 AM, Anne Gentle wrote:
Hi Shep and others -
A couple of questions to enhance my understanding while I walk through this for
the install doc.
Service Tenant - do you create just one service tenant to enclose all the
service users?
Glance Service User - do you create
Yeah, one service tenant, and then service accounts for each of nova, glance,
quantum, swift. I've got a review that's updating this detail in the keystone
docs right now (https://review.openstack.org/#change,5348)
The catalog can be either the template (in which case, you don't use commands,
We recently changed the MAC address assigned to guests so that they started
with 0xfe, in the hope of avoiding (theoretical?) issues with MAC addresses
changing on the bridge device as machines are shut down (because supposedly
the bridge grabs the lowest MAC address numerically):
On Wed, Mar 14, 2012 at 10:50:28AM -0700, Justin Santa Barbara wrote:
We recently changed the MAC address assigned to guests so that they started
with 0xfe, in the hope of avoiding (theoretical?) issues with MAC addresses
changing on the bridge device as machines are shut down (because
Hi Vish,
I have done some more testing on those two reviews on a clean devstack
install with this nova review :
https://review.openstack.org/5338
this keystone review :
https://review.openstack.org/5340
and a small modification to devstack to have S3_URL pointing to Swift
if we have it
On 03/14/2012 01:50 PM, Justin Santa Barbara wrote:
We recently changed the MAC address assigned to guests so that they started
with
0xfe, in the hope of avoiding (theoretical?) issues with MAC addresses
changing
on the bridge device as machines are shut down (because supposedly the bridge
I investigated this and it looks like there is some kind of odd race condition
causing the status to show up as available before the image is actually
available. This caused euca-deregister to get executed too quickly and the
upload of the image to glance failed.
I'm not quite sure how that
From what I understand, the SmokeStack integration tests are running on Ubuntu
11.10 (XenServer) and Fedora 16 (Libvirt), so as a practical matter those
platforms will be more battle-tested even if they aren't officially blessed as
supported platforms.
Take care,
Lorin
--
Lorin Hochstein
Lead
On 03/11/2012 02:31 AM, wangsuyi640 wrote:
Dear all:
The release of openstack on my server is D3. I tred to run 'qemu-kvm
-hda /root/free.img -m 512 -vga qxl -spice port=5930,disable-ticketing '
without openstack , it worked well.
However,I have tried to modify the
We are following a similar approach, as indicated by Brian here, in the
Linux-bridge plugin for Quantum. There is a dummy tap device created
with the requested MAC address, and is the first one to get added to the
bridge. Subsequently, the bridge's MAC address stays anchored to this
tap device's
Dear all,
After getting past some initial keystone issues on Essex E4 (Ubuntu 12.04
B1) I'm now having issues with communicating with nova using keystone.
I've a paste of my session here: http://paste.openstack.org/show/9413/
Essentially I've set up my keystone endpoints (which I'm pretty sure
Hi,
be sure that auth_strategy=keystone it in your nova.conf file and
keystone enable in /etc/nova/api-paste.ini (Not neccesarry this last step
with new conf file format, post-essex4)
Ghe Rivero
On Wed, Mar 14, 2012 at 9:24 PM, Kevin Jackson ke...@linuxservices.co.ukwrote:
Dear all,
After
Apologies if you receive this email twice, I sent the first one from the wrong
address.
Hello Everyone,
Last week during the release meeting it was mentioned that the VSA code is not
working properly and we should either fix it or remove it. I propose to remove
it for the following reasons:
Hello,
I see that quantum has come a long way since its diablo version. I was
wondering if quantum-essex works with nova/openstack essex version only or is
quantum-essex indepedent of nova/openstack versions/evolution.
Thanks,
-Vijay___
Mailing
On Wed, Mar 14, 2012 at 4:35 PM, Vijay vija...@yahoo.com wrote:
Hello,
I see that quantum has come a long way since its diablo version. I was
wondering if quantum-essex works with nova/openstack essex version only or
is quantum-essex indepedent of nova/openstack versions/evolution.
Hi
Related links:
https://bugs.launchpad.net/nova/+bug/954490
https://review.openstack.org/#change,5377
On Mar 14, 2012, at 6:54 PM, Vishvananda Ishaya wrote:
Apologies if you receive this email twice, I sent the first one from the
wrong address.
Hello Everyone,
Last week during the
Have you tinkered with devstack Its simplifies some of the issues
you raised for a dev guy.
debo
From: openstack-bounces+dedutta=cisco@lists.launchpad.net
[mailto:openstack-bounces+dedutta=cisco@lists.launchpad.net] On
Behalf Of Aniruddha Khadkikar
Sent: Wednesday, March 14,
On Thu, Mar 15, 2012 at 9:46 AM, Debo Dutta (dedutta) dedu...@cisco.com wrote:
Have you tinkered with devstack …. Its simplifies some of the issues you
raised for a dev guy.
No, I have not used Devstack as the purpose is to simulate a close to
production type POC and not a deployment on a
Then you might want to start with some of the chef cookbooks people use.
Ask Jay Pipes, he was planning to consolidate them!
debo
-Original Message-
From: Aniruddha Khadkikar [mailto:askhadki...@gmail.com]
Sent: Wednesday, March 14, 2012 9:37 PM
To: Debo Dutta (dedutta)
Cc:
Public bug reported:
It appears to work for CLI options but not when using config files.
Looking at the tests, this appears to be a known bug since the assertion
in test_conf_file_multistr_values_append has been commented out with a
FIXME.
** Affects: openstack-common
Importance: Undecided
Reviewed: https://review.openstack.org/5179
Committed:
http://github.com/openstack/openstack-common/commit/e8a5ae2e5aab6b649b57d03f8a03af689d7e6b6e
Submitter: Jenkins
Branch:master
commit e8a5ae2e5aab6b649b57d03f8a03af689d7e6b6e
Author: Jason Kölker ja...@koelker.net
Date: Fri Mar 9
Reviewed: https://review.openstack.org/5306
Committed:
http://github.com/openstack/openstack-common/commit/b2c59f50a8d449d619f52db318cff10211075c53
Submitter: Jenkins
Branch:master
commit b2c59f50a8d449d619f52db318cff10211075c53
Author: Joe Gordon j...@cloudscaling.com
Date: Tue Mar 13
44 matches
Mail list logo
