opendevstack / opendevstack/ods-core
ODS in a Box with Vagrant
@georgfedermann is already working on this.
Since Jan 5, 2021.
- Dominant language
- Shell
- Stars
- 53
- Forks
- 34
- Avg merge
- 3h 26m
- Merged PRs (30d)
- 1
Description
The concept of ODS in a box it's a really great idea and I am learning more about it in my spare time. I am interested in creating a cloud-agnostic VM image (not coupled to AWS for instance) that can run on my laptop (not in the cloud) using Vagrant with VirtualBox.
I've forked ods-core (master branch) into my personal account and extended ODS in a box with the following files:
- Created a Centos 7 Base image for VirtualBox with Packer
- Created a ODS Box for Vagrant with Packer
When I run packer build -on-error=ask ./ods-devenv/packer/CentOS2ODSBoxVagrant.json, Vagrant spins up a new VM in VirtualBox using the Centos 7 Base image and it proceeds to install the Atlassian stack, OpenShift, etc (using the boostrap.sh script). However, it fails when it tries to build the nexus image:
Screenshots
Affected version (please complete the following information):
- OpenShift: 3.11
- OpenDevStack (master branch)
Additional context
From the error message, I understand that the user does not have the RBAC permissions needed to list the secrets under the ods namespace.
==> vagrant: Warning: Group 'system:authenticated' not found
vagrant: role "view" added: "system:authenticated"
==> vagrant: + oc adm policy add-cluster-role-to-group system:image-puller system:authenticated -n ods
==> vagrant: Warning: Group 'system:authenticated' not found
vagrant: cluster role "system:image-puller" added: "system:authenticated"
==> vagrant: + oc adm policy add-cluster-role-to-user self-provisioner system:serviceaccount:ods:jenkins
==> vagrant: Warning: ServiceAccount 'jenkins' not found
vagrant: cluster role "self-provisioner" added: "system:serviceaccount:ods:jenkins"
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.