Dear Scalr team,
Will you comment on my query?
Thanks,
Swarup
On Thursday, June 18, 2015 at 10:49:08 PM UTC+5:30, Swarup Kotikalapudi
wrote:
>
> Dear All,
>
> I am experimenting on open source scalr, with Openstack and AWS automation
> related work.
>
> While working with Scalr I have some observations as mentioned below:
>
> a) I am seeing the VM bring up time becomes quiet longer whenever new
> scalarizr update is released. As scalr-upd-client tried to download latest
> scalrizr agent.
>
> b) In AWS , scalr-upd-client sometimes stuck in apt-get update. Please see
> below log from scalarizer_update.log
>
> 2015-06-18 06:31:27,486 - DEBUG - scalarizr.queryenv - QueryEnv
> response (parsed): {'scalr.id': '7a583212', 'scalr.version': '5.3.2',
> 'dns.static.endpoint': 'example-dns.net'}
> 2015-06-18 06:31:27,487 - INFO - scalarizr.linux.pkgmgr - Ensuring
> repository "scalr-stable" (file: /etc/apt/sources.list.d/scalr-stable.list)
> 2015-06-18 06:31:27,487 - INFO - scalarizr.updclient.api - Updating
> packages cache
> 2015-06-18 06:31:27,488 - DEBUG - scalarizr.util - system:
> ('/usr/bin/apt-get', '-q', '-y', '--force-yes', '-o
> Dpkg::Options::=--force-confold', 'update')
>
> c) Sometime VM launch itself failing in initialization phase.
> I had a role with Mysql customization selected during role creation
> with Ubuntu 14.04 Trusty image and scalarizer agent 3.4.4 , it was working
> fine till 7.30 IST 12th June, and we terminate and launch the farm around 8
> PM IST, the scalarizer agent changed to 3.6.2.
> The role was failing with env not defined. NameError: global name 'env' is
> not defined. I am attaching the scalarizr log for your reference.
>
> I understand Scalr recommend to use local repository to avoid going to
> Scalr server for updates, however as i am trying to understand/prototype
> with Scalr and not so good internet connectivity issue, I have following
> questions
>
> a) Does there is a option during development and testing phase, if we want
> to stick with a particular scalarizr agent version, to program/configure
> the scalr-upd-client not to upgrade to newer scalarizr version.
> b) Does during testing/exploration phase, if i disable scalr-upd-client,
> and run scalarizr agent only, will Scalarizer work properly for this kind
> of scenario. I understand feature enhancement/bug fix of a newer release we
> might not get by sticking to some particular version only.
>
> Thanks for your cooperation and support.
>
> Thanks,
> Swarup
>
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"scalr-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
