Also, several other projects (import, baserock-chroot,
lorry-controler, lorry ...) have been moved to gitlab.com/baserock
I tihnk the only relevent one I didn't mirror yet is
; do we want
to move this repo to gitlab.com/baserock
or keep it in the trove only?
Active merge request for definitions has been moved to ; feel free
to send more!
Below some of the action points in progress
On 8 November 2016 at 11:26, Pedro Alvarez
On 07/11/16 12:09, Javier Jardón wrote:
>>> I've already migrated the active merge request to the new location
>>> , and I will try to edit the wiki over the weekend
>>> To mirror back definitions to
I need the trove
>>> credentials (user/pass) so gitlab can push there; can anyone give me
>>> them in private? (or join the gitlab.com/baserock/definitions
>>> , and configure the mirror here  :))
>> I don't understand this requirement. Can you explain this better?
>> Why would you need an user/pass in the trove for this? User/pass
>> access is disabled in the Trove for security reasons, and only the
>> infrastructure team has access to it using ssh keys.
>> What would you do with them? change something internally? Some kind of
>> configuration? Anything that implies configuring the trove should be
>> scripted so that we can do it again anytime.
>> I don't think you will be able to (git) push anything to the Trove
>> with this kind of credentials (if they existed)... Or is it the case
>> that Gitlab does something "clever" and `rsync`s the contents?
>> If Gitlab can push (when configured properly) why do we have to move
>> it to delta/definitions? I thought that the only way to do this was to
>> create a lorry for definitions from gitlab.
>> If what you are looking for is for a Gitano user that can push via
>> https using User/pass, I think that's disabled as well, but we could
>> have a look.
> Yeah, this last one is what we need to alloy gitlab to push in the trove.
> As I said, we can do it this way or we can setup a lorry to mirror the
> definitions repo in gitlab to g.b.o
Sorry for not answering earlier, I'm quite busy these days :/
I'd prefer to set up Gitlab to Push. That will mean that we will not
Yeah, me too
need to change the location in g.b.o. but also we will need to do
- Create an user for Gitlab in g.b.o using Ansible setup scripts of
- Research if https user/password login is safe
- Enable https user/password login
- Ensure nobody else, only Gitlab, can push to "baserock/" epositories.
- Document the Gitlab integration with g.b.o in infrastructure.git
I do not have access to the trove infra to do this changes; can anyone
with access make this?
If we want to go with the lorring approach (uglier IMO)
- Create a lorry for all of the repositories in Gitlab
- Deprecate the migrated repos in g.b.o. and even make them read-only
I think is better the previous approach
Common: Deprecate Gerrit
- Move relevant patches to Gitlab
- Kill (or shutdown) instance
- Stop the backups of Gerrit database
- Adjust infrastructure.git to remove Gerrit from there
No access to gerrit instance to do this; but I think we can hold on
this until everything is migrated
- Remove mentions about Gerrit in the wiki, and replace with docs
I'm working on this