Skip to content

Instantly share code, notes, and snippets.

@jrrickard
Last active August 29, 2015 14:23
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save jrrickard/a2724c9ede44de0186cc to your computer and use it in GitHub Desktop.
Save jrrickard/a2724c9ede44de0186cc to your computer and use it in GitHub Desktop.
Running lattice.cf on VMware AppCatalyst

I'll preface this by saying I don't think any of this is supported and AppCatalyst is a Tech Preview. But it's a great developer tool!

First, install AppCatalyst

Next, install the AppCatalyst Vagrant Provider

The Vagrant Provider needs the AppCatalyst REST API, so once installed, you need to start the AppCatalyst daemon: appcatalyst-daemon

start daemon

Finally, follow the Lattice.cf getting started guide, including installing ltc.

Once you get everything installed, the only real issue I had was networking.

The default subnet for AppCatalyst is 192.168.136.0, per Library/Preferences/VMware AppCatalyst/networking:

answer VNET_8_HOSTONLY_NETMASK 255.255.255.0
answer VNET_8_HOSTONLY_SUBNET 192.168.136.0

However, the Vagrantfile looks for an environment variable that contains the Lattice IP or it defaults to 192.168.11.11. The IP seems to increment by 1 for each new virtual machine in AppCatalyst, so my next IP would have been 192.168.136.133.

So finally, I launched the vagrant box with:

LATTICE_SYSTEM_IP=192.168.136.133 vagrant up --provider=vmware_appcatalyst

vagrant up

Once that was up, run the ltc target:

jrickard-mbpro:lattice jrickard$ ltc target 192.168.136.133.xip.io
Api Location Set

Finally, I launched the sample lattice-app.

jrickard-mbpro:lattice jrickard$ ltc create lattice-app cloudfoundry/lattice-app
No port specified, image metadata did not contain exposed ports. Defaulting to 8080.
No working directory specified, using working directory from the image metadata...
Monitoring the app on port 8080...
No start command specified, using start command from the image metadata...
Start command is:
/lattice-app
Creating App: lattice-app...................
06/22 19:54:01.92 [APP|0] Successfully created container
06/22 19:54:02.22 [APP|0] {"timestamp":"1435024442.223613262","source":"lattice-app","message":"lattice-app.lattice-app.starting","log_leve
l":1,"data":{"port":"8080"}}
06/22 19:54:02.22 [APP|0] {"timestamp":"1435024442.223858833","source":"lattice-app","message":"lattice-app.lattice-app.up","log_level":1,"data":{"port":"8080"}}
06/22 19:54:02.75 [HEALTH|0] healthcheck passed
06/22 19:54:02.75 [HEALTH|0] Exit status 0
lattice-app is now running.
App is reachable at:
http://lattice-app.192.168.136.133.xip.io

targeted

Now, let's fire up a browser and hit http://lattice-app.192.168.136.133.xip.io

we have app

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment