| Admin iTeam Meeting Minutes May 11, 2010
- Hosted by Byron
- Discuss Config. A server instance has up to 4 different config & server elements to get its true configuration. Is this known/planned/working ??
- Related to previous bullet – If we allow stand-alone instances then they have *2* config & server elements. An example of the frequent special-case code for stand-alone instances. I still recommend not allowing them. Let's decide today!
- Let's discuss how we are going to pass information back and forth to the remote ssh gizmo.
- list-instance – It would be great if I could call RemoteCommand in admin-cli from the server-side in core/kernel. Is there any reason to NOT do this?
- __not a good idea. Instead Bill Shannmon developed RemoteAdminCommand in admin/util that is designed to be called from the server-side.
- Progress report from developers. This is a good time for more detailed debriefing. What have you been up to?
- Byron reported that he has the initial versions of start-local-instance, stop-instance and list-instances working. Delete-instance is next for Byron.
Old Resolved Action Items
- BYRON: What happens when you add a property to a cluster that has a reference to a config. Does it go into the cluster or the config elements?
- Answer: tested by creating a cluster with "--systemproperties foo=goo". It goes into the cluster element only.
- BYRON: Can you use server-config as a config-ref when making a new cluster in V2?
- __Answer - No! See below:
-config Creates a shared cluster. The specified configuration name must exist and must not be default-config (the standalone cluster configuration template) or a stan dalone configuration (including server-config). If this option is omitted, a standalone cluster is created. ~/eric/sailfin/bin>./aa_d2 create-cluster --config server-config cl3 The configuration of the Domain Administration Server (named server-config) cannot be referenced by a shared server instance or shared cluster. CLI137 Command create-cluster failed. __
|
