Activity
From 11/15/2011 to 11/21/2011
11/22/2011
-
05:09 pm Feature #10498: Implement 'node clean' as part of the 'node_aws terminate' process
- Hey Jeff,
I expect all the information to go away. The 'terminate' renders the instance un-revivable. If you just ...
11/21/2011
-
01:10 pm Bug #10990 (Closed): gems.erb cloudpack script contains incorrect (nonworking) yum repository
- ./lib/puppet/cloudpack/scripts/gems.erb in the cloud_provisioner puppet module creates a repository called 'epel' tha...
-
12:26 pm Bug #10988 (Needs More Information): installing puppet with cloud provisioner creates unusable ce...
- In bootstrapping an EC2 image using cloud provisioner the certificate generation leaves the host in a state that it c...
-
12:10 pm Bug #10871: Should be able to choose alternate fog credentials
- Self reminder: I have code to fix this in cloud-provisioner, but I have to port, commit, push, and send a pull request.
11/20/2011
-
01:24 pm Feature #10974 (Needs More Information): CP should support using instance IDs instead of just pub...
- Instances don't always have an public DNS name. EBS backed instances can be stopped, but not terminated. In this st...
-
01:09 pm Feature #10971 (In Topic Branch Pending Review): Cloud Provisioner should be able to set custom f...
-
11:16 am Bug #10970: Cloud Provisioner should be able to set custom facts during install
- Click "Change Propeties (More)" and you can change the tracker. No need to close and re-open.
-
11:14 am Feature #10971 (Merged - Pending Release): Cloud Provisioner should be able to set custom facts d...
- During the install of a node, CP should be able to set custom facts using facts.d. The format should be something li...
-
11:14 am Bug #10970 (Rejected): Cloud Provisioner should be able to set custom facts during install
- Ment to make this a feature, not a bug. Closing and making a new one
-
11:12 am Bug #10970 (Rejected): Cloud Provisioner should be able to set custom facts during install
- During the install of a node, CP should be able to set custom facts using facts.d. The format should be something li...
-
12:33 am Bug #10968 (Needs More Information): potential issues with reuse of puppet http method in classif...
- This is more of a heads up than a known issue with cloudprovisioner, I reused the same http connection code (Puppet::...
11/17/2011
-
11:47 am Feature #10922 (Needs More Information): puppet node_aws list should have the ability to filter o...
- Would like the ability to filter on state of instance, so that I could only list instances in a given state, such as ...
-
01:30 am Feature #10810: Add support for Rackspace Cloud Servers
- I will be working on the tests for this pull request today. Also, should this only get merged once it's 100% completed?
-
01:28 am Feature #10810: Add support for Rackspace Cloud Servers
- ## Pending Review ##
Pull request has been issued here: [https://github.com/puppetlabs/puppetlabs-cloud-provisione...
11/16/2011
-
09:55 am Bug #10871: Should be able to choose alternate fog credentials
- Relevant Fog changes: <https://github.com/fog/fog/pull/614>
-
09:31 am Bug #10871: Should be able to choose alternate fog credentials
- By default, fog will look for the `credential` symbol `:default` or the string stored in `FOG_CREDENTIAL` (in `lib/fo...
-
09:17 am Bug #10871: Should be able to choose alternate fog credentials
- Unless I am doing something wrong, exporting `FOG_CREDETIAL` does not work, unfortunately. It just acts as if there w...
-
04:33 pm Bug #10871 (Merged - Pending Release): Should be able to choose alternate fog credentials
- The cloud provisioner documentation says to put Fog crenentials in `~/.fog` under the `default` account name, which i...
Also available in: Atom