Enabling Robottelo for IPv6 Testing

[jyejare]

Problem Statement

Enabling IPv6 switching in Robottelo Automation

Solution

• Added the IPV6 switch and IPV6 proxy config that would switch ON and OFF the IPv6 Testing for robottelo tests via CI or local
• Added setup of Satellite HTTP Proxy by default to all satellite spinned as/by broker workers, factory, directly from Broker context manager
• Adder teardown of Satellite HTTP Proxy by default to all satellite spinned as/by broker workers, factory, directly from Broker context manager
• Added setup of Capsule HTTP Proxy by default to all capsules spinned by factory, directly from Broker context manager to speak to CDN for content access
• Adder teardown of Capsule HTTP Proxy by default to all capsules spinned by factory, directly from Broker context manager
• Deploy Arguments switches satellite / capsule spin up to use Ipv6 sat/cap/host

Followup PRs, coming next:

• [DEVs are yet to decide, Out of scope of the PR] Hosts spins up to use ipv6/ipv4 network (based on strategy of host testing in IPv6 is yet to decide)
• HTTP Proxy specific tests uses its own non-default-http-proxy setup

Broker Pending(Not blocking this PR from merge):

• Adding support to deploy container as content host in Ipv6 network

Related Issues

[JacobCallahan]

can you add some validators for these?

[rplevka]

I am not 100% sold on the implemented approach to dynamically update the hostname based on a single setting.

My suggestion would be to extend the settings that point to certain hostnames, to contain both versions, so the fixtures/tests could pick the appropriate one.

SETTING:
    SOME_SERVER_RESOURCE:
        IPV4: foo.bar.ipv4.baz
        IPV6: foo.bar.ipv6.baz

we could also implement some "default" flag (like we do in broker with providers) to save ourselves from having to be explicit about the IP version in scenarios where we don't care.

[jyejare]

@rplevka The hook implementation isnt really helping here as its resetting all the settings after the post hook and hence I changed the implementation to do this switching in config after settings object is initialized.

Coming back to your first concern which is having two different settings is not idealistic because then you have lot of handling(if conditioning) throughout robottelo to choose between v4 or v6 instance based on the network execution we are doing v4 or v6. Trust me it would be a lot of code changes.

With the current approach, the setting names would remain the same and only the values/hostnames would change behind the scenes, even one doesn't need to change the value/hostname to switch.

The only switch is is_ipv6 setting.

[rmynar]

ACK - although it's not perfect yet, the main goal seems to be completed - deployment of ipv6 server is possible and nothing else seems to be broken.

[jyejare]

The sanity regression testing is successfully verified for Ipv4 after recent changes. An Ipv6 was tested previously and it was successful too.

CC: @JacobCallahan

@devendra104 , I think we need to merge the changes in CI for this PR to me merged. Especiallly conf related changes which wont also impact existing IPv4 pipelines.

[jyejare]

trigger: test-robottelo
pytest: tests/foreman -m build_sanity
env:
    ROBOTTELO_server__deploy_arguments__deploy_network_type: ipv4
    ROBOTTELO_server__is_ipv6: False
    ROBOTTELO_server__http_proxy_ipv6_url: ''

[Satellite-QE]

PRT Result

Build Number: 7388
Build Status: SUCCESS
PRT Comment: pytest tests/foreman -m build_sanity --external-logging
Test Result : ======= 12 passed, 5502 deselected, 5607 warnings in 1555.35s (0:25:55) ========

[jyejare]

@JacobCallahan We should be good to merge the PR now as the PRT is passing showing no regression on existing IPv4 testing.

This should not need CI MR to merged as we are taking care of it from dynaconf validators.

[JacobCallahan]

I'm going to merge this now. @ogajduse if there is anything you'd still like addressed for this post-merge, please write it down and create an issue for it to be resolved later. I'd like to move this forward so we can flesh out things live.