openstack team mailing list archive

[Sagar Nikam <sagar.r.nikam@xxxxxxxxx>]

Hi,

Have you added rules in the security group.
For ping to work ICMP rule needs to be added and for SSH to work TCP rule
needs to be added.

Check the following doc for more details

http://docs.openstack.org/folsom/openstack-compute/admin/content/instance-networking.html

Regards,
Sagar


On Sun, Mar 31, 2013 at 4:44 PM, Romil Gupta <romilgupta19@xxxxxxxxx> wrote:

> Hi ,
>
> First of all check whether VM is getting the desired IP or not  jst by
> logging into it if you have KVM use Virt-manager .
> do ifconfig
>
> if IP is there then try to set your switch in *promisc mode .*
>
> Hopefully this solves your problem.
>
>
>
> On Fri, Mar 29, 2013 at 1:52 PM, zengshan2008 <zengshan2008@xxxxxxxxx>wrote:
>
>> **
>> **
>> Hi all,
>> I just installed openstack folsm version in two machines, one works as
>> the controller node and the other is the compute node in the mode VLAN, and
>> I can launch instance without error, shown as below:
>>  but I can't access the virtual machines by ping or ssh, neither through
>> the external address or the internal address(through the vnc console in the
>> horizon, I can see that the virtual machine is running ).
>> The ip addresss of the controller node is 202.122.39.*, do I need to
>> make some configuration on the switch which the controller node connected
>> to? if so, how can I do it?
>> The followings are some of the configuration in my environment:
>> root@*controller01* <root@controller01>:~# brctl show
>> bridge name     bridge id               STP enabled     interfaces
>> br-ex           0000.441ea15d8581       no              eth1
>>                                                         qg-3fb4f234-87
>>                                                         qg-858cc92d-e9
>> br-int          0000.56fdf9dbfa44       no              qr-da193884-e6
>>                                                         tap2362751e-47
>>                                                         tap98f5950d-16
>> root@*controller01* <root@controller01>:~# quantum net-list
>>
>> +--------------------------------------+-------------+--------------------------------------+
>> | id                                   | name        |
>> subnets                              |
>>
>> +--------------------------------------+-------------+--------------------------------------+
>> | bfab9f72-a02b-4a50-8bc8-5ed98f54bbb0 | private_net |
>> 7e959bb7-38ba-4d1b-8abb-ba740a4e942b |
>> | f65401c3-a5a5-4452-813b-3663df2586d7 | public_net  |
>> e2ad8f43-dd9d-4955-b768-73e19ff805af |
>>
>> +--------------------------------------+-------------+--------------------------------------+
>> root@*controller01* <root@controller01>:~# brctl show
>> bridge name     bridge id               STP enabled     interfaces
>> br-ex           0000.441ea15d8581       no              eth1
>>                                                         qg-3fb4f234-87
>>                                                         qg-858cc92d-e9
>> br-int          0000.56fdf9dbfa44       no              qr-da193884-e6
>>                                                         tap2362751e-47
>>                                                         tap98f5950d-16
>> root@compute01:~# brctl show
>> bridge name     bridge id               STP enabled     interfaces
>> br-eth2         0000.002655e9ec09       no              eth2
>>                                                         phy-br-eth2
>> br-int          0000.ba1b4a5e2140       no              int-br-eth2
>>                                                         qvo7b839399-09
>>                                                         qvo8631dc9c-88
>>                                                         qvoe7a81c82-07
>>                                                         qvoff01f526-89
>> qbr7b839399-09          8000.ba07ccb67827       no
>> qvb7b839399-09
>>                                                         vnet5
>> qbr8631dc9c-88          8000.e2c3f43f4908       no
>> qvb8631dc9c-88
>>                                                         vnet0
>> qbre7a81c82-07          8000.3e31e86477bf       no
>> qvbe7a81c82-07
>>                                                         vnet1
>> qbrff01f526-89          8000.4af1c1728f83       no
>> qvbff01f526-89
>>                                                         vnet2
>>
>> Meanwhile, I am wonderring how the virtual machine access to the
>> internet, and how the external machines access the virutal machine?
>> It will be great if anyone can help me, thank you very much!
>>
>> 2013-03-29
>> ------------------------------
>>  zengshan2008
>> **
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> *Thanks & Regards,*
> *Romil Gupta
> M.Tech (CSE), Manipal
> Intern@ HP ISO,Bangalore
> Contact No. : 8880414133*
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>