What is the difference between rhc and oc CLI-tools?
As I see, they do almost the same:
oc:
The OpenShift CLI exposes commands for managing your applications, as
well as lower level tools to interact with each component of your
system.
rhc does the same, no?
What should I use to manage my containers on OpenShift platform?
The rhc tool is for OpenShift 2. The oc tool is for OpenShift 3. They are completely different versions of the package. So you need to know which version of OpenShift you are using. If you are using the existing OpenShift Online version it is version 2. If you are using the new OpenShift Online developer preview, it is version 3.
Related
Since Docker can now run on Windows, is there a way to deploy Openshift OKD over a Windows VM?
In the documentation under System and environment requirements we can read that rhel family OS are needed, but I'm just wondering if there is a side process (alternative) process to perform this operation.
My main concern is that I need to run Windows containers on OKD.
The answer is that for OKD 3.11 this is not possible and has to do with the networking (OVS) not being available for Windows machines.
That being said, there is a lot of information available for Windows Container in Kubernetes itself, although there are A LOT of things that are not implemented or are not supported at this time: https://kubernetes.io/docs/setup/production-environment/windows/intro-windows-in-kubernetes/
You can expect Windows Containers to become available in OKD 4.5 or later as Tech Preview, but I personally would not hold my breath.
I want to install Fuse 7.0 on the servers of my company. Before with Fuse 6.3 to install a cluster I used Fabric ... What is the best way to do it with Fuse 7? Is it possible with the Fuse Standalone version?
Thanks!
Fuse 7 has built in cluster management when you use Fuse on OpenShift deployments. If you don't want to use OpenShift, then you will need to manage/automate the cluster of standalone Fuse JVMs yourself. Ansible is a great tool for this kind of thing, but definitely different from how Fabric used to work in Fuse 6.3.
I am trying to port one of our Tomcat based Windows application to Windows Nano Server Container. The installation process includes two Windows Service installations - an ActiveMQ service and another Tomcat Service. This is achieved using two batch files provided with the product. In addition to installing the service, they also pass several arguments pertaining to JVM. Now the issue I am facing is I am not able to get these services installed on a Nano Server. The same Dockerfile works perfect and installs the product on Windows Server Core Container.
Observation: The services which get installed through batch files are dependent on two system components - Ancillary Function Driver for Winsock (Service name: afd) and TCP/IP Protocol Driver (Service Name: tcpip). This is something which I discovered on a VM where the product was installed when checking the service properties. I see that they are absent in a Nano Server Container but are present in Windows Server Core container. Could that be a reason? If yes, is there any way to get those services running on Nano Server?
I am at a loss on how to troubleshoot this issue. Are there any limitations on Nano Server Container when it comes to Windows Services?
Consider building your docker container from the ground up,
Determine and set your prerequisites
Install all of the dependencies first
Install the application and services in question
(For additional information you can look at this wiki page.)
The Nano server container is minimal and misses many windows default services, you’ll have to build most of them through Dockerfile yourself.
The easiest method will be to do this manually on Nano server and confirm everything to be working in the docker container/image, and then later generate an automated build.
I've created my first application using Openshift Tech. It's a Java Web Application running on a JBoss at Openshift and uses MySQL 5.5 as its database. And I have to deploy by it using the war file (I don't know how to do it the normal way).
So anyone can tell me: Should I create a local database or use online database? And is there another way to deploy my Java app not using the war file?
I would suggest that you check out the OpenShift Developer Center (https://developers.openshift.com), specifically this link (https://developers.openshift.com/en/jbossas-overview.html) about using jboss. Make sure you read all of the sections, specifically the Deployment Options, and the Datasources links. If you are interested in just being able to do a "git push" to deploy your code, you should create a new jboss application on OpenShift, and do a "git clone" of the code and check out how it's setup, it is using the Maven project structure, which is pretty common.
Im trying to install the following components on Openshift (Free plan: 3 small gears):
Nginx
Php - php-fpm
MySQL
Wordpress
Since a DIY cartridge is limited to 1 gear and can't be scaled, do I need to install all components on one gear, or should I install each component on a separate gear? What's the best approach to install a custom LEMP stack on this server?
Thanks
You would need to install all of the components on one gear. If you install the database on a separate gear, without using a scaled application, then you would run into issues connecting to the database without using port forwarding between your gears.