Hi,
Right now it is my understanding that access to the artifacts rsync server is restricted to the subnet 172.19.0.0/22. The virtual machines in the new OpenStack cloud are located in 172.19.4.0/22 and are therefore getting permission denied errors.
This is a problem if we want to be uploading artifacts from a virtual machine. The vast majority of our artifacts are uploaded from the Duffy bare metal node (logs and so on) and it was our expectation that we could continue with this workflow with the OpenStack cloud. It sounds rather inefficient (but doable nonetheless) to first pull the logs from the node (baremetal or VM) to the slave and then re-upload it to the artifacts server but we'd rather avoid that.
Is there anything we can do ?
Thanks,
David Moreau Simard Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On 02/08/16 16:31, David Moreau Simard wrote:
Hi,
Right now it is my understanding that access to the artifacts rsync server is restricted to the subnet 172.19.0.0/22. The virtual machines in the new OpenStack cloud are located in 172.19.4.0/22 and are therefore getting permission denied errors.
we need to have the cloud instances be able to get to all ci infra, including the artifacts nodes.
This is a problem if we want to be uploading artifacts from a virtual machine. The vast majority of our artifacts are uploaded from the Duffy bare metal node (logs and so on) and it was our expectation that we could continue with this workflow with the OpenStack cloud. It sounds rather inefficient (but doable nonetheless) to first pull the logs from the node (baremetal or VM) to the slave and then re-upload it to the artifacts server but we'd rather avoid that.
Is there anything we can do ?
you should not need to do any workarounds like this, the cloud instances are meant to be setup to access all ci infra, this artifacts thing just looks like something we forgot to look at when setting up the network.
Fabian, is this something you can look into ? is there anything else that the cico nodes can get to that cloud.cico cant ?
On 03/08/16 07:36, Karanbir Singh wrote:
On 02/08/16 16:31, David Moreau Simard wrote:
Hi,
Right now it is my understanding that access to the artifacts rsync server is restricted to the subnet 172.19.0.0/22. The virtual machines in the new OpenStack cloud are located in 172.19.4.0/22 and are therefore getting permission denied errors.
we need to have the cloud instances be able to get to all ci infra, including the artifacts nodes.
This is a problem if we want to be uploading artifacts from a virtual machine. The vast majority of our artifacts are uploaded from the Duffy bare metal node (logs and so on) and it was our expectation that we could continue with this workflow with the OpenStack cloud. It sounds rather inefficient (but doable nonetheless) to first pull the logs from the node (baremetal or VM) to the slave and then re-upload it to the artifacts server but we'd rather avoid that.
Is there anything we can do ?
you should not need to do any workarounds like this, the cloud instances are meant to be setup to access all ci infra, this artifacts thing just looks like something we forgot to look at when setting up the network.
Network/routing is fine between the two locations/subnets : it's at the rsyncd configuration that there is a limitation (through host allow = ) that was configured when the artifacts node was installed/configured. We can add the remote 172.19.4.0/22 subnet too, but worth knowing that it will go through the vpn tunnel, so slower and hopefully people will not send multiple gigabytes of data through it
Fabian, is this something you can look into ? is there anything else that the cico nodes can get to that cloud.cico cant ?
We can have a look at that.
-
David Moreau Simard -
Fabian Arrotin -
Karanbir Singh