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

Adds basic name convention support [full ci] #6265

Closed
wants to merge 11 commits into from

Conversation

hickeng
Copy link
Member

@hickeng hickeng commented Sep 10, 2017

Adds redo logic for concurrent modifications to the rename path
Adds very basic naming convention mechanism

Does not add tests or reconfigure support for the new option.

Updates needed in priority order:

  • only apply to the vsphere displayName, not the container name
  • provide {id} (shortID) as a token as well as {name} - name could be omitted in initial support
  • support reconfigure of convention
  • convention should persist over docker renames
  • reserve name on the create path

End goal is:
vSphere display name like cVM_prod-short_id, from a convention template of cVM_prod-{id}
container name as normal, like random_name
docker rename does not impact vsphere display name unless {name} is used in convention

mhagen-vmware and others added 9 commits August 28, 2017 11:05
…6159)

This change borrows the specific ci logic to run only
Group11-Upgrade and 7-01-Regression tests on a tag build (tag
event on a *refs/tags* branch).
…rt (vmware#6160) (vmware#6194)

Adding gateway address for bridge networks on VCH restart
We were not reinitializing session status on out-of-band power
operations, meaning we hit a filter in the launch logic that skipped
launching the container process.

Additional tests to follow
Cherry pick of vmware/govmomi#829

master branch has this change via the full govmomi update in vmware#6144

Fixes vmware#6152
It was possible for the Stop() method close the RPC channels when
the main loop was in the middle of Send/Receive.
@hickeng hickeng force-pushed the rename-alternatives branch from 8946236 to 61fec99 Compare September 11, 2017 14:22
Provides basic container naming convention via {id} and {name} tokens.
The naming is enforced only on vSphere and will not be visible via
the docker client.
Copy link
Contributor

@mhagen-vmware mhagen-vmware left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this PR currently has a bunch of bad merges it looks like

@@ -113,6 +114,7 @@ Upgrade VCH with Harbor On HTTP
Test VCH And Registry %{VCH-IP}:%{VCH-PORT} ${harbor_ip}

Upgrade VCH with Harbor On HTTPS
Pass Execution Need to use a different insecure registry, because Harbor does not support VIC as insecure and 0.5.0 is too old
${out}= Cleanup Harbor ${http_harbor_name}
Log ${out}
${out}= Cleanup Harbor ${https_harbor_name}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bed merge? This is in master already..

@mhagen-vmware
Copy link
Contributor

I think this can just be closed in favor of #6284

@chengwang86
Copy link
Contributor

@hickeng @cgtexmex Is this still needed? A big chunk of duplicates with #6284

@mhagen-vmware
Copy link
Contributor

closing in favor of #6284 as per email from @hickeng

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

Successfully merging this pull request may close these issues.

6 participants