You can set up a VPC in amazon and then assign a private ip address to the network interface associated with an instance.
If you set up your own DNS for the VPC then you can associate the hostname of the instance with the ENI ip address. If your hostname resolution is based on both file and DNS (a la nsswitch.conf or some such) then the hostname is determined by DNS lookup and you're good to go. I don't have the command line options in front of me to give you and I haven't done this in a year but, at a previous job I ran SGE on Amazon in a VPC with my own DNS and a route into our company network. We could launch jobs from our local network into the cloud. It was pretty cool. If you're interested in this route I could see about working out the details again from my notes. I think Amazon still allows free developer access to a VPC and a small collection of instances. The solution might be overly complex for your needs, though. John. On Mon, Jan 27, 2014 at 6:13 PM, Ed Lauzier <[email protected]> wrote: > Update: > > Finally coaxed it to work after a bit of cleanup..... > > put desired hostname on loopback address. > > example 127.0.0.1 localhost.localdomain localhost > myhostname.mydomain.commyhostname > act_qmaster set to the desired hostname > cleaned up queue, admin, and sub host entries.... > > set hostname at the top of sgeqmaster script: > > ex: > > sysctl kernel.hostname=myhostname > rebooted to check. > > works well now. > > One thing in startup script, had to tell it qmaster_host=true one time so > that it would > at least start up with the new name w/o issues once. then, removed the > line and restarted > the instance to check. > > All seems well. > > So the result is a standalone instance of soge 8.1.6 on aws ec2 that will > not be effected by > dhcp host name and ip addr changes..... > > Not standard by any means, but fits our app profile needs for slice and > dice modelling work > on a single multicore host..... > > -Ed > > -----Original Message----- > *From:* Bill Bryce [mailto:[email protected]] > *Sent:* Monday, January 27, 2014 04:45 PM > *To:* 'Ed Lauzier' > *Cc:* 'Chi Chan', [email protected] Group > *Subject:* Re: [gridengine users] soge 8.1.6 - on a standalone aws ec2 > instance with dhcp > > Grid Engine certainly doesn't like it when you use the loopback 127.0.0.1 > for the hostname...if that is what you were intending to do. > > Regards, > > Bill. > > On Jan 27, 2014, at 4:33 PM, Ed Lauzier <[email protected]> wrote: > > I try to avoid using the loopback address for hostname, but may be ok for > a standalone > instance....( like fedora desktop systems used to do....and maybe still > do....) > > I'll give it a shot and see how it works. > I also use x11 graphical tools in the instance ( rstudio... R > plots.....etc....) > > Thanks, > > Ed > > > > -----Original Message----- > *From:* Chi Chan [mailto:[email protected] <[email protected]>] > *Sent:* Monday, January 27, 2014 04:24 PM > *To:* 'Ed Lauzier' > *Cc:* [email protected] > *Subject:* Re: [gridengine users] soge 8.1.6 - on a standalone aws ec2 > instance with dhcp > > There is nothing that special about AWS EC2. What you get is a Xen VM on a > standard DHCP network. You can set the localhost hostname using standard > methods like /etc/hosts when your VM boots. --Chi On Mon, Jan 27, 2014 at > 3:24 PM, Ed Lauzier wrote: > Hi, > > Anyone have experience with aws ec2 > and gridengine for a standalone instance > running ge with dhcp enabled? > > > Is there a way to configure the ami so that if the ip address and > hostname > change it will not effect the instance of ge. > > Ex: 16 core 30 > GB ram with EBS storage 200 GB and where the ip addrss > and hostname may > change when the instance is stopped and restarted. > > I guess we could > have a wrapper starter script to set things up > automagically > every time > the instance is started. > > Thanks, > > Ed > > > > _______________________________________________ > users mailing list > > [email protected] > https://gridengine.org/mailman/listinfo/users > > > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users > > > > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users > >
_______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
