Ask Your Question

khedhermail's profile - activity

2020-02-15 22:51:15 -0500 received badge  Student (source)
2016-12-17 06:29:18 -0500 received badge  Famous Question (source)
2015-11-19 01:17:05 -0500 received badge  Famous Question (source)
2015-11-16 03:05:01 -0500 received badge  Notable Question (source)
2015-03-31 07:39:45 -0500 received badge  Notable Question (source)
2014-11-25 16:34:16 -0500 received badge  Popular Question (source)
2014-11-10 05:07:44 -0500 received badge  Popular Question (source)
2013-02-19 12:17:09 -0500 answered a question Modify ssh key for running instance

Hey John,

Thanks for resopnse. In fact, I am using cirros image. But what cloud-init does with that ?

2013-02-18 14:23:12 -0500 answered a question Modify ssh key for running instance

Thanks for response.

Actually, I found many problem with sshing the instances even whiile proceeding by creating the ssh key first with nova keypair-add command line and then boot new instance by specifying the keyname but once ssh the instance it still not accpeted . I was following documentation in OpenStack website and get in -verbose mode such output:

ssh -vvvvvvvvvvvvv -i mykey root@10.10.10.1 OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012 Warning: Identity file mykey not accessible: No such file or directory. debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to 10.10.10.1 [10.10.10.1] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug3: Incorrect RSA1 identifier debug3: Could not load "/root/.ssh/id_rsa" as a RSA1 public key debug1: identity file /root/.ssh/id_rsa type 1 debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048 debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048 debug1: identity file /root/.ssh/id_rsa-cert type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: identity file /root/.ssh/id_dsa-cert type -1 debug1: identity file /root/.ssh/id_ecdsa type -1 debug1: identity file /root/.ssh/id_ecdsa-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.9p1 Debian-5ubuntu1 debug1: match: OpenSSH_5.9p1 Debian-5ubuntu1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 debug2: fd 3 setting O_NONBLOCK debug3: load_hostkeys: loading entries for host "10.10.10.1" from file "/root/.ssh/known_hosts" debug3: load_hostkeys: found key type ECDSA in file /root/.ssh/known_hosts:1 debug3: load_hostkeys: loaded 1 keys debug3: order_hostkeyalgs: prefer hostkeyalgs: ecdsa-sha2-nistp256-cert-v01@openssh.... debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ecdsa-sha2-nistp256-cert-v01@openssh.... debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcf... debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcf... debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.co... debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.co... debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256 debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcf... debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcf... debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.co... debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.co... debug2: kex_parse_kexinit: none,zlib@openssh.com debug2: kex_parse_kexinit: none,zlib@openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-ctr hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-ctr hmac-md5 none debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ECDSA c6:8c:20:18:6d:e3:23:30:1f:25:0b:d4:10:31:0c:f2 debug3: load_hostkeys: loading entries for host "172.16.0.14" from file "/root/.ssh/known_hosts" debug3: load_hostkeys: found key type ECDSA in file /root/.ssh/known_hosts:1 debug3: load_hostkeys ... (more)

2013-02-18 13:00:41 -0500 asked a question Modify ssh key for running instance

Hi,

Is that possible to modify ssh key for an instance while it is running!! Imagine that we did not mention the key in nova boot command but later once trying to access it we should add a ssh key !!1

Thanks for any response !

2013-02-14 13:41:54 -0500 answered a question Ephemeral/Persistent disks

Thanks John Garbutt, that solved my question.

2013-02-11 08:13:02 -0500 answered a question Ephemeral/Persistent disks

Thanks for your response. It helps by mentionning vda as you said before but still wondering about the 'vda' as a first disk for example will be created once the command launched ? and what is the differene between this way and using a cindervol2 as created above ?

2013-02-08 16:07:20 -0500 answered a question Ephemeral/Persistent disks

I did not see how libvirt should recognise 'volcinder2' as a device. is that /dev/vda naming imporant for that ?

2013-02-08 14:06:47 -0500 answered a question Ephemeral/Persistent disks

tail -n150 /var/log/nova/nova-compute.log | grep error:

TRACE nova.compute.manager [instance: 618c913c-f47d-4449-95cb-2501fdf72bcd] libvirtError: internal error Invalid harddisk device name: volcinder2 TRACE nova.openstack.common.rpc.amqp self._set_instance_error_state(context, instance['uuid']) TRACE nova.openstack.common.rpc.amqp libvirtError: internal error Invalid harddisk device name: volcinder2

it seems that the cinder volume not recognized by nova. It s already configured in cinder.conf file. To create that volume group I proceeded as follows:

dd if=/dev/zero of=volcinder2 bs=1 count=0 seek=6G losetup /dev/loop3 volcinder2 fdisk /dev/loop3

Then we could see i cinder list the new volume group created and available.

Just after executing nova boot as follows: nova boot --flavor 1 --image Test --key_name mykey --block-device-mapping volcinder2=19fd60dc-0b6e-4b11-8fc0-5cd32e45dacd:::0 ServerFromBoot

show building --> Error status.

???

n p 1 ENTER ENTER t 8e w

pvcreate /dev/loop3 vgcreate volcinder2 /dev/loop3

2013-02-08 11:39:47 -0500 answered a question Ephemeral/Persistent disks

The instance created booted from that volume shows ERROR status in nova list instances. However I can ping it. No errors shown actually. try to figure out how it was done I could see in the /var/lib/nova/instances/instance000000x/libvirt.xml the creation of two types of disk [file and block types] <disk type="file" device="disk"> <driver name="qemu" type="qcow2" cache="none"/> <source file="/var/lib/nova/instances/instance-00000011/disk"/> <target bus="virtio" dev="vda"/> </disk> <disk type="block" device="disk"> <driver name="qemu" type="raw" cache="none"/> <source dev="/dev/disk/by-path/ip-172.16.0.3:3260-iscsi-iqn.2010-10.org.openstack:volume-19fd60dc-0b6e-4b11-8fc0-5cd32e45dacd-lun-1"/> <target bus="virtio" dev="volcinder2"/> </disk>

Is still something missing ?

2013-02-07 17:40:58 -0500 answered a question Ephemeral/Persistent disks

Thanks for the response, In fact I used cinder as volume backend and followed the example above. Once created a vm, it shows an error status without mentioning any reason in log files nova or cinder log files. I was checking /var/lib/nova/instances to check the instance created but no new instance000000x was created in the folder. I checked also nova show vm and as OS-EXT-SRV-ATTR:instance_name was instance-0000000a. that means as far as I understand that the ephemeral disk is created [folder disk] in cinder-volumes level. Could the be reason of the error ?

2013-02-06 09:06:24 -0500 asked a question Ephemeral/Persistent disks

Hi, Actually I am running OpenStack Folsom release and I was wondering about the point that OpenStack handle the disks. When we ask Nova to boot a VM, nova-compute will connect to Glance and "GET" the image file from Glance and save it on the its local filesystem. So by default the disk of an instance is basically stored on the local filesystem of the server where the instance is running that is the 'ephemeral' disk. In oppoiste of persistent disks, the ephemeral disks will be discarded if the VM is shut down and on failures.

Is that possible to make nova boot the primary disk 'ephemeral' as persistent from a volume instead in the local machine runing the hypervisor ?