Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Luna Node Dynamic | OpenStack KVM VPS | Toronto | Hourly billing
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Luna Node Dynamic | OpenStack KVM VPS | Toronto | Hourly billing

perennateperennate Member, Host Rep
edited August 2014 in Offers

Luna Node Dynamic - dynamic virtualization platform (KVM)

Luna Node Dynamic is an hourly billing virtualization platform featuring rapid virtual machine deployment, hourly billing, snapshotting capabilities, an API for automation, complementary minimal server monitoring / DNS hosting, and more. Virtual machines are provisioned in Toronto.

Luna Node has been around for over a year, offering reliable KVM virtual private servers at affordable prices. We use OpenStack for the Luna Node Dynamic backend.

Here's a more detailed feature explanation:

  • Hourly billing - you can create or destroy virtual machines at any time, and then only pay for the hours that VMs were used for. This allows you to provision test containers or scale your Internet application without having to pay for a month per container. The service is prepaid, with Paypal and Bitcoin (via Coinbase) as our current billing options.
  • Custom operating systems - simply submit a URL, and the system will download your ISO image or qcow2 template. Once downloaded, you can provision new virtual machines with the custom operating system. For ISO images, OS installation can be completed over VNC (noVNC client).
  • Snapshotting - hit a button to snapshot your virtual machine, and the current state of the disk image will be saved to our distributed filesystem. You can then use it to restore your virtual machine to a previous saved state or to provision more VMs. Snapshots are charged at $0.04 / GB / month (billed hourly); the first 20 GB is currently free but this is subject to change.
  • API - we provide a simple API that you can use to manage your servers without going through the web UI.
  • Track billing - a Billing tab is included in the Luna Node Dynamic panel that allows you to easily check your expenses for each month, with expenses sorted by day. Invoices are also posted at the end of each month for users who require such documents.
  • Floating IP addresses - you can keep IP addresses on reserve in your account for $1/month (billed hourly). This means you can easily switch an external IP address between different virtual machines on your account. Additionally, if you don't need a VM for the time being, you can snapshot it and then disassociate its floating IP address so that you only have to pay for the storage space and IP.
  • Redundant cloud storage - VMs may optionally be provisioned on top of a distributed, fault-tolerant filesystem to prevent data loss or downtime in case of a host node failure.
  • Private virtual networks - you can create a private virtual network, and the private interface of virtual machines in that network will be isolated from other clients. (Each network is $4/month, billed hourly.)
  • Load balancing, firewall, VPN as a service - inside your private network, these features are available. See https://wiki.lunanode.com/index.php/Virtual_networks for details. Currently you have to open a ticket for setup and configuration, but we are working on integrating virtual network service management into the Luna Node Dynamic panel.
  • Detachable volumes - create arbitrary-sized block devices (volumes) and attach/detach them to virtual machine instances on the fly. For example, you can store application data on a separate volume so that the OS can be upgraded independently.
  • Server monitoring - we offer basic server monitoring at no additional cost, where you can set up checks (e.g. ping, TCP connect), and receive notifications over email or SMS when the checks fail.

To get started, you can register an account from our panel; an initial deposit of $12.00 is required. After the initial deposit, more credit in smaller increments can be added when needed. We accept payments through Paypal and Bitcoin.

Plans

  • 512 MB - 1 vCPU, 15 GB storage, 1000 GB bandwidth, $0.005 hourly ($3.6 monthly)
  • 1024 MB - 2 vCPU, 20 GB storage, 1500 GB bandwidth, $0.0072 hourly ($5.18 monthly)

Port speed is 1 gbit/s. Click here for full plan list.

You can open a ticket within the first week to request a refund of remaining credit on your account, no questions asked.

Note that Canadian customers will be charged sales tax when adding credit, at 5.00% for those outside British Columbia and 12.00% for those in British Columbia.

Sign up for an account now!

Locations

Test IP for Toronto location (245 Consumers Rd 300 Toronto) is here: http://toronto-test.lunanode.com/100MB.test

About

LunaNode Hosting Inc. is a registered company based in British Columbia, Canada. We first launched in August 2013, focusing on low-cost, reliable KVM virtual private server hosting. We use OpenStack for our back-end and an in-house billing / VM management panel called lndynamic on the front-end (we also developed and continue to maintain pbobp, a free software billing panel, and use it for managed hosting services).

Upload your PGP key to https://lunanode.com/gpgmw to receive encrypted email from our mail server.

Links:

