We have a prototype of similar capabilities targeting Nova services, using
ZooKeeper (heartbeat/membership, leader election, etc -- will share with
the community soon). Would be interesting to compare the two approaches.
Regards,
Alex
From: Martin Gerhard Loschwitz
Hello everyone,
The last 2012.1 (Essex) release candidates for Keystone, Horizon and
Nova are finally out ! Please check out:
https://launchpad.net/keystone/essex/essex-rc2
https://launchpad.net/horizon/essex/essex-rc2
https://launchpad.net/nova/essex/essex-rc3
Together with Glance 2012.1 RC3
Thanks to all for your feedback it has been helpfull !
On 04/03/2012 06:42 PM, Dolph Mathews wrote:
See `keystone help role-list`.
Great, makes more sense now !
On 04/04/2012 06:42 AM, Chmouel Boudjnah wrote:
You are in the group Admin and your operator_roles is admin (lowercase).
That was
Cheers Chmouel. I'll get on it and do some testing.
Kev
On 2 April 2012 23:35, Chmouel Boudjnah chmo...@chmouel.com wrote:
There is a review on the go here:
https://review.openstack.org/#change,6088
which should address swift-dispertion to be able to connect to auth
version 2.0 servers.
Hi all,
I have a two node Essex setup: One node is running all services
including -compute, the other node is only running nova-compute and
-network. When I launch an instance on the first node, everything is
fine but when I use the second (compute-only) node the instance gets no
ip address.
+1 on the Ubuntu 12.04 Precise and Essex.
Whilst there are other methods and OS of choice, given you've been using
11.10 - 12.04 is the natural home for it.
The betas of Precise are rock-solid and can vouch for the Ubuntu packaging
following quite quickly behind the devs. I highly recommend this
Hi everyone,
According to the statement of this article from Gartner group
http://blogs.gartner.com/lydia_leong/2012/04/03/citrix-cloudstack-openstack-and-the-war-for-open-source-clouds/
Openstack is a
highly immature platform.
But why? What's make Openstack so immature?
Any comments on that?
I had a problem like this when the umask was locked down. Setting the umask
to 022 in the init script for nova-compute solved my problem.
I'm running from devstack setup - so I don't have an init-script. All the
processes run in a screen session.
Here is what I did :
1. Stopped nova-compute
Immaturity of a platform is something you can easily fix paying the right
fee to your favorite analyst firm.
Seriously, Openstack is an open platform and an open community. This means
problems and issues are open to discuss to everyone. Propietary platforms
issues are rarely disclosed, and they
Ø Check if not only root can write on the nfs share (specially libvirt user).
It doesn’t look like permissions issue to me. Just to be doubly sure, I
“touched” a file, in that folder, edited and deleted the file. All operations
worked w/o error.
As I have listed below, several files got
Please have a look at my experience to see if it can help.Thanks-openstack-bounces+gongysh=cn.ibm@lists.launchpad.net wrote: -To: Razique Mahroua razique.mahr...@gmail.comFrom: Yong Sheng Gong/China/IBM@IBMCNSent by: openstack-bounces+gongysh=cn.ibm@lists.launchpad.netDate:
All,
On the link given below vish asked if I could “chown” the files in that folder
– turns out I couldn’t.
I’ve answered his query on the link below – but repeating the updates here for
larger audience (Unfortunately, I have revived a question that is marked as
“solved” – so not many people
Are you sure your libvirtd will start /usr/bin/kvm with libvirtd group?In default, the /usr/bin/kvm is running with libvirt-qemu like user (that depends on how it is built). you can try to check it by running "ps -ef" to see the effective user and group id after starting a VM in your
Hello Thierry,
Do you know if exists some page that have information about diablo bugs
that was fixed on essex?]
Thanks
Em 4 de abril de 2012 04:44, Thierry Carrez thie...@openstack.orgescreveu:
Hello everyone,
The last 2012.1 (Essex) release candidates for Keystone, Horizon and
Nova are
Eoghan Glynn wrote:
- how is the mapping between project and quota-class established?
I was expecting a project_quota_class_association table or
some-such in the nova DB. Is this association maintained by
keystone instead?
- is the quota_class attribute currently
It depends on what you expect OpenStack to do for you. If you want
pre-packaged, click-to-install software, it is not there, yet. But if
you want to be able to influence the future of the project you want to
bet your business on, you have a much higher chance of doing that with
OpenStack than with
I believe this Openstack is a highly immature platform. is referring
more to nova than swift. The simple reason for that is nova is more
focused on dev than ops but that is changing.In mature projects
the questions like How do I run this reliably every day? and How
can I safely upgrade from
I was able to resolve the problem – Thanks to hint Vish provided and suggestion
from Rohit (CC’ed)
Turns out there is some problem with nfs v4 – So we mounted the share using nfs
version 3 (mount –o vers=3)
Now we could “chown” the files in nfs folder, and the instance creation also
worked !!!
Guilherme Souza wrote:
Do you know if exists some page that have information about diablo bugs
that was fixed on essex?]
Those are listed in the milestone pages, and should move on the final
release page once released.
In the mean time, the simpler is probably to look at:
Hi,
I have tried this but still doesn't work. Here is my interfaces config of DomU:
auto eth0:1iface eth0:1 inet staticaddress 192.168.110.1netmask
255.255.255.0broadcast 192.168.120.255gateway 192.168.110.1
auto eth0:2iface eth0:2 inet staticaddress
Everyone,
As we get ready to release Essex, I should move all Essex blueprints and
bugs (for Nova, Glance, Horizon and Keystone) to target the release
milestone, in an effort to present all features and bugs fixed on that
release a single page, like:
https://launchpad.net/nova/diablo/2011.3
For
The "immaturity" being exposed here has nothing to do with neither stability nor bugs - in fact the angle is more about an ease of deployment.Such statements are not new, and well known from "enterprises" point of view.I remember same articles about Linux, few years back about Zimbra, few months
On 04/04/2012 09:06 AM, Thierry Carrez wrote:
Everyone,
As we get ready to release Essex, I should move all Essex blueprints and
bugs (for Nova, Glance, Horizon and Keystone) to target the release
milestone, in an effort to present all features and bugs fixed on that
release a single page,
H. While ease of deployment is definitely an area of future strength for
OS, the gap is closing rapidly and the reality for the enterprise is that
initial, comparable (apples to apples) VMWare installations all come with an
initial professional services engagement anyway.
Having just
On Wed, Apr 4, 2012 at 8:14 AM, Razique Mahroua
razique.mahr...@gmail.comwrote:
The immaturity being exposed here has nothing to do with neither
stability nor bugs - in fact the angle is more about an ease of deployment.
Such statements are not new, and well known from enterprises point of
On Tue, Apr 3, 2012 at 2:21 PM, Adam Gandelman ad...@canonical.com wrote:
On 04/03/2012 08:20 AM, Lillie Ross-CDSR11 wrote:
My question is, should I base our new installation directly off the Essex
branch in the git repository, or use the packages that will be deployed as
part of the
Hi,
I just install the current source code of nova, glance and python-novaclient
on a CentOS 6.2 node.
Running command: #nova-manage db sync
Gives me the following error message:
Command failed, please check log for more info
2012-04-04 16:40:57 CRITICAL nova [-] cannot import
On Tue, Apr 3, 2012 at 10:39 PM, Brian Waldon
brian.wal...@rackspace.com wrote:
to be a drop-in replacement for the existing client that lives in Glance,
but a complete rewrite with a shiny new interface that maintains
feature-parity.
Coolness! I've added it to the command mapping in
Very cool guys!
We'll be reworking the Quantum client in a similar alignment effort during
Folsom.
One question to that end: is there any effort to get much of the code that
will be common across all OpenStack python-*client projects into something
like openstack-common (or an
Lucian -
Could you also paste your iptables nat rules to the question?
Usually, when I get into a funky network state like you are in, I bust out
tcpdump and map out exactly how packets are getting moved from interface to
interface. That usually gets to the problem quickly.
A
On Wed, Apr 4,
On 04/04/2012 11:36 AM, Mauch, Viktor (SCC) wrote:
Hi,
I just install the current source code of nova, glance and
python-novaclient on a CentOS 6.2 node.
Running command: #nova-manage db sync
Gives me the following error message:
Command failed, please check log for more info
Am 04.04.2012 18:29, schrieb Russell Bryant:
On 04/04/2012 11:36 AM, Mauch, Viktor (SCC) wrote:
Hi,
I just install the current source code of nova, glance and
python-novaclient on a CentOS 6.2 node.
Running command: #nova-manage db sync
Gives me the following error message:
Command
Anthony,
I added my iptables rules in the launchpad question
https://answers.launchpad.net/nova/+question/192153
And I'll try the tcpdump, thanks.
Lucian Thomaz
Date: Wed, 4 Apr 2012 09:25:43 -0700
Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
From:
On Apr 3, 2012, at 5:49 PM, Michael March wrote:
I accidentally posted this on openstack-operat...@lists.openstack.org..
-- Forwarded message --
Everyone,
After googlin' around I can not find any docs on how to setup OpenStack with
ESXi as a hypervisor.
This
I think it was because it was not linked from any of the other rst files. Which
table of contents should it be listed in?
Doug
On Apr 4, 2012, at 1:41 PM, Lorin Hochstein lo...@nimbisservices.com wrote:
On Apr 3, 2012, at 5:49 PM, Michael March wrote:
I accidentally posted this on
On 04/04/2012 01:21 PM, Viktor Mauch wrote:
Am 04.04.2012 18:29, schrieb Russell Bryant:
On 04/04/2012 11:36 AM, Mauch, Viktor (SCC) wrote:
Hi,
I just install the current source code of nova, glance and
python-novaclient on a CentOS 6.2 node.
Running command: #nova-manage db sync
Gives
Doug:
I'm not sure. I'll port these to compute admin docs so it shows up in the
OpenStack Compute Admin guide at docs.openstack.org.
Mike, in the meantime, you can view this page by going to:
https://github.com/openstack/nova/blob/master/doc/source/vmwareapi_readme.rst
The missing block
Thanks everyone,
BTW, I was able to pull up a Google cache version of the document this
morning too.
Is this one page the extent of the vSphere docs?
On Wed, Apr 4, 2012 at 10:56 AM, Lorin Hochstein
lo...@nimbisservices.comwrote:
Doug:
I'm not sure. I'll port these to compute admin docs so
According to the statement of this article from Gartner
group http://blogs.gartner.com/lydia_leong/2012/04/03/citrix-cloudstack-openstack-and-the-war-for-open-source-clouds/ Openstack is a
highly immature platform.
But why? What's make Openstack so immature?
Any comments on that?
Thank you
Essex is a key release in this respect. With the excellent work done by the
developers, testers and packaging teams, OpenStack is much better positioned
than with Diablo.
As the work proceeds on Folsom, back porting critical bugs and planning for a
smooth migration path for production
I've created a quick OpenStack plugin for Jenkins, using the Java bindings
that Luis I created.
It's available on github here:
https://github.com/platformlayer/openstack-jenkins (no binaries - yet!)
Right now, it has the same (jenkins) functionality as the S3 plugin; it can
store artifacts
There are many projects rolled up into the thing called OpenStack.
Nova is only one of them and is the one that most people are talking
about when they say OpenStack. This does a huge disservice to the
other projects especially Swift.
It's very frustrating to see the other projects all painted
Justin++
This is really cool plugin.
Good Job!
2012/4/4 Justin Santa Barbara jus...@fathomdb.com:
I've created a quick OpenStack plugin for Jenkins, using the Java bindings
that Luis I created.
It's available on github here:
https://github.com/platformlayer/openstack-jenkins (no binaries
+1000
I believe the nova team should make backporting essential bugs to a
stable essex base and dealing with the upgrade issue the highest
priority for the start (at least) of the Folsom cycle. We need people to
deploy real systems using Essex. With regard to smooth upgrades, they
won't
Hello everyone,
Murphy striked, two regressions were found in recent commits in Nova. We
therefore rebuilt a new (and hopefully last) release candidate for
OpenStack Compute (Nova) 2012.1:
https://launchpad.net/nova/essex/essex-rc4
Now let's get those release notes right:
Maybe it would be more interesting, instead of getting on the defensive to
instead start asking what people think is broken or is immature and fix those
areas.
Push forward, get peoples feelings about it, and take it as constructive input.
If people think its immature, ask for why and then fix
Hi Kevin,
I'm in the process of looking at the Ubuntu packages. I've booted up 3 12.04
instances in our existing cloud and have installed the Ubuntu packages. I'm
playing with the new keystone 'lite' service as I write this. In fact, I'm
looking at your script to bootstrap keystone versus
Another perspective worth considering is immaturity vs growth. Are
there enough progresses being made? When problems are identified, are
these solved swiftly and effectively? I think the people involved in
the OpenStack community do and have done a great job in this regard,
and should be praised
This is a plugin for OpenStack; it won't support any other clouds. This
means there will be no baggage from having to support EC2, or any of the
other clouds that JClouds supports. We can support all the OpenStack
goodness directly.
JClouds is great, but it's an abstraction layer that doesn't
Justin, it's a pleasure work with you
Great work with the Jenkins stuff
Cheers!
Luis
On Thu, Apr 5, 2012 at 12:40 AM, Justin Santa Barbara
jus...@fathomdb.comwrote:
This is a plugin for OpenStack; it won't support any other clouds. This
means there will be no baggage from having to support
Justin Santa Barbara jus...@fathomdb.com writes:
This is a plugin for OpenStack; it won't support any other clouds. This
means there will be no baggage from having to support EC2, or any of the
other clouds that JClouds supports. We can support all the OpenStack
goodness directly.
I second
Greeting:
I want my instances not be able to communicate to each other, I know it is
possible to set the firewall manually. I just want know if there are more
graceful way to do that
thanks
William Herry
--
Where there is a will, there is a way.
williamherrych...@gmail.com
Thanks - there are some good feature requests here.
Have you proposed a design summit session where you are going to talk about
OpenStack features that you would like to see? Things like supporting
cloud federation, instance pooling, or fixing that networking bug?
The Jenkins features (e.g.
Use the flag --allow_same_net_traffic :
This flag will allow all traffic from other vms (and host machines) in the
same network. It defaults to true. If you would prefer to block all vm-vm
traffic and use security groups to manage vm-vm traffic, set this flag to
false.
On Wed, Apr 4, 2012 at
On Wed, Apr 4, 2012 at 7:24 PM, Joshua Harlow harlo...@yahoo-inc.com wrote:
keystone token-get --debug
U get: keystone: error: unrecognized arguments: --debug
But if u do it before it works, odd. Guess that’s a “false” message/error.
Actually that is exactly how it is supposed to work.
** Changed in: openstack-common
Status: Fix Committed = In Progress
--
You received this bug notification because you are a member of OpenStack
Common Drivers, which is the registrant for openstack-common.
https://bugs.launchpad.net/bugs/960487
Title:
Request deserializer does not pass
56 matches
Mail list logo
