AWS EFS and Windows (yet again) - windows-server

Restarting a topic I found here, a few years back: need to migrate a large pool of NFS shares / mount points content, used equally by Windows and Linux clients, from on-prem, to AWS. I looked at the official EFS page # AWS, here, and there still doesn't seem to provide "support" for Windows instances. On the other hand, as few mentioned a few years back the UMIch NFS client ver 4.1 for Windows, that is already [what I assume to be] a new version available officially from Microsoft, supporting Server 2012, 2016, etc. Is Microsoft client still lacking what the UMich client offers, in order to work with the AWS EFS?

Related

Add a Windows node to Openshift OKD v.3.11

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.

possibility of having 2 mercurial servers, using the same database

I have a Mercurial server on a simple server (Virtual Machine (VM)), and about 100 users with access. And from time to time, requests have been slow.
And since I can not change the hardware of this server, because the VM server no longer has available resources, and migrating it would do a great job.
I would like to know it is possible to have 2 mercurial servers, using the same database, because this would balance the load, and in one server would put a large team, and in the other the other teams. In short, I can not mess with the server you're on today.
VM:
Windows Server 2003 SP2
1.5GB Memory
60GB HD
Settings:
Python 2.7.2
Mercurial 2.5.4
RhodeCode 1.6.0rc1
Note:
Sorry if you're confused, this question was translated via google. If you can edit and rearrange it, I'll be very grateful.
This is certainly possible. If you have shares storage RhodeCode can use the same DB and load-balance load between machines.
Btw, 1.6.0 is very old I'd take a chance at upgrading this.

Installing Apache, MySQL (and secure it), PHP, phpMyAdmin in Amazon EC2

The reason for me posting this is I am really tired and wasted days trying to properly install a web server in amazon AWS Amazon Linux AMI 2015.03 (HVM), SSD Volume Type instance.
I have tried to install LAMP as mentioned in Tutorial: Installing a LAMP Web Server on Amazon Linux and found I am still not able to access PHPMyadmin.
Now for days I am trying to setup Apache, Apache Tomcat, MySQL, PhpMyAdmin and I always face troubles because 99% of the tutorials are written in 2012 and 100% outdated by now. Amazon tutorials are incomplete as they always are, so something is always left to find.I have almost opened and closed more than 4 instances, due to heavy "mess ups".
Can someone please point me to an "updated" tutorial which has the information of installing Apache, MySQL, PhyMyAdmin, PHP ? And of course I need to access these services from a URL, so remote access instructions also required.
Maybe you should consider running your setup on an Ubuntu instance, there are tons of tutorials for running a lamp stack on Ubuntu 14.04.
For instance, Digital Ocean Tutorials are a great resource: https://www.digitalocean.com/community/tutorials/how-to-install-linux-apache-mysql-php-lamp-stack-on-ubuntu-14-04
Next time please post this on serverfault.com .

Open Source Application Server Solution

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.

SQL server failover Cluster not reporting correct patch version

I've got a bit of an obscure problem and I'm hoping someone here can give me some pointers regarding it, I've exhausted everythign I can think of...
At the moment, I have a two node cluster setup (sql server 2008). I have patched this, as per the microsoft guidlines, to service pack 1. The issue is, when I connect to each node individually, I can see the version is 10.1.xxxx, but, when I connect to the cluster by it's name, it reports 10.0.xxxx (the pre-service-pack installation version).
I've tried restarting the cluster services, and also re-applying the patch (which is impossible, because the service pack installer reports the cluster is at 10.1.xxxx - sp1).
Any help/advice/ideas welcome.
Dave
I opened a microsoft support ticket for this, and had the issue corrected by an extremely helpful MS support engineer - sadly, I'm not sure of the details of the fix.
Dave