diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2014-07-2014-09.xml b/en_US.ISO8859-1/htdocs/news/status/report-2014-07-2014-09.xml index 8a64b31738..44e2ef4fd7 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2014-07-2014-09.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2014-07-2014-09.xml @@ -105,22 +105,21 @@ -

Deficiencies in the current automounter, amd(8), are a +

Deficiencies in the current automounter, amd(8), are a recurring problem reported by many FreeBSD users. A new - automounter is being developed to address these concerns. + automounter is being developed to address these concerns.

- The automounter is a cleanroom implementation of +

The automounter is a cleanroom implementation of functionality available in most other Unix systems, using proper kernel support implemented via an autofs filesystem. The automounter supports a standard map format, and will integrate with the Lightweight Directory Access Protocol - (LDAP) service. + (LDAP) service.

- The code is ready to use - it has been committed to 11-CURRENT +

The code is ready to use - it has been committed to 11-CURRENT and 10-STABLE, and will ship as part of 10.1-RELEASE. There is ongoing work on improving performance and fixing possible - bugs. -

+ bugs.

@@ -159,17 +158,16 @@ released in FreeBSD 10.0, Chelsio Communications has begun developing an offload interface to take advantage of the hardware offload capabilities of Chelsio T4 and T5 10 and 40 - gigabit Ethernet adapters. + gigabit Ethernet adapters.

- The code implements hardware PDU offload for both target and +

The code implements hardware PDU offload for both target and initiator. The iSCSI stack has been modified to provide hardware-independent offload API, allowing offload drivers to be loaded as kernel modules, and to provide mechanisms for the system administrator to configure this feature. The project is entering a testing phase. The code will be released under the BSD license and is expected to be completed later in the - year and ship in FreeBSD 10.2-RELEASE. -

+ year and ship in FreeBSD 10.2-RELEASE.

@@ -318,4 +316,221 @@ + + + ZFS Chapter of the Handbook + + + + + Allan + Jude + + + allanjude@FreeBSD.org + + + + + Benedict + Reuschling + + + bcr@FreeBSD.org + + + + + Warren + Block + + + wblock@FreeBSD.org + + + + + ZFS Section of the FreeBSD Handbook + + + +

ZFS is one of the premier features of FreeBSD and the quality + of the documentation should match that of other important + features. Much of the original documentation from Sun and + Oracle has disappeared, moved, or is about the proprietary + version of ZFS. The OpenZFS project does not provide much + documentation and instead provides users with a few links, + including the FreeBSD Handbook. New users have many questions + about ZFS and yet there exists a great deal more bad advice + about ZFS than proper documentation.

+ +

After over a year of work, a new ZFS chapter has been added + to the FreeBSD Handbook. Over 20,000 words describing the + basics of creating, managing and maintaining a ZFS pool, as + well as using some of the advanced features like compression, + deduplication, and delegation. The chapter also contains a + glossary of terms, explaining a number of the concepts unique + to ZFS. The chapter also includes documentation of some of + the many sysctl variables that can be used to tune ZFS.

+ +

The remaining work is the FAQ section. To help users address + the most common questions or problems they might face with + ZFS. It would be useful to hear experiences, questions, + misconceptions, gotchas, stumbling blocks and suggestions for + the FAQ section from other users. Also, a use cases section + that highlights some of the cases where ZFS provides + advantages over traditional file systems.

+ +

Please send suggestions to the docs mailing list.

+ + + ScaleEngine Inc. + + + Technical review by Matt Ahrens (co-creator of ZFS) + Improve delegation section + Improve tuning section, add recently added sysctls + Add section on jails and the jailed property + Add FAQ section + Add Use Cases section + General editing and review + + + + + Jenkins Continuous Integration for FreeBSD + + + + + Craig + Rodrigues + + rodrigc@FreeBSD.org + + + + Jenkins Administrators + jenkins-admin@FreeBSD.org + + + + &os; Testing + freebsd-testing@FreeBSD.org + + + + + Jenkins CI server in &os; cluster + Jenkins working group at DevSummit + Jenkins presentation at BSDCan + clang static analyzer + FreeBSD static analysis results + BSD Now episode 44 + livirt and bhyve" + Kyua testing framework + Issue to update Jenkins to JNA 4.1.0 for FreeBSD + Pull request #1 to upgrade JNA in Jenkins + Pull request #2 to upgrade JNA in Jenkins + Jenkins job for testing pkg + yacc bug found by kyua + IPv6 multicast join() problem found by Jenkins + Kyua Quickstart Guide + + + +

