jbayer

nslookup your-cluster-name-here.vault.your-project-id-here.aws.hashicorp.cloud
Server:		192.168.86.1
Address:	192.168.86.1#53

Non-authoritative answer:
Name:	your-cluster-name-here.vault.your-project-id-here.aws.hashicorp.cloud
Address: 34.215.184.84
Name:	your-cluster-name-here.vault.your-project-id-here.aws.hashicorp.cloud
Address: 54.185.0.185
Name:	your-cluster-name-here.vault.your-project-id-here.aws.hashicorp.cloud

jbayer

Keybase proof

I hereby claim:

• I am jbayer on github.
• I am jambay (https://keybase.io/jambay) on keybase.
• I have a public key ASBNEqvKihkY657SPA0MAd-d9y6lUrXSkVw-i8_Zv2iAIQo

To claim this, I am signing this object:

jbayer

---
apiVersion: v1
kind: Service
metadata:
  name: waypoint
  namespace: default
  
spec:
  ports:
  - port: 9701

jbayer

$ cf push -m 64M
FAILED
Manifest file is not found in the current directory, please provide either an app name or manifest

NAME:
   push - Push a new app or sync changes to an existing app

USAGE:
   Push a single app (with or without a manifest):
   cf push APP_NAME [-b BUILDPACK_NAME] [-c COMMAND] [-d DOMAIN] [-f MANIFEST_PATH] [--docker-image DOCKER_IMAGE]

jbayer

$ cf push ubuntu -o library/ubuntu -u none -c "nc -l 8080"
Creating app ubuntu in org local.micropcf.io-org / space dev as admin...
OK

Creating route ubuntu.local.micropcf.io...
OK

Binding ubuntu.local.micropcf.io to ubuntu...
OK

jbayer

#!/bin/bash

export PIVNET_TOKEN=PASTE_THIS_FROM_PIVNET_USER_PROFILE
export LOCAL_FILE_NAME=stack_announcement.pdf
export DOWNLOAD_URL=https://network.pivotal.io/api/v2/products/pivotal-cf/releases/267/product_files/1804/download

wget -O "$LOCAL_FILE_NAME" --post-data="" --header="Authorization: Token $PIVNET_TOKEN" $DOWNLOAD_URL

jbayer

pintail:lattice jamesbayer$ 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
...11 Apr 08:15 [APP|0] Successfully created container
11 Apr 08:15 [APP|0] {"timestamp":"1428765351.428330660","source":"lattice-app","message":"lattice-app.lattice-app.starting","log_level":1,"data":{"port":"8080"}}

jbayer

doug,

thanks for writing up your experiences!

it's not too difficult to install it on a VM without vagrant. someone has already done it with heat for example: https://github.com/LaynePeng/heat-lattice

if you look at the Vagrantfile, you can see the provisioning steps are fairly simple:
https://github.com/cloudfoundry-incubator/lattice/blob/master/Vagrantfile#L10-L40

"ltc create" currently creates a diego lrp, so if you want to create an ubuntu image, this works:

jbayer

Error applying plan:

1 error(s) occurred:

* Network vpc-8ced8ee9 has some mapped public address(es). Please unmap those public address(es) before detaching the gateway. (DependencyViolation)

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

jbayer

GCLOUD (1)                                                                                                                                                                                                    GCLOUD (1)

NAME
       gcloud - manage Google Cloud Platform resources and developer workflow

SYNOPSIS
       gcloud GROUP |  COMMAND [--format FORMAT] [--help] [--project PROJECT_ID] [--quiet, -q] [--user-output-enabled USER_OUTPUT_ENABLED] [--verbosity VERBOSITY] [-h]

DESCRIPTION
       The gcloud CLI manages authentication, local configuration, developer workflow, and interactions with the Google Cloud Platform APIs.