Revision history [back]

Hey everybody. I'm experimenting with programmatically provisioning the OpenStudio-server, and Ry Horsey suggested I give the openstudio_meta executable a try. It looks awesome, because it should take a lot of the heavy lifting out of trying to provision an AWS instance on the fly, and I do mean a lot of heavy lifting. Anyway, I'm playing around with it, and I thought this would be a chance to document what I'm doing and hopefully get some questions answered.

First, I used this executable, in the /bin folder of the Openstudio-server. I execute it with $ ./openstudio_meta <some command=""> on my Mac, and all is fine there. Seems to be working.

The executable as far as I can tell is not documented. But if you type --help at the end of any command, it appears to give you some instructions on options you can provide, etc.

There are six different commands you can run install_gems (not sure why we need gems if we are running remotely...but it seems the most logical and probably some dependencies are needed for this executable to run) start local/remote run stop local/remote

I believe, but have not yet verified, that this is more or less the order in which you'd want to use this executable.

I haven't gotten that far yet with this, right now I'm stuck on install_gems. I don't think it is the fault of the executable, I think it is a problem with my ruby environment. When I run $ ./openstudio_meta install_gems, bundler works, it installs everything in my gems folder, and then I see a bunch of health Using <gemname> statements ... followed by :

Bundle updated! Gems in the group test, development, and docker were not installed.

Then rake aborted!

I see something along the lines of Load Error: cannot load such file -openstudio

I believe the reason this is happening is because I recently upgraded to Ruby 2.2.4 to be able to run OpenStudio 2.1 on my Mac, and I use RVM to manage my rubies and gemsets. I'm thinking that my ruby environment needs a tweak to get RVM gems and OpenStudio talking to one another. I've tried making modifications to my $PATH, but so far nothing is working.

Any thoughts? I'm hoping to keep posting as fixes are made to document this process for others who may use it.

Hey everybody. I'm experimenting with programmatically provisioning the OpenStudio-server, and Ry Horsey suggested I give the openstudio_meta openstudio_meta executable a try. It looks awesome, because it should take a lot of the heavy lifting out of trying to provision an AWS instance on the fly, and I do mean a lot of heavy lifting. Anyway, I'm playing around with it, and I thought this would be a chance to document what I'm doing and hopefully get some questions answered.

First, I used this executable, in the /bin /bin folder of the Openstudio-server. I execute it with $ ./openstudio_meta <some command=""> command> on my Mac, and all is fine there. Seems to be working.

The executable as far as I can tell is not documented. But if you type --help --help at the end of any command, it appears to give you some instructions on options you can provide, etc.

There are six different commands you can run install_gems run

• install_gems (not sure why we need gems if we are running remotely...but it seems the most logical and probably some dependencies are needed for this executable to run) run)

• start local/remote run local/remote

• run
• stop local/remote

I believe, but have not yet verified, that this is more or less the order in which you'd want to use this executable.

I haven't gotten that far yet with this, right now I'm stuck on install_gems. I don't think it is the fault of the executable, I think it is a problem with my ruby environment. When I run $ ./openstudio_meta install_gems, install_gems, bundler works, it installs everything in my gems folder, and then I see a bunch of health Using <gemname> statements ... followed by :

Then rake aborted!

I see something along the lines of of

Load Error: cannot load such file -openstudio

I believe the reason this is happening is because I recently upgraded to Ruby 2.2.4 to be able to run OpenStudio 2.1 on my Mac, and I use RVM to manage my rubies and gemsets. I'm thinking that my ruby environment needs a tweak to get RVM gems and OpenStudio talking to one another. I've tried making modifications to my $PATH, $PATH, but so far nothing is working.

Any thoughts? I'm hoping to keep posting as fixes are made to document this process for others who may use it.

Hey everybody. I'm experimenting with programmatically provisioning the OpenStudio-server, and Ry Horsey suggested I give the openstudio_meta executable a try. It looks awesome, because it should take a lot of the heavy lifting out of trying to provision an AWS instance on the fly, and I do mean a lot of heavy lifting. Anyway, I'm playing around with it, and I thought this would be a chance to document what I'm doing and hopefully get some questions answered.

First, I used this executable, in the /bin folder of the Openstudio-server. I execute it with $ ./openstudio_meta <some command> on my Mac, and all is fine there. Seems to be working.

