Sean McGrath wrote:
> David Garcia - ONPIT stated:
>   
>> Sean McGrath wrote:
>>     
>>> David Garcia - ONPIT stated:
>>>   
>>>       
>>>> On 27/02/09 17:33, Sean McGrath wrote:
>>>>     
>>>>         
>>>>> David Garcia - ONPIT stated:
>>>>>          
>>>>>           
>>>>>> Sean McGrath wrote:
>>>>>>              
>>>>>>             
>>>>>>> David Garcia - ONPIT stated:
>>>>>>>
>>>>>>>                  
>>>>>>>               
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I'm not sure whether this is a bug or an enhancement request..
>>>>>>>>
>>>>>>>> For x86 machines, whenever we add a new client it'll create specific
>>>>>>>> entries on /tftpboot for that client based in its mac address. We use
>>>>>>>>   this in our environment to have fixed DHCP entries.
>>>>>>>>
>>>>>>>> However, we can't do that for sparc machines at the moment since no
>>>>>>>> specific entries are created in
>>>>>>>> http://$SERVER_IP:555/var/ai/image-server/images/$IMAGE-CONTAINER
>>>>>>>>
>>>>>>>>
>>>>>>>> We workarounded this by adding a link to the AI folder with the mac
>>>>>>>> address of our client so we can have this feature on sparc machines.
>>>>>>>> I'll explain it better with an example:
>>>>>>>>
>>>>>>>> - installadm create-service -n snv_106_sparc -s $ISO
>>>>>>>> /export/macroroot/snv_106_sparc/
>>>>>>>> - installadm create-client -n snv_106_sparc -e $MAC -t
>>>>>>>> /export/macroroot/snv_106_sparc/
>>>>>>>> - ln -s /export/macroroot/snv_106_sparc/
>>>>>>>> /var/ai/image-server/images/export/macroroot/$MAC
>>>>>>>>
>>>>>>>>                      
>>>>>>>>                 
>>>>>>>    installadm should create that symlink for you.
>>>>>>>
>>>>>>>    My installadm version is:
>>>>>>> VERSION:  11.11,REV=2009.02.16.04.00
>>>>>>>     (and will be updated again real soon).
>>>>>>>    installadm gets a good deal of fixes all the time, updating it every
>>>>>>>    two weeks at least can be a good idea.
>>>>>>>
>>>>>>>    It creates the symlinks fine here on my server.
>>>>>>>
>>>>>>> Sean.
>>>>>>> .
>>>>>>>
>>>>>>>                  
>>>>>>>               
>>>>>> I indeed updated it, actually 2 hours before I sent the email.
>>>>>>              
>>>>>>             
>>>>>    Possible bug then.  installadm create-service calls the setup-image 
>>>>> script
>>>>>     which has this code.
>>>>>          
>>>>>           
>>>> I'm afraid you misread my email. If you read it again you'll notice I 
>>>>  was referring on adding a *new client*, not a new service (which 
>>>> works  perfectly in my system)
>>>>     
>>>>         
>>>   so the installadm create-service creates the symlinks ok then ?
>>>   
>>>       
>> Yes.
>>
>>     
>>>   But you need to create the symlink after installadm add/create-client ?
>>>   
>>>       
>> Yes, in case I want to use a static DHCP entry for my client, as stated  
>> in the subject.
>>
>>     
>>>     Seems then this symlink is getting deleted somewhere.
>>>   
>>>       
>> No, because I'm not talking about the same link.
>> When you create a service, it'll create a link pointing at the AI  
>> folder, so in my particular case the DHCP server needs to point at:  
>> http://$SERVER:5555/export/macroroot/snv_106_sparc
>>
>> Now what I'm talking about here is, that I want *another* link to be  
>> created when I add a client, something like:
>> http://SSERVER:5555/export/macroroot/0:14:4f:e5:fb:50
>>     
>
>   Ah, ok.  Thats where we differ.  I too have static dhcp entries but
>    for sparc we leave the Rootpath part of the dhcp macro pointing to the
>    http://$SERVER:5555/export/macroroot/snv_106_sparc 
>   

Then it's not static. Meaning if you want a new service (i.e. 
snv_108_sparc) to install that particular machine, you will have to edit 
your DHCP macro to point to the new location. If create-client created 
and managed that new link based on the client's MAC address, you 
wouldn't have to.

David

Reply via email to