Puppet users - Oct 2008 - how to update solaris packages without keeping local copies

Greetings,

I have a solaris package stored on a puppet server.  I''d like
to be able to maintain the package on a client system without
having to also keep a copy of the package file on the client
system.  (think lots and lots of packages)

Checksums work okay for noticing changes on the fileserver,
but it seems that I have to keep a local copy of the file as well.

When I rev the package on the file server, the client should download
the package file, install package from the package file, then delete
the package file.

How have you solved this?

Thanks,

Richard.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

you could create a repository based on pkg-get binary (blastwave).

Cheers,
Ohad

On Thu, Oct 16, 2008 at 7:47 AM, Richard Doty <rad@twig.com> wrote:
>
> Greetings,
>
> I have a solaris package stored on a puppet server.  I''d like
> to be able to maintain the package on a client system without
> having to also keep a copy of the package file on the client
> system.  (think lots and lots of packages)
>
> Checksums work okay for noticing changes on the fileserver,
> but it seems that I have to keep a local copy of the file as well.
>
> When I rev the package on the file server, the client should download
> the package file, install package from the package file, then delete
> the package file.
>
> How have you solved this?
>
> Thanks,
>
> Richard.
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Richard,

On Oct 16, 1:47 am, Richard Doty <r...@twig.com>
wrote:
> I have a solaris package stored on a puppet server.  I''d like
> to be able to maintain the package on a client system without
> having to also keep a copy of the package file on the client
> system.  (think lots and lots of packages)
>
it is not very well known, but pkgadd can take an URL as dtastream,
i.e.
pkgadd -d http://yourserver.com/pkgs/SUNWxyz.pkg

I haven''t checked if puppet supports this, but it is worth
investigating :)

cheers,
/Martin
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Hi
> it is not very well known, but pkgadd can take an URL as dtastream,
> i.e.
> pkgadd -d http://yourserver.com/pkgs/SUNWxyz.pkg
> 
> I haven''t checked if puppet supports this, but it is worth
> investigating :)

for all other package providers I use, you can use the source param to
install packages from a specific location.

greets pete

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On Thu, Oct 16, 2008 at 3:41 AM, martin <martin.englund@sun.com>
wrote:
>
> Richard,
>
> On Oct 16, 1:47 am, Richard Doty <r...@twig.com> wrote:
>> I have a solaris package stored on a puppet server.  I''d like
>> to be able to maintain the package on a client system without
>> having to also keep a copy of the package file on the client
>> system.  (think lots and lots of packages)
>>
> it is not very well known, but pkgadd can take an URL as dtastream,
> i.e.
> pkgadd -d http://yourserver.com/pkgs/SUNWxyz.pkg
>
> I haven''t checked if puppet supports this, but it is worth
> investigating :)
Another quick point about this.. pkgadd isn''t smart enough to handle a
response file with packages installed this way.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Sam Rowe wrote:
> Another quick point about this.. pkgadd isn''t smart enough to
handle a
> response file with packages installed this way.
It will however use an admin file.

Here''s what I have for installing packages on Solaris systems:

define pkgadd {
        $pkgrepo="http://pca.itgasiapac.com/pkgs"
        package{"$name":
                source => "$pkgrepo/$name.pkg.$hardwareisa",
                ensure => installed,
                adminfile => "puppet",
                require => File["/var/sadm/install/admin/puppet"]
        }
}

My "base" define which gets pulled in for everything ensures that the
admin file is in the right place.  This is a full-auto admin file.  Then
I define packages I want installed thus:

  pkgadd{ITGlsof:}

The hitch is that I''m not sure that puppet is able to handle the
Solaris
package version info -- pkgadd itself doesn''t really either.  So this
doesn''t keep packages updated, merely installs them from the repository
if they''re not there.

What you *can* do, though, is have a sort of "temporary" define that
gets pulled in for all Solaris hosts, and when you update a package you
can explicitly pkgrm it there.  It should then get the updated version
installed.

A long way from perfect but if it''s happening during a maintenance
window then it isn''t *too* bad.

It ought to be possible to write a custom fact that enumerates all
package versions, though I think you''d want to be careful and either do
some caching or ignore anything starting with SUNW*.  It would probably
then be possible to write an improved ''pkgadd'' define that
also takes a
version number and automatically updates if the installed version is
older than the declared one.

Still not perfect but probably a whole lot better.

Matt


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---


++++++++++++++++++++++++++++++++++++++++++++++++
The information contained in this communication is strictly confidential and
intended solely for the use of the intended recipient(s). The copyright in this
communication belongs to ITG Australia Ltd, ITG Hong Kong Limited, ITG Japan
Limited, ITG Singapore Pte Ltd and/or their related entities, including
Investment Technology Group, Inc., (collectively referred to as “ITG") and
may contain information that is private, confidential or subject to legal
professional or other privilege.  No confidentiality or privilege is waived or
lost by any mis-transmission of this email.

Access to this email by anyone other than the intended recipient is unauthorized
and further distribution of this email is strictly prohibited without the
permission of ITG.  If you are not the intended recipient of this email, any
review, disclosure, copying, distribution, retention or any action taken or
omitted to be taken in reliance on it is prohibited and may be unlawful.  If you
are not the intended recipient of this email, you should not disseminate,
distribute or copy this e-mail and you should delete it and all copies of it
from your system, destroy any hard copies of it and notify the sender.  ITG
and/or its affiliates reserve the right to monitor and archive all electronic
communications through its/their network.

The information contained in this email is believed to be accurate at the time
of publication.  However, ITG disclaims all responsibility for any loss or
damage howsoever arising as a result of any person or entity acting upon the
information contained in this email and no liability will be accepted by ITG for
any such loss or damage.  Any views expressed in this email are those of the
individual sender, except where the email states otherwise and the sender is
authorized to state them to be the views of ITG.
++++++++++++++++++++++++++++++++++++++++++++++++

Why not to create your own blastwave repo to use pkg-get with, or am I
missing anything here?

Thanks,
Ohad

On Tue, Oct 28, 2008 at 8:41 AM, McLeod, Matt <Matt.McLeod@itg.com> wrote:
> Sam Rowe wrote:
> > Another quick point about this.. pkgadd isn''t smart enough to
handle a
> > response file with packages installed this way.
>
> It will however use an admin file.
>
> Here''s what I have for installing packages on Solaris systems:
>
> define pkgadd {
>        $pkgrepo="http://pca.itgasiapac.com/pkgs"
>        package{"$name":
>                source => "$pkgrepo/$name.pkg.$hardwareisa",
>                ensure => installed,
>                adminfile => "puppet",
>                require =>
File["/var/sadm/install/admin/puppet"]
>        }
> }
>
> My "base" define which gets pulled in for everything ensures that
the
> admin file is in the right place.  This is a full-auto admin file.  Then
> I define packages I want installed thus:
>
>  pkgadd{ITGlsof:}
>
> The hitch is that I''m not sure that puppet is able to handle the
Solaris
> package version info -- pkgadd itself doesn''t really either.  So
this
> doesn''t keep packages updated, merely installs them from the
repository
> if they''re not there.
>
> What you *can* do, though, is have a sort of "temporary" define
that
> gets pulled in for all Solaris hosts, and when you update a package you
> can explicitly pkgrm it there.  It should then get the updated version
> installed.
>
> A long way from perfect but if it''s happening during a maintenance
> window then it isn''t *too* bad.
>
> It ought to be possible to write a custom fact that enumerates all
> package versions, though I think you''d want to be careful and
either do
> some caching or ignore anything starting with SUNW*.  It would probably
> then be possible to write an improved ''pkgadd'' define
that also takes a
> version number and automatically updates if the installed version is
> older than the declared one.
>
> Still not perfect but probably a whole lot better.
>
> Matt
>
>
> >
>
> ++++++++++++++++++++++++++++++++++++++++++++++++
> The information contained in this communication is strictly confidential
> and intended solely for the use of the intended recipient(s). The copyright
> in this communication belongs to ITG Australia Ltd, ITG Hong Kong Limited,
> ITG Japan Limited, ITG Singapore Pte Ltd and/or their related entities,
> including Investment Technology Group, Inc., (collectively referred to as
> "ITG") and may contain information that is private, confidential
or subject
> to legal professional or other privilege.  No confidentiality or privilege
> is waived or lost by any mis-transmission of this email.
>
> Access to this email by anyone other than the intended recipient is
> unauthorized and further distribution of this email is strictly prohibited
> without the permission of ITG.  If you are not the intended recipient of
> this email, any review, disclosure, copying, distribution, retention or any
> action taken or omitted to be taken in reliance on it is prohibited and may
> be unlawful.  If you are not the intended recipient of this email, you
> should not disseminate, distribute or copy this e-mail and you should
delete
> it and all copies of it from your system, destroy any hard copies of it and
> notify the sender.  ITG and/or its affiliates reserve the right to monitor
> and archive all electronic communications through its/their network.
>
> The information contained in this email is believed to be accurate at the
> time of publication.  However, ITG disclaims all responsibility for any
loss
> or damage howsoever arising as a result of any person or entity acting upon
> the information contained in this email and no liability will be accepted
by
> ITG for any such loss or damage.  Any views expressed in this email are
> those of the individual sender, except where the email states otherwise and
> the sender is authorized to state them to be the views of ITG.
> ++++++++++++++++++++++++++++++++++++++++++++++++
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

In my case, because we''re not doing Blastwave packages, we''re
just doing
a few things we''ve built locally.  And because I hadn''t
thought of it.
:)

Do you need to actually install pkg-get and the Blastwave base to make
this work, or does Puppet natively handle the repo?

(Blastwave and friends tend to drag in dependencies that pollute our dev
environments so we can''t use them in most cases.)

Matt
> -----Original Message-----
> From: puppet-users@googlegroups.com
[mailto:puppet-users@googlegroups.com]
> On Behalf Of Ohad Levy
> Sent: Tuesday, 28 October 2008 1:09 PM
> To: puppet-users@googlegroups.com
> Subject: [Puppet Users] Re: how to update solaris packages without
keeping
> local copies
> 
> Why not to create your own blastwave repo to use pkg-get with, or am I
> missing anything here?
> 
> Thanks,
> Ohad
> 
> 
> On Tue, Oct 28, 2008 at 8:41 AM, McLeod, Matt <Matt.McLeod@itg.com>
wrote:
> 
> 
> 	Sam Rowe wrote:
> 	> Another quick point about this.. pkgadd isn''t smart enough
to
> handle a
> 	> response file with packages installed this way.
> 
> 
> 	It will however use an admin file.
> 
> 	Here''s what I have for installing packages on Solaris systems:
> 
> 	define pkgadd {
> 	       $pkgrepo="http://pca.itgasiapac.com/pkgs"
> 	       package{"$name":
> 	               source => "$pkgrepo/$name.pkg.$hardwareisa",
> 	               ensure => installed,
> 	               adminfile => "puppet",
> 	               require =>
File["/var/sadm/install/admin/puppet"]
> 	       }
> 	}
> 
> 	My "base" define which gets pulled in for everything ensures
that the
> 	admin file is in the right place.  This is a full-auto admin
file.
> Then
> 	I define packages I want installed thus:
> 
> 	 pkgadd{ITGlsof:}
> 
> 	The hitch is that I''m not sure that puppet is able to handle the
> Solaris
> 	package version info -- pkgadd itself doesn''t really either.  So
this
> 	doesn''t keep packages updated, merely installs them from the
> repository
> 	if they''re not there.
> 
> 	What you *can* do, though, is have a sort of "temporary" define
that
> 	gets pulled in for all Solaris hosts, and when you update a
package
> you
> 	can explicitly pkgrm it there.  It should then get the updated
> version
> 	installed.
> 
> 	A long way from perfect but if it''s happening during a
maintenance
> 	window then it isn''t *too* bad.
> 
> 	It ought to be possible to write a custom fact that enumerates
all
> 	package versions, though I think you''d want to be careful and
either
> do
> 	some caching or ignore anything starting with SUNW*.  It would
> probably
> 	then be possible to write an improved ''pkgadd'' define
that also
takes
> a
> 	version number and automatically updates if the installed
version is
> 	older than the declared one.
> 
> 	Still not perfect but probably a whole lot better.
> 
> 	Matt
> 
> 
> 
> 
> 
> 	++++++++++++++++++++++++++++++++++++++++++++++++
> 	The information contained in this communication is strictly
> confidential and intended solely for the use of the intended
recipient(s).
> The copyright in this communication belongs to ITG Australia Ltd, ITG
Hong
> Kong Limited, ITG Japan Limited, ITG Singapore Pte Ltd and/or their
> related entities, including Investment Technology Group, Inc.,
> (collectively referred to as "ITG") and may contain information
that
is
> private, confidential or subject to legal professional or other
privilege.
> No confidentiality or privilege is waived or lost by any
mis-transmission
> of this email.
> 
> 	Access to this email by anyone other than the intended recipient
is
> unauthorized and further distribution of this email is strictly
prohibited
> without the permission of ITG.  If you are not the intended recipient
of
> this email, any review, disclosure, copying, distribution, retention
or
> any action taken or omitted to be taken in reliance on it is
prohibited
> and may be unlawful.  If you are not the intended recipient of this
email,
> you should not disseminate, distribute or copy this e-mail and you
should
> delete it and all copies of it from your system, destroy any hard
copies
> of it and notify the sender.  ITG and/or its affiliates reserve the
right
> to monitor and archive all electronic communications through its/their
> network.
> 
> 	The information contained in this email is believed to be
accurate at
> the time of publication.  However, ITG disclaims all responsibility
for
> any loss or damage howsoever arising as a result of any person or
entity
> acting upon the information contained in this email and no liability
will
> be accepted by ITG for any such loss or damage.  Any views expressed
in
> this email are those of the individual sender, except where the email
> states otherwise and the sender is authorized to state them to be the
> views of ITG.
> 	++++++++++++++++++++++++++++++++++++++++++++++++
> 
> 
> 
> 
> 
> > 

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---


++++++++++++++++++++++++++++++++++++++++++++++++
The information contained in this communication is strictly confidential and
intended solely for the use of the intended recipient(s). The copyright in this
communication belongs to ITG Australia Ltd, ITG Hong Kong Limited, ITG Japan
Limited, ITG Singapore Pte Ltd and/or their related entities, including
Investment Technology Group, Inc., (collectively referred to as “ITG") and
may contain information that is private, confidential or subject to legal
professional or other privilege.  No confidentiality or privilege is waived or
lost by any mis-transmission of this email.

Access to this email by anyone other than the intended recipient is unauthorized
and further distribution of this email is strictly prohibited without the
permission of ITG.  If you are not the intended recipient of this email, any
review, disclosure, copying, distribution, retention or any action taken or
omitted to be taken in reliance on it is prohibited and may be unlawful.  If you
are not the intended recipient of this email, you should not disseminate,
distribute or copy this e-mail and you should delete it and all copies of it
from your system, destroy any hard copies of it and notify the sender.  ITG
and/or its affiliates reserve the right to monitor and archive all electronic
communications through its/their network.

The information contained in this email is believed to be accurate at the time
of publication.  However, ITG disclaims all responsibility for any loss or
damage howsoever arising as a result of any person or entity acting upon the
information contained in this email and no liability will be accepted by ITG for
any such loss or damage.  Any views expressed in this email are those of the
individual sender, except where the email states otherwise and the sender is
authorized to state them to be the views of ITG.
++++++++++++++++++++++++++++++++++++++++++++++++

hmm, you just need the pkg-get and wget binaries (or packages) and than
puppet will use the blastwave provider.
for the repo, it will used whatever defined in pkg-get.conf, in my case, we
a few different packages (blastwave, home made etc) which we put in our
"pkg-get repo",  allowing puppet do use blastwave to download them
I use the following  script <http://pastie.org/302029> to generate the
repo.

Cheers,
Ohad

On Tue, Oct 28, 2008 at 10:51 AM, McLeod, Matt <Matt.McLeod@itg.com>
wrote:
> In my case, because we''re not doing Blastwave packages,
we''re just doing
> a few things we''ve built locally.  And because I hadn''t
thought of it.
> :)
>
> Do you need to actually install pkg-get and the Blastwave base to make
> this work, or does Puppet natively handle the repo?
>
> (Blastwave and friends tend to drag in dependencies that pollute our dev
> environments so we can''t use them in most cases.)
>
> Matt
>
> > -----Original Message-----
> > From: puppet-users@googlegroups.com
> [mailto:puppet-users@googlegroups.com]
> > On Behalf Of Ohad Levy
> > Sent: Tuesday, 28 October 2008 1:09 PM
> > To: puppet-users@googlegroups.com
> > Subject: [Puppet Users] Re: how to update solaris packages without
> keeping
> > local copies
> >
> > Why not to create your own blastwave repo to use pkg-get with, or am I
> > missing anything here?
> >
> > Thanks,
> > Ohad
> >
> >
> > On Tue, Oct 28, 2008 at 8:41 AM, McLeod, Matt
<Matt.McLeod@itg.com>
> wrote:
> >
> >
> >       Sam Rowe wrote:
> >       > Another quick point about this.. pkgadd isn''t
smart enough to
> > handle a
> >       > response file with packages installed this way.
> >
> >
> >       It will however use an admin file.
> >
> >       Here''s what I have for installing packages on Solaris
systems:
> >
> >       define pkgadd {
> >              $pkgrepo="http://pca.itgasiapac.com/pkgs"
> >              package{"$name":
> >                      source =>
"$pkgrepo/$name.pkg.$hardwareisa",
> >                      ensure => installed,
> >                      adminfile => "puppet",
> >                      require =>
File["/var/sadm/install/admin/puppet"]
> >              }
> >       }
> >
> >       My "base" define which gets pulled in for everything
ensures
> that the
> >       admin file is in the right place.  This is a full-auto admin
> file.
> > Then
> >       I define packages I want installed thus:
> >
> >        pkgadd{ITGlsof:}
> >
> >       The hitch is that I''m not sure that puppet is able to
handle the
> > Solaris
> >       package version info -- pkgadd itself doesn''t really
either.  So
> this
> >       doesn''t keep packages updated, merely installs them
from the
> > repository
> >       if they''re not there.
> >
> >       What you *can* do, though, is have a sort of
"temporary" define
> that
> >       gets pulled in for all Solaris hosts, and when you update a
> package
> > you
> >       can explicitly pkgrm it there.  It should then get the updated
> > version
> >       installed.
> >
> >       A long way from perfect but if it''s happening during a
> maintenance
> >       window then it isn''t *too* bad.
> >
> >       It ought to be possible to write a custom fact that enumerates
> all
> >       package versions, though I think you''d want to be
careful and
> either
> > do
> >       some caching or ignore anything starting with SUNW*.  It would
> > probably
> >       then be possible to write an improved ''pkgadd''
define that also
> takes
> > a
> >       version number and automatically updates if the installed
> version is
> >       older than the declared one.
> >
> >       Still not perfect but probably a whole lot better.
> >
> >       Matt
> >
> >
> >
> >
> >
> >       ++++++++++++++++++++++++++++++++++++++++++++++++
> >       The information contained in this communication is strictly
> > confidential and intended solely for the use of the intended
> recipient(s).
> > The copyright in this communication belongs to ITG Australia Ltd, ITG
> Hong
> > Kong Limited, ITG Japan Limited, ITG Singapore Pte Ltd and/or their
> > related entities, including Investment Technology Group, Inc.,
> > (collectively referred to as "ITG") and may contain
information that
> is
> > private, confidential or subject to legal professional or other
> privilege.
> > No confidentiality or privilege is waived or lost by any
> mis-transmission
> > of this email.
> >
> >       Access to this email by anyone other than the intended recipient
> is
> > unauthorized and further distribution of this email is strictly
> prohibited
> > without the permission of ITG.  If you are not the intended recipient
> of
> > this email, any review, disclosure, copying, distribution, retention
> or
> > any action taken or omitted to be taken in reliance on it is
> prohibited
> > and may be unlawful.  If you are not the intended recipient of this
> email,
> > you should not disseminate, distribute or copy this e-mail and you
> should
> > delete it and all copies of it from your system, destroy any hard
> copies
> > of it and notify the sender.  ITG and/or its affiliates reserve the
> right
> > to monitor and archive all electronic communications through its/their
> > network.
> >
> >       The information contained in this email is believed to be
> accurate at
> > the time of publication.  However, ITG disclaims all responsibility
> for
> > any loss or damage howsoever arising as a result of any person or
> entity
> > acting upon the information contained in this email and no liability
> will
> > be accepted by ITG for any such loss or damage.  Any views expressed
> in
> > this email are those of the individual sender, except where the email
> > states otherwise and the sender is authorized to state them to be the
> > views of ITG.
> >       ++++++++++++++++++++++++++++++++++++++++++++++++
> >
> >
> >
> >
> >
> > >
>
>
> >
>
> ++++++++++++++++++++++++++++++++++++++++++++++++
> The information contained in this communication is strictly confidential
> and intended solely for the use of the intended recipient(s). The copyright
> in this communication belongs to ITG Australia Ltd, ITG Hong Kong Limited,
> ITG Japan Limited, ITG Singapore Pte Ltd and/or their related entities,
> including Investment Technology Group, Inc., (collectively referred to as
> "ITG") and may contain information that is private, confidential
or subject
> to legal professional or other privilege.  No confidentiality or privilege
> is waived or lost by any mis-transmission of this email.
>
> Access to this email by anyone other than the intended recipient is
> unauthorized and further distribution of this email is strictly prohibited
> without the permission of ITG.  If you are not the intended recipient of
> this email, any review, disclosure, copying, distribution, retention or any
> action taken or omitted to be taken in reliance on it is prohibited and may
> be unlawful.  If you are not the intended recipient of this email, you
> should not disseminate, distribute or copy this e-mail and you should
delete
> it and all copies of it from your system, destroy any hard copies of it and
> notify the sender.  ITG and/or its affiliates reserve the right to monitor
> and archive all electronic communications through its/their network.
>
> The information contained in this email is believed to be accurate at the
> time of publication.  However, ITG disclaims all responsibility for any
loss
> or damage howsoever arising as a result of any person or entity acting upon
> the information contained in this email and no liability will be accepted
by
> ITG for any such loss or damage.  Any views expressed in this email are
> those of the individual sender, except where the email states otherwise and
> the sender is authorized to state them to be the views of ITG.
> ++++++++++++++++++++++++++++++++++++++++++++++++
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Sorry, google striped the url, the script can be found here:
http://pastie.org/302029


On Tue, Oct 28, 2008 at 12:52 PM, Ohad Levy <ohadlevy@gmail.com> wrote:
> hmm, you just need the pkg-get and wget binaries (or packages) and than
> puppet will use the blastwave provider.
> for the repo, it will used whatever defined in pkg-get.conf, in my case, we
> a few different packages (blastwave, home made etc) which we put in our
> "pkg-get repo",  allowing puppet do use blastwave to download
them
> I use the following  script <http://pastie.org/302029> to generate
the
> repo.
>
> Cheers,
> Ohad
>
>
> On Tue, Oct 28, 2008 at 10:51 AM, McLeod, Matt
<Matt.McLeod@itg.com>wrote:
>
>> In my case, because we''re not doing Blastwave packages,
we''re just doing
>> a few things we''ve built locally.  And because I
hadn''t thought of it.
>> :)
>>
>> Do you need to actually install pkg-get and the Blastwave base to make
>> this work, or does Puppet natively handle the repo?
>>
>> (Blastwave and friends tend to drag in dependencies that pollute our
dev
>> environments so we can''t use them in most cases.)
>>
>> Matt
>>
>> > -----Original Message-----
>> > From: puppet-users@googlegroups.com
>> [mailto:puppet-users@googlegroups.com]
>> > On Behalf Of Ohad Levy
>> > Sent: Tuesday, 28 October 2008 1:09 PM
>> > To: puppet-users@googlegroups.com
>> > Subject: [Puppet Users] Re: how to update solaris packages without
>> keeping
>> > local copies
>> >
>> > Why not to create your own blastwave repo to use pkg-get with, or
am I
>> > missing anything here?
>> >
>> > Thanks,
>> > Ohad
>> >
>> >
>> > On Tue, Oct 28, 2008 at 8:41 AM, McLeod, Matt
<Matt.McLeod@itg.com>
>> wrote:
>> >
>> >
>> >       Sam Rowe wrote:
>> >       > Another quick point about this.. pkgadd isn''t
smart enough to
>> > handle a
>> >       > response file with packages installed this way.
>> >
>> >
>> >       It will however use an admin file.
>> >
>> >       Here''s what I have for installing packages on
Solaris systems:
>> >
>> >       define pkgadd {
>> >              $pkgrepo="http://pca.itgasiapac.com/pkgs"
>> >              package{"$name":
>> >                      source =>
"$pkgrepo/$name.pkg.$hardwareisa",
>> >                      ensure => installed,
>> >                      adminfile => "puppet",
>> >                      require =>
File["/var/sadm/install/admin/puppet"]
>> >              }
>> >       }
>> >
>> >       My "base" define which gets pulled in for
everything ensures
>> that the
>> >       admin file is in the right place.  This is a full-auto admin
>> file.
>> > Then
>> >       I define packages I want installed thus:
>> >
>> >        pkgadd{ITGlsof:}
>> >
>> >       The hitch is that I''m not sure that puppet is able
to handle the
>> > Solaris
>> >       package version info -- pkgadd itself doesn''t
really either.  So
>> this
>> >       doesn''t keep packages updated, merely installs them
from the
>> > repository
>> >       if they''re not there.
>> >
>> >       What you *can* do, though, is have a sort of
"temporary" define
>> that
>> >       gets pulled in for all Solaris hosts, and when you update a
>> package
>> > you
>> >       can explicitly pkgrm it there.  It should then get the
updated
>> > version
>> >       installed.
>> >
>> >       A long way from perfect but if it''s happening
during a
>> maintenance
>> >       window then it isn''t *too* bad.
>> >
>> >       It ought to be possible to write a custom fact that
enumerates
>> all
>> >       package versions, though I think you''d want to be
careful and
>> either
>> > do
>> >       some caching or ignore anything starting with SUNW*.  It
would
>> > probably
>> >       then be possible to write an improved
''pkgadd'' define that also
>> takes
>> > a
>> >       version number and automatically updates if the installed
>> version is
>> >       older than the declared one.
>> >
>> >       Still not perfect but probably a whole lot better.
>> >
>> >       Matt
>> >
>> >
>> >
>> >
>> >
>> >       ++++++++++++++++++++++++++++++++++++++++++++++++
>> >       The information contained in this communication is strictly
>> > confidential and intended solely for the use of the intended
>> recipient(s).
>> > The copyright in this communication belongs to ITG Australia Ltd,
ITG
>> Hong
>> > Kong Limited, ITG Japan Limited, ITG Singapore Pte Ltd and/or
their
>> > related entities, including Investment Technology Group, Inc.,
>> > (collectively referred to as "ITG") and may contain
information that
>> is
>> > private, confidential or subject to legal professional or other
>> privilege.
>> > No confidentiality or privilege is waived or lost by any
>> mis-transmission
>> > of this email.
>> >
>> >       Access to this email by anyone other than the intended
recipient
>> is
>> > unauthorized and further distribution of this email is strictly
>> prohibited
>> > without the permission of ITG.  If you are not the intended
recipient
>> of
>> > this email, any review, disclosure, copying, distribution,
retention
>> or
>> > any action taken or omitted to be taken in reliance on it is
>> prohibited
>> > and may be unlawful.  If you are not the intended recipient of
this
>> email,
>> > you should not disseminate, distribute or copy this e-mail and you
>> should
>> > delete it and all copies of it from your system, destroy any hard
>> copies
>> > of it and notify the sender.  ITG and/or its affiliates reserve
the
>> right
>> > to monitor and archive all electronic communications through
its/their
>> > network.
>> >
>> >       The information contained in this email is believed to be
>> accurate at
>> > the time of publication.  However, ITG disclaims all
responsibility
>> for
>> > any loss or damage howsoever arising as a result of any person or
>> entity
>> > acting upon the information contained in this email and no
liability
>> will
>> > be accepted by ITG for any such loss or damage.  Any views
expressed
>> in
>> > this email are those of the individual sender, except where the
email
>> > states otherwise and the sender is authorized to state them to be
the
>> > views of ITG.
>> >       ++++++++++++++++++++++++++++++++++++++++++++++++
>> >
>> >
>> >
>> >
>> >
>> > >
>>
>>
>> >>
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++
>> The information contained in this communication is strictly
confidential
>> and intended solely for the use of the intended recipient(s). The
copyright
>> in this communication belongs to ITG Australia Ltd, ITG Hong Kong
Limited,
>> ITG Japan Limited, ITG Singapore Pte Ltd and/or their related entities,
>> including Investment Technology Group, Inc., (collectively referred to
as
>> "ITG") and may contain information that is private,
confidential or subject
>> to legal professional or other privilege.  No confidentiality or
privilege
>> is waived or lost by any mis-transmission of this email.
>>
>> Access to this email by anyone other than the intended recipient is
>> unauthorized and further distribution of this email is strictly
prohibited
>> without the permission of ITG.  If you are not the intended recipient
of
>> this email, any review, disclosure, copying, distribution, retention or
any
>> action taken or omitted to be taken in reliance on it is prohibited and
may
>> be unlawful.  If you are not the intended recipient of this email, you
>> should not disseminate, distribute or copy this e-mail and you should
delete
>> it and all copies of it from your system, destroy any hard copies of it
and
>> notify the sender.  ITG and/or its affiliates reserve the right to
monitor
>> and archive all electronic communications through its/their network.
>>
>> The information contained in this email is believed to be accurate at
the
>> time of publication.  However, ITG disclaims all responsibility for any
loss
>> or damage howsoever arising as a result of any person or entity acting
upon
>> the information contained in this email and no liability will be
accepted by
>> ITG for any such loss or damage.  Any views expressed in this email are
>> those of the individual sender, except where the email states otherwise
and
>> the sender is authorized to state them to be the views of ITG.
>> ++++++++++++++++++++++++++++++++++++++++++++++++
>>
>>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Thanks for that -- I''ll take a proper look later.

Is there any way to do versionable packages on Solaris?  I could''ve
sworn
the blastwave stuff could do it, but apparently not.  It''d be awfully
handy
to be able to tell puppet to install a specific version of a package.

Also, my apologies to the list for the stupid disclaimers on my previous
posts.  I''ve resubbed from my personal address to eliminate that
particular
avenue for looking like a prat.

Matt

Ohad Levy wrote:
> hmm, you just need the pkg-get and wget binaries (or packages) and than
> puppet will use the blastwave provider.
> for the repo, it will used whatever defined in pkg-get.conf, in my case, we
> a few different packages (blastwave, home made etc) which we put in our
> "pkg-get repo",  allowing puppet do use blastwave to download
them
> I use the following  script <http://pastie.org/302029> to generate
the repo.
> 
> Cheers,
> Ohad
> 
> On Tue, Oct 28, 2008 at 10:51 AM, McLeod, Matt <Matt.McLeod@itg.com>
wrote:
> 
> > In my case, because we''re not doing Blastwave packages,
we''re just doing
> > a few things we''ve built locally.  And because I
hadn''t thought of it.
> > :)
> >
> > Do you need to actually install pkg-get and the Blastwave base to make
> > this work, or does Puppet natively handle the repo?
> >
> > (Blastwave and friends tend to drag in dependencies that pollute our
dev
> > environments so we can''t use them in most cases.)
> >
> > Matt
> >
> > > -----Original Message-----
> > > From: puppet-users@googlegroups.com
> > [mailto:puppet-users@googlegroups.com]
> > > On Behalf Of Ohad Levy
> > > Sent: Tuesday, 28 October 2008 1:09 PM
> > > To: puppet-users@googlegroups.com
> > > Subject: [Puppet Users] Re: how to update solaris packages
without
> > keeping
> > > local copies
> > >
> > > Why not to create your own blastwave repo to use pkg-get with, or
am I
> > > missing anything here?
> > >
> > > Thanks,
> > > Ohad
> > >
> > >
> > > On Tue, Oct 28, 2008 at 8:41 AM, McLeod, Matt
<Matt.McLeod@itg.com>
> > wrote:
> > >
> > >
> > >       Sam Rowe wrote:
> > >       > Another quick point about this.. pkgadd isn''t
smart enough to
> > > handle a
> > >       > response file with packages installed this way.
> > >
> > >
> > >       It will however use an admin file.
> > >
> > >       Here''s what I have for installing packages on
Solaris systems:
> > >
> > >       define pkgadd {
> > >              $pkgrepo="http://pca.itgasiapac.com/pkgs"
> > >              package{"$name":
> > >                      source =>
"$pkgrepo/$name.pkg.$hardwareisa",
> > >                      ensure => installed,
> > >                      adminfile => "puppet",
> > >                      require =>
File["/var/sadm/install/admin/puppet"]
> > >              }
> > >       }
> > >
> > >       My "base" define which gets pulled in for
everything ensures
> > that the
> > >       admin file is in the right place.  This is a full-auto
admin
> > file.
> > > Then
> > >       I define packages I want installed thus:
> > >
> > >        pkgadd{ITGlsof:}
> > >
> > >       The hitch is that I''m not sure that puppet is able
to handle the
> > > Solaris
> > >       package version info -- pkgadd itself doesn''t
really either.  So
> > this
> > >       doesn''t keep packages updated, merely installs
them from the
> > > repository
> > >       if they''re not there.
> > >
> > >       What you *can* do, though, is have a sort of
"temporary" define
> > that
> > >       gets pulled in for all Solaris hosts, and when you update a
> > package
> > > you
> > >       can explicitly pkgrm it there.  It should then get the
updated
> > > version
> > >       installed.
> > >
> > >       A long way from perfect but if it''s happening
during a
> > maintenance
> > >       window then it isn''t *too* bad.
> > >
> > >       It ought to be possible to write a custom fact that
enumerates
> > all
> > >       package versions, though I think you''d want to be
careful and
> > either
> > > do
> > >       some caching or ignore anything starting with SUNW*.  It
would
> > > probably
> > >       then be possible to write an improved
''pkgadd'' define that also
> > takes
> > > a
> > >       version number and automatically updates if the installed
> > version is
> > >       older than the declared one.
> > >
> > >       Still not perfect but probably a whole lot better.
> > >
> > >       Matt
> > >
> > >
> > >
> > >
> > >
> > >       ++++++++++++++++++++++++++++++++++++++++++++++++
> > >       The information contained in this communication is strictly
> > > confidential and intended solely for the use of the intended
> > recipient(s).
> > > The copyright in this communication belongs to ITG Australia Ltd,
ITG
> > Hong
> > > Kong Limited, ITG Japan Limited, ITG Singapore Pte Ltd and/or
their
> > > related entities, including Investment Technology Group, Inc.,
> > > (collectively referred to as "ITG") and may contain
information that
> > is
> > > private, confidential or subject to legal professional or other
> > privilege.
> > > No confidentiality or privilege is waived or lost by any
> > mis-transmission
> > > of this email.
> > >
> > >       Access to this email by anyone other than the intended
recipient
> > is
> > > unauthorized and further distribution of this email is strictly
> > prohibited
> > > without the permission of ITG.  If you are not the intended
recipient
> > of
> > > this email, any review, disclosure, copying, distribution,
retention
> > or
> > > any action taken or omitted to be taken in reliance on it is
> > prohibited
> > > and may be unlawful.  If you are not the intended recipient of
this
> > email,
> > > you should not disseminate, distribute or copy this e-mail and
you
> > should
> > > delete it and all copies of it from your system, destroy any hard
> > copies
> > > of it and notify the sender.  ITG and/or its affiliates reserve
the
> > right
> > > to monitor and archive all electronic communications through
its/their
> > > network.
> > >
> > >       The information contained in this email is believed to be
> > accurate at
> > > the time of publication.  However, ITG disclaims all
responsibility
> > for
> > > any loss or damage howsoever arising as a result of any person or
> > entity
> > > acting upon the information contained in this email and no
liability
> > will
> > > be accepted by ITG for any such loss or damage.  Any views
expressed
> > in
> > > this email are those of the individual sender, except where the
email
> > > states otherwise and the sender is authorized to state them to be
the
> > > views of ITG.
> > >       ++++++++++++++++++++++++++++++++++++++++++++++++
> > >
> > >
> > >
> > >
> > >
> > > >
> >
> >
> > >
> >
> > ++++++++++++++++++++++++++++++++++++++++++++++++
> > The information contained in this communication is strictly
confidential
> > and intended solely for the use of the intended recipient(s). The
copyright
> > in this communication belongs to ITG Australia Ltd, ITG Hong Kong
Limited,
> > ITG Japan Limited, ITG Singapore Pte Ltd and/or their related
entities,
> > including Investment Technology Group, Inc., (collectively referred to
as
> > "ITG") and may contain information that is private,
confidential or subject
> > to legal professional or other privilege.  No confidentiality or
privilege
> > is waived or lost by any mis-transmission of this email.
> >
> > Access to this email by anyone other than the intended recipient is
> > unauthorized and further distribution of this email is strictly
prohibited
> > without the permission of ITG.  If you are not the intended recipient
of
> > this email, any review, disclosure, copying, distribution, retention
or any
> > action taken or omitted to be taken in reliance on it is prohibited
and may
> > be unlawful.  If you are not the intended recipient of this email, you
> > should not disseminate, distribute or copy this e-mail and you should
delete
> > it and all copies of it from your system, destroy any hard copies of
it and
> > notify the sender.  ITG and/or its affiliates reserve the right to
monitor
> > and archive all electronic communications through its/their network.
> >
> > The information contained in this email is believed to be accurate at
the
> > time of publication.  However, ITG disclaims all responsibility for
any loss
> > or damage howsoever arising as a result of any person or entity acting
upon
> > the information contained in this email and no liability will be
accepted by
> > ITG for any such loss or damage.  Any views expressed in this email
are
> > those of the individual sender, except where the email states
otherwise and
> > the sender is authorized to state them to be the views of ITG.
> > ++++++++++++++++++++++++++++++++++++++++++++++++
> >
> >
> 
> > 
-- 
* Matt McLeod | mail: matt@boggle.org | blog: http://abortrephrase.com/ *
     --- People can do the work, so machines have time to think ---

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Hmm... versions just work with pkg-get ;) give it a try

On Tue, Oct 28, 2008 at 2:08 PM, Matt McLeod <matt@boggle.org> wrote:
>
> Thanks for that -- I''ll take a proper look later.
>
> Is there any way to do versionable packages on Solaris?  I
could''ve sworn
> the blastwave stuff could do it, but apparently not.  It''d be
awfully handy
> to be able to tell puppet to install a specific version of a package.
>
> Also, my apologies to the list for the stupid disclaimers on my previous
> posts.  I''ve resubbed from my personal address to eliminate that
particular
> avenue for looking like a prat.
>
> Matt
>
> Ohad Levy wrote:
> > hmm, you just need the pkg-get and wget binaries (or packages) and
than
> > puppet will use the blastwave provider.
> > for the repo, it will used whatever defined in pkg-get.conf, in my
case,
> we
> > a few different packages (blastwave, home made etc) which we put in
our
> > "pkg-get repo",  allowing puppet do use blastwave to
download them
> > I use the following  script <http://pastie.org/302029> to
generate the
> repo.
> >
> > Cheers,
> > Ohad
> >
> > On Tue, Oct 28, 2008 at 10:51 AM, McLeod, Matt
<Matt.McLeod@itg.com>
> wrote:
> >
> > > In my case, because we''re not doing Blastwave packages,
we''re just
> doing
> > > a few things we''ve built locally.  And because I
hadn''t thought of it.
> > > :)
> > >
> > > Do you need to actually install pkg-get and the Blastwave base to
make
> > > this work, or does Puppet natively handle the repo?
> > >
> > > (Blastwave and friends tend to drag in dependencies that pollute
our
> dev
> > > environments so we can''t use them in most cases.)
> > >
> > > Matt
> > >
> > > > -----Original Message-----
> > > > From: puppet-users@googlegroups.com
> > > [mailto:puppet-users@googlegroups.com]
> > > > On Behalf Of Ohad Levy
> > > > Sent: Tuesday, 28 October 2008 1:09 PM
> > > > To: puppet-users@googlegroups.com
> > > > Subject: [Puppet Users] Re: how to update solaris packages
without
> > > keeping
> > > > local copies
> > > >
> > > > Why not to create your own blastwave repo to use pkg-get
with, or am
> I
> > > > missing anything here?
> > > >
> > > > Thanks,
> > > > Ohad
> > > >
> > > >
> > > > On Tue, Oct 28, 2008 at 8:41 AM, McLeod, Matt
<Matt.McLeod@itg.com>
> > > wrote:
> > > >
> > > >
> > > >       Sam Rowe wrote:
> > > >       > Another quick point about this.. pkgadd
isn''t smart enough to
> > > > handle a
> > > >       > response file with packages installed this way.
> > > >
> > > >
> > > >       It will however use an admin file.
> > > >
> > > >       Here''s what I have for installing packages on
Solaris systems:
> > > >
> > > >       define pkgadd {
> > > >             
$pkgrepo="http://pca.itgasiapac.com/pkgs"
> > > >              package{"$name":
> > > >                      source =>
"$pkgrepo/$name.pkg.$hardwareisa",
> > > >                      ensure => installed,
> > > >                      adminfile => "puppet",
> > > >                      require =>
> File["/var/sadm/install/admin/puppet"]
> > > >              }
> > > >       }
> > > >
> > > >       My "base" define which gets pulled in for
everything ensures
> > > that the
> > > >       admin file is in the right place.  This is a full-auto
admin
> > > file.
> > > > Then
> > > >       I define packages I want installed thus:
> > > >
> > > >        pkgadd{ITGlsof:}
> > > >
> > > >       The hitch is that I''m not sure that puppet is
able to handle
> the
> > > > Solaris
> > > >       package version info -- pkgadd itself doesn''t
really either.
>  So
> > > this
> > > >       doesn''t keep packages updated, merely
installs them from the
> > > > repository
> > > >       if they''re not there.
> > > >
> > > >       What you *can* do, though, is have a sort of
"temporary" define
> > > that
> > > >       gets pulled in for all Solaris hosts, and when you
update a
> > > package
> > > > you
> > > >       can explicitly pkgrm it there.  It should then get the
updated
> > > > version
> > > >       installed.
> > > >
> > > >       A long way from perfect but if it''s happening
during a
> > > maintenance
> > > >       window then it isn''t *too* bad.
> > > >
> > > >       It ought to be possible to write a custom fact that
enumerates
> > > all
> > > >       package versions, though I think you''d want
to be careful and
> > > either
> > > > do
> > > >       some caching or ignore anything starting with SUNW*. 
It would
> > > > probably
> > > >       then be possible to write an improved
''pkgadd'' define that also
> > > takes
> > > > a
> > > >       version number and automatically updates if the
installed
> > > version is
> > > >       older than the declared one.
> > > >
> > > >       Still not perfect but probably a whole lot better.
> > > >
> > > >       Matt
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >       ++++++++++++++++++++++++++++++++++++++++++++++++
> > > >       The information contained in this communication is
strictly
> > > > confidential and intended solely for the use of the intended
> > > recipient(s).
> > > > The copyright in this communication belongs to ITG Australia
Ltd, ITG
> > > Hong
> > > > Kong Limited, ITG Japan Limited, ITG Singapore Pte Ltd
and/or their
> > > > related entities, including Investment Technology Group,
Inc.,
> > > > (collectively referred to as "ITG") and may
contain information that
> > > is
> > > > private, confidential or subject to legal professional or
other
> > > privilege.
> > > > No confidentiality or privilege is waived or lost by any
> > > mis-transmission
> > > > of this email.
> > > >
> > > >       Access to this email by anyone other than the intended
> recipient
> > > is
> > > > unauthorized and further distribution of this email is
strictly
> > > prohibited
> > > > without the permission of ITG.  If you are not the intended
recipient
> > > of
> > > > this email, any review, disclosure, copying, distribution,
retention
> > > or
> > > > any action taken or omitted to be taken in reliance on it is
> > > prohibited
> > > > and may be unlawful.  If you are not the intended recipient
of this
> > > email,
> > > > you should not disseminate, distribute or copy this e-mail
and you
> > > should
> > > > delete it and all copies of it from your system, destroy any
hard
> > > copies
> > > > of it and notify the sender.  ITG and/or its affiliates
reserve the
> > > right
> > > > to monitor and archive all electronic communications through
> its/their
> > > > network.
> > > >
> > > >       The information contained in this email is believed to
be
> > > accurate at
> > > > the time of publication.  However, ITG disclaims all
responsibility
> > > for
> > > > any loss or damage howsoever arising as a result of any
person or
> > > entity
> > > > acting upon the information contained in this email and no
liability
> > > will
> > > > be accepted by ITG for any such loss or damage.  Any views
expressed
> > > in
> > > > this email are those of the individual sender, except where
the email
> > > > states otherwise and the sender is authorized to state them
to be the
> > > > views of ITG.
> > > >       ++++++++++++++++++++++++++++++++++++++++++++++++
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > >
> > >
> > >
> > > >
> > >
> > > ++++++++++++++++++++++++++++++++++++++++++++++++
> > > The information contained in this communication is strictly
> confidential
> > > and intended solely for the use of the intended recipient(s). The
> copyright
> > > in this communication belongs to ITG Australia Ltd, ITG Hong Kong
> Limited,
> > > ITG Japan Limited, ITG Singapore Pte Ltd and/or their related
entities,
> > > including Investment Technology Group, Inc., (collectively
referred to
> as
> > > "ITG") and may contain information that is private,
confidential or
> subject
> > > to legal professional or other privilege.  No confidentiality or
> privilege
> > > is waived or lost by any mis-transmission of this email.
> > >
> > > Access to this email by anyone other than the intended recipient
is
> > > unauthorized and further distribution of this email is strictly
> prohibited
> > > without the permission of ITG.  If you are not the intended
recipient
> of
> > > this email, any review, disclosure, copying, distribution,
retention or
> any
> > > action taken or omitted to be taken in reliance on it is
prohibited and
> may
> > > be unlawful.  If you are not the intended recipient of this
email, you
> > > should not disseminate, distribute or copy this e-mail and you
should
> delete
> > > it and all copies of it from your system, destroy any hard copies
of it
> and
> > > notify the sender.  ITG and/or its affiliates reserve the right
to
> monitor
> > > and archive all electronic communications through its/their
network.
> > >
> > > The information contained in this email is believed to be
accurate at
> the
> > > time of publication.  However, ITG disclaims all responsibility
for any
> loss
> > > or damage howsoever arising as a result of any person or entity
acting
> upon
> > > the information contained in this email and no liability will be
> accepted by
> > > ITG for any such loss or damage.  Any views expressed in this
email are
> > > those of the individual sender, except where the email states
otherwise
> and
> > > the sender is authorized to state them to be the views of ITG.
> > > ++++++++++++++++++++++++++++++++++++++++++++++++
> > >
> > >
> >
> > >
>
> --
> * Matt McLeod | mail: matt@boggle.org | blog: http://abortrephrase.com/ *
>     --- People can do the work, so machines have time to think ---
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---