date:20130316

Re: [Openstack] ssh from VM to VM

2013-03-16 Thread Chathura M. Sarathchandra Magurawalage

I solved the issue by copying the rsa public key of the first VM to the
second VM. Thought I did not have to do this.

Thanks.

On 16 March 2013 12:34, Pranav  wrote:

> I think you need not exchange key pairs for Cirros image.
> Regards,
> Pranav
>
>
> On Sat, Mar 16, 2013 at 4:32 PM, Chathura M. Sarathchandra Magurawalage <
> 77.chath...@gmail.com> wrote:
>
>> Thanks for your reply.
>>
>> I have inserted PasswordAuthentication yes to the ssh config file. All
>> VMs have the same metadata including the ssh public key of the controller.
>> So I cant see why only cirros vms can do this.
>>
>> Still does not work.
>>
>>
>>
>> On 16 March 2013 06:24, Aaron Rosen  wrote:
>>
>>> I suspect that that host 10.5.5.6 has ssh configured for
>>> PasswordAuthentication set to no and you don't have your public key of the
>>> host you are on, in the authorized_key file of 10.5.5.6.
>>>
>>> Aaron
>>>
>>>  On Fri, Mar 15, 2013 at 7:26 PM, Chathura M. Sarathchandra
>>> Magurawalage <77.chath...@gmail.com> wrote:
>>>
 Hello,

 I can't ssh from Ubuntu cloud VM to other VM. I get following

 ubuntu@master:~$ ssh cirros@10.5.5.6 -v
 OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012
 debug1: Reading configuration data /etc/ssh/ssh_config
 debug1: /etc/ssh/ssh_config line 19: Applying options for *
 debug1: Connecting to 10.5.5.6 [10.5.5.6] port 22.
 debug1: Connection established.
 debug1: identity file /home/ubuntu/.ssh/id_rsa type -1
 debug1: identity file /home/ubuntu/.ssh/id_rsa-cert type -1
 debug1: identity file /home/ubuntu/.ssh/id_dsa type -1
 debug1: identity file /home/ubuntu/.ssh/id_dsa-cert type -1
 debug1: identity file /home/ubuntu/.ssh/id_ecdsa type -1
 debug1: identity file /home/ubuntu/.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
 debug1: SSH2_MSG_KEXINIT sent
 debug1: SSH2_MSG_KEXINIT received
 debug1: kex: server->client aes128-ctr hmac-md5 none
 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
 7b:8f:6a:ee:ba:e5:0a:c5:04:01:ca:bd:e5:38:69:55
 debug1: Host '10.5.5.6' is known and matches the ECDSA host key.
 debug1: Found key in /home/ubuntu/.ssh/known_hosts:4
 debug1: ssh_ecdsa_verify: signature correct
 debug1: SSH2_MSG_NEWKEYS sent
 debug1: expecting SSH2_MSG_NEWKEYS
 debug1: SSH2_MSG_NEWKEYS received
 debug1: Roaming not allowed by server
 debug1: SSH2_MSG_SERVICE_REQUEST sent
 debug1: SSH2_MSG_SERVICE_ACCEPT received
 debug1: Authentications that can continue: publickey
 debug1: Next authentication method: publickey
 debug1: Trying private key: /home/ubuntu/.ssh/id_rsa
 debug1: Trying private key: /home/ubuntu/.ssh/id_dsa
 debug1: Trying private key: /home/ubuntu/.ssh/id_ecdsa
 debug1: No more authentication methods to try.
 Permission denied (publickey).

 But I can ssh from to my Cirros VMs. Also I can ssh from Ubuntu VM to
 Cirros VM.

 Any Idea?

 Thanks.

 ___
 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] TC Candidacy

2013-03-16 Thread Chuck Thier

Hello all,

I would like to run for a seat on the TC.   I am one of the original
developers of Rackspace Cloud Files which became Openstack Swift, and was
deeply involved with the creation of Openstack.  I also lead the team at
Rackspace to create Cloud Block Storage which built off the foundation of
Openstack Cinder, and during that time contributed directly and indirectly
to Nova and Cinder.  I have the unique experience of not only developing
across several Openstack projects, but also being responsible for deploying
the projects at a very large scale.  I have a track record for fighting for
reasonable APIs, upgradeability, and maintainability across projects.  I
have also fought to ensure that we have equal and fair representation from
all projects in the Openstack community.

The purpose of the TC is not to "legislate from the bench", but when
questions and issues are brought to the TC I will continue to support these
ideals.  I deeply care for Openstack and its future success, so please
consider me for this position.

Thanks,

--
Chuck Thier
@creiht
___
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] [Quantum] Access problem to Metadata server

2013-03-16 Thread Pranav

there is a problem with Quantum Network you need to use L2 and L3 agents.
Or Nova-Networks.
Regards,
Pranav


On Fri, Mar 15, 2013 at 1:55 PM, Sylvain Bauza
wrote:

>
>
> Le 15/03/2013 08:20, Sammy Fung a écrit :
>
>   I am following this nice guide to configure Quantum.
>
>
> https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst
>
>
>
>  I got timeout on HTTP request to 169.254.169.254 connecting from VM.
>
> $ wget http://169.254.169.254/2009-04-04/meta-data/instance-id
> Connecting to 169.254.169.254 (169.254.169.254:80)
> wget: can't connect to remote host (169.254.169.254): Connection timed out
>
> But I got 404 Not Found if I connect to public IP port 8775 connecting
> from VM.
>
> $ wget http://1.2.3.4:8775/2009-04-04/meta-data/instance-id
>
> Connecting to 1.2.3.4:8775 (1.2.3.4:8775)
> wget: server returned error: HTTP/1.1 404 Not Found
>
>
>
>Anything I can try for debug/solving it ?
>
>
> As said in the guide, make sure your host running nova-api (incl.
> metadata, ie. 1.2.3.4) does have a route to the public IPs of your VMs.
>
> -Sylvain
>
> ___
> 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] Unable to successfully create instances with horizon

2013-03-16 Thread Pranav

Hi,

I have a similar setup and I spawn Nova Instances inside OpenStack deployed
on VirtuaBox VM instances. Make sure that your VM's are configured to Qemu
and not KVM as KVM will not work inside VM's. Also check this out it has
complete steps to setup OpenStack on VM's.
https://github.com/dguitarbite/OpenStack-Folsom-VM-SandBox-Guide

Regards,
Pranav


On Sat, Mar 16, 2013 at 5:47 AM, AJ Schroeder wrote:

> Hello list,
>
> ** **
>
> I’ve been following along with these instructions to get an openstack
> environment setup:
> http://docs.openstack.org/folsom/basic-install/content/basic-install_intro.html-
>  I am a total newbie with openstack.
> 
>
> ** **
>
> I am using virtualbox with Ubuntu 12.04 LTS guests and I have all three
> nodes setup and operational. After some troubleshooting I was finally able
> to create volumes in cinder, but now I can’t successfully create any
> instances. I use horizon and navigate through the process of setting up the
> instance, and when I click launch the instance shows up in the list, but
> the status is always “error”. I’m not sure what to post that would be
> relevant, but here are some log entries and output:
>
> ** **
>
> # -- nova-scheduler.log --#
>
> 2013-03-15 09:40:13 1475 DEBUG nova.openstack.common.rpc.amqp [-] received
> {u'_context_roles': [u'Member', u'admin'], u'_context_request_id':
> u'req-cccd3bed-8a37-4166-be5d-02f74221a2b6', u'_context_quota_class': None,
> u'_context_project_name': u'demo', u'_context_service_catalog':
> [{u'endpoints': [{u'adminURL': u'
> http://192.168.1.1:8774/v2/ef28e5b6b9d143c4baa15b271440586a', u'region':
> u'RegionOne', u'internalURL': u'
> http://192.168.1.1:8774/v2/ef28e5b6b9d143c4baa15b271440586a', u'id':
> u'110f0468149c42c88256f02a01aa54d0', u'publicURL': u'
> http://192.168.1.1:8774/v2/ef28e5b6b9d143c4baa15b271440586a'}],
> u'endpoints_links': [], u'type': u'compute', u'name': u'nova'},
> {u'endpoints': [{u'adminURL': u'http://192.168.1.1:9696/', u'region':
> u'RegionOne', u'internalURL': u'http://192.168.1.1:9696/', u'id':
> u'45faf59eb6c747daaae2ef16a68e7eef', u'publicURL': u'
> http://192.168.1.1:9696/'}], u'endpoints_links': [], u'type': u'network',
> u'name': u'quantum'}, {u'endpoints': [{u'adminURL': u'
> http://192.168.1.1:9292/v2', u'region': u'RegionOne', u'internalURL': u'
> http://192.168.1.1:9292/v2', u'id': u'16938ca8049446688ce57f7f98a71c32',
> u'publicURL': u'http://192.168.1.1:9292/v2'}], u'endpoints_links': [],
> u'type': u'image', u'name': u'glance'}, {u'endpoints': [{u'adminURL': u'
> http://192.168.1.1:8776/v1/ef28e5b6b9d143c4baa15b271440586a', u'region':
> u'RegionOne', u'internalURL': u'
> http://192.168.1.1:8776/v1/ef28e5b6b9d143c4baa15b271440586a',
> u'serviceName': u'cinder', u'id': u'f7a1448a776c4aa2b6a5843f38c33022',
> u'publicURL': u'
> http://192.168.1.1:8776/v1/ef28e5b6b9d143c4baa15b271440586a'}],
> u'endpoints_links': [], u'type': u'volume', u'name': u'cinder'},
> {u'endpoints': [{u'adminURL': u'http://192.168.1.1:8773/services/Admin',
> u'region': u'RegionOne', u'internalURL': u'
> http://192.168.1.1:8773/services/Cloud', u'id':
> u'0bb938dbb76d44ae94fa24998c3c8a94', u'publicURL': u'
> http://192.168.1.1:8773/services/Cloud'}], u'endpoints_links': [],
> u'type': u'ec2', u'name': u'ec2'}, {u'endpoints': [{u'adminURL': u'
> http://192.168.1.1:8080/v1', u'region': u'RegionOne', u'internalURL': u'
> http://192.168.1.1:8080/v1/AUTH_ef28e5b6b9d143c4baa15b271440586a', u'id':
> u'169ad8d8a930442ba189b626e1f574f7', u'publicURL': u'
> http://192.168.1.1:8080/v1/AUTH_ef28e5b6b9d143c4baa15b271440586a'}],
> u'endpoints_links': [], u'type': u'object-store', u'name': u'swift'},
> {u'endpoints': [{u'adminURL': u'http://192.168.1.1:35357/v2.0',
> u'region': u'RegionOne', u'internalURL': u'http://192.168.1.1:5000/v2.0',
> u'id': u'457ce03d6aa5479e819cae931760ab62', u'publicURL': u'
> http://192.168.1.1:5000/v2.0'}], u'endpoints_links': [], u'type':
> u'identity', u'name': u'keystone'}], u'_context_user_name': u'demo',
> u'_context_auth_token': '', u'args': {u'request_spec':
> {u'block_device_mapping': [{u'volume_size': u'', u'device_name': u'vda',
> u'delete_on_termination': False, u'volume_id':
> u'b26596e4-f142-4692-9507-5bcdd44ea0ca'}], u'image': {u'status': u'active',
> u'name': u'Ubuntu', u'deleted': False, u'container_format': u'bare',
> u'created_at': u'2013-03-13T02:48:56.00', u'disk_format': u'qcow2',
> u'updated_at': u'2013-03-13T02:48:57.00', u'properties': {},
> u'min_disk': 0, u'min_ram': 0, u'checksum': None, u'owner': None,
> u'is_public': True, u'deleted_at': None, u'id':
> u'dd89f63f-4b2a-44c5-96f2-084e198dd9aa', u'size': 251068416},
> u'instance_type': {u'memory_mb': 512, u'root_gb': 0, u'deleted_at': None,
> u'name': u'm1.tiny', u'deleted': False, u'created_at': None,
> u'ephemeral_gb': 0, u'updated_at': None, u'disabled': False, u'vcpus': 1,
> u'extra_specs': {}, u'swap': 0, u'rxtx_factor': 1.0, u'is_public': True,
> u'flavorid': u'1', u'vcpu_weight': None, u'id'

Re: [Openstack] ssh from VM to VM

2013-03-16 Thread Pranav

I think you need not exchange key pairs for Cirros image.
Regards,
Pranav


On Sat, Mar 16, 2013 at 4:32 PM, Chathura M. Sarathchandra Magurawalage <
77.chath...@gmail.com> wrote:

> Thanks for your reply.
>
> I have inserted PasswordAuthentication yes to the ssh config file. All
> VMs have the same metadata including the ssh public key of the controller.
> So I cant see why only cirros vms can do this.
>
> Still does not work.
>
>
>
> On 16 March 2013 06:24, Aaron Rosen  wrote:
>
>> I suspect that that host 10.5.5.6 has ssh configured for
>> PasswordAuthentication set to no and you don't have your public key of the
>> host you are on, in the authorized_key file of 10.5.5.6.
>>
>> Aaron
>>
>>  On Fri, Mar 15, 2013 at 7:26 PM, Chathura M. Sarathchandra Magurawalage
>> <77.chath...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> I can't ssh from Ubuntu cloud VM to other VM. I get following
>>>
>>> ubuntu@master:~$ ssh cirros@10.5.5.6 -v
>>> OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012
>>> debug1: Reading configuration data /etc/ssh/ssh_config
>>> debug1: /etc/ssh/ssh_config line 19: Applying options for *
>>> debug1: Connecting to 10.5.5.6 [10.5.5.6] port 22.
>>> debug1: Connection established.
>>> debug1: identity file /home/ubuntu/.ssh/id_rsa type -1
>>> debug1: identity file /home/ubuntu/.ssh/id_rsa-cert type -1
>>> debug1: identity file /home/ubuntu/.ssh/id_dsa type -1
>>> debug1: identity file /home/ubuntu/.ssh/id_dsa-cert type -1
>>> debug1: identity file /home/ubuntu/.ssh/id_ecdsa type -1
>>> debug1: identity file /home/ubuntu/.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
>>> debug1: SSH2_MSG_KEXINIT sent
>>> debug1: SSH2_MSG_KEXINIT received
>>> debug1: kex: server->client aes128-ctr hmac-md5 none
>>> 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
>>> 7b:8f:6a:ee:ba:e5:0a:c5:04:01:ca:bd:e5:38:69:55
>>> debug1: Host '10.5.5.6' is known and matches the ECDSA host key.
>>> debug1: Found key in /home/ubuntu/.ssh/known_hosts:4
>>> debug1: ssh_ecdsa_verify: signature correct
>>> debug1: SSH2_MSG_NEWKEYS sent
>>> debug1: expecting SSH2_MSG_NEWKEYS
>>> debug1: SSH2_MSG_NEWKEYS received
>>> debug1: Roaming not allowed by server
>>> debug1: SSH2_MSG_SERVICE_REQUEST sent
>>> debug1: SSH2_MSG_SERVICE_ACCEPT received
>>> debug1: Authentications that can continue: publickey
>>> debug1: Next authentication method: publickey
>>> debug1: Trying private key: /home/ubuntu/.ssh/id_rsa
>>> debug1: Trying private key: /home/ubuntu/.ssh/id_dsa
>>> debug1: Trying private key: /home/ubuntu/.ssh/id_ecdsa
>>> debug1: No more authentication methods to try.
>>> Permission denied (publickey).
>>>
>>> But I can ssh from to my Cirros VMs. Also I can ssh from Ubuntu VM to
>>> Cirros VM.
>>>
>>> Any Idea?
>>>
>>> Thanks.
>>>
>>> ___
>>> 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] using vlan tagged ports in cluster

2013-03-16 Thread Pranav

It is common to loose your network in 3 NIC setup that is why the third NIC
card, its ok if you cant ping your public IP directly. But this work around
wont hurt either. This work around has been implemented in two nic VLAN
method in the same git repo.
Regards,
Pranav


On Fri, Mar 15, 2013 at 10:08 PM, JR  wrote:

> Rain, I owe you a beer!  That did the trick.  Thanks.
>
> JR
>
> On 3/15/2013 11:32 AM, Rain Li wrote:
> > Hi, JR,
> >
> > You should check your route. Before "ovs-vsctl add-port br-ex p1p1.4",
> > you should have the route entry like:
> > 192.168.251.0   0.0.0.0  255.255.255.0 U 0 0 0 p1p1.4
> > But after that, since p1p1.4 is plugged in br-ex, you should change the
> > above route to go through br-ex, and may also change other (default
> > route) to this interface as well, if they originally go through p1p1.4.
> >
> > Regards,
> > Rain
> >
> >
> > On Thu, Mar 14, 2013 at 5:22 AM, JR  > > wrote:
> >
> > Greetings,
> >
> > I'm setting up openstack on some machines using
> >
> https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst
> .
> >
> > I'm using 3 nodes: a controller, network node and compute node.  All
> the
> > network interfaces are VLAN tagged use the same underlying physical
> 10G,
> > e.g.,
> >
> > controller: p1p1.4 (public net: 192.168.251.*/24), p1p1.5 (management
> > net: 10.10.10.*/24)
> > network:p1p1.4 (public net: 192.168.251.*/24), p1p1.5 (management
> > net: 10.10.10.*/24), p1p1.6 (vm net: 10.20.20.*/24)
> >
> > # I haven't gotten to the compute node yet but it should be
> > compute:   p1p1.5 (management net: 10.10.10.*/24), p1p1.6 (vm net:
> > 10.20.20.*/24)
> >
> > When I bring up my openvswitch bridges on the network node, I can not
> > longer get out to the public net (see *MORE* below).
> >
> > I'm running ubuntu 12.10 and have run apt-get dist-upgrade.  The 10G
> > nics are intel 82599EB.  ubuntu seems a bit flakey; initially I'd
> > created /etc/udev/rules/70-persistent-net.rules to map p1p1 to eth2,
> > however, the config was ignored and eth2 wound up being a 1G NIC.
> >
> > Is it not allowed to use VLAN interfaces for my networks?
> >
> > If I remove, say, the br-ex bridge I can get out again:
> > root@nebula03:~# ping 192.168.251.1
> > PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
> > ^C
> > --- 192.168.251.1 ping statistics ---
> > 1 packets transmitted, 0 received, 100% packet loss, time 0ms
> >
> > root@nebula03:~# ovs-vsctl del-port p1p1.4
> > root@nebula03:~# ovs-vsctl del-br br-ex
> > root@nebula03:~# ping 192.168.251.1
> > PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
> > 64 bytes from 192.168.251.1 : icmp_req=1
> > ttl=64 time=0.650 ms
> > ^C
> > --- 192.168.251.1 ping statistics ---
> > 1 packets transmitted, 1 received, 0% packet loss, time 0ms
> > rtt min/avg/max/mdev = 0.650/0.650/0.650/0.000 ms
> > root@nebula03:~#
> >
> >
> > Thanks for any help,
> > JR
> >
> > 
> > *MORE*
> > 
> > root@nebula03:~# ovs-vsctl show
> > 1bdf2f73-1a5d-4893-b745-7501557acaea
> > Bridge br-int
> > Port br-int
> > Interface br-int
> > type: internal
> > Bridge br-ex
> > Port br-ex
> > Interface br-ex
> > type: internal
> > Port "p1p1.4"
> > Interface "p1p1.4"
> > Bridge br-vm
> > Port br-vm
> > Interface br-vm
> > type: internal
> > Port "p1p1.6"
> > Interface "p1p1.6"
> > ovs_version: "1.4.3"
> > root@nebula03:~# ifconfig p1.4
> > p1.4: error fetching interface information: Device not found
> > root@nebula03:~# ifconfig p1p1.4
> > p1p1.4Link encap:Ethernet  HWaddr 90:e2:ba:2c:8a:08
> >   inet addr:192.168.251.92  Bcast:192.168.251.255
> > Mask:255.255.255.0
> >   inet6 addr: fe80::92e2:baff:fe2c:8a08/64 Scope:Link
> >   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >   RX packets:20964 errors:0 dropped:0 overruns:0 frame:0
> >   TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
> >   collisions:0 txqueuelen:0
> >   RX bytes:22269341 (22.2 MB)  TX bytes:594 (594.0 B)
> >
> > root@nebula03:~# ping 192.168.251.1
> > PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
> > ^C
> > --- 192.168.251.1 ping statistics ---
> > 2 packets transmitted, 0 received, 100% packet loss, time 1007ms
> >
> > root@nebula03:~# ping 192.168.251.91`
> > > ^C
> > root@nebula03:~# ping 192.168.251.91
> > PING 192.168.251.91 (192.168.251.91) 56(84) bytes of data.
> > ^C
> >
> >
>

Re: [Openstack] ssh from VM to VM

2013-03-16 Thread Chathura M. Sarathchandra Magurawalage

Thanks for your reply.

I have inserted PasswordAuthentication yes to the ssh config file. All VMs
have the same metadata including the ssh public key of the controller. So I
cant see why only cirros vms can do this.

Still does not work.



On 16 March 2013 06:24, Aaron Rosen  wrote:

> I suspect that that host 10.5.5.6 has ssh configured for
> PasswordAuthentication set to no and you don't have your public key of the
> host you are on, in the authorized_key file of 10.5.5.6.
>
> Aaron
>
> On Fri, Mar 15, 2013 at 7:26 PM, Chathura M. Sarathchandra Magurawalage <
> 77.chath...@gmail.com> wrote:
>
>> Hello,
>>
>> I can't ssh from Ubuntu cloud VM to other VM. I get following
>>
>> ubuntu@master:~$ ssh cirros@10.5.5.6 -v
>> OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012
>> debug1: Reading configuration data /etc/ssh/ssh_config
>> debug1: /etc/ssh/ssh_config line 19: Applying options for *
>> debug1: Connecting to 10.5.5.6 [10.5.5.6] port 22.
>> debug1: Connection established.
>> debug1: identity file /home/ubuntu/.ssh/id_rsa type -1
>> debug1: identity file /home/ubuntu/.ssh/id_rsa-cert type -1
>> debug1: identity file /home/ubuntu/.ssh/id_dsa type -1
>> debug1: identity file /home/ubuntu/.ssh/id_dsa-cert type -1
>> debug1: identity file /home/ubuntu/.ssh/id_ecdsa type -1
>> debug1: identity file /home/ubuntu/.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
>> debug1: SSH2_MSG_KEXINIT sent
>> debug1: SSH2_MSG_KEXINIT received
>> debug1: kex: server->client aes128-ctr hmac-md5 none
>> 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
>> 7b:8f:6a:ee:ba:e5:0a:c5:04:01:ca:bd:e5:38:69:55
>> debug1: Host '10.5.5.6' is known and matches the ECDSA host key.
>> debug1: Found key in /home/ubuntu/.ssh/known_hosts:4
>> debug1: ssh_ecdsa_verify: signature correct
>> debug1: SSH2_MSG_NEWKEYS sent
>> debug1: expecting SSH2_MSG_NEWKEYS
>> debug1: SSH2_MSG_NEWKEYS received
>> debug1: Roaming not allowed by server
>> debug1: SSH2_MSG_SERVICE_REQUEST sent
>> debug1: SSH2_MSG_SERVICE_ACCEPT received
>> debug1: Authentications that can continue: publickey
>> debug1: Next authentication method: publickey
>> debug1: Trying private key: /home/ubuntu/.ssh/id_rsa
>> debug1: Trying private key: /home/ubuntu/.ssh/id_dsa
>> debug1: Trying private key: /home/ubuntu/.ssh/id_ecdsa
>> debug1: No more authentication methods to try.
>> Permission denied (publickey).
>>
>> But I can ssh from to my Cirros VMs. Also I can ssh from Ubuntu VM to
>> Cirros VM.
>>
>> Any Idea?
>>
>> Thanks.
>>
>> ___
>> 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] glance --- HTTPInternalServerError (HTTP 500)

2013-03-16 Thread 杨峰

No, I did not follow devstack install, I am installing folsom from three
new virtual machines.

I had checked those conf/ini files,
I add follow lines in every files. but I always get the same error, any
other I can check?
sql_connection = mysql://glance:password@localhost/glance
admin_tenant_name = service
admin_user = glance
admin_password = password

于 13-3-14 下午9:29, JuanFra Rodriguez Cardoso 写道:
> Have you followed a devstack install? Have you verified credentials
> (tenant, user, pass, auth_url) in glance-*.conf/.ini are ok?
>
> Regards!
> ---
> JuanFra
>
>
> 2013/3/14 杨峰 mailto:hoking.y...@gmail.com>>
>
> I install folsom as the guide ( basic-install-folsom.pdf ), when I
> go to section Glance, and execute : #glance image-list and #glance
> image-create, I always get the error like below:
>
> root@controller:~# glance image-create --location
> 
> http://uec-images.ubuntu.com/releases/12.04/release/ubuntu-12.04-server-cloudimg-amd64-disk1.img
> --is-public true --disk-format qcow2 --container-format bare
> --name "Ubuntu"
> Request returned failure status.
> None
> HTTPInternalServerError (HTTP 500)
>
> root@controller:~# glance image-list
> Request returned failure status.
> None
> HTTPInternalServerError (HTTP 500)
>
> I google the error, and find the bug 1092783 (
> https://bugs.launchpad.net/devstack/+bug/1092783 ), but I do not
> know how to apply the patch.
>
> ___
> 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] Call for help on Grizzly documentation

2013-03-16 Thread Pranav

Hi, Even I'm interested. Ill be working on this for sure.
Regards,
Pranav


On Fri, Mar 15, 2013 at 7:42 PM, Michael Basnight wrote:

>  Of course... I spaced. I'd love to review the doc for this.
>
> Sent from my digital shackles
>
> On Mar 15, 2013, at 5:47 AM, "Anne Gentle"  wrote:
>
>   Yes, go ahead. Use the guidelines we have for Doc bug triage. [1]
>
>  Hey Bas, a DocImpact would have been ideal on that commit message so we
> could already have a doc bug logged. [2]
>
>  Thanks,
> Anne
>
>  1.
> https://wiki.openstack.org/wiki/Documentation/HowTo#Doc_Bug_Triaging_Guidelines
> 2.
> https://wiki.openstack.org/wiki/Documentation/HowTo#Using_the_DocImpact_Flag_in_a_Commit_Message
>
>
>
>
> On Fri, Mar 15, 2013 at 6:11 AM, Jérôme Gallard wrote:
>
>> Hi Anne,
>>
>> I'm a newbie in the "documentation area" but, I would like to give an
>> help.
>>
>> I haven't found any documentations (or open bug) regarding the cinder
>> multi-backend feature (
>> https://wiki.openstack.org/wiki/Cinder-multi-backend --
>> https://review.openstack.org/#/c/21815/ ).
>>
>> Do you know if this documentation is planed to be written?
>> Can I open a bug for this?
>>
>> Thanks a lot,
>> Jérôme
>>
>> On Tue, Mar 12, 2013 at 3:27 PM, Anne Gentle  wrote:
>> > Hi all,
>> > You all did great with DocImpact, but now that we're less than a month
>> from
>> > release, the tiny doc team is facing a long list of doc bugs that won't
>> be
>> > done by April 4th, many generated by DocImpact flags.
>> >
>> > We typically do a "release" of the docs about a month after the actual
>> > release date, to ensure packages are available and to try to get our
>> doc bug
>> > backlog to a manageable level.
>> >
>> > As you can see from our backlog for operator docs in openstack-manuals
>> [1]
>> > and API docs in api-site [2], there are over 50 confirmed doc bugs for
>> > Grizzly operator and admin docs and less than 20 for API docs. With
>> those
>> > numbers we need all the help we can get.
>> >
>> > Please dive in, the patch process is just like code and fully
>> documented.
>> > [3] We're on IRC in #openstack-doc and can answer any questions you
>> have as
>> > you go.
>> >
>> > Thanks!
>> > Anne, Tom, Diane, Laura, Emilien, Daisy, and all the other doc peeps
>> >
>> > 1. https://launchpad.net/openstack-manuals/+milestone/grizzly
>> > 2. https://launchpad.net/openstack-api-site/+milestone/grizzly
>> > 3. http://wiki.openstack.org/Documentation/HowTo
>> >
>>   > ___
>> > 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] ssh from VM to VM

[Openstack] TC Candidacy

Re: [Openstack] [Quantum] Access problem to Metadata server

Re: [Openstack] Unable to successfully create instances with horizon

Re: [Openstack] ssh from VM to VM

Re: [Openstack] using vlan tagged ports in cluster

Re: [Openstack] ssh from VM to VM

Re: [Openstack] glance --- HTTPInternalServerError (HTTP 500)

Re: [Openstack] Call for help on Grizzly documentation

9 matches

Site Navigation

Mail list logo

Footer information