[ https://issues.apache.org/jira/browse/CLOUDSTACK-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13730429#comment-13730429 ]
ASF subversion and git services commented on CLOUDSTACK-3181: ------------------------------------------------------------- Commit 8339a22febd7956c0434b95a9b021ed016566251 in branch refs/heads/master from [~radhikap] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8339a22 ] CLOUDSTACK-3181 and CLOUDSTACK-847 > update the docs with the changes related to the user-data and reset-ssh keys. > ----------------------------------------------------------------------------- > > Key: CLOUDSTACK-3181 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3181 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc > Affects Versions: 4.2.0 > Reporter: Bharat Kumar > Fix For: 4.2.0 > > > Earlier we used to use the eth0 ip of the router to get the public key and > user-data. now with the multiple subnets the user data needs to be accessed > by the name data-server instead of the eth0 ip. > We used to fetch the eth0 ip of the router from the dhcp files in the VM. For > VMs in new subnet this will be one of the ipalises on the router eth0 > interface. using this ip to access user-data will not work for new subnets as > the service is not running on the alias ips. so we now use a name data-server > to access the user-data and public key . The name gets resolved by the > dnsmasq to the primary ip of the eth0 interface . > In case of ssh-key reset we have modified the script to fetch the public key > using the name data-server instead of the eth0Ip of the router. So if some > one wants to use this multiple ip ranges feature they will need to update the > uservm templates with this modified ssh-key rest script. All VMs deployed > prior to using this feature will be able to use the ssh-key reset with the > old script. The updating of the templates is required for the VMs which will > be deployed in the new subnet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira