does anyone has any experience/idea about installing WSO2 Private PaaS 4.0.0 on HP Helion public cloud.
I followed the instructions of the "Automated Product Configuration" in the WSO2 webpage, and
everything seems fine, I came to the last step "sudo ./boot.sh"
the display prompts the following:
WSO2 Private PaaS product configuration completed.
Do you need to setup WSO2 BAM (Business Activity Monitor) as a core service? [y/n] y
Do you need to start WSO2 Private PaaS? [y/n] y
Starting BAM core service...
nohup: ignoring input and redirecting stderr to stdout
Starting Gitblit core service...
nohup: ignoring input and redirecting stderr to stdout
Starting WSO2 Private PaaS server as root user...
the process hangs here.
I tried several times, and with the same results
By the way I have selected Openstack as the IaaS opotions (see below screen catch)
Enter your IaaS. vCloud, EC2 and OpenStack are the currently supported IaaSs. Enter "vcloud" for vCloud, "ec2" for EC2 and "os" for OpenStack: os
You selected OpenStack.
Enter OpenStack identity : 10976979403672:K7B6GX5A6AXJX7VXGFML
Enter OpenStack credentials :
Enter OpenStack jclouds_endpoint : https://region-a.geo-1.compute.hpcloudsvc.com/v2/10976979403672
Enter the region of the IaaS you want to spin up instances : US West
Enter OpenStack keypair name : paas-dev
Enter OpenStack security groups : paas-dev-sg
Enter OpenStack cartridge base image id : agent-base
thanks
WSO2 Private PaaS 4.0.0 only supports Amazon EC2, OpenStack and VCloud.
Private PaaS uses Apache jClouds to talks to the underlying IaaS. Therefore it is possible to extend it to support HP Helion since jClouds supports Helion according to [1]. But that is not yet implemented.
[1] https://jclouds.apache.org/reference/providers/
Related
I am a new starter for google cloud platform, I started a thing on marketplace which I think will help me install craft-cms, how to start? I mean where can I have the password of the root user on mysql, where is the password of phpadmin, I don't know where to start error I am facing
deployment
You have to finish the installation of MySQL after deploying the solution. You can't login to phpMyAdmin because you have not set up a password for root yet.
I assume you deployed the solution
MySQL Server + phpMyadmin on Ubuntu Server 20.04 and now you have a VM that you can SSH into.
SSH into the VM machine.
run the command sudo mysql_secure_installation to start the MySQL configuration.
Follow the onscreen prompts and reply 'y' to the prompts.
run the following commands to set up a password for root. Be sure to replace 'your_pass_here' with your own password.
sudo mysql
ALTER USER 'root'#'localhost' IDENTIFIED WITH mysql_native_password BY 'your_pass_here';
FLUSH PRIVILEGES;
Now you can log off your SSH session and login to phpMyAdmin using your new password.
If you deployed one of the marketplace solutions, you will have a deployment manifest in the Deployment Manager section of the Google cloud console.
Go to the Google Cloud Platform
https://console.cloud.google.com/
Ensure that you have the correct project selected (that will be the
one you deploy the marketplace solution in the first place) in the
dropdown menu in the top of the screen.
In the search bar type Deployment Manager and select "Google Cloud
Deployment Manager".
Press the button "Go To Cloud Deployment Manager"
You will find listed all the deployments for that project. You
should be able to find your deployment there.
Click on the deployment name and in the next screen you will be able
to find the deployment specifications, usually you will find the
names and passwords for the deployment there.
Here is an example of a deployment as seen in the Deployment Manager:
I receive an error message while attempting to deploy anything from the marketplace into a specific GCP project.
You must have a valid default service account in order to create a
deployment, but this account could not be detected. Contact support
for help restoring the account.
Things I've Tried:
Every VM from the marketplace shows the same error message
I can deploy regular VM instance
I can see there is an enabled service account for the project with the name "Compute Engine default service account".
I am able to deploy VM's from the marketplace into other projects under the same organization
I've contacted GCP Billing support and they cannot find anything wrong from a billing perspective
Researching online shows that others that have had this issue have just rebuilt the project. It appears that service account is created by default when the project is spun up.
I'm hoping there is another way around it as this project is a host for a shared VPC deployment. There are already other projects with deployed VM's that are utilizing the host projects networks.
Thank you!
Looks like you deleted a default service account.
As mentioned in one comment some can be recreated by disable/enable the corresponding API
Below are the default service accounts I have in my project, hope it helps you to find the root cause. (these service accounts let me deploy a wordpress solution depending on what you are trying to deploy you might need more service accounts)
PROJECT-NUMBER-compute#developer.gserviceaccount.com Compute Engine
default service account
PROJECT-NUMBER#cloudservices.gserviceaccount.com Google APIs Service
Agent
PROJECT-ID#appspot.gserviceaccount.com App Engine default service
account
service-ORG-ID3#gcp-sa-cloudasset.iam.gserviceaccount.com Cloud Asset
Service Agent
service-PROJECT-NUMBER#cloud-ml.google.com.iam.gserviceaccount.com Google
Cloud ML Engine Service Agent
service-PROJECT-NUMBER#compute-system.iam.gserviceaccount.com Compute
Engine Service Agent
service-PROJECT-NUMBER#container-engine-robot.iam.gserviceaccount.com Kubernetes
Engine Service Agent
service-PROJECT-NUMBER#containerregistry.iam.gserviceaccount.com Google
Container Registry Service Agent
service-PROJECT-NUMBER#dataflow-service-producer-prod.iam.gserviceaccount.com Cloud
Dataflow Service Account
service-PROJECT-NUMBER#service-networking.iam.gserviceaccount.com Service
Networking Service Agent
The service account was intact and had the same permissions as other service accounts for working projects.
We purchased and opened a case with GCP technical support. After a little more than a week of them troubleshooting the issues, they determined there was no way to correct the problem. Their root cause was that something happened during the initial project deployment that caused some backend configuration issues. For what its worth, the project was deployed using Terraform, but its uncertain if that was a factor.
After recreating the host project, we were able to deploy from the marketplace again successfully.
If you run into this problem, save yourself the hassle and time and just recreate the project.
I'm attempting to connect to a Google Cloud SQL instance via a MySQL client which requires me to connect via the Google Cloud proxy. I have followed all instructions on the Google Cloud Docs, yet after running the command to start the proxy (using correct INSTANCE_CONNECTION_NAME and PATH_TO_KEY_FILE), I receive the following error.
Command :
./cloud_sql_proxy -dir=/cloudsql -instances=INSTANCE_CONNECTION_NAME \ - credential_file=PATH_TO_KEY_FILE &
Error :
couldn't connect to "INSTANCE_CONNECTION_NAME": ensure that the account has access to "INSTANCE_CONNECTION_NAME" (and make sure there's no typo in that name). Error during createEphemeral for INSTANCE_CONNECTION_NAME: googleapi: Error 403: Access Not Configured. Cloud SQL Administration API has not been used in project 563584335869 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/sqladmin.googleapis.com/overview?project=563584335869 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry., accessNotConfigured
I have confirmed that the Google Cloud SQL API is enabled on the console for the project, but the weird thing is my project name is not 563584335869, and I have already set the correct project name via the GC CLI to no avail. So when visiting https://console.developers.google.com/apis/api/sqladmin.googleapis.com/overview?project=563584335869, I see:
The API "sqladmin.googleapis.com" doesn't exist or you don't have permission to access it
I also created a service account under the role Cloud SQL Client, and downloaded the private key which PATH_TO_KEY_FILE points to.
Can you confirm that you have enabled the "Cloud SQL API" (sqladmin.googleapis.com) and not "Cloud SQL" API? (sql-component.googleapis.com)?
Can you also give some more information as to your environment? Are you running this from your local machine or are you working in Cloud Shell?
I have clustered and deployment synchronize enabled 'wso2 esbs'(4.9).and i had enable secure vault. now all the deployments have been sync with all worker nodes.but how can i sync my secure vault credentials with worker nodes.
I tried copy "wso2carbon.jks" file,i tried copy "cypher-text.property" file,it doesn't worked.
so how can i sync my secure valet with other worker node?
Yes. If you have clustered the environment correctly it should automatically get synchronized. Steps to follow,
Add a secure vault entry to ESB manager node.
Check the secure vaults in ESB woker node. (If not running in the -Dworker mode.)
If the workers are running on -Dworker mode, you can also check the wso2carbon.log for the logs right after adding the entries to secure vault.
When you are deploying ESB cluster, you can use Puppet and Hiera to make the configurations changes.Wso2, already provided puppet modules to deploy wso2 product clusters.You can use existing Wso2 ESB puppet module to
achieve your requirement. Refer "Running WSO2 Enterprise Service Bus with Secure Vault" section of the README of the WSO2 Enterprise Service Bus Puppet Module to configure Secure Vault related configurations among the cluster.
I'm trying to get the introduction to spring cloud app working with an instance of Cloud Foundry that I'm running on my machine. I tried to push the app and I get this message:
Could not find service postgres-service to bind to hello-spring-cloud
So I started tracking down the postgres service. When I run cf marketplace, I get
service plans description
mongodb default MongoDB NoSQL database
postgresql default PostgreSQL database
rabbitmq default RabbitMQ message queue
redis default Redis key-value store
I try to create a service instance of the postgresql service and I get:
cf create-service postgresql default postgresql-service
Creating service instance postgresql-service in org xyz / space development as admin...
FAILED
Server error, status code: 500, error code: 10001, message: Service broker error: Not authorized
I have tried running cf create-service-auth-token postgresql core 123 but that didn't seem to help with the "Not Authorized" message.
I'm pretty new to Cloud Foundry so I'm a little lost. How do I get my the sample app to bind to the postgresql service?
update
Here are the permissions for the space:
Getting users in org xyz / space development as admin
SPACE MANAGER
admin
SPACE DEVELOPER
admin
** update 2: cf service-access **
$ cf service-access
Getting service access as admin...
Then shows nothing on the terminal. So I tried to enable service access...
$ cf enable-service-access postgresql
Enabling access to all plans of service postgresql for all orgs as admin...
All plans of the service are already accessible for all orgs
OK
But I still can't create the service.
Not sure if there was a resolution to that, but it looks like an issue with deployment of the service broker for PostgreSQL (auth creds for service broker).
It can be checked/updated via
cf service-brokers
cf update-service-broker ...
or via redeployment of the service (via tile in PCF/bosh or whatever way you use)