On Fri, Dec 9, 2011 at 1:42 PM, Peter Sellars <[email protected]> wrote:
> Is there any benefit to setting up two Artifactory instances - one for the
> ISO repository storage and another for the smaller artifacts - or is that
> overkill? (I suppose it would depend on the size of the ISO repository?)
>
Normally you wouldn't need to do this unless you foresee these repositories
managed and administered by different entities, possibly sitting in
different netwrok regions, or exposed to high loads that may interfere with
one another.
>
> At the moment I have just done a basic install on Ubuntu. Plan on moving
> it to use JBoss with MySQL database.
>
> I will set up initially with the filesystem-mysql and utilise some virtual
> repositories and take a look at the YUM repositories.
>
> Thanks for your advice
> Pete
>
>
> On Fri, Dec 9, 2011 at 9:23 PM, Yoav Landman <[email protected]> wrote:
>
>> I see. Storage configuration is global per Artifactory instance and
>> cannot be changed per repo.
>> The default is to store artifacts on the file-system and metadata in
>> DB. With databases, such as Oracle, that are doing efficient blob handling
>> you can have the binaries in the database, with the main benefit of being
>> able to bootstrap Artifactory from a simple DB backup.
>> The file-system based storage will work great for all your repositories -
>> ISO or regular smaller artifacts, so I'd stick with that. The default
>> bundled filesystem-derbydb will work great, though we typically recommend
>> using the filesystem-mysql configuration to offload the JVM.
>>
>> Yoav
>>
>> On Fri, Dec 9, 2011 at 8:13 AM, cato1971 <[email protected]> wrote:
>>
>>> Thanks for that information Yoav.
>>>
>>> I may not have been clear about were I intended to store the ISO files. I
>>> always intended to store them in Artifactory and had read about the YUM
>>> repositories which is something I will need to look into as well. My
>>> question was more around the way to configure the Artifactory repository.
>>>
>>> Can you assign storage types for each repository? I may be reading the
>>> user
>>> guide wrong, but I was under the impression that a repository can use a
>>> file
>>> storage or db storage and was asking if when using Artifactory I could
>>> set
>>> this up to have some repositories using file storage (those with ISOs
>>> etc)
>>> and others with default db storage? Can I and is it recommended to set
>>> the
>>> repository storage type to file based for the ISO repository?
>>>
>>> I had been reading about
>>> http://wiki.jfrog.org/confluence/display/RTF/Changing+the+Default+Storage
>>> Changing the Default Storage and wondered if this would enable me to use
>>> file storage managed by Artifactory rather than sticking ISO files in a
>>> database?
>>>
>>> I like the advice on using virtual repositories for common sets of
>>> install
>>> files too - something I shall have to experiment with.
>>>
>>> Any advice/suggestions based on these clarification more than welcome and
>>> thanks for taking the time to reply to my initial request.
>>>
>>> Pete
>>>
>>> --
>>> View this message in context:
>>> http://forums.jfrog.org/ISO-Storage-Advice-tp7076968p7077174.html
>>> Sent from the Artifactory - Users mailing list archive at Nabble.com.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Cloud Services Checklist: Pricing and Packaging Optimization
>>> This white paper is intended to serve as a reference, checklist and
>>> point of
>>> discussion for anyone considering optimizing the pricing and packaging
>>> model
>>> of a cloud services business. Read Now!
>>> http://www.accelacomm.com/jaw/sfnl/114/51491232/
>>> _______________________________________________
>>> Artifactory-users mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Cloud Services Checklist: Pricing and Packaging Optimization
>> This white paper is intended to serve as a reference, checklist and point
>> of
>> discussion for anyone considering optimizing the pricing and packaging
>> model
>> of a cloud services business. Read Now!
>> http://www.accelacomm.com/jaw/sfnl/114/51491232/
>> _______________________________________________
>> Artifactory-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>>
>>
>
>
> ------------------------------------------------------------------------------
> Cloud Services Checklist: Pricing and Packaging Optimization
> This white paper is intended to serve as a reference, checklist and point
> of
> discussion for anyone considering optimizing the pricing and packaging
> model
> of a cloud services business. Read Now!
> http://www.accelacomm.com/jaw/sfnl/114/51491232/
> _______________________________________________
> Artifactory-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
>
------------------------------------------------------------------------------
Cloud Services Checklist: Pricing and Packaging Optimization
This white paper is intended to serve as a reference, checklist and point of
discussion for anyone considering optimizing the pricing and packaging model
of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
