I'm unable to migrate an application from OpenShift2 to OpenShift3.
I've an instance of Fuseki installed on Openshift2. It is viewed as being on a 'redHat type' account.
It uses a cartridge of type "Do-It-Yourself 0.1"
I'm able to copy the content in a local git by using ssh link at the right of my config page.
Then, I created a new account in Openshift3 and I don't see any documentation or tool useful to install my application on OpenShift3.
The migration must be done before the end of the month and I'm stuck at that point.
Any help?
Related
I am unable to create project in open shift. I created a project previously and deleted it. Looks like a project exists but unable to access or delete it. Seems like i am stuck. Also logging into the console https://console.preview.openshift.com/console/ doesn't show any existing projects.
I ran the following oc commands from the terminal.
Any suggestions on how to resolve this issue?
Thanks
XX:~ XX$ oc new-project test
Error from server: projectrequests "test" is forbidden: user XX cannot create more than 1 project(s).
XX:~ XX$ oc delete project test
Error from server: User "XX" cannot delete projects in project "test"
XX:~ XX$ oc status
Error from server: User "XX" cannot get projects in project "default"
XX:~ XX$ oc get projects
You need to give privileges/policies to your user which will allow the actions you want to perform.
If you are just in a proof-of-concept environment I would recommend the make your user cluster-admin in the whole cluster. This will give all the possible privileges to your user. Of course this in't recommended for every user in a 'real' environment.
First you need to authenticate with the 'default admin' which is created after the installation. This default admin-user isn't working with the normal user/password authentication. It's using a client certificate.
oc login -u system:admin --config=/etc/origin/master/admin.kubeconfig
Now you will see a list of the available projects (default, openshift management, etc). Now you're able to give cluster-roles to other users.
Make your user cluster-admin over the whole cluster
oadm policy add-cluster-role-to-user cluster-admin (youruser)
Now you have the cluster-admin privileges inside the whole cluster. You are also able to give privileges for some user in a specific project and not in the whole cluster. Than you have to use:
oadm policy add-role-to-user <role> <username> (in the current project)
This will give the role to a user, but only inside the project from where you've performed this command.
For more information about the avaiable cluster roles and policies I will point to the official documentation.
I raised a defect with Openshift Team as pointed out in the Support Link.
https://docs.openshift.com/online/getting_started/devpreview_faq.html#devpreview-faq-support
Here is the response i received from Support Team.
It seems that you have issued a bug and followed up for this already:
https://bugzilla.redhat.com/show_bug.cgi?id=1368862
After the cause is investigated, our operations team will sure clean up the project manually for you to allow you continue working with the developer preview
Latest update:
The project has now been cleaned up and you should be able to create a new project.
I am able to create Project in Openshift now.
I am trying to install and setup MobileFirst. SO i was able to install WAS ND, create a server, Install Mobilefirst Server, Install database, Create database and now i am trying to create a runtime with the configuration tool.
Below is the Database screenshot which proves that the database exist
This is a screenshot of the creating admin configuration and also it show that the port number is ok
This is a screen shot of the database additional extra setting which is checking for the database WLADM70 which i have given, validation happened without problem but its always in the checking for the database state.
I am following the APIC tutorial documented here:
Publishing a project from the command line
I have gone through the steps in the tutorial to get into the APIConnect dashboard in Bluemix and into the Sandbox catalog.
I get the baseURL under api management:
e.g. https://api.us.apiconnect.ibmcloud.com/FREDusibmcom-dev/sb
Then I use that to
apic config:set
catalog=apic-catalog://api.us.apiconnect.ibmcloud.com/orgs/FREDusibmcom-dev/catalogs/sb
app=apic-app://api.us.apiconnect.ibmcloud.com/orgs/FREDusibmcom-dev/apps/acme-bank-Fred
After this as per the instructions, I try to login using my Bluemix credentials
apic login --server api.us.apiconnect.ibmcloud.com -u fred -p mypassword
This fails with:
ERROR Login to api.us.apiconnect.ibmcloud.com failed, please verify the servername and credential
Am I doing something wrong in regards to the servername or credentials that I am using? Thanks!
For your server argument in the login command, use us.apiconnect.ibmcloud.com instead. I think the api portion is throwing things off.
Once successful there, I also recommend that you run apic edit and proceed to Log in with Bluemix there, as that will ensure that you're able to publish applications to Bluemix from the CLI or API Designer.
I assume you used your actual username/password, and not "fred/mypassword".
If so, then the problem may be with the Bluemix URL. There's now a simpler way to get the app identifier and catalog identifier (and to make sure you have the right Bluemix base URL). The catalog & app tiles now have a link icon that you can click to easiy copy the catalog/app identifers:
Geting the catalog identifier
The Bluemix base URL will the part immediately following apic-catalog:// in the catalog identifier.
We're in the process of updating the docs with this.
I set up a Neo4j database on Azure following this guide. The set-up process went fine. The issue I'm having is that the database is not asking for a username or password when I access it though the public port. In other words, anyone can access and edit the database by simply navigating to the URL. Can anyone point me in the right direction as to how to set up authentication?
First: That's a fairly old walkthrough, with the v1.8 version of Neo4j running on the preview of Virtual Machines. And that image had a pre-set username and password. Look closely at the login box:
"The server says neo4j graphdb"
Those two will be your username and password.
Note: This is not the case if you use the latest 2.0x image in VM Depot.
I was able to get this working by modifying the /conf/neo4j-server.properties file and following the instructions at the github repo.
# Basic Auth-Filter-Extension
# See docs here: https://github.com/neo4j-contrib/authentication-extension
org.neo4j.server.credentials=your_user_name:your_password
org.neo4j.server.thirdparty_jaxrs_classes=org.neo4j.server.extension.auth=/auth
I was deploy pentaho bi server on my running tomcat server ref from here.
Now I want to create JNDI bases datasource so I login through pentaho administration console but in that web page nothing to shows users lists, user role. After googling some times I was found that change console.xml then I was changed my console.xml file as below
<?xml version="1.0" encoding="UTF-8"?>
<console>
<solution-path>/home/pc-name/pentaho-solutions</solution-path>
<war-path>/home/pc-name/apache-tomcat-7.0.47/webapps/pentaho</war-path>
<platform-username>joe</platform-username>
<biserver-status-check-period-millis>30000</biserver-status-check-period-millis>
<homepage-url>http://www.pentaho.com/console_home</homepage-url>
<homepage-timeout-millis>15000</homepage-timeout-millis>
<!-- comma separated list of roles (no spaces) -->
<default-roles>Authenticated</default-roles>
<default-server-dir>biserver-ce</default-server-dir>
</console>
then I was stopped administration console and then again start but still it not shows me any user lists, role lists. After that I hard coded start-pac.sh as below
DIR_REL=`dirname $0`
cd $DIR_REL
DIR=`/home/pc-name/apache-tomcat-7.0.47`
cd -
. "$DIR/set-pentaho-env.sh"
setPentahoEnv "$DIR/../biserver-ce/jre"
but running at start-pac.sh it shows set-pentaho-env.sh not found but in my first steps deploying pentaho bi server on existing tomcat it not mentioned anything about set-pentaho-env.sh where to copy or set. Can any one knows how to solve this problem?
Short answer: Pentaho 5.0 doesn't have an admin console because both user roles and database connections are easily configured in the user console. It seems you just started to deploy your biserver so I suggest you upgrade to the new version and leave admin console behind. Trust me. You will like it.
Long answer: If you still wish to stay with 4.8 for some strange reason:
Don't change anything in Pac-start.bat, revert to the original version before your changes. If you need to change the default URL or port, then
find biserver-ce\tomcat\conf\server.xml
the default for pentaho user console is 8080, and the default admin console port is 8443. Change those to your preference. Once done,
find biserver-ce\tomcat\webapps\pentaho\WEB-INF\web.xml
change here:
<context-param>
<param-name>fully-qualified-server-url</param-name>
<param-value>http://localhost:8080/pentaho/</param-value>
</context-param>
then find the list of trusted Ip's and add additional trusted IP's here (this is somewhere around line 133)
<param-name>TrustedIpAddrs</param-name>
<param-value>127.0.0.1,0\:0\:0\:0\:0\:0\:0\:1(%.+)*$</param-value>
<description>Comma separated list of IP addresses of a trusted hosts.</description>
(Also covered in this article: http://wiki.pentaho.com/display/ServerDoc2x/Setting+up+trust+between+Administration+Console+and+BI+Server)
Make sure when you start the admin console, pentaho biserver is running already. Admin console will not work if the biserver is not running.
Make sure you use the correct JDK, because a wrong java configuration, or wrong java_home_path can also cause admin console to not stand up.
Really, just go with Pentaho 5.0.1.