Need clarification of workflow for content sources/repositories/packages
Steven North
swn at ocsystems.com
Wed Jul 6 23:39:40 UTC 2011
OK, let me back up. ;-)
What I am trying to do is move a zip file containing configuration
information back and forth from the server (or a client of the server)
to the agent plugin. The configuration includes some properties, which
might be candidates for <resource-configuration>, but it also includes
some other files that are not suitable for display. So, for now, I
wanted to treat the configuration zip as a single entity. The only
mechanism I saw that supported both pushing and pulling files was the
content facet, so that is what I was trying to use. It may be OK to
settle for a one-way interaction where the configuration is only pushed
to the agent, if necessary.
I looked at the indicated RHQ pages and read the JON Basic Admin guide,
but I still don't see how to use the content system appropriately.
But while rescanning the documents I see in the CLI Guide an example of
dealing with JBoss application JARs as resources and getting backup a
copy of the resource, so I think I will use that model because it more
closely matches what I want to do.
Thanks for the replies.
Steve
On 7/6/2011 3:08 PM, Charles Crouch wrote:
>
> ----- Original Message -----
>> some wiki pages that are related:
>>
>> http://rhq-project.org/display/JOPR2/Content
>> http://rhq-project.org/display/RHQ/Design-Content
>> http://rhq-project.org/display/RHQ/Design+-+Content+Synchronization
>>
>> Those last two are design pages, and may not reflect reality 100%.
>>
>> Synchronizing a repo is not related to subscriptions. So you don't
>> even
>> need to subscribe resources to a repository (or what was called a
>> channel in the past, I can't remember the verbage that was settled on,
>> I
>> think channel was renamed "repository" and content source is the same)
>>
>> All that does is it synchronizes the content found in your remote
>> system
>> (like a webserver, or git repo, or filesystem) to the RHQ repository.
>>
>> A plugin on the agent can auto-detect packages (what are called
>> InstallPackages) and the RHQ Server will log them so you can have a
>> record of what the resource has. They are not placed in any repository
>> that I am aware of (the last time this stuff was touched, I was not
>> involved in it, and the people that were involved I do no think are
>> actively working on the project anymore).
>>
>>> How do I know if I have configured
>>> things properly so that deployment will happen at the scheduled time
>>> (assuming it will)?
>> We do not automatically push out content to resources, you have to
>> manual push them out. I think you have a misunderstanding of what this
>> feature does.
>>
>> Perhaps you are thinking about the Bundle Provisoning subsystem (which
>> is loosely related to the repo/package stuff):
>>
>> http://rhq-project.org/display/JOPR2/Provisioning
>>
>> But that, too, does not perform any automatic scheduling of bundle
>> deployments. We actually do have code started down that path, but
>> right
>> now, there is no scheduling of bundles for automatic deployment in the
>> future.
>>
>>
> But I suspect if this "auto-deployment" was ever implemented it would be as part of the bundle subsystem, not the content subsystem.
> Given the bundle deployment actions are available via the CLI you could automate this with a CLI script. Then you just need fire that script off on a schedule.
> There are multiple ways to do that:
> -cron
> -create an alert that fires every hour and have it trigger the script, this feature is new in 4.0
> -an RFE to add the capability of scheduling a CLI script to execute
>
>>
>> On 07/06/2011 05:21 PM, Steven North wrote:
>>> I am trying to understand the workflow surrounding content sources,
>>> repositories, resources, and packages.
>>>
>>> I have files of type .xyz that are my content. I think those are
>>> called
>>> packages in RHQ. I have an agent that discovers the deployed .xyz
>>> packages for a given resource. Now I want to define the steps
>>> necessary
>>> to deploy new versions of the .xyz packages to the appropriate
>>> resources.
>>>
>>> I have defined a content source pointing to a directory with .xyz
>>> files. I have defined a content repository and associated the
>>> content
>>> source with it. I have subscribed the appropriate platform resource
>>> to
>>> the repository. I have clicked on Synchronize at various times
>>> during
>>> this process, but I never see any packages in the repository.
>>>
>>> Am I missing a step somewhere? How do I know if I have configured
>>> things properly so that deployment will happen at the scheduled time
>>> (assuming it will)?
>>>
>>> Is there a way to force a manual deployment? (I did see that I can
>>> go
>>> to a resource and "pull" the package to it from the
>>> Content->New->Upload
>>> New Package button.)
>>>
>>> What is the normal workflow for deploying new package content? Do
>>> you
>>> really go around to each destination resource/group and pull
>>> packages?
>>>
>>> Thanks in advance,
>>>
>>> Steve
>>>
>>> _______________________________________________
>>> rhq-devel mailing list
>>> rhq-devel at lists.fedorahosted.org
>>> https://fedorahosted.org/mailman/listinfo/rhq-devel
>> _______________________________________________
>> rhq-devel mailing list
>> rhq-devel at lists.fedorahosted.org
>> https://fedorahosted.org/mailman/listinfo/rhq-devel
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/rhq-devel
More information about the rhq-devel
mailing list