You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be useful if users can assign hostnames from Dynamic DNS service directly to VMs using fedcloudclient: either during creation or latter:
During creation: fedcloud openstack server create ... --hostname "hostname.vm.fedcloud.eu:secret". Implementation by inserting curl https://hostname:[email protected]/update to cloud-init script.
After creation: fedcloud dns assign hostname.vm.fedcloud.eu:secret --site site --vo vo --vm vm-id. Implementation by using openstack server ssh for executing the mentioned curl command to assign the hostname to the VM.
By this way, users don't have to care about IP addresses of the VMs, all access to VMs can be realized via the hostnames, not IP addresses.
The text was updated successfully, but these errors were encountered:
It would be useful if users can assign hostnames from Dynamic DNS service directly to VMs using fedcloudclient: either during creation or latter:
During creation:
fedcloud openstack server create ... --hostname "hostname.vm.fedcloud.eu:secret"
. Implementation by insertingcurl https://hostname:[email protected]/update
tocloud-init
script.After creation:
fedcloud dns assign hostname.vm.fedcloud.eu:secret --site site --vo vo --vm vm-id
. Implementation by usingopenstack server ssh
for executing the mentionedcurl
command to assign the hostname to the VM.By this way, users don't have to care about IP addresses of the VMs, all access to VMs can be realized via the hostnames, not IP addresses.
The text was updated successfully, but these errors were encountered: