ISC Open Source Projects issueshttps://gitlab.isc.org/groups/isc-projects/-/issues2023-07-13T20:45:26Zhttps://gitlab.isc.org/isc-projects/kea-quick-config/-/issues/24fix misspellings2023-07-13T20:45:26ZDarren Ankneyfix misspellingsSee Basic options step. Secondary and globally are misspelled on that page.See Basic options step. Secondary and globally are misspelled on that page.0.1https://gitlab.isc.org/isc-projects/kea-quick-config/-/issues/23what does this do?2023-07-13T20:48:11ZDarren Ankneywhat does this do?0.1https://gitlab.isc.org/isc-projects/kea-quick-config/-/issues/22Add release notes2023-07-13T20:14:09ZDarren AnkneyAdd release notesFor now, it will be kept simple. Release notes will be in an html file that has a pre section with the actual release notes that are handcrafted. If there is some further collaboration with others in the future, this may not be the mos...For now, it will be kept simple. Release notes will be in an html file that has a pre section with the actual release notes that are handcrafted. If there is some further collaboration with others in the future, this may not be the most appropriate going forward. Will worry about that later :smile:
Add a link to this release notes (target=_new) in the opening page where the type is chosen.
Maybe at the bottom, instead, in a small div that is just ALWAYS at the bottom that contains version number and the link? That seems most reasonable. Tucked away, out of the way.0.1Darren AnkneyDarren Ankneyhttps://gitlab.isc.org/isc-projects/kea-quick-config/-/issues/21Add ARM links to each input field2023-07-25T20:02:57ZDarren AnkneyAdd ARM links to each input fieldThe examples were moved inside the input fields (see: https://gitlab.isc.org/isc-private/kea-quick-config/-/issues/9 as a prerequisite to this ticket). Now we can put ARM links directly to an area that explains the field.The examples were moved inside the input fields (see: https://gitlab.isc.org/isc-private/kea-quick-config/-/issues/9 as a prerequisite to this ticket). Now we can put ARM links directly to an area that explains the field.0.1Darren AnkneyDarren Ankneyhttps://gitlab.isc.org/isc-projects/kea-quick-config/-/issues/20Add support for kea-dhcp6 configuration generation2023-08-02T11:17:07ZDarren AnkneyAdd support for kea-dhcp6 configuration generationCurrently, only `kea-dhcp4` configurations can be generated. This is a stub ticket that will track adding support for `kea-dhcp6` in this milestone. Many tickets will be needed probably as there are several concerns. A partial list of ...Currently, only `kea-dhcp4` configurations can be generated. This is a stub ticket that will track adding support for `kea-dhcp6` in this milestone. Many tickets will be needed probably as there are several concerns. A partial list of the concerns follows.
- Subnets will need different fields shown
- Some validation will need to change based on type chosen (the validation should return an error if `kea-dhcp6` isn't supported)
- `interfaces-config` will need different validation depending on type
- The logging configuration will need to change in some way depending on typehttps://gitlab.isc.org/isc-projects/kea-quick-config/-/issues/19Expanded interfaces-config validation2023-08-02T11:16:58ZDarren AnkneyExpanded interfaces-config validationExpand the `interfaces-config` validation to allow matching of more interfaces. Especially this will be needed for `kea-dhcp6` support. See the ARM for the `interfaces-config` that are allowed. Separate pattern matching may be needed ...Expand the `interfaces-config` validation to allow matching of more interfaces. Especially this will be needed for `kea-dhcp6` support. See the ARM for the `interfaces-config` that are allowed. Separate pattern matching may be needed between `kea-dhcp4` and `kea-dhcp6`.https://gitlab.isc.org/isc-projects/kea-quick-config/-/issues/18Add hook support2023-08-02T11:16:50ZDarren AnkneyAdd hook supportAdd support for hooks in the configuration. Some restrictions:
- Only the open source hooks
- With the exception of HA, if the hook requires additional information, don't include.
- Use a checklist to enable the desired hooks
- Gather t...Add support for hooks in the configuration. Some restrictions:
- Only the open source hooks
- With the exception of HA, if the hook requires additional information, don't include.
- Use a checklist to enable the desired hooks
- Gather the file location of the hooks libraries (probably need some simple `find` instructions here)
- HA hook will need gathering of additional parametershttps://gitlab.isc.org/isc-projects/kea-quick-config/-/issues/17High Availability support2023-08-02T11:16:42ZDarren AnkneyHigh Availability supportAdd support for a simple HA configuration. Explain that the entire Kea configuration should be the same on both servers with the exception of `"this-server-name"`. Just gather some information, don't allow complicated configurations. ...Add support for a simple HA configuration. Explain that the entire Kea configuration should be the same on both servers with the exception of `"this-server-name"`. Just gather some information, don't allow complicated configurations. Only allow hot-standby mode for simplicity.https://gitlab.isc.org/isc-projects/kea-quick-config/-/issues/16Add Options support2023-12-01T18:08:40ZDarren AnkneyAdd Options supportShould be available at:
- global level
- subnet level
- in reservations
- in classes
These should be from a select list as we don't want to get into custom options and other complicated areas.Should be available at:
- global level
- subnet level
- in reservations
- in classes
These should be from a select list as we don't want to get into custom options and other complicated areas.0.3Darren AnkneyDarren Ankneyhttps://gitlab.isc.org/isc-projects/kea/-/issues/2979RAI based flex-id reservations2024-03-27T12:56:42ZPeter DaviesRAI based flex-id reservationsRAI based flex-id reservations:
When providing dhcp services for customer equipment, maintaining a consistent IP
address is often desired even when customers replace their equipment.
Host reservations may be defined using a ...RAI based flex-id reservations:
When providing dhcp services for customer equipment, maintaining a consistent IP
address is often desired even when customers replace their equipment.
Host reservations may be defined using a flex-id host identifier based on some
RAI options; however, the lease data will typically contain the hw-address as
the identifier.
This works well until the customer replaces his equipment and there is an active
lease on the reserved address with the old client's hw-address. In this case,
Kea will regard this as an address conflict.
Enabling the "replace-client-id" flex-id flag can mitigate this; however, changing
the value of this flag on a running Kea server will cause address conflicts.
Is there a way to address this problem?
[RT #20140](https://support.isc.org/Ticket/Display.html?id=20140)kea2.5.8https://gitlab.isc.org/isc-projects/kea-quick-config/-/issues/15Add reservations support2023-12-21T19:31:22ZDarren AnkneyAdd reservations supportAdd the possibility to add global reservations WITH NO IP address assignment. Add possibility to configure subnet level reservations WITH IP address assignment. include ability to specify client classes.Add the possibility to add global reservations WITH NO IP address assignment. Add possibility to configure subnet level reservations WITH IP address assignment. include ability to specify client classes.0.3Darren AnkneyDarren Ankneyhttps://gitlab.isc.org/isc-projects/kea-quick-config/-/issues/14Add client-classes support2023-12-12T21:48:58ZDarren AnkneyAdd client-classes supportCurrently there is no support for client-classes. Add such at that global and subnet level. Include the possibility of adding client-classes requirement to the pool(s) as that will be a somewhat common thing. Also need to add the poss...Currently there is no support for client-classes. Add such at that global and subnet level. Include the possibility of adding client-classes requirement to the pool(s) as that will be a somewhat common thing. Also need to add the possibility of selecting some client classes to become a member of in a host reservation.0.3Darren AnkneyDarren Ankneyhttps://gitlab.isc.org/isc-projects/kea-quick-config/-/issues/13Valid lifetime configuration2023-11-17T20:01:52ZDarren AnkneyValid lifetime configurationAdd ability to configure valid-lifetime both in global and at subnet level. There should be some lease time related global options set to true (calculate-tee-times if it doesn't already default true) possibly.Add ability to configure valid-lifetime both in global and at subnet level. There should be some lease time related global options set to true (calculate-tee-times if it doesn't already default true) possibly.https://gitlab.isc.org/isc-projects/kea-quick-config/-/issues/12Create kea-ctrl-agent configuration2023-08-02T15:08:02ZDarren AnkneyCreate kea-ctrl-agent configurationGather necessary details for use in kea-ctrl-agent configuration. This could be tricky as `Control Socket:` for both `kea-dhcp4` and `kea-dhcp6` config files will be needed. These files are / will be created separately which could intr...Gather necessary details for use in kea-ctrl-agent configuration. This could be tricky as `Control Socket:` for both `kea-dhcp4` and `kea-dhcp6` config files will be needed. These files are / will be created separately which could introduce the possibility of user-error.https://gitlab.isc.org/isc-projects/kea-quick-config/-/issues/11Split javascript functions into separate javascript files2023-07-17T20:44:38ZDarren AnkneySplit javascript functions into separate javascript filesThis would make the javascript easier to work on as multiple functions could be viewed simultaneously. It would make the storage of the page a little more cumbersome as there would be multiple files. Probably would want to put these fi...This would make the javascript easier to work on as multiple functions could be viewed simultaneously. It would make the storage of the page a little more cumbersome as there would be multiple files. Probably would want to put these files in a subdirectory called 'javascript' in public_html so they could be loaded like this:
```
<script src="javascript/WriteItem.js"></script>
<script src="javascript/ReadItem.js"></script>
<script src="javascript/DelItem.js"></script>
```
etc...0.1Darren AnkneyDarren Ankneyhttps://gitlab.isc.org/isc-projects/kea-quick-config/-/issues/10remove PHP from the project2023-07-12T20:08:35ZDarren Ankneyremove PHP from the projectre-implement the validation of the steps (and associated helper functions) in javascript so that PHP will not be required for the project. As a side effect, a web server would no longer be required for the project to work.re-implement the validation of the steps (and associated helper functions) in javascript so that PHP will not be required for the project. As a side effect, a web server would no longer be required for the project to work.futurehttps://gitlab.isc.org/isc-projects/kea-quick-config/-/issues/9Move examples inside of the input fields2023-07-18T19:06:53ZDarren AnkneyMove examples inside of the input fieldsShow examples inside the input fields instead of next to the fields as it is now. Leave the third column of the tables, however, as it will be reused for another purpose in another ticket.Show examples inside the input fields instead of next to the fields as it is now. Leave the third column of the tables, however, as it will be reused for another purpose in another ticket.0.1Darren AnkneyDarren Ankneyhttps://gitlab.isc.org/isc-projects/kea-quick-config/-/issues/8Mark required fields with a *2023-07-18T14:20:24ZDarren AnkneyMark required fields with a *This is mostly a normal convention that web sites usually use. Required fields are marked with a * directly following the field. Currently, the required fields aren't marked at all and the optional field have a huge OPTIONAL. Remove th...This is mostly a normal convention that web sites usually use. Required fields are marked with a * directly following the field. Currently, the required fields aren't marked at all and the optional field have a huge OPTIONAL. Remove the OPTIONAL as well.0.1Darren AnkneyDarren Ankneyhttps://gitlab.isc.org/isc-projects/kea-quick-config/-/issues/7Add a confirmation dialog on press of "Start Over"2023-07-25T18:51:36ZDarren AnkneyAdd a confirmation dialog on press of "Start Over"Currently, when clicking "Start Over", it just happily erases all of your content and takes you back to the beginning. Someone could accidentally click that and lose all of their work. Show some kind of confirmation dialog (js popup? h...Currently, when clicking "Start Over", it just happily erases all of your content and takes you back to the beginning. Someone could accidentally click that and lose all of their work. Show some kind of confirmation dialog (js popup? hidden div?) when the button is clicked.0.1Darren AnkneyDarren Ankneyhttps://gitlab.isc.org/isc-projects/kea-quick-config/-/issues/6Make buttons appear in a series of absolute position divs2023-07-20T17:05:26ZDarren AnkneyMake buttons appear in a series of absolute position divsCurrently the buttons flop all over the place as different divs are shown as the content of the divs shown is only one linear html page. Best to split this up into divs with absolute positions or sizes so that scroll bars will appear fo...Currently the buttons flop all over the place as different divs are shown as the content of the divs shown is only one linear html page. Best to split this up into divs with absolute positions or sizes so that scroll bars will appear for the forms and so on and the navigation buttons themselves don't move.0.1Darren AnkneyDarren Ankney