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

enh 434: instance template should support multiple NICs #31

Conversation

alexkonkin
Copy link
Contributor

No description provided.

@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.


What to do if you already signed the CLA

Individual signers
Corporate signers

ℹ️ Googlers: Go here for more info.

@alexkonkin
Copy link
Contributor Author

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

What to do if you already signed the CLA

Individual signers
* It's possible we don't have your GitHub username or you're using a different email address on your commit. Check [your existing CLA data](https://cla.developers.google.com/clas) and verify that your [email is set on your git commits](https://help.github.com/articles/setting-your-email-in-git/).
Corporate signers
* Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to [go/cla#troubleshoot](http://go/cla#troubleshoot) ([Public version](https://opensource.google.com/docs/cla/#troubleshoot)).

* The email used to register you as an authorized contributor must be the email used for the Git commit. Check [your existing CLA data](https://cla.developers.google.com/clas) and verify that your [email is set on your git commits](https://help.github.com/articles/setting-your-email-in-git/).

* The email used to register you as an authorized contributor must also be [attached to your GitHub account](https://github.com/settings/emails).

ℹ️ Googlers: Go here for more info.

I signed it!

@googlebot
Copy link

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@alexkonkin alexkonkin force-pushed the feature/434_instance_template_multi_NIC_support branch from 7eb9f04 to 5f1b4e9 Compare May 17, 2019 14:47
@ocsig ocsig self-assigned this May 19, 2019
@ocsig ocsig added DM Deployment Manager CFT cla: yes labels May 19, 2019
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

@@ -25,53 +25,61 @@ required:
- zone
- machineType
- diskImage
- network
Copy link
Member

Choose a reason for hiding this comment

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

Please update your implementation in a way that both 'network' (as the current implementation) as 'networks' (the new implementation) is supported to assure backwards compatibility.

@@ -20,7 +20,7 @@ info:

required:
- diskImage
- network
Copy link
Member

Choose a reason for hiding this comment

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

Please update your implementation in a way that both 'network' (as the current implementation) as 'networks' (the new implementation) is supported to assure backwards compatibility.

@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

ℹ️ Googlers: Go here for more info.

@ocsig ocsig added cla: yes and removed cla: no labels May 20, 2019
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

@alexkonkin alexkonkin force-pushed the feature/434_instance_template_multi_NIC_support branch from d5282d7 to 7333011 Compare May 20, 2019 14:11
@googlebot
Copy link

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

ℹ️ Googlers: Go here for more info.

@@ -17,9 +17,20 @@ resources:
machineType: f1-micro
diskType: pd-ssd
canIpForward: true
network: test-network-${RAND}
subnetwork: regions/us-central1/subnetworks/test-subnet-${RAND}
networks:
Copy link
Contributor

Choose a reason for hiding this comment

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

why we don't use "network" in this case?

Copy link
Contributor Author

@alexkonkin alexkonkin May 20, 2019

Choose a reason for hiding this comment

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

Andriy, this test is dedicated to the networks property.
We have a separate test that should also check the network property.

@ocsig ocsig added cla: yes and removed cla: no labels May 20, 2019
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

@morgante morgante requested a review from ocsig May 21, 2019 01:03
@ocsig
Copy link
Member

ocsig commented May 21, 2019

Please update the Managed Instance Group Schema to support the multi NIC Instance templates

@ocsig ocsig merged commit fc452a8 into GoogleCloudPlatform:master May 22, 2019
bohdanyurov-gl added a commit to bohdanyurov-gl/cloud-foundation-toolkit that referenced this pull request May 23, 2019
ocsig pushed a commit that referenced this pull request May 24, 2019
…ates, MIGs with backwards compatibility

* Fixes instance & instance template errors introduces in this PR:
#42

Issue:
GoogleCloudPlatform/deploymentmanager-samples#434

* Additional fix

* Reverted fix

* Follow-up for
#31

Fixes DM#434 for managed_instance_group
GoogleCloudPlatform/deploymentmanager-samples#434
@ocsig ocsig mentioned this pull request May 24, 2019
SnowmanSeniorDev added a commit to SnowmanSeniorDev/cloud-foundation-toolkit that referenced this pull request Apr 17, 2023
…ates, MIGs with backwards compatibility

* Fixes instance & instance template errors introduces in this PR:
GoogleCloudPlatform/cloud-foundation-toolkit#42

Issue:
GoogleCloudPlatform/deploymentmanager-samples#434

* Additional fix

* Reverted fix

* Follow-up for
GoogleCloudPlatform/cloud-foundation-toolkit#31

Fixes DM#434 for managed_instance_group
GoogleCloudPlatform/deploymentmanager-samples#434
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes DM Deployment Manager CFT
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants