I want to install openshift origin containerized installation(advanced installation) on machine without internet access.
I referred to this URL -> https://docs.openshift.com/enterprise/3.1/install_config/install/disconnected_install.html
But it still going to docker.io and registry.*.redhat.com.
Please suggest a possible approach to achieve the goal.
There is a way to accomplish this install.The updated documentation does list the steps.
Let me know if you are still looking for the steps.
Related
The option to create dynamic certificates in ZAP is not available. I cannot see anywhere that it might have moved to and Google is not helping. I am running it on a Kali VM.
Does anyone know whether it's been removed? If not, where/how do I get to it?
Thanks.
No, we've not removed it :/
But you might have accidentally disabled it - have a look in the Options / Extensions - is the ExtensionDynSSL there? If so is it disabled? Enabling it and restarting ZAP should do the trick. If its not there I'd be tempted to try reinstalling..
Simon (ZAP Project Lead)
I am running openshift origin All-in-One setup using available binaries. Is it possible to add multiple nodes to this existing installation ?
What are the prerequisites for this, do I need to setup ssh connections between hosts?
Please do let me know how or if there is any link available for the same?
Thanks a lot!
Yes you can add additional nodes. Check this link
Basically you have to export the config for this new node and move it over to that node and start using the node-config.yaml
I have a kubernetes cluster, and I am wondering how (best practice) to update containers. I know the idea is to tear down the old containers and put up new ones, but is there a one-liner I can use, do I have to remove the replication controller or pod(s) and then spin up new ones (pods or replicaiton controllers)? With this I am using a self hosted private library that I know I have to build from the Dockerfile and the push to anyway, this I can automate with gulp (or any other build tool), can I automate kubernetes update/tear down and up?
Kubectl can automate the process of rolling updates for you. Check out the docs here:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/kubectl_rolling-update.md
A rolling update of an existing replication controller foo running Docker image bar:1.0 to image bar:2.0 can be as simple as running
kubectl rolling-update foo --image=bar:2.0.
Found where in the Kubernetes docs they mention updates: https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/replication-controller.md#rolling-updates. Wish it was more automated, but it works.
EDIT 1
For automating this, I've found https://www.npmjs.com/package/node-kubernetes-client which since I already automate the rest of my build and deployment with a node process, this will work really well.
The OpenShift Origin project (https://github.com/openshift/origin) runs an embedded Kubernetes cluster, but provides automated build and deployment workflows on top of your cluster if you do not want to roll your own solution.
I recommend looking at the example here:
https://github.com/openshift/origin/tree/master/examples/sample-app
It's possible some of the build and deployment hooks may move upstream into the Kubernetes project in the future, but this would serve as a good example of how deployment solutions can be built on top of Kubernetes.
I was able to install the default cartridges bundled in Origin,,
What if I need to add some application like ex: httpd server, ldap server, tomcat etc..
Is there a way to do it, I saw the DIY and customer cartridge install, is there any pointers on how to use those?
Regards
G
I am not sure your question is 100% clear. If you are trying to install downloadable cartridges, you should be able to use the same syntax that you use for online, something like:
rhc app create jekyll https://raw.github.com/openshift-cartridges/openshift-jekyll-cartridge/master/metadata/manifest.yml
If that is not what you are asking, can you be more specific about what you are trying to do, and what you have tried already and what errors it gave?
Currently, I can push my repositories to CentOS server (example.com) through ssh to /var/lib/mercurial-server/repos/SOMEREPO using hgadmin.
Is there a way to access SOMEREPO via example.com/SOMEREPO ?
There are a lot of ways how you can publish your repositories.
If you're familiar with apache, the probably simplest solution is to use hgweb.cgi which is a cgi script that comes with the mercurial distribution.
An in-depth step-by-step guide how to setup hgweb can be found at the mercurial wiki . Since you mentioned CentOS, you probably want to check out the hgweb setup guide for RHEL4.
If you're looking for more complete web-based tools to manage your repositories you may want to look into SCM-Manager or RhodeCode.