[Rdo-list] GSoC Cloud in a Box

[Tom Buskey]

On Thu, Jun 18, 2015 at 11:42 AM, Mohammed Arafa <mohammed.arafa at gmail.com>
wrote:

> I am no programmer but packstack has taken 2 years or more to get where it
> is today by a team of developers (well definitely more than one :) ). I
> would not assume a single person can get anything reasonably close to that
> in one summer.
>
> from a sysadmin point of view, i'd think a kickstart file with a post
> install section containing the path to packstack and the parameters needed
> would be the method i'd use to deploy what you want. you can translate that
> into anaconda syntax/language/format if you like
>
>
>
packstack works quite well for non-HA, single node installs.

If you want to eliminate internet access after the OS install

   - kickstart a minimal base
   - login & rpm -qa | sort > pkgfile
   - set the yum cache to save all yum installed packages
   - run packstack & anything else you need to install
   - save all the packages from the yum cache
   - add the rpms listed in the pkgfile to that store
   - run createrepo against it to create your private repo

Now kickstart another base
put the private repo somewhere
create a repo file pointing at the private with file://

I'd suggest putting the original repo files on, but disabled.  If you need
a yum update beyond what's on the DVD, you can enable them and get them
over the net as needed.


>
> On Thu, Jun 18, 2015 at 11:26 AM, sad man <asadxflow at gmail.com> wrote:
>
>> Thanks a lot, So you are suggesting that I add RDO packages in ISO and
>> integrate packstack with Anaconda instead of writing my own OpenStack
>> installer script?
>>
>> On 18 June 2015 at 15:52, Haïkel <hguemar at fedoraproject.org> wrote:
>>
>>> Yeah, but configuring your OpenStack deployment from raw packages may
>>> be tricky and
>>> you won't be able to finish your GSoC if you go that path.
>>>
>>> Packstack is quite reliable and it will handle most of errors. I
>>> suggest that you include
>>> RDO packages in our ISO, that will remove the dependency on network hence
>>> the biggest failure cause.
>>>
>>> Regards,
>>> H.
>>>
>>
>>
>>
>> --
>> Cheers,
>>
>> Asadullah Hussain
>>
>> _______________________________________________
>> Rdo-list mailing list
>> Rdo-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/rdo-list
>>
>> To unsubscribe: rdo-list-unsubscribe at redhat.com
>>
>
>
>
> --
>
>
> <https://candidate.peoplecert.org/ReportsLink.aspx?argType=1&id=13D642E995903C076FA394F816CC136539DBA6A32D7305539E4219F5A650358C02CA2ED9F1F26319&AspxAutoDetectCookieSupport=1>
>
>   *805010942448935*
> <https://www.redhat.com/wapps/training/certification/verify.html?certNumber=805010942448935&verify=Verify>
>
> *GR750055912MA*
> <https://candidate.peoplecert.org/ReportsLink.aspx?argType=1&id=13D642E995903C076FA394F816CC136539DBA6A32D7305539E4219F5A650358C02CA2ED9F1F26319&AspxAutoDetectCookieSupport=1>
>
> *Link to me on LinkedIn <http://www.linkedin.com/in/mohammedarafa>*
>
> _______________________________________________
> Rdo-list mailing list
> Rdo-list at redhat.com
> https://www.redhat.com/mailman/listinfo/rdo-list
>
> To unsubscribe: rdo-list-unsubscribe at redhat.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rdoproject.org/pipermail/dev/attachments/20150618/e430f9fb/attachment.html>