summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* More cloud functionalityGreg Blomquist2008-06-181-2/+3
|
* Switching to the new command name - func-find-resourcesGreg Blomquist2008-06-181-1/+1
|
* Greg's changes to support koaning through funcGreg Blomquist2008-06-183-32/+105
|
* Merge branch 'master' of it@hackathon1-repo.usersys.redhat.com:/pub/git/toolsGreg Blomquist2008-06-182-0/+14
|\
| * Updating build README instructionsMatthew Hicks2008-06-181-2/+6
| |
| * Moving all the func changes to a public repo and changing theMatthew Hicks2008-06-186-287/+2
| | | | | | | | README to reference that until those changes are upstream
| * Reshuffling the patches to match upstream submissionsMatthew Hicks2008-06-183-25/+0
| |
| * Adding a find-resource script to funcMatthew Hicks2008-06-182-0/+182
| | | | | | | | Fixing a file handle leak during virt install
| * Adding the func patches used to build a custom version of funcMatthew Hicks2008-06-174-0/+138
| | | | | | | | until those patches are accepted upstream
* | Adding support for a "cloud" mode in everest-bootstrapGreg Blomquist2008-06-176-3/+178
|/ | | | | | | | | | | ------------------------------------------------------ The "cloud" mode acts like the "wizard" in the standard mode of everest-bootstrap in that it asks relevant questions for provisioning a new machine. After collecting the standard information, it registers the new system with cobbler and with everestd. It then asks everestd to koan the new machine. Adding support to everestd to call func to koan a requested machine on the most suitable everest host ----------------------------------------------------------------------------------------------------- Now everestd asks "cloud-inventory" which host/vol_group combination is the best fit for a particular machine. Then, everestd will delegate to func to koan the new machine on the host/vol_group combination.
* Adding maximum retries to the exec_command methodMatt Hicks2008-06-153-7/+54
| | | | Starting a test suite for everest-lib
* Removing the gwt codeMatt Hicks2008-06-1544-2986/+0
|
* Ignoring package additionsMatt Hicks2008-06-141-0/+1
|
* Removing pkg directory and filesMatt Hicks2008-06-1431-2840/+0
|
* More library changesMatt Hicks2008-06-145-9/+54
|
* Adding some more app functionMatt Hicks2008-06-1125-0/+2660
|
* More flexible command parsing added (regex based pattern matching)Matt Hicks2008-06-114-20/+36
|
* Adding support for returning a specific vmMatt Hicks2008-06-114-14/+34
|
* Moving xm calls to virshMatt Hicks2008-06-114-2/+2
|
* Moving xm library to generalized vmMatt Hicks2008-06-112-2/+2
|
* Moving xm library to generalized vmMatt Hicks2008-06-114-6/+6
|
* Initial round of library functionsMatt Hicks2008-06-1061-0/+5732
|
* Removing swap fileMatt Hicks2008-06-091-0/+0
|
* Initial ev commitMatt Hicks2008-06-0925-0/+2784
|
* Current soademo stateMatt Hicks2008-06-092-0/+170
|
* workingMatt Hicks2008-06-094-95/+88
|
* Sort of workingMatt Hicks2008-06-094-224/+129
|
* Adding soademo web app to the misc toolsMatt Hicks2008-06-0939-0/+9839
|
* Adding demo code to bring up a tomboss stackMatthew Hicks2008-06-027-0/+286
|
* Fix minor but in everest-bootstrap whenever parameters have no defaultsBrenton Leanhardt2008-05-123-4/+5
|
* everest-bootstrap will now clean up stale Xen configurationsBrenton Leanhardt2008-05-011-0/+9
|
* Adding colorization to everest-bootstrapBrenton Leanhardt2008-05-012-10/+14
| | | | Hopefully this will make the output a little easier to read
* Adding an 'advanced' mode to everest-bootstrapBrenton Leanhardt2008-05-013-20/+65
| | | | | This allows you to pass in a yaml description for a node type via stdin or with the --yaml option. See 'everest-bootstrap advanced -h' for more info.
* Updates to everest-bootstrap to support everestdBrenton Leanhardt2008-05-014-164/+147
| | | | | | | | | | | | | | | | | | | | | | These changes are to support a oneliner provisioning story in the Everest environment. New features: * We use facts instead of parameters. The can be create prior to koaning a machine. They can also be managed centrally in a more efficient manner. * uses the cobbler xmlrpc api to allow users to select which OS that would like to use for their machine type. * it's now possible to optionally use Red Hat's DDNS * added a '--config-only' option. This does not need to be run as root in that case. This is useful if you simpy want to update a machine's parameters. This will also be useful when it comes time to port machines over to the use of parameters. The machines already exist therefore they don't need to be koaned. TODO: everest-bootstrap will kick of koan but after it finishes the machine will not start back up. We can either do some trickery to make the tool smart enough to know when it finishes or we can try and find a way for Xen to reboot the machine automatically.
* Committing everestdBrenton Leanhardt2008-04-2832-0/+3039
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | everestd is a simple service for handling our everest machine types. Currently is serves the following purposes: 1) Backend service for everest-bootstrap 2) Creates the yaml files used for Puppet's external nodes. Usage: Once installed simply browse to http://[hostname]:8601/nodes.html. From there it should be easy to navigate to the rest of the functionality. Most resources have several representations. Try changing 'html' to 'xml' or 'yaml' in the urls. Configuration: The config file gets laid down in /etc/everestd/ In the future it could be switched to use a db for storing the external node data. This would allow us to do some interesting things but it would make bootstrapping a repo more complicated. Currently Puppet installs everestd once it has alread been bootstrapped. Since our external node script simply looks to the yaml files on disk Puppet doesn't even have to know everestd exists. This is also closer to how Prod Ops manages there external nodes. Implementation details: everestd uses the everest gem to get at the machine type information for a particular repo. This is similar to how our old external nodes script worked. For the web portion everestd makes use of the camping microframework. This includes the reststop library for restful controllers and views as well as the the picnic gem for the service script. Yay for stupid names. The gem was created with newgem and the rpm spec file was generated with gem2rpm. TODO: * make the yaml node dir configurable. * consider allowing machines to be configured/koan from the web ui (as a possible replacement for everest-bootstrap)
* Fixing typoBrenton Leanhardt2008-03-052-3/+3
| | | | This is precisely why I need to unit::test this stuff
* Major overhaul on everest-bootstrapBrenton Leanhardt2008-03-0425-203/+897
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The major goal of this patchset is to consolidate all machine types and their corresponding facts logic in one place. As more machine types were getting created it became unrealistic to have all facts on all machine types. There were also quite a few complexities involved in the ordering of regexes and such which made the whole process very error prone. There is now a config file dropped in /etc/everest by puppet that houses all the logic. The external nodes script, the nodetypes cgi, and everest-bootstrap all use that file as the canonical source of information. Another goal of this patchset is to have all the various responsibilities of everest-bootstrap at the same level of abstraction. The way we were using the 'main' gem was a little out of hand. In one block you had configuration, bootstrap logic and two different DSLs. That was a little absurd. This will allow us to test the tool alot more. I even committed a vew trivial unit tests for the DDNS stuff. Instead of adding more and more complex command line options I'm taking the 'wizard' approach. This should help to educate people and over time we can make this a little more non-interactive. Tickets fixed: Making the regex used for scraping the DDNS hash a little more strict https://engineering.redhat.com/trac/IT_Architecture/ticket/71 Added some tests Removing CGI call from everest-bootstrap https://engineering.redhat.com/trac/IT_Architecture/ticket/40 Host bootstrapping will now prompt the user to finish https://engineering.redhat.com/trac/IT_Architecture/ticket/45 everest-bootstrap will now forcefully unmout when cleaning up https://engineering.redhat.com/trac/IT_Architecture/ticket/39 everest-bootstrap now requires '--repo' https://engineering.redhat.com/trac/IT_Architecture/ticket/77 Improving everest-bootstrap DDNS error message https://engineering.redhat.com/trac/IT_Architecture/ticket/65
* A simple prototype for backing up Xen guests to S3Brenton Leanhardt2008-02-1844-0/+1048
generated by cgit (git 2.34.1) at 2025-09-28 15:53:11 +0000