Ask Your Question
0

metadata in both router and dhcp namespace

asked 2015-10-02 05:07:57 -0500

busyboy gravatar image

hi,

in default setup of KILO, meta-data is enabled only in the qrouter namespaces, whereas in qdhcp there is no meta-data defined. I know it is possible to enable it in qdhcp namesapces, but the question is

1) can meta-data co-exist in qrouter and qdhcp namespace at the same time

so that LANs without Routers involved can access meta-data.

history

I have different LANS, some with access to provider network using Qrouter and some of the LANs are only local to the OpenStack Instances and need no access to the Provider network. these VM Instances don't get meta-data when they are booting off from a router-less network and I have to enable a connection less router to enable the VMs with meta-data.

Regards,

edit retag flag offensive close merge delete

Comments

Please, elaborate how connection less router may provide access to neutron-ns-metadata-proxy running qrouter-namespace

dbaxps gravatar imagedbaxps ( 2015-10-03 02:12:14 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
1

answered 2015-10-02 05:59:28 -0500

dbaxps gravatar image

updated 2015-10-05 07:35:23 -0500

UPDATE 10/05/2015
See http://dbaxps.blogspot.com/2015/10/ho...
END UPDATE

Tested on Liberty (beta). I made update to /etc/neutron/dhcp_agent.ini

enable_isolated_metadata = True

restarted service and was able to launch CirrOS 0.3.4 on old sub-net with neutron router.
So, on isolated sub-net without neutron router it makes sense attempt to reproduce
http://techbackground.blogspot.com/20...
See also https://bugs.launchpad.net/neutron/+b...
Tested OK on Liberty (beta)

Switched to enable_isolated_metadata = True in dhcp_agent.ini
# openstack-service restart
1. Created private network without attaching to neutron router and launched F22, CirrOS 0.3.4 instances  via this network. Both have access to metadata, both VMs accessible via qdhcp-namespace ( CirrOS also via console login)
2. Launched new F22 and CirrOS VM to old tenants sub-net having neutron router.
Normal behavior in/outbound connectivity via floating ips && access to metadata
with no problems.

No need to touch opts dnsmasq file , already created as needed
F22 VM launched to isolated tenants subnet 30.0.0.0/24

[root@vfedora22wks ~(keystone_admin)]# ip netns exec qdhcp-e0f08063-2002-4cc9-b7b1-611925ad01e5  ping -c 3 30.0.0.12
PING 30.0.0.12 (30.0.0.12) 56(84) bytes of data.
64 bytes from 30.0.0.12: icmp_seq=1 ttl=64 time=0.308 ms
64 bytes from 30.0.0.12: icmp_seq=2 ttl=64 time=0.182 ms
64 bytes from 30.0.0.12: icmp_seq=3 ttl=64 time=0.495 ms

--- 30.0.0.12 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.182/0.328/0.495/0.129 ms


 [root@vfedora22wks ~(keystone_admin)]# ip netns exec qdhcp-e0f08063-2002-4cc9-b7b1-611925ad01e5  ssh -i oskeylibery.pem fedora@30.0.0.12
    Last login: Fri Oct  2 14:10:04 2015 from 30.0.0.10
    [fedora@vf22devs012 ~]$ sudo su -
    [root@vf22devs012 ~]# curl http://169.254.169.254/latest/meta-data/instance-id
    i-00000006[root@vf22devs012 ~]# 
    [root@vf22devs012 ~]# curl http://169.254.169.254/latest/meta-data/local-ipv4
    30.0.0.12[root@vf22devs012 ~]# 
    [root@vf22devs012 ~]# ip route
    default via 30.0.0.1 dev eth0  proto static 
    30.0.0.0/24 dev eth0  proto kernel  scope link  src 30.0.0.12 
    169.254.169.254 via 30.0.0.10 dev eth0  proto static

Booting logs uploaded here :- http://textuploader.com/a2yhc
Final draft for this answer is uploaded here :- http://textuploader.com/a2bjv

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2015-10-02 05:07:57 -0500

Seen: 589 times

Last updated: Oct 05 '15