OpenIndiana/OpenSolaris/Solaris 11 IPS Package Support

Removing 'Triaged' bit so ticket gets picked up in next triage pass.

this patch needs to be reworked for whyrun support in 10.14

also, i think solaris 11 needs to default to IPS

What are you referring to by 10.14? There's no OpenIndiana release by that number.

Chef 10.14.0, the upcoming release with whyrun.
On Jul 26, 2012 6:57 PM, "Jason J. W. Williams (JIRA)" <
oss-tickets@opscode.com> wrote:

>
> [
> http://tickets.opscode.com/browse/CHEF-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25634#comment-25634]
>
> Jason J. W. Williams commented on CHEF-2496:
> --------------------------------------------
>
> What are you referring to by 10.14? There's no OpenIndiana release by that
> number.
>
> > OpenIndiana/OpenSolaris/Solaris 11 IPS Package Support
> > ------------------------------------------------------
> >
> > Key: CHEF-2496
> > URL: http://tickets.opscode.com/browse/CHEF-2496
> > Project: Chef
> > Issue Type: Improvement
> > Components: Packages
> > Environment: Solaris (OpenIndiana b151)
> > Reporter: Jason J. W. Williams
> > Assignee: Jason J. W. Williams
> > Priority: Major
> > Labels: ipsopenindiana, opensolaris, package, solaris
> >
> > Integrate provider for the IPS package system used in OpenSolaris,
> OpenIndiana and Solaris 11. This branch on Github enhances Chef to support
> the IPS system when using the 'package' Chef resource and defaults
> OpenSolaris and OpenIndiana to using IPS:
> https://github.com/williamsjj/chef/tree/ips_packaging_support
>
> –
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>

Jason, I'm working on porting your IPS patch to 10.14 here:

https://github.com/opscode/chef/tree/CHEF-2496

This is very WIP right now.

Made a couple changes, will merge shortly.

Whyrun:

btm@btmsol:~/chef/chef/pkg$ sudo chef-client --why-run
Password: 
[2012-08-01T14:55:04+00:00] WARN: Forcing formatter of 'doc' to capture whyrun output.
Starting Chef Client, version 10.14.0.beta.2
[2012-08-01T14:55:04+00:00] INFO: *** Chef 10.14.0.beta.2 ***
[2012-08-01T14:55:08+00:00] INFO: Run List is [recipe[soltest]]
[2012-08-01T14:55:08+00:00] INFO: Run List expands to [soltest]
[2012-08-01T14:55:08+00:00] INFO: Starting Chef Run for btmsol
[2012-08-01T14:55:08+00:00] INFO: Running start handlers
[2012-08-01T14:55:08+00:00] INFO: Start handlers complete.
resolving cookbooks for run list: ["soltest"]
[2012-08-01T14:55:10+00:00] INFO: Loading cookbooks [soltest]
Synchronizing Cookbooks:
[2012-08-01T14:55:11+00:00] INFO: Storing updated cookbooks/soltest/recipes/default.rb in the cache.
  - soltest
Compiling Cookbooks...
Converging 2 resources
Recipe: soltest::default
  * package[crypto/gnupg] action install[2012-08-01T14:55:11+00:00] INFO: Processing package[crypto/gnupg] action install (soltest::default line 16)
 (up to date)
  * package[crypto/gnupg] action remove[2012-08-01T14:55:12+00:00] INFO: Processing package[crypto/gnupg] action remove (soltest::default line 18)

    - Would remove  package crypto/gnupg
[2012-08-01T14:55:14+00:00] WARN: In whyrun mode, so NOT performing node save.
[2012-08-01T14:55:14+00:00] INFO: Chef Run complete in 5.159104 seconds
[2012-08-01T14:55:14+00:00] INFO: Running report handlers
[2012-08-01T14:55:14+00:00] INFO: Report handlers complete
Chef Client finished, 1 resources updated

package removal / installation (already installed). Note that installing takes can take a while and you don't get the output so have patience.

btm@btmsol:~/chef/chef/pkg$ sudo chef-client 
[2012-08-01T14:55:23+00:00] INFO: *** Chef 10.14.0.beta.2 ***
[2012-08-01T14:55:26+00:00] INFO: Run List is [recipe[soltest]]
[2012-08-01T14:55:26+00:00] INFO: Run List expands to [soltest]
[2012-08-01T14:55:26+00:00] INFO: Starting Chef Run for btmsol
[2012-08-01T14:55:26+00:00] INFO: Running start handlers
[2012-08-01T14:55:26+00:00] INFO: Start handlers complete.
[2012-08-01T14:55:27+00:00] INFO: Loading cookbooks [soltest]
[2012-08-01T14:55:27+00:00] INFO: Processing package[crypto/gnupg] action install (soltest::default line 16)
[2012-08-01T14:55:28+00:00] INFO: Processing package[crypto/gnupg] action remove (soltest::default line 18)
[2012-08-01T14:56:26+00:00] INFO: package[crypto/gnupg] removed
[2012-08-01T14:56:30+00:00] INFO: Chef Run complete in 63.705647 seconds
[2012-08-01T14:56:30+00:00] INFO: Running report handlers
[2012-08-01T14:56:30+00:00] INFO: Report handlers complete

merged to master, still needs tests.

base tests added, all in master.

Is there still a separate branch for this changeset?

no, I merged to topic branch in with the working provider so it would be immediately available for other people working on Solaris at Opscode. The tests are subsequent commits to master.

Reopening, couple things.

1. OmniOS also uses IPS, and it should be the default package provider for that platform. I opened CHEF-3359 for this.

2. Generally we don't automatically accept license agreements, and I think a resource attribute should be added to accept licenses, and should default to false, so the user implementing the resource in a recipe would have to know whether they accept the license.

Something else that needs addressing is how Chef deals with IPS creating a new boot environment when packages require it. When that happens all changes get written to the current/mounted BE as usual despite the new BE (missing the config file changes etc) being what will be active after reboot. We worked around this temporarily in the original patch by having a resource flag to suppress BE creation. Unfortunately, many IPS packages refuse to install if they can't create create a BE which breaks the Chef run.

Jason - can you provide a repeatable example of a package requiring a new BE, so we can test this, and allow for it?

Installing the "network/ssh" package will reliably create a new BE.

Any update on the status of this SNS?

Currently implementing accept license resource attribute. Can anyone recommend an obvious package which requires user intervention with respect to license?

Created test package which requires a license to be accepted.

Have implemented top level package resource attribute which allows licences to be accepted, and can be used by any provider which offers this functionality. Testing.

https://github.com/opscode/chef/compare/CHEF-2496_10

I'll modify this later to use an ips_package resource rather than adding the unique accept_license attribute to the default package resource.

merged accept_license fix to 10-stable, this now requires the use of the ips_package resource, e.g.

ips_package "lame-package" do
  action :install
  accept_license true
end