Re: Issue with Scalarizr on Windows 2012

2016-09-20 Thread Marc O'Brien
Hi Jeff,

It appears that the instance is unable to connect to the Openstack 
meta-data server and eventually gives up:
  
agent.scalrinit.metadata.openstack - Does not fit: 
HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded 
with url: /openstack/latest/meta_data.json (Caused by 
ConnectTimeoutError(, 'Connection to 169.254.169.254 timed out.
...
ERROR - agent.scalrinit.app - No Instance-Id: User-data file 
/mnt/config\openstack\latest\meta_data.json do not exist or not accessible.

ERROR - upd.client ..  NoUserdataError: User-data file 
/mnt/config\openstack\latest\meta_data.json do not exist or not accessible.


We are calling http://169.254.169.254/openstack/latest/meta_data.json which 
should contain the user-data.  Are you able to execute the following from 
the impacted instance?  Are you able to do the same from your successfully 
launched CentOS or RHEL instances?

curl http://169.254.169.254/openstack/latest/meta_data.json 

Many thanks,
Wm. Marc O'Brien
Scalr Technical Support


On Tuesday, September 20, 2016 at 4:39:21 PM UTC-6, Jeff Gojkovich wrote:
>
> Hey Marc
> We are using 5.11.22 (Community Edition)
> I am attaching the entire log directory.  We have never got a Windows 
> instance to launch successfully with the scalarizr agent.  We have got 
> CentOS and RedHat instances to launch successfully.
>
> On Tuesday, September 20, 2016 at 3:24:33 PM UTC-7, Marc O'Brien wrote:
>>
>> Hi Jeff,
>>
>> What version of Scalr are you using?  Have Openstack Windows 2012 
>> instances previously launched successfully?  Are you seeing these issues 
>> with any other instances?  Copies of the following logs from 
>> C:\opt\scalarizr\var\log may be helpful:
>>
>> scalarizr.log
>> scalarizr_debug.log
>> scalarizr_update.log
>>
>> Many thanks,
>> Wm. Marc O'Brien
>> Scalr Technical Support
>>
>> On Tuesday, September 20, 2016 at 3:51:16 PM UTC-6, Jeff Gojkovich wrote:
>>>
>>> I am trying to launch an instance in an Openstack environment utilizing 
>>> Scalr and it hangs at "Waiting for OS to finish booting".  It looks like 
>>> the scalarizr agent isn't automatically started on the instance and when I 
>>> manually start it, the build still does not finish.  Let me know what steps 
>>> I can take to further troubleshoot the issue.
>>>
>>> This is the scalarizr log
>>>
>>> *2016-09-20 21:43:19,257+00:00 - INFO - scalarizr.app - [pid: 1840] 
>>> Starting scalarizr 4.11.2*
>>> *2016-09-20 21:43:19,273+00:00 - INFO - scalarizr.node - State: unknown*
>>> *2016-09-20 21:43:19,305+00:00 - INFO - scalarizr.app - Polling 
>>> UpdateClient state...*
>>> *2016-09-20 21:44:20,039+00:00 - WARNING - scalarizr.app - Failed to 
>>> talk to UpdateClient: Failed to get UpdateClient status. Timeout: 60 
>>> seconds reached*
>>> *2016-09-20 21:45:20,555+00:00 - ERROR - scalarizr.app - 
>>> UpdateClient(scalr-init) completion flag 
>>> C:\opt\scalarizr\var\run\result.json still not available after 60 seconds.*
>>> *Check that 'ScalrUpdClient' service has no errors in log.*
>>>
>>>
>>> This is in the scalarizr_update.log file
>>>
>>> *2016-09-20 21:43:25,539 - INFO - agent.scalrinit.metadata - Meta-data 
>>> providers that fit: [, ]*
>>> *2016-09-20 21:43:25,539 - DEBUG - agent.scalrinit.metadata.configdrive 
>>> - Found meta_data.json*
>>> *2016-09-20 21:43:25,539 - INFO - agent.scalrinit.metadata - Best match 
>>> for Instance-Id: *
>>> *2016-09-20 21:43:25,539 - DEBUG - agent.scalrinit.metadata.configdrive 
>>> - Found meta_data.json*
>>> *2016-09-20 21:43:25,539 - INFO - agent.scalrinit.metadata - Best-match 
>>> for User-data: *
>>> *2016-09-20 21:43:25,539 - ERROR - agent.scalrinit.app - No Instance-Id: 
>>> User-data file /mnt/config\openstack\latest\meta_data.json do not exist or 
>>> not accessible.*
>>> *2016-09-20 21:43:25,539 - INFO - upd.client - Stopping UpdateClient*
>>> *2016-09-20 21:43:25,539 - INFO - upd.client - Stopped*
>>> *2016-09-20 21:43:25,539 - ERROR - upd.client - Detailed exception 
>>> information below:*
>>> *Traceback (most recent call last):*
>>> *  File 
>>> "C:\opt\scalarizr\4.11.2\embedded\lib\site-packages\scalarizr-4.11.2-py2.7.egg\scalarizr\updclient\app.py",
>>>  
>>> line 184, in do_start*
>>> *agent.scalrinit.app.main_start()*
>>> *  File 
>>> "C:\opt\scalarizr\4.11.2\embedded\lib\site-packages\fatmouse_agent-0.1.26ad7587c-py2.7.egg\agent\scalrinit\app.py",
>>>  
>>> line 26, in main_start*
>>> *instance_id = metadata.instance_id()*
>>> *  File 
>>> "C:\opt\scalarizr\4.11.2\embedded\lib\site-packages\fatmouse_agent-0.1.26ad7587c-py2.7.egg\common\utils\mixutil.py",
>>>  
>>> line 297, in wrapper*
>>> *func._memorized = func(*args, **kwds)*
>>> *  File 
>>> "C:\opt\scalarizr\4.11.2\embedded\lib\site-packages\fatmouse_agent-0.1.26ad7587c-py2.7.egg\agent\scalrinit\metadata.py",
>>>  
>>> line 578, in instance_id*
>>> *return create_provider(get_datasource()['instance_id']).instance_id*
>>> *  File 
>>> 

Re: Issue with Scalarizr on Windows 2012

2016-09-20 Thread Marc O'Brien
Hi Jeff,

What version of Scalr are you using?  Have Openstack Windows 2012 instances 
previously launched successfully?  Are you seeing these issues with any 
other instances?  Copies of the following logs from 
C:\opt\scalarizr\var\log may be helpful:

scalarizr.log
scalarizr_debug.log
scalarizr_update.log

Many thanks,
Wm. Marc O'Brien
Scalr Technical Support

On Tuesday, September 20, 2016 at 3:51:16 PM UTC-6, Jeff Gojkovich wrote:
>
> I am trying to launch an instance in an Openstack environment utilizing 
> Scalr and it hangs at "Waiting for OS to finish booting".  It looks like 
> the scalarizr agent isn't automatically started on the instance and when I 
> manually start it, the build still does not finish.  Let me know what steps 
> I can take to further troubleshoot the issue.
>
> This is the scalarizr log
>
> *2016-09-20 21:43:19,257+00:00 - INFO - scalarizr.app - [pid: 1840] 
> Starting scalarizr 4.11.2*
> *2016-09-20 21:43:19,273+00:00 - INFO - scalarizr.node - State: unknown*
> *2016-09-20 21:43:19,305+00:00 - INFO - scalarizr.app - Polling 
> UpdateClient state...*
> *2016-09-20 21:44:20,039+00:00 - WARNING - scalarizr.app - Failed to talk 
> to UpdateClient: Failed to get UpdateClient status. Timeout: 60 seconds 
> reached*
> *2016-09-20 21:45:20,555+00:00 - ERROR - scalarizr.app - 
> UpdateClient(scalr-init) completion flag 
> C:\opt\scalarizr\var\run\result.json still not available after 60 seconds.*
> *Check that 'ScalrUpdClient' service has no errors in log.*
>
>
> This is in the scalarizr_update.log file
>
> *2016-09-20 21:43:25,539 - INFO - agent.scalrinit.metadata - Meta-data 
> providers that fit: [, ]*
> *2016-09-20 21:43:25,539 - DEBUG - agent.scalrinit.metadata.configdrive - 
> Found meta_data.json*
> *2016-09-20 21:43:25,539 - INFO - agent.scalrinit.metadata - Best match 
> for Instance-Id: *
> *2016-09-20 21:43:25,539 - DEBUG - agent.scalrinit.metadata.configdrive - 
> Found meta_data.json*
> *2016-09-20 21:43:25,539 - INFO - agent.scalrinit.metadata - Best-match 
> for User-data: *
> *2016-09-20 21:43:25,539 - ERROR - agent.scalrinit.app - No Instance-Id: 
> User-data file /mnt/config\openstack\latest\meta_data.json do not exist or 
> not accessible.*
> *2016-09-20 21:43:25,539 - INFO - upd.client - Stopping UpdateClient*
> *2016-09-20 21:43:25,539 - INFO - upd.client - Stopped*
> *2016-09-20 21:43:25,539 - ERROR - upd.client - Detailed exception 
> information below:*
> *Traceback (most recent call last):*
> *  File 
> "C:\opt\scalarizr\4.11.2\embedded\lib\site-packages\scalarizr-4.11.2-py2.7.egg\scalarizr\updclient\app.py",
>  
> line 184, in do_start*
> *agent.scalrinit.app.main_start()*
> *  File 
> "C:\opt\scalarizr\4.11.2\embedded\lib\site-packages\fatmouse_agent-0.1.26ad7587c-py2.7.egg\agent\scalrinit\app.py",
>  
> line 26, in main_start*
> *instance_id = metadata.instance_id()*
> *  File 
> "C:\opt\scalarizr\4.11.2\embedded\lib\site-packages\fatmouse_agent-0.1.26ad7587c-py2.7.egg\common\utils\mixutil.py",
>  
> line 297, in wrapper*
> *func._memorized = func(*args, **kwds)*
> *  File 
> "C:\opt\scalarizr\4.11.2\embedded\lib\site-packages\fatmouse_agent-0.1.26ad7587c-py2.7.egg\agent\scalrinit\metadata.py",
>  
> line 578, in instance_id*
> *return create_provider(get_datasource()['instance_id']).instance_id*
> *  File 
> "C:\opt\scalarizr\4.11.2\embedded\lib\site-packages\fatmouse_agent-0.1.26ad7587c-py2.7.egg\agent\scalrinit\metadata.py",
>  
> line 333, in instance_id*
> *return json.loads(self.user_data)['uuid']*
> *  File 
> "C:\opt\scalarizr\4.11.2\embedded\lib\site-packages\fatmouse_agent-0.1.26ad7587c-py2.7.egg\agent\scalrinit\metadata.py",
>  
> line 326, in user_data*
> *.format(self._metadata_path))*
> *NoUserdataError: User-data file 
> /mnt/config\openstack\latest\meta_data.json do not exist or not accessible*
> .
>
>
>
>

-- 
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 scalr-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Issue with Scalarizr on Windows 2012

2016-09-20 Thread Jeff Gojkovich
I am trying to launch an instance in an Openstack environment utilizing 
Scalr and it hangs at "Waiting for OS to finish booting".  It looks like 
the scalarizr agent isn't automatically started on the instance and when I 
manually start it, the build still does not finish.  Let me know what steps 
I can take to further troubleshoot the issue.

This is the scalarizr log

*2016-09-20 21:43:19,257+00:00 - INFO - scalarizr.app - [pid: 1840] 
Starting scalarizr 4.11.2*
*2016-09-20 21:43:19,273+00:00 - INFO - scalarizr.node - State: unknown*
*2016-09-20 21:43:19,305+00:00 - INFO - scalarizr.app - Polling 
UpdateClient state...*
*2016-09-20 21:44:20,039+00:00 - WARNING - scalarizr.app - Failed to talk 
to UpdateClient: Failed to get UpdateClient status. Timeout: 60 seconds 
reached*
*2016-09-20 21:45:20,555+00:00 - ERROR - scalarizr.app - 
UpdateClient(scalr-init) completion flag 
C:\opt\scalarizr\var\run\result.json still not available after 60 seconds.*
*Check that 'ScalrUpdClient' service has no errors in log.*


This is in the scalarizr_update.log file

*2016-09-20 21:43:25,539 - INFO - agent.scalrinit.metadata - Meta-data 
providers that fit: [, ]*
*2016-09-20 21:43:25,539 - DEBUG - agent.scalrinit.metadata.configdrive - 
Found meta_data.json*
*2016-09-20 21:43:25,539 - INFO - agent.scalrinit.metadata - Best match for 
Instance-Id: *
*2016-09-20 21:43:25,539 - DEBUG - agent.scalrinit.metadata.configdrive - 
Found meta_data.json*
*2016-09-20 21:43:25,539 - INFO - agent.scalrinit.metadata - Best-match for 
User-data: *
*2016-09-20 21:43:25,539 - ERROR - agent.scalrinit.app - No Instance-Id: 
User-data file /mnt/config\openstack\latest\meta_data.json do not exist or 
not accessible.*
*2016-09-20 21:43:25,539 - INFO - upd.client - Stopping UpdateClient*
*2016-09-20 21:43:25,539 - INFO - upd.client - Stopped*
*2016-09-20 21:43:25,539 - ERROR - upd.client - Detailed exception 
information below:*
*Traceback (most recent call last):*
*  File 
"C:\opt\scalarizr\4.11.2\embedded\lib\site-packages\scalarizr-4.11.2-py2.7.egg\scalarizr\updclient\app.py",
 
line 184, in do_start*
*agent.scalrinit.app.main_start()*
*  File 
"C:\opt\scalarizr\4.11.2\embedded\lib\site-packages\fatmouse_agent-0.1.26ad7587c-py2.7.egg\agent\scalrinit\app.py",
 
line 26, in main_start*
*instance_id = metadata.instance_id()*
*  File 
"C:\opt\scalarizr\4.11.2\embedded\lib\site-packages\fatmouse_agent-0.1.26ad7587c-py2.7.egg\common\utils\mixutil.py",
 
line 297, in wrapper*
*func._memorized = func(*args, **kwds)*
*  File 
"C:\opt\scalarizr\4.11.2\embedded\lib\site-packages\fatmouse_agent-0.1.26ad7587c-py2.7.egg\agent\scalrinit\metadata.py",
 
line 578, in instance_id*
*return create_provider(get_datasource()['instance_id']).instance_id*
*  File 
"C:\opt\scalarizr\4.11.2\embedded\lib\site-packages\fatmouse_agent-0.1.26ad7587c-py2.7.egg\agent\scalrinit\metadata.py",
 
line 333, in instance_id*
*return json.loads(self.user_data)['uuid']*
*  File 
"C:\opt\scalarizr\4.11.2\embedded\lib\site-packages\fatmouse_agent-0.1.26ad7587c-py2.7.egg\agent\scalrinit\metadata.py",
 
line 326, in user_data*
*.format(self._metadata_path))*
*NoUserdataError: User-data file 
/mnt/config\openstack\latest\meta_data.json do not exist or not accessible*.



-- 
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 scalr-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Error while Sync Shared Roles

2016-09-20 Thread Amit Saini
Thanks Marc
Its Sync Now

Regards 
Amit

On Tuesday, September 20, 2016 at 2:25:28 PM UTC-4, Marc O'Brien wrote:
>
> Hi Amit,
>
> The whitelist request has been processed on our end.  Shared Roles Sync 
> should complete successfully for this installation now.  Can you test this 
> again?
>
> Many thanks,
> Wm. Marc O'Brien
> Scalr Technical Support
>
> On Tuesday, September 20, 2016 at 12:22:29 PM UTC-6, Marc O'Brien wrote:
>>
>> Hi Amit,
>>
>> I did see your whitelist request come through.  This message means that 
>> our whitelisting database does not yet have your Installation ID in place 
>> as we are still processing the whitelist request.
>>
>> You will receive a confirmation email soon once this has been completed 
>> on our end.  Let us know if issues persist after you have received the 
>> confirmation email.
>>
>> Many thanks,
>> Wm. Marc O'Brien
>> Scalr Technical Support
>>
>> On Tuesday, September 20, 2016 at 12:07:40 PM UTC-6, Amit Saini wrote:
>>>
>>> Hi Marc
>>>
>>> *I got the following error while Sync Shared Roles*
>>>
>>> amit@amit-virtual-machine:~$ sudo /opt/scalr-server/embedded/
>>> bin/php /opt/scalr-server/embedded/scalr/app/tools/sync_shared_roles.php
>>> [sudo] password for amit: 
>>> Unable to import shared roles: Unrecognized setup: update denied. Please 
>>> use this form http://hub.am/1fDAc2B to be 
>>> whitelisted.amit@amit-virtual-machine:~$
>>>
>>> Regards 
>>> Amit Saini
>>>
>>

-- 
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 scalr-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Error while Sync Shared Roles

2016-09-20 Thread Marc O'Brien
Hi Amit,

The whitelist request has been processed on our end.  Shared Roles Sync 
should complete successfully for this installation now.  Can you test this 
again?

Many thanks,
Wm. Marc O'Brien
Scalr Technical Support

On Tuesday, September 20, 2016 at 12:22:29 PM UTC-6, Marc O'Brien wrote:
>
> Hi Amit,
>
> I did see your whitelist request come through.  This message means that 
> our whitelisting database does not yet have your Installation ID in place 
> as we are still processing the whitelist request.
>
> You will receive a confirmation email soon once this has been completed on 
> our end.  Let us know if issues persist after you have received the 
> confirmation email.
>
> Many thanks,
> Wm. Marc O'Brien
> Scalr Technical Support
>
> On Tuesday, September 20, 2016 at 12:07:40 PM UTC-6, Amit Saini wrote:
>>
>> Hi Marc
>>
>> *I got the following error while Sync Shared Roles*
>>
>> amit@amit-virtual-machine:~$ sudo /opt/scalr-server/embedded/
>> bin/php /opt/scalr-server/embedded/scalr/app/tools/sync_shared_roles.php
>> [sudo] password for amit: 
>> Unable to import shared roles: Unrecognized setup: update denied. Please 
>> use this form http://hub.am/1fDAc2B to be 
>> whitelisted.amit@amit-virtual-machine:~$
>>
>> Regards 
>> Amit Saini
>>
>

-- 
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 scalr-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Error while Sync Shared Roles

2016-09-20 Thread Marc O'Brien
Hi Amit,

I did see your whitelist request come through.  This message means that our 
whitelisting database does not yet have your Installation ID in place as we 
are still processing the whitelist request.

You will receive a confirmation email soon once this has been completed on 
our end.  Let us know if issues persist after you have received the 
confirmation email.

Many thanks,
Wm. Marc O'Brien
Scalr Technical Support

On Tuesday, September 20, 2016 at 12:07:40 PM UTC-6, Amit Saini wrote:
>
> Hi Marc
>
> *I got the following error while Sync Shared Roles*
>
> amit@amit-virtual-machine:~$ sudo /opt/scalr-server/embedded/
> bin/php /opt/scalr-server/embedded/scalr/app/tools/sync_shared_roles.php
> [sudo] password for amit: 
> Unable to import shared roles: Unrecognized setup: update denied. Please 
> use this form http://hub.am/1fDAc2B to be 
> whitelisted.amit@amit-virtual-machine:~$
>
> Regards 
> Amit Saini
>

-- 
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 scalr-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Error while Sync Shared Roles

2016-09-20 Thread Amit Saini
Hi Marc

*I got the following error while Sync Shared Roles*

amit@amit-virtual-machine:~$ sudo /opt/scalr-server/embedded/
bin/php /opt/scalr-server/embedded/scalr/app/tools/sync_shared_roles.php
[sudo] password for amit: 
Unable to import shared roles: Unrecognized setup: update denied. Please 
use this form http://hub.am/1fDAc2B to be 
whitelisted.amit@amit-virtual-machine:~$

Regards 
Amit Saini

-- 
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 scalr-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Scalr-meta is not available in my AWS Console

2016-09-20 Thread Marc O'Brien
Hi Amit,

You will want to start by Syncing our Shared Roles 

 
in order to gain access to our catalog of standard Roles built from 
commonly used images.  Alternatively you can create your own Roles 
 if you 
prefer.  Once you have some Roles in your library, you will then want to 
start with our 3-Tier app tutorial 
.
  
This will be the best starting point to familiarize yourself with the 
construction of Farms, Farm Roles, and Scalr in general.  Let us know if 
you have any questions from here.

Cheers,
Wm. Marc O'Brien
Scalr Technical Support


On Tuesday, September 20, 2016 at 10:00:54 AM UTC-6, Amit Saini wrote:
>
> Hi Marc
>
> Could you please share me Scalr LINK to start EC2 Instance with Farms and 
> Role configurations...???
>
> Regards
> Amit  
>
> On Monday, September 19, 2016 at 6:57:30 PM UTC-4, Marc O'Brien wrote:
>>
>> Hi Amit,
>>
>> It sounds like the issue here is that you have not yet launched any AWS 
>> instances with Scalr using your Cloud Credentials.  You will need to do the 
>> following:
>>
>>1. Launch your first VM in Scalr, so it will tag this first resource.
>>2. Wait for 8 hours.
>>
>> Let us know if troubles persist at that point.
>>
>>
>> Many thanks,
>> Wm. Marc O'Brien
>> Scalr Technical Support
>>
>> On Monday, September 19, 2016 at 4:21:55 PM UTC-6, Marc O'Brien wrote:
>>>
>>> Hi Amit,
>>>
>>> Did you also Add and Save the Cloud Credentials for the AWS account 
>>> within Scalr?  In my testing once I have created and added the AWS 
>>> credentials to my Scalr deployment, Scalr then created the appropriate tags 
>>> within the AWS account.  If you have done this, are you able to launch 
>>> Farms and view the scalr-meta tag on any instance of Farm Roles that are 
>>> instantiated?  As shown in the attached screenshot of the Farm Designer, 
>>> Scalr will automatically provision Farm Role instances with this tag and 
>>> values specific to the instance.
>>>
>>> Many thanks,
>>> Wm. Marc O'Brien
>>> Scalr Technical Support
>>>
>>>
>>> 
>>>
>>

-- 
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 scalr-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Scalr-meta is not available in my AWS Console

2016-09-20 Thread Amit Saini
Hi Marc

Could you please share me Scalr like to start EC2 Instance with Farms and 
Role configurations...???

Regards
Amit  

On Monday, September 19, 2016 at 6:57:30 PM UTC-4, Marc O'Brien wrote:
>
> Hi Amit,
>
> It sounds like the issue here is that you have not yet launched any AWS 
> instances with Scalr using your Cloud Credentials.  You will need to do the 
> following:
>
>1. Launch your first VM in Scalr, so it will tag this first resource.
>2. Wait for 8 hours.
>
> Let us know if troubles persist at that point.
>
>
> Many thanks,
> Wm. Marc O'Brien
> Scalr Technical Support
>
> On Monday, September 19, 2016 at 4:21:55 PM UTC-6, Marc O'Brien wrote:
>>
>> Hi Amit,
>>
>> Did you also Add and Save the Cloud Credentials for the AWS account 
>> within Scalr?  In my testing once I have created and added the AWS 
>> credentials to my Scalr deployment, Scalr then created the appropriate tags 
>> within the AWS account.  If you have done this, are you able to launch 
>> Farms and view the scalr-meta tag on any instance of Farm Roles that are 
>> instantiated?  As shown in the attached screenshot of the Farm Designer, 
>> Scalr will automatically provision Farm Role instances with this tag and 
>> values specific to the instance.
>>
>> Many thanks,
>> Wm. Marc O'Brien
>> Scalr Technical Support
>>
>>
>> 
>>
>

-- 
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 scalr-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.