?
Did you mistype your comment or misread mine? Raw does NOT work for snapshots.
snapshots only work for qcow2. Implementing snapshotting with raw would be
possible. Logic just needs to be added to skip the internal snapshot step and
just use the entire file when uploading to glance. This
Thanks to the 16 persons that took the time to give their preference on
Doodle [1]. The poll is now closed and the meeting time that came out
of it is:
Thursdays at 4pm UTC on #openstack-metering
I was not sure if we could use #openstack-meeting as we are not yet an
official project, lkm if
JSONP has been used for years - for example Solr has supported it since
2008 (and possibly earlier). CORS matches the Openstack APIs better though.
Redirects are unrelated to the problem as far as I can see.
I think that toolmakers trying to build Javascript tools that connect to
multiple
On 12/04/12 13:35, J. Daniel Schmidt wrote:
While testing our SUSE OpenStack packages we hit a nasty bug and reported it
as: https://bugs.launchpad.net/keystone/+bug/972502
We found out that the underlying cause was a lack of referential integrity[1]
using sqlite or mysql. When we tried
Hi Team,
I have deployed OpenStack on Ubuntu 11.10 using DevStack script. I would
like to know how to increase the disk size/add an extra disk to an already
existing (Running) Virtual machine using OpenStack Dashboard.
Your help will be of great use to me.
Thanks,
Swetha
Hi Swetha,I don't think it's possible to resize an already assigned volume via the dashboard.Via the console, it would be possible, in order :- to resize the LV ($ lvresize)- to umount the FS- to check the FS ($ fsck)- to resize the FS (resize2fs)
Nuage Co - Razique
Dear.
I've run into troubles with the resize of partitions and file injection;
using libvirt and raw images.
According to https://bugs.launchpad.net/nova/+bug/929005 file injection
into images only works in the following situations:
1.- whole disk image - inject to partition 1.
2.- separate
Hi
I tried to see how we can control any existing infrastructure of
VMWare/XenServer etc from openstack.
What i understood is that nova compute needs to be installed on the
hypervisors(compute hosts) which can be Ubuntu Servers for KVM etc.
Also for XenServer, we can build a package on Ubuntu
Hi,
I worked with Cloudstack too, Cloudstack use the vCenter for launch the VM's,
destroy, etc. That is a good idea but you depend, always, for the good
funcionality of vCenter.
The Information for Openstack is so short:
On Tue, Apr 24, 2012 at 1:11 PM, Joe Gordon j...@cloudscaling.com wrote:
Hi All,
I would like to propose a minimum required code coverage level per file in
Nova. Say 80%. This would mean that any new feature/file should only be
accepted if it has over 80% code coverage. Exceptions to this
On 04/24/2012 10:08 PM, Lorin Hochstein wrote:
On Apr 24, 2012, at 4:11 PM, Joe Gordon wrote:
Hi All,
I would like to propose a minimum required code coverage level per
file in Nova. Say 80%. This would mean that any new feature/file
should only be accepted if it has over 80% code
Since we're talking snapshots, quick doc-related snapshot questions:
- Are snapshots only supported on qemu/kvm, or do they work with other
hypervisors as well? (Does Xen support qcow2 images?)
- Does OpenStack do anything with snapshots other than using them to generate
new images? I was a
That looks like enough interest to be worthwhile.
Date of next meeting:
Wednesday 9th May, 17:00 UTC
I have updated the wiki page:
http://wiki.openstack.org/Meetings/XenAPI
Not sure how the meetbot finds out about my plans, advice welcome...
Thanks,
John
-Original Message-
From:
The VMWare and XenServer OpenStack support have very similar architectures.
Every hypervisor has a VM that runs the nova-compute code. You don’t as such
install it into the hypervisor. In the case of XenServer, there are certainly
some plugins that are installed, but nova, at the moment, still
XenServer does snapshots, but it uses VHD files on the EXT file system. That
means it is not supported with LVM storage.
As far as I understand things: Snapshot = upload current state of disk to
Glance as a new image
I have not seen any support for incremental snapshots/backups as yet, but I
On Apr 25, 2012, at 7:44 AM, Lorin Hochstein wrote:
Since we're talking snapshots, quick doc-related snapshot questions:
- Are snapshots only supported on qemu/kvm, or do they work with other
hypervisors as well? (Does Xen support qcow2 images?)
I was speaking about libvirt/kvm, but the
There was discussion on the list recently of a similar problem using nfs4.
Perhaps their solution will work for you:
http://www.mail-archive.com/openstack@lists.launchpad.net/msg09440.html
Vish
On Apr 25, 2012, at 8:18 AM, Sergio Ariel de la Campa Saiz wrote:
Hello:
I have found some
Hi Sergio,
We have environment with external NFS Server, NetAPP, Nexenta, EMC, etc and we
haven´t this problem, sounds like a problem with privileges, i can see the
libvirt.xml is nobody:nogroup, it is wrong, must be root:root. Try to change
manually, but maybe you have a wrong parameter in a
On Tue, 2012-04-24 at 13:11 -0700, Joe Gordon wrote:
nova/openstack/common/iniparser 40%
nova/openstack/common/cfg 41%
It's probably worth pointing out that, although openstack-common has
comprehensive unit tests, apparently, those tests are not copied into
client projects when the code is…
On 04/25/2012 01:13 PM, Alvaro Lopez wrote:
Dear.
I've run into troubles with the resize of partitions and file injection;
using libvirt and raw images.
According to https://bugs.launchpad.net/nova/+bug/929005 file injection
into images only works in the following situations:
1.- whole
Hi,
As I can see, nobody has replied to my last e-mail since yesterday, but
I'm sure you want to know the situation.
You can see my architecture :
https://lists.launchpad.net/openstack/pdfD4HBwoSR2Y.pdf
I've finally installed Quantum-server on essex-1 and solved a lot of
smalls issues.
For
It would be great if someone can spare some time to have a look at these :
https://review.openstack.org/#/c/6451/ : I've addressed comments from
first review cycle - Second patch set needs to be reviewed and
approved
https://review.openstack.org/#/c/6452/ : Brad Hall reviewed - But more
review
Salut Emilien,
- Horizon with Quantum : I can't integrate Quantum in the dashboard
even with
http://docs.openstack.org/trunk/openstack-compute/admin/content/build-and-configure-openstack-dashboard.html
It's because this part of the doc is outdated, quantum in horizon has be
disabled, new
I would like to keep the service type and name under the service and not the
endpoint, too. Make it easier to parse for a given service.
One thing is that I am not sure if we need the metadata tag... In the Keystone
XSD, we have the construct anyAttribute namespace=##other
Thanks... I have read this post but is not the problem I have :-(
Sergio Ariel
de la Campa Saiz
GMV-SES Infraestructura /
GMV-SES Infrastructure
GMV
Isaac Newton, 11
P.T.M. Tres Cantos
E-28760 Madrid
Tel.
+34 91 807 21 00
Fax
+34 91 807 21 99
www.gmv.com
Lorin Hochstein asked:
Are snapshots only supported on qemu/kvm, or do they work with other
hypervisors as well? (Does Xen support qcow2 images?)
Does OpenStack do anything with snapshots other than using them to generate
new images? I was a little confused by the existence of the
This isn't about parsing the data structure - it's about what a service
represents so that we can model it appropriately. So what does the service
here represent? the collection of all possible services of that type? That's
what your example would seem to indicate.
In your example, the service
Jan: is the concern that you don't see the value in the use case or that you
don't believe the proposed technologies are sufficiently mature?
In order to keep the thread somewhat linear I'm basically going to +1 what Nick
said and add that as an application developer I should be able to serve
Hi:
Thanks for your respond.
This is my /etc/export file in the NFS server:
/export 192.168.111.0/24(rw,sync,no_root_squash,fsid=0)
and my /etc/fstab file in my host is:
ip nfs server://nfs-directory nfs4 defaults00
Directories /export and /nfs-directory have 777
A little of both. Serving JS, et al from a CDN for a set of domain services is
easy peasey stuff and we do it all the time... but we tend to do so with a
common edge (at the very least in DNS space) that precludes the need for
JSONP/CORS. I'm not sure if the use case here is:
1) JS client
Hi Sergio,
Dont worry about the questions, this a list for help.
I see that nobody:nogroup is the owner of the top folder, i think this is
wrong, change with a chown -R to root:root for the top folder, be sure of all
the files have root:root, and try again.
drwxrwxr-x 2 nobody nogroup 4096
+1 for skipping the metadata container; seems superfluous.
The service type (compute, identity, etc) should definitely be distinct from
the endpoint's type (public, admin, internal, etc). The endpoint type should
also be more easily flexible than it is today -- we've had complaints about
hard
From: Joseph Heck [mailto:he...@me.com]
Sent: Wednesday, April 25, 2012 9:47 AM
To: Nguyen, Liem Manh
Cc: Joe Savak; openstack@lists.launchpad.net (openstack@lists.launchpad.net);
Adam Gandelman
Subject: Re: [Openstack] [Keystone] What exactly are we modeling with endpoints?
This isn't about
How about let's rephrase this question:
Who is actually explicitly using the service catalog (besides just having
keystoneclient find the next auth endpoint)? What complaints do you have?
AKA, trying to pull some data out of it and use it to in some way
discover a service.
From my experiences,
So if what u are talking about is anything RPC/MQ based, then I would say those
are not internal API's.
Once a RPC/MQ mechanism is introduced they don't really become internal API's
anymore (if we are talking about the same API's, haha).
Since other stuff can be reading those messages on the
Could be a misunderstanding there. My fault.
Lets see what happens with volumes. I just hope that the new volume service
doesn't require X whizbang feature which will require everyone to reformat with
newfilesystem-alpha v.1 (questionably stable), or a similar other untested
requirement
Is it reasonable to have a service without any endpoints?
There are no use cases today that I know of that would need a service
represented in the service catalog without endpoints. Since the future is vague
though and each implementation could be different, I don't think we should
require a
So the ability to create a snapshot, rollback to a snapshot and to create a
new snapshot that references a snapshot as its base are strong
candidates for abilities to design for volume drivers. Any device that did
not support this capability would simply state so. Snapshotting would
then
Hi Emilien,
On Wed, Apr 25, 2012 at 9:13 AM, Emilien Macchi emilien.openst...@gmail.com
wrote:
For example, Quantum does not work with Keystone : When nova-network send
an API call to Quantum-server, the token is missing in the HTTP HEADER.
I've disabled Keystone at this time.
That is
I'm not sure it makes sense for a service to have more than one
endpoint. Two different endpoints might as well be two separate services
IMO, even if they directly affect each other.
For example, creating a tenant on the identity admin endpoint makes that
tenant just as available on the identity
On Wed, Apr 25, 2012 at 7:38 AM, Andrew Hutchings and...@linuxjedi.co.ukwrote:
On 12/04/12 13:35, J. Daniel Schmidt wrote:
While testing our SUSE OpenStack packages we hit a nasty bug and
reported it
as: https://bugs.launchpad.net/keystone/+bug/972502
We found out that the underlying
A common use-case for a service to have more than one endpoints is when
there are different regions for different endpoints serving the same service.
This is potentially a place where the endpoints may be discriminated, if the
consumer of the catalogue is geo-aware.
Liem
From:
TL;DR for the below: +1 to what Nick said.
I think both sides here are valid...
Yes, security issues are opened up with these technologies, and they are indeed
rather new, but the use-case for wanting to access the files in this manner
also definitely exists.
Whatever solution is decided
A service can have 0 to N endpoints. Why not? To the end users, what's the
difference between no endpoints and unreachable endpoints anyway. It should
be up to the client to return a more human-readable, actionable error
message.
An endpoint is basically consisted of an URI and a bunch of
Liem,
I think yes, because service is just a logical concept, and endpoint API
may decide to support multiple services (for billing or whatever)...
Can you explain this a bit further? I'm completely lost on what you're
describing.
-Dolph
On Wed, Apr 25, 2012 at 12:13 PM, Nguyen, Liem Manh
Is there a concept of locality in Essex? For example if I stand up a cab that
connects to a certain volume store, and has a particular network range/vlan,
and later set up a second pod or cell and have it be mostly independent
from the first cab. It seems zone-esque but I'm not sure of the
For example, block storage and compute go hand-in-hand in Openstack... But,
what if someone wants to separate them for billing purpose for instance, then
those would become separate services, but the endpoint may be the same... We
could require the endpoints in this case to be different, but,
On another note: Regions.
I acknowledge that there's a real-world problem to be solved here, but A)
no two deployments seem to share the same philosophy on how to describe the
problem or it's complexity, B) some deployments don't have that problem at
all (e.g. devstack).
The concept of a region
I've heard a few people mention pulling messages off the queue, or
communicating via RPC outside of the project, or outside of Python. In theory,
this sounds nice, but the RPC implementations are strictly making sure that A
can execute calls on target B and that responses get back to A.
This
On 04/25/2012 03:22 PM, Eric Windisch wrote:
I've heard a few people mention pulling messages off the queue, or
communicating via RPC outside of the project, or outside of Python. In
theory, this sounds nice, but the RPC implementations are strictly
making sure that A can execute calls on
Hey, sorry y'all. I grepped for SUSPENDED but needed to do it for SHUTOFF.
What can you tell me about SHUTOFF based on the code here?
Yep, not too embarrassed to admit this to 3000+ of you. :)
./nova/api/ec2/cloud.py:vm_states.SHUTOFF: inst_state.SHUTOFF,
./nova/api/ec2/cloud.py:if
andi.abes asked:
Would this also be applicable to the ephemeral instance storage?
An ephemeral instance is essentially a non-persistent clone of a snapshot image.
___
Mailing list: https://launchpad.net/~openstack
Post to :
On Wed, Apr 25, 2012 at 3:39 PM, Caitlin Bestler
caitlin.best...@nexenta.com wrote:
andi.abes asked:
Would this also be applicable to the ephemeral instance storage?
An ephemeral instance is essentially a non-persistent clone of a snapshot
image.
that's an interesting perspective. But
Sure, but then the contract becomes between the notifier and the client,
presumably? I'm not as familiar with the notification system as I should be.
I haven't written a ZeroMQ notifier yet, figuring that task would be better
delayed until the move to openstack-common.
--
Eric Windisch
On
Hi Dan,
Thank you for your quick answer.
I really was looking forward to hear you about my mail.
I have VNC access from the dashboard, and tomorrow I will follow your
tip about manual configuration.
I will let you know about the result.
For the dashboard, I want to try in order to have
On 04/25/2012 03:45 PM, Eric Windisch wrote:
Sure, but then the contract becomes between the notifier and the client,
presumably? I'm not as familiar with the notification system as I should
be.
Right, and to me that's a much different thing than accepting that any
arbitrary application is
Andi Abes wrote:
On Wed, Apr 25, 2012 at 3:39 PM, Caitlin Bestler
caitlin.best...@nexenta.com wrote:
andi.abes asked:
Would this also be applicable to the ephemeral instance storage?
An ephemeral instance is essentially a non-persistent clone of a snapshot
image.
that's an interesting
On Mon, 2012-04-23 at 06:45 -0700, Mike Scherbakov wrote:
Hi Calvin,
Sorry I didn't respond earlier, the email temporarily got lost :)
show us iptables -nL -t nat | grep NAT on the node with nova-network.
(192.168.0.101 is the nova-network node's external address)
DNAT all --
Let me try to summarize:
1. If you are running from a web browser, post requests to hosts or
ports other than the origin are allowed, but the headers cannot be
modified. This prevents the addition of the token from Keystone to
provide single sign on.
2. There are various browser side
Yee,
What are you modeling by saying you can have a service without an endpoint?
What's a service without a means of serving?
-Dolph
On Wed, Apr 25, 2012 at 1:54 PM, Yee, Guang guang@hp.com wrote:
A service can have 0 to N endpoints. Why not? To the end users, what's the
difference
org.openstack.sync__1__size=627965952
org.openstack.sync__1__checksum=224237ee1b9a341ac7d79bcebda0580d
disk_format=qcow2
container_format=bare
is_public=True
org.openstack__1__os_distro=debian.org
org.openstack__1__os_version=6.0.4
org.openstack__1__architecture=x64
org.openstack__1__updated_at=20120425
A few things
I believe config-drive is the way to fix injection problems. I use it and
it works great. (I just wish there was a way to use it from Horizon...)
We'll never be able to inject into every image; also some people don't want
us messing with their images.
Config drive is effectively injection into
If you let me know in a bit more detail what you're looking for, I can
probably whip something up. Email me direct?
Justin
On Wed, Apr 25, 2012 at 6:59 AM, Monty Taylor mord...@inaugust.com wrote:
On 04/24/2012 10:08 PM, Lorin Hochstein wrote:
On Apr 24, 2012, at 4:11 PM, Joe Gordon
The main issue is when the relevant tables are moved into a separate service a
la quantum or cinder. We can't keep referential integrity across multiple
databases, so the foreign keys in this case need to be removed. It leads to an
odd situation when there is still an internal implementation
On Wed, Apr 25, 2012 at 5:17 PM, Vishvananda Ishaya
vishvana...@gmail.comwrote:
The main issue is when the relevant tables are moved into a separate
service a la quantum or cinder. We can't keep referential integrity across
multiple databases, so the foreign keys in this case need to be
Hey - funny story - in responding to Justin I re-read the original email
and realized it was asking for a static low number, which we _can_ do -
at least project-wide. We can't do per-file yet, nor can we fail on a
downward inflection... and I've emailed Justin about that.
If we have consensus on
Hi all,
I was looking at the notification outputs, which are very useful and I was
wondering if the way to say figure out which hypervisor a VM is being built on.
There seems to be the following key: publisher_id: compute.buildingbuild
(event is compute.instance.create.end)
It would seem the
On Thu, Mar 8, 2012 at 11:53 AM, Andrew Bogott abog...@wikimedia.org wrote:
I'm working on an API and implementation to support the creation of
filesystems that are shared among Nova instances.
http://wiki.openstack.org/SharedFS
My hope is to keep this API isolated from core Nova code,
On 4/25/12 4:48 PM, Nathanael Burton wrote:
On Thu, Mar 8, 2012 at 11:53 AM, Andrew Bogottabog...@wikimedia.org wrote:
I'm working on an API and implementation to support the creation of
filesystems that are shared among Nova instances.
http://wiki.openstack.org/SharedFS
My hope is
On Wed, Apr 25, 2012 at 6:04 PM, Andrew Bogott abog...@wikimedia.org wrote:
Nate --
The short answer is: I'm sure that it's straightforward to create a
'private' table which doesn't collide with existing nova tables, but I have
yet to do so.
The longer answer is: Everything about that
One concern I have is this: suppose we find that a code block is
unnecessary, or can be refactored more compactly, but it has test coverage.
Then removing it would make the % coverage fall.
We want to remove the code, but we'd have to add unrelated tests to the
same merge because otherwise the
The notification system is simply 'borrowing' some code from rpc to push
notifications. The notifications have a specified JSON message format,
documented on the wiki: http://wiki.openstack.org/NotificationSystem
As far as the notification drivers, they are very very simple.
On Apr 25,
On Wed, 2012-04-25 at 16:19 -0400, Adam Young wrote:
Kerberos is designed to solve this problem. It has the benefit of being
integrated into the browser. Where Kerberos fails is that: typically
it only allows a single authentication provider (KDC in Kerberso speak)
and it does not work
Looking at the rabbitmq notifier, it actually just wraps rpc (so it is really
an rpc notifier)… it won't work with the ZeroMQ driver because it breaks the
presumption that topics are $topic.$host. Granted, that might have been
presumptuous, but nothing besides the notifier did this. I'd much
You want these events:
scheduler.run_instance.start (generated when scheduling begins)
scheduler.run_instance.scheduled (when a host is selected. one per instance)
scheduler.run_instance.end (all instances placed)
The .scheduled event will have the target hostname in it in the
weighted_host key
Has there been any investigation into using already existing plugin frameworks
and just use those (and/or make those better)?
Just from a quick google search:
http://wehart.blogspot.com/2009/01/python-plugin-frameworks.html
It might be useful to see if we can find one that is generic and
How does everyone build OpenStack disk images? The official documentation
describes a manual process (boot VM with ISO), which is sub-optimal in
terms of repeatability / automation / etc. I'm hoping we can do better!
I posted how I do it on my blog, here:
Hi
Thanks a lot for the responses. I still have some clarifications.
Openstack documentation states (
http://docs.openstack.org/trunk/openstack-compute/admin/content/hypervisor-configuration-basics.html
)
*Hypervisor Configuration Basics*
*The node where the nova-compute service is installed
Great point Justin. I've worked on projects where this has happened repeatedly
and it's a drag.
From: openstack-bounces+tim.simpson=rackspace@lists.launchpad.net
[openstack-bounces+tim.simpson=rackspace@lists.launchpad.net] on behalf of
Justin Santa
I just curious. Is anyone using the VMware functionality in OpenStack?
I'm getting the feeling that it is more of a 'check box' thing of yeah, we
have that hypervisor covered than something that's seriously being used.
If my feeling is wrong, I'd like to know.
On Wed, Apr 25, 2012 at 7:22 PM,
IDEA:
Add pxe boot support to nova (which seems interesting on its own!), and pxe
boot from an installer image, then snapshot it.
OR:
Modify boot from iso image to allow the iso to attach separately (currently it
replaces the root drive in KVM) so that you could boot from an iso but still
On Apr 25, 2012, at 7:22 PM, Atul Gosain wrote:
Hi
Thanks a lot for the responses. I still have some clarifications.
Openstack documentation states
(http://docs.openstack.org/trunk/openstack-compute/admin/content/hypervisor-configuration-basics.html)
Hypervisor Configuration Basics
Justin,
I'm a fan of veewee.
https://github.com/jedi4ever/veewee
Probably some work to support Xen, but should work for building KVM images.
These docs should give a bit better idea.
https://github.com/jedi4ever/veewee/blob/master/doc/definition.md
Hi,
I'm trying to get the s3 interface in Essex working.
I'm using the packages provided in Ubuntu 12.04.
my pipeline order is:
pipeline = catch_errors healthcheck cache swift3 s3token authtoken
keystone proxy-server
[filter:s3token]
paste.filter_factory =
On Thu, Apr 26, 2012 at 5:49 AM, Adam Young ayo...@redhat.com wrote:
Let me try to summarize:
1. If you are running from a web browser, post requests to hosts or
ports other than the origin are allowed, but the headers cannot be
modified. This prevents the addition of the token from
I still think it's a bad idea to inject such values in code. Even with
typical distutils install, you have to respect the prefix which was
provided with code, and if you'll have several installations in your
system, this can lead to some problems. For example, you can install
Keystone with
I'd like the defaults to be configurable by distributors, distutils,
etc. and this is a common pattern with autoconf based projects.
What I don't accept, though, is that we should require users to specify
config options just because we can't figure out a mechanism to get sane
defaults right out
I agree with Mark. In my world, all options should have sane defaults.
--
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/983734
Title:
Keystone fails badly if you miss one
88 matches
Mail list logo
