Open Stack

Russell,

Thanks for the quick reply. If I understand what you are suggesting it is
that there would be one Trove-Service Tenant/User that owns all instances
from the perspective of Nova.  This was one option proposed during our
discussions.  However, what we thought would be best is to continue to use
the user credentials so that Nova has the correct association.  We wanted
a more substantial and deliberate relationship between Nova and a
dependent service.  In this relationship, Nova would acknowledge which
instances are being managed by which Services and while ownership was
still to that of the User, management/manipulation of said Instance would
be solely done by the Service.

At this point the guard that Nova needs to provide around the instance
does not need to be complex.  It would even suffice to keep those
instances hidden from such operations as ³nova list² when invoked by
directly by the user.

Thanks,

Justin Hopper
Software Engineer - DBaaS
irc: juice | gpg: EA238CF3 | twt: @justinhopper




On 4/5/14, 14:20, "Russell Bryant" <rbryant at redhat.com> wrote:

>On 04/04/2014 08:12 PM, Hopper, Justin wrote:
>> Greetings,
>> 
>> I am trying to address an issue from certain perspectives and I think
>> some support from Nova may be needed.
>> 
>> _Problem_
>> Services like Trove use run in Nova Compute Instances.  These Services
>> try to provide an integrated and stable platform for which the ³service²
>> can run in a predictable manner.  Such elements include configuration of
>> the service, networking, installed packages, etc.  In today¹s world,
>> when Trove spins up an Instance to deploy a database on, it creates that
>> Instance with the Users Credentials.  Thus, to Nova, the User has full
>> access to that Instance through Nova¹s API.  This access can be used in
>> ways which unintentionally compromise the service.
>> 
>> _Solution_
>> A proposal is being formed that would put such Instances in a read-only
>> or invisible mode from the perspective of Nova.  That is, the Instance
>> can only be managed from the Service from which it was created.  At this
>> point, we do not need any granular controls.  A simple lock-down of the
>> Nova API for these Instances would suffice.  However, Trove would still
>> need to interact with this Instance via Nova API.
>> 
>> The basic requirements for Nova would beŠ
>> 
>>     A way to identify a request originating from a Service vs coming
>>     directly from an end-user
>>     A way to Identify which instances are being managed by a Service
>>     A way to prevent some or all access to the Instance unless the
>>     Service ID in the request matches that attached to the Instance
>> 
>> Any feedback on this would be appreciated.
>
>The use case makes sense to me.  I'm thinking we should expect an
>identity to be created in Keystone for trove and have trove use that for
>managing all of its instances.
>
>If that is sufficient, trove would need some changes to use its service
>credentials instead of the user credentials.  I don't think any changes
>are needed in Nova.
>
>Is there anything missing to support your use case using that approach?
>
>-- 
>Russell Bryant
>
>_______________________________________________
>OpenStack-dev mailing list
>OpenStack-dev at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5441 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140406/45bf8aa2/attachment.bin>