I am in the process of setting up structures for a development process with IBM Cloud Code Engine. The documentation says "service instance" in the privilege matrix, but I wonder if Code Engine projects are meant. I want to only grant few developers the ability to create new projects.
Would I grant Platform Editor to create a Code Engine project?
The Editor role would be the appropriate role to assign. In other Code Engine documentation, on how to retrieve the ID of the Code Engine service instance, it is noted that:
Identify the service instance that represents your Code Engine project and determine the GUID from the output.
Thus, the concept of IBM Cloud service instance maps to a Code Engine project.
Related
I am attempting to create Cloud Object Storage to work in conjunction with a Watson Studio service instance. However, when I attempt to create it, the following error message is displayed:
“Reseller channel 2c95500b-ea86-4b13-8bb5-b2f0c2fa8200 is invalid.”
How can I create the storage that I need?
When you attempt to create the cloud object storage instance through the Watson Studio service, a link sends you to a storage provisioning page. However, you are unable to provision the storage instance. As a workaround, you can create the Cloud Object Storage service manually through the IBM Cloud Catalog at the following URL: https://cloud.ibm.com/catalog/services/cloud-object-storage
I had this issue as well. Turns out when you create the new account it will ask you for a location for services and by default it's set to "Dallas". However changing that to London/Tokyo fixed this issue for me. I needed it for IBM Course on Coursera. I would recommend making a new account with services location set to London / Tokyo. It'll instantly fix this problem.
I managed to solve this by first creating the object storage before creating the Watson Studio service.
After you have created a cloud object storage service with the direct link to the service
While creating a new project On Watson Studio, you will see an option to Add a cloud Object Storage service under Define storage to your project in the project creation page. Once you click Add, you can either use an existing Service as you have now or create a new COS service.
For more details instructions check this section of the solution tutorial
[there is some internal server error while creating database instance in cloud][1]
[1]:[ https://i.stack.imgur.com/I5tty.png]
Raise a support ticket with IBM.
Operational issues on commercial cloud services are not for stackoverflow.
Additionally, if you are on the "lite" plan (as suggested by your image), there is no ability to create a Database instance. Instead, you can only connect to a shared multi-tenanted database with your your account. It has a schema which is your account-name.
I'm getting "internal error occurred while creating a Google Cloud Storage bucket" errors when I try to publish an App Engine App from Visual Studio 19. (It also fails with the exact same error when trying to publish from shell).
From what I can find here and elsewhere, theres a "quick fix" to this, using
gcloud config set app/use_deprecated_preparation True
but that returns
Section [app] has no property [use_deprecated_preparation]
I'm pretty confident this has to do with role settings.
I've set permissions in IAM; App Engine default service account has the roles Editor, Service Account Token Creator and Storage Object Creator. I personally have the role of Owner.
Can someone point me in the direction of what I'm missing in roles?
I am using Public Bluemix. I have provisioned a dashDB service instance using my IBM ID in Bluemix. I have also provisioned a Object Storage service. I would like to load files from Object Storage into dashDB.
When I try to define a load job in dashDB to get a file from Object Storage, I face a problem.
dashDB allows me to choose either Amazon S3 or Swift Object Store as the data source. I chose "Swift" and then provided the following Bluemix Object Store service credentials.
Public authentication endpoint : https://identity.open.softlayer.com
User name: as found in my my Bluemix Object Store credentials 'username'
API access key: as found in my my Bluemix Object Store credentials 'password'
Then, I clicked "Browse swift files", expecting to see the files which exist in my Bluemix Object Store's container. But, it shows me just a blank folder and no files.
I need to understand the method to connect Bluemix dashDB to Bluemix Object Store. Please help.
I'm having trouble getting this to work too.
At first, I found an answer on dWAnswers that said this may not be supported.
https://developer.ibm.com/answers/questions/166630/dataworks-integration-between-object-storage-and-d.html
Edit:
The Bluemix support team got back to me with the following message:
For loading from Swift, Bluemix Object Storage is not supported
and only object storage on SoftLayer is supported at this time.
Thanks.
I'm trying to use Cloud SQL from my VM instance.
When creating the VM Instance I activated Cloud SQL Option for it.
The Cloud SQL instance authorizes my Compute Engine Project to access it.
At first I was expecting to have some tools like google_sql.sh installed on my VM since I had activated Cloud SQL on it but no :-/
In Cloud SQL docs it says that I should copy my local access token to my VM Instance.
My local machine is Mac OSX so the tokens are stored in :
~user/Library/Preferences/com.google.cloud.plist
but on my Linux VM it's stored in:
~user/.java/.userPrefs/com/google/cloud/sqlservice/oauth2/prefs.xml.
Do I have to create a prefs.xml and copy it on my VM? (but I guess the XML schema is not the same between com.google.cloud.plist and prefs.xml?)
Does someone have perfs.xml example I could use as a template (unless schema is exactly the same as com.google.cloud.plist which I doubt)?
Thanks all for your help.
The simplest thing is actually to include service account scopes when you create your instance. This page in the compute engine docs describes how to do it. This maintains an access token in the compute engine instance's metadata server which the Cloud SQL tools can then access when they need to authenticate. A similar technique works for cloud storage and other products.