I have OKD 4.5 installed on bare metal servers. I am looking for options to configure storage in worker node itself. In OKD 3.11 I was using Glusterfs as distributed storage and It seems glusterfs is not supported in OKD4. As alternate I am thinking to use OCS openshift container storage, But I could not find this operator in the OKD4 operatorHub.
Is there anyway to use glusterfs as PV or install OCS in OKD4 ?
Yes OCS is available on OCP v4.x, it is based on Ceph instead of Gluster
The official links to the doc:
https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.5/
https://docs.openshift.com/container-platform/4.6/storage/persistent_storage/persistent-storage-ocs.html
The original question was "Is there anyway to use glusterfs as PV or install OCS in OKD4 ?"
I don't think that OCS can be installed in OKD (It can, of course, be installed in OCP). I would love to be wrong, though. Not having an open-distribution of OCS means that even test and dev environments need to run costly licensed versions of OCP if you want to use OCS at all. It's a drag.
I suppose you could install the Rook operator to deploy and manage Ceph... it should be more-or-less the same thing, but it is not supported by Red Hat in production environments, so likely won't fit the bill for many shops.
GlusterFS appears to have no future in Red Hat as a container storage solution.
I am having RHEL7 OS VM of 16GB RAM and 4core CPU. I wanted to install openshift container platform 4.6.3 version as a all-in-one installation as I don't wanted to use codeready container platform for this purpose is there any way how I can install openshift 4x version as all-in-one installation.
No, installing OpenShift Container Platform 4.6 on this particular VM is not possible for multiple reasons:
In any case, the Control Plane requires Red Hat CoreOS as its Operating System.
The smallest possible OCP cluster is a Three-Node OpenShift Compact Cluster, where Control Plane nodes are also used to schedule workload. A single-node cluster installation does not exist at this time (apart from CodeReady Containers, which you do not want to use).
Even with the small cluster above, you are looking at at least 3x 24GB of RAM as the minimum requirement. VMs with less RAM might work, but the cluster will likely be unstable.
With limited resources, the only way to run OpenShift 4 is to use CodeReady Containers.
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.
A project with the following technologies and components has surfaced: to up a Web stack solution initially composed with Ubuntu, JDK, JBoss, Spring MVC 3.0+, and MySQL.
In planning this project, I have been struggling to find answers to the following questions for first steps, best practices, and sequence:
1) Does the JDK (and JBoss) need to be installed as ‘root’? (I have seen articles that mention it is not a good idea to operate in root unless absolutely necessary due to the fatal consequences.)
2) Does Ubuntu need to be installed as a Server in order to accomplish all this, or can it also be installed as a Desktop? I have not been able to determine if having a JBoss and MySQL need to be installed on top of Linux as a server.
3) Does Maven need to be used within Spring STS in order to get JBoss, and MySQL (and in the future Hibernate) to work successfully together?
4) My intent is to install in this order: a) Ubuntu -> b) Java -> c) JBoss -> d) Spring STS -> and e) MySQL. Are there any blatant conflicts in this sequence?
JBoss will require Java (recommend Java 7) before it will do anything. I don't think it really "installs" per-say, but rather just unpacks to some directory (even if you install from the package manager, it just really extracts itself). I question your need for Spring since JBoss and Java EE in general really does everything Spring does, and better now-a-days. Unless you have a specific requirement for Spring, I'd question this extra dependency.
For linux - in a high level, any OS can be a "server", all it needs is to be capable of serving things (web pages, ssh connections, etc). In M$ world, different "levels" of the OS have been specially designed based on anticipated task/workload. So for example, while Windows 7 can indeed run as a server, it was not designed for it and therefore may not be optimized or include helper utilities and tools to make life easier as a sys admin of the system. Windows Server on the other hand does include all the "normal" server tools and lots of goodies to make maintaining and setting the server up easier.
In linux land, this is no such thing. Linux is the kernel that talks back and forth with the bare metal, etc... and Distro makers will take that and build an OS around the kernel, basically just attaching any packages they feel their distro needs... such as wget, or cat, or any other standard userland apps, plus some non-standard such as mysql or java or whatever they want.
Now, some distributions of linux will tailor themselves at being "server" ready, while others will tailor themselves at being a desktop OS. The difference? It's really just whatever default packages the distribution maker decides to include or not. For example, the overwhelming majority of linux servers are run completely headless, and therefore there is absolutely no reason to have X11 and a huge bloated GUI environment installed and/or running on that system... it's pointless. Also, an "average joe" user does not need MySQL installed by default on his desktop system since it would only bloat his system and he likely won't ever use it.
So basically it comes down to default installed packages.
Some linux server distros take this further and exercise extreme caution when making updates, patches, or new releases in the name of stability and security, while on the other hand most desktop distros are more haphazard with their updates since if it breaks a home users web browser, it's probably not a huge deal... but if a server update breaks the webserver application stack, now that's a serious problem.
So you'll find server OS's like CentOS (based on upstream RHEL) are extremely slow to bring in the "latest and greatest" features that desktop OS's get early on. Their goal is high security and long term stability.
Now, for Ubuntu. While I certainty know a lot of folks run Ubuntu as their server OS choice (partly due to Amazon choosing Ubuntu as the default linux VM for their ECS cloud), but I'd really question this. Ubuntu is not focused on being a server. It's focused on being a great all-around desktop oriented OS. Yes the LTS version is meant for long term stability, but it's based out of a desktop OS, so it's still not the focus.
IMHO, I'd go with CentOS because it's free and completely binary compatible version of RHEL - and RHEL is the de-facto standard for enterprise-grade linux servers. Be aware though, the RHEL way of doing things is a bit different than the debian way -- so there is no apt-get, you must use yum install instead. Startup scripts are different and some ways of doing things are different, but really, once you know linux, you know linux.
EDIT: Also check into Jenkins - its a free opensource continuous integration system that runs on JBoss or Tomcat or any other container, and can automagically pull your code from a repo (github, git, svn, etc) and compile/package it then push it to live deployment. You setup your ANT or Maven build scripts, and it can kick off on a schedule or however you configure it.
EDIT EDIT: I'd also recommend using OpenJDK -- as it's likely included in your package manager (for just about every disto) and will be more updated than the oracle version if it's in your package manager too. I've found most "server" distros will have OpenJDK 7 while only having Oracle java 6 in their package managers. Also, installing it via the package manager will enable you to keep it updated a ton easier.
Installed as root, why not? Run as root, probably not a good idea.
If you want a desktop, install a desktop distrib. If you want a server, install a server distrib. This doesn't change what can and can't be run in the OS. It only changes what is installed by default.
Maven is a build tool. JBoss doesn't care how you build your app. All it cares about is if the application you deploy is a valid Java EE application.
No. You need an OS, so Ubuntu must come first. JBoss and (AFAIK) Spring STS need a JRE to run, as they're Java applications, so Java should be installed before them. MySQL is independent of JBoss, STS and Java, so you can install it whenever you want.
Note that if you're struggling just with this installation part, be prepared to suffer with the rest. Building a Java EE webapp is not a piece of cake, and you should probably find some experienced developer to help you, as it seems you're only beginning with Java.
I am currently running ubuntu 10.4, I would like to be able to run windows XP from within that machine, using vmware player/workstation. I am not sure which is better for my situation.
I need to verify my builds under a windows environment, which is why i need the vmware software, Does anyone have experience, running Hudson slaves on windows machine that is a VM, from a Linux machine that runs the master Hudson.
Are there any guides or tutorials on how to set this up, or practice that would speed up the process, and limit road blocks in the future.
Thanks.
Edit: VirtualBox would be just as useful. :) -- actually more interested in that.
Since you mentioned VirtualBox, there is a VirtualBox plugin for Hudson.