Editing Standard Lamp Template

[kapow]

First warning: I'm new, so please forgive me.

I've been only working with AppLogic for about a week. I first wanted to create a Ruby on Rails installation on the web server appliance, but the Fedora version wouldn't support the Ruby version (latest) I needed.

I have now a WEB5 appliance with CentOS 5. My attempt to create a new application template by replacing the Fedora instance with the CentOS has failed and I'm sure I'm missing some step somewhere.

What I did was:
- Copy the LAMP application
- Add the WEB5 CentOS appliance
- Remove the connections to the Fedora server and connect them to the WEB5 appliance
- Delete the Fedora server appliance

First thing I notice is that the application properties are messed up. No types. I'm assuming there is missing association with the redirects from the appliances. I branched WEB5, opened the properties and saved them back and they seemed to show up fine.

I checked all the properties, volumes, etc. to ensure they matched closely to the LAMP application template, but when I try to provision the app, the net appliance times out when trying to instantiate it.

Any clues or tutorials on this is greatly appreciated. Thanks.

[PeterNic]

Kapow,

Thanks for using the forums -- you will get the help you need here.

1. First, how you can create a LAMP template with a CentOS-5 based web server

- copy the lamp template, say into lamp5
- edit the new lamp5 template
- in the editor, select the catalog that has WEB5 in it
- shift-drag the WEB5 appliance from the catalog and drop it over the web server in the lamp5 app (keep the shift down until after releasing the mouse button). You will be asked if you want to replace the instance of WEB with an instance of WEB5, confirm.
- save the lamp5 template and use freely.

The shift-drag replacement of appliances is described in the infrastructure editor docs. See there for more details.

2. What went wrong in what you did?

You didn't complete it. Application-level properties are always propagated to properties of one or more appliances. When you deleted the old WEB appliance, the properties that used to go to the web appliance became orphaned -- not leading to anything. To make the copy you made work, you would need to configure the new web appliance -- set its properties to the values they were in the old appliance (values may be explicit values, like 0 or 1, or "redirects" to the application's boundary -- again, read on this more in the Instance settings, Properties docs of the infrastructure editor). Of course, if you use the method #1 above, this won't be necessary -- the shift-drag class change retains the properties and connections (which is why we added it :).

Let me know if this helps.

Regards,
-- Peter

BTW, 3Tera just released AppLogic 2.1.1, which contains a number of bugfixes, and, I believe, has all the templates updated to use the new appliances.

[kapow]

Awesome! I knew there was a simple way. Worked first time and so simple. Thank you very much!