In May, &a.rodrigc; led a working group Continuous + Integration and Testing with Jenkins for FreeBSD at the + FreeBSD Devsummit in Ottawa. &a.rodrigc; also gave a Jenkins + presentation at BSDCan.

+ +

At BSDCan, &a.rodrigc; had some discussions with &a.jmmv; + about how to better integrate &os; testing efforts with + Jenkins and kyua. As a result of this discussion, &a.jmmv; + enhanced the kyua testing framework with a + kyua report-junit command. This command takes kyua + test results and outputs a test report in JUnit XML format. + Jenkins can directly import JUnit XML test results and display + them nicely.

+ +

In June, &a.rodrigc; was interviewed for episode 44 of BSD + Now. The interview covered Jenkins and Continuous Integration + in the &os; project.

+ +

In July, &a.rodrigc; gave a presentation to the Bay Area &os; + Users Group (BAFUG), Libvirt and bhyve, based on + experience he had with those technologies when used with + Jenkins.

+ +

&a.lwhsu; set up a Jenkins job to run the LLVM scan-build + tool to perform static analysis of the &os; code, and make the + results availalble at scan.freebsd.org.

+ +

&a.swills; modified the Jenkins job which builds + pkg(8) to use the kyua report-junit command + to integrate pkg(8) test results in Jenkins.

+ +

Anthony Williams reported that the version of the Java + Native Access (JNA) library bundled with Jenkins has problems + on &os;. This causes problems with Jenkins using libpam and + other plugins which use JNA. Craig filed JENKINS-24521 + against Jenkins. Craig submitted patches to Jenkins to update + Jenkins to use JNA 4.1.0, which has fixes for &os;. Github + pull request 1410 was accepted into Jenkins, while pull + request 1387 is pending.

+ +

&a.rodrigc; worked on automatically running the tests in the + &os; /usr/tests directory under Jenkins using the + kyua test framework. &a.rodrigc; provided feedback + to &a.jmmv; about kyua and &a.jmmv; incorporated some + of the feedback as bugfixes and feature enhancements to + kyua. &a.rodrigc; committed some fixes to &os; to + eliminate some test failures. One of the tests still results + in a crash in byacc. This is being tracked in PR 193499. + Thomas E. Dickey (byacc maintainer) submitted a patch to fix + the problem, and this has been committed to FreeBSD.

+ +

&a.rodrigc; analyzed the cause of some startup errors in + Jenkins when opening a multicast socket. He had some + discussion with &a.bms; captured in PR 193246. The Java JDK + depends on functionality in Solaris where it is possible to + open an IPv4 multicast socket, but with an IPv4 multicast + address mapped to an IPv6 address. On Linux, there are + modifications to the JDK itself to work around this. &a.bms; + said that the work to make the FreeBSD IPv6 stack behave like + Solaris would require some work.

+ +

&a.rodrigc; started writing a Kyua Quickstart Guide. This + guide is meant to help new kyua users who want to write tests + and run them under kyua. &a.rodrigc; is seeking feedback to + help improve this guide.

+ + + + + Upstream more fixes to Jenkins for FreeBSD, such as JNA fixes. + + + + Automate the build of /usr/tests. + + + + Set up more builds based on examples from the existing FreeBSD + Tinderbox. + + + + Get feedback for improving the Kyua Quickstart Guide. + + + + We need more people to join us on freebsd-testing@freebsd.org + and help out. We especially need people with devops and + scripting experience to help us set up more builds and tests. + We would also like to integrate with other parts of the + project, such as Phabricator. + + +