Re: [Openstack] [HPC] Openstack HPC telecon
Hi John Paul All, 11am EDT sounds perfectly fine with European TX. Regular Confcall format is fine too. Best regards, Patrick Le 6 juil. 2012 19:39, John Paul Walters jwalt...@isi.edu a écrit : Earlier is totally fine. I want to strike a balance with the people on the west coast. How about noon EDT or even 11am EDT? Is that getting too early for the west coast? JP On Jul 6, 2012, at 11:55 AM, Tim Bell wrote: Would it be possible a bit earlier ? This would be 10pm in Europe so it would limit the participation. Tim -Original Message- From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Narayan Desai Sent: 06 July 2012 17:08 To: John Paul Walters Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net) Subject: Re: [Openstack] [HPC] Openstack HPC telecon On Fri, Jul 6, 2012 at 9:51 AM, John Paul Walters jwalt...@isi.edu wrote: Does something like the first Monday of the month at 4:00pm EDT (UTC-4) work? I'm just throwing out that time as something that seems to broadly work on my end, but I'd welcome any input from others. That generally works fine for me. -nld ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Compressed image support ?
hi, all As to the horizon UI, zip and tar.gz image files are supported. Specify an image to upload to the Image Service. Currently only images available via an HTTP URL are supported. The image location must be accessible to the Image Service. Compressed image binaries are supported (.zip and .tar.gz.) My test environment is as follow: 1. LVM as image backend of vms. 2. running vms on Xen in PV mode But when I upload a tar gzipped raw image file, nova just dd from it to logical volume, thus, nova error logged Boot loader didn't return any data! I grepped the nova and glance source code, found nothing about of gz or zip that related to image. This feature is valuable to our use case, for the raw image file is 4GB, but the compressed version is only 400MB. Did I misunderstand the compressed image support? Regards. Wang Li ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Nova can not detached a volume
Hiroki Ishikawa wrote: I have been faced a problem that the volume can not be detached when an instance is booted from a volume with an invalid name. Here is a sequence that the problem happens: [...] Any chance you could file this as a bug at: https://bugs.launchpad.net/nova/+filebug ? This would ensure that we can efficiently track progress towards the fix of this problem. Thanks ! -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] How to speed-up removal of a volume in Openstack Essex
When terminating a volume, openstack default overwrites the complete volume with zero’s for security reasons. This can take a long time, especially with large volumes. If security isn’t an issue in your environment, you can speed-up deletion to only overwrite the first 1GB with zero’s, which will then delete only the mbr, partition table and the first part of the filesystem. See this post ( https://dijks.wordpress.com/2012/07/09/how-to-speedup-removal-of-a-volume/) for a brief tutorial to speed-up removal of a volume if security isn't an issue. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] How to speed-up removal of a volume in Openstack Essex
Hi Heber,thanks for the tip :-) Nuage Co - Razique Mahrouarazique.mahr...@gmail.com Le 9 juil. 2012 à 11:17, Heber Dijks a écrit :When terminating a volume, openstack default overwrites the complete volume with zero’s for security reasons. This can take a long time, especially with large volumes.If security isn’t an issue in your environment, you can speed-up deletion to only overwrite the first 1GB with zero’s, which will then delete only the mbr, partition table and the first part of the filesystem. See this post (https://dijks.wordpress.com/2012/07/09/how-to-speedup-removal-of-a-volume/) for a brief tutorial to speed-up removal of a volume if security isn't an issue. ___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help : https://help.launchpad.net/ListHelp___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] How to speed-up removal of a volume in Openstack Essex
On Mon, Jul 09, 2012 at 11:17:13AM +0200, Heber Dijks wrote: When terminating a volume, openstack default overwrites the complete volume with zero’s for security reasons. This can take a long time, especially with large volumes. If security isn’t an issue in your environment, you can speed-up deletion to only overwrite the first 1GB with zero’s, which will then delete only the mbr, partition table and the first part of the filesystem. See this post ( https://dijks.wordpress.com/2012/07/09/how-to-speedup-removal-of-a-volume/) for a brief tutorial to speed-up removal of a volume if security isn't an issue. On the flipside if security /is/ your concern, then you may well consider fill-with-zeros to be insufficient. The ability to invoke the 'scrub' command, would be quite desirable. It sounds like Nova really ought to have this be all configurable, to choose between none, zeros, or one of the many 'scrub' algorithms. Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] How to speed-up removal of a volume in Openstack Essex
Daniel filed a bug for it (https://bugs.launchpad.net/nova/+bug/1022511), thanks Daniel! So go to Lanuchpad and confirm the bug if it affects you too. Regards, Heber On Mon, Jul 9, 2012 at 11:40 AM, Daniel P. Berrange berra...@redhat.comwrote: On Mon, Jul 09, 2012 at 11:17:13AM +0200, Heber Dijks wrote: When terminating a volume, openstack default overwrites the complete volume with zero’s for security reasons. This can take a long time, especially with large volumes. If security isn’t an issue in your environment, you can speed-up deletion to only overwrite the first 1GB with zero’s, which will then delete only the mbr, partition table and the first part of the filesystem. See this post ( https://dijks.wordpress.com/2012/07/09/how-to-speedup-removal-of-a-volume/ ) for a brief tutorial to speed-up removal of a volume if security isn't an issue. On the flipside if security /is/ your concern, then you may well consider fill-with-zeros to be insufficient. The ability to invoke the 'scrub' command, would be quite desirable. It sounds like Nova really ought to have this be all configurable, to choose between none, zeros, or one of the many 'scrub' algorithms. Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/:| |: http://libvirt.org -o- http://virt-manager.org:| |: http://autobuild.org -o- http://search.cpan.org/~danberr/:| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc:| ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] how to properly get rid of some `nova-manage service list` entries
Hey all, I'm having some old entries in the output of `nova-manage service list`, which I would like to get rid from. One compute, and 2 nova-network items. Is it safe to just DELETE them from the mysql table or is there more involved? Best regards, Christian Parpart. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Nova can not detached a volume
Thierry Carrez wrote: Any chance you could file this as a bug at: https://bugs.launchpad.net/nova/+filebug ? This would ensure that we can efficiently track progress towards the fix of this problem. [...] Thanks for your reply. I added a new bug to launchpad. Please see at: https://bugs.launchpad.net/nova/+bug/1022520 Thanks! -- Hiroki Ishikawa ishikawa...@gmail.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] how to properly get rid of some `nova-manage service list` entries
Hi, you can simply delete them from the mysql services table. Belmiro CERN On Jul 9, 2012, at 12:46 PM, Christian Parpart wrote: Hey all, I'm having some old entries in the output of `nova-manage service list`, which I would like to get rid from. One compute, and 2 nova-network items. Is it safe to just DELETE them from the mysql table or is there more involved? Best regards, Christian Parpart. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [CHEF] Clarification on osops/chef-repo/roles/nova-compute.rb
Vish and Ron, just getting back to this... see inline continued
questions for you both.
On 07/02/2012 04:24 PM, Vishvananda Ishaya wrote:
On Jul 2, 2012, at 7:28 AM, Jay Pipes wrote:
Hi Ron, cc'ing the openstack ML for extra eyes and opinions...
So, Nati and I are looking to use either the osops chef-repo or
something similar as the basis of the new TryStack zone chef deployment.
I've been going through the recipes and roles and I have a question on
the nova-compute *role*:
https://github.com/osops/chef-repo/blob/master/roles/nova-compute.rb
I'm wondering why the nova-api recipe is in the runlist for nova-compute?
Because metadata needs to run on the compute hosts in the default layout.
This should
be switched to use nova-api-metadata instead of nova-api, but the split out
hasn't been done yet.
OK, I will work on splitting this out a bit more effectively.
One additional question, though. In opening up the
/cookbooks/nova/recipes/nova/compute.rb file, you will notice this at
the top:
include_recipe nova::api
Therefore, unless I am mistaken, the nova-compute *role*'s runlist
actually doesn't need to contain both nova-api AND nova-compute since
apparently the nova-compute *recipe* already includes all of the
nova-api recipe.
Would you agree with that?
In addition, I was wondering if y'all had considered making more use of
roles instead of recipes to allow most of the attribute assignment and
variation to be in the combination of roles assigned to a host, instead
of recipes combined in a role?
For example, right now, there is a nova-controller role that looks
like this:
name nova-controller
description Nova controller node (vncproxy + rabbit)
run_list(
role[base],
recipe[nova::controller]
)
Because most of the special sauce is in the nova::controller recipe, I
have to go into that recipe to see what the role is composed of:
include_recipe mysql::server
include_recipe openssh::default
include_recipe rabbitmq::default
include_recipe keystone::server
include_recipe glance::registry
include_recipe glance::api
include_recipe nova::nova-setup
include_recipe nova::scheduler
include_recipe nova::api
if platform?(%w{fedora})
# Fedora skipping vncproxy for right now
else
include_recipe nova::vncproxy
end
But what this recipe really is is an opinionated description of a
controller role. If the role was, instead, structured like so:
name nova-controller
description Nova Controller - All major API services and control
servers like MySQL and Rabbit
run_list(
role[base],
recipe[mysql::server],
recipe[openssh::default],
recipe[rabbitmq::default],
recipe[keystone::server],
recipe[glance::api],
recipe[glance::registry],
recipe[nova::scheduler],
recipe[nova::api],
)
Then the deployer can more easily switch up the way they deploy
OpenStack servers by merely changing the role -- say, removing the
Rabbit service and putting it somewhere else -- WITHOUT having to modify
a recipe in a Git submodule in the upstream cookbooks.
Furthermore, if we broke out more roles -- such as control-services
which might be MySQL and Rabbit only -- than we could make the super
roles ,like the nova-controller role above, more of a put this and
that role together, like so:
name nova-controller
description Nova Controller - All major API services and control
servers like MySQL and Rabbit
run_list(
role[base],
role[control_services],
recipe[keystone::server],
recipe[glance::api],
recipe[glance::registry],
recipe[nova::scheduler],
recipe[nova::api],
)
This all makes sense to me. Ron?
Ron, any disagreement here?
Finally, I've noticed that there are aren't any HA options in the osops
recipes -- specifically around MySQL. Are there plans to do so? We use
heartbeat/Pacemaker/DRBD in the original TryStack cookbooks [1] and
environments to get simple HA solutions up and would love to see those
in the upstream.
Either of you, any thoughts on this front?
Thanks!
-jay
Thanks and all the best guys,
-jay
[1]
https://github.com/trystack/openstack-chef/tree/stable/diablo/cookbooks/heartbeat
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Glance/Swift tenant specific storage
- Original Message - From: David Kranz david.kr...@qrclab.com To: Dan Prince dpri...@redhat.com Sent: Monday, July 9, 2012 9:15:00 AM Subject: Re: [Openstack] Glance/Swift tenant specific storage Dan, I am involved in a project (not Glance) that is doing something similar to this though it is at an early stage. One unresolved issue was what happens when the auth_token used to access Swift expires? If the auth_token expired the request would fail. I'm not sure how common this scenario would be however. I suppose if you are expiring tokens very quickly then it could happen... otherwise it would take a really long Glance task to be able to hit this right? Unless Glance stores the user's password, and in a reversible way, how does it get a new token? It can't. The user would have to re-submit the request to upload, download, or access the image data with a fresh token. Note: There are still some Glance tasks like delayed delete which already required a username:password (stored in a config file) to work. With Multi-tenant this would still be the case. One thing to note: Glance isn't storing auth_tokens in this new implementation. It simply obtains the token from the incoming request and uses that to access Swift accordingly. This is actually the same thing Nova does to access Glance... so presumably any token expiration issue you'd hit with Glance-Swift integration would also potentially happen between Nova-Glance. This seems like a keystone use case that is not clear unless I am missing something. -David On 7/8/2012 9:59 PM, Dan Prince wrote: I started working on the Glance swift-tenant-specific-storage blueprint last week. I've got a working branch in play here: https://github.com/dprince/glance/commits/swift_multi_tenant3 Some details on how I've done things so far: * Update Glance so that it uses the service catalog for each user to obtain the Swift storage URL. * Provide backend stores access to the context. Glance Essex doesn't give stores access to the RequestContext (auth token). We'll need this information for tenant specific storage if we want to be able to access individual swift accounts. * Store images in separate containers. Swift only allows individual ACL's to be set per container... not per object. As such it appears we'll need to store each image in a separate container in order to support setting public and/or individual read/write access on each image. * Set 'public' access for images in Swift. * Set 'private' read and/or write access for Glance image members which have been granted access to specific images. * Delayed delete (scrubber) will require an authenticated context in order to delete Swift images from the backend. Glance can either be make to grant write access to this account (for all images) or an administrative Swift account could be used to run the delayed delete operation. * Maintain full support with the existing single tenant Glance swift storage scheme. I made some general implementation notes up on this wiki page as well: http://wiki.openstack.org/GlanceSwiftTenantSpecificStorage I'm anxious to get things up for review but before I do so I wanted to ask if this implementation looks reasonable? Any thoughts or feedback? Dan ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] QA for Live Migration
Hi, There are currently no tests for live migration. I imagine that the reason is because there is very poor documentation on the os-migrateLive API extension. I'd be happy to help you in writing the tests. Cool, thanks. I'd love some help in identifying some documentation ... we need to know the contractual state changes that need to be asserted in the Tempest tests. Additionally, I'd like to point out that there is a lot of confusion as to what is different between the standard Compute API call to migrate a server (POST /servers/SERVER_ID/action with 'migrate' action...) and the live migration extension. ... +1 Renuka and I are looking at proposing a blueprint to try and sort out some of this confusion. I think this is the current situation: - historically XenAPI had migrate, Libvirt had live migrate - But by end of Folsom we should have both having both - Live migration was originally only nova-manage controlled - Migrate is useful, but requires things like passwordless ssh - We could re-implement migrate as snapshot and restart - Above is also true for Resize - But there may be billing implications for the above changes - Live-migrate is more useful than migrate - But live-migrate not always possible (miss matched CPUs, etc) - Ideally we would have single migrate/live-migrate API Possible first steps for Folsom: - Extend the migrate API to support a live and live-block migration options - Maybe add live with fallback to non-live option - Maybe above should be the default, add a non-live option - Fully document the expanded migrate API for Folsom Does this sound reasonable? Cheers, John ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] QA for Live Migration
On 07/09/2012 09:35 AM, John Garbutt wrote: Renuka and I are looking at proposing a blueprint to try and sort out some of this confusion. I think this is the current situation: - historically XenAPI had migrate, Libvirt had live migrate - But by end of Folsom we should have both having both Yes, but what is the difference between the two? - Live migration was originally only nova-manage controlled - Migrate is useful, but requires things like passwordless ssh - We could re-implement migrate as snapshot and restart This seems entirely reasonable. - Above is also true for Resize That is actually how it already happens, with the CONFIRM_RESIZE state acting as the quiescence point for the operation. - But there may be billing implications for the above changes - Live-migrate is more useful than migrate Why? :) - But live-migrate not always possible (miss matched CPUs, etc) - Ideally we would have single migrate/live-migrate API This would be my preference. The way it stands today is entirely confusing. Possible first steps for Folsom: - Extend the migrate API to support a live and live-block migration options Please explain these differences. - Maybe add live with fallback to non-live option Again, need to know what the difference is you envision here? - Maybe above should be the default, add a non-live option - Fully document the expanded migrate API for Folsom Oh, definitely. :) Best, -jay Does this sound reasonable? Cheers, John ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] QA for Live Migration
- historically XenAPI had migrate, Libvirt had live migrate - But by end of Folsom we should have both having both Yes, but what is the difference between the two? Got you. I think this is right: Migration: - shutdown the VM - move current disk to the destination - start VM - user sees reboot, and sees downtime - resize is very similar, just starts as different flavour Live-migration: - snapshot running state - copy memory + CPU state to other machine - start - user sees VM pause for a small amount of time - assumes VM is on shared storage, so disks are not moved Block-migration and live-migration: - as above, but disk needs to be copied Live migration can only happen when the source and destination CPU matches Hopefully my comments make more sense now? - Live migration was originally only nova-manage controlled - Migrate is useful, but requires things like passwordless ssh - We could re-implement migrate as snapshot and restart This seems entirely reasonable. - Above is also true for Resize That is actually how it already happens, with the CONFIRM_RESIZE state acting as the quiescence point for the operation. I thought it just did a copy and left the old image on the previous machine, but that might just be XenAPI. I was more thinking upload the snapshot into glance as a private image, rather than do a 'behind the scenes' copy between hypervisors. - But live-migrate not always possible (miss matched CPUs, etc) - Ideally we would have single migrate/live-migrate API This would be my preference. The way it stands today is entirely confusing. Cool ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [OpenStack][Nova] Live Migration Error
I see pre_live_migration in destination compute log, so migration at
least started.
Since there are no errors in either compute log, is it possible that
migration is taking long ? (Just a possibility)
When you say migration fails what error did you get ?
-Mandar
On Mon, Jul 9, 2012 at 7:39 PM, Leander Bessa Beernaert leande...@gmail.com
wrote:
Ok, so i've updated to the test packages from
The migration still fails, but i see no errors in the logs. I'm trying to
migrate a VM with the m1.tiny flavor from one machine to another. Their
hardware are identical and they have more than enough resources to support
the m1.tiny flavor:
cloud35 (total) 43867 186
cloud35 (used_now) 0 312 5
cloud35 (used_max) 0 0 0
These are the logs from the origin compute node:
http://paste.openstack.org/show/19319/ and the destination compute
node: http://paste.openstack.org/show/19318/ . The scheduler's log has no
visible errors or stack traces.
I'm still using nfsv4.
Any ideas?
On Fri, Jul 6, 2012 at 7:57 PM, Leander Bessa Beernaert
leande...@gmail.com wrote:
Thanks for the tip, it's a better than nothing :)
Regards,
Leander
On Fri, Jul 6, 2012 at 6:32 PM, Mandar Vaze / मंदार वझे
mandarv...@gmail.com wrote:
Not sure if you are able to debug this, but a while ago there was a bug
where instance.id was passed where instance.uuid was expected. This
used to cause some problem.
It looks like you are using distribution package rather than devstack
installation, so it is likely that the issue is now fixed. Can you try
latest packages (and/or try devstack if you can)
I wish I could help more.
-Mandar
On Fri, Jul 6, 2012 at 3:26 PM, Leander Bessa Beernaert
leande...@gmail.com wrote:
Hello,
I've recently setup a system to test out the live migration feature. So
far i've been able to launch the instances with the shared nfs folder.
However, when i run the live-migration command i encounter this error in
the destination compute node:
2012-07-05 09:33:48 ERROR nova.manager [-] Error during
ComputeManager.update_available_resource: Domain not found: no domain with
matching id 2
2012-07-05 09:33:48 TRACE nova.manager Traceback (most recent call
last):
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/manager.py, line 155, in
periodic_tasks
2012-07-05 09:33:48 TRACE nova.manager task(self, context)
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 2409, in
update_available_resource
2012-07-05 09:33:48 TRACE nova.manager
self.driver.update_available_resource(context, self.host)
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line
1936, in update_available_resource
2012-07-05 09:33:48 TRACE nova.manager 'vcpus_used':
self.get_vcpu_used(),
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line
1743, in get_vcpu_used
2012-07-05 09:33:48 TRACE nova.manager dom =
self._conn.lookupByID(dom_id)
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/libvirt.py, line 2363, in lookupByID
2012-07-05 09:33:48 TRACE nova.manager if ret is None:raise
libvirtError('virDomainLookupByID() failed', conn=self)
2012-07-05 09:33:48 TRACE nova.manager libvirtError: Domain not found:
no domain with matching id 2
Any ideas on how to solve this?
Regards,
Leander
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [OpenStack][Nova] Live Migration Error
There is no error, it just doesn't do anything :s.
I've left the instance alone for 3 hours now and it's still stuck on the
original compute node.
On Mon, Jul 9, 2012 at 5:55 PM, Mandar Vaze / मंदार वझे
mandarv...@gmail.com wrote:
I see pre_live_migration in destination compute log, so migration at
least started.
Since there are no errors in either compute log, is it possible that
migration is taking long ? (Just a possibility)
When you say migration fails what error did you get ?
-Mandar
On Mon, Jul 9, 2012 at 7:39 PM, Leander Bessa Beernaert
leande...@gmail.com wrote:
Ok, so i've updated to the test packages from
The migration still fails, but i see no errors in the logs. I'm trying to
migrate a VM with the m1.tiny flavor from one machine to another. Their
hardware are identical and they have more than enough resources to support
the m1.tiny flavor:
cloud35 (total) 43867 186
cloud35 (used_now) 0 312 5
cloud35 (used_max) 0 0 0
These are the logs from the origin compute node:
http://paste.openstack.org/show/19319/ and the destination compute
node: http://paste.openstack.org/show/19318/ . The scheduler's log has
no visible errors or stack traces.
I'm still using nfsv4.
Any ideas?
On Fri, Jul 6, 2012 at 7:57 PM, Leander Bessa Beernaert
leande...@gmail.com wrote:
Thanks for the tip, it's a better than nothing :)
Regards,
Leander
On Fri, Jul 6, 2012 at 6:32 PM, Mandar Vaze / मंदार वझे
mandarv...@gmail.com wrote:
Not sure if you are able to debug this, but a while ago there was a bug
where instance.id was passed where instance.uuid was expected. This
used to cause some problem.
It looks like you are using distribution package rather than devstack
installation, so it is likely that the issue is now fixed. Can you try
latest packages (and/or try devstack if you can)
I wish I could help more.
-Mandar
On Fri, Jul 6, 2012 at 3:26 PM, Leander Bessa Beernaert
leande...@gmail.com wrote:
Hello,
I've recently setup a system to test out the live migration feature.
So far i've been able to launch the instances with the shared nfs folder.
However, when i run the live-migration command i encounter this error in
the destination compute node:
2012-07-05 09:33:48 ERROR nova.manager [-] Error during
ComputeManager.update_available_resource: Domain not found: no domain
with
matching id 2
2012-07-05 09:33:48 TRACE nova.manager Traceback (most recent call
last):
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/manager.py, line 155, in
periodic_tasks
2012-07-05 09:33:48 TRACE nova.manager task(self, context)
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 2409, in
update_available_resource
2012-07-05 09:33:48 TRACE nova.manager
self.driver.update_available_resource(context, self.host)
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line
1936, in update_available_resource
2012-07-05 09:33:48 TRACE nova.manager 'vcpus_used':
self.get_vcpu_used(),
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line
1743, in get_vcpu_used
2012-07-05 09:33:48 TRACE nova.manager dom =
self._conn.lookupByID(dom_id)
2012-07-05 09:33:48 TRACE nova.manager File
/usr/lib/python2.7/dist-packages/libvirt.py, line 2363, in lookupByID
2012-07-05 09:33:48 TRACE nova.manager if ret is None:raise
libvirtError('virDomainLookupByID() failed', conn=self)
2012-07-05 09:33:48 TRACE nova.manager libvirtError: Domain not
found: no domain with matching id 2
Any ideas on how to solve this?
Regards,
Leander
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] PEP8 checks
On Mon, 2012-07-02 at 08:15 -0400, Monty Taylor wrote: It's not really expected, and I honestly don't understand why run_tests.sh -p would have problems running pep8. Although we do not use run_tests.sh for anything in jenkins, we have not done anything to disable or change what it's doing. I need to point out that run_tests.sh -p doesn't run straight-up pep8; it monkey-patches the pep8 tool to include several HACKING-compliance tests. Ever since tox stopped using this version of pep8, several HACKING-compliance issues have crept into the code base. -- Kevin L. Mitchell kevin.mitch...@rackspace.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Inaugurating the new Development list
Hello folks, following up on the creation the new mailing list for OpenStack Development as discussed and agreed on http://openstack.markmail.org/thread/6a5yyel5qo3moskq The mailing list is on: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev About this list currently says[1]: This list for the developers of OpenStack to discuss development issues and roadmap. It is focused on the next release of OpenStack: you should post on this list if you are a contributor to OpenStack or are very familiar with OpenStack development and want to discuss very precise topics, contribution ideas and similar. Do not ask support requests on this list. All current OpenStack developers should subscribe to that list immediately and start using it next Monday. Sign up, update your filters so that we can use the new shiny toys. /stef [1] suggestions to improve it are welcome. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Compressed image support ?
Hi Wang, Horizon simply uses the Python interface to Glance and tells it to create the image. Glance supports creating images from remote locations that are in a compressed format. There are examples in the Glance documentation here: https://github.com/openstack/glance/blob/master/doc/source/glance.rst#examples-of-uploading-different-kinds-of-images and in the Glance binary itself here: https://github.com/openstack/glance/blob/master/bin/glance#L190 So this is widely supported and documented in Glance. The caveats are that through Horizon, the file MUST be accessible via the network configuration where Glance resides, if it is not accessible due to network configuration or something else, it will fail but seem to have succeeded. Also, you need to make sure you are linking DIRECTLY to the image itself, as if it is a redirect or any other HTTP response besides the file, Glance will still create an image out of it and it will seem to have worked. Sometimes you can even launch said instances that are totally invalid. (During my testing of this I was able to successfully launch instances that were just the HTTP data from 302 redirects.) I would first confirm that where Horizon is installed is able to communicate to where you are trying to copy the image from, and that the link you are using for the image is, in fact, a valid binary and not some other HTTP response. John Postlethwait Nebula, Inc. On Monday, July 9, 2012 at 1:04 AM, Wang Li wrote: hi, all As to the horizon UI, zip and tar.gz image files are supported. Specify an image to upload to the Image Service. Currently only images available via an HTTP URL are supported. The image location must be accessible to the Image Service. Compressed image binaries are supported (.zip and .tar.gz.) My test environment is as follow: 1. LVM as image backend of vms. 2. running vms on Xen in PV mode But when I upload a tar gzipped raw image file, nova just dd from it to logical volume, thus, nova error logged Boot loader didn't return any data! I grepped the nova and glance source code, found nothing about of gz or zip that related to image. This feature is valuable to our use case, for the raw image file is 4GB, but the compressed version is only 400MB. Did I misunderstand the compressed image support? Regards. Wang Li ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OVF vs. bare container formats for qcow2 images
That's correct. If there's an .ovf, it's currently ignored. It's also not generated when we upload images (snapshots). I'm sure there's plans in someone's head to implement that support at some point.. but right now we expect the .vhds to have specific names in the tar file. - Chris On Jul 8, 2012, at 6:01 PM, Lorin Hochstein wrote: Paul: I assume you're using XenServer? When I grepped through the code, there appears to be a XenServer plugin for glance for supporting tar balls that could be OVAs, but don't necessarily contain the OVF file (?). Here's the code: https://github.com/openstack/nova/blob/stable/essex/plugins/xenserver/xenapi/etc/xapi.d/plugins/glance#L365 Take care, Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.comhttps://www.nimbisservices.com/ On Jul 5, 2012, at 11:22 AM, Paul Voccio wrote: Lorin, We've been using OVA packages since the beginning. I believe there is a flag in glance for this. Thanks, ~pvo Paul Voccio paul.voc...@rackspace.commailto:paul.voc...@rackspace.com 770-335-2143 (c) pvo on #openstack ಠ_ಠ On Jul 3, 2012, at 9:07 PM, Lorin Hochstein wrote: On Jun 29, 2012, at 9:53 PM, Adam Young wrote: On 04/01/2012 11:15 AM, Lorin Hochstein wrote: On Mar 29, 2012, at 12:40 PM, Daniel P. Berrange wrote: On Wed, Mar 28, 2012 at 04:41:28PM -0400, Lorin Hochstein wrote: All: Given that I have a qcow2 image from somewhere (e.g., downloaded it from a uec-images.ubuntu.comhttp://uec-images.ubuntu.com/, created one from a raw image using qemu-img) that i want to add to glance: 1. How can I tell whether it's an ovf or bare container format? You are mixing up terminology here. Disk image formats are things like raw, qcow2, vmdk, etc. OVF refers to the format of a metadata file provided alongside the disk image, which describes various requirements for running the image. The two are not tied together at all, merely complementary to each other. Thanks, that clears things up. I was confused by this language, which sounded to me like the metadata was embedded in the disk image file: http://glance.openstack.org/formats.html The container format refers to whether the virtual machine image is in a file format that also contains metadata about the actual virtual machine. In addition, the docs have examples like this, which clearly aren't meaningful: http://glance.openstack.org/glance.html#important-information-about-uploading-images Just to add to the confusion the OVF can contain both the metadata file and the disk image file in a single archived file. An OVF package consists of several files, placed in one directory. A one-file alternative is the OVA package, which is a TAR file with the OVF directory inside. http://en.wikipedia.org/wiki/Open_Virtualization_Format#Technical_description Does anybody know if OpenStack (nova+glance) currently supports OVA packages? Take care, Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.comhttps://www.nimbisservices.com/ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Inaugurating the new Development list
Hi, And what happens to openstack@lists.launchpad.net then? Cheers!! Atul From: openstack-bounces+atul.jha=csscorp@lists.launchpad.net [openstack-bounces+atul.jha=csscorp@lists.launchpad.net] on behalf of Stefano Maffulli [stef...@openstack.org] Sent: Tuesday, July 10, 2012 12:52 AM To: Dev, OpenStack Subject: [Openstack] Inaugurating the new Development list Hello folks, following up on the creation the new mailing list for OpenStack Development as discussed and agreed on http://openstack.markmail.org/thread/6a5yyel5qo3moskq The mailing list is on: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev About this list currently says[1]: This list for the developers of OpenStack to discuss development issues and roadmap. It is focused on the next release of OpenStack: you should post on this list if you are a contributor to OpenStack or are very familiar with OpenStack development and want to discuss very precise topics, contribution ideas and similar. Do not ask support requests on this list. All current OpenStack developers should subscribe to that list immediately and start using it next Monday. Sign up, update your filters so that we can use the new shiny toys. /stef [1] suggestions to improve it are welcome. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp http://www.csscorp.com/common/email-disclaimer.php ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Inaugurating the new Development list
On Mon 09 Jul 2012 01:48:25 PM PDT, Atul Jha wrote: And what happens to openstack@lists.launchpad.net then? good question: at the moment nothing happens, this list will remain active. According to the new mailing list layout[1], it will be named 'General' but it will remain as it is for the time being. there is a general agreement though that in the future all the lists hosted on launchpad should migrate to the new mailing list server. I'd say lets stabilize the new development list and start thinking about moving stuff around soon after that's done. /stef [1] http://wiki.openstack.org/MailingLists ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Call for comments and testing: prototype for OpenStack Document translation process
Hi, team I created a prototype of document translation, to verify the whole document translation process: slicing a doc, uploading to transifex, translating, downloading to local disk, merging the translation back into DocBook, and generating translated PDF/HTML. The source codes are in https://github.com/daisy-ycguo/openstack-manuals-i18n. ( It's a copy of openstack-manuals, not the latest version, just for testing ) The document is here: https://gist.github.com/3037139. The translation start point is here: https://www.transifex.com/projects/p/openstack-manuals-i18n/ You can try to create a Chinese version of api-quick-start and openstack-api-programming following the guidance in https://gist.github.com/3037139 as a coordinator. If you meet with any problems, please let me know. Following topics are under discussion: a Whether to use a separate repository for each language I personally don't prefer that, because separate repository will make the synchronization very complex. In this prototype, I only keep the English DocBook and a serials of PO files. The latest Chinese DocBook can be generated from these resources. b How to handle when the original English doc book is updated I'm investigating it. c How to make the process automatically I think we need CI team's help, to see which steps can be integrated with Jenkins. Regards Daisy___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] PEP8 checks
On Mon, Jul 02, 2012 at 08:28:04AM -0400, Monty Taylor wrote: On 07/02/2012 06:46 AM, John Garbutt wrote: Hi, I noticed I can now run the pep8 tests like this (taken from Jenkins job): tox -v -epep8 ... pep8: commands succeeded congratulations :) But the old way to run tests seems to fail: ./run-tests.sh -p ... File /home/johngar/openstack/nova/.venv/local/lib/python2.7/site-packages/pep8.py, line 1220, in check_logical for result in self.run_check(check, argument_names): TypeError: 'NoneType' object is not iterable Is this expected? Did I just miss an email about this change? I cannot reproduce this on my system. Can you run bash -x run_tests.sh -p and pastebin the output? Also, tools/with_venv.sh pep8 --version just to be sure. Hi, The issue is that as of a recent change to upstream pep8 [1], the additional pep8 rules in tools/hacking.py need to be changed from returns to yields.. :( [1] https://github.com/jcrocholl/pep8/commit/b9f72b16011aac981ce9e3a47fd0ffb1d3d2e085 Kind Regards, Dave Walker dave.wal...@canonical.com Engineering Manager, Ubuntu Server Infrastructure signature.asc Description: Digital signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] PEP8 checks
On Mon, Jul 9, 2012 at 3:01 PM, Dave Walker davewal...@ubuntu.com wrote: On Mon, Jul 02, 2012 at 08:28:04AM -0400, Monty Taylor wrote: On 07/02/2012 06:46 AM, John Garbutt wrote: Hi, I noticed I can now run the pep8 tests like this (taken from Jenkins job): tox -v -epep8 ... pep8: commands succeeded congratulations :) But the old way to run tests seems to fail: ./run-tests.sh -p ... File /home/johngar/openstack/nova/.venv/local/lib/python2.7/site-packages/pep8.py, line 1220, in check_logical for result in self.run_check(check, argument_names): TypeError: 'NoneType' object is not iterable Is this expected? Did I just miss an email about this change? I cannot reproduce this on my system. Can you run bash -x run_tests.sh -p and pastebin the output? Also, tools/with_venv.sh pep8 --version just to be sure. Hi, The issue is that as of a recent change to upstream pep8 [1], the additional pep8 rules in tools/hacking.py need to be changed from returns to yields.. :( Proof of Concept: https://review.openstack.org/#/c/9569 [1] https://github.com/jcrocholl/pep8/commit/b9f72b16011aac981ce9e3a47fd0ffb1d3d2e085 Kind Regards, Dave Walker dave.wal...@canonical.com Engineering Manager, Ubuntu Server Infrastructure ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] PEP8 checks
- Original Message - From: Dave Walker davewal...@ubuntu.com To: Monty Taylor mord...@inaugust.com Cc: openstack@lists.launchpad.net, John Garbutt john.garb...@citrix.com Sent: Monday, July 9, 2012 6:01:19 PM Subject: Re: [Openstack] PEP8 checks On Mon, Jul 02, 2012 at 08:28:04AM -0400, Monty Taylor wrote: On 07/02/2012 06:46 AM, John Garbutt wrote: Hi, I noticed I can now run the pep8 tests like this (taken from Jenkins job): tox -v -epep8 ... pep8: commands succeeded congratulations :) But the old way to run tests seems to fail: ./run-tests.sh -p ... File /home/johngar/openstack/nova/.venv/local/lib/python2.7/site-packages/pep8.py, line 1220, in check_logical for result in self.run_check(check, argument_names): TypeError: 'NoneType' object is not iterable Is this expected? Did I just miss an email about this change? I cannot reproduce this on my system. Can you run bash -x run_tests.sh -p and pastebin the output? Also, tools/with_venv.sh pep8 --version just to be sure. Hi, The issue is that as of a recent change to upstream pep8 [1], the additional pep8 rules in tools/hacking.py need to be changed from returns to yields.. :( This brings up a good point. Why are we following the latest pep8 release so closely in Nova? The latest release is hardly a month old and we are already using it? We aren't necessarily doing the same for all the other OpenStack projects... (nor am I suggesting that we do). So why Nova? I'm not convinced the latest pep8 features really provide us enough benefit that we need to bump our pep8 baseline every month or two. in fact they may be hurting us in terms of churn, extra work, back-portability of upstream patches, etc. Ultimately is tracking the latest pep8 really worth it? [1] https://github.com/jcrocholl/pep8/commit/b9f72b16011aac981ce9e3a47fd0ffb1d3d2e085 Kind Regards, Dave Walker dave.wal...@canonical.com Engineering Manager, Ubuntu Server Infrastructure ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Bandwidth limit
Hi Everyone! I want to know if there is a table or something that contains information about the bandwidth of each tenant, to billing purposes. There are a way to limit the bandwith of the tenants?? Thanks in Advance! ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Compressed image support ?
John Postlethwait wrote: ... Also, you need to make sure you are linking DIRECTLY to the image itself, as if it is a redirect or any other HTTP response besides the file, Glance will still create an image out of it and it will seem to have worked. Sometimes you can even launch said instances that are totally invalid. (During my testing of this I was able to successfully launch instances that were just the HTTP data from 302 redirects.) Why would the Glance client treat an HTTP 302 redirect as a 2xx? That seems rather odd behavior, and less like a feature and more like a bug, to me, if true. From the looks of the code, a RedirectException should be thrown. Cheers, Christopher Ferris IBM Distinguished Engineer, CTO Industry and Cloud Standards Member, IBM Academy of Technology IBM Software Group, Standards Strategy email: chris...@us.ibm.com Twitter: christo4ferris phone: +1 508 234 2986 -openstack-bounces+chrisfer=us.ibm@lists.launchpad.net wrote: - To: Wang Li fox...@gmail.com From: John Postlethwait Sent by: openstack-bounces+chrisfer=us.ibm@lists.launchpad.net Date: 07/09/2012 03:38PM Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Compressed image support ? Hi Wang, Horizon simply uses the Python interface to Glance and tells it to create the image. Glance supports creating images from remote locations that are in a compressed format. There are examples in the Glance documentation here: https://github.com/openstack/glance/blob/master/doc/source/glance.rst#exa mples-of-uploading-different-kinds-of-images and in the Glance binary itself here: https://github.com/openstack/glance/blob/master/bin/glance#L190 So this is widely supported and documented in Glance. The caveats are that through Horizon, the file MUST be accessible via the network configuration where Glance resides, if it is not accessible due to network configuration or something else, it will fail but seem to have succeeded. Also, you need to make sure you are linking DIRECTLY to the image itself, as if it is a redirect or any other HTTP response besides the file, Glance will still create an image out of it and it will seem to have worked. Sometimes you can even launch said instances that are totally invalid. (During my testing of this I was able to successfully launch instances that were just the HTTP data from 302 redirects.) I would first confirm that where Horizon is installed is able to communicate to where you are trying to copy the image from, and that the link you are using for the image is, in fact, a valid binary and not some other HTTP response. John Postlethwait Nebula, Inc. On Monday, July 9, 2012 at 1:04 AM, Wang Li wrote: hi, all As to the horizon UI, zip and tar.gz image files are supported. Specify an image to upload to the Image Service. Currently only images available via an HTTP URL are supported. The image location must be accessible to the Image Service. Compressed image binaries are supported (.zip and .tar.gz.) My test environment is as follow: 1. LVM as image backend of vms. 2. running vms on Xen in PV mode But when I upload a tar gzipped raw image file, nova just dd from it to logical volume, thus, nova error logged Boot loader didn't return any data! I grepped the nova and glance source code, found nothing about of gz or zip that related to image. This feature is valuable to our use case, for the raw image file is 4GB, but the compressed version is only 400MB. Did I misunderstand the compressed image support? Regards. Wang Li ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Compressed image support ?
Hi Wang Li, I believe so far there is no compressed RAW image support. Please check https://bugs.launchpad.net/nova/+bug/745985 for detail. -- unicell On Mon, Jul 9, 2012 at 4:04 PM, Wang Li fox...@gmail.com wrote: hi, all As to the horizon UI, zip and tar.gz image files are supported. Specify an image to upload to the Image Service. Currently only images available via an HTTP URL are supported. The image location must be accessible to the Image Service. Compressed image binaries are supported (.zip and .tar.gz.) My test environment is as follow: 1. LVM as image backend of vms. 2. running vms on Xen in PV mode But when I upload a tar gzipped raw image file, nova just dd from it to logical volume, thus, nova error logged Boot loader didn't return any data! I grepped the nova and glance source code, found nothing about of gz or zip that related to image. This feature is valuable to our use case, for the raw image file is 4GB, but the compressed version is only 400MB. Did I misunderstand the compressed image support? Regards. Wang Li ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Compressed image support ?
Filed that bug a month ago: https://bugs.launchpad.net/glance/+bug/1009248 Patches welcome. ;-) - Gabriel -Original Message- From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net [mailto:openstack- bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of Christopher B Ferris Sent: Monday, July 09, 2012 7:41 PM To: openstack@lists.launchpad.net Subject: Re: [Openstack] Compressed image support ? John Postlethwait wrote: ... Also, you need to make sure you are linking DIRECTLY to the image itself, as if it is a redirect or any other HTTP response besides the file, Glance will still create an image out of it and it will seem to have worked. Sometimes you can even launch said instances that are totally invalid. (During my testing of this I was able to successfully launch instances that were just the HTTP data from 302 redirects.) Why would the Glance client treat an HTTP 302 redirect as a 2xx? That seems rather odd behavior, and less like a feature and more like a bug, to me, if true. From the looks of the code, a RedirectException should be thrown. Cheers, Christopher Ferris IBM Distinguished Engineer, CTO Industry and Cloud Standards Member, IBM Academy of Technology IBM Software Group, Standards Strategy email: chris...@us.ibm.com Twitter: christo4ferris phone: +1 508 234 2986 -openstack-bounces+chrisfer=us.ibm@lists.launchpad.net wrote: -openstack-bounces+- To: Wang Li fox...@gmail.com From: John Postlethwait Sent by: openstack-bounces+chrisfer=us.ibm@lists.launchpad.net Date: 07/09/2012 03:38PM Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Compressed image support ? Hi Wang, Horizon simply uses the Python interface to Glance and tells it to create the image. Glance supports creating images from remote locations that are in a compressed format. There are examples in the Glance documentation here: https://github.com/openstack/glance/blob/master/doc/source/glance.rst# e xa mples-of-uploading-different-kinds-of-images and in the Glance binary itself here: https://github.com/openstack/glance/blob/master/bin/glance#L190 So this is widely supported and documented in Glance. The caveats are that through Horizon, the file MUST be accessible via the network configuration where Glance resides, if it is not accessible due to network configuration or something else, it will fail but seem to have succeeded. Also, you need to make sure you are linking DIRECTLY to the image itself, as if it is a redirect or any other HTTP response besides the file, Glance will still create an image out of it and it will seem to have worked. Sometimes you can even launch said instances that are totally invalid. (During my testing of this I was able to successfully launch instances that were just the HTTP data from 302 redirects.) I would first confirm that where Horizon is installed is able to communicate to where you are trying to copy the image from, and that the link you are using for the image is, in fact, a valid binary and not some other HTTP response. John Postlethwait Nebula, Inc. On Monday, July 9, 2012 at 1:04 AM, Wang Li wrote: hi, all As to the horizon UI, zip and tar.gz image files are supported. Specify an image to upload to the Image Service. Currently only images available via an HTTP URL are supported. The image location must be accessible to the Image Service. Compressed image binaries are supported (.zip and .tar.gz.) My test environment is as follow: 1. LVM as image backend of vms. 2. running vms on Xen in PV mode But when I upload a tar gzipped raw image file, nova just dd from it to logical volume, thus, nova error logged Boot loader didn't return any data! I grepped the nova and glance source code, found nothing about of gz or zip that related to image. This feature is valuable to our use case, for the raw image file is 4GB, but the compressed version is only 400MB. Did I misunderstand the compressed image support? Regards. Wang Li ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help :
[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_nova_trunk #110
Title: quantal_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/110/Project:quantal_folsom_nova_trunkDate of build:Mon, 09 Jul 2012 22:07:39 -0400Build duration:11 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesFix KeyError key_name when KeyPairExists raised.by dprinceeditnova/compute/api.pyFetch kernel/ramdisk images directlyby johannes.erdfelteditnova/virt/xenapi/vm_utils.pyConsole Output[...truncated 16234 lines...]Build-Time: 385Distribution: quantal-folsomFail-Stage: buildInstall-Time: 45Job: nova_2012.2+git201207092208~quantal-0ubuntu1.dscPackage: novaPackage-Time: 452Source-Version: 2012.2+git201207092208~quantal-0ubuntu1Space: 67760Status: attemptedVersion: 2012.2+git201207092208~quantal-0ubuntu1Finished at 20120709-2218Build needed 00:07:32, 67760k disc spaceERROR:root:Error occurred during package creation/buildERROR:root:Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'nova_2012.2+git201207092208~quantal-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/quantal-folsom-proposed /tmp/tmpdmjlCC/novamk-build-deps -i -r -t apt-get -y /tmp/tmpdmjlCC/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 642ec634c3beeb69175d0df12bcec8833e7efae5..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201207092208~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201207092208~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2012.2+git201207092208~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A nova_2012.2+git201207092208~quantal-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'nova_2012.2+git201207092208~quantal-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'nova_2012.2+git201207092208~quantal-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
