Re: [wpkg-users] deploy to a pilot group first?

2008-09-23 Thread Falko Trojahn
Hello Kent,

Kent Tong wrote:
 However, I'd like to deploy it to pilot group first. To avoid deploying to
 all users,
 I can't modify the existing package. It means I have to create a new
 package.
 If they have the same package id, then it will confuse wpkg, right? If they
 have
 different package ids, then wpkg will execute the install command instead of
 the upgrade command.
   
Yes. You could do the following

- replace the check,  upgrade and remove commands from the existing
package mypackage by e.g.
check type=file condition=exists
path=%SystemDrive%\netinst\logs\acrobat7.txt  /
upgrade cmd='cmd /c echo ok
%SystemDrive%\netinst\logs\acrobat7.txt ' 
  exit code=any /
/upgrade
remove cmd='cmd /c del /q
%SystemDrive%\netinst\logs\acrobat7.txt ' 
  exit code=any /
/remove
  (so the software is not changed in any way when upgrading/removing the
package)

- increase the revision number, so nothing on the existing clients is
changed, only the text file will be created/removed

- create a new, at least identical package, say mypackage2; assign it
to the test group, remove mypackage from the same group

- up to this point, nothing has changed to the clients but the text file
and the contents of wpkg.xml

- change the check/install/upgrade/remove entries in mypackage2 and
test that at the test group

- when you are satisfied with your package, remove the assignment of
mypackage and assign mypackage2 to the target group
 An approach to this problem is to let different groups see a different set
 of available 
 packages, then the problem will be solved.

 Is there any way to do it? 
   
Yes. You can set base as parameter or in config.xml, see
http://wpkg.org/WPKG_flags#Optional_parameters
But IMHO you would need a copy of your software repository, then.

Best regards,
Falko


-
wpkg-users mailing list archives  http://lists.wpkg.org/pipermail/wpkg-users/
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users


Re: [wpkg-users] deploy to a pilot group first?

2008-09-23 Thread Kent Tong


Falko Trojahn-2 wrote:
 
 - increase the revision number, so nothing on the existing clients is
 changed, only the text file will be created/removed
 
 - create a new, at least identical package, say mypackage2; assign it
 to the test group, remove mypackage from the same group
 

Hi Falko,

Thanks for your reply! Take the mypackage2 as an example, will it use
the same package id as mypackage?



-
--
Kent Tong
Wicket tutorials freely available at http://www.agileskills2.org/EWDW
Axis2 tutorials freely available at http://www.agileskills2.org/DWSAA
-- 
View this message in context: 
http://www.nabble.com/deploy-to-a-pilot-group-first--tp19620583p19622617.html
Sent from the WPKG - Users mailing list archive at Nabble.com.

-
wpkg-users mailing list archives  http://lists.wpkg.org/pipermail/wpkg-users/
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users


Re: [wpkg-users] deploy to a pilot group first?

2008-09-23 Thread mscdex
Why not just create a new profile (called pilot or something) that
contains the package to test, and then in your hosts.xml add this new
profile to selected hosts that are to pilot the new package. You would still
have to create a separate package entry with a unique id of course, but
that's the way I would go about it.

On 9/23/08, Kent Tong [EMAIL PROTECTED] wrote:



 Falko Trojahn-2 wrote:
 
  - increase the revision number, so nothing on the existing clients is
  changed, only the text file will be created/removed
 
  - create a new, at least identical package, say mypackage2; assign it
  to the test group, remove mypackage from the same group
 


 Hi Falko,

 Thanks for your reply! Take the mypackage2 as an example, will it use
 the same package id as mypackage?




 -
 --
 Kent Tong
 Wicket tutorials freely available at http://www.agileskills2.org/EWDW
 Axis2 tutorials freely available at http://www.agileskills2.org/DWSAA
 --

 View this message in context:
 http://www.nabble.com/deploy-to-a-pilot-group-first--tp19620583p19622617.html

 Sent from the WPKG - Users mailing list archive at Nabble.com.

 -

 wpkg-users mailing list archives 
 http://lists.wpkg.org/pipermail/wpkg-users/
 ___
 wpkg-users mailing list
 wpkg-users@lists.wpkg.org
 http://lists.wpkg.org/mailman/listinfo/wpkg-users

