Skip to content

Resolve the issue of running provision again#1

Open
knight-corvi wants to merge 7 commits intoUCMAndesLab:masterfrom
knight-corvi:master
Open

Resolve the issue of running provision again#1
knight-corvi wants to merge 7 commits intoUCMAndesLab:masterfrom
knight-corvi:master

Conversation

@knight-corvi
Copy link

In my effort to figure out the the issue about having to run provision twice, I made modifications in terms of the structure of the content of the files, mostly spacing between characters and moving inline scripts to variables or files

…s hostname to _tinyOS_

+ Adds puppet repository using the DEB package.
+ Fixes the issue of not having puppet v4 in the ubuntu repositories which is
required by the _apt_ module in puppet if installing from the plugin install
utility.
It resolves the issue of running provision after a setup. The problem was caused
when installing java.
See: https://askubuntu.com/questions/769467/can-not-install-openjdk-9-jdk-because-it-tries-to-overwrite-file-aready-includ
Adds full fingerprint for _tinyprod_ source and as such it removes the warning
about having a short ID.
Puts the correct location of _profile_ in _source_
@alexbeltran
Copy link
Contributor

Could you please add some more descriptions of what exactly you are doing to your pull request. From what I see you did the following:

  1. Clean the structure of the vagrant file.
  2. Made vagrant install puppet during initialization
  3. Moved the .profile file to its own dedicated file and copied it over.
  4. Mount a local directory as a shared directory.
  5. Include the ubuntu patch in the repository.

Vagrant up is not working at the moment since it assumes that a user already has a cse160-networks directory. This vagrant file is designed to be used outside of the class also, but I wouldn't mind having a shared directory. If possible include a way to create this directory without having the user create the directory separately.

vm:
* The host path of the shared folder is missing: cse160-networks

Besides that, everything seems to work great. Thanks for your contribution. I'll accept once the shared folder stuff is resolved.

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.

2 participants