[Ovirt-devel] Re: Virtual machine configuration screen

[Bryan Kearney]

Perry N. Myers wrote:
> 
> 
> Bryan Kearney wrote:
>>
>>
>> Darryl L. Pierce wrote:
>>> +++ Scott Seago [28/07/08 16:56 -0400]:
>>>> Darryl L. Pierce wrote:
>>>>> The initial set of configurable options that I'm looking at are:
>>>> Is this something we should keep a copy of in the PG database, or 
>>>> should  we just grab a list of cobbler profiles when displaying the 
>>>> form to the  user (and then store this as a string)?
>>>
>>> I think it would be best to grab a copy the first time we need them 
>>> and then
>>> either hold onto it in memory for a time. I don't think we should be 
>>> storing
>>> that list in our schema, though. We can easily and quickly get the 
>>> list from
>>> Cobbler when/as needed.
>>
>> Are you assuming a dedicated cobbler service which is part of oVirt, 
>> or integration with a sepertae cobbler server? If the latter, do you 
>> have an issue with items being managed in cobbler which should not be 
>> in oVirt?
> 
> Both.  We need to be able to integrate with an existing cobbler server 
> if one exists and if it doesn't we need to be able to create a new 
> cobbler server.
> 
> As for 'hiding' specific profiles/images from oVirt, that is not 
> something we have considered.  What would the use case for this be?
> 
> Perry
> 

Just thinking out loud, but if there is a "public" cobbler server.. it 
is possible that there is some subset of the available profiles which 
they may want to enable via oVirt. For example.. "Dont touch DEV 
machines". This could be controlled via security, assuming both are 
using the same user base.

-- bk