immortal master
Reported by fairchild | November 24th, 2008 @ 04:57 PM
I would like to be able to set it so that poolparty cannot terminate my master instance. I have an ec2 instance that I use for other things, and keep on a 24/7. I would like to be able to use it as the master of a PP cloud, but not allow poolparty to ever shutdown this master instance.
Comments and changes to this ticket
-
Ari Lerner November 26th, 2008 @ 06:35 PM
I like this idea, but I think we can extrapolate the functionality and have a method that sets the master apart from the cloud. I think we can do a subsect like:
cloud :app do set_master_to "127.0.0.1" do using :ec2 end end
Thoughts?
-
Ari Lerner December 3rd, 2008 @ 03:45 PM
Sweet!
First, I apologize for the delayed response. I was hit with a bad case of food poisoning and have spent most of the last several days flat on my back in bed.
This shouldn't be too bad to add. There is an after_launched callback for callbacks on launching the instances so the plugins can overwrite those... There should be an easy method of calling that... not sure yet how the best approach to that is yet... but I'm sure it'll be pretty easy.
As far as the exporitng through NFS, how much experience do you have with that? Have you done that before?
-
Ari Lerner December 4th, 2008 @ 12:02 PM
Just fyi, the clouds take the place of iClassify, by design.
So, what I think the "best" option in this case would be would design a plugin and use the line:
has_nfs_share(:name => '...
Thoughts?
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Elastic cloud computing framework
Ari Lerner
fairchild