Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install getting started #983

Merged
merged 5 commits into from
Mar 24, 2020
Merged

Install getting started #983

merged 5 commits into from
Mar 24, 2020

Conversation

achamayou
Copy link
Member

fix #969

@achamayou achamayou requested a review from a team as a code owner March 24, 2020 11:44
@jumaffre
Copy link
Contributor

As I understand it, the expected workflow is:

  1. Download the CCF install on your local machine (e.g. laptop). Untar.
  2. Install Azure CLI.
  3. Run the scripts in getting_started/create_vm to create a new DC VM.
  4. SSH onto the VM and download the CCF install again. Untar.
  5. Run the ansible scripts in getting_started/setup_vm
    (Alternative to 5. is to run the ansible playbooks directly from the machine on which 1. was run, provided that ansible is installed there).
  6. Build you app.

All files apart from getting_started/create_vm in the first install are not actually required but I guess it's the best way to distribute this script. An alternative would be to package getting_started/create_vm and export it as a release artifact. What do you think?

@achamayou
Copy link
Member Author

  1. is done by ./pre_make_vm.sh, so it's sort part of 3.?
  2. well yeah...

I think I prefer to keep things simple for now with a single SDK tarball that has All You Need (tm), but arguably the create_vm stuff could migrate elsewhere, since it's not actually CCF-specific (oe_engine? openenclave-azure-get-started?) and we could just reference it.

I suspect this is a post-0.9 thing though.

@achamayou
Copy link
Member Author

CI breaks for unrelated reasons (quote verification issue in ACC)

@achamayou achamayou merged commit 07f5404 into microsoft:master Mar 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Install directory and release should contain getting_started directory
4 participants