My bad, here the good link :
https://github.com/EmilienM/doc-openstack/issues/new
Regards
On Mon, Jul 16, 2012 at 6:55 AM, Trinath Somanchi
trinath.soman...@gmail.com wrote:
Hi Emilien-
The link given by you throwing an error. 404 page not found.
Hi-
Got a doubt in configuring Quantum in Controller and Node.
In Controller, we have Quantum-Server and Quantum-Agent.
In Node we have only Quantum-Agent.
Why do we need Quantum-Agent in the Controller side?
Please kindly help me understand this...
--
trinath
On Mon, Jul 16, 2012 at 2:14
Hi Trinath,
I will forward you one mail where we have already been discussed there
about this.
Thanks,
Hitesh wadekar
On Mon, Jul 16, 2012 at 3:07 PM, Trinath Somanchi
trinath.soman...@gmail.com wrote:
Hi-
Got a doubt in configuring Quantum in Controller and Node.
In Controller, we
Hi,
*Quantum-Server :*
Can be a VM, or installed also on nova-controller node.
*Quantum-Agent :*
Should be run on each compute node, and ALSO the nova-network node (to
create virtual gateway).
If you run nova-network on nova-controller node, you'll need also
Quantum-Agent.
Regards
On Mon,
Hi,
The patch https://review.openstack.org/#/c/9591/ contains the initial
support for the scalable agents (this is currently implemented on the
linux bridge). At the moment this does not support a network or port
update, that is, the user can set 'admin_status_up' to 0. This means
that either
hi, all
As LVM backend image support was introduced in the trunk version of
nova, is there any plan to support snapshot of the LVM backend image?
I am using libvirt and Xen, with lvm as the instance image backend.
There are two issues when creating snapshot.
1.
Current snapshot implementation for libvirt driver doesn't support
snapshotting for everything except qcow2 (as i remember, because
virDomainManagedSave
will fail on everything except qcow2). So, maybe we can discuss it here.
This for sure can be implemented for lvm using lvm snapshots but it will
On 07/12/2012 05:40 PM, Vishvananda Ishaya wrote:
Excellent points. Let me make the following proposal:
1) Leave the code in nova-volume for now.
2) Document and test a clear migration path to cinder.
3) Take the working example upgrade to the operators list and ask them for
opinions.
4)
Does it make sense to shutdown instance before doing snaphotting, and then
make a lvm snaphot of instance disk. This would be safe for instance though
it‘s not some sort of 'live snaphot'.
2012/7/16 Boris Filippov bfilip...@griddynamics.com
Current snapshot implementation for libvirt driver
On Mon, 2012-07-16 at 15:20 +0400, Boris Filippov wrote:
Current snapshot implementation for libvirt driver doesn't support
snapshotting for everything except qcow2 (as i remember, because
virDomainManagedSave
will fail on everything except qcow2).
Sheepdog also supports the
Well, according to
http://libvirt.org/html/libvirt-libvirt.html#virDomainManagedSave
domain will be suspended.
After snapshotting there is new _create_domain call:
if state == power_state.RUNNING:
virt_dom.managedSave(0)
... snapshotting...
finally:
On Sat, Jul 14, 2012 at 10:02 PM, 张家龙 zhan...@awcloud.com wrote:
Hi,all.
Sorry for late reply.
Until now, I not test folsom. So, I`am not sure how it work in folsom .
The follow is my qpid config file:
http://pastebin.com/sBXm6k7z
And Doug writed set driver to
But qemu can also write the vm state outside of the backend image, which
should be usable with all image backends.
Use that instead managedSave? This should suffice. Save VM state,
suspend domain - do snapshot - restore VM with previous state?
___
An Storage Networking Industry Association (SNIA) for Cloud Data Management
Interface (CDMI) specification implementation based on OpenStack Swift has
been published at https://github.com/osaddon/cdmi
This implementation supports basic CDMI cloud data and container
manipulation and provides over
An excellent idea. I believe that if the below message had been sent in
April, the tenor of the discussion would have been much different. I
think a main source of angst around this was that there was no mention
at the Folsom summit of nova-volume being simply removed immediately,
except
Hi, Joseph
I'm working on the patch for blueprints
https://blueprints.launchpad.net/nova/+spec/update-flavor-key-value, to
add/delete the extra_specs for flavor through nova-manage. I'm still setting up
my environment to push the patch.
However, when I was testing my patch, I
Dear Doug,
Thanks for reply.
While ,where to find the patch posted John ? If it`s prossable,please
point it out,Thanks.
And it`s my pleasure to be the first one to receive the message about you
fix this problems.
Good luck !
--
Best Regards
ZhangJialong
On 07/13/2012 05:39 PM, Nathanael Burton wrote:
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
Dan,
Here's my proposed scheme.
Doug,
I will start ceilometer installation now. Would you recommend installing Folsom
then instead of essex? (I already have essex installed so, this is the reason
for asking).
Thanks,
Glaucimar Aguiar
From: openstack-bounces+glaucimar.aguiar=hp@lists.launchpad.net
An earlier message in this thread points to a bug (
https://bugs.launchpad.net/ceilometer/+bug/1024563) which has a review
patch attached.
On Mon, Jul 16, 2012 at 10:03 AM, 张家龙 zhan...@awcloud.com wrote:
Dear Doug,
Thanks for reply.
While ,where to find the patch posted John ? If it`s
I have been doing all of my development with Folsom HEAD because DreamHost
plans to deploy ceilometer with our Folsom-based cloud. I know Julien has
done some work on Essex compatibility, but I don't know where that stands
or if he is still working on it.
Doug
On Mon, Jul 16, 2012 at 10:12 AM,
I definitely agree with everything said here.
On Jul 16, 2012, at 8:55 AM, David Kranz wrote:
An excellent idea. I believe that if the below message had been sent in
April, the tenor of the discussion would have been much different. I think a
main source of angst around this was that there
David Kranz wrote:
Going forward, and this may be controversial, I think these kinds of
issues would be best addressed by following these measures:
1. Require each blueprint that involves an API change or significant
operational incompatibility to include a significant justification of
Hi,
We are trying to test the openstack with quantum stable/essex release using
devstack. We are seeing the following issue at our setup:
=
+ /opt/stack/nova/bin/nova-manage network create private 10.0.0.0/24 1 4096
2012-07-16 21:47:37
Hey Phil,
As Chris mentioned, I do have another review up:
https://review.openstack.org/#/c/9402/
The goal with that one is to more completely calculate all the capacity and
resource consumption information on the compute host than the current
capacity_notifier does. So, capacity-based
On 07/16/2012 09:55 AM, David Kranz wrote:
An excellent idea. I believe that if the below message had been sent in
April, the tenor of the discussion would have been much different. I
think a main source of angst around this was that there was no mention
at the Folsom summit of nova-volume
Would someone please comment on the status of Donabe and if there are any
new work/documents/code that can be shared with the community.
Thanks,
-Mohammad___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Has the user committee selection/ setup process been discussed before?
Does it matter how big a customer the user represents - big co vs
individual/ enthusiast?
Thanks,
-Sriram
-Original Message-
From: openstack-bounces+sriram=sriramhere@lists.launchpad.net
On 06/28/2012 11:54 AM, Dean Troyer wrote:
On Mon, Jun 25, 2012 at 5:28 PM, Doug Hellmann
doug.hellm...@dreamhost.com wrote:
On Mon, Jun 25, 2012 at 6:19 PM, Ken Thomas k...@yahoo-inc.com wrote:
[...]
I've already submitted the keystone changes for review
The code checks that it's has a tty before it prompts. Automatic scripts
should work just as before using the env variable or command line
option. If they aren't present and there's no tty, then they'll error
out exactly as they did before.
Ken
On 7/16/12 2:00 PM, Adam Young wrote:
On
Hello
I've submit patch (https://review.openstack.org/#/c/7101/), that help Swift use
special features of file system on that it working.
One of the changes in this patch is for reduce number of network replicas of
partition if user use self-repairing mirrored device. For this user should add
cc'ing the PPB mailing list...
On 07/16/2012 06:25 PM, Steven Dake wrote:
Dear members of the Project Policy Board:
After four months of development on the Heat project[1], the developers
voted[2] to apply for incubation. The developers feel Heat provides a
feature rich user experience and
Hi All,
I've got a working implementation of quotas in Keystone. However it's only
working for the KVS and SQL backends right now and I need it to work with
LDAP before submitting it for review. I have limited experience with LDAP
and only from an ops perspective, I've never developed any
Hello,
Last time I deployed OpenStack, I recall it didn't have any performance
monitoring of VM instances or any auto scaling (up/down like Amazon ec2)
features. I would like to know if any incubated projects support or plan to
support these features. I'm specially interesting in auto scaling for
Hi,
Hello,
snip
Last time I deployed OpenStack, I recall it didn't have any performance
monitoring of VM instances or any auto scaling (up/down like Amazon ec2)
features. I would like to know if any incubated projects support or plan to
support these features. I'm specially interesting in
Speaking of the User Committee as proposed in the draft governance docs, I
can
certainly see value in having the committee chair chosen by the board.
However, as
currently proposed, there is a convoluted process for appointing the
representatives
of the committee. Frankly, if you want to give a
On 16/07/12 18:36 -0500, Miguel Alejandro González wrote:
Hello,
Last time I deployed OpenStack, I recall it didn't have any performance
monitoring of VM instances or any auto scaling (up/down like Amazon ec2)
features. I would like to know if any incubated projects support or plan to
support
On 07/16/2012 07:31 PM, Everett Toews wrote:
Hi All,
I've got a working implementation of quotas in Keystone. However it's
only working for the KVS and SQL backends right now and I need it to
work with LDAP before submitting it for review. I have limited
experience with LDAP and only from an
Christopher B Ferris wrote:
Speaking of the User Committee as proposed in the draft governance docs,
I can
certainly see value in having the committee chair chosen by the board.
However, as
currently proposed, there is a convoluted process for appointing the
representatives
of the
We're running into what looks like a linux bridging bug, which causes
both substantial (20-40%) packet loss, and DNS to fail about that same
fraction of the time. We're running essex on precise, with dedicated
nova-network servers and VLANManager. On either of our nova-network
servers, we see the
Hi Naveen,
Your best bet is probably to create a question on
https://answers.launchpad.net/quantum/ . I would include the log output
below, plus logs from nova-network and quantum screens.
Dan
On Mon, Jul 16, 2012 at 9:53 AM, Naveen Kuna naveen.k...@oneconvergence.com
wrote:
Hi,
We are
Narayan,
Are you doing bonding in conjunction with your bridging + vlans? Or is it
just a single interface backing the vlan_interface?
Nate
On Jul 16, 2012 9:55 PM, Narayan Desai narayan.de...@gmail.com wrote:
We're running into what looks like a linux bridging bug, which causes
both
Boris Filippov wrote:
But qemu can also write the vm state outside of the backend image, which
should be usable with all image backends.
Use that instead managedSave? This should suffice. Save VM state,
suspend domain - do snapshot - restore VM with previous state?
For best
Hi all,
I have a question as the subject above, I use 'essex' and qemu-kvm.
The reason I want to know this is that, if I attach some disks on the guest,
for example, I specified target devices as /dev/vdc/dev/vdd, but they may be
/dev/vdb/dev/vdc in the guest os,
so if the guest user want to
Jiang, Yunhong wrote:
Hi, Joseph
I’m working on the patch for blueprints
https://blueprints.launchpad.net/nova/+spec/update-flavor-key-value,
to add/delete the extra_specs for flavor through nova-manage. I’m
still setting up my environment to push the patch.
However,
Hi,
If the name is intended to be a description then how about the idea of
calling the field description instead. This is far more descriptive
and does not lend the user to think that this should be unique.
Thanks
Gary
___
Mailing list:
Hi Gary, this is an example of when I wish openstack APIs had a
style-guide to try to ensure some consistency across projects.
For those new to the conversation, the original topic of discussion is
whether names for API objects should be forced to be unique (presumably
within a tenant?) or
47 matches
Mail list logo
