I just checked in the changes for this, so initial virtualization configuration becomes :
asadmin create-ims-config-native for Native/laptop mode
asadmin create-ims-config-libivrt for libvirt
so for example :
$WS_HOME/appserver/distributions/glassfish/glassfish3/glassfish/bin/asadmin create-ims-config-libvirt kvm
for kvm
jerome
On Sep 12, 2011, at 9:44 AM, Shreedhar Ganapathy wrote:
> CC'ing folks who need to know
>
> On 9/12/11 9:25 AM, Jerome Dochez wrote:
>> ok that's fine with me.
>>
>> On Sep 12, 2011, at 9:20 AM, Tom Mueller wrote:
>>
>>> On 9/12/2011 11:13 AM, Jerome Dochez wrote:
>>>> On Sep 9, 2011, at 10:05 AM, Tom Mueller wrote:
>>>>
>>>>> Jerome,
>>>>> On the scrum call you asked about ideas for a different name than "add-virtualization".
>>>>>
>>>>> How about:
>>>>>
>>>>> add-infrastructure-config
>>>>>
>>>>> or
>>>>>
>>>>> add-ims-config
>>>>>
>>>>> or maybe:
>>>>>
>>>>> create-ims-config
>>>> I could use that. the issue is that the command is virtualization specific so we will need things like :
>>>>
>>>> create-libvirt-ims-config
>>>> create-native-ims-config
>>>>
>>>> sounds good ?
>>> For other create commands that have various types, the syntax seems to be "create-<thing>-<subtype-of-thing>", as in:
>>>
>>> create-connector-connection-pool
>>> create-connector-resource
>>> create-connector-security-map
>>> create-connector-work-security-map
>>>
>>> create-node-config
>>> create-node-dcom
>>> create-node-ssh
>>>
>>> Following this pattern, should this be
>>>
>>> create-ims-config-libvirt
>>> create-ims-config-native
>>>
>>> ?
>>>
>>>
>>>>> This last one would parallel create-http-lb-config.
>>>>>
>>>>> Tom
>>>>>