Concurrent Releases #71

New issue

Closed

opened 2020-12-03 16:26:15 +00:00 by rafael · 4 comments

rafael commented

2020-12-03 16:26:15 +00:00

(Migrated from gitlab.privaz.io)

ACS Releases rely on specific Vagrant VM names and IP spaces used on VLAN 20

It would be good to be able to run as many releases as possible in parallel.

For that a ACS ID could be used, from 1 to 254, and used that ID to name the Vagrant VMs as well as the public network on VLAN 20

10.20.ID.0/24 can be used as public IPs both for System VMs and and VMs.

ACS Releases rely on specific Vagrant VM names and IP spaces used on VLAN 20 It would be good to be able to run as many releases as possible in parallel. For that a ACS ID could be used, from 1 to 254, and used that ID to name the Vagrant VMs as well as the public network on VLAN 20 10.20.ID.0/24 can be used as public IPs both for System VMs and and VMs.

rafael commented

2020-12-03 16:54:46 +00:00

(Migrated from gitlab.privaz.io)

The Pipeline ID can be used to calculate the ACS ID with bc

The pipeline ID can be get from $CI_PIPELINE_ID

$CI_PIPELINE_ID % 254 | bc

That would return the ACS ID and with that derive other names, etc.

The Pipeline ID can be used to calculate the ACS ID with bc The pipeline ID can be get from $CI_PIPELINE_ID ``` $CI_PIPELINE_ID % 254 | bc ``` That would return the ACS ID and with that derive other names, etc.

rafael (Migrated from gitlab.privaz.io) closed this issue

2020-12-04 11:23:58 +00:00

rafael commented

2020-12-06 10:32:19 +00:00

(Migrated from gitlab.privaz.io)

mentioned in issue #75