Updating from Version 0.2 to Version 1.0

If you've just upgraded from OKWS version 0.2 to version 1.0, you'll need to follow these brief directions on how to smooth the upgrade:

Though you scan still dump your config file in the old /etc/sfs/okws_config, OKWS1.0 and above prefer them in /usr/local/etc/okws/okws_config, and we recommend you put them there. The same goes for pub_config; we recommend the file location /usr/local/etc/okws/pub_config.

In OKWS 1.0, you can run Pub v1 or v2, or both at the same time; the approach is to have a separate publisher daemon running for each version of the Pub protocol. To run both Pub v1 and Pub v2, add a new line to tell OKWS how to find Pub v2:

  Pubd2ExecPath pubd -2 

Also, new OKWS wants to know what group to run OKWS services as. Something like this will do the trick:

  ServiceGroup www

Assuming the group www is defined on your system.

If you're upgrading your services from OKWS v0.2 to OKWS v1.0, you probably want to change the new publishing system. More details on that can be found here.

In particular, we recommend the following steps:

1. Change all instances of pub::include to pub2::run for publishing files.
2. Eliminate the virtual method init_publist. Instead, specialize the method oksrvc_t::post_launch_pub2. In that method, publish all needed configuration files via the pub2::run_cfg method, loading up the global pub2 object with the needed configuration parameters. Once the init_publist method has been elimanted, OKWS will guess that calls of the form (*srvc)[“foo”], where srvc is a pointer to an oksrvc_t object, should refer to the Pub v2 configuration, and not the Pub v1 configuration. For an example, see the service static.T in the OKWS distribution.
3. Change the return type of your oksrvc_t::make_newclnt calls from okclnt_t * to oksrvc_t::newclnt_t *. In OKWS 1.0, this is typdef'ed to be the same, but in OKWS 1.1, it will change.

As described in the Pub v2 documentation, every cluster running OKWS should have one instance of the treestat application running on its NFS server. It's safe to run treestat without any options to get reasonable behavior, as long as the default pub_config file points to the same HTDOCS root as the Web server is using.