As I understand it, the global variable SCALR_INSTANCE_INDEX only has a
scope of its farm role. I was hoping to have one with a scope of the
environment or even of the account. We are going to be using environments
as organizations and they want to have a running index of all of their VMs.
On Monday, June 13, 2016 at 9:13:04 AM UTC-5, Jay Farschman wrote:
>
> Ronald,
>
> Maybe I don't understand what you want to to, but take a look at the
> "Environment Scope | Governance | Scalr | Server hostname format"
>
> {SCALR_FARM_ROLE_ALIAS}-{SCALR_INSTANCE_INDEX}
>
> Would that do it?
>
> On Wednesday, June 8, 2016 at 8:21:03 AM UTC-6, [email protected]
> wrote:
>>
>> It seems I can only modify global variables up to the farm or farm role
>> scope, not the environment or the account scope which is where I was
>> hoping. I don't see how a global variable at either of those scopes (farm
>> or farm role) can be applied to multiple VMs across an environment. We are
>> hoping to be able to name our hosts with a suffix that is an index that is
>> incremented once after each provision: -00001, -00002, -00003, and so on. I
>> guess the only way to do that is not with a sclar variable but with an
>> external database I guess.
>>
>> On Tuesday, June 7, 2016 at 1:14:53 PM UTC-5, [email protected]
>> wrote:
>>>
>>> Is there a way to modify user defined global variables via scripts in
>>> Scalr? I haven't found a way to do so yet. I'm trying to find a way to have
>>> an index that is used for host names that is used across an entire
>>> environment. From what I see the SCALR_INSTANCE_INDEX variable is only
>>> good for a single farm role so it has too limited a scope. This is with
>>> Open Stack. Thanks.
>>>
>>
--
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.
