Hi Trinath,
Yes, you need to install openvswitch and the quantum-agent on the nova
compute nodes as well.
Aaron
On Fri, Jul 13, 2012 at 1:29 AM, Trinath Somanchi
trinath.soman...@gmail.com wrote:
Hi-
With respect to your document, on Openstack - OVS and Quantum,
I'm unable to understand
Hi -
Thanks a lot for the reply.
Following the document (
https://lists.launchpad.net/openstack/pdfuNjHGvU5UA.pdf,) for installing
the OVS and Quantum Agent in Compute nodes.
*Open-vSwitch Quantum-agent*
apt-get install openvswitch-switch quantum-openvswitch-agent
modprobe openvswitch_mod
echo
Hi Trinath,
I'm not sure off hand, I've never installed the deb package. If you just
looking to get up and running quickly I'd recommend following this
http://wiki.openstack.org/QuantumDevstack using devstack.
Aaron
On Fri, Jul 13, 2012 at 2:00 AM, Trinath Somanchi
trinath.soman...@gmail.com
Matt Joyce wrote:
To certain extent I agree with george's sentiment.
Recent example... we're changing tenants to projects in the keystone api.
Yes we maintain v2 api compatibility but there will be a cost to users
in the confusion of decisions like this. George is right to be calling
Hello everyone,
If you have been following this list, you might have seen that the
Ceilometer project, while not yet fully functional, has made some great
progress over the past three month. The next summit being just a few
months away, we thought it would be time to start collecting general
+1 to Vish's proposal
I'd go a step further and suggest adopt this model for such changes going
forward.
Chris
Sent from my iPad
On Jul 12, 2012, at 5:40 PM, Vishvananda Ishaya vishvana...@gmail.com
wrote:
On Jul 12, 2012, at 2:36 PM, David Mortman wrote:
On Thu, Jul 12, 2012 at 3:38
This is exactly the sort of interaction we need between the two perspectives of
the OpenStack community.
Thanks
Chris
Sent from my iPad
On Jul 12, 2012, at 11:20 PM, Joe Topjian joe.topj...@cybera.ca wrote:
Hello,
I'm not an OpenStack developer nor any type of developer. I am, however,
Sent from my iPad
On Jul 13, 2012, at 12:41 AM, Blake Yeager blake.yea...@gmail.com
wrote:
snip
I am excited to see such passion from the community but we need to make
sure that passion is directed in a constructive manner.
+1
Chris___
Mailing
Hi All,
INDIA OpenStack User Group is planning to organise a meetup in DELHI NCR.
All those who are interested in attending, presenting or helping to
organise.
Please reply here or mail me at syedarm...@ymail.com
Cheers!
Syed Armani
___
Mailing list:
Hi,
I'm trying to make an update request (PUT
/v2.0/OS-KSADM/services/53ccd2984389495cab439640dc5596d3) and it's
returning HTTP 404.
The docs also miss the PUT method [1], so I guess if there is a way to
update a service through the WS API?
Thanks,
Antonio.
[1]
There are no method update_service here [1], so I think update is
not possible, am I right?
Thanks,
Antonio.
[1]
https://github.com/openstack/keystone/blob/0425fba560e7d68e52f922667972765e64ad17dc/keystone/controllers/services.py
2012/7/13 Antonio Manuel Muñiz Martín amu...@klicap.es:
Hi,
Hello list,
i've this problem, when i run nova-manage service list i get
nova-compute server1.site.it nova enabled
:-) 2012-07-13 12:15:44
nova-volume server1.site.it nova enabled
:-) 2012-07-13 12:15:51
It would seem that those voting for option 1 do so primarily from a code
hygiene and maintenance perspective. If code hygiene were the only issue this
would make sense.
But for those of us with a production environment going straight from
Nova-volumes to a full Cinder deployment is too big a
Thank's to Adam Gandelman for the last e-mail about *Folsom Testing Packages
* in *Ubuntu* [1].
I would like to share here my feedback and also the Issues I have today
with that :
- Glance Packaging [2] : Conflict between two packages.
- Glance Endpoint does not work with API V2 but works
Hi Folks,
I was reviewing a code change to add generic retries for build failures (
https://review.openstack.org/#/c/9540/2 ), and wanted to be sure that it
wouldn't invalidate the capacity accounting used by the scheduler.
However I've been sitting here for a while working through the Folsom
On Thu, Jul 12, 2012 at 9:42 PM, 张家龙 zhan...@awcloud.com wrote:
Dear all,
As the project named ceilometer appeared,I paid close attention to it.
According to the docs of ceilometer,I deploied it in openstack exsse
environment.
While,I cannot start the ceilometer collector and
On Fri, Jul 13, 2012 at 10:04 AM, Doug Hellmann doug.hellm...@dreamhost.com
wrote:
On Thu, Jul 12, 2012 at 9:42 PM, 张家龙 zhan...@awcloud.com wrote:
Dear all,
As the project named ceilometer appeared,I paid close attention to it.
According to the docs of ceilometer,I deploied it in
Dear Doug,
I`m use Qpid instead of Rabbit .
Did it cause the error ?
In addition,my nova.conf,mongodb.conf and ceilometer-collector.conf are
here:
http://pastebin.com/sW5d8eRv
http://pastebin.com/D5GMkLsb
http://pastebin.com/u5vH22Lh
Were there some
On 07/12/2012 03:54 PM, George Reese wrote:
This community needs offending.
This is your opinion and you're entitled to it but let me assure you
that *nobody* here wants to be offended by you. This community is made
of smart people that deserve respect: stop offending them, now.
Make your point
Hi Chris,
What happens to notifications to other compute servers that are generated as
side effect of VM creation a result of using the IPtables firewall driver ?
Are they somehow propagated to other Cells, or is there something that keeps
all VMs in a particular security group within a
On Fri, Jul 13, 2012 at 11:36 AM, 张家龙 zhan...@awcloud.com wrote:
Dear Doug,
I`m use Qpid instead of Rabbit .
Did it cause the error ?
Qpid should work, but I haven't been testing with that so you might have
found a bug.
There are (at least) two differences between your setup and
On 07/11/2012 02:24 PM, Nick Barcet wrote:
Candidates should, before July 24th:
1/ declare themselves on this mailing list
It has been so much fun and so rewarding to kick-start this project,
that I can't resist to propose myself as Candidate. Not being a true
developer places me in an awkward
Because the community has done such a good job in the area of interoperability
and compatibility over the past few years that it thus deserves the benefit of
the doubt even though we have a thread previously showing blatant disregard for
such concerns?
No, this community has, by and large,
Eglynn pointed out some concurrency concerns in this review that I wanted to
highlight:
https://review.openstack.org/#/c/9552/
The issue is we need to provide Glance stores access to the request context.
The current thought is that we'd like to modify Glance to create new Store
objects for
Hi Phil,
The nova.db.api.compute_node_update() call is what the individual virt
drivers call to update the compute node stats. grep for that and you'll
see where the calls to set the compute node data are called.
Best,
-jay
On 07/13/2012 09:38 AM, Day, Phil wrote:
Hi Folks,
I was
In the V2 API, there's no update available - it's just create/delete.
-joe
On Jul 13, 2012, at 5:19 AM, Antonio Manuel Muñiz Martín wrote:
There are no method update_service here [1], so I think update is
not possible, am I right?
Thanks,
Antonio.
[1]
On 07/13/2012 06:55 AM, Leandro Reox wrote:
Ok, here is the story, we deployed some inhouse APIs in our Openstack
privade cloud, and we were stressing them up, we realize that some
packages were taking so long, to discard the behavior of the api, we
installed apache, lighttpd and event tried
On 07/13/2012 05:50 AM, Emilien Macchi wrote:
Thank's to Adam Gandelman for the last e-mail about *Folsom Testing
Packages* in *Ubuntu* [1].
I would like to share here my feedback and also the Issues I have
today with that :
* Glance Packaging [2] : Conflict between two packages.
*
Hi Trinath,
I suspect that /etc/quantum should be created when you run the following
line from Emilien's document:
apt-get install -y quantum-server quantum-plugin-openvswitch
python-keystone
python-keystoneclient openvswitch-datapath-source
If /etc/quantum was not created, perhaps its an issue
Hi guys,
i've 2 hosts configured in multi_host, i had 2 vm (1 per host) with 1 floating
ip each, then nova-compute on second host crashed when deleting the vm2, i've
restarted host2 and it deleted the vm successfully, then i've got an error
about floating ip cannot be associated to vm2 in logs,
Phil,
This may shine some light.
https://bugs.launchpad.net/nova/+bug/1016273
best,
Joe
On Fri, Jul 13, 2012 at 10:27 AM, Day, Phil philip@hp.com wrote:
Hi Jay,
If I read it correctly that updates the *_used values that show actual
consumption, but what I was looking for is the
Hi all,
I just tried to install nova from the folsom-2 package and run into an issue
with the api server, which I can't really figure out.
Tracking the progress with a large number of strategically placed prints I
get to the stage where the api (for example metadata) app is being loaded in
I *just* ran into a problem today triggered by some code moving around in
nova and common. I had to set my driver to
nova.openstack.common.notifier.rabbit_notifier (in both files).
I didn't see any errors from that until I tried to launch an instance, so
it doesn't seem to prevent any of the nova
The only way currently is to delete the records from the services table in the
database.
Vish
On Jul 13, 2012, at 5:27 AM, Alessandro Tagliapietra wrote:
Hello list,
i've this problem, when i run nova-manage service list i get
nova-compute server1.site.it nova
Larsk Kellogg-Stedman shared a few weeks ago the tool he uses to clean
up OpenStack database after messing with it:
http://markmail.org/message/gygnjvdy3njwfrtg
maybe it's useful for others, too.
Cheers,
stef
On 07/12/2012 12:48 PM, Sébastien Han wrote:
What an idtio, it's create, not add.
Sorry for the spam
Il giorno 13/lug/2012, alle ore 20:00, Alessandro Tagliapietra ha scritto:
Hi guys,
i've 2 hosts configured in multi_host, i had 2 vm (1 per host) with 1
floating ip each, then nova-compute on second host crashed when deleting the
Hi Sam,
Would you mind filing a bug against Horizon with the details so that we can get
it fixed? You can do so here: https://bugs.launchpad.net/horizon/+filebug
John Postlethwait
Nebula, Inc.
206-999-4492
On Thursday, July 12, 2012 at 3:55 PM, Sam Su wrote:
I finally found why this
From: openstack-bounces+atul.jha=csscorp@lists.launchpad.net
[openstack-bounces+atul.jha=csscorp@lists.launchpad.net] on behalf of
Alessandro Tagliapietra [tagliapietra.alessan...@gmail.com]
Sent: Saturday, July 14, 2012 12:18 AM
To:
Glance pagination was added in Folsom. Adding a bug for this won’t help since
it’s already been added in the current code.
- Gabriel
From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
[mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] On
Thank you for you guys' suggestions.
Even so, I'd like to file a bug to track this issue, if someone else have
the same problem, they would know what happened and what progressed from
the bug trace.
Sam
On Fri, Jul 13, 2012 at 12:43 PM, Gabriel Hurley
gabriel.hur...@nebula.comwrote:
Glance
That's actually an issue with Packaging and I met in April during Essex
Release.
My document does not explain in details how to manage Quantum, but this is
a document which allow to get something working in dual node.
Of course, maybe I did some errors and the best way for me to correct it
asap
Well, it sounds like this issue only happens in Essex, and is no longer an
issue in Folsom, so the bug will just be closed as invalid, as it is now fixed
in the newer code...
John Postlethwait
Nebula, Inc.
206-999-4492
On Friday, July 13, 2012 at 1:36 PM, Sam Su wrote:
Thank you for you
Capacity based scheduling currently adds up all instance usage in
host_manager.py
There's another review marked as WIP that will be ready when retries go in that
cleans that and the capacity tracking up. Look for it from Brian Elliott.
On Jul 13, 2012, at 6:38 AM, Day, Phil philip@hp.com
I am attempting to find a workable solution for the following use case, and
would like to get feedback from the community about it.
There are some situations when it is required to put a proxy in front of
multiple API endpoints and route by URL. This allows for more flexible
routing/filtering
Dan,
Adam Young was advocating for something like this. I don't know if a
consensus was ever reached, but I thought it was a good idea.
https://lists.launchpad.net/openstack/msg10864.html
Nate
On Jul 13, 2012 5:31 PM, Dan Sneddon d...@cloudscaling.com wrote:
I am attempting to find a
On Fri, Jul 13, 2012 at 10:56 PM, John Postlethwait
john.postlethw...@nebula.com wrote:
Well, it sounds like this issue only happens in Essex, and is no longer an
issue in Folsom, so the bug will just be closed as invalid, as it is now
fixed in the newer code...
Please backport this bug
Was this problem ever resolved? I'm having the identical issue right now
(perhaps because I am following Sebastien's guide [0]). I found this
question raised on LP [1], but no helpful responses, and no linked bug. I
can confirm that I can attach an RBD instance manually through virsh, no
My bad. I know for the future now.
Thank's and sorry for the mistake.
Regards
On Fri, Jul 13, 2012 at 7:19 PM, Adam Gandelman ad...@canonical.com wrote:
On 07/13/2012 05:50 AM, Emilien Macchi wrote:
Thank's to Adam Gandelman for the last e-mail about *Folsom Testing
Packages* in
On Tue, Jun 12, 2012 at 8:20 AM, Pádraig Brady p...@draigbrady.com wrote:
On 06/12/2012 04:07 PM, Fredric Morenius wrote:
From: Scott Moser [mailto:ssmos...@gmail.com] On Behalf Of Scott Moser
Sent: den 11 juni 2012 23:16
...Without digging around on older versions of OS's and their included
On 07/13/2012 03:09 PM, Travis Rhoden wrote:
Was this problem ever resolved? I'm having the identical issue right now
(perhaps because I am following Sebastien's guide [0]). I found this
question raised on LP [1], but no helpful responses, and no linked bug. I
can confirm that I can attach an
I agree if someone wants to commit a backported fix. This makes sense to
do. It's a pretty significant bug for essex users.
-Matt
On Fri, Jul 13, 2012 at 3:00 PM, Christian Parpart tra...@gmail.com wrote:
On Fri, Jul 13, 2012 at 10:56 PM, John Postlethwait
john.postlethw...@nebula.com
Highlights of the week
G
stands for Grizzly
Results of the naming poll for next OpenStack release are
in, and the G release will be named Grizzly.
The regular poll
Disagreements and misunderstanding concerning etiquette and upgrading
Cassandra aside, this thread has three major themes: 1) the relative ease
or burden of upgrade paths 2) compatibility between versions and 3) what
OpenStack values when making decisions.
I believe the first two hinge on the
On 07/14/2012 12:09 AM, Mark Moseley wrote:
On Tue, Jun 12, 2012 at 8:20 AM, Pádraig Brady p...@draigbrady.com wrote:
On 06/12/2012 04:07 PM, Fredric Morenius wrote:
From: Scott Moser [mailto:ssmos...@gmail.com] On Behalf Of Scott Moser
Sent: den 11 juni 2012 23:16
...Without digging around
On Friday, July 13, 2012 at 20:35 PM, Pádraig Brady wrote:
More interesting though, and what might be of use to other people, the
kpartx -a calls get run and then the code in nova/virt/disk/mount.py
immediately checks for whether or not the newly created
/dev/mapper/nbdXXpX
Josh,
Thanks so much for the pointers. I did not figure out that libvirt was
trying to read /etc/ceph/ceph.conf. It was in fact being denied by
apparmor. I fixed my problem by editing /etc/apparmor.d/libvirt/TEMPLATE
and adding /etc/ceph/** r, to the template. Now it works for newly
spawned
at 20120713-1205Build needed 00:01:25, 648k disc spaceERROR:root:Error occurred during package creation/buildERROR:root:Command '['sbuild', '-d', 'precise-folsom
Title: quantal_folsom_horizon_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_horizon_trunk/47/Project:quantal_folsom_horizon_trunkDate of build:Fri, 13 Jul 2012 16:31:54 -0400Build duration:2 min 9 secBuild cause:Started by an SCM changeBuilt
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/148/Project:quantal_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 16:31:55 -0400Build duration:3 min 25 secBuild cause:Started by an SCM changeBuilt
Title: precise_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/151/Project:precise_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 16:34:05 -0400Build duration:3 min 29 secBuild cause:Started by an SCM changeBuilt
Title: precise_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/152/Project:precise_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 17:31:55 -0400Build duration:3 min 12 secBuild cause:Started by an SCM changeBuilt
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/150/Project:quantal_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 18:01:54 -0400Build duration:2 min 52 secBuild cause:Started by an SCM changeBuilt
Title: precise_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/153/Project:precise_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 18:01:54 -0400Build duration:3 min 5 secBuild cause:Started by an SCM changeBuilt
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/151/Project:quantal_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 18:31:56 -0400Build duration:2 min 51 secBuild cause:Started by an SCM changeBuilt
Title: precise_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/154/Project:precise_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 18:31:55 -0400Build duration:3 min 24 secBuild cause:Started by an SCM changeBuilt
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/152/Project:quantal_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 19:01:56 -0400Build duration:3 min 26 secBuild cause:Started by an SCM changeBuilt
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/153/Project:quantal_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 19:31:54 -0400Build duration:2 min 52 secBuild cause:Started by an SCM changeBuilt
Title: precise_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/156/Project:precise_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 19:31:54 -0400Build duration:3 min 25 secBuild cause:Started by an SCM changeBuilt
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/155/Project:quantal_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 20:31:55 -0400Build duration:2 min 36 secBuild cause:Started by an SCM changeBuilt
Title: precise_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/158/Project:precise_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 20:31:54 -0400Build duration:3 min 5 secBuild cause:Started by an SCM changeBuilt
Title: precise_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/159/Project:precise_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 22:31:54 -0400Build duration:3 min 32 secBuild cause:Started by an SCM changeBuilt
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/156/Project:quantal_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 22:35:27 -0400Build duration:2 min 24 secBuild cause:Started by an SCM changeBuilt
72 matches
Mail list logo
