Spinnaker

VS 2017 + OpenCV + Spinnaker SDK(PointGrey) 配置

巧了我就是萌 提交于 2020-05-02 19:44:55
1. OpenCV 配置 1.1 下载 opencv 源码,并将其添加至环境变量 D:\opencv4.1\build\x64\vc15\bin 注:vs2015 选 vc14,vs2017 选 vc15 1.2 创建 C++ 项目,选择 “视图” -> “属性页”,配置:活动(Debug),平台:活动(x64) VC++目录:包含目录和库目录 包含目录:D:\opencv4.1\build\include; D:\opencv4.1\build\include\opencv2 库目录:D:\opencv4.1\build\x64\vc15\lib “链接器” -> “输入” -> “附加依赖项” opencv_world410.lib opencv_world410d.lib 注: opencv_world410d.lib 中的 'd' 表示 "debug",若没有 'd',表示 "release"; 这两个文件在 "D:\opencv4.1\build\x64\vc15\lib" 目录下。 1.3 测试 注:运行前,选择 Debug,x64 #include <opencv2/opencv.hpp> #include <iostream> using namespace std; using namespace cv; int main( int argc, char **

Spinnaker authentication using IAP

有些话、适合烂在心里 提交于 2020-03-03 04:43:10
问题 We are trying to enable authentication in Spinnaker using IAP. Spinnaker is deployed in GKE using HAL Deck and Gate are exposed to different domains using Ingress and HTTPS is enabled for both. IAP is enabled and credential is created. HAL configurations for IAP have been done and redeployed. BaseURLs for UI & API have been set. CORS pattern is set to the UI URL. Now when i try to open the application, initially the redirects to https://accounts.google.com/o/oauth2/v2/auth?.... fails a few

Spinnaker authentication using IAP

风格不统一 提交于 2020-03-03 04:43:07
问题 We are trying to enable authentication in Spinnaker using IAP. Spinnaker is deployed in GKE using HAL Deck and Gate are exposed to different domains using Ingress and HTTPS is enabled for both. IAP is enabled and credential is created. HAL configurations for IAP have been done and redeployed. BaseURLs for UI & API have been set. CORS pattern is set to the UI URL. Now when i try to open the application, initially the redirects to https://accounts.google.com/o/oauth2/v2/auth?.... fails a few

如何在阿里云容器服务ACK上部署应用管理/发布系统Spinnaker

狂风中的少年 提交于 2020-03-01 02:44:42
Spinnaker是一个开源的多云持续交付平台,可帮助您方便管理应用以及快速交付应用。 Spinnaker的两个主要功能是: 应用管理 , 应用交付 Applications, clusters, and server groups是Spinnaker中非常重要的几个概念, Load balancers and firewalls描述了如何向用户公开你的服务: 应用部署和部署策略: 在ACK上部署Spinnaker的步骤: (1)创建一个ACK集群 (2)创建Spinnaker需要的Kubernetes资源 (3)配置Spinnaker的安装文件 (4)部署并访问Spinnaker 1. 创建集群 参考 创建阿里云容器服务ACK集群 2. 创建Spinnaker需要的Kubernetes资源 2.1 创建 Namespace $ kubectl create ns spinnaker 2.2 创建 ServiceAccount ClusterRoleBinding 资源用于 Halyard 部署 Spinnaker rbac.yaml 文件内容: apiVersion: v1 kind: ServiceAccount metadata: name: spinnaker-service-account namespace: spinnaker --- apiVersion: rbac

云服务OpenAPI的7大挑战,架构师如何应对?

痞子三分冷 提交于 2020-02-29 07:25:16
阿里妹导读:API 是模块或者子系统之间交互的接口定义。好的系统架构离不开好的 API 设计,而一个设计不够完善的 API 则注定会导致系统的后续发展和维护非常困难。比较好的API设计样板可以参考 github 和 k8s ,它们都是典型的RESTful接口。云服务对外开放的窗口就是OpenAPI,今天要讨论的话题是“云服务场景下OpenAPI设计的挑战”。 为什么要有API规范 之所以强调“云服务”的原因在于,小规模独立API的设计与大规模批量生产API面临的问题是不一样的。同样,只专注于自身产品API的可用性与从更高的层次去看云服务整体API体系的健壮性,要建设的体系也是不一样的。 例如,做一个WEB页面使用的API,只需要考虑性能、稳定性、鉴权就好,因为页面与API是一体的,可以一起发布和回滚,只要功能正常,即便API设计有缺陷,用户也可以接受。而云服务要开放API考虑问题就多了: 首先,云服务开放的是基础设施和服务接口,一般是系统级的对接,API一旦开放想要变更就非常困难; 其次,云服务并非单独运行,不同的产品实际场景中是互相组合的,需考虑产品间的一致性和互通便利性; 云服务API数量庞大,为了更方便使用,配套的API查找、编排、自动化生成SDK等需求也比普通服务强烈; 云服务的稳定性非常重要,核心产品的稳定性就是客户的生命线,要求非常高。 所以云服务由于产品线众多

Spinnaker Nexus Integration

♀尐吖头ヾ 提交于 2020-01-25 11:11:46
问题 I'm facing issue while integrating spinnaker with Nexus. Basically, here is my process - Building docker image using Jenkins and uploading to Nexus. Next, want to trigger spinnaker pipelines based on new image available on Nexus to deploy apps on kubernetes. I've used these 2 commands hal config provider docker-registry enable hal config provider docker-registry account add my-docker-registry \ --address <pvtIP>:9082 \ --repositories repository/<repoName> \ --username <userName> \ --password

Spinnaker with restricted namspace access

﹥>﹥吖頭↗ 提交于 2019-12-24 11:29:24
问题 I am trying to setup spinnaker with kubernetes and getting an error: user cannot list namespace. I don't have access to list namespace in cluster scope. Is it possible to set up and apply hal configuration without access to list namespaces at cluster scope? if yes, please let me know the steps. Below I mention the command out for reference: hal deploy apply + Get current deployment Success - Prep deployment Failure Problems in default.provider.kubernetes.my-k8s-account: ! ERROR Unable to

Spinnaker: not able to access with localhost:9000 on Azure WM

Deadly 提交于 2019-12-23 05:49:10
问题 I have deployed Spinnaker successfully on an Azure VM. I am able to successfully connect via "ssh" and the outputs of curl http://9000 and curl http:8084/health are appropriate. Did the tunnelling as documented. However from my host machine browser I am not able to open the Deck UI. The http://localhost:9000 from my Mac Chrome Browser says: "This site can’t be reached. localhost refused to connect." 回答1: As long as your VM has a public IP/DNS the following instructions should work on a Mac, I

How to spin up spinnaker locally for the first time

為{幸葍}努か 提交于 2019-12-13 08:37:11
问题 How to spin up a local version of Spinnaker? This has been answered and addressed in detail here. https://github.com/spinnaker/spinnaker/issues/1729 回答1: Ok, so I got it to work, but not without you valuable help! @lwander So I'll leave the steps here for posterity. Each line is a separate command in the command line, I've installed this on a virtual machine with a freshly installed Ubuntu 14.04 copy with nothing else than SSH. Then SSH as root, You will need to configure sshd on your console

如何在阿里云容器服务ACK上部署应用管理/发布系统Spinnaker

一曲冷凌霜 提交于 2019-11-30 12:25:36
Spinnaker是一个开源的多云持续交付平台,可帮助您方便管理应用以及快速交付应用。 Spinnaker的两个主要功能是: 应用管理 , 应用交付 Applications, clusters, and server groups是Spinnaker中非常重要的几个概念, Load balancers and firewalls描述了如何向用户公开你的服务: 应用部署和部署策略: 在ACK上部署Spinnaker的步骤: (1)创建一个ACK集群 (2)创建Spinnaker需要的Kubernetes资源 (3)配置Spinnaker的安装文件 (4)部署并访问Spinnaker 1. 创建集群 参考 创建阿里云容器服务ACK集群 2. 创建Spinnaker需要的Kubernetes资源 2.1 创建 Namespace $ kubectl create ns spinnaker 2.2 创建 ServiceAccount ClusterRoleBinding 资源用于 Halyard 部署 Spinnaker rbac.yaml 文件内容: apiVersion: v1 kind: ServiceAccount metadata: name: spinnaker-service-account namespace: spinnaker --- apiVersion: rbac