On 02/01/2014 04:19 PM, Craig J wrote:
> I think the best way to accomplish this is to write a custom piece of > paste middleware and plug it into the nova api. I'm planning on > basically overriding the name provide by the user with a name that we > can guarantee to be unique. do you plan to rename the vm in case the name already exists or just abort the creation? i would choose the second > > So, two questions: > 1. Does anyone have a similar piece of middleware they'd care to share? i don't i would love to have it, i would share if i have it > 2. Are there any reasons this approach won't work? Any better approaches? it think it should be done at tenant level, my use case is i want to restrict vm names depending on the tenant them are in example: tenant foo, vm names allowes foo-mysql-n foo-apache-n tenant bar foo-mongodb-n foo-nginx this help a lot with orchestration, we are doing it manually now but i would like to enforce it > > > Thanks in advance, > Craig > > > _______________________________________________ > 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 > -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 _______________________________________________ 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
