Re: [Openstack] [Openstack-devel] Openstack packages tags in Debian
Great work Thomas! Ghe Rivero On Sat, Jan 21, 2012 at 8:45 AM, Thomas Goirand tho...@goirand.fr wrote: Hi, I have spent quite some time making sure that we have nice tags for Openstack in Debian, making it easier to find each of our daemons and programs. I have also pushed for a new tag called Suite::openstack, so that it's easy now to find absolutely all packages related to openstack with a very simple query. Now, since there's a lot of packages (more than 50 binary packages!!!), and that I did it only with my limited knowledge, I must have done few mistakes. So if you are interested, I would welcome anyone to review the work, and submit more tags, also removing the ones which are wrong. Everything is there: http://debtags.debian.net/ And if you want more specifically to show all Openstack packages in Debian, you can go there: http://debtags.debian.net/reports/maint/openstack-de...@lists.alioth.debian.org Cheers, Thomas Goirand (zigo) ___ Openstack-devel mailing list openstack-de...@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/openstack-devel -- Pinky: Gee, Brain, what do you want to do tonight? The Brain: The same thing we do every night, Pinky—try to take over the world! .''`. Pienso, Luego Incordio : :' : `. `' `- www.debian.org www.openstack.com GPG Key: 26F020F7 GPG fingerprint: 4986 39DA D152 050B 4699 9A71 66DB 5A36 26F0 20F7 ___ 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 packages tags in Debian
On 01/21/2012 03:45 PM, Thomas Goirand wrote: Hi, I have spent quite some time making sure that we have nice tags for Openstack in Debian, making it easier to find each of our daemons and programs. I have also pushed for a new tag called Suite::openstack, so that it's easy now to find absolutely all packages related to openstack with a very simple query. Now, since there's a lot of packages (more than 50 binary packages!!!), and that I did it only with my limited knowledge, I must have done few mistakes. So if you are interested, I would welcome anyone to review the work, and submit more tags, also removing the ones which are wrong. Everything is there: http://debtags.debian.net/ And if you want more specifically to show all Openstack packages in Debian, you can go there: http://debtags.debian.net/reports/maint/openstack-de...@lists.alioth.debian.org Cheers, Thomas Goirand (zigo) When I'm at it, for Ubuntu maintainers, you might want to read this: http://www.enricozini.org/2012/debian/debtags-for-derivatives/ so you can import the tags directly from Debian in Ubuntu, which will save much of the (quite boring) work... Thomas ___ 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] Boot from volume invalid device name /dev/vda
Getting an error trying to boot an instance from volume (the following is
the traceback from nova compute):
(nova.rpc): TRACE: Traceback (most recent call last):
(nova.rpc): TRACE: File /opt/stack/nova/nova/rpc/impl_kombu.py, line
723, in _process_data
(nova.rpc): TRACE: rval = node_func(context=ctxt, **node_args)
(nova.rpc): TRACE: File /opt/stack/nova/nova/exception.py, line 126, in
wrapped
(nova.rpc): TRACE: return f(*args, **kw)
(nova.rpc): TRACE: File /opt/stack/nova/nova/compute/manager.py, line
150, in decorated_function
(nova.rpc): TRACE: self.add_instance_fault_from_exc(context,
instance_uuid, e)
(nova.rpc): TRACE: File /usr/lib/python2.7/contextlib.py, line 24, in
__exit__
(nova.rpc): TRACE: self.gen.next()
(nova.rpc): TRACE: File /opt/stack/nova/nova/compute/manager.py, line
145, in decorated_function
(nova.rpc): TRACE: return function(self, context, instance_uuid, *args,
**kwargs)
(nova.rpc): TRACE: File /opt/stack/nova/nova/compute/manager.py, line
565, in run_instance
(nova.rpc): TRACE: self._run_instance(context, instance_uuid, **kwargs)
(nova.rpc): TRACE: File /opt/stack/nova/nova/compute/manager.py, line
394, in _run_instance
(nova.rpc): TRACE: vm_state=vm_states.ERROR)
(nova.rpc): TRACE: File /usr/lib/python2.7/contextlib.py, line 24, in
__exit__
(nova.rpc): TRACE: self.gen.next()
(nova.rpc): TRACE: File /opt/stack/nova/nova/compute/manager.py, line
381, in _run_instance
(nova.rpc): TRACE: self._deallocate_network(context, instance)
(nova.rpc): TRACE: File /usr/lib/python2.7/contextlib.py, line 24, in
__exit__
(nova.rpc): TRACE: self.gen.next()
(nova.rpc): TRACE: File /opt/stack/nova/nova/compute/manager.py, line
378, in _run_instance
(nova.rpc): TRACE: injected_files, admin_password)
(nova.rpc): TRACE: File /opt/stack/nova/nova/compute/manager.py, line
511, in _spawn
(nova.rpc): TRACE: network_info, block_device_info)
(nova.rpc): TRACE: File /opt/stack/nova/nova/exception.py, line 126, in
wrapped
(nova.rpc): TRACE: return f(*args, **kw)
(nova.rpc): TRACE: File
/opt/stack/nova/nova/virt/libvirt/connection.py, line 681, in spawn
(nova.rpc): TRACE: domain = self._create_new_domain(xml)
(nova.rpc): TRACE: File
/opt/stack/nova/nova/virt/libvirt/connection.py, line 1255, in
_create_new_domain
(nova.rpc): TRACE: domain = self._conn.defineXML(xml)
(nova.rpc): TRACE: File /usr/lib/python2.7/dist-packages/libvirt.py,
line 1708, in defineXML
(nova.rpc): TRACE: if ret is None:raise
libvirtError('virDomainDefineXML() failed', conn=self)
(nova.rpc): TRACE: libvirtError: internal error Invalid harddisk device
name: /dev/vda
(nova.rpc): TRACE:
The block_device_mapping supplied was {/dev/vda: 1:::1} which results
in:
[{u'volume_size': u'', u'device_name': u'/dev/vda',
u'delete_on_termination': u'1', u'volume_id': u'1'}]), however I've tried
about every combination of values I can think of (supplying type, size,
changing device name, etc.) with the same result (although the error is
Invalid harddisk device name: /dev/vdb or whatever I supplied as the
device name).
If it helps:
Running devstack @ af0f7cadb9
Tried to launch an instance with both the cirros default devstack image and
UEC oneiric x64.
The existing volume is larger than the image's ephemeral volume (not sure
if that matters).
What am I doing wrong?
___
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] Instances with status error and what to do with them n the UI
The obvious answer is to have Horizon show whatever nova-client would show here. However, given that these things now stay around forever, I would argue that the functionality within nova-client itself is suspect and that perhaps there should be a flag to show instances/volumes with an error state. Otherwise something that fails just stays around forever, which is certainly not desirable. Devin On Saturday, January 21, 2012 at 10:29 AM, Tres Henry wrote: While trying to debug boot-from-volume I've ended up with instances (and volumes for that matter) in various states of failure. Currently Horizon simply displays all instances regardless of state (see attached ss). Horizon can filter out instances in an error state very simply, however, that is not necessarily the desired user experience. For example if a user attempts to launch a new instance and the instance goes into an error state before Horizon can render the instances page. In that case if we filtered out instances in an error state the user would never see the instance. It would appear as though nothing happened. This issue exists for any asynchronous process which could result in an object in the system with an unexpected state. This issue also impacts every client (not just Horizon). My question to the greater community is this: how should OpenStack present objects in unexpected states consistently so that every client (Horizon, CLI, third-party tool, etc) provides a consistent user experience? ___ 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 Attachments: - error_instances.png ___ 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] Memory quota in nova-compute nodes.
These are great options! Thanks :) Sent from my iPhone On 20/01/2012, at 14:52, Eric Windisch e...@cloudscaling.com wrote: On Thursday, January 19, 2012 at 12:52 PM, Jorge Luiz Correa wrote: I would like to know if it's possible to configure quota in each nova-compute node. For example, I set up a new hardware with 8 GB of memory and install the nova-compute, but I wish only 4 GB of memory are used (dedicated to nova-compute). Is it possible? If so, how can I configure that? I've seen quotas in projects, configured using nova-manage command line tool. But it isn't what I'm looking for. In Essex, you can use 'reserved_host_memory_mb' with the ZoneManager to reserve a certain amount of memory per host. If you're on Diablo, Joe Gordon made a pluggable scheduler based on the SimpleScheduler to do the same: https://github.com/cloudscaling/cs-nova-simplescheduler The relevent key here would be 'cs_host_reserved_memory_mb'. Note that both of these define how much memory goes to your OS and applications, rather than how much memory is set aside for Nova / VMs. If you had 8GB and wanted to give Nova 6GB, you would reserve 2GB for your host OS. This is a soft limit, your OS will happily take more memory absent cgroup support as aforementioned. -- Eric Windisch ___ 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-poc] [Question #183787]: multi node installation takes the services for lastly installed node
Question #183787 on devstack changed: https://answers.launchpad.net/devstack/+question/183787 Status: Open = Expired Launchpad Janitor expired the question: This question was expired because it remained in the 'Open' state without activity for the last 15 days. -- You received this question notification because you are a direct subscriber of the question. ___ Mailing list: https://launchpad.net/~openstack-poc Post to : openstack-poc@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-poc More help : https://help.launchpad.net/ListHelp