Comments

  • MuZoMuZo Member

    doesn't work, toronto-test.lunanode.com does 301 to lunanode.com --> resulting URL: https://www.lunanode.com/100MB.test

    Thanked by 1perennate
  • perennateperennate Member, Host Rep
    edited August 2014

    MuZo said: doesn't work, toronto-test.lunanode.com does 301 to lunanode.com --> resulting URL: https://www.lunanode.com/100MB.test

    Yes, we migrated our DNS server recently and the secondary DNS server was not updated with correct master IP, and the toronto-test was added a few days ago. I updated the secondary DNS server after making the post, it should update after an hour or so but your browser probably will cache the redirect.

    Thanks for letting me know.

    Here is the direct link: http://38.110.117.201/100MB.test

  • cogentco, cogentco and cogentco (pure cogentco?)

    Thanked by 1perennate
  • hbjlee17hbjlee17 Member, Host Rep
    edited August 2014

    @tommy said:
    cogentco, cogentco and cogentco (pure cogentco?)

    yes, yes and yes ( 100% cogentco )
    for now.

    Thanked by 2perennate tommy
  • Sadly you are no longer doing cheap alphassl wildcards. Other than that, nice offer.

    Thanked by 1perennate
  • IP's geo location comes up as USA, not Canada on the test IP. Are all of your IP ranges detected by ip2locaiton/maxmind as USA?

    Thanked by 1perennate
  • perennateperennate Member, Host Rep

    vpnarea said: IP's geo location comes up as USA, not Canada on the test IP. Are all of your IP ranges detected by ip2locaiton/maxmind as USA?

    New VMs are assigned to 170.75.160.0/20.

  • still needed 20$ deposit?

    Thanked by 1perennate
  • perennateperennate Member, Host Rep

    rokok said: still needed 20$ deposit?

    It is $12.00 for initial account deposit. After that you can add credit from $5.00.

  • Compared to mnx.io's 100$/month for private VLAN, 4$/ month is like a steal.

    But I still think private network should be free, it is the essential bits you can call yourself a cloud vm, just my 2 cents.

    Thanked by 1perennate
  • perennateperennate Member, Host Rep
    edited August 2014

    bookstack said: But I still think private network should be free, it is the essential bits you can call yourself a cloud vm, just my 2 cents.

    There is shared private network for all clients, if you want isolated private network then there is $4/mo fee for the virtual router.

  • @vpnarea said:
    IP's geo location comes up as USA, not Canada on the test IP. Are all of your IP ranges detected by ip2locaiton/maxmind as USA?

    Both of my traceroutes (from Toronto) appear to end up back in Torontol. Except, you'll notice that the last traceroute seems to redirect to 38.140.10.90

    $ traceroute 38.110.117.201

    traceroute to 38.110.117.201 (38.110.117.201), 30 hops max, 60 byte packets

    1 mail.esbohosting.com (67.213.93.179) 0.058 ms 0.026 ms 0.019 ms

    2 cr1.yyz01.3z.ca (208.68.88.178) 0.484 ms 0.471 ms 0.516 ms

    3 xe-3-3-0.cr1.tor1.ca.nlayer.net (69.31.143.153) 0.354 ms 0.383 ms 0.382 ms

    4 ae2-50.tor10.ip4.gtt.net (199.229.230.89) 0.355 ms 0.377 ms 0.562 ms

    5 te0-0-0-10.ccr21.yyz02.atlas.cogentco.com (154.54.13.73) 0.816 ms 1.142 ms 1.281 ms

    6 be2428.rcr11.yyz01.atlas.cogentco.com (154.54.1.94) 1.715 ms 1.714 ms 1.715 ms

    7 te0-0-2-1.nr11.b011152-1.yyz01.atlas.cogentco.com (154.24.4.46) 1.296 ms 4.024 ms te0-0-2-3.nr11.b011152-1.yyz01.atlas.cogentco.com (154.24.4.50) 3.957 ms

    8 38.140.10.90 (38.140.10.90) 1.187 ms 1.156 ms 1.125 ms

    9 201.117.110.38.rdns.lunanode.com (38.110.117.201) 1.117 ms 1.087 ms 1.057 ms

    $ traceroute 170.75.160.23

    traceroute to 170.75.160.23 (170.75.160.23), 30 hops max, 60 byte packets

    1 mail.esbohosting.com (67.213.93.179) 0.044 ms 0.025 ms 0.026 ms

    2 cr1.yyz01.3z.ca (208.68.88.178) 0.459 ms 0.455 ms 0.660 ms

    3 xe-3-3-0.cr1.tor1.ca.nlayer.net (69.31.143.153) 0.233 ms 0.268 ms 0.321 ms

    4 ae2-50.tor10.ip4.gtt.net (199.229.230.89) 8.346 ms 8.487 ms 8.449 ms

    5 te0-0-0-10.ccr21.yyz02.atlas.cogentco.com (154.54.13.73) 0.895 ms 0.874 ms 0.912 ms

    6 be2428.rcr11.yyz01.atlas.cogentco.com (154.54.1.94) 1.547 ms 1.655 ms 1.639 ms

    7 te0-0-2-3.nr11.b011152-1.yyz01.atlas.cogentco.com (154.24.4.50) 1.824 ms te0-0-2-1.nr11.b011152-1.yyz01.atlas.cogentco.com (154.24.4.46) 1.548 ms 4.565 ms

    8 38.140.10.90 (38.140.10.90) 1.076 ms 1.079 ms 1.083 ms

    9 te0-0-1-3.nr11.b011152-1.yyz01.atlas.cogentco.com (38.140.10.89) 1.933 ms 1.933 ms 1.959 ms

    10 38.140.10.90 (38.140.10.90) 1.196 ms 1.186 ms 1.156 ms

    11 te0-0-1-3.nr11.b011152-1.yyz01.atlas.cogentco.com (38.140.10.89) 1.825 ms 1.788 ms 1.579 ms

    12 38.140.10.90 (38.140.10.90) 0.901 ms 0.878 ms 0.912 ms

    13 te0-0-1-3.nr11.b011152-1.yyz01.atlas.cogentco.com (38.140.10.89) 1.546 ms 1.791 ms 1.802 ms

    14 38.140.10.90 (38.140.10.90) 0.970 ms 3.334 ms 3.213 ms

    15 te0-0-1-3.nr11.b011152-1.yyz01.atlas.cogentco.com (38.140.10.89) 3.406 ms 4.250 ms 4.210 ms

    16 38.140.10.90 (38.140.10.90) 3.031 ms 3.062 ms 2.990 ms

    17 te0-0-1-3.nr11.b011152-1.yyz01.atlas.cogentco.com (38.140.10.89) 12.525 ms 12.592 ms 12.553 ms

    18 38.140.10.90 (38.140.10.90) 12.273 ms 12.235 ms 12.216 ms

    19 te0-0-1-3.nr11.b011152-1.yyz01.atlas.cogentco.com (38.140.10.89) 12.361 ms 12.318 ms 7.921 ms

    20 38.140.10.90 (38.140.10.90) 7.304 ms 7.267 ms 7.476 ms

    21 te0-0-1-3.nr11.b011152-1.yyz01.atlas.cogentco.com (38.140.10.89) 7.765 ms 9.404 ms 9.371 ms

    22 38.140.10.90 (38.140.10.90) 7.305 ms 1.280 ms 1.216 ms

    23 te0-0-1-3.nr11.b011152-1.yyz01.atlas.cogentco.com (38.140.10.89) 3.889 ms 3.865 ms 3.836 ms

    24 38.140.10.90 (38.140.10.90) 2.098 ms 2.555 ms 2.456 ms

    25 te0-0-1-3.nr11.b011152-1.yyz01.atlas.cogentco.com (38.140.10.89) 4.039 ms 3.795 ms 3.764 ms

    26 38.140.10.90 (38.140.10.90) 1.321 ms 1.287 ms 1.217 ms

    27 te0-0-1-3.nr11.b011152-1.yyz01.atlas.cogentco.com (38.140.10.89) 3.754 ms 3.784 ms 3.978 ms

    28 38.140.10.90 (38.140.10.90) 1.712 ms 1.846 ms 1.809 ms

    29 te0-0-1-3.nr11.b011152-1.yyz01.atlas.cogentco.com (38.140.10.89) 3.757 ms 3.722 ms 3.672 ms

    30 38.140.10.90 (38.140.10.90) 1.723 ms 1.735 ms 1.720 ms

  • perennateperennate Member, Host Rep
    edited August 2014

    ub3rstar said: Both of my traceroutes (from Toronto) appear to end up back in Torontol. Except, you'll notice that the last traceroute seems to redirect to 38.140.10.90

    The 38.110.116.0/23 range is from Cogent and geo-iplocates to U.S., where Cogent is, since the geoiplocation takes from database. New VMs are mostly provisioned with IP addresses in 170.75.160.0/20 range.

  • very tempting, ping ip is good awesome on my side.

    may i know why people commenting about cogentco? isnt bad or good?

    Thanked by 1perennate
  • perennateperennate Member, Host Rep

    rokok said: may i know why people commenting about cogentco? isnt bad or good?

    Single-homed services (i.e., networks with only one upstream provider) hold the risk that if the upstream provider has issues such as fiber cuts, then BGP route changes away from that upstream provider would not be possible and packet loss may occur for several hours or days before the issues are resolved. Some people also believe, for example, that having Cogent as the sole upstream provider is worse than having GTT as the sole upstream provider, however in my experience Cogent has offered more reliable and consistent network connectivity than some other upstream providers (for example, one VM I had that seemed to be single-homed under GTT had continuous and unresolvable packet loss with a couple of eastern U.S. ISPs).

    We are planning on adding another upstream provider at some point, but it could be several months before this happens.

    Thanked by 1rokok
Sign In or Register to comment.