SLA Appliance

[BeckyHester]

This topic is dedicated to questions and comments related to the SLA - SLA Controller appliance.
The SLA data sheet can be found at:
AppLogic 2.4.x: http://doc.3tera.net/AppLogic24/CatDynSla.html
AppLogic 2.7.x: http://doc.3tera.net/AppLogic27/CatDynSla.html (page will be published concurrently with 2.7 release)

Please post any questions and/or comments here.

[igord]

Hello Becky and others,

we are trying to setup SLA on 2.8.9 grid version into one of test application, and constantly receiving message:

"
Aug 18 14:24:24 Grid28test applogic: [233:error s:47]: srv1: VM 'vm.srv1.test_application.main.SLA.ctl' failed to start.
Aug 18 14:24:24 Grid28test applogic: [803:error s:47]: srv1: test_application:main.SLA.ctl: ERROR: grid controller query failed - either wrong grid_ctl_ip or private key file does not authenticate
Aug 18 14:24:24 Grid28test applogic: [803:error s:47]: srv1: test_application:main.SLA.ctl: appliance start failed
"

we have followed procedure described on at

http://doc.3tera.com/AppLogic27/CatDynSlaExample.html

e.g. created public/private keys with ssh-keygen without password, copied private key to root of volume which is used for "config" at SLA, created user on grid using previously created public key with ssh-keygen, put right controller IP into SLA attributes... but always receiving that error!

Please, do you have any info about what are we missing?

Thanks in advance!

[andybrucenet]

I'm running into this problem as well with 3.0.30 in September of 2011. Any ideas since 2009?? Like where to start in debugging it??

[GChiba]

I tested SLA appliance on ver.2.9.9 grid and works fine.

Please check it as below steps.
1. try "app start --debug appname"
2. login as "ssh appname:main.SLA.ctl"
3. and attempt pub-key auth with simple ssh command "ssh -i private_key_name controller_ip"

if you get 3tshell as a result, pub-key authentication is working fine. and your failure is depends on any other reasons...
SLA appliance hooking 3tshell command via ssh connection. I think if you can access via above steps, it is working easily ;-)

[andybrucenet]

The problem? I inherited this project and did not realize that for a newly provisioned application the admin group doesn't have permissions.

In my case: "app modify_acl [app_name] local:group:admin=full" did the trick.

The SLA user associated with the public key for the generated grid-private key is a member of the local "admin" group. So now it works fine.

Thanks for the tips!

[GChiba]

Dear andy,

Yes... ACL information has not notified in ver.3.0.30. So when you created new user or new applications on the AppLogic controller, you have to a modify ACL informations manually as below.
- After created new user
> grid modiy_acl local:user:new_user=grid_administrator
("grid_administrator" have permission of full access controll)

- After create new applications
> app modify_acl [app_name] local:group:all=full
(group "all" is a default group for ALL users. and above means "add full access for all users")

or...

> app modify_acl [app_name] local:user:admin=owner
(setting ownership for created application)

regards ;-)