The executable as far as I can tell is not documented. But if you type --help at the end of any command, it appears to give you some instructions on options you can provide, etc.

There are six different commands you can run

• install_gems (not sure why we need gems if we are running remotely...but it seems the most logical and probably some dependencies are needed for this executable to run)

• start local/remote

• run
• stop local/remote

I believe, but have not yet verified, that this is more or less the order in which you'd want to use this executable.

I haven't gotten that far yet with this, right now I'm stuck on install_gems. I don't think it is the fault of the executable, I think it is a problem with my ruby environment. When I run $ ./openstudio_meta install_gems, bundler works, it installs everything in my gems folder, and then I see a bunch of health Using <gemname> statements ... followed by :

Bundle updated!

Gems in the group test, development, and docker were not installed.

Then rake aborted!

I see something along the lines of

Load Error: cannot load such file -openstudio

I believe the reason this is happening is because I recently upgraded to Ruby 2.2.4 to be able to run OpenStudio 2.1 on my Mac, and I use RVM to manage my rubies and gemsets. I'm thinking that my ruby environment needs a tweak to get RVM gems and OpenStudio talking to one another. I've tried making modifications to my $PATH, but so far nothing is working.

Any thoughts? I'm hoping to keep posting as fixes are made to document this process for others who may use it.

Hey everybody. I'm experimenting with programmatically provisioning the OpenStudio-server, and Ry Horsey suggested I give the openstudio_meta executable a try. It looks awesome, because it should take a lot of the heavy lifting out of trying to provision an AWS instance on the fly, and I do mean a lot of heavy lifting. Anyway, I'm playing around with it, and I thought this would be a chance to document what I'm doing and hopefully get some questions answered.

First, I used this executable, in the /bin folder of the Openstudio-server. I execute it with $ ./openstudio_meta <some command> on my Mac, and all is fine there. Seems to be working.

The executable as far as I can tell is not documented. But if you type --help at the end of any command, it appears to give you some instructions on options you can provide, etc.

There are six different commands you can run

• install_gems (not sure why we need gems if we are running remotely...but it seems the most logical and probably some dependencies are needed for this executable to run)

• start local/remote

• run
• stop local/remote

I believe, but have not yet verified, that this is more or less the order in which you'd want to use this executable.

I haven't gotten that far yet with this, right now I'm stuck on install_gems. I don't think it is the fault of the executable, I think it is a problem with my ruby environment. When I run $ ./openstudio_meta install_gems, bundler works, it installs everything in my gems folder, and then I see a bunch of health Using <gemname> statements ... followed by :

Bundle updated!

Gems in the group test, development, and docker were not installed.

Then rake aborted!

I see something along the lines of

Load Error: cannot load such file -openstudio

I believe the reason this is happening is because I recently upgraded to Ruby 2.2.4 to be able to run OpenStudio 2.1 on my Mac, and I use RVM to manage my rubies and gemsets. I'm thinking that my ruby environment needs a tweak to get RVM gems and OpenStudio talking to one another. I've tried making modifications to my $PATH, but so far nothing is working.

Any thoughts? I'm hoping to keep posting as fixes are made to document this process for others who may use it.

I'm experimenting with programmatically provisioning the OpenStudio-server, and Ry Horsey suggested I give the openstudio_meta executable a try. It looks awesome, because it should take a lot of the heavy lifting out of trying to provision an AWS instance on the fly, and I do mean a lot of heavy lifting. Anyway, I'm playing around with it, and I thought this would be a chance to document what I'm doing and hopefully get some questions answered.

First, I used this executable, in the /bin folder of the Openstudio-server. I execute it with $ ./openstudio_meta <some command> on my Mac, and all is fine there. Seems to be working.

The executable as far as I can tell is not documented. But if you type --help at the end of any command, it appears to give you some instructions on options you can provide, etc.

There are six different commands you can run

• install_gems (not sure why we need gems if we are running remotely...but it seems the most logical and probably some dependencies are needed for this executable to run)

• start local/remote

• run
• stop local/remote

I believe, but have not yet verified, that this is more or less the order in which you'd want to use this executable.

I haven't gotten that far yet with this, right now I'm stuck on install_gems. I don't think it is the fault of the executable, I think it is a problem with my ruby environment. When I run $ ./openstudio_meta install_gems, bundler works, it installs everything in my gems folder, and then I see a bunch of health Using <gemname> statements ... followed by :

