Does this depend on any backend API change?

Nevermind - I checked, it does; we may need to wait until the upstream PR is merged at all.

@blueorangutan package

@GabrielBrascher a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress.

Packaging result: ✔️centos ✔️debian ✔️archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/838 (JID-3634)

It fails to open the edit popup when trying to edit a template. Tested via http://primate-qa.cloudstack.cloud:8080/client/pr/838.

Can you please check this @ravening?

It fails to open the edit popup when trying to edit a template. Tested via http://primate-qa.cloudstack.cloud:8080/client/pr/838.

Can you please check this @ravening?

@GabrielBrascher do you have the back end change as well?
I tested with having backend change and worked fine. I have attached the screenshot as well

Ah ... it got merged yesterday (apache/cloudstack#3945), I see. I will test it later based on the recently merged commit.

It fails to open the edit popup when trying to edit a template. Tested via http://primate-qa.cloudstack.cloud:8080/client/pr/838.
Can you please check this @ravening?

@GabrielBrascher do you have the back end change as well?
I tested with having backend change and worked fine. I have attached the screenshot as well

@GabrielBrascher on a side note, Im curious to know how to have multiple instances on primate running for each pr? is it an automated task? is there a way I can do that on my setup as well? I see that for each pr, there is an endpoint /client/pr/<pr#> . I want to know how to generate new setup like that for each pr

@ravening I have not much idea on the blueoragutan configuration. @rhtyd or @PaulAngus would be able to give some details.

My guess is that this was configured via Jenkins in order to provide the same Mocked infra (hosts, zone, networks, VMs, etc) for all PRs that are tested.

Blue Orangutan sends build requests to ShapeBlue's internal infra to do builds; So calls to it need to come from ShapeBlue people to protect the infra (and it's easier to shout at them than community members :) ).

We can happily share the actual build process (done via Jenkins).

The medium/long term goal is to have distributed build and test environments across 'donated' central community hardware and private environments, which would be orchestrated from a central location, with some kind of deployment planner.

Internally we know this project as Winston ("I fix things"), and we're going to create it internally which we will then share as a draft blueprint to be taken forward as a community (assuming people want it),

Blue Orangutan sends build requests to ShapeBlue's internal infra to do builds; So calls to it need to come from ShapeBlue people to protect the infra (and it's easier to shout at them than community members :) ).

We can happily share the actual build process (done via Jenkins).

The medium/long term goal is to have distributed build and test environments across 'donated' central community hardware and private environments, which would be orchestrated from a central location, with some kind of deployment planner.

Internally we know this project as Winston ("I fix things"), and we're going to create it internally which we will then share as a draft blueprint to be taken forward as a community (assuming people want it),

@PaulAngus Can you please share the build process and steps so that I will try implementing the same for our internal infrastructure?

@ravening

I've checked with Rohit regarding the base VM that we use to build primate.

It can be built using any Ubuntu LTS 18.04/20.04 base docker container.

There are build instructions are in the repo's README (https://github.com/apache/cloudstack-primate#getting-started)
These are wrapped up in `https://github.com/apache/cloudstack-primate/blob/master/packaging/package.sh

The overview of installation (again thanks to Rohit) is:

Install nodejs LTS

curl -sL https://deb.nodesource.com/setup_12.x | sudo -E bash -
sudo apt-get install -y nodejs debhelper rpm

Install build tools

npm install -g @vue/cli webpack eslint

In a cloned Primate repo and run package.sh

cd packaging
bash -x package.sh

In the README.md - https://github.com/apache/cloudstack-primate#packaging

Looks like related backend PR was merged, should we consider merging this @PaulAngus @DaanHoogland @davidjumani ?

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress.

Packaging result: ✔️centos ✔️debian ✔️archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/838 (JID-3687)