Ah, systemvm.iso was moved to
/usr/lib64/cloud/common/vms/systemvm.iso, so now the agent can't find
it. I'll fix up a patch to LibvirtComputingResource.java

On Thu, Sep 20, 2012 at 11:44 AM, Marcus Sorensen <shadow...@gmail.com> wrote:
> Have there been any changes around this? I don't seem to be getting
> the systemvm.iso anymore when I launch a system vm, so I never get the
> latest cloud-early-config, etc.
>
> On Tue, Sep 11, 2012 at 3:24 PM, Wido den Hollander <w...@widodh.nl> wrote:
>>
>>
>> On 09/11/2012 10:10 PM, Chiradeep Vittal wrote:
>>>
>>>
>>>
>>> On 9/11/12 12:55 PM, "Wido den Hollander" <w...@widodh.nl> wrote:
>>>
>>>> Hi,
>>>>
>>>> Currently the management server does some magic stuff with systemvm.iso
>>>> like injecting keys into it with injectkeys.sh on boot.
>>>>
>>>> However, is this still required? I can't find any reference that we
>>>> transfer this modified ISO from the management server to the Hypervisor,
>>>> do we? As it seems the SSH keys are injected by the Agent and no longer
>>>> by the management server.
>>>
>>>
>>> The ssh keys are generated by the management server on first startup and
>>> injected into the ISO.
>>> This ISO is copied down to the XenServer (CitrixResourceBase.setupServer)
>>> and mounted by the system vm.
>>>
>>> When the system vm boots, it checks for this key and copies it into
>>> authorized keys. See
>>> patches/systemvm/debian/config/etc/init.d/cloud-early-config
>>>
>>
>> Ah, yes. I was confused by KVM, the process there works differently. It's
>> the Agent which injects the key into the systemvm.
>>
>>
>>>>
>>>> I'd like to get rid of this code as it seems to confuse people.
>>>>
>>>> "injectkeys.sh" is also part of the cloud-agent-scripts package which I
>>>> don't want to have installed on a management server.
>>>>
>>
>> The script should then however be moved from package. Imho it's not correct
>> to install cloud-agent-scripts on a management server.
>>
>> Wido
>>
>>
>>>> I think it can be removed, but I'd just want conformation.
>>>
>>>
>>> No, for the above reasons.
>>> --
>>> Chiradeep
>>>
>>

Reply via email to