Hello John,
Thanks for your reply , sorry for providing less information .
I am working on developing websphere multi-node deployment module , in that
i have two roles one is deploymanager another is appserver.
I have a type and provider already created for it which run on the
deploymanager , which needs certain values like hostname , which would be
dynamically generated when the machine is provisioned .
@@websphere_profile { $servertype:
ensure => $ensure_profile,
hostname => $fqdn,
profilename => $ndm_profilename,
profilepath => $profilepath,
templatepath => $templatepath,
cellname => $cellname,
nodename => $nodename,
port => $start_port,
enableadminsecurity => $enableadminsecurity,
adminusername => $adminusername,
adminpassword => $adminpassword,
appservernodename => $appservernodename,
tag => websphere,
}
this resource type first runs on the deploymanager machine which gets
provisioned , making it exported resource will store its attributes value
in puppetdb .
Once this machine is completed , a new machine would be provisioned which
would be appserver , then appserver will also run this resource type
providing fqdn from the puppetdb of the deploymanager which is stored by
the exported resource.
Now this whole piece would be run by a end-user who will just see a catalog
, saying multi-node websphere.
*Another scenerio in case simultaneously two users runs that module , first
> machine save its hostname , same time again that module is intiated by
> another user , now the latest machine would overwrite the entry in
> puppetdb.*
>
>
*Why would you suppose that one machine's data would overwrite a different
one's? Puppet distinguishes one machine from another by their certs,
unless you intentionally confuse it by manually assigning the same cert to
multiple machines. Puppetdb associates node data with node identity, so
one node's data will not overwrite a different one's.*
Now if this catalog is ran by two users at the same time , as the exported
resource will save information with the tag websphere. As there would be
two multinode websphere deployment at the same time , how will puppet know
how appserver gets the hostname of its correct deploymanager.
Thanks for helping me out .
Regards,
Ritesh
On Thu, May 22, 2014 at 7:50 AM, jcbollinger <john.bollin...@stjude.org>wrote:
>
>
> On Wednesday, May 21, 2014 3:27:32 PM UTC-5, Ritesh Nanda wrote:
>>
>> Hello ,
>>
>> I am designing a multi-node deployment env with Puppet.
>>
>
>
> Ok.
>
>
>
>> Scenario i have is once one machine is created it will have its
>> hostname allocated dynamically ,
>>
>
>
> Ok.
>
>
>
>> that hostname has to be used by another machine when it runs it manifest
>> on it .
>>
>
>
> Huh? What other machine? What is "it"? And "it"? And "it"?
>
>
>
>> I can get that fqdn of that machine save it in puppetdb and ask another
>> machine to get that hostname using exported resource Is that correct?
>>
>>
>
> If you connect a client machine to your puppet master then compilation of
> the client's catalog can cause a resource to be exported that associates
> the client's hostname and fqdn. A Host resource would fill that role quite
> naturally. Supposing that you use puppetdb as your storeconfigs back end
> (as you should do), those data will be recorded in puppetdb. There are
> multiple things you can do with the data from there, but I'm not following
> what specific thing you are looking to do.
>
> The situation might be similar if you're using 'puppet apply' with local
> manifests instead of 'puppet agent' and a central master, but in that case
> there are likely to be much better ways to store local data than in
> puppetdb.
>
>
>
>> Another scenerio in case simultaneously two users runs that module ,
>> first machine save its hostname , same time again that module is intiated
>> by another user , now the latest machine would overwrite the entry in
>> puppetdb.
>>
>>
>
> Why would you suppose that one machine's data would overwrite a different
> one's? Puppet distinguishes one machine from another by their certs,
> unless you intentionally confuse it by manually assigning the same cert to
> multiple machines. Puppetdb associates node data with node identity, so
> one node's data will not overwrite a different one's.
>
>
> John
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Puppet Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/puppet-users/NM3vaVmOG1U/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/65b2db76-2f22-4e01-abdd-56258891e2a9%40googlegroups.com<https://groups.google.com/d/msgid/puppet-users/65b2db76-2f22-4e01-abdd-56258891e2a9%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
* With Regards *
* Ritesh Nanda*
<http://www.ericsson.com/>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAO5CbpCsBx%2BTa8YjGba4DxBGe%2Bxza4witfJ%3DWf%3DpKfEF8qu%2B4Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
