Does anyone know what should I do to allow a turbine server to discover hystrix streams from services located in different openshift projects?
I'm using kubeflix 1.0.28 with openshift 3.11 and tried adding view and cluster-reader roles to turbine service account but turbine server cannot discover streams from other projects but only the same one where it's deployed.
These are the commands executed from the project where turbine server is located
oc policy add-role-to-user view system:serviceaccount:myproject:turbine -n otherproject
oc adm policy add-cluster-role-to-user cluster-reader system:serviceaccount:myproject:turbine
Have any clue?
Related
Who has installed Openshift4 on Virtualbox VMs? How to bypass BMC limitations (BMC is required in install-config.yaml)?
https://docs.openshift.com/container-platform/4.6/installing/installing_bare_metal_ipi/ipi-install-installation-workflow.html#configuring-the-install-config-file_ipi-install-configuration-files
The prerequisites for an OCP 4.6 IPI (Installer Provisioned Infrastructure) install requires BMC access to each node.
With this setup a UPI (User Provisioned Infrastucture) deployment would be a better fit. You would need to set up the VMs and DNS entries before starting the deployment, as described in https://docs.openshift.com/container-platform/4.6/installing/installing_bare_metal/installing-bare-metal.html#installation-requirements-user-infra_installing-bare-metal.
I have openshift 3.9 installed in one AWS region ohio. I have jenkins installed in it. I have a pipeline code in where it will take Java code from GitHub bind with jboss and deployed it in project test within the same cluster. It works fine and I'm able to access the app as pod is creating and app is also binding with jboss. Now I want to deploy this application across different clusters either within the same region or across different regions. Is there a way to achieve this?
You can use the oc command line tool in your Jenkins pipeline to deploy it to a different cluster. For a related example, check the Gitlab review apps example using an OpenShift cluster. It does something similar, where the CI pipeline deploys the required artifacts to an OpenShift cluster using oc and appropriate credentials.
I am trying to log in to the Bluemix Container Service with cmd.exe. I installed the latest Bluemix CLI and IBM Bluemix Container Service plug-in, and tried to login using the following command:
C:\>bx login -a api.ng.bluemix.net
...
OK
...
C:\>bx cs init --host https://us-south.containers.bluemix.net
The IBM Bluemix Container Service Kubernetes beta in the US South region (Dallas) has concluded. You can access your bet
a clusters via the CLI using (bx cs init --host https://us-south-beta.containers.bluemix.net). See https://ibm.biz/cont
ainer-migration for beta migration information.
Using user provided API endpoint: https://us-south-beta.containers.bluemix.net
OK
C:\>bx cs clusters
The IBM Bluemix Container Service Kubernetes beta in the US South region (Dallas) has concluded. You can access your bet
a clusters via the CLI using (bx cs init --host https://us-south-beta.containers.bluemix.net). See https://ibm.biz/cont
ainer-migration for beta migration information.
FAILED
The client is not yet configured. Run `bx login`.
The Bluemix login was successful, but an error occurred. I tried it with bash on Windows, but the results were the same.
I would recommend to install Cloud Foundry CLI instead of Bluemix CLI and work hope your problem gets resolved.
I'm trying to install Cloudera Manager in a Google Compute Engine Ubuntu 12-04 instance. Everything works fine until the installation step.
The error occur when tries to detect the Cloudera Manager Server. It seems an error with the hostname... the report error is the next one:
could not contact scm server at 236.193.155.104.bc.googleusercontent.com:7182, giving up
waiting for rollback request
Screenshot:
Please someone help me with this! I'm working on it for too long time and I feel that it is not complicated to resolve..
Many thanks in advance!
Add the firewall exception for your instances to allow tcp connections on port 7182 through them.The following is the command that allows all the tcp connections.
gcloud compute firewall-rules create cloudera-manager --allow tcp
Reference: Hadoop on GCE http://github.com/scalding-io/hadoop-on-gce/blob/master/build-cluster
To help with deploying Cloudera Manager, I wrote these scripts which may be of use to you, as they simplify the installation and deployment of Cloudera Manager on Google Compute Engine.
Also, you can now use Cloudera Director to deploy and provision Hadoop clusters on Google Cloud Platform. Cloudera Director is a single server binary which can deploy and manage other VMs to install Cloudera Manager as well as the rest of the Cloudera Hadoop distribution automatically with an easy-to-use GUI.
I try to use the IBM Websphere $AdminApp (and the Ant tasks) to install/update an application EAR on a remote server. You may want to read this question too.
Manual process
I open a jython console with this command line:
$was61profile1\bin$> wsadmin.bat -lang jython -host MYHOST -port 32092
After that I want to list all applications:
wsadmin>AdminApp.list()
WASX7015E: Exception running command: "$AdminApp list"; exception information:
com.ibm.ws.scripting.ScriptingException: WASX7206W: The application management service is not running. Application management commands will not run.
I think the message here is clear: The application management service is not running.
How to enable the Application Management Service?
I did search for documentation on the horrible, horrible IBM website. I also tried to click through the configuration options on the Websphere admin pages. But I can't find anything remotely close to application management service. I do that clicking again with english language settings now, but I'd appreciate if someone can point me to the configuration option or the documentation.
Crap, I was connected to the wrong port. If you want to use AdminApp.list() you have to connect to the deployment manager (abbreviated as DMGR). I restarted my console with
*WAS_HOME*\profiles\was61profile1\bin>wsadmin.bat -lang jython -host MYHOST -port 32003
and then I could list installed applications via AdminApp.
Make sure you go to the Websphere Administration console web interface and go to System configuration -> Deployment manager and check the list of Ports on the right hand side of the page. There is a port for SOAP_CONNECTOR_ADDRESS and that is what you need to use for the console.