Send kea-dev mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/kea-dev
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of kea-dev digest..."
Today's Topics:
1. DDNS testing (wlodek)
2. Re: DDNS testing (Thomas Markwalder)
3. Re: DDNS testing (Shawn Routhier)
4. Re: DDNS testing (Tomek Mrugalski)
----------------------------------------------------------------------
Message: 1
Date: Thu, 05 Jun 2014 10:27:31 +0200
From: wlodek <[email protected]>
To: [email protected]
Subject: DDNS testing
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hello,
I need to bring one subject to discussion. DDNS testing framework.
1. It will be done by extending Forge
2. Tests will be run on whole system not just D2 server. We need to set up:
- DHCP (for v4 and v6 will be separate tests)
- DDNS server
- DNS server
3. Extended tests will be for:
- multiple DNS servers running
- DHCPv4 and DHCPv6 working at the same time.
4. Detailed tests cases were not specified yet.
In general it is simple as it is. But in Forge there is no way to manage
DNS server - so I need to extend it.
Stephen suggested:
- run BIND as DNS server
- add config file to each test for DNS server (mostly it will be the
same very simple config)
That is the easiest, fastest method, in this case we need just basic DNS
managing. Generally that is all we need to perform DDNS testing.
What I proposed was:
- extend Forge for dynamic building DNS config files (for now just for BIND)
- add module to manage BIND in the same way it is done for Kea, ISC-DHCP
or Dibbler.
- add module that will handle managing two servers at the same time (now
we can run only one)
That is more work and more time. We gain only ability to run DDNS test
with different DNS server, what is not so important to do the DDNS
testing itself. But that isn't point of Forge to make generic tests?
Another thing is that I have on a list 'extend Forge with DNS tests' I
could make preparations for DNS testing and just write tests some time
after.
What do you think? I would really like have some input from you guys.
Thank you very much,
W?odek
------------------------------
Message: 2
Date: Thu, 05 Jun 2014 10:53:00 -0400
From: Thomas Markwalder <[email protected]>
To: [email protected]
Subject: Re: DDNS testing
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8
On 6/5/14, 4:27 AM, wlodek wrote:
> Hello,
> I need to bring one subject to discussion. DDNS testing framework.
>
> 1. It will be done by extending Forge
>
> 2. Tests will be run on whole system not just D2 server. We need to
> set up:
> - DHCP (for v4 and v6 will be separate tests)
> - DDNS server
> - DNS server
>
> 3. Extended tests will be for:
> - multiple DNS servers running
> - DHCPv4 and DHCPv6 working at the same time.
>
> 4. Detailed tests cases were not specified yet.
>
> In general it is simple as it is. But in Forge there is no way to
> manage DNS server - so I need to extend it.
> Stephen suggested:
> - run BIND as DNS server
> - add config file to each test for DNS server (mostly it will be the
> same very simple config)
>
> That is the easiest, fastest method, in this case we need just basic
> DNS managing. Generally that is all we need to perform DDNS testing.
>
> What I proposed was:
> - extend Forge for dynamic building DNS config files (for now just for
> BIND)
> - add module to manage BIND in the same way it is done for Kea,
> ISC-DHCP or Dibbler.
> - add module that will handle managing two servers at the same time
> (now we can run only one)
>
> That is more work and more time. We gain only ability to run DDNS test
> with different DNS server, what is not so important to do the DDNS
> testing itself. But that isn't point of Forge to make generic tests?
> Another thing is that I have on a list 'extend Forge with DNS tests' I
> could make preparations for DNS testing and just write tests some time
> after.
>
> What do you think? I would really like have some input from you guys.
>
> Thank you very much,
> W?odek
> _______________________________________________
> kea-dev mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/kea-dev
I'm assuming you mean BIND9? I can tarball up what I did for my manual
testing using BIND9. It might give you a leg up or at least some
ideas. For each DNS server instance I wanted, I created a directory
tree which housed its configuration files and db files, and then wrote a
script that let me start, stop, reload configuration, reset database for
a given DNS server. Made things pretty easy. If you're not familiar
with rndc (BIND9's remote control program) you should read up on it.
------------------------------
Message: 3
Date: Thu, 5 Jun 2014 18:15:10 -0700
From: Shawn Routhier <[email protected]>
To: Thomas Markwalder <[email protected]>
Cc: [email protected]
Subject: Re: DDNS testing
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
On Jun 5, 2014, at 7:53 AM, Thomas Markwalder wrote:
> On 6/5/14, 4:27 AM, wlodek wrote:
>> Hello,
>> I need to bring one subject to discussion. DDNS testing framework.
>>
>> 1. It will be done by extending Forge
>>
>> 2. Tests will be run on whole system not just D2 server. We need to
>> set up:
>> - DHCP (for v4 and v6 will be separate tests)
>> - DDNS server
>> - DNS server
>>
>> 3. Extended tests will be for:
>> - multiple DNS servers running
>> - DHCPv4 and DHCPv6 working at the same time.
remember that this requires the clients to do the right
thing with the duid / clientid if you want them to share
a name.
>>
>> 4. Detailed tests cases were not specified yet.
>>
>> In general it is simple as it is. But in Forge there is no way to
>> manage DNS server - so I need to extend it.
>> Stephen suggested:
>> - run BIND as DNS server
>> - add config file to each test for DNS server (mostly it will be the
>> same very simple config)
>>
>> That is the easiest, fastest method, in this case we need just basic
>> DNS managing. Generally that is all we need to perform DDNS testing.
>>
>> What I proposed was:
>> - extend Forge for dynamic building DNS config files (for now just for
>> BIND)
>> - add module to manage BIND in the same way it is done for Kea,
>> ISC-DHCP or Dibbler.
>> - add module that will handle managing two servers at the same time
>> (now we can run only one)
>>
>> That is more work and more time. We gain only ability to run DDNS test
>> with different DNS server, what is not so important to do the DDNS
>> testing itself. But that isn't point of Forge to make generic tests?
>> Another thing is that I have on a list 'extend Forge with DNS tests' I
>> could make preparations for DNS testing and just write tests some time
>> after.
>>
>> What do you think? I would really like have some input from you guys.
>>
>> Thank you very much,
>> W?odek
>> _______________________________________________
>> kea-dev mailing list
>> [email protected]
>> https://lists.isc.org/mailman/listinfo/kea-dev
> I'm assuming you mean BIND9? I can tarball up what I did for my manual
> testing using BIND9. It might give you a leg up or at least some
> ideas. For each DNS server instance I wanted, I created a directory
> tree which housed its configuration files and db files, and then wrote a
> script that let me start, stop, reload configuration, reset database for
> a given DNS server. Made things pretty easy. If you're not familiar
> with rndc (BIND9's remote control program) you should read up on it.
>
You also may want to note that you can run multiple copies of Bind9 in one
machine
using different addresses. You don't need to have a separate VM for each bind
instance you want.
> _______________________________________________
> kea-dev mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/kea-dev
------------------------------
Message: 4
Date: Fri, 06 Jun 2014 13:33:26 +0200
From: Tomek Mrugalski <[email protected]>
To: [email protected]
Subject: Re: DDNS testing
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8
On 06/06/14 03:15, Shawn Routhier wrote:
>
> On Jun 5, 2014, at 7:53 AM, Thomas Markwalder wrote:
>
>> On 6/5/14, 4:27 AM, wlodek wrote:
>>> Hello,
>>> I need to bring one subject to discussion. DDNS testing framework.
>>>
>>> 1. It will be done by extending Forge
>>>
>>> 2. Tests will be run on whole system not just D2 server. We need to
>>> set up:
>>> - DHCP (for v4 and v6 will be separate tests)
>>> - DDNS server
>>> - DNS server
>>>
>>> 3. Extended tests will be for:
>>> - multiple DNS servers running
>>> - DHCPv4 and DHCPv6 working at the same time.
>
> remember that this requires the clients to do the right
> thing with the duid / clientid if you want them to share
> a name.
Wlodek's tests ARE the clients. The plan here is to use ISC Forge to
simulate both DHCPv4 and DHCPv6 clients. The tests can do that
separately. The current work here is to do that for both families at the
same time. At least that's how I understand the plan.
Tomek
------------------------------
_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev
End of kea-dev Digest, Vol 3, Issue 1
*************************************
