Hello,
I was about to propose a Fedora RDO remix, it's nice to know that i'm not
the only one with the idea.
The point here is to enhance the RDO experience so users can install a basic
OpenStack setup from the OS installation step instead of having to manually
setup repos, install packstack, configure and run it as it is recommended
right now on the RDO QuickStart page [1] which IMHO does not feel right.
There's a Fedora remix for digital jounalists and there's none for RDO!! [2].
I've talked about this with the Packstack and Puppet installers team and
the idea was well recieved so i'm more than happy to help on this effort.
The basic idea is:
- Integrate a lightweight installer like Packstack into anaconda
- Add Packstack options
- Standard: All in one install, everything is setup automatically
- Advanced: Allow the user to set Packstack options in the nice
way that anaconda does.
- Integrate the RDO repo into the ISO
This will need a lot of development if is decided to generate the remix
automatically wich each new OpenStack. Also it changes to Packstack might
be required since it's concieved to run in an already installed system and
it starts OpenStack services as dependencies while installing (most installers
will do this).
If you want to talk about this, i'm available in the #rdo channel with the nickname:
imcsk8
Let me know if you want to get trhough with this because it's very important
effort that could help boost RDO popularity.
[1]
From: "sad man" <asadxflow(a)gmail.com>
To: "Tom Buskey" <tom(a)buskey.name>
Cc: rdo-list(a)redhat.com
Sent: Thursday, June 18, 2015 3:53:59 PM
Subject: Re: [Rdo-list] GSoC Cloud in a Box
Thanks Tom, That's a great way to go about it but it totally eliminates any
programming/development from the task and as it is summer of code I need to
implement an open source code base. So do you have any suggestions for me
regarding maybe extending your idea to do some development?
Otherwise currently based on responses on this thread, I am going for
directly interfacing pack-stack with Anaconda (need to do more research on
exact nuts & bolts of it).
On 18 June 2015 at 22:44, Tom Buskey < tom(a)buskey.name > wrote:
On Thu, Jun 18, 2015 at 11:42 AM, Mohammed Arafa < mohammed.arafa(a)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(a)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(a)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(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
--
805010942448935
GR750055912MA
Link to me on LinkedIn
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
--
Cheers,
Asadullah Hussain
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com