Bundle updated!

Gems in the group test, development, and docker were not installed.

Then rake aborted!

I see something along the lines of

Load Error: cannot load such file -openstudio

I believe the reason this is happening is because I recently upgraded to Ruby 2.2.4 to be able to run OpenStudio 2.1 on my Mac, and I use RVM to manage my rubies and gemsets. I'm thinking that my ruby environment needs a tweak to get RVM gems and OpenStudio talking to one another. I've tried making modifications to my $PATH, but so far nothing is working.

Any thoughts? I'm hoping to keep posting as fixes are made to document this process for others who may use it.

I'm experimenting with programmatically provisioning the OpenStudio-server, and Ry Horsey suggested I give the openstudio_meta executable a try. It looks awesome, because it should take a lot of the heavy lifting out of trying to provision an AWS instance on the fly, and I do mean a lot of heavy lifting. Anyway, I'm playing around with it, and I thought this would be a chance to document what I'm doing and hopefully get some questions answered.

First, I used this executable, in the /bin folder of the Openstudio-server. I execute it with $ ./openstudio_meta <some command> on my Mac, and all is fine there. Seems to be working.

The executable as far as I can tell is not documented. But if you type --help at the end of any command, it appears to give you some instructions on options you can provide, etc.

There are six different commands you can run

• install_gems (not sure why we need gems if we are running remotely...but it seems the most logical and probably some dependencies are needed for this executable to run)

• start local/remote

• run
• stop local/remote

I believe, but have not yet verified, that this is more or less the order in which you'd want to use this executable.

I haven't gotten that far yet with this, right now I'm stuck on install_gems. I don't think it is the fault of the executable, I think it is a problem with my ruby environment. When I run $ ./openstudio_meta install_gems, bundler works, it installs everything in my gems folder, and then I see a bunch of health Using <gemname> statements ... followed by :

Bundle updated!

Gems in the group test, development, and docker were not installed.

Then rake aborted!

I see something along the lines of

Load Error: cannot load such file -openstudio

I believe the reason this is happening is because I recently upgraded to Ruby 2.2.4 to be able to run OpenStudio 2.1 on my Mac, and I use RVM to manage my rubies and gemsets. I'm thinking that my ruby environment needs a tweak to get RVM gems and OpenStudio talking to one another. I've tried making modifications to my $PATH, but so far nothing is working.

Any thoughts? I'm hoping to keep posting as fixes are made to document this process for others who may use it.

I'm experimenting with programmatically provisioning the OpenStudio-server, and Ry Horsey suggested I give the openstudio_meta executable a try. It looks awesome, because it should take a lot of the heavy lifting out of trying to provision an AWS instance on the fly, and I do mean a lot of heavy lifting. Anyway, I'm playing around with it, and I thought this would be a chance to document what I'm doing and hopefully get some questions answered.

First, I used this executable, in the /bin folder of the Openstudio-server. I execute it with $ ./openstudio_meta <some command> on my Mac, and all is fine there. Seems to be working.

The executable as far as I can tell is not documented. But if you type --help at the end of any command, it appears to give you some instructions on options you can provide, etc.

There are six different commands you can run

• install_gems (not sure why we need gems if we are running remotely...but it seems the most logical and probably some dependencies are needed for this executable to run)

• start local/remote

• run
• stop local/remote

I believe, but have not yet verified, that this is more or less the order in which you'd want to use this executable.

I haven't gotten that far yet with this, right now I'm stuck on install_gems. I don't think it is the fault of the executable, I think it is a problem with my ruby environment. When I run $ ./openstudio_meta install_gems, bundler works, it installs everything in my gems folder, and then I see a bunch of health Using <gemname> statements ... followed by :

Bundle updated!

Gems in the group test, development, and docker were not installed.

Then rake aborted!

I see something along the lines of

Load Error: cannot load such file -openstudio

I believe the reason this is happening is because I recently upgraded to Ruby 2.2.4 to be able to run OpenStudio 2.1 on my Mac, and I use RVM to manage my rubies and gemsets. I'm thinking that my ruby environment needs a tweak to get RVM gems and OpenStudio talking to one another. I've tried making modifications to my $PATH, but so far nothing is working.

Any thoughts? I'm hoping to keep posting as fixes are made to document this process for others who may use it.