improved docker related things

[maldex]

Following up issue #18, this pr concerns a few docker-things:

• Dockerfile: moved add run.sh to bottom, don't redo the whole thing if only this script has changed.
• run.sh: added an argument parser for classic Unix-compatibily and not only relying on environment variables.
• run.sh: overwrite the nsx_image_webserver in the config.yml with altered concourse_url.
• run.sh: corrected fly initialization as described in #18 (login/sync sequence and adding --non-interactive)
• nsx-t-install-09122018.tar: removed, afaik can the releases​ feature of your RCS be used for this.
• all: some other little tweaks. Feel free to test and improve.

thx

[vmwclabot]

@maldex, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <john.doe@email.org> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit e17b6f6c15c6754232282b048300a94afba63007 must be signed by user@sisyphos

[vmwclabot]

@maldex, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <john.doe@email.org> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit e17b6f6c15c6754232282b048300a94afba63007 must be signed by user@sisyphos
• Commit ae7c618477820a99ea0183b0be0a31827c916646 must be signed by user@sisyphos

[maldex]

Sorry, i don't get how that's supposed to work.

[kais66]

Sorry, i don't get how that's supposed to work.

use '-s' when committing :)

[maldex]

Please dissect and reject this PR: it's merely how i quick-n-dirty got the nsx-t-pipeline up and displayable. It's notproduction safe but only addresses #18 and inherently a few things along. "Properly" addressing and implementing some of the discussed aspects would deserve another issue and pull-request afaik. Please invite me