openstack team mailing list archive

[Remo Mattei <remo@xxxxxxxxxx>]

By default you instances will get a 10 network if you need to go out you have to map it with a second nic and also if you have not created a security rule it will not come in so there are multiple steps to look and you will have to ge a floating ip if you want to come from the outside and the map it to the machine you just created. Did you deeply this from scratch or are you using something to test this like devstack etc.  you did not provide some details that may help to answer your scenario 

Ciao

Inviato da iPad ()

Il giorno Jul 13, 2013, alle ore 10:28, Yuval Mazor <yuvmaz@xxxxxxxxx> ha scritto:

> Hi, OpenStack newbie here, please be gentle... :-)
> 
> I followed the instructions from this post:  http://www.cloudbase.it/devstack-on-hyper-v/ with 2 exceptions:
> 1.  Use an existing virtual switch
> 2.  Not using the Quantum plugin (i.e., I want to use nova-network - haven't gotten around to figuring out Quantum ye
> 
> Instances come up fine - including instances from Windows images.  However, they come up with addresses in the 10.0.0.0 network.  Since the virtual switch connected to the NIC in the instance is the external switch, this address is (of course) on the wrong network and I'm unable to ping/RDP into it.  Console access works fine.
> 
> Am I missing something here or is this the way things are supposed to work?  How do I configure things so that I can ping the instances on the Hyper-V host?
> 
> 
> Thanks for your time!
> Yuval
> !DSPAM:2,51e18e6a14721420119099!
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
> 
> 
> !DSPAM:2,51e18e6a14721420119099!