[openstack-dev] Anvil in action!
harlowja at yahoo-inc.com
Sun Aug 11 05:12:20 UTC 2013
A tip that seems useful.
If u are using firefox (or chrome) the terminal-casts look better in full-screen mode (at least when running in Linux mint). Your mileage may vary :P
Sent from my really tiny device...
On Aug 10, 2013, at 5:12 PM, "Joshua Harlow" <harlowja at yahoo-inc.com<mailto:harlowja at yahoo-inc.com>> wrote:
Since I thought it would be useful to show others a real example of anvil doing its thing (and since I wanted to try out this new website/tool that easily shows this) I created a terminal screencast that shows the different stages anvil goes through.
For those who have not tried anvil (or do not have easy access to a centos/rhel machine) below are some live examples that I recorded (showterm.io is pretty neat). Note that after the building stage the repositories that are created can be used by more than just anvil to do further installations of the same components (and there dependencies).
The walkthrough itself: http://anvil.readthedocs.org/en/latest/topics/gettingstarted.html
This is needed to get ready for the rest of anvils stages by installing anvils python dependencies so that anvil can correctly run using said dependencies.
This stage does the download of the source repositories, analysis of dependencies, download of missing dependencies and building of source repositories and missing dependencies into source rpms.
Directory structure after this stage: http://showterm.io/c9558f78582727432bbb9
This is the stage responsible for translating the previously prepared source rpms into installable rpms (of the non-source type). The output of this phase is two repositories, one with the dependencies and one with the rpms for the openstack components themselves.
Directory structure after this stage: http://showterm.io/6ec41fe645bb0e9423c1a
This is the stage that is responsible for ensuring the needed rpms are still available and installing them onto your system (using all the created dependencies and repositories from the previous stages). It also configures the components configuration files (paste for example) and sets up the needed databases and MQ components (rabbit or qpid).
This stage now starts the services for the individual components. At this stage, since each component was packaged as an rpm we also nicely included a set of init.d scripts for each component in its rpm; this starting support uses those init.d scripts to start those components up. It also goes about running the needed post-start actions, including downloading+installing an image for you, setting up keystone configuration and making your nova network.
This stage uses the service control layer to stop all components.
This removes the packages that were installed (+ it does some extra cleanup of some components dirty laundry that is sometimes left behind), restoring your environment back to its pre-installation state.
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev