-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Unable to define reusable custom types #4773
Comments
This issue hasn't been updated in 45 days, so we are tagging it as 'stale'. If you want to remove this label, comment:
|
@spinnakerbot remove-label stale |
This issue remains to be a problem. |
Please address this limitation. |
This issue hasn't been updated in 45 days, so we are tagging it as 'stale'. If you want to remove this label, comment:
|
@spinnakerbot remove-label stale |
This issue hasn't been updated in 45 days, so we are tagging it as 'stale'. If you want to remove this label, comment:
|
@spinnakerbot remove-label stale |
This issue hasn't been updated in 45 days, so we are tagging it as 'stale'. If you want to remove this label, comment:
|
@spinnakerbot<https://github.com/spinnakerbot> remove-label stale
Sent from my Verizon, Samsung Galaxy smartphone
…-------- Original message --------
From: spinnakerbot <[email protected]>
Date: 3/22/20 1:25 PM (GMT-05:00)
To: spinnaker/spinnaker <[email protected]>
Cc: "Kaufman, Lawrence" <[email protected]>, Manual <[email protected]>
Subject: Re: [spinnaker/spinnaker] Unable to define reusable custom types (#4773)
External Email – Please use caution before opening attachments or clicking links
This issue hasn't been updated in 45 days, so we are tagging it as 'stale'. If you want to remove this label, comment:
@spinnakerbot<https://github.com/spinnakerbot> remove-label stale
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#4773 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEEJP4FE55GVDLCKUWDBFTDRIZCZPANCNFSM4INX7LNQ>.
_________________________________________________
This message is for the designated recipient only and may contain privileged, proprietary
or otherwise private information. If you have received it in error, please notify the sender
immediately and delete the original. Any other use of the email by you is prohibited.
Dansk - Deutsch - Espanol - Francais - Italiano - Japanese - Nederlands - Norsk - Portuguese - Chinese
Svenska: http://www.cardinalhealth.com/en/support/terms-and-conditions-english.html
|
@spinnakerbot remove-label stale |
@spinnakerbot remove-label stale |
"stale" has not been applied, and cannot be removed. |
@spinnakerbot remove-label stale |
"stale" has not been applied, and cannot be removed. |
We still need this. Do you have any update? |
Still needed. |
This issue hasn't been updated in 45 days, so we are tagging it as 'stale'. If you want to remove this label, comment:
|
This issue hasn't been updated in 45 days, so we are tagging it as 'stale'. If you want to remove this label, comment:
|
This issue is tagged as 'stale' and hasn't been updated in 45 days, so we are tagging it as 'to-be-closed'. It will be closed in 45 days unless updates are made. If you want to remove this label, comment:
|
Looks like this is handled a little differently for E2 instances, which don't allow >16GB. Does this handle that case? Perhaps Spinnaker shouldn't try to replicate the GCE Console's business logic, instead it should just let users put in whatever they want and rely on the GCE APIs to accept or reject it? |
@spinnakerbot remove-label to-be-closed |
@spinnakerbot remove-label stale |
The interface @siddhu-opsmx presented would work for me, but @plumpy has a valid concern about the complexity of reproducing the GCP business logic. It looks like E2 doesn't have the extended memory "feature." |
I'm a spinnaker novice. So as long as it is easy to see the GCP error message(s) when an invalid combination is selected, letting the users enter what they want it fine by me. |
Sure, that works. |
I have documented the use case for such a scenario, it would be really helpful if you could provide some feedback on it. |
@plumpy @cah-lawrence-kaufman it would be really helpful if you could provide some feedback on above "use case doc". So based on feedback I will raised PR for the same. |
So if you check the box, the "Memory (Gb)" field changes from a drop-down to a text entry box? I guess that works for me. Thanks. |
@siddhu-opsmx I've looked at the "use case doc." I'm not expert in GCP. But with extended memory, I believe that there is a requirement that -ext should be appened to the custom machine type. So if the extended memory check box is checked, the -ext should be appended as well. Sorry for the delayed response, I was on vacation, just back today. |
This issue hasn't been updated in 45 days, so we are tagging it as 'stale'. If you want to remove this label, comment:
|
This issue is tagged as 'stale' and hasn't been updated in 45 days, so we are tagging it as 'to-be-closed'. It will be closed in 45 days unless updates are made. If you want to remove this label, comment:
|
This issue is tagged as 'to-be-closed' and hasn't been updated in 45 days, so we are closing it. You can always reopen this issue if needed. |
Issue Summary:
Unable to define reusable custom types or define servers with more than 6.5 GB of memory per core.
Cloud Provider(s):
GCE
Environment:
Spinnaker running in GKE built through Halyard.
Feature Area (if this issue is UI/UX related, please tag
@spinnaker/ui-ux-team
):@spinnaker/ui-ux-team, GCE, clouddriver
Description:
Spinnaker provides the option to use custom types; however, there is no way to add a custom type. This prevents us from using instances that use extended memory.
Since GCE allows for the use of custom types, Spinnaker should reflect this.
You can specify the CPU and memory explicitly. However this is coded to limit it to 6.5GB of Memory per code. At this time, this is an arbitrary limit, as GCE doesn't have the same issue.
This can be seen by midifiying the JSON to use something more that 6.5GB and trying to deploy (screenshot below)
Steps to Reproduce:
Try to create a server with 4 CPU ad more than 26GB of Memory
Additional Details:
The text was updated successfully, but these errors were encountered: