Hot answers tagged joyent
As you said, this isn't exactly an apples to apples comparison (in addition there is agreement already, that decent data backup procedures must be in place for both, so I'm not going to address this). Therefore the question cannot be answered as such, rather one should be aware of the architectural details of each offering and apply those in respect to a ...
SmartOS is an open-source distribution of the illumos operating system, a Solaris derivative. It supports KVM as a first-class citizen. With KVM, you can boot a Linux instance that will appear in most ways just like running Linux on bare metal. You manage the Linux instance entirely yourself, so you can install whatever packages you want. Similarly, you can ...
There isn't a way to upgrade from one base image to another. You would have to provision a new base image and migrate what you have over. However, you can update an existing base image to a newer pkgsrc release though. That tends to be what people typically want, access to the newer packages. There are instructions on how to do that here: ...
You can use puttygen to generate your ssh key. The steps are: Choose "SSH-2 RSA" Click "Generate" Follow the instruction (move mouse randomly) After the key has been successfully generated, paste the string in below the "Public key for pasting into OpenSSH authorized_keys file:" into the ssh-keys list in your Joyent Node account Save the private key by ...
S3 doesn't support rsync out of the box. However, you can use FUSE and s3fs to create a file system over S3 and then rsync there. From there, you can follow this guide on setting up the whole thing.
Creating an ISCSI Target enable the storage server and iscsi target server if necessary svcadm enable stmf svcadm enable -r svc:/network/iscsi/target:default create a volume if necessary (sparse 10T in example) zfs create -V 10T -s zones/iscsi create a logical unit sbdadm create-lu /dev/zvol/rdsk/zones/iscsi Add a view on it (GUID is output by ...
All of your needs can be met by the logs in /var/svc/log. Those are the logs for everything SMF is doing to your system, behind the scenes. Extracting the 'interesting' data is left as an exercise for the reader.
You might also choose to implement additional monitoring with Nodefly, NewRelic, Pagerduty, Pingdom, or any of nagios, Munin, or zabbix. You have a lot of choices available.
Try replacing 0.0.0.0 with the IP you actually want the connection to be forwarded to. E.g.: ssh -vgR *:12043:localhost:8843 firstname.lastname@example.org
You don't have the data unless you have it in triplicate at two geographically different locations. Depending on single RAID instance, virtual block device, single supplier, etc. to reliably store your data is careless at best. That being said, unless nothing changed during past 2-3 years since I last checked, Amazon doesn't give any guarantee that S3 data ...
Only top voted, non community-wiki answers of a minimum length are eligible