Hi Ewan,
Thanks *a lot* for your very accurate and long reply. That's going to
help me so much for working on the Nova + XCP packaging in Debian.
On 01/24/2012 06:19 AM, Ewan Mellor wrote:
I already started writing a README.xcp_and_openstack to document how to
do an Openstack + XCP setup.
On 01/24/2012 12:35 AM, Joshua Harlow wrote:
So some of the issues after doing a comparison might be the following:
For RHEL6 + EPEL a lot of the packages are there (yippe!).
Yes there has been lots of work in this area. See here for details:
On 01/17/2012 08:20 PM, Joshua Harlow wrote:
My goals were/are/(may continue to be, haha) the following:
1. Add in enough abstraction so that you can look at how each component is
installed/uninstalled/started/stopped by looking at a single file (maybe 2
files)
2. Have the ability to
Hello everyone,
Our weekly project release status meeting will take place at 21:00 UTC
this Tuesday in #openstack-meeting on IRC. PTLs, if you can't make it,
please name a substitute on [2].
Today is the *last* day before we cut Essex-3 milestone branches. Since
E3 serves as a feature freeze
Hello,
I've setup a single node configuration with keystone using the packages
from https://launchpad.net/~managedit/+archive/openstack.
I've managed to launch an instance, however when i run the commando nova
diagnostics server i get this:
REQ: curl -i http://127.0.0.1:5000/tokens -X POST -H
Hi All,
I installed OpenStack using devsatck script (http://devstack.org/) on
Ubuntu 11.10. Installation was successful but there is no /etc/nova/
directory and It looks like that devstack script doesn't install all
the nova services. Should I install them manually as described in the
getting
Oh, I had thought it didn't exist in Diablo.. My mistake!
Thanks,
Kiall
On Tue, Jan 24, 2012 at 5:46 PM, Brian Waldon brian.wal...@rackspace.comwrote:
The diagnostics command moved to a server action. We will need to update
novaclient to support this. I went ahead and filed a bug for it:
Actually the diagnostics command was not added in Essex, but it was converted
to a true extension. However it is part of the Admin API, which means for
Diablo you need to set the allow_admin_api flag on your nova-api node.
On Jan 24, 2012, at 9:41 AM, Kiall Mac Innes wrote:
Hi,
The
I've just verified this against my install, but since the diagnostics is
unsupported when using libvirt/kvm, it still errors out (but with a 500,
rather than 404)
Thanks,
Kiall
On Tue, Jan 24, 2012 at 5:56 PM, Brian Waldon brian.wal...@rackspace.comwrote:
Actually the diagnostics command was
Ok, I was using 6.1.
Is there any reason that it isn't available for 6.1 and 6.2 (technically?)
It would be nice to not have to distinguish (6.1 vs 6.2) in the new devstack v2.
My guess is the list I created then was using the 6.1 repo, which may not have
those pkgs (darn it).
When using Devstack the files are written to /opt/stack/component. So,
you can find nova.conf in /opt/stack/nova/bin/.
Regards.
On Tue, Jan 24, 2012 at 3:48 PM, Joe Smithian joe.smith...@gmail.comwrote:
Hi All,
I installed OpenStack using devsatck script (http://devstack.org/) on
Ubuntu
Hello everybody.
I am searching for some days but I can't figure out how to attach a vm to a
network?
I am using Quantum 2011.3 with OVS to create the network. And Diablo.
I am looking to something like:
$ nova boot --flavor 1 --image 2 *--nic net-id=* --key_name key
instance10
But in
There have been conversations about changing that. That nova should
use /etc/nova/nova.conf
Thoughts?
On Tue, Jan 24, 2012 at 10:40 AM, Jorge Luiz Correa corre...@gmail.com wrote:
When using Devstack the files are written to /opt/stack/component. So, you
can find nova.conf in
Hi Kiall,
Thanks for your reply, I was confused between DevStack and regular
installation! The first time I installed devStack using the stack.sh
script everything was fine and I was able to login to dashboard, but
it doesn't work anymore, I think after I changed the IP address of the
machine and
Thanks guys for the info.
Out of curiosity , If somebody wants to implement openstack in their
production environment which package repository should they consider?
github, ubuntu, managedit or (any) others?
Paras.
On Mon, Jan 23, 2012 at 5:17 PM, Debo Dutta (dedutta) dedu...@cisco.com wrote:
Hi Alisson,
The --nic option was only added to nova client in Essex, thus it will not
be available in Diablo code.
However, if you spin up a VM with no --nic options, the VM will actually
automatically get a NIC on each global network (i.e. no project is set)
and each project network (--project
Using the Dashboard GUI (on an openstack install on a single machine using
devstack with Quantum and OVS) and user Demo, I can create new networks by
using the button Networks under the Network section. A message says the
network was created and an ID is shown. However, I do not see anything
Hi,
Completely agreed that nova.conf should be moved to /etc/nova/nova.conf
If the DB needs to be re-created the nova-manage db sync command will fail at
least the nova.conf is in the /etc directory. So, if you are running devstack,
you have to manually copy the file to avoid the problem.
I'm seeing this type of result (400 errors) when I go through the
install manual I just proposed that uses the Managed IT packages... I
am running it in a VM on my Macbook. Would love to learn more. It
nearly always happens after I work at work, then work from home, even
if the IP address of the
If you have the Open vSwitch components installed in domain 0, then
there
are a few scripts that wrap around it to set up the isolation rules
used
in flat mode. These are in nova/plugins/xenapi/networking.
I believe you mean: plugins/xenserver/networking
Yes, those are the ones.
Hi Mohammed,
On Tue, Jan 24, 2012 at 11:51 AM, Mohammad Banikazemi m...@us.ibm.com wrote:
Using the Dashboard GUI (on an openstack install on a single machine
using devstack with Quantum and OVS) and user Demo, I can create new
networks by using the button Networks under the Network section.
In general, it is unfortunate that there is such a big difference in the
end result between deploying from source and from packages, even though
they are supposed to function the same. Ideally the process structure,
locations of configuration files, etc. could be the same. The location
of
It looks like some nova and keystone services are not running. So my
question is how to check the status and restart all services in
devStack?
I can't use commands like restart nova-api because they are not
installed. There should be other ways to start services in devStack.
Devstack is for
On 01/24/2012 06:39 PM, Joshua Harlow wrote:
Ok, I was using 6.1.
Is there any reason that it isn’t available for 6.1 and 6.2 (technically?)
Well it's not been tested on 6.1 currently.
One issue with 6.1 is the version of libvirt is too old I think.
cheers,
Pádraig.
If you're running diablo, you should just have to restart your nova-api nodes
with the allow_admin_api flag on. But as Kiall points out, 'diagnostics' is not
implemented for libvirt. Unfortunately, I don't know how to help you on that
front. Maybe somebody else has some pointers?
On Jan 24,
Yes, I understand.
But My problem is:
i) I create a network: # nova-manage network create --label=public
--fixed_range_v4=8.8.8.0/24
ii) Then I spin up a vm: # nova boot --flavor 1 --image 2 --key_name
key instance1
But this vm does NOT have a fixed_ip associated to its interface, so I
think
Ok dokie,
Let me see what I can do to get a 6.2 system. Thx.
On 1/24/12 1:53 PM, Pádraig Brady p...@draigbrady.com wrote:
On 01/24/2012 06:39 PM, Joshua Harlow wrote:
Ok, I was using 6.1.
Is there any reason that it isn't available for 6.1 and 6.2 (technically?)
Well it's not been tested on
Monitoring can be done through libvirt monitoring plugins. For example:
http://honk.sigxcpu.org/projects/libvirt/
Vish
On Jan 24, 2012, at 2:01 PM, Leander Bessa wrote:
How exactly do i install that particular extension and what can i use as an
alternative to monitor instances with KVM?
Hi Folks,
I'm trying to write some scripts to work with Swift containers, but I don't
actually know what the restrictions on container names are. Does anyone
know what the specification is, or where I can read up on it?
For example:
What are the length requirements for container names?
Hi,
On Tue, Jan 24, 2012 at 13:40, Jorge Luiz Correa corre...@gmail.com wrote:
When using Devstack the files are written to /opt/stack/component. So, you
can find nova.conf in /opt/stack/nova/bin/.
Is there a reason why a configuration file is installed in a bin/
directory (not following the
Per today's meeting, I am proposing the ZeroMQ RPC driver for a feature-freeze
exception.
I am making good progress on this blueprint, it adds a new optional module and
service without modifying any existing code or modules. I have been pushing to
complete this work by E3, so I am close to
FWIW, I'd love to see this land in E3...
d
On 24 Jan 2012 - 16:08, Eric Windisch wrote:
Per today's meeting, I am proposing the ZeroMQ RPC driver for a
feature-freeze exception.
I am making good progress on this blueprint, it adds a new optional
module and service without modifying any
Hi I'm curious and unfamiliar with the subject. What's the benefit of
0MQ vs Kombu? Thanks,
Yun
On Tue, Jan 24, 2012 at 7:08 PM, Eric Windisch e...@cloudscaling.com wrote:
Per today's meeting, I am proposing the ZeroMQ RPC driver for a
feature-freeze exception.
I am making good progress on
On Jan 24, 2012, at 5:22 PM, Matthew Wodrich wrote:
Hi Folks,
I'm trying to write some scripts to work with Swift containers, but I don't
actually know what the restrictions on container names are. Does anyone know
what the specification is, or where I can read up on it?
For example:
Under specific architectures, 0MQ can process millions of messages per
second vs. RabbitMQ's many thousands.
RabbitMQ is a messaging system; 0MQ is a messaging framework. There's a
pretty good write-up on some of the basic differences here:
http://www.zeromq.org/docs:welcome-from-amqp
Note
This is really just a dev choice.
In the newer devstack it can be in a different place (programmer determined).
I am making it typically be the following.
$ROOTDIR/$COMPONENT/app (for the git checked out code)
$ROOTDIR/$COMPONENT/config (for configs - unless overridden by the component
class)
I assume the messages will be delivered directly to the destination rather
than piling up on a queue server?
On Wed, Jan 25, 2012 at 10:49 AM, Duncan McGreggor dun...@dreamhost.comwrote:
Under specific architectures, 0MQ can process millions of messages per
second vs. RabbitMQ's many
You'll also find this info in the Object Storage API document, see
http://docs.openstack.org/api/openstack-object-storage/1.0/content/ch_object-storage-dev-api-storage.html
On Tue, Jan 24, 2012 at 7:27 PM, John Dickinson m...@not.mn wrote:
On Jan 24, 2012, at 5:22 PM, Matthew Wodrich wrote:
Where would u like all the configs to be.
I can attempt to make this better in the new devstack2.
Might as well get it right the second time around ;)
On 1/24/12 1:28 PM, David Kranz david.kr...@qrclab.com wrote:
In general, it is unfortunate that there is such a big difference in the
end
Sorry, I had originally sent only to Yun Mao. Sending to list.
---
Rather than attempt to answer this, I defer to the ZeroMQ guide. It should be
noted that the designers of AMPQ, iMatix, designed and build ZeroMQ. (RabbitMQ
and QUID implement AMQP)
On Tuesday, January 24, 2012 at 6:05 PM, Zhongyue Luo wrote:
I assume the messages will be delivered directly to the destination rather
than piling up on a queue server?
Although the blueprint doesn't specify this level of detail, the intention had
originally been to deliver a
41 matches
Mail list logo
