Re: capacity for more slaves

Hello David. Forgot one "A". So it is SLAAC a scheme where IP address of the host in IPv6 is generated from the mac address by the host itself and so it is stateless at that sense and does not require keeping IP to MAC database anywhere. Also unless privacy extension is enabled the machine will

Re: capacity for more slaves

On 05/13 10:50, Anton Marchukov wrote: > Hello All. > > Then I suggest consider rolling out IPv6 for the slaves right away > especially since it was declared a goal for oVirt 4. This can also simplify > slaves management as we can use SLAC for IP assignment and can solve that > DHCP update

Please remove ovirt-node-ng-image* from several repositories

Hey, could someone please remove all builds of these two packages: ovirt-node-ng-image ovirt-node-ng-image-update from the ovirt-3.6* ovirt-4.0* master* repositories? This is needed, because the versioning was changed. Thanks fabian -- Fabian Deutsch RHEV Hypervisor

Re: capacity for more slaves

Hello All. Then I suggest consider rolling out IPv6 for the slaves right away especially since it was declared a goal for oVirt 4. This can also simplify slaves management as we can use SLAC for IP assignment and can solve that DHCP update problems we had in foreman due to stale mac addresses

Re: capacity for more slaves

On 05/13 09:10, Anton Marchukov wrote: > Hello All. > > Are those IPs are used by any tests or the jobs itself? Are used by the slaves themselves (each slave has one ip), not really needed for anything (the slaves are not contacted by any outside machine nor offering any service) > > Anton. >

[oVirt Jenkins] ovirt-engine_master_upgrade-from-3.6_el7_merged - Build # 216 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/216/ Build Number: 216 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/57387

[oVirt Jenkins] ovirt-engine_master_upgrade-from-master_el7_merged - Build # 221 - Failure!

Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/221/ Build Number: 221 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/57387

Re: ovirt-srv11

> > I think that coupling the engine upgrade with the new slaves is not > necessary. > we can start by installing the hook on ovirt-srv11 and spinning up new > slaves, > that way we can also test the hook in production. because there is no NFS > involved, > and live migration isn't working with

Re: capacity for more slaves

I agree with David here, I don't see a point in giving out real internet IPs to machines that don't need it. Options are: * request a new VLAN and put internal machines there * use internal IPs on the same VLAN (quick fix, yet not a good one) * request to extend /25 subnet to /24 or allocate

Re: capacity for more slaves

Hello All. Are those IPs are used by any tests or the jobs itself? Anton. On Fri, May 13, 2016 at 9:03 AM, David Caro Estevez wrote: > One possibility that will give us a lot of ips is using internal ones, > though it will require a bit more configuration but now that the

Re: capacity for more slaves

One possibility that will give us a lot of ips is using internal ones, though it will require a bit more configuration but now that the jenkins master is in phx I think it might be a good option David Caro El 13 may. 2016 7:57, Eyal Edri escribió: Please open a ticket in