A fair bit of my setup uses service names for automatic naming
elsewhere. For example, we have NFS mounts like /path/to/<servername>
and automatic DNS like <servername>.example.org
Of course, if a user is determined to to create a less useful
instance, they can create one with a name like "...." or "../../.."
which will result in hilarity.
I'm sure that I'm not the only one who regards a server name as
useful for naming other resources. What solutions do you use? Is there
a way to tell nova or Horizon to restrict server names to a given pattern?
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
elsewhere. For example, we have NFS mounts like /path/to/<servername>
and automatic DNS like <servername>.example.org
Of course, if a user is determined to to create a less useful
instance, they can create one with a name like "...." or "../../.."
which will result in hilarity.
I'm sure that I'm not the only one who regards a server name as
useful for naming other resources. What solutions do you use? Is there
a way to tell nova or Horizon to restrict server names to a given pattern?
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack