openshift

Travis + Openshift Not deploying to openshift

由 大憨熊 提交于 2020-01-24 22:42:11
问题 We are having issues with being able to deploy to openshift. The deployment process runs but then doesn't actually deploy any new code to our gears. Here is my travis file: language: node_js node_js: - '0.10' before_script: - npm install -g bower grunt-cli - gem install sass - bower install services: mongodb before_deploy: - rm -rf .sass-cache .tmp client e2e node_modules server styleguide *.* - mv dist/* ./ - rm -rf dist - ls notifications: slack: REMOVED deploy: - provider: heroku api_key:

Cannot import a json in MongoDB

由 亡梦爱人 提交于 2020-01-24 22:41:25
问题 I am using RockMongo in Openshift to import a json file in MongoDB database. I exported directly the json from another MongoDB and I haven't changed anything. Here is a part of the json: { "_id" : "10352", "author" : "8988607", "country" : "...", "views" : 1716, "title" : "...", "comments" : 1, "likes" : 28, "text" : "...", "date" : { "$date" : 1278070740000 }, "approved" : "8480596" } And I have this error message: exception: field names cannot start with $ [$date] at src/mongo/shell

Can PostgreSQL service in OpenShift cluster receive external traffic via exposed route

由 混江龙づ霸主 提交于 2020-01-24 20:47:26
问题 Is it possible to run PostgreSQL as a service inside an OpenShift cluster and get external traffic to it via an exposed route (the recommended default way for communicating from the outside)? The OpenShift 3.9 documentation states this: A router is configured to accept external requests and proxy them based on the configured routes. This is limited to HTTP/HTTPS(SNI)/TLS(SNI), which covers web applications. PostgreSQL can to SSL and it can be configured to listen on port 443 (HTTPS), but I

Validate OpenShift objects defined in yaml before actually applying or executing it

由 五迷三道 提交于 2020-01-24 09:54:05
问题 I have a OpenShift template in template.yaml file which includes following objects - deployment-config, pod, service and route. I am using the following command to execute the yaml: oc process -f template.yml | oc apply -f - I want to perform following validations before I actually apply/execute the yaml: YAML syntax validation - if there are any issues with the YAML syntax. OpenShift schema validation - to check if the object definition abides by the OpenShift object schema. It seems that

openshift3.10集群部署

由 谁说我不能喝 提交于 2020-01-23 16:25:52
简介 openshift是基于k8s的开源容器云。 要求 系统环境：CentOS 7.5 搭建一个master节点，两个node节点 注意： openshift3 依赖docker的版本为1.13.1 openshift3.10支持的是ansible2.4.3.0以上2.8.X以下 保证各节点时间统一，可以统一向阿里云时间服务器同步 准备工作 所有节点创建工作目录：在根目录下创建家目录 mkdir /home && cd /home # 先关闭防火墙，后续为了安全再重新配置防火墙 # 查看防火墙的状态 systemctl status firewalld # 关闭防火墙 systemctl stop firewalld # 关闭防火墙的自启动 systemctl disable firewalld 配置说明 修改主机名 #master: #192.168.2.180 hostnamectl set-hostname master.example.com #node1: #192.168.2.181 hostnamectl set-hostname node1.example.com #node2: #192.168.2.182 hostnamectl set-hostname node2.example.com 域名映射 这3台主机(master,node1,node2)都需要在

Difference between API versions v2beta1 and v2beta2 in Horizontal Pod Autoscaler?

由 元气小坏坏 提交于 2020-01-23 07:37:08
问题 The Kubernetes Horizontal Pod Autoscaler walkthrough in https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/ explains that we can perform autoscaling on custom metrics. What I didn't understand is when to use the two API versions: v2beta1 and v2beta2. If anybody can explain, I would really appreciate it. Thanks in advance. 回答1: The first metrics autoscaling/V2beta1 doesn't allow you to scale your pods based on custom metrics. That only allows you to scale

Multiple containers in one pod

由 橙三吉。 提交于 2020-01-21 14:37:34
问题 I am migrating an application from openshift 2 such consists of a Java(jetty) webserver and a mongo database. Both the webserver and mongo need access to persistent storage, as well as the server accessing the database. As the volume available to me can't (I believe) be accessed by two pods my current goal is to include both the server and dB into the same pod as separate containers. I have tried copying the mongo container into the deploy config for the server but I just get an error saying

Multiple containers in one pod

由 倾然丶 夕夏残阳落幕 提交于 2020-01-21 14:35:33
问题 I am migrating an application from openshift 2 such consists of a Java(jetty) webserver and a mongo database. Both the webserver and mongo need access to persistent storage, as well as the server accessing the database. As the volume available to me can't (I believe) be accessed by two pods my current goal is to include both the server and dB into the same pod as separate containers. I have tried copying the mongo container into the deploy config for the server but I just get an error saying

Openshift与Kubernetes的区别

由 百般思念 提交于 2020-01-18 21:22:51
Openshift与Kubernetes的区别 Openshift首个支持企业级 Java 的 PaaS 平台，支持 JEE6 与 JBoss 和其 Eclipse 集成开发环境以及 Maven 和 Jenkins 自动化。使用 OpenShift 的人数及社区人数在不断增长。OpenShift基于Kubernetes，增加哪儿些功能？有什么区别? 1.Openshift 的 Web console Openshift的web console采用node.js 与angularJS开发，支持实时推送,如下示例 2.集成容器管理与ImageStream OpenShift Container Registry 自动管理镜像的版本，ImageStream包含所有镜像的原数据，但ImageStream不包含Image数据。 使用Image Stream的目的是方便地将一组相关联的镜像进行整合管理和使用。 Openshift默认为用户定义了一系列开箱即用的Image Stream。 #查看Image Stream对象 #oc get is -n openshift 3. Native CI/CD factory 原生支持Pipeline的Build实现CI/CD过程 Jenkins Plugin能直接触发openshift的构建和部署过程, 同时最吸引的特点是:

从一张图看Devops全流程

由 南笙酒味 提交于 2020-01-18 00:46:59
一、持续交付工具链全图 上图源自网络。上图很清晰地列出了CD几个阶段使用的工具。 CD的工具链很长，但并不是每个模块所有工具都那么流行；换言之，我们在每个模块用好一种工具就足够了。 Build 在SCM的模块中：Git系列用的比较多，如Gitlab； 在CI模块中：Jenkins显然是最流行的； 在Build模块中：Maven、docker用的较多； Test 在Testing模块中：Junit、Jmeter用的较多； Deploy 在配置管理模块中：前些年Puppet比较火，这两年Ansible用的比较多；、 在Artifact管理中：Dockerhub是在线的，docker registry是离线的。Openshift的集成镜像仓库用的就是docker registry技术。Quay是CoreOS的镜像仓库工具，有在线也有离线的，相信后续会被整合到Openshift中。 Run 在Cloud/IaaS/PaaS模块中：这两年PaaS的活跃程度超过IaaS，我接触比较多的是其中的Openshift。 在编排模块中：K8S目前是主流，无可争议。 在BI/Monitoring/Logging中：EFK之前用的比较多，但大家普遍看好普罗米修斯。 二、红帽的Devops全图 上图是一个比较典型的Devops流程。包括产品立项、需求分析、应用设计、开发、测试、持续发布、生产运维、回顾阶段。
订阅 openshift