Hello again, that's great! As for the method you mentioned i haven't tried it but i will just to see what happens.
Thanks again George On 31 October 2015 at 15:29, Geo Varghese <[email protected]> wrote: > Hi George, > > I just tried your method and it seems working perfectly :) > > Thanks for your valuable inputs. > > On Sat, Oct 31, 2015 at 6:42 PM, Geo Varghese <[email protected]> wrote: > >> Hi George, >> >> Thanks for the update. Yes, you are right that is the exact requirement. >> >> "assign ip from that network directly to the instance with out the use of >> a private net and floating ip over nat" >> >> I got a update about external network like this from list. Thats why i >> tried it like that. >> >> ========================================================== >> A Neutron router can also be attached to the same network so that >> instances in non-routable tenant networks can obtain floating IPs from the >> same 'public' network. At one time non-admin users were not allowed to >> attach VMs to 'external' networks but I believe that restriction was >> removed around Kilo or so. >> >> Yes, as long as the network is marked as both 'shared' and external, a >> tenant can attach VMs and router gateway interfaces directly to it. >> ========================================================== >> >> According to your inputs, the above method is not correct right? >> >> >> And about the method of adding bridge to compute node, do we need to add >> following options? >> >> bridgemapping in ml2 conf >> enable_distributed_routing to true >> >> Thanks again for your time. >> >> >> On Sat, Oct 31, 2015 at 2:20 PM, George Paraskevas <[email protected]> >> wrote: >> >>> Hello there, >>> >>> From what I understand you want to assign ip from that network directly >>> to the instance with out the use of a private net and floating ip over nat. >>> Now you need to correct some things and you will be quite there. First when >>> you create an external network then that network can only work though >>> floating ip. So instead create the same net but don't mark it as external. >>> Also you need that bridge on compute nodes because the VM nic will bind >>> directly to it. So don't configure l3 agent just configure ml mapping for >>> that network. I hope you can under stand and I also hope I understood you. >>> Thanks >>> George >>> >>> On Sat, 31 Oct 2015, 08:43 Geo Varghese <[email protected]> wrote: >>> >>>> Hi Team, >>>> >>>> I need help with adding instance with fixed ip in external network with >>>> out using private and floating ip. >>>> >>>> I have tested it using following steps >>>> >>>> 1) Created a new nic - eth4 for new external network(192.168.122.0/24) >>>> in controller. >>>> >>>> 2) Created a bridge - br-ex2 and added eth4 as port to bridge. >>>> >>>> 3) Mapped this bridge in ml2 conf and restarted l3 agent and neutron >>>> plugin >>>> >>>> 4) Then added shared external network Ext2 in openstack. Then added >>>> subnet as 192.168.122.0/24 >>>> >>>> 5) Added it to the router- router2 as interface with a IP - >>>> 192.168.122.99. Network topology shows the interface is active with this >>>> IP. Ping to this ip is also working from other machines. >>>> >>>> Later created VM in this network, but it failed with following error in >>>> nova-compute log. >>>> >>>> ========================================================= >>>> Unable to mount image >>>> /var/lib/nova/instances/903a6630-941c-4fd0-948f-85522fa20979/disk with >>>> error libguestfs installed but not usable (/usr/bin/supermin-helper exited >>>> with error status 1. >>>> ========================================================== >>>> >>>> Please check attached screen shot of network topology. >>>> >>>> Please help me with your inputs. >>>> >>>> -- >>>> -- >>>> Regards, >>>> Geo Varghese >>>> _______________________________________________ >>>> OpenStack-operators mailing list >>>> [email protected] >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >>>> >>> >> >> >> -- >> -- >> Regards, >> Geo Varghese >> > > > > -- > -- > Regards, > Geo Varghese >
_______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