-
wpkg-users mailing list archives  http://lists.wpkg.org/pipermail/wpkg-users/
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users


Re: [wpkg-users] deploy to a pilot group first?

2008-09-23 Thread Falko Trojahn
Hi,

first: please don't top post / full quote, thank you.

mscdex wrote:
 Why not just create a new profile (called pilot or something) that
 contains the package to test, and then in your hosts.xml add this new
 profile to selected hosts that are to pilot the new package. You would
 still have to create a separate package entry with a unique id of
 course, but that's the way I would go about it.
At least after installation of the new package the old package would
fail it's check(s), reinstall the older software,
even possible that after this the newer package would remove/upgrade the
older software ... nice loop.

Best regards,
Falko
-
wpkg-users mailing list archives  http://lists.wpkg.org/pipermail/wpkg-users/
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users


Re: [wpkg-users] deploy to a pilot group first?

2008-09-23 Thread Marco Gaiarin
Mandi! Kent Tong
  In chel di` si favelave...

 Is there any way to do it? 

Apart what yust sayed, no.

If the 'testbed' are to little and phisically near you, normally i
modify the package but not the revision of, then i:

1) test the upgrade editing C:\WINDOWS\SYSTEM32\WPKG.XML and
 subtracting 1 to the revision of that package, so an upgrade
are forced.

2) test install/remove by adding/removing package from the profile
 (this is a bit easy)

clearly using a 'scatch' profile.


Some time ago i've asked for a feature, eg like in modern package
management system, to 'pinpoint' a package with a specific revision to
a profile, eg:

profile id=ced
depends profile-id=default /

package package-id=whfc revision=124/
/profile

I think this is a good solution for this problem.

-- 
dott. Marco Gaiarin GNUPG Key ID: 240A3D66
  Associazione ``La Nostra Famiglia''http://www.sv.lnf.it/
  Polo FVG  -  Via della Bontà, 7 - 33078  -  San Vito al Tagliamento (PN)
  marco.gaiarin(at)sv.lnf.it  tel +39-0434-842711  fax +39-0434-842797

Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA!
   http://www.lanostrafamiglia.it/chi_siamo/5xmille.php
(cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA)
-
wpkg-users mailing list archives  http://lists.wpkg.org/pipermail/wpkg-users/
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users


Re: [wpkg-users] deploy to a pilot group first?

2008-09-23 Thread Kent Tong

Hi all,

Thanks for all the suggestions! I think pinpointing is the way to go while
the
rest can serve as effective workaround for the moment. Going to file an
feature request...

-
--
Kent Tong
Wicket tutorials freely available at http://www.agileskills2.org/EWDW
Axis2 tutorials freely available at http://www.agileskills2.org/DWSAA
-- 
View this message in context: 
http://www.nabble.com/deploy-to-a-pilot-group-first--tp19620583p19624852.html
Sent from the WPKG - Users mailing list archive at Nabble.com.

-
wpkg-users mailing list archives  http://lists.wpkg.org/pipermail/wpkg-users/
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users


[wpkg-users] deploy to a pilot group first?

2008-09-22 Thread Kent Tong

Hi,

Suppose that there is an existing package which now has a new version,
assuming
that it can perform an in-place upgrade, it is easy to deploy the new
version 
with wpkg: just modify the revision attribute and the install and upgrade
commands.

However, I'd like to deploy it to pilot group first. To avoid deploying to
all users,
I can't modify the existing package. It means I have to create a new
package.
If they have the same package id, then it will confuse wpkg, right? If they
have
different package ids, then wpkg will execute the install command instead of
the upgrade command.

An approach to this problem is to let different groups see a different set
of available 
packages, then the problem will be solved.

Is there any way to do it? 

Thanks!

-
--
Kent Tong
Wicket tutorials freely available at http://www.agileskills2.org/EWDW
Axis2 tutorials freely available at http://www.agileskills2.org/DWSAA
-- 
View this message in context: 
http://www.nabble.com/deploy-to-a-pilot-group-first--tp19620583p19620583.html
Sent from the WPKG - Users mailing list archive at Nabble.com.

-
wpkg-users mailing list archives  http://lists.wpkg.org/pipermail/wpkg-users/
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users