Re: [Openstack] console.log is empty, what to do?
2013/2/1 JuanFra Rodriguez Cardoso juanfra.rodriguez.card...@gmail.com: Hi all again: Finally I got dump logs to file 'console.log'. It needed to add 'console=tty0 console=ttyS0,115200' to kernel line in /etc/grub.conf. Hi JuanFra, Thanks for this hint. I was facing the same issue and this solves it :-) I've tested it on a Debian wheezy image with grub2, so there is a slight difference: Line: GRUB_CMDLINE_LINUX=console=tty0 console=ttyS0,115200 File: /etc/default/grub # update-grub And console.log appears in next boot Regards Alberto ___ 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] It is stuck when attach the volume to the vm.
Hi Lei, I was facing a similar issue with nova-volume on essex, so I'm not sure if this can be useful to you ... Where are you looking for errors? I found volume attach errors at nova-compute.log of node where instance is running I hope this help you Alberto ___ 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] Essex volume attach issue on Debian Wheezy
On Wed, Dec 05, 2012 at 11:46:46AM -0800, Vishvananda Ishaya wrote: and /etc/nova/rootwrap.d/volume.filters contains the line: iscsiadm_usr: CommandFilter, /usr/bin/iscsiadm, root ? Vish You were right. This filter was not defined on compute nodes, but Debian is still using essex, so /etc/nova/rootwrap.d is not present [1], rootwrap filters are defined at /usr/share/pyshared/nova/rootwrap/ iscsiadm filter is defined in volume.py: filters.CommandFilter(/usr/bin/iscsiadm, root), but that file is included in nova-volume package: dpkg -S /usr/share/pyshared/nova/rootwrap/volume.py nova-volume: /usr/share/pyshared/nova/rootwrap/volume.py This is a problem (a bug?) because nova-volume is not installed on computer nodes. Putting this filter in compute.py on compute nodes resolves this issue and rootwrap works properly. I'm facing a new issue :-), but it will be reported at another thread Can someone confirm that this is a possible bug? or perhaps I'm doing something wrong Alberto [1] http://wiki.openstack.org/Packager/Rootwrap ___ 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] Problem with keystone on Debian
On Thu, Dec 06, 2012 at 04:21:49PM -0200, Guilherme Russi wrote: Hello Guys, I'm trying to install OpenStack on Debian Wheezy, but i'm getting some problems with keystone, when i try to create a user in a tenant using the --tenant-id command, it returns the error: keystone: error: unrecognized arguments: --service-id service-id number. Are you using essex (official repo) or folsom (backport repo)? If you are using essex, you must use the command: keystone user-role-add --user user_id --role role_id --tenant_id tenant_id where *_id are user, role and tenants ids previously created. Cheers Alberto ___ 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] Essex volume attach issue on Debian Wheezy
Hi all, We're facing an issue attaching a volume to a running instance in an Essex deployment on Debian Wheezy. nova-volume is installed on the cloud controller, but nova-network is installed on the computes nodes in a multi_host setup. The relevant configuration parameters in nova.conf are (nexentastor-ce is used for volume storage): volume_driver=nova.volume.nexenta.volume.NexentaDriver use_local_volumes=false nexenta_host=172.22.222.2 nexenta_volume=nova nexenta_user=admin nexenta_password= Volumes can be created properly: $ nova volume-create --display_name demovol1 1 $ nova volume-list ++---+--+--+-+-+ | ID | Status | Display Name | Size | Volume Type | Attached to | ++---+--+--+-+-+ | 1 | available | demovol1 | 1| None| | ++---+--+--+-+-+ But attaching to a volume fails with no error: $ nova volume-attach 63abfd8a-...-...-... 1 /dev/vdc and the volume still remains available. It seems that the problem is related to these logs found in the compute node (nova-compute.log): TRACE nova.rpc.amqp ProcessExecutionError: Unexpected error while running command. TRACE nova.rpc.amqp Command: sudo nova-rootwrap iscsiadm -m node -T iqn.1986-03.com.sun:02:nova-volume-001 -p 172.22.222.2:3260 TRACE nova.rpc.amqp Exit code: 1 TRACE nova.rpc.amqp Stdout: '' TRACE nova.rpc.amqp Stderr: 'Traceback (most recent call last):\n File /usr/bin/nova-rootwrap, line 69, in module\n env=filtermatch.get_environment(userargs))\n File /usr/lib/python2.7/subprocess.py, line 679, in __init__\nerrread, errwrite)\n File /usr/lib/python2.7/subprocess.py, line 1249, in _execute_child\nraise child_exception\nOSError: [Errno 2] No such file or directory\n' Trying to execute this command from the command line (as nova user): nova@calisto:~$ sudo nova-rootwrap iscsiadm -m node -T iqn.1986-03.com.sun:02:nova-volume-001 -p 172.22.222.2:3260 Traceback (most recent call last): File /usr/bin/nova-rootwrap, line 69, in module env=filtermatch.get_environment(userargs)) File /usr/lib/python2.7/subprocess.py, line 679, in __init__ errread, errwrite) File /usr/lib/python2.7/subprocess.py, line 1249, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory Whereas executing the same command as root without sudo nova-rootwrap seems to work ok: root@calisto:~# iscsiadm -m node -T iqn.1986-03.com.sun:02:nova-volume-001 -p 172.22.222.2:3260 # BEGIN RECORD 2.0-873 node.name = iqn.1986-03.com.sun:02:nova-volume-001 node.tpgt = 1 node.startup = manual ... Any tips on this? Cheers! Alberto ___ 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] Essex volume attach issue on Debian Wheezy
2012/12/5 Vishvananda Ishaya vishvana...@gmail.com: Probably wheezy puts iscsiadm somewhere that rootwrap can't find it. iscsiadm: CommandFilter, /sbin/iscsiadm, root iscsiadm_usr: CommandFilter, /usr/bin/iscsiadm, root You should do a: which iscsiadm Thanks for the quick response but it seems that iscsiadm location is correct: nova@calisto:~$ which iscsiadm /usr/bin/iscsiadm Alberto ___ 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] create more than 16cores in one server
Hi Edward, Are you using Simple.Scheduler? I think it must be related to max_cores option. max_cores default value is 16, you can override it in nova.conf max_cores = 24 cpu_allocation_ratio (vCPU/CPU ratio) default value is 1, if you want to use more virtual cores: cpu_allocation_ratio = ... See: http://docs.openstack.org/trunk/openstack-compute/admin/content/simple.html http://docs.openstack.org/trunk/openstack-compute/admin/content/corefilter.html Alberto ___ 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] Cloud with Essex for educational purposes
Hi all, Sometime ago, I asked to the list for some help about hardware specification for implementing a little cloud for educational purposes. Finally we've successfully finished the deployment of the cloud with OpenStack Essex and we've documented all the procedure [1], so we are glad to share our experience with you all. There is only an important limitation: all this documentation has been written in our mother tongue (spanish), so It will mainly be useful to the spanish-speaking community inside OpenStack. At this moment we are just beginning to discover with our students the tremendous educational possibilities that the cloud can bring to us, so we would like to thank everyone involved in this great project! Alberto [1] http://www.gonzalonazareno.org/cloud ___ 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] ZFS/ZVol + iscsi for volume
El lun, 11-06-2012 a las 10:26 -0500, Narayan Desai escribió: How integrated is the network target support for zfs on freebsd? One of the most compelling features (IMHO) of ZFS on illumos is the whole comstar stack. On the zfs linux port at least, there are just integration hooks out to the standard linux methods (kernel-nfs, etc) for nfs, iscsi, etc. I'm really interested to hear how this goes on FreeBSD. I've been playing with zfs on linux as well, but the results haven't been so good for me. -nld AFAIK, support for ZFS on FreeBSD is good. The main problem for using Debian/KFreeBSD at this moment is nova-volume: it depends on lvm2 and tgt [1], packages that are not available in Debian/KfreeBSD port. [1] http://qa.debian.org/debcheck.php?dist=unstablepackage=nova ___ 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] hardware specifications for a little private cloud
Hi all, I'm a teacher at a sysadmin academy and we are planning to deploy a private cloud with OpenStack for educational/training purposes. We are currently selecting the optimal hardware configuration for our needs and I'm asking for some help to the list. Using [1] as a reference, we are clear about hardware specifications of compute nodes (4 nodes with 2 processors), but we aren't about the best solution for node controller and optimal storage: Option 1: 1 server with 2 HD in RAID1 (nova controller, nova volume, glance, ...) + 1 SAN iSCSI Option 2: 1 server with 12 HD in RAID5/6 (nova controller, nova volume, glance, ...) We are excited about the possibilities that a private cloud brings to us and we don't want to fail in this critical step, so any help will be really appreciated. Alberto Molina Coballes IES Gonzalo Nazareno [1] http://www.referencearchitecture.org/hardware-specifications/ ___ 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] hardware specifications for a little private cloud
2012/3/26 Razique Mahroua razique.mahr...@gmail.com Hello Alberto, I would advise you to deploy as much as node as you can, and dedicate separate services. That would bring you the possibility to extend your knowledge on HA mechanisms, and really understand how services interact each other. Yes I know, but we have budget limitations. OpenStack HA is not an objective at this moment, it is a educational environment and we can still use a whiteboard ;) Let's say you spawn an instance from the api server, while it's is launched on a compute node - which is one another server. By having splitted architecture, you won't miss the obvious ;-) OK, but we are always considering 1 controller node and 4 compute nodes, the main doubt is regarding storage, is it better in controller node or in a external SAN iSCSI in a little cloud like this? What is the purpose of the lab ? Sysadmin training. At this moment, each student uses an isolated virtual LAN with Xen/KVM and shares some physical servers, but with a private cloud we can deploy a plethora of new configurations. Furthermore, the cloud itself. Alberto Molina Coballes IES Gonzalo Nazareno